Hi,
Let me give more information,
I use an aggregator project for war1 project:
../jar1
../jar2
../war-inc
../war1
Another aggregator project for war2 project:
../jar1
../war-inc
../war1
Notice they both depend on jar1.
The Maven team is pleased to announce the release of the Apache Maven
One Plugin (RETIRED), version 1.3
As you can see in the release notes below, this plugin has now been
retired. There will be no more releases of this plugin.
Eases the migration from Maven 1.x to Maven 2.x by providing a POM
co
Hi all,
Is Maven 2.2.1 support localRepository to be defined as a relative path?
say for eg, repository, so that for each
project I build, there will be a separate repository being created.. ?
Also, is -Dmaven.repo.local="path" option supported?
I was able to get it working in Maven 3, but coul
> This has nothing to do with maven, but since I started this thread thinking
> it was a maven problem I though that I finnish it with the end result.
Thanks Tommy. Perhaps you will also come back and tell us when Oracle
has fixed and released it.
Wayne
--
you configured *assembly:single* to be executed during the package phase,
so calling *mvn package* also executes *assembly:single*. When you remove
the *executions* part from your configuration, then you must call *mvn
package single:assembly*.
Cheers,
Rotsch
2013/7/31 Tim Wu T
> Hi,
>
> Reall
Hi,
Really thanks for your suggestion.
More clear now :)
Just one small question, not so clear about this:
(which is needless with your configuration if you don't remove the executions
part)
Thanks in advance.
Br,
Tim
-Original Message-
From: Roger Brechbühl [mailto:rotscher...@gmail.
when calling assembly:single only, the package phase and all its attached
plugins are not executed. Especially, the maven-jar-plugin is not executed,
so no jar file is generated and attached. Hence the error message.
mvn package single:assembly (which is needless with your configuration if
you don
