Jochen,
I agree with you that XSLT for the task is overkill and excessively
complicated.
The kind of code generated is fairly simple.
I was thinking of moving away entirely from code generation using any
out-of-band code generators. Instead, we could use Java annotations to
generate the thinks we need, so we stay within Java-land as much as
possible.
Thoughts?
Vinayak
Jochen Wiedmann wrote:
Hi, Vinayak,
first of all, in the medium term, I personally find XSLT much too
complicated. IMO, using a template system like FreeMarker or even a
fully blown source generator framework like OpenArchitectureWare would
be a much better solution. But that's for the medium term.
For XSLT, there are a number of options:
- Use the maven-antrun-plugin, in other words Ant. The easiest way to do so
would be to move the generation stuff to a separate build.xml,
which is configurated
through some properties and invoke that from both the current build.xml and
the Maven POM. This is the best solution as long as both Maven and Ant are
in use.
- Use the xml-maven-plugin, which is basically the Maven replacement for Ant's
xslt task.
Jochen
On Sun, Oct 4, 2009 at 5:45 PM, Vinayak Borkar <[email protected]> wrote:
Jochen,
Do you know how we could use maven and continue to generate the .java files
currently generated by XSLT?
Thanks,
Vinayak
Jochen Wiedmann wrote:
On Sun, Oct 4, 2009 at 12:52 PM, Till Westmann <[email protected]> wrote:
Is this something we could achieve during this week?
The build.xml is a little bit complex. I wouldn't expect to have a
complete migration in one go. A partial migration is more than
realistic.
Also, what would be the best thing for me to do to help (and not to step
on
your feet)?
If you feel that you have some Maven know how (or even just if you'd
like to learn it): Feel free to create an initial pom.xml to play
with. Just make sure that you commit from time to time (and check for
updates on the other hand).
Jochen
