Thanks for the input everyone.
On Thu, Dec 3, 2009 at 10:41 AM, Kalle Korhonen
wrote:
> I wouldn't worry *too much* about the true and righteous way. While I
> agree that the more modular approach is more proper and allows for
> more flexibility, as with anything else, you need to strike a balan
I wouldn't worry *too much* about the true and righteous way. While I
agree that the more modular approach is more proper and allows for
more flexibility, as with anything else, you need to strike a balance
with building for future and practicality. With multiple modules,
there comes additional com
I'd like to stress that Jesse explains the true Maven way. This is how this
should be done if you want to enjoy simple and correct dependency management
through Maven.
Using classifiers will make your two (for instance) artifacts have the same
dependencies. As I've stated before, classifiers are mo
Hi KJ,
On Wed, Dec 2, 2009 at 3:19 PM, K J wrote:
> Does anyone have any examples or tips about how to handle the
> generation of multiple artifacts based on a shared model? For example,
> I have a project which needs to produce both Java and ActionScript
> code based on a shared UML model. I'm h
Since the build artifacts are output of the same source, they should
part of the same module. Use classifiers to specify the different
artifacts. If you are using custom scripts to produce the output (i.e.
not plugins that attach additional artifacts automatically), use
buildhelper plugin to attach
Does anyone have any examples or tips about how to handle the
generation of multiple artifacts based on a shared model? For example,
I have a project which needs to produce both Java and ActionScript
code based on a shared UML model. I'm having trouble figuring out how
to best setup and manage thes
