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: useProjectArtifacttrue|false/useProjectArtifact.
For compatibility
On 8/16/07, John Casey [EMAIL PROTECTED] 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: useProjectArtifacttrue|false/useProjectArtifact.
For compatibility with the 2.1 release of
On 8/16/07, Bryan Noll [EMAIL PROTECTED] wrote:
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
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
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: useProjectArtifacttrue|false/useProjectArtifact.
For compatibility with the 2.1 release of maven-assembly-plugin, this
flag is set to true by
Alright, I got an answer myself. The solution is the add one more 'fileSet'
to include the artifact produced the jar plugin.
fileSet
includes
include${artifactId}-*.jar/include
/includes
directory${basedir}/target/directory
outputDirectorylib/outputDirectory
Dear users and developers,
I have a single module project, is it possible to create an assembly
such that, it include the normal project artifact, extra files (scripts/sql)
and dependency in the assembly output?
I can use an descriptor to include the scripts and dependencies
included in the
