Thanks for following up and letting us know John. Good info.
John Casey wrote:
BTW, this problem is fixed in the latest snapshots of the assembly
plugin, where there is a new flag in the assembly descriptor's
dependencySet: true|false.
For compatibility with the 2.1 release of maven-assembly-
Zarick...
Just wanted to let you know that your solution just helped me out. I
would second it that it seems odd to me that extra configuration is
required in order to get the jar your project is building into the
assembly. Seems to me this should be the default behavior, and then the
user
Nevermind... I did it with a '-U' arg tacked on, and it worked...
Thanks again for the help.
Bryan Noll wrote:
Thanks for the feedback. I'm trying to use the project-info-reports
plugin, and am getting the following:
org.apache.maven.lifecycle.LifecycleExecutionExcept
could be found
...which seems odd to me, because I can see it right here:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/
Any ideas?
Alan D. Salewski wrote:
On Thu, Feb 22, 2007 at 11:00:42AM -0700, Bryan Noll spake thus:
Can anyone tell me the quick
Can anyone tell me the quick-n-dirty way to figure out which dependency
is responsible for a jar that is being transitively downloaded/included
in the project? For instance, I see the servlet-api jar showing up in
my assembly, but don't need it. I've already excluded it once from the
spring d
