Community
Participate
Working Groups
The idea is to create a resource plugin that collects/filters documentation artifacts during maven build time. overall idea: http://dev.eclipse.org/mhonarc/lists/wtp-incubator-dev/msg01180.html uses cases that benefit are here: http://tech.groups.yahoo.com/group/dita-users/message/17273 * This maven plugin needs to be available in a maven repository for other people to use it. * It should be possible to collect or/and filter documentation resources, code resources and perhaps also images. (The main targets are documentation and code artifacts). * Option to make compliance mandatory or optional. i.e. the build would fail if something expected is not there. * The plugin should also be able to run within the Eclipse IDE, (m2eclipse as a starting point). Maven 2.1 or above compatibility is expected. * Create documentation and a realistic example of usage and lifecycle * JUnit test * May contribute support an archetype
Moved to Mylyn Docs Vex.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn