Are you sure that you absolutely need parameterized Java code? There's really no good way to work with it. You could instead use the maven-shade-plugin to customer-ize your results as part of their build.
On Sun, Mar 9, 2014 at 3:36 PM, Petar Tahchiev <[email protected]> wrote: > Hey guys, > > here's an interesting question: how do you develop your maven archetypes? I > have a web-project that consists of lots of controllers and jsps, and I > have been developing this for a long time, and I want to keep developing > it. I also want to provide this project to my clients as an archetype so > they can be up-and-running as quickly as possible. > > I thought of creating an archetype from my project every time I release the > archetype, but that seems really unefficient as I release new versions very > often, and also the archetype is quite complicated. > > I also thought to create the archetype once, and keep developing it in > Eclipse, but that's not possible because for instance the package names > look like this: > > package ${packageName}; > > and of-course Eclipse complains. > > So my questions is - if you have a complicated archetype that you keep > developing over time, how do you develop it? Is there an Eclipse/IntelliJ > plugin for archetype developing? > > -- > Regards, Petar! > Karlovo, Bulgaria. > --- > Public PGP Key at: > https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 > Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
