Re: What is the 'Maven way' to handle multi-artifact code generation from a single model source?

[Kalle Korhonen <ka...@gmail.com>]

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 them (and specify the classifiers) see
http://mojo.codehaus.org/build-helper-maven-plugin/usage.html. The
actionscript code should be packaged up to produce a single artifact
(zip it up if a specific packaging format like swf won't do).

Kalle


On Wed, Dec 2, 2009 at 12:19 PM, K J <go...@gmail.com> 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 having trouble figuring out how
> to best setup and manage these types of projects, so that a change to
> the source project can easily result in the build of all the various
> generated outputs.  Thanks in advance for the help.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org