Non-artifact dependencies

[James CE Johnson <jc...@tragus.org>]

Forgive me if this has come up before...

I've got a project with many sub-projects.  Most of them create a jar file
that others can depend upon. However, I have two "special" sub-projects:
'schema' and 'domainData'.

My 'schema' subproject doesn't depend on anything at all and has only two
useful goals: 'blow-away-the-database' and 'create-the-database'.

My 'domainData' subproject depends on a couple of normal subprojects that
create jar files (with persistence-interface objects) but also depends on
'schema'.

Thus, a 'maven build-the-world' at the top of my project tree will use the
multiproject plugin to build all of the jar-creating projects in the
correct (per <dependencies .../>) order. It also, however, needs to fire
off the 'schema' and 'domainData' projects somewhere along the way.

Must I manually invoke 'schema' via the reactor before multiproject
invokes all of the others or is there some way to make 'domainData' depend
on it explicitly?

Thanks,
J


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