Hi there,
I really need someone to shade some light on the issue below. I have
exausted my resources and still I am unable to get the assembly plugin
to work properly.
Thanks.
Original Message
Subject:Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
Date
I'm unable to reproduce this with anything similar. Can you boil it
down to a small test case and attach it to JIRA?
Thanks,
Brett
On 10/9/05, Erick Dovale [EMAIL PROTECTED] wrote:
Hi there,
I really need someone to shade some light on the issue below. I have
exausted my resources and still I
Either I am missing somethinghere or we have some bug hanging around.
I did what you suggested first and got this behaivor where the zip file
is created but no resources (dependencies and artifacts) from the
modules is added to it.
The modules are been iterated through and the jars for each one
Hi Brett,
I finally got the assembly 2.0-beta-2-SNAPSHOT to work this morning
after downloading the m2-beta-3. It seems to be working fine except for
the fact that it is not including the jars for the modules nor their
dependencies. Maybe I am missing something here:
At first it was
On Wed, 2005-10-05 at 11:07 -0400, Erick Dovale wrote:
Hi Brett,
I finally got the assembly 2.0-beta-2-SNAPSHOT to work this morning
after downloading the m2-beta-3. It seems to be working fine except for
the fact that it is not including the jars for the modules nor their
dependencies.
When is the beta-3 goint to be realeased??
cheers,
erick.
Brett Porter wrote:
.. fixed in SVN for the beta-3 release.
On 10/3/05, Brett Porter [EMAIL PROTECTED] wrote:
It's a bug. The aggregator isn't forking the package goal first as it should.
I will fix it shortly.
- Brett
On
Hi Brett,
I checked out the assembly plugin and was able to build it and deploy it
to my local repo. I also updated the version of the pluging in my root
pom to use 2.0-beta-2-SNAPSHOT which is the version of the newly built
plugin.
When I run the assembly plugin on my root pom it is behaiving
It's a bug. The aggregator isn't forking the package goal first as it should.
I will fix it shortly.
- Brett
On 10/3/05, Erick Dovale [EMAIL PROTECTED] wrote:
Hi Brett,
I checked out the assembly plugin and was able to build it and deploy it
to my local repo. I also updated the version of
.. fixed in SVN for the beta-3 release.
On 10/3/05, Brett Porter [EMAIL PROTECTED] wrote:
It's a bug. The aggregator isn't forking the package goal first as it
should.
I will fix it shortly.
- Brett
On 10/3/05, Erick Dovale [EMAIL PROTECTED] wrote:
Hi Brett,
I checked out the
Thanks for your reply Brett, I have inlined some questions I hope you
can answer for me.
Brett Porter wrote:
On 9/30/05, Erick Dovale [EMAIL PROTECTED] wrote:
I was trying to do exactly what this email is explaining below and had
exactly the same problem now using M2b1 which is that m2
On 10/2/05, Erick Dovale [EMAIL PROTECTED] wrote:
What is this tag?
It indicates the plugin should not run over subprojects, but has
access to the reactor to perform an aggregating task.
How do I get my hands on the latest commited code?
See the instructions on the site for building frmo
Hello there,
I was trying to do exactly what this email is explaining below and had
exactly the same problem now using M2b1 which is that m2 tries to run
the assembly plugin on each and every subproject. If I want to generate
a single assembly file containing all sub projects and their
On 9/30/05, Erick Dovale [EMAIL PROTECTED] wrote:
I was trying to do exactly what this email is explaining below and had
exactly the same problem now using M2b1 which is that m2 tries to run
the assembly plugin on each and every subproject.
Thanks for the reminder. I just committed the missing
13 matches
Mail list logo
