. The plugin seems to get quite complicated which I think should be
possible to avoid
Anyone having experience with this kind of setup? Any best practices out
there?
best regards
Tomas
--
View this message in context:
http://www.nabble.com/Best-practice-for-source-generating-multiple
think should be
possible to avoid
Anyone having experience with this kind of setup? Any best practices out
there?
best regards
Tomas
--
View this message in context:
http://www.nabble.com/Best-practice-for-source-generating-multiple-archetype-plugin-tf2622203s177.html#a7361402
Hi,
We have a tool that given one input file generates code for different
purposes (currently j2me, j2se, ansi-c). I'm planning to write an m2 plugin
for this tool but I'm not really sure how to do it.
What I'm trying to achieve is to only have one copy of the original input
file and whenever
if the
plugin/underlying tool changes for one mode, but not the others.
/jonas
-Ursprungligt meddelande-
Från: Tomas Carlsson [mailto:[EMAIL PROTECTED]
Skickat: den 13 november 2006 14:17
Till: users@maven.apache.org
Ämne: Best practice for source-generating multiple archetype plugin
Tomas Carlsson [EMAIL PROTECTED] writes:
Hi,
My initial thought is to create a plugin that first generates sources for
the different purposes, then compiles them and lastly packages one archive
for each type.
I.e:
1 input file = 3 generated source trees = 3 compiled classes tress =
3
