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 most often NOT the way to go IMO.
/Anders On Wed, Dec 2, 2009 at 22:40, Jesse Farinacci <[email protected]> wrote: > Hi KJ, > > On Wed, Dec 2, 2009 at 3:19 PM, K J <[email protected]> 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 go the real Maven way, I think that I'd probably put the shared > model data (perhaps some sort of XML?) into a Maven module. Then I'd > have more Maven modules for Java and ActionScript, each, that would > depend on the model data module. They would use it as a dependency and > then generate their source codes accordingly. > > -jesse > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
