I'm using maven-assembly-plugin and jar-with-dependencies descriptor to
generate an executable jar for my desktop application. But when I try to
execute this jar, I have the following exception:
Exception in thread "main" java.lang.SecurityException: no manifiest section
for signa
Dear Micheal,
according to the assembly usage documentation, see chapter "Normal
Assemblies" on
http://maven.apache.org/plugins/maven-assembly-plugin/usage.html
your pom should be modified as follows:
maven-assembly-plugin
Emmanuel Hugonnet a écrit :
Hi,
I have a multi-modules project. Some of my modules are to be
distributed in formats defined by assembly.
I would like to call assembly:assembly from my parent directory
instead of calling it from each of my submodule.
How am i to configure this ?
Thanks
Emmanuel
Hi,
I have a multi-modules project. Some of my modules are to be distributed
in formats defined by assembly.
I would like to call assembly:assembly from my parent directory instead
of calling it from each of my submodule.
How am i to configure this ?
Thanks
Emmanuel
---
John Casey wrote:
> I'm spending a little time here and there to try to debug a few of the
> bigger issues for 2.2-beta-2 right now, but it's kind of slow going. We're
> probably going to have to do at least a -beta-3 before this is over, so we
> can get -beta-2 out the door more quickly and get so
ny
announcements
> out there.
>
> Thanks in advance,
>
> J.A.F
> --
> View this message in context:
http://www.nabble.com/Status-of-assembly-plugin-tf3964301s177.html#a11251043
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
>
g/build-helper-maven-plugin/
>
> jp4 schrieb:
>> I use the assembly plugin to create an executable jar file that contains
>> all
>> of it's dependencies. The file name is
>> foo-1.0-SNAPSHOT-jar-with-dependencies.jar. I would like to be able to
>> install thi
nouncements
out there.
Thanks in advance,
J.A.F
--
View this message in context:
http://www.nabble.com/Status-of-assembly-plugin-tf3964301s177.html#a11251043
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To
seen any announcements
out there.
Thanks in advance,
J.A.F
--
View this message in context:
http://www.nabble.com/Status-of-assembly-plugin-tf3964301s177.html#a11251043
Sent from the Maven - Users mailing list archive at Nabble.com
John,
you can attach the jar file with the attach:artifact goal from
build-helper-maven-plugin [1] over at the mojo project.
-Tim
[1] http://mojo.codehaus.org/build-helper-maven-plugin/
jp4 schrieb:
I use the assembly plugin to create an executable jar file that contains all
of it&#
I use the assembly plugin to create an executable jar file that contains all
of it's dependencies. The file name is
foo-1.0-SNAPSHOT-jar-with-dependencies.jar. I would like to be able to
install this artifact locally and/or deploy to a remote repository. How can
I do this?
I have include
-plugin
2.1
assembly-bin-distributions
package
attached
This way in the package phase , i was able to filter resources first
and then execute the assembly plugin. I didnt even had to specify
filtered
;> **--nudge--**
> >>
> >> On 6/8/07, Karan Malhi <[EMAIL PROTECTED]> wrote:
> >>> I have a module named assembly. I am using the assembly plugin 2.1 .
> >>> if i run maven from the parent project, then resources are not
> >&
src/main/resources
true
maven-assembly-plugin
2.1
assembly-bin-distributions
package
attached
g/maven-v4_0_0.xsd";>
assembly
org.apache.openejb
3.0.0-SNAPSHOT
4.0.0
openejb-standalone
pom
OpenEJB :: Assembly :: Standalone
src/main/resources
true
maven-assembly-plugin
2.1
The previous version used
to work.
I guess I second the nudge. :-)
Jim
"Karan Malhi" <[EMAIL PROTECTED]> writes:
**--nudge--**
On 6/8/07, Karan Malhi <[EMAIL PROTECTED]> wrote:
I have a module named assembly. I am using the assembly plugin 2.1 .
if i run maven fr
the assembly with a shell
script ...instead of spending even more time on maven.
If you find good solution - please let me know.
cheers
--
Torsten
On 14.06.2007, at 01:25, Francois Fernandes wrote:
Hi list,
and again a problem using the maven-assembly-plugin. I've got a
multimodule
I see this, too, though I don't know why. The previous version used
to work.
I guess I second the nudge. :-)
Jim
"Karan Malhi" <[EMAIL PROTECTED]> writes:
> **--nudge--**
>
> On 6/8/07, Karan Malhi <[EMAIL PROTECTED]> wrote:
> > I have a module name
On 6/13/07, Kannan Ekanath <[EMAIL PROTECTED]> wrote:
Thanks, I seem to get it. While doing a mvn assembly:assembly it is showing
me a "myapp.zip" however, when I do a
"mvn install" i assumed this file will be stored in the .m2\repo it is still
showing as package-0.3-SNAPSHOT.zip and not myapp.
Hi,
Thanks, I seem to get it. While doing a mvn assembly:assembly it is showing
me a "myapp.zip" however, when I do a
"mvn install" i assumed this file will be stored in the .m2\repo it is still
showing as package-0.3-SNAPSHOT.zip and not myapp.zip(myapp.zip gets copied
into the m2\repo as packag
On 6/13/07, Kannan Ekanath <[EMAIL PROTECTED]> wrote:
"mvn -Dproject.build.finalName=my-installer-0.3-SNAPSHOT clean
assembly:assembly" but it still creates the zip file with the name "
package-0.3-SNAPSHOT". Can someone tell me if there is something i am
missing?
Try setting in pom.xml, not
Maven version: 2.0.4
Maven assembly plugin version: 2.2 (current version)
I assume that maven plugin related questions are supposed to be asked in the
main maven mailling list. Kindly let me know if that isnot the case.
I have got an assembly plugin to work from
http://maven.apache.org/plugins
g these through! :)
Enjoy,
Mike
On 6/12/07, Mike Cumings <[EMAIL PROTECTED]> wrote:
Hello,
I'm in the process of trying to convert a few projects from ant build
scripts to Maven2. In the process, I've run into quite a few issues
with the assembly plugin. I started by running into:
Hi list,
and again a problem using the maven-assembly-plugin. I've got a
multimodule build with a custom assembly descriptor I would like to
execute the assembly plugin when the install phase is beeing executed.
Unfortunately this doesn't work as expected. The assembly is beeing
Hello,
I'm in the process of trying to convert a few projects from ant build
scripts to Maven2. In the process, I've run into quite a few issues
with the assembly plugin. I started by running into:
http://jira.codehaus.org/browse/MASSEMBLY-213 and/or
http://jira.codehaus.org/browse
x for
the behavior you expected in a new version. I've sometimes resorted to
creating a separate assembly pom that specifies just those module
dependencies I need to get the same effect.
Kalle
On 6/8/07, Kevin Stembridge <[EMAIL PROTECTED]> wrote:
Hi all,
I'm having a problem wit
**--nudge--**
On 6/8/07, Karan Malhi <[EMAIL PROTECTED]> wrote:
I have a module named assembly. I am using the assembly plugin 2.1 .
if i run maven from the parent project, then resources are not
filtered. if i run maven from the assembly module itself, resources
are filtered properl
Hi all,
I'm having a problem with the assembly plugin. It isn't including
dependencies for a binary within a module set. I have the following
configuration:
my.company:my-artifact
true
true
lib
false
I have a module named assembly. I am using the assembly plugin 2.1 .
if i run maven from the parent project, then resources are not
filtered. if i run maven from the assembly module itself, resources
are filtered properly.
Any ideas why this would be happening?
--
Karan Malhi
I have a problem with the maven assembly plugin.
When I issue a mvn install I get this error:
[INFO] Building jar:
/home/clem/projects/aware/aware-designer/target/aware-designer-1.0-SNAPSHOT.jar
[INFO]
[ERROR] BUILD ERROR
On 04/06/07, John Casey <[EMAIL PROTECTED]> wrote:
Hi,
You actually can bind the assembly plugin to two different phases of
the lifecycle, or even twice to the same phase. The key is to use the
block, rather than re-declare the plugin
again. Below, you have two executions declared...yo
Hi,
You actually can bind the assembly plugin to two different phases of
the lifecycle, or even twice to the same phase. The key is to use the
block, rather than re-declare the plugin
again. Below, you have two executions declared...you just need to put
them in the same plugin section
single script.
3) Create a zip file ready for deployment.
I'm trying to work out the best way of structuring the module
responsible for doing this.
Can I do it all in a single module, by binding different plugins to
the appropriately sequenced phase?
e.g.
1) Use maven-assembly-plugin bound
.
I'm trying to work out the best way of structuring the module
responsible for doing this.
Can I do it all in a single module, by binding different plugins to
the appropriately sequenced phase?
e.g.
1) Use maven-assembly-plugin bound to compile to create a temporary
working directory of all o
On 01/06/07, Dan Tran <[EMAIL PROTECTED]> wrote:
assembly plugin uses plexus-archiver which currently does not support
unpacking .rar extension.
File a enhancement request against both plexux-archiver and assembly
plugin.
http://jira.codehaus.org/browse/PLXCOMP-67
and
assembly plugin uses plexus-archiver which currently does not support
unpacking .rar extension.
File a enhancement request against both plexux-archiver and assembly plugin.
-D
On 6/1/07, James Abley <[EMAIL PROTECTED]> wrote:
I have this in my assembly configu
es?
I ask about the configuration route, since the documentation seems to
imply that it can be configured to generate different outputs, so I
wondered whether the UnArchiver can be similarly configured.
http://maven.apache.org/plugins/maven-assembly-plugin/index.html
"and any other format that th
can try to replicate/explore the problem here? The
assembly plugin is such a complex beast (both in configuration and
implementation) that it's hard to know exactly what's going on through these
sorts of discussions.
Thanks,
-john
On 5/23/07, Rodrigo Madera <[EMAIL PROTECTED]> w
Actually the package phase is indeed executed first, but not bound to
the package phase.
I can rephrase the whole problem as follows:
"The Assembly plugin won't find and artifact that was d on
the assembly because somehow the logic it uses to find the generated
JAR is not matc
lt;[EMAIL PROTECTED]> wrote:
Hi,
Could you provide more info?
Can you post more snippets from the assembly xml file and from your pom?
Thanks,
Deng
Rodrigo Madera wrote:
> Hello all,
>
> I have been struggling with the maven-assembly-plugin because of a
> problem that seems to have
Hi,
Could you provide more info?
Can you post more snippets from the assembly xml file and from your pom?
Thanks,
Deng
Rodrigo Madera wrote:
Hello all,
I have been struggling with the maven-assembly-plugin because of a
problem that seems to have been around for some time (or so I
understood
Hello all,
I have been struggling with the maven-assembly-plugin because of a
problem that seems to have been around for some time (or so I
understood).
My project structure is:
- peanuts
- charlie
- snoopy
- linus
- linus-core
- linus-blanket
I upgraded my pom to use 2.2 of the assembly plugin to fix an unrelated
issue, and now I can't seem to get filtering to work. Filtering worked
in 2.1 with the identical descriptor, and it didn't look like its format
changed in any relevant way (according to the docs).
Anyone know anyt
ion, which should result in the
> target/debug.dir folder being created. Unfortunately, IIRC we
> cannot affect
> the ".dir" extension, since the assembly plugin always appends the
> format
> (read: extension) to the created assembly.
>
You should be able to remove
extension, since the assembly plugin always appends the
format
(read: extension) to the created assembly.
You should be able to remove the '.dir' extension by using
false
as part of you configuration.
Matt
Sorry it took me so long to respond, the email got buried... :(
If you add something like the following to your assembly plugin config in
your POM, you should be able to use target/debug.dir:
maven-assembly-plugin
src/assembly/debug.xml
debug
With maven-assembly-plugin I can't filter files using a filter.properties
file
(note that it works with pom built-in properties e.g. ${project.groupId} or
toto)
I've created a small project using mvn archetype:create and inserted the
assembly configuration (see below)
Everything
A lot of projects where I work use the following idiom:
* jar-plugin is configured with addClasspath=true
* assembly-plugin is used to collect together all the needed jars with
a dependencySet
* shell script then invokes "java -jar" on the main jar, to run the
progra
nv/*.props
vault/*.props
Thanks!
Philip
> -Original Message-
> From: John Casey [mailto:[EMAIL PROTECTED]
> Sent: 26 April 2007 15:00
> To: Maven Users List
> Subject: Re: maven-assembly-plugin and target di
On 4/26/07, John Casey <[EMAIL PROTECTED]> wrote:
In your POM, you should configure the assembly plugin with the following:
debug
Although I will say that this will only generate a 'target/debug.dir'
directory, not a target/debug one...that's because the assembly format
ith the help of these
references:
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html
http://maven.apache.org/plugins/maven-assembly-plugin/component.html
(BTW, it looks like you've tried to put POM configuration of the assembly
plugin into your assembly descriptor, with the
In your POM, you should configure the assembly plugin with the following:
debug
Although I will say that this will only generate a 'target/debug.dir'
directory, not a target/debug one...that's because the assembly format is
always appended to the directory/file name.
...oh
Hi,
I'm trying to use the assembly plugin to create a directory in my
target Dir called debug. In this I'm going to put everything i need in
order to run the project in debug mode via my ide.
Currently I have this assembly descriptor
debug
dir
README*
I want to create a simple tar file which has two directories, each with
a couple of files.
When the tar file is extracted, the directories needs to be extracted to
the current working directory - not to a subdirectory in the
project-version directory.
I do not have the luxury of being ablt to ext
Hi Antonio,
Thanks, I'll give it a try !
As a workaround I've currently just hardcoded the entire path to the target,
but that is not a good solution.
Thanks again!
Regards
Arne
> > Hi Antonio
> > I tried adding 2.2-SNAPSHOT to the
> module plugin,
> > but it didn't find it.
> > How should
2007/4/25, Arne Styve <[EMAIL PROTECTED]>:
Hi Antonio
I tried adding 2.2-SNAPSHOT to the module plugin, but it
didn't find it.
How should I og about getting the 2.2 version ?
You have to add the snapshot repository to your pom, or to your settings.xml:
/* snip */
apache.
nvoke from the project directory and thus the rel paths
are correct.
put the ${basedir} variable in the place where you define the path.
Milos
On 4/25/07, Arne Styve <[EMAIL PROTECTED]> wrote:
Hi Antonio
> >
> > I'm trying to use the maven-assembly-plugin from wit
Hi Antonio
> >
> > I'm trying to use the maven-assembly-plugin from within
> Netbeans 5.5
> > (with Mavenide installed), but when executing the goal
> > assembly:assembly, I get the following message when using the
> > predefined descriptor
> > jar-
On Tue, April 24, 2007 4:09 pm, Jörg Schaible wrote:
> use goal "single" instead of "attached".
This also seems to make no difference.
One thing I have noticed is that a small part of the assembly is created,
with the contents below.
It looks like as soon as it's encountered the dependency with
mvn install is run from the assembly artifact, the
> assembly is built
> correctly.
>
> If however mvn install is run from the root pom (ie a reactor build),
> the assembly plugin goes through the motions, but the assembly
> created is empty.
>
> Does the "attached" go
scriptor to add the basedir in front of the path
to the assembly, but it made no difference:
${basedir}/assembly.xml
> As a test, rename the assembly.xml file to .blah and run from child.
> If the assembly plugin "looks" the same as when execut
2007/4/24, Styve Arne <[EMAIL PROTECTED]>:
Hi,
I'm trying to use the maven-assembly-plugin from within Netbeans 5.5
(with Mavenide installed), but when executing the goal
assembly:assembly,
I get the following message when using the predefined descriptor
jar-with-dependencies:
Emb
Hi,
I'm trying to use the maven-assembly-plugin from within Netbeans 5.5
(with Mavenide installed), but when executing the goal
assembly:assembly,
I get the following message when using the predefined descriptor
jar-with-dependencies:
Embedded error: C:\Programfiler\netbeans-5.5\target\cl
Are you sure Assembly is finding the assembly.xml you've specified
during the reactor build? I know paths specified in child pom plugins
sometimes don't work as expected during reactor builds, etc.
As a test, rename the assembly.xml file to .blah and run from child.
If the assembly plu
Hi all,
I have an assembly linked into the mvn build lifecycle like below using
the "attached" goal.
When mvn install is run from the assembly artifact, the assembly is built
correctly.
If however mvn install is run from the root pom (ie a reactor build), the
assembly plugin goes t
istently on certain machines and not
in others. I am able to build, but one of my co-workers cannot, same branch.
So much about reproducible builds.
Any clues on what can be going wrong, will be appreciated.
--
View this message in context:
http://www.nabble.com/NullPointer-excecption-on-assemb
looks like a bug in the line-ending filtration...that's a part I pretty much
carried straight over from 2.1 (IIRC), so it may have some bugs I didn't
see. Can you file it in JIRA?
http://jira.codehaus.org/browse/MASSEMBLY
Thanks,
John
On 4/13/07, Orford, Ian <[EMAIL PROTECTED]> wrote:
Hi,
I
doing something like ${pom.artifactId} -- is the same
facility available when filtering files in the assembly plugin? It
doesn't seem to work that way.
What I want to do is put a filter in a batch file I'm including in the
assembly so that the name of my jar will be included.
T
TED]> wrote:
I may be wrong, but try removing the
with unpack set to
false. I think it will pick up the dependencies then.
Good luck,
Brad
On Tue, 2007-04-17 at 15:35 +0200, Graham Leggett wrote:
> Hi all,
>
> While trying to build an assembly using 2.2-beta-1 of the assembly
plugin,
>
Hello,
I've a problem using assembly plugin v. 2.2-SNAPSHOT and don't know, if it's a
bug or my fault.
So, i have a multi-module project.
/parent
|
|-war
|-ear
And in each module I package alternative configuration files according to
profile (i.e. each customer
Hi,
From what I've read, you can include stuff from your POM when filtering
resources by doing something like ${pom.artifactId} -- is the same
facility available when filtering files in the assembly plugin? It
doesn't seem to work that way.
What I want to do is put a filter in a
I may be wrong, but try removing the
with unpack set to
false. I think it will pick up the dependencies then.
Good luck,
Brad
On Tue, 2007-04-17 at 15:35 +0200, Graham Leggett wrote:
> Hi all,
>
> While trying to build an assembly using 2.2-beta-1 of the assembly plugin,
> I en
Hi all,
While trying to build an assembly using 2.2-beta-1 of the assembly plugin,
I end up with en empty zip file.
The key difference is the false - if this is set to true,
the assembly works, if however it is set to false, the assembly plugin
ignores the dependencies.
In order to be useful to
Hi,
I have a project that creates a tar.gz deliverable that includes unix
shell scripts. In the assembly descriptor, I have:
target/bin
bin
*.sh
0755
lf
As you can see, I'm specifying the lineEnding.
When I deploy this from the project lev
]
Sent: Thursday, April 12, 2007 4:35 PM
To: Maven Users List
Subject: Re: Problem with maven-assembly-plugin 2.2-beta-1
This is reported in MASSEMBLY-179 (
http://jira.codehaus.org/browse/MASSEMBLY-179), and the workaround is to
add the following to your dependencySet:
That should fix your problem
This is reported in MASSEMBLY-179 (
http://jira.codehaus.org/browse/MASSEMBLY-179), and the workaround is to add
the following to your dependencySet:
That should fix your problem.
-john
On 4/12/07, Lacoste, Dana <[EMAIL PROTECTED]> wrote:
With assembly plugin 2.2-beta-1, unpacked pa
With assembly plugin 2.2-beta-1, unpacked packages aren't
being handled consistently with how 2.1 worked.
Specifically, if I have an assembly which has a dependency
which is unpacked, it is unpacked into "dependency-name/",
as if the dependency had includeBaseDirectory set to tr
Traditionally, Maven regards the repository as a database for artifacts.
This means that anything in the repository is meant to be reachable by
Maven. Having said that, most repositories live on some sort of webserver
somewhere, which means the Maven repository is usually just a directory
structur
I'm not insisting on it either. The artifacts were deployed automatically
when we deploy the parent project. As far as I know we don't need them in
the repository though. I'll have to take a closer look.
Thanks for your help.
On 4/11/07, Alan D. Salewski <[EMAIL PROTECTED]> wrote:
On Wed, Apr
On Wed, Apr 11, 2007 at 09:45:17PM +0200, Heinrich Nirschl spake thus:
*snip*
> On 4/11/07, Alan D. Salewski <[EMAIL PROTECTED]> wrote:
> >Maybe we need an attribute for 'finalName' that indicates "yes I know
> >this name will not be accessible by maven once installed or deployed";
> >when set mave
On 4/11/07, Alan D. Salewski <[EMAIL PROTECTED]> wrote:
On Wed, Apr 11, 2007 at 01:27:42PM -0500, Michael Dick spake thus:
*snip*
> It seems that the finalName *could* be added in an xml file in the
> repository. Whether it *should* be added is another issue.
I did not think too much about that
On Wed, Apr 11, 2007 at 01:27:42PM -0500, Michael Dick spake thus:
*snip*
> It seems that the finalName *could* be added in an xml file in the
> repository. Whether it *should* be added is another issue.
>
> FTR I'm just curious whether this is a possibility, or if anyone else thinks
> it would be
Thank you for the explanation,
Wouldn't it be possible to store the finalName in the
maven-metadata.xmlfile or another xml file in the repository? We
already have a unique path in
the repository ${groupId}/${artifactId}/${version}. I'm not interested in
changing the path, just the name of the fin
On 4/11/07, Michael Dick <[EMAIL PROTECTED]> wrote:
Hi,
I've noticed that the finalName configuration option for an assembly is
ignored when you install or deploy your project. Is this intended behavior?
I have a project named openjpa-project which contains the a source and
binary assembly whic
Hi,
I've noticed that the finalName configuration option for an assembly is
ignored when you install or deploy your project. Is this intended behavior?
I have a project named openjpa-project which contains the a source and
binary assembly which packages various OpenJPA sub-projects. We'd like to
Hi all,
I use maven-assembly-plugin to assemble my project. My project contains some
modules.
A module "myModule" contains a dependency with scope=provided
("myDependencyProvided"). This module as a
specific packaging (not a jar, war, ...): "myPackaging"
I w
--
View this message in context:
http://www.nabble.com/Maven-assembly-plugin-to-build-simple-jar-
tf3500378s177.html#a9775773
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail:
f files based on
>> a
>> pattern-set.Currently i am using ant jar task for the same and calling
>> that
>> with antrun-plugin.
>>
>> Thanks in advance
>> Raju
>> --
>> View this message in context:
>> http://www
hieve just jarring of files based on a
pattern-set.Currently i am using ant jar task for the same and calling that
with antrun-plugin.
Thanks in advance
Raju
--
View this message in context:
http://www.nabble.com/Maven-assembly-plugin-to-build-simple-jar-tf3500378s177.html#a9775773
Sent from the Maven
-plugin.
Thanks in advance
Raju
--
View this message in context:
http://www.nabble.com/Maven-assembly-plugin-to-build-simple-jar-tf3500378s177.html#a9775773
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To
that possible? It
>> doesn't
>> >> seem like it.
>> >
>> >
>> >
>> > Sorry, I'm not sure I follow; what do you mean by "installed with"?
>> >
>> > -j
>> >
>>
>> I mean the asse
ll wondering how I can attach the zip
>> to
>> >> a
>> >> WAR when it's installed with another WAR. Is that possible? It
>> doesn't
>> >> seem like it.
>> >
>> >
>> >
>> > Sorry, I'm not sure I follo
ther WAR. Is that possible? It
doesn't
>> seem like it.
>
>
>
> Sorry, I'm not sure I follow; what do you mean by "installed with"?
>
> -j
>
I mean the assembly is created and installed in my local repo (using the
followin
you mean by "installed with"?
>
> -j
>
I mean the assembly is created and installed in my local repo (using the
following config):
maven-assembly-plugin
2.1
src/assemb
gt; -john
>
> On 3/28/07, mraible <[EMAIL PROTECTED]> wrote:
>>
>>
>> I've managed to get my WARs and ZIPs into the same release ZIP using
the
>> following assembly descriptor. However, I'd like to combine the two
zips
>> into a single
the same release ZIP using the
>> following assembly descriptor. However, I'd like to combine the two zips
>> into a single zip. Is this possible with the maven-assembly-plugin or do
>> I
>> need to resort to Ant for that?
>>
>>
>>
make sense?
-john
On 3/28/07, mraible <[EMAIL PROTECTED]> wrote:
I've managed to get my WARs and ZIPs into the same release ZIP using the
following assembly descriptor. However, I'd like to combine the two zips
into a single zip. Is this possible with the maven-assembly-plugin o
I've managed to get my WARs and ZIPs into the same release ZIP using the
following assembly descriptor. However, I'd like to combine the two zips
into a single zip. Is this possible with the maven-assembly-plugin or do I
need to resort to Ant for that?
bin
TECTED]
Envoyé : mercredi 28 mars 2007 07:55
À : users@maven.apache.org
Objet : Using the assembly plugin to package up WARs and ZIPs
I'm trying to use the assembly plugin to package up WARs from a bunch of
sub-projects. My goal is to get a target/release.zip after running "mvn
pa
I'm trying to use the assembly plugin to package up WARs from a bunch of
sub-projects. My goal is to get a target/release.zip after running "mvn
package" from the top-level directory.
I have this working when I run "mvn package assembly:assembly", but I'd like
to
901 - 1000 of 1333 matches
Mail list logo
