[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [wtp-incubator-dev] maven support for DITA
|
Open a separate bug for Dita 1.2 support, we have DITA 1.1 DTDs approved
by IP, but will need to send any updated specification through IP review
in order to include it.
I have no problem with adding a Maven plugin that is built at WTP and
distributed. However we need to make sure that the build and the
artifacts produced can be integrated into the overall WTP build
eventually. There are ways to do this, but we'll have to work things out.
Open a bug for option 4 and 3, and you might want to look at integrating
or reusing some of the framework from the existing eclipse maven frameworks.
http://www.eclipse.org/projects/project_summary.php?projectid=technology.m2e
http://www.eclipse.org/projects/project_summary.php?projectid=technology.iam
I would make these optional features, just because they aren't required
for the Core functionality of Vex.
Dave
On 05/06/2010 05:19 AM, Igor Lino wrote:
Hi VEX developers,
I have created a concept some months ago for DITA documentation in maven-based continuous integration builds which is to assemble parts of the documentation dynamically. Maven and maven plugins are a requirement at the build time.
For this concept to come to an implementation, I need some tooling support:
1) An editor that supports inclusion of code (DITA 1.2 feature)
2) A dita maven plugin that compiles the PDF during build time (already exists at http://mojo.codehaus.org/dita-maven-plugin/ [apache 2.0 license])
3) An custom resource plugin that collects/filters documentation artifacts during maven build time. (not existing)
This would have to be available in a maven repository for other people to use.
4) An IDE [wizard] that enables project creation with maven support. This would mean, that it would create a proper pom.xml with adecuate maven dependencies.
VEX currently does not have any of it #1 - #4.
I would like to work on it (#1, #3, #4), and I'm wondering if we can have a maven plugin (#3) as part of the framework, and also if that plugin can be automatically deployed to some maven repository.
Any thoughts on maven support?
Thanks,
Igor
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
