Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 312153

Summary: CollabNet TeamForge Wiki markup not supported
Product: z_Archived Reporter: Wolfgang Strunk <eclipse>
Component: MylynAssignee: David Green <greensopinion>
Status: RESOLVED NOT_ECLIPSE QA Contact:
Severity: enhancement    
Priority: P3 CC: markphip
Version: 1.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
mylyn/context/zip none

Description Wolfgang Strunk CLA 2010-05-08 06:34:44 EDT
Build Identifier: M20090917-0800

CollabNets TeamForge uses its own wiki markup language which is based on an old version of JspWiki (http://www.jspwiki.org/). Although there is a Mylyn connector for  TeamForge available, the wiki markup is not supported by WikiText yet.



Reproducible: Couldn't Reproduce
Comment 1 Wolfgang Strunk CLA 2010-05-08 06:36:51 EDT
I am already working on an implementation. Currently I am unclear how unit testing is done in the WikiText subproject. I can't see any examples in implementations for the other supported markup languages.
Comment 2 David Green CLA 2010-05-10 10:23:07 EDT
Wolfgang, thanks for the enhancement request.   Great to hear that you've already got a start.  

It's not the intention of the Mylyn WikiText project to directly support every wiki syntax. It's expected that third parties will use Mylyn WikiText as a framework and add on extensions to support wiki syntaxes. Currently Mylyn WikiText supports syntaxes for which there is a corresponding Mylyn connector, and MediaWiki which is the backbone of EclipsePedia.

I hope that you've already found the Mylyn WikiText Developer Guide, which comes with the Mylyn WikiText SDK.  It should give you a good start.  It can also be very useful to look at existing markup language implementations in WikiText, of which TextileLanguage is a good place to start looking.  Unit tests are critical in developing a markup language correctly, I highly recommend taking a look at TextileLanguageTest.  To get source for unit tests you'll need to set up your workspace with source projects, see the "Mylyn Contributor Reference":http://wiki.eclipse.org/Mylyn/Contributor_Reference#Setup for details.

I've attached a Mylyn Context pointing to TextileLanguage and TextileLanguageTest.

Feel free to use the mylyn-dev@eclipse.org for any questions that you might have, and as you proceed feel free to contribute to the developer guide.
Comment 3 David Green CLA 2010-05-10 10:24:41 EDT
Created attachment 167714 [details]
mylyn/context/zip
Comment 4 Mark Phippard CLA 2010-05-10 11:37:14 EDT
Wolfgang, I am confused.  The CollabNet TeamForge connector has supported this since August 2009 when version 1.10 of the CollabNet Desktop was released. Current version is 2.0.

Source code is here:

http://desktop-eclipse.open.collab.net/source/browse/desktop-eclipse/trunk/plugins/com.collabnet.ee.tracker.core/src/com/collabnet/ee/wikitext/

This feature is even on by default.
Comment 5 Wolfgang Strunk CLA 2010-05-11 02:19:00 EDT
Mark, I wasn't aware of the WikiText implementation in CollabNet desktop. If I got David's comment right, that is exactly the right place to put it and therefore this  bug should be closed.

Looking at CollabNet's implementation, unfortunately only a part of the markup language is supported. I am missing
- css changes like %%(color: yellow;)some text in yellow%% 
- replacement of  CamelCase words
- table of contents

Is that due to the fact, that the trackers don't support full wiki markup?
Mark, is it possible to contribute to your implementation?
Comment 6 Mark Phippard CLA 2010-05-11 08:15:08 EDT
(In reply to comment #5)

> Looking at CollabNet's implementation, unfortunately only a part of the markup
> language is supported. I am missing
> - css changes like %%(color: yellow;)some text in yellow%% 
> - replacement of  CamelCase words
> - table of contents

I do not believe any of the Eclipse wiki text implementations are a full-blown implementation of their respective wiki's.  It is just used for some basic formatting capabilities so that you can have lists and some text formatting in artifact comments etc.

> Mark, is it possible to contribute to your implementation?

The CollabNet Desktop is EPL licensed and we will review and accept patches.
Comment 7 David Green CLA 2010-05-11 19:41:54 EDT
Resolving NOT_ECLIPSE, since this is clearly a CollabNet issue.
Feel free to continue the discussion here, though it may make sense to move it to a CollabNet issue tracker.