Hi Wendy,
Thank you for the helpful reply! I've never used Maven on this scale before
and it's a steep learning curve! I've been trying to convert a massive multi
module project from ant to maven these past two weeks, it all compiles and
runs unit tests now, but i've had no end of problems getting
war-modules with appropriate
dependencies.
Kind regards
Karl Heinz Marbaise
-
Kind regards
Karl Heinz Marbaise
http://www.soebes.de
http://www.skmwiki.de
http://supose.org/wiki/supose
--
View this message in context:
http://maven.40175.n5.nabble.com/The-maven-assembly-plugin-and-a-large-
On Wed, Apr 6, 2011 at 10:44 AM, Adam Gibbons wrote:
> Also I refer you to:
> http://maven.apache.org/plugins/maven-assembly-plugin/which states
> that it can create distributions in the war format.
It *can* but you generally only need it if the war plugin is not doing
what you ne
On Wed, Apr 6, 2011 at 10:37 AM, Adam Gibbons wrote:
> At the moment I don't think the jar modules get compiled/deployed
> when i build the war.
What makes you say that? What exactly are you doing and what happens
vs. what you expected to happen?
Guessing, I'd say you are in one of the war sub
Also I refer you to:
http://maven.apache.org/plugins/maven-assembly-plugin/which states
that it can create distributions in the war format.
On 6 April 2011 15:27, Karl Heinz Marbaise wrote:
> Hi Adam,
>
> > What I would like is a top level pom which upon doing mvn package it will
&g
number of modules and some of the
> multiple
> > modules have a dependency on in-house compiled jars. Ideally when
> building
> > the WARs I'd like all of the child modules and jars built/deployed.
>
> That sound's you're trying a wrong thing, cause a war shoul
Ideally when building
> the WARs I'd like all of the child modules and jars built/deployed.
That sound's you're trying a wrong thing, cause a war should be produced by the
Maven War Plugin and not via maven-assembly-plugin...
I would suggest to use a structure like this:
root
Hello all,
I'm working on a large aggregate project that I'm trying to build 4 WAR
files for.
What I would like is a top level pom which upon doing mvn package it will
produce my 4 WAR files by compiling all child modules AND jars.
Each WAR file is comprised of a number of modules and some of the
that gives a NullPointerException during
> the assembly:
>
> maven builder waiting
> mavenExecutionResult exceptions not empty
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.2:single (make
> zipfil
execute
goal org.apache.maven.plugins:maven-assembly-plugin:2.2:single (make
zipfile) on project plugin-sdk-assembly: Execution make zipfile of goal
org.apache.maven.plugins:maven-assembly-plugin:2.2:single failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
Found the answer at:
http://stackoverflow.com/questions/3998596/renaming-resources-in-maven
"You can avoid the over head of Ant by using the Maven Assembly plugin
<http://maven.apache.org/plugins/maven-assembly-plugin/> and the file
assembly descriptor
<http://maven.apache.org
My maven project manages files for an open standard and uses the
maven-assembly-plugin to produce a zip for all artifacts for a specific
version of the standard.
The project files are stored in version control so naturally the spec
document files that are in the assembly zip do not have the
Hi
I'm assuming that org.ferris:ferris-assemblies:jar:0.0.3 is a dependency
that you have configured for the assembly-plugin. If that is the case
then with Maven 3 that dependency must be available in a repository that
is defined as a . If it is only available in a normal
Maven 3 will n
Michael Remijan wrote:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
(ferris-bin-assembly) on project ferris-bible-common: Execution
ferris-bin-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single failed: Plugin
I've switched to Maven 3.0.2in an attempt to get a working release plugin but
now the assembly plugin is not working.
I can 'clean install' my multi-module project fine with 2.2.1. When switching
to 3.0.2 Maven has a problem with the assembly with the following error printed
The Maven team is pleased to announce the release of the Maven Assembly
Plugin, version 2.2.1
Do you want to create a binary distribution from a Maven project that
includes supporting scripts, configuration files, and all runtime
dependencies? You need to use the Assembly Plugin to create a
ok.
Someone knows a good example of the use of that assembly plugin with a multiple
modules project ?
--- On Sat, 2/26/11, Anders Hammar wrote:
From: Anders Hammar
Subject: Re: Assembly plugin to produce an EAR archive
To: "Maven Users List"
Date: Saturday, February 26, 201
Normally, you ear plugin should fit your needs. If it turns out not to do
all you want it to do, then possibly look at the assembly plugin.
/Anders
On Sat, Feb 26, 2011 at 16:11, Celinio wrote:
> Hi,
> I have this multiple module project where one module is the parent and 2
> other mo
Hi,
I have this multiple module project where one module is the parent and 2 other
modules are children.
One child module produces a JAR and the other child module produces a WAR
archive (webapp).
I would like to use the assembly plugin to join these 2 archives inside an EAR
archive.
Is there
On 02/15/2011 12:58 PM, Steve Cohen wrote:
I can set the permissions of s and s and
s in the maven-assembly-plugin, but it seems from the
online documentation that I can't do so on the . What is more,
when assembling a format, the perms default to 777. At least
that's what I get wh
Hi,
Thanks for the quick response.
I did that and now I'm getting the following error (see bellow).
My descriptor is very simple:
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:s
:
> Hi all,
>
> I'm having a problem with maven assembly plugin. It happens that I have a
> child pom with relative paths and when I hit assembly:assembly the
> environment becomes corrupted (that doesn't happen if I hit mvn install,
> package whatever in both project'
Hi all,
I'm having a problem with maven assembly plugin. It happens that I have a
child pom with relative paths and when I hit assembly:assembly the
environment becomes corrupted (that doesn't happen if I hit mvn install,
package whatever in both project's pom directory or in
I can set the permissions of s and s and
s in the maven-assembly-plugin, but it seems from the
online documentation that I can't do so on the . What is more,
when assembling a format, the perms default to 777. At least
that's what I get when I unzip the file (having erased t
Hi all,
I will zip a folder with the name '.metadata' but assembly plugin is ignoring
me ;-)
This is ignored:
.metadata/version.ini
Does anybody have an idea, why assembly is ignoring '.metadata'?
Or is it a fe
Thanks for the prompt replies :-)
I didn't precise I was not at an Application layer, but in a layer above.
I confirm that on the Application layer, Spring answers really well about
the problematic.
For example, my packaging will produce a complete archive with tomcat
bundled into it.
In the tomc
On Thu, Feb 3, 2011 at 6:48 PM, Frederic Camblor wrote:
> Nobody has any piece of advice against these options ? :(
When you tell us you can't change anything, there's not much to say.
Either move the configuration out of the war, or put it *all* in there
and use something (like Spring) that can
On 3 February 2011 15:48, Frederic Camblor wrote:
> Nobody has any piece of advice against these options ? :(
N artifacts is (as I think you've already discovered) not very scalable. :-)
So take the configuration out of the WAR. Create a single WAR that can
be (re)used by all environments. Use a
Nobody has any piece of advice against these options ? :(
On Sun, Jan 30, 2011 at 3:13 AM, Frederic Camblor wrote:
> Hi all !
>
> My context :
> - 1 pom Artefact
> - This artefact generate N zip artefacts via the maven-assembly-plugin.
> These N artefact are contextual
Hi all !
My context :
- 1 pom Artefact
- This artefact generate N zip artefacts via the maven-assembly-plugin.
These N artefact are contextualized upon a target deployment environnment.
- N = ~5 for the moment, but it can evolve depending on the number of
environnment that will grow in the future
Thanks...I went through the example and created a bin.xml that represented
> the jar-with-dependencies example.
>
> xmlns="
> http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
Thanks...I went through the example and created a bin.xml that represented
the jar-with-dependencies example.
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://mave
d/jws
${basedir}/src/main/webapp/web.xml
--
View this message in context:
http://maven.40175.n5.nabble.com/Tar-pom-xml-dependencies-Maven-Assembly-Plugin-tp3335797p3336789.html
Sent from the Maven - Users mailing list archive at Nabble.com.
Yes, the assembly plugin is they way to do this. Declare the packaging as
"pom".
There are several examples at the plugin's homepage, or google for some live
ones.
/Anders
On Tue, Jan 11, 2011 at 02:11, jaybytez wrote:
>
> Is the Maven Assembly Plugin the right way for m
Is the Maven Assembly Plugin the right way for me to define a pom.xml and be
able to tar up the jars that are labeled as a dependency?
The only way I know how to do this with my limited knowledge is to make the
pom.xml a war and allow the war to pull all the dependency jars into the
target
On 5 January 2011 08:22, xtonic wrote:
>
> I would like to produce a tar with my project artifact and all its
> dependents
> jars jarsigned. Also, I would like to deploy the tar as attachment.
>
> I used assembly plugin and write my own descriptor. However, I don’t know
>
I would like to produce a tar with my project artifact and all its dependents
jars jarsigned. Also, I would like to deploy the tar as attachment.
I used assembly plugin and write my own descriptor. However, I don’t know
how to sign all the jars before the tar is created.
I did try create the
;> [DEBUG] Installing
>> com.whatever:bpm-dist:0.0.3-SNAPSHOT/maven-metadata.xml to
>>
>> /home/abcdefg/.m2/repository/com/whatever/bpm-dist/0.0.3-SNAPSHOT/maven-metadata-local.xml
>>
>> [DEBUG] Installing com.whatever:bpm-dist/maven-metadata.xml to
>>
>> /home/abcdefg/
e ultimate zip file in target/appassembler of the
main project.
The aggregator project using the assembly plugin then pulls these as
filesets from this location.
There may be (and probably is, I would guess) a way to do this using
only the assembly plugin and not appassembler. But the documentat
On Sat, Jan 1, 2011 at 12:22 AM, Steve Cohen wrote:
> Well, all I can say is that I was doing approximately as you have described
> and it didn't really work.
>
> I was using assembly:assembly (single for some reason failed to bring in
> everything needed - perhaps the mistake was mine), I also us
ound to the package phase of the main project, aggregating all
stuff needed in the ultimate zip file in target/appassembler of the
main project.
The aggregator project using the assembly plugin then pulls these as
filesets from this location.
There may be (and probably is, I would guess) a way to d
have it set up now, and it's working as I want, appassembler
is bound to the package phase of the main project, aggregating all
stuff needed in the ultimate zip file in target/appassembler of the
main project.
The aggregator project using the assembly plugin then pulls these as
fileset
ng all stuff
needed in the ultimate zip file in target/appassembler of the main project.
The aggregator project using the assembly plugin then pulls these as
filesets from this location.
There may be (and probably is, I would guess) a way to do this using
only the assembly plugin and not ap
mble assembly:single
>
> Now it very well may be that there is a way to do the same thing with the
> assembly plugin alone. But the documentation and the examples for that
> plugin do not explain that way for me. Instead I get dragged into
> discussions of "Reactors" and
embly and move it into the project that
> builds the jar with the main() class. A single maven command does it
> all from scratch:
>
> clean install package appassembler:assemble assembly:single
>
> Now it very well may be that there is a way to do the same thing with
> the asse
a way to do the same thing with
the assembly plugin alone. But the documentation and the examples for
that plugin do not explain that way for me. Instead I get dragged into
discussions of "Reactors" and all sorts of things that I shouldn't need
to understand (and don't), ju
n wrote:
> Now that was good, but the question is why can't something like that be
> available through the assembly plugin itself?
>
> Build the main jar and its dependencies, install the non-third party jars
> into the local repository, then pull them back out into an asse
Now that was good, but the question is why can't something like that be
available through the assembly plugin itself?
Build the main jar and its dependencies, install the non-third party
jars into the local repository, then pull them back out into an assembly
staging area, together with
cies into a zip file. End of story. Can I do
it in less than a day?
Sorry to be so gun-shy but I'm still recovering from the assembly-plugin
experience.
Hi Steve
May I suggest that you have a look at the Appassembler Maven Plugin for
your batch processing application.
http://mojo.codeh
sues using the assembly plug-in to build the
resulting artifacts.
On 30/12/2010 3:16 PM, Steve Cohen wrote:
After a very frustrating couple of days trying to understand the new
features of the assembly plugin, let me try to specify what I am
TRYING to do and see if there isn't a be
off) but I can ignore that. The creation of
the repository inside the target is slick, and I assume I can use that
to suck all the jars into the assembly plugin.
Yep, here's the assembly descriptor I use:
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
xmlns:xs
ssume I can use that
> to suck all the jars into the assembly plugin.
Yep, here's the assembly descriptor I use:
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.a
I think this is going to work.
I absolutely don't need any of the shellscript generation (it would be
nice to be able to turn it off) but I can ignore that. The creation of
the repository inside the target is slick, and I assume I can use that
to suck all the jars into the assembly p
I think the problem may be in terminology, I'll try to describe it
below. It has to do with "modules"
Let me preface this by saying I have never got modulesets working and
have found that I don't need to.
Have you read
http://maven.apache.org/plugins/maven-assembly-plugin
pt and
> might have been the way to go before I developed all this by hand with
> commons-daemon and NOT AT ALL about the actual packaging.
>
> Is the idea then to assemble everything in a directory and THEN pass this as
> a fileSet to the assembly plugin?
That is exactly what I did to
hand with commons-daemon and NOT AT ALL about the actual packaging.
Is the idea then to assemble everything in a directory and THEN pass
this as a fileSet to the assembly plugin?
Or am I missing something?
On 12/30/2010 02:37 PM, Dennis Lundberg wrote:
Hi Steve
May I suggest that you have
han a day?
>
> Sorry to be so gun-shy but I'm still recovering from the assembly-plugin
> experience.
>
>
>> Hi Steve
>>
>> May I suggest that you have a look at the Appassembler Maven Plugin for
>> your batch processing application.
>>
>>
>
pendencies into a zip file. End of
story. Can I do it in less than a day?
Sorry to be so gun-shy but I'm still recovering from the assembly-plugin
experience.
Hi Steve
May I suggest that you have a look at the Appassembler Maven Plugin for
your batch processing application.
http
to understand the new
> features of the assembly plugin, let me try to specify what I am TRYING
> to do and see if there isn't a better (i.e. more mavenish) way of doing
> it. Maven is flexible as long as you don't stray too far out of the
> beaten path.
>
> I am supportin
After a very frustrating couple of days trying to understand the new
features of the assembly plugin, let me try to specify what I am TRYING
to do and see if there isn't a better (i.e. more mavenish) way of doing
it. Maven is flexible as long as you don't stray too far out of the
b
now that
helped
me a lot when debugging assembly problems.
On Wed, Dec 29, 2010 at 7:45 AM, Steve Cohen
wrote:
On 12/29/2010 09:21 AM, Steve Cohen wrote:
Aargh!
Following the pattern outlined here:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclus
u tried running with useAllReactorProjects set to false?
No, as I said in my earlier thread, I was following the model that is
described at
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
where they introduce useAllReactorProjects wh
well the build didnt fail. However it seems none of your modules were
included in the assembly. Ive done a little bit with assemblies, I was
never able to get the tags to work.
What are you trying to accomplish here? it looks like you just want the
artifacts from your 6 modules added into a zi
that helped
me a lot when debugging assembly problems.
On Wed, Dec 29, 2010 at 7:45 AM, Steve Cohen wrote:
On 12/29/2010 09:21 AM, Steve Cohen wrote:
Aargh!
Following the pattern outlined here:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusi
t; Following the pattern outlined here:
>>
>>
>> http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
>>
>>
>> I create POM's and assembly descriptors fitting that model.
>>
>> All of the su
On 12/29/2010 09:21 AM, Steve Cohen wrote:
Aargh!
Following the pattern outlined here:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
I create POM's and assembly descriptors fitting that model.
All of the submodules are
A quick update. Despite having other poi dependencies, this is the only one
which causes the StackOverFlow. It occurs when the plugin imports the xsb's
into the jar.
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-assembly-plugin-StackOverflowError-tp3321403p33
Aargh!
Following the pattern outlined here:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
I create POM's and assembly descriptors fitting that model.
All of the submodules are built and installed in a local repository.
I'm having a bit of difficulty with the multimodule project
documentation for the 2.2 plugin.
The basic idea, as expressed here:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
seems to be that you have a parent pom and a chil
## In replies all text above this line is added to the ticket ##
Request received: Tests run twice using assembly plugin (ticket #21984)
Your request (#21984) has been received, and is being reviewed by our support
staff.
To review the status of the request and add additional comments, follow
I am using the assembly plugin to build a zip file for a project. This
uses a custom made assembly descriptor.
The pom for this projects lists several modules, each of which has its
own pom and builds a jar.
For some reason I don't understand, this setup causes each submodule t
More context on how I got to this phase:
http://maven.40175.n5.nabble.com/Create-complicated-client-jar-release-target-s-td3295582.html
The 2.2 assembly plugin includes the projects artifacts by default in the
dependencySet tag. However there is a tag that *should* resolve this. I've
s
; section inside the assembly plugin configuration, so instead of having
>
>
>
>
>
> maven-assembly-plugin
>
>
>
>
>
>
Hi Gérald,
just a quick update: I arranged stuff working moving the
section inside the assembly plugin configuration, so instead of having
maven-assembly-plugin
rg/
>
>
>
> On Fri, Nov 26, 2010 at 3:18 PM, Gérald Quintana
> wrote:
>> The assembly plugin doesn't take the filter configuration from the
>> project, I has to re-inject the filters!
>>
>> Gérald
>>
>> Le 26 novembre 2010 14:03, Arnaud Héri
I got *exactly* the same issue, I suppose we should fill a new Issue on Jira!!!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Nov 26, 2010 at 3:18 PM, Gérald Quintana
wrote:
> The assembly plugin doesn't take the filter configuration from the
> projec
The assembly plugin doesn't take the filter configuration from the
project, I has to re-inject the filters!
Gérald
Le 26 novembre 2010 14:03, Arnaud Héritier a écrit :
> Couldn't it be the same problem as in resources plugin (there are using same
> libraries to do that) which s
th files which should be copied and filtered:
>
>src/main/config
>config
>true
>
>quartz.properties
>
>
>
> Files are copied but not filtered (${...} are still here)
>
>
with maven-assembly-plugin 2.2 but not with 2.2-beta-5.
It it a known bug or a problem in my configuration?
Gérald
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h
I want to insert the filename of one of my project's dependency into a
configuration file via filtering. I can do it in some sloppy fashion
or another, but I wondered if there was a way to get a plugin to set a
definition for me.
Casey is correct
maven-assembly-plugin
assembly
package
single
src/main/assembly/bin.xml
true
M, Haszlakiewicz, Eric wrote:
-Original Message-
From: Wendy Smoak [mailto:wsm...@gmail.com]
On Thu, Oct 21, 2010 at 1:40 PM, Phillip Hellewell
wrote:
I just found out the hard way that the latest version of the assembly
plugin requires an tag in the descriptor file, which is used as
the c
A simple scan of the release notes reveals this was introduced
intentionally by MASSEMBLY-464
On Mon, Oct 25, 2010 at 4:58 PM, Wendy Smoak wrote:
> On Mon, Oct 25, 2010 at 1:07 PM, Haszlakiewicz, Eric
> wrote:
>>>-Original Message-
>>>From: Wendy Smoak [mailto:wsm...@gmail.com]
>
>>>Have
On Mon, Oct 25, 2010 at 1:07 PM, Haszlakiewicz, Eric
wrote:
>>-Original Message-
>>From: Wendy Smoak [mailto:wsm...@gmail.com]
>>Have you tried setting appendAssemblyId to false?
>
> No, that doesn't help, but thanks for the suggestion.
How so? If is required (and this is a good thing)
I'll add comments but I don't think this is a bug.
On Mon, Oct 25, 2010 at 4:23 PM, Phillip Hellewell wrote:
> On Mon, Oct 25, 2010 at 11:07 AM, Haszlakiewicz, Eric
> wrote:
>>
>> I was finally able to test this with the 2.2 release version, and it
>> fails for me too, so I created a issue in Ji
assemblies in 2.2,
> use 'descriptorRefs' instead of 'descriptors' and drop the '.xml' file
> extension. (This is also how one calls built-in descriptors like
> 'jar-with-dependencies' and 'bin'.) So, to adjust your example:
>
>
>
On Mon, Oct 25, 2010 at 11:07 AM, Haszlakiewicz, Eric
wrote:
>
> I was finally able to test this with the 2.2 release version, and it
> fails for me too, so I created a issue in Jira: MASSEMBLY-517.
Thanks Eric. Now I don't have to create it :)
Phillip
-
>-Original Message-
>From: Wendy Smoak [mailto:wsm...@gmail.com]
>
>On Thu, Oct 21, 2010 at 1:40 PM, Phillip Hellewell
>wrote:
>> I just found out the hard way that the latest version of the assembly
>> plugin requires an tag in the descriptor file, which i
On Thu, Oct 21, 2010 at 1:40 PM, Phillip Hellewell wrote:
> I just found out the hard way that the latest version of the assembly
> plugin requires an tag in the descriptor file, which is used as
> the classifier appended to the zip.
>
> I don't want to specify an id here
for me.
>> What version are you using?
>
>2.2, which was released a couple weeks ago apparently:
>
>http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-assembly-
>plugin/2.2/
hmm.. weird, the index my Nexus instance isn't picking up this version, so I
can't
alls built-in descriptors like
'jar-with-dependencies' and 'bin'.) So, to adjust your example:
maven-assembly-plugin
2.2
make-base-war
package
single
> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Thu, Oct 21, 2010 at 7:08 PM, Jon Paynter wrote:
>> > On Thu, Oct 21, 2010 at 4:08 AM, Aleksey Didik
>> > wrote:
>>
correctly and some others not O_o
> Any hint?
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Thu, Oct 21, 2010 at 7:08 PM, Jon Paynter wrote:
> > On Thu, Oct 21, 2010 at 4:08 AM, Aleksey Didik
> > wrote:
> >
> &
4:08 AM, Aleksey Didik
> wrote:
>
>> Hello all!
>>
>> I have used maven-assembly-plugin 2.2-beta-2 before and have those lines in
>> my descriptor:
>>
>>
>>
>> ${basedir}/src/scripts/python/updater.py
>> /
&g
po1.maven.org/maven2/org/apache/maven/plugins/maven-assembly-plugin/2.2/
Phillip
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
>-Original Message-
>From: Phillip Hellewell [mailto:ssh...@gmail.com]
>
>On Thu, Oct 21, 2010 at 11:40 AM, Phillip Hellewell
>wrote:
>> I just found out the hard way that the latest version of the assembly
>> plugin requires an tag in the descriptor fi
On Thu, Oct 21, 2010 at 11:40 AM, Phillip Hellewell wrote:
> I just found out the hard way that the latest version of the assembly
> plugin requires an tag in the descriptor file, which is used as
> the classifier appended to the zip.
>
> I don't want to specify an id here
I just found out the hard way that the latest version of the assembly
plugin requires an tag in the descriptor file, which is used as
the classifier appended to the zip.
I don't want to specify an id here because then means I have to
specify a classifier in the dependency section of my
On Thu, Oct 21, 2010 at 4:08 AM, Aleksey Didik
wrote:
> Hello all!
>
> I have used maven-assembly-plugin 2.2-beta-2 before and have those lines in
> my descriptor:
>
>
>
> ${basedir}/src/scripts/python/updater.py
>
Hello all!
I have used maven-assembly-plugin 2.2-beta-2 before and have those lines in
my descriptor:
${basedir}/src/scripts/python/updater.py
/
true
Filtering works right, I have got real project version instead of
301 - 400 of 1333 matches
Mail list logo
