Thanks ! I knew that the lines could be broken, but I did not know that
they could be broken in the middle of a jar name! So I thought this was
one cause of my problem. In fact, it is not. The problem is with the
assembly descriptors. But I think I will eventually find a solution know
I "know"
Hi,
I am trying to use maven2 assembly plug-in. It seems to be completely
broken:
- First, a small problem: the standard assembly descriptor is not usable
because of it very strange name. If the app is called "myapp", the
resulting jar will be called myapp-jar-with-dependencies.jar. It seems
This is explained very clearly in the documentation:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
(look at section "Depencdency scope")
Here is an example:
I use Wicket, which is dependent on log4j through teh following
declaration in wicket-parent pom
I switched to Maven 2 because I was tired of Ant.
When one looks at a good Java project, one can find its way easyly
because there are well known architecturing and coding standards. There
are no such things with Ant. I remember trying to find my way in Ant
scripts calling other Ant scripts, a
