I actually don't want to install these jars/wars/hars into my repository
because they aren't really separate components. No other project of ours
uses them. Instead, I'm trying to build a multi-part project which consists
of two built wars, a built har, three built jars, plus all of the dependent
2009/7/10 David Weintraub qazw...@gmail.com
I actually don't want to install these jars/wars/hars into my repository
because they aren't really separate components. No other project of ours
uses them. Instead, I'm trying to build a multi-part project which consists
of two built wars, a built
Still a bit confused. The Assembly plugin's documentation says it runs a
lifecyle package before creating the assembly. The only thing I can think
of is that assembly:assembly is running a separate package against each
and every pom.xml separately.
I did a mvn clean verify and everything runs.
Move your assembly into a project separate from the root and then make
it dependent on the ear project.
Don't reference an artifact across project boundaries using relative
directories in an assembly descriptor. Declare dependencies and use
the local repository as the medium to store and
We have a project we're converting over to Maven. The structure is a bit
convoluted:
Project Root
apps.war: Builds apps.war
aimwebservices: Builds aimwebservices.war
ear: Builds adinventory.ear. Contains all other modules
projects
adplanning: Builds adplanning.jar
base
David,
It looks like com.solbright.adinventory.projects.base:jar:jar:2.1.2-SNAPSHOT
can't be found in the local repository. Instead of running
assembly:assembly by itself, try: mvn install assembly:assembly
Better yet, why not just bind the assembly goal to the package phase
of the project
