You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by John Casey <jd...@commonjava.org> on 2008/07/23 23:03:29 UTC
[PLEASE TEST] Maven 2.0.10-RC2
Hello everyone,
Okay, I think we've got all of the problems with RC1 sorted out, and the
integration tests are finally passing again.
So, without further ado, let's get RC2 out there for testing! You can
find the distribution here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2
(In fact, the tarballs/zipfile are here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/)
Happy testing! Again, please let me know if you find any problems, and
I'll get them fixed ASAP.
Thanks,
-john
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by Jesse McConnell <je...@gmail.com>.
yep, I have others to throw on that stack then :) gl
On Thu, Jul 24, 2008 at 1:00 PM, John Casey <jd...@commonjava.org> wrote:
> See http://jira.codehaus.org/browse/MNG-3680
>
> -j
>
> Fabrice Bellingard wrote:
>>
>> Hi,
>>
>> well, a couple of things:
>>
>>
>> 1- I also had the stack trace issue (but Brett apparently just fixed it in
>> SVN)
>>
>>
>> 2- the following output appears several times in the build log of one of
>> my
>> projects (which I don't have with 2.0.9):
>>
>> ----------------
>> [WARNING] POM for 'bcel:bcel:pom:5.1:compile' is invalid. It will be
>> ignored
>> for artifact resolution. Reason: Parse error reading POM. Reason:
>> Unrecognised association: 'groupId' (position: START_TAG seen
>> ...<dependencies>\n <groupId>... @7:14) for project bcel:bcel at
>> C:\JIP\home\.m2\repository\bcel\bcel\5.1\bcel-5.1.pom
>> ----------------
>>
>> It is actually printed:
>> - twice in [resources:resources] phase
>> - 4 times in [resources:testResources] phase
>> - 4 times in [compiler:testCompile] phase
>> - 4 times in [surefire:test] phase
>> - 4 times in [assembly:attached] phase, in which I also get:
>>
>> ----------------
>> [WARNING] Attempting to build MavenProject instance for Artifact
>> (bcel:bcel:5.1) of type: jar; constructing POM artifact instead.
>> ----------------
>>
>> The POM for BCEL 5.1 is indeed invalid on Maven repo, which I had never
>> noticed before. So this is a good point (I created MEV-592). However,
>> printing this log 18 times is a bit violent, isn't it? :-)
>>
>>
>> Appart from that, all my projects build fine.
>>
>>
>> - Fabrice
>> bellingard@apache.org
>>
>> On Wed, Jul 23, 2008 at 11:03 PM, John Casey <jd...@commonjava.org>
>> wrote:
>>
>>> Hello everyone,
>>>
>>> Okay, I think we've got all of the problems with RC1 sorted out, and the
>>> integration tests are finally passing again.
>>>
>>> So, without further ado, let's get RC2 out there for testing! You can
>>> find
>>> the distribution here:
>>>
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2>
>>>
>>> (In fact, the tarballs/zipfile are here:
>>>
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/>
>>> )
>>>
>>> Happy testing! Again, please let me know if you find any problems, and
>>> I'll
>>> get them fixed ASAP.
>>>
>>> Thanks,
>>>
>>> -john
>>>
>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
jesse mcconnell
jesse.mcconnell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by John Casey <jd...@commonjava.org>.
See http://jira.codehaus.org/browse/MNG-3680
-j
Fabrice Bellingard wrote:
> Hi,
>
> well, a couple of things:
>
>
> 1- I also had the stack trace issue (but Brett apparently just fixed it in
> SVN)
>
>
> 2- the following output appears several times in the build log of one of my
> projects (which I don't have with 2.0.9):
>
> ----------------
> [WARNING] POM for 'bcel:bcel:pom:5.1:compile' is invalid. It will be ignored
> for artifact resolution. Reason: Parse error reading POM. Reason:
> Unrecognised association: 'groupId' (position: START_TAG seen
> ...<dependencies>\n <groupId>... @7:14) for project bcel:bcel at
> C:\JIP\home\.m2\repository\bcel\bcel\5.1\bcel-5.1.pom
> ----------------
>
> It is actually printed:
> - twice in [resources:resources] phase
> - 4 times in [resources:testResources] phase
> - 4 times in [compiler:testCompile] phase
> - 4 times in [surefire:test] phase
> - 4 times in [assembly:attached] phase, in which I also get:
>
> ----------------
> [WARNING] Attempting to build MavenProject instance for Artifact
> (bcel:bcel:5.1) of type: jar; constructing POM artifact instead.
> ----------------
>
> The POM for BCEL 5.1 is indeed invalid on Maven repo, which I had never
> noticed before. So this is a good point (I created MEV-592). However,
> printing this log 18 times is a bit violent, isn't it? :-)
>
>
> Appart from that, all my projects build fine.
>
>
> - Fabrice
> bellingard@apache.org
>
> On Wed, Jul 23, 2008 at 11:03 PM, John Casey <jd...@commonjava.org> wrote:
>
>> Hello everyone,
>>
>> Okay, I think we've got all of the problems with RC1 sorted out, and the
>> integration tests are finally passing again.
>>
>> So, without further ado, let's get RC2 out there for testing! You can find
>> the distribution here:
>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2>
>>
>> (In fact, the tarballs/zipfile are here:
>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/>
>> )
>>
>> Happy testing! Again, please let me know if you find any problems, and I'll
>> get them fixed ASAP.
>>
>> Thanks,
>>
>> -john
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by Fabrice Bellingard <be...@gmail.com>.
Hi,
well, a couple of things:
1- I also had the stack trace issue (but Brett apparently just fixed it in
SVN)
2- the following output appears several times in the build log of one of my
projects (which I don't have with 2.0.9):
----------------
[WARNING] POM for 'bcel:bcel:pom:5.1:compile' is invalid. It will be ignored
for artifact resolution. Reason: Parse error reading POM. Reason:
Unrecognised association: 'groupId' (position: START_TAG seen
...<dependencies>\n <groupId>... @7:14) for project bcel:bcel at
C:\JIP\home\.m2\repository\bcel\bcel\5.1\bcel-5.1.pom
----------------
It is actually printed:
- twice in [resources:resources] phase
- 4 times in [resources:testResources] phase
- 4 times in [compiler:testCompile] phase
- 4 times in [surefire:test] phase
- 4 times in [assembly:attached] phase, in which I also get:
----------------
[WARNING] Attempting to build MavenProject instance for Artifact
(bcel:bcel:5.1) of type: jar; constructing POM artifact instead.
----------------
The POM for BCEL 5.1 is indeed invalid on Maven repo, which I had never
noticed before. So this is a good point (I created MEV-592). However,
printing this log 18 times is a bit violent, isn't it? :-)
Appart from that, all my projects build fine.
- Fabrice
bellingard@apache.org
On Wed, Jul 23, 2008 at 11:03 PM, John Casey <jd...@commonjava.org> wrote:
> Hello everyone,
>
> Okay, I think we've got all of the problems with RC1 sorted out, and the
> integration tests are finally passing again.
>
> So, without further ado, let's get RC2 out there for testing! You can find
> the distribution here:
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2>
>
> (In fact, the tarballs/zipfile are here:
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/>
> )
>
> Happy testing! Again, please let me know if you find any problems, and I'll
> get them fixed ASAP.
>
> Thanks,
>
> -john
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by Michael McCallum <gh...@apache.org>.
On Thu, 24 Jul 2008 15:10:40 Michael McCallum wrote:
> I'm getting stack traces rather than the nice message when an artifact does
> not exist the repository...
For regular maven user you could almost get away with this... but for newbies
its will give them the willies and drive them away getting tonnes of stack
traces during normal behaviour.
In my case its a little worse 'cause I have 5 repositories...
* local
* overides
* java.net (proxy cached)
* restlet (proxy cached)
* central mirror (proxy cached)
so for each artifact thats new in the central repo i get 4 stack traces and
then a downloading message...
if no one goes DOH.. i know where that is i'll have a look at it later but
i'm. Its only for the lightweight http wagon BTW... obvious in the stack
trace me thinks
ta
--
Michael McCallum
Enterprise Engineer
mailto:gholam@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by Brett Porter <br...@apache.org>.
Fixed in SVN (you can also see comment on the RC1 thread for the
reason this was occuring).
- Brett
On 24/07/2008, at 1:10 PM, Michael McCallum wrote:
> I'm getting stack traces rather than the nice message when an
> artifact does
> not exist the repository...
>
> Downloading:
> http://mvn.somedomaindev.co.nz/central/nz/co/somedomain/nz.co.somedomain.parent/14-java4/nz.co.somedomain.parent-14-java4.pom
> org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate
> resource in repository
> at
> org
> .apache
> .maven
> .wagon
> .providers
> .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:
> 132)
> at
> org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:
> 116)
> at
> org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
> at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
> at
> org
> .apache
> .maven
> .artifact
> .manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:
> 474)
> at
> org
> .apache
> .maven
> .artifact
> .manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:363)
> at
> org
> .apache
> .maven
> .artifact
> .manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:318)
> at
> org
> .apache
> .maven
> .artifact
> .resolver
> .DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:200)
> at
> org
> .apache
> .maven
> .artifact
> .resolver
> .DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74)
> at
> org
> .apache
> .maven
> .project
> .DefaultMavenProjectBuilder
> .findModelFromRepository(DefaultMavenProjectBuilder.java:557)
> at
> org
> .apache
> .maven
> .project
> .DefaultMavenProjectBuilder
> .assembleLineage(DefaultMavenProjectBuilder.java:1393)
> at
> org
> .apache
> .maven
> .project
> .DefaultMavenProjectBuilder
> .buildInternal(DefaultMavenProjectBuilder.java:822)
> at
> org
> .apache
> .maven
> .project
> .DefaultMavenProjectBuilder
> .buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:507)
> at
> org
> .apache
> .maven
> .project
> .DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:199)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:
> 578)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
> at
> org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
> 292)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun
> .reflect
> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun
> .reflect
> .DelegatingMethodAccessorImpl
> .invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: java.io.FileNotFoundException:
> http://mvn.somedomaindev.co.nz/central/nz/co/somedomain/nz.co.somedomain.parent/14-java4/nz.co.somedomain.parent-14-java4.pom
> at
> sun
> .net
> .www
> .protocol
> .http.HttpURLConnection.getInputStream(HttpURLConnection.java:1239)
> at
> org
> .apache
> .maven
> .wagon
> .providers
> .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:
> 115)
>
> --
> Michael McCallum
> Development Lead
> somedomain Ltd
> cell: 021.576.907
> msn: gholam@xtra.co.nz
> jabber: mccallum.michael@gmail.com
> aim: gholamses
> http://www.somedomain.co.nz
> --
> Michael McCallum
> Enterprise Engineer
> mailto:gholam@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by Michael McCallum <gh...@apache.org>.
I'm getting stack traces rather than the nice message when an artifact does
not exist the repository...
Downloading:
http://mvn.somedomaindev.co.nz/central/nz/co/somedomain/nz.co.somedomain.parent/14-java4/nz.co.somedomain.parent-14-java4.pom
org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate
resource in repository
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:132)
at
org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:474)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:363)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:318)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:200)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:557)
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1393)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:822)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:507)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:199)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:578)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.io.FileNotFoundException:
http://mvn.somedomaindev.co.nz/central/nz/co/somedomain/nz.co.somedomain.parent/14-java4/nz.co.somedomain.parent-14-java4.pom
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1239)
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:115)
--
Michael McCallum
Development Lead
somedomain Ltd
cell: 021.576.907
msn: gholam@xtra.co.nz
jabber: mccallum.michael@gmail.com
aim: gholamses
http://www.somedomain.co.nz
--
Michael McCallum
Enterprise Engineer
mailto:gholam@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [PLEASE TEST] Maven 2.0.10-RC2
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
No doubt this is related to not resolving the contents of the build
section so that plugins like clover could fork and change things. This
might be troublesome.
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Wednesday, July 23, 2008 8:48 PM
To: Maven Developers List
Subject: Re: [PLEASE TEST] Maven 2.0.10-RC2
in 2.0.9, i used to beable to do this
<execution>
<id>${some.custom.var}</id>
....
Not any more with 2.0.10-RC2
here is the error:
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] One or more required plugin parameters are invalid/missing for
'appassemb
ler:assemble'
[0] Inside the definition for plugin 'appassembler-maven-plugin' specify
the fol
lowing:
<configuration>
...
<programs>VALUE</programs>
</configuration>.
Is it legal?
Any how, it is not a big deal, i can fix my build to deal with that.
-D
On Wed, Jul 23, 2008 at 2:03 PM, John Casey <jd...@commonjava.org>
wrote:
> Hello everyone,
>
> Okay, I think we've got all of the problems with RC1 sorted out, and
the
> integration tests are finally passing again.
>
> So, without further ado, let's get RC2 out there for testing! You can
find
> the distribution here:
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2
>
> (In fact, the tarballs/zipfile are here:
>
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apac
he/maven/apache-maven/2.0.10-RC2/)
>
> Happy testing! Again, please let me know if you find any problems, and
I'll
> get them fixed ASAP.
>
> Thanks,
>
> -john
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by John Casey <jd...@commonjava.org>.
Please file a JIRA for this issue, and if you can include a failing test
case that will make it much simpler to fix the issue.
Thanks,
-john
Marvin Froeder wrote:
> Running a report mojo (extends AbstractMojo and implements MavenReport)
>
> I inject build:
> /**
> * @parameter expression="${project.build}"
> * @required
> * @readonly
> */
> protected Build build;
>
> At some point I get build directory:
> build.getDirectory()
>
> But is returning "${project.basedir}/target"
>
> O maven 2.0.9 was returning c:/blabalba/bla/myproject/target
>
>
> VELO
>
>
> On Wed, Jul 23, 2008 at 9:48 PM, Dan Tran <da...@gmail.com> wrote:
>
>> in 2.0.9, i used to beable to do this
>>
>> <execution>
>> <id>${some.custom.var}</id>
>> ....
>>
>> Not any more with 2.0.10-RC2
>>
>> here is the error:
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] One or more required plugin parameters are invalid/missing for
>> 'appassemb
>> ler:assemble'
>>
>> [0] Inside the definition for plugin 'appassembler-maven-plugin' specify
>> the fol
>> lowing:
>>
>> <configuration>
>> ...
>> <programs>VALUE</programs>
>> </configuration>.
>>
>>
>> Is it legal?
>>
>> Any how, it is not a big deal, i can fix my build to deal with that.
>>
>> -D
>>
>> On Wed, Jul 23, 2008 at 2:03 PM, John Casey <jd...@commonjava.org>
>> wrote:
>>> Hello everyone,
>>>
>>> Okay, I think we've got all of the problems with RC1 sorted out, and the
>>> integration tests are finally passing again.
>>>
>>> So, without further ado, let's get RC2 out there for testing! You can
>> find
>>> the distribution here:
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2>
>>>
>>> (In fact, the tarballs/zipfile are here:
>>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/>
>> )
>>> Happy testing! Again, please let me know if you find any problems, and
>> I'll
>>> get them fixed ASAP.
>>>
>>> Thanks,
>>>
>>> -john
>>>
>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by John Casey <jd...@commonjava.org>.
FWIW, I've opened http://jira.codehaus.org/browse/MNG-3684
for this issue.
-john
Marvin Froeder wrote:
> Running a report mojo (extends AbstractMojo and implements MavenReport)
>
> I inject build:
> /**
> * @parameter expression="${project.build}"
> * @required
> * @readonly
> */
> protected Build build;
>
> At some point I get build directory:
> build.getDirectory()
>
> But is returning "${project.basedir}/target"
>
> O maven 2.0.9 was returning c:/blabalba/bla/myproject/target
>
>
> VELO
>
>
> On Wed, Jul 23, 2008 at 9:48 PM, Dan Tran <da...@gmail.com> wrote:
>
>> in 2.0.9, i used to beable to do this
>>
>> <execution>
>> <id>${some.custom.var}</id>
>> ....
>>
>> Not any more with 2.0.10-RC2
>>
>> here is the error:
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] One or more required plugin parameters are invalid/missing for
>> 'appassemb
>> ler:assemble'
>>
>> [0] Inside the definition for plugin 'appassembler-maven-plugin' specify
>> the fol
>> lowing:
>>
>> <configuration>
>> ...
>> <programs>VALUE</programs>
>> </configuration>.
>>
>>
>> Is it legal?
>>
>> Any how, it is not a big deal, i can fix my build to deal with that.
>>
>> -D
>>
>> On Wed, Jul 23, 2008 at 2:03 PM, John Casey <jd...@commonjava.org>
>> wrote:
>>> Hello everyone,
>>>
>>> Okay, I think we've got all of the problems with RC1 sorted out, and the
>>> integration tests are finally passing again.
>>>
>>> So, without further ado, let's get RC2 out there for testing! You can
>> find
>>> the distribution here:
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2>
>>>
>>> (In fact, the tarballs/zipfile are here:
>>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/>
>> )
>>> Happy testing! Again, please let me know if you find any problems, and
>> I'll
>>> get them fixed ASAP.
>>>
>>> Thanks,
>>>
>>> -john
>>>
>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by Marvin Froeder <ve...@gmail.com>.
Running a report mojo (extends AbstractMojo and implements MavenReport)
I inject build:
/**
* @parameter expression="${project.build}"
* @required
* @readonly
*/
protected Build build;
At some point I get build directory:
build.getDirectory()
But is returning "${project.basedir}/target"
O maven 2.0.9 was returning c:/blabalba/bla/myproject/target
VELO
On Wed, Jul 23, 2008 at 9:48 PM, Dan Tran <da...@gmail.com> wrote:
> in 2.0.9, i used to beable to do this
>
> <execution>
> <id>${some.custom.var}</id>
> ....
>
> Not any more with 2.0.10-RC2
>
> here is the error:
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] One or more required plugin parameters are invalid/missing for
> 'appassemb
> ler:assemble'
>
> [0] Inside the definition for plugin 'appassembler-maven-plugin' specify
> the fol
> lowing:
>
> <configuration>
> ...
> <programs>VALUE</programs>
> </configuration>.
>
>
> Is it legal?
>
> Any how, it is not a big deal, i can fix my build to deal with that.
>
> -D
>
> On Wed, Jul 23, 2008 at 2:03 PM, John Casey <jd...@commonjava.org>
> wrote:
> > Hello everyone,
> >
> > Okay, I think we've got all of the problems with RC1 sorted out, and the
> > integration tests are finally passing again.
> >
> > So, without further ado, let's get RC2 out there for testing! You can
> find
> > the distribution here:
> >
> > http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2>
> >
> > (In fact, the tarballs/zipfile are here:
> >
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/>
> )
> >
> > Happy testing! Again, please let me know if you find any problems, and
> I'll
> > get them fixed ASAP.
> >
> > Thanks,
> >
> > -john
> >
> > --
> > John Casey
> > Developer, PMC Member - Apache Maven (http://maven.apache.org)
> > Blog: http://www.ejlife.net/blogs/buildchimp/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by Dan Tran <da...@gmail.com>.
http://jira.codehaus.org/browse/MNG-3679
On Thu, Jul 24, 2008 at 7:46 AM, John Casey <jd...@commonjava.org> wrote:
> I'll take a look at it. If you have a small test case you could put into a
> JIRA ticket, that would help me out quite a bit.
>
> Thanks,
>
> -john
>
> Dan Tran wrote:
>>
>> in 2.0.9, i used to beable to do this
>>
>> <execution>
>> <id>${some.custom.var}</id>
>> ....
>>
>> Not any more with 2.0.10-RC2
>>
>> here is the error:
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] One or more required plugin parameters are invalid/missing for
>> 'appassemb
>> ler:assemble'
>>
>> [0] Inside the definition for plugin 'appassembler-maven-plugin' specify
>> the fol
>> lowing:
>>
>> <configuration>
>> ...
>> <programs>VALUE</programs>
>> </configuration>.
>>
>>
>> Is it legal?
>>
>> Any how, it is not a big deal, i can fix my build to deal with that.
>>
>> -D
>>
>> On Wed, Jul 23, 2008 at 2:03 PM, John Casey <jd...@commonjava.org>
>> wrote:
>>>
>>> Hello everyone,
>>>
>>> Okay, I think we've got all of the problems with RC1 sorted out, and the
>>> integration tests are finally passing again.
>>>
>>> So, without further ado, let's get RC2 out there for testing! You can
>>> find
>>> the distribution here:
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2
>>>
>>> (In fact, the tarballs/zipfile are here:
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/)
>>>
>>> Happy testing! Again, please let me know if you find any problems, and
>>> I'll
>>> get them fixed ASAP.
>>>
>>> Thanks,
>>>
>>> -john
>>>
>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by John Casey <jd...@commonjava.org>.
I'll take a look at it. If you have a small test case you could put into
a JIRA ticket, that would help me out quite a bit.
Thanks,
-john
Dan Tran wrote:
> in 2.0.9, i used to beable to do this
>
> <execution>
> <id>${some.custom.var}</id>
> ....
>
> Not any more with 2.0.10-RC2
>
> here is the error:
>
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] One or more required plugin parameters are invalid/missing for 'appassemb
> ler:assemble'
>
> [0] Inside the definition for plugin 'appassembler-maven-plugin' specify the fol
> lowing:
>
> <configuration>
> ...
> <programs>VALUE</programs>
> </configuration>.
>
>
> Is it legal?
>
> Any how, it is not a big deal, i can fix my build to deal with that.
>
> -D
>
> On Wed, Jul 23, 2008 at 2:03 PM, John Casey <jd...@commonjava.org> wrote:
>> Hello everyone,
>>
>> Okay, I think we've got all of the problems with RC1 sorted out, and the
>> integration tests are finally passing again.
>>
>> So, without further ado, let's get RC2 out there for testing! You can find
>> the distribution here:
>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2
>>
>> (In fact, the tarballs/zipfile are here:
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/)
>>
>> Happy testing! Again, please let me know if you find any problems, and I'll
>> get them fixed ASAP.
>>
>> Thanks,
>>
>> -john
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC2
Posted by Dan Tran <da...@gmail.com>.
in 2.0.9, i used to beable to do this
<execution>
<id>${some.custom.var}</id>
....
Not any more with 2.0.10-RC2
here is the error:
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] One or more required plugin parameters are invalid/missing for 'appassemb
ler:assemble'
[0] Inside the definition for plugin 'appassembler-maven-plugin' specify the fol
lowing:
<configuration>
...
<programs>VALUE</programs>
</configuration>.
Is it legal?
Any how, it is not a big deal, i can fix my build to deal with that.
-D
On Wed, Jul 23, 2008 at 2:03 PM, John Casey <jd...@commonjava.org> wrote:
> Hello everyone,
>
> Okay, I think we've got all of the problems with RC1 sorted out, and the
> integration tests are finally passing again.
>
> So, without further ado, let's get RC2 out there for testing! You can find
> the distribution here:
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2
>
> (In fact, the tarballs/zipfile are here:
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/)
>
> Happy testing! Again, please let me know if you find any problems, and I'll
> get them fixed ASAP.
>
> Thanks,
>
> -john
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org