You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Kurt Schrader <ks...@karmalab.org> on 2003/02/13 00:25:33 UTC
[ANNOUNCEMENT] Maven Beta-8 Release
Maven Beta-8 has been released and can be found here:
http://jakarta.apache.org/builds/jakarta-turbine-maven/release/1.0-beta-8/
This release should be considered a mostly feature complete, but not bug
free, version of Maven 1.0. The website will be updated over the next few
days to reflect the changes in Beta 8. Please help us by upgrading to
Beta 8 and reporting any problems that you experience to our bug tracker.
Thanks,
The Maven Team
Re: LinkCheck test failures - previously [ANNOUNCEMENT] Maven Beta-8
Release
Posted by Ben Walding <de...@walding.com>.
If you're still having problems, can I get a copy of the files created
into target/test-reports/*LinkCheck*
And which platform you are building on
Cheers,
Ben
Jeff Turner wrote:
>On Wed, Feb 12, 2003 at 06:25:33PM -0500, Kurt Schrader wrote:
>
>
>>Maven Beta-8 has been released and can be found here:
>>
>>http://jakarta.apache.org/builds/jakarta-turbine-maven/release/1.0-beta-8/
>>
>>This release should be considered a mostly feature complete, but not bug
>>free, version of Maven 1.0. The website will be updated over the next few
>>days to reflect the changes in Beta 8. Please help us by upgrading to
>>Beta 8 and reporting any problems that you experience to our bug tracker.
>>
>>
>
>Building from CVS at the MAVEN_1_0_B8 tag, I get:
>
>...chugchug...
> [exec] test:test:
> [exec] [junit] dir attribute ignored if running in the same VM
> [exec] [junit] Running org.apache.maven.linkcheck.LinkCheckTest
> [exec] Rhino classes (js.jar) not found - Javascript disabled
> [exec] [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.819 sec
> [exec] [junit] [ERROR] TEST org.apache.maven.linkcheck.LinkCheckTest FAILED
>
> [exec] BUILD FAILED
> [exec] com.werken.werkz.UnattainableGoalException: Unable to obtain goal [plugin] -- null:14:34: <attainGoal> null:95:54: <fail> There were test failures.
> [exec] at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:389)
> [exec] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> [exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> [exec] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
> [exec] at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
> [exec] at com.werken.werkz.Goal.fire(Goal.java:639)
> [exec] at com.werken.werkz.Goal.attain(Goal.java:575)
> [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:383)
> [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:360)
> [exec] at org.apache.maven.cli.App.doMain(App.java:518)
>...lots more tracktrace...
>BUILD FAILED
>file:/old/home/jeff/homeoverflow/apache/jakarta/jakarta-turbine-maven-b8/build-bootstrap.xml:227: exec returned: 70
>
>Anyway, I'll try the binary distribution.
>
>
>--Jeff
>
>
>
>>Thanks,
>>The Maven Team
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-maven-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-maven-user-help@jakarta.apache.org
>
>
>
>
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Jeff Turner <je...@apache.org>.
On Wed, Feb 12, 2003 at 06:25:33PM -0500, Kurt Schrader wrote:
> Maven Beta-8 has been released and can be found here:
>
> http://jakarta.apache.org/builds/jakarta-turbine-maven/release/1.0-beta-8/
>
> This release should be considered a mostly feature complete, but not bug
> free, version of Maven 1.0. The website will be updated over the next few
> days to reflect the changes in Beta 8. Please help us by upgrading to
> Beta 8 and reporting any problems that you experience to our bug tracker.
Building from CVS at the MAVEN_1_0_B8 tag, I get:
...chugchug...
[exec] test:test:
[exec] [junit] dir attribute ignored if running in the same VM
[exec] [junit] Running org.apache.maven.linkcheck.LinkCheckTest
[exec] Rhino classes (js.jar) not found - Javascript disabled
[exec] [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.819 sec
[exec] [junit] [ERROR] TEST org.apache.maven.linkcheck.LinkCheckTest FAILED
[exec] BUILD FAILED
[exec] com.werken.werkz.UnattainableGoalException: Unable to obtain goal [plugin] -- null:14:34: <attainGoal> null:95:54: <fail> There were test failures.
[exec] at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:389)
[exec] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
[exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
[exec] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
[exec] at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
[exec] at com.werken.werkz.Goal.fire(Goal.java:639)
[exec] at com.werken.werkz.Goal.attain(Goal.java:575)
[exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:383)
[exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:360)
[exec] at org.apache.maven.cli.App.doMain(App.java:518)
...lots more tracktrace...
BUILD FAILED
file:/old/home/jeff/homeoverflow/apache/jakarta/jakarta-turbine-maven-b8/build-bootstrap.xml:227: exec returned: 70
Anyway, I'll try the binary distribution.
--Jeff
>
> Thanks,
> The Maven Team
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by saimon <sa...@yahoo.co.uk>.
Congratulations and well done to all the Maven developers!
You did good! ;)
Now for us users to pitch in...
Saimon
Kurt Schrader wrote:
>Maven Beta-8 has been released and can be found here:
>
>http://jakarta.apache.org/builds/jakarta-turbine-maven/release/1.0-beta-8/
>
>This release should be considered a mostly feature complete, but not bug
>free, version of Maven 1.0. The website will be updated over the next few
>days to reflect the changes in Beta 8. Please help us by upgrading to
>Beta 8 and reporting any problems that you experience to our bug tracker.
>
>Thanks,
>The Maven Team
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-maven-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-maven-user-help@jakarta.apache.org
>
>
>
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Ben Walding <be...@walding.com>.
While the behaviour is not desired (a better error message is
preferred), it is caused by running maven in a directory with no project.xml
I've raised MAVEN-265 for this.
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-265
Kasper Nielsen wrote:
> Kurt Schrader wrote:
>
>> Maven Beta-8 has been released and can be found here:
>>
>> http://jakarta.apache.org/builds/jakarta-turbine-maven/release/1.0-beta-8/
>>
>> This release should be considered a mostly feature complete, but not bug
>> free, version of Maven 1.0. The website will be updated over the
>> next few
>> days to reflect the changes in Beta 8. Please help us by upgrading to
>> Beta 8 and reporting any problems that you experience to our bug
>> tracker.
>>
>> Thanks,
>> The Maven Team
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> turbine-maven-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail:
>> turbine-maven-user-help@jakarta.apache.org
>>
>>
>
> is it just me or...
> unzip stuff
> f:\maven-1.0-beta-8>set MAVEN_HOME=f:\maven-1.0-beta-8
> F:\maven-1.0-beta-8>.\bin\maven -v
> __ __
> | \/ |__ Jakarta _ ___
> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> |_| |_\__,_|\_/\___|_||_| v. 1.0-beta-8
>
>
> java.lang.NullPointerException at
> org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:354)
> at
> org.apache.maven.MavenSession.attainGoals(MavenSession.java:360)
> at org.apache.maven.cli.App.doMain(App.java:518)
> at org.apache.maven.cli.App.main(App.java:1074)
> 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:324)
> at com.werken.forehead.Forehead.run(Forehead.java:543)
> at com.werken.forehead.Forehead.main(Forehead.java:573)
> Total time: 2 seconds
>
>
> Fresh download of maven-beta-8
>
> - Kasper
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> turbine-maven-user-help@jakarta.apache.org
>
>
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Kasper Nielsen <ne...@kav.dk>.
Kurt Schrader wrote:
> Maven Beta-8 has been released and can be found here:
>
> http://jakarta.apache.org/builds/jakarta-turbine-maven/release/1.0-beta-8/
>
> This release should be considered a mostly feature complete, but not bug
> free, version of Maven 1.0. The website will be updated over the next few
> days to reflect the changes in Beta 8. Please help us by upgrading to
> Beta 8 and reporting any problems that you experience to our bug tracker.
>
> Thanks,
> The Maven Team
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-maven-user-help@jakarta.apache.org
>
>
is it just me or...
unzip stuff
f:\maven-1.0-beta-8>set MAVEN_HOME=f:\maven-1.0-beta-8
F:\maven-1.0-beta-8>.\bin\maven -v
__ __
| \/ |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-8
java.lang.NullPointerException at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:354)
at
org.apache.maven.MavenSession.attainGoals(MavenSession.java:360)
at org.apache.maven.cli.App.doMain(App.java:518)
at org.apache.maven.cli.App.main(App.java:1074)
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:324)
at com.werken.forehead.Forehead.run(Forehead.java:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
Total time: 2 seconds
Fresh download of maven-beta-8
- Kasper
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Colin Sampaleanu <co...@exis.com>.
After your commit, the build does break. The code still needs work, in
that aside from the build breakage and message about that, now there is
an error displayed even for file not found (for remote repos that are
accessed through http, but not through 'file:' ), which is not
appropriate. I will try to spend a bit of time on this code on the
weekend to clean things up...
dion@multitask.com.au wrote:
>Was this before or after my commit an hour or two back?
>--
>dIon Gillard, Multitask Consulting
>Blog: http://www.freeroller.net/page/dion/Weblog
>Work: http://www.multitask.com.au
>
>
>"Peter Lynch" <pe...@mindspring.com> wrote on 14/02/2003 06:10:28 PM:
>
>
>
>>I can also verify that with maven HEAD today builds does not fail when
>>dependencies can't be found.
>>
>>I use Win 2000 JDK 1.4.1_01 also.
>>
>>-Peter
>>
>>
>>----- Original Message -----
>>From: "Colin Sampaleanu" <co...@exis.com>
>>To: "Turbine Maven Users List" <tu...@jakarta.apache.org>
>>Sent: Thursday, February 13, 2003 8:34 AM
>>Subject: Re: [ANNOUNCEMENT] Maven Beta-8 Release
>>
>>
>>
>>
>>>Jason van Zyl wrote:
>>>
>>>
>>>
>>>>On Thu, 2003-02-13 at 11:02, Colin Sampaleanu wrote:
>>>>
>>>>
>>>>
>>>>
>>>>>Jason van Zyl wrote:
>>>>>
>>>>>
>>>>>
>>>>>>On Thu, 2003-02-13 at 09:40, Colin Sampaleanu wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>This is quite possible, since the current code doesn't break the
>>>>>>>
>>>>>>>
>build
>
>
>>>>>>>when a dependency is not found...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>Ok, I just tried what you described with HEAD and got:
>>>>>>
>>>>>>-----
>>>>>>__ __
>>>>>>| \/ |__ Jakarta _ ___
>>>>>>| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
>>>>>>|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9
>>>>>>
>>>>>>
>>>>>>Attempting to download crapola-1.0.jar.
>>>>>>WARNING: Failed to download crapola-1.0.jar.
>>>>>>The build cannot continue because of the following unsatisfied
>>>>>>dependency:
>>>>>>
>>>>>>crapola-1.0.jar
>>>>>>
>>>>>>Total time: 4 seconds
>>>>>>
>>>>>>-----
>>>>>>
>>>>>>Where do we have the mismatch?
>>>>>>
>>>>>>
>>>>>>
>>>>>Maybe it's an OS thing. I am running Win2k, and I think you are
>>>>>
>>>>>
>running
>
>
>>>>>Linux?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>Yes, I have Linux. Do you have multiple repositories set? Maybe
>>>>
>>>>
>that's
>
>
>>>>it.
>>>>
>>>>
>>>>
>>>>>The other thing I just verified is that while dIon had said he
>>>>>was going to change the ignoreErrors flag to false (in
>>>>>DependencyVerifier), it's still true. So actually, I understand why
>>>>>
>>>>>
>it's
>
>
>>>>>not failing for me, I don't understand why it's failing for you.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>We should probably change the logic to just let the downloads occur
>>>>
>>>>
>and
>
>
>>>>then check again afterward which artifacts are present. That way it
>>>>
>>>>
>wil
>
>
>>>>always depend on what is actually present in the local repository.
>>>>
>>>>
>>>>
>>>>>I think
>>>>>in my case what is happening is that an expected error happens (in
>>>>>HttpUtils), and because of the ignoreErrors that doesn't get
>>>>>
>>>>>
>returned as
>
>
>>>>>an error. In your case, an exception of another sort gets thrown,
>>>>>
>>>>>
>which
>
>
>>>>>doesn't get filtered by the ignoreErrors flag but comes through to
>>>>>DependencyVerifier, so the artifact is not treated as downloaded.
>>>>>
>>>>>Will try to figure this out in more depth.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>Ok, thanks. Things are in better shape now so patches can be applied
>>>>
>>>>
>a
>
>
>>>>little faster now.
>>>>
>>>>
>>>>
>>>Here is some more info, after stepping through the code again in a
>>>debugger. In my case, everything is behaving exactly as expected,
>>>
>>>
>given
>
>
>>>the code that is there. I don't understand why it's failing for you.
>>>
>>>getRemoteArtifact() calls HttpUtils.getFile() with ignoreErrors set to
>>>true. getfile does a connection, gets past the point where it checks
>>>
>>>
>the
>
>
>>>headers for HTTP_NOT_MODIFIED and HTTP_UNAUTHORIZED, and arrives at
>>>
>>>
>the
>
>
>>>loop where it tries 3 times to get the inputstream. At that point, it
>>>catches any IOException (in this case, FileNotFoundException) and
>>>
>>>
>always
>
>
>>>ignores it. Immediately afterwards, because ignoreErrors is true, it
>>>doesn't treat the fact that the inputstream is null as an error, but
>>>simply returns.
>>>
>>>So everything works exactly as it should, given the code in CVS. The
>>>real question is why the build is failing for you. I think in your
>>>
>>>
>case
>
>
>>>possibly something else other than an IOException is being thrown, so
>>>
>>>
>is
>
>
>>>not being caught in getFile(), or maybe an exception is thrown before
>>>that point even...
>>>
>>>What would _probably_ resolve things is to set ignoreErrors to false,
>>>
>>>
>as
>
>
>>>dIon had wanted to, but I would still figure out why stuff is working
>>>for you with the present code, since it just doesn't make sense.
>>>
>>>Colin
>>>
>>>
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by di...@multitask.com.au.
Was this before or after my commit an hour or two back?
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
"Peter Lynch" <pe...@mindspring.com> wrote on 14/02/2003 06:10:28 PM:
> I can also verify that with maven HEAD today builds does not fail when
> dependencies can't be found.
>
> I use Win 2000 JDK 1.4.1_01 also.
>
> -Peter
>
>
> ----- Original Message -----
> From: "Colin Sampaleanu" <co...@exis.com>
> To: "Turbine Maven Users List" <tu...@jakarta.apache.org>
> Sent: Thursday, February 13, 2003 8:34 AM
> Subject: Re: [ANNOUNCEMENT] Maven Beta-8 Release
>
>
> > Jason van Zyl wrote:
> >
> > >On Thu, 2003-02-13 at 11:02, Colin Sampaleanu wrote:
> > >
> > >
> > >>Jason van Zyl wrote:
> > >>
> > >>>On Thu, 2003-02-13 at 09:40, Colin Sampaleanu wrote:
> > >>>
> > >>>>This is quite possible, since the current code doesn't break the
build
> > >>>>when a dependency is not found...
> > >>>>
> > >>>Ok, I just tried what you described with HEAD and got:
> > >>>
> > >>>-----
> > >>>__ __
> > >>>| \/ |__ Jakarta _ ___
> > >>>| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> > >>>|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9
> > >>>
> > >>>
> > >>>Attempting to download crapola-1.0.jar.
> > >>>WARNING: Failed to download crapola-1.0.jar.
> > >>>The build cannot continue because of the following unsatisfied
> > >>>dependency:
> > >>>
> > >>>crapola-1.0.jar
> > >>>
> > >>>Total time: 4 seconds
> > >>>
> > >>>-----
> > >>>
> > >>>Where do we have the mismatch?
> > >>>
> > >>Maybe it's an OS thing. I am running Win2k, and I think you are
running
> > >>Linux?
> > >>
> > >>
> > >Yes, I have Linux. Do you have multiple repositories set? Maybe
that's
> > >it.
> > >
> > >>The other thing I just verified is that while dIon had said he
> > >>was going to change the ignoreErrors flag to false (in
> > >>DependencyVerifier), it's still true. So actually, I understand why
it's
> > >>not failing for me, I don't understand why it's failing for you.
> > >>
> > >>
> > >We should probably change the logic to just let the downloads occur
and
> > >then check again afterward which artifacts are present. That way it
wil
> > >always depend on what is actually present in the local repository.
> > >
> > >>I think
> > >>in my case what is happening is that an expected error happens (in
> > >>HttpUtils), and because of the ignoreErrors that doesn't get
returned as
> > >>an error. In your case, an exception of another sort gets thrown,
which
> > >>doesn't get filtered by the ignoreErrors flag but comes through to
> > >>DependencyVerifier, so the artifact is not treated as downloaded.
> > >>
> > >>Will try to figure this out in more depth.
> > >>
> > >>
> > >Ok, thanks. Things are in better shape now so patches can be applied
a
> > >little faster now.
> > >
> > Here is some more info, after stepping through the code again in a
> > debugger. In my case, everything is behaving exactly as expected,
given
> > the code that is there. I don't understand why it's failing for you.
> >
> > getRemoteArtifact() calls HttpUtils.getFile() with ignoreErrors set to
> > true. getfile does a connection, gets past the point where it checks
the
> > headers for HTTP_NOT_MODIFIED and HTTP_UNAUTHORIZED, and arrives at
the
> > loop where it tries 3 times to get the inputstream. At that point, it
> > catches any IOException (in this case, FileNotFoundException) and
always
> > ignores it. Immediately afterwards, because ignoreErrors is true, it
> > doesn't treat the fact that the inputstream is null as an error, but
> > simply returns.
> >
> > So everything works exactly as it should, given the code in CVS. The
> > real question is why the build is failing for you. I think in your
case
> > possibly something else other than an IOException is being thrown, so
is
> > not being caught in getFile(), or maybe an exception is thrown before
> > that point even...
> >
> > What would _probably_ resolve things is to set ignoreErrors to false,
as
> > dIon had wanted to, but I would still figure out why stuff is working
> > for you with the present code, since it just doesn't make sense.
> >
> > Colin
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
turbine-maven-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
turbine-maven-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
turbine-maven-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-maven-user-help@jakarta.apache.org
>
> ForwardSourceID:NT000B15E6
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Peter Lynch <pe...@mindspring.com>.
I can also verify that with maven HEAD today builds does not fail when
dependencies can't be found.
I use Win 2000 JDK 1.4.1_01 also.
-Peter
----- Original Message -----
From: "Colin Sampaleanu" <co...@exis.com>
To: "Turbine Maven Users List" <tu...@jakarta.apache.org>
Sent: Thursday, February 13, 2003 8:34 AM
Subject: Re: [ANNOUNCEMENT] Maven Beta-8 Release
> Jason van Zyl wrote:
>
> >On Thu, 2003-02-13 at 11:02, Colin Sampaleanu wrote:
> >
> >
> >>Jason van Zyl wrote:
> >>
> >>>On Thu, 2003-02-13 at 09:40, Colin Sampaleanu wrote:
> >>>
> >>>>This is quite possible, since the current code doesn't break the build
> >>>>when a dependency is not found...
> >>>>
> >>>Ok, I just tried what you described with HEAD and got:
> >>>
> >>>-----
> >>>__ __
> >>>| \/ |__ Jakarta _ ___
> >>>| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> >>>|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9
> >>>
> >>>
> >>>Attempting to download crapola-1.0.jar.
> >>>WARNING: Failed to download crapola-1.0.jar.
> >>>The build cannot continue because of the following unsatisfied
> >>>dependency:
> >>>
> >>>crapola-1.0.jar
> >>>
> >>>Total time: 4 seconds
> >>>
> >>>-----
> >>>
> >>>Where do we have the mismatch?
> >>>
> >>Maybe it's an OS thing. I am running Win2k, and I think you are running
> >>Linux?
> >>
> >>
> >Yes, I have Linux. Do you have multiple repositories set? Maybe that's
> >it.
> >
> >>The other thing I just verified is that while dIon had said he
> >>was going to change the ignoreErrors flag to false (in
> >>DependencyVerifier), it's still true. So actually, I understand why it's
> >>not failing for me, I don't understand why it's failing for you.
> >>
> >>
> >We should probably change the logic to just let the downloads occur and
> >then check again afterward which artifacts are present. That way it wil
> >always depend on what is actually present in the local repository.
> >
> >>I think
> >>in my case what is happening is that an expected error happens (in
> >>HttpUtils), and because of the ignoreErrors that doesn't get returned as
> >>an error. In your case, an exception of another sort gets thrown, which
> >>doesn't get filtered by the ignoreErrors flag but comes through to
> >>DependencyVerifier, so the artifact is not treated as downloaded.
> >>
> >>Will try to figure this out in more depth.
> >>
> >>
> >Ok, thanks. Things are in better shape now so patches can be applied a
> >little faster now.
> >
> Here is some more info, after stepping through the code again in a
> debugger. In my case, everything is behaving exactly as expected, given
> the code that is there. I don't understand why it's failing for you.
>
> getRemoteArtifact() calls HttpUtils.getFile() with ignoreErrors set to
> true. getfile does a connection, gets past the point where it checks the
> headers for HTTP_NOT_MODIFIED and HTTP_UNAUTHORIZED, and arrives at the
> loop where it tries 3 times to get the inputstream. At that point, it
> catches any IOException (in this case, FileNotFoundException) and always
> ignores it. Immediately afterwards, because ignoreErrors is true, it
> doesn't treat the fact that the inputstream is null as an error, but
> simply returns.
>
> So everything works exactly as it should, given the code in CVS. The
> real question is why the build is failing for you. I think in your case
> possibly something else other than an IOException is being thrown, so is
> not being caught in getFile(), or maybe an exception is thrown before
> that point even...
>
> What would _probably_ resolve things is to set ignoreErrors to false, as
> dIon had wanted to, but I would still figure out why stuff is working
> for you with the present code, since it just doesn't make sense.
>
> Colin
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-maven-user-help@jakarta.apache.org
>
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Colin Sampaleanu <co...@exis.com>.
Jason van Zyl wrote:
>On Thu, 2003-02-13 at 11:02, Colin Sampaleanu wrote:
>
>
>>Jason van Zyl wrote:
>>
>>>On Thu, 2003-02-13 at 09:40, Colin Sampaleanu wrote:
>>>
>>>>This is quite possible, since the current code doesn't break the build
>>>>when a dependency is not found...
>>>>
>>>Ok, I just tried what you described with HEAD and got:
>>>
>>>-----
>>>__ __
>>>| \/ |__ Jakarta _ ___
>>>| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
>>>|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9
>>>
>>>
>>>Attempting to download crapola-1.0.jar.
>>>WARNING: Failed to download crapola-1.0.jar.
>>>The build cannot continue because of the following unsatisfied
>>>dependency:
>>>
>>>crapola-1.0.jar
>>>
>>>Total time: 4 seconds
>>>
>>>-----
>>>
>>>Where do we have the mismatch?
>>>
>>Maybe it's an OS thing. I am running Win2k, and I think you are running
>>Linux?
>>
>>
>Yes, I have Linux. Do you have multiple repositories set? Maybe that's
>it.
>
>>The other thing I just verified is that while dIon had said he
>>was going to change the ignoreErrors flag to false (in
>>DependencyVerifier), it's still true. So actually, I understand why it's
>>not failing for me, I don't understand why it's failing for you.
>>
>>
>We should probably change the logic to just let the downloads occur and
>then check again afterward which artifacts are present. That way it wil
>always depend on what is actually present in the local repository.
>
>>I think
>>in my case what is happening is that an expected error happens (in
>>HttpUtils), and because of the ignoreErrors that doesn't get returned as
>>an error. In your case, an exception of another sort gets thrown, which
>>doesn't get filtered by the ignoreErrors flag but comes through to
>>DependencyVerifier, so the artifact is not treated as downloaded.
>>
>>Will try to figure this out in more depth.
>>
>>
>Ok, thanks. Things are in better shape now so patches can be applied a
>little faster now.
>
Here is some more info, after stepping through the code again in a
debugger. In my case, everything is behaving exactly as expected, given
the code that is there. I don't understand why it's failing for you.
getRemoteArtifact() calls HttpUtils.getFile() with ignoreErrors set to
true. getfile does a connection, gets past the point where it checks the
headers for HTTP_NOT_MODIFIED and HTTP_UNAUTHORIZED, and arrives at the
loop where it tries 3 times to get the inputstream. At that point, it
catches any IOException (in this case, FileNotFoundException) and always
ignores it. Immediately afterwards, because ignoreErrors is true, it
doesn't treat the fact that the inputstream is null as an error, but
simply returns.
So everything works exactly as it should, given the code in CVS. The
real question is why the build is failing for you. I think in your case
possibly something else other than an IOException is being thrown, so is
not being caught in getFile(), or maybe an exception is thrown before
that point even...
What would _probably_ resolve things is to set ignoreErrors to false, as
dIon had wanted to, but I would still figure out why stuff is working
for you with the present code, since it just doesn't make sense.
Colin
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Jason van Zyl <ja...@zenplex.com>.
On Thu, 2003-02-13 at 11:02, Colin Sampaleanu wrote:
> Jason van Zyl wrote:
>
> >On Thu, 2003-02-13 at 09:40, Colin Sampaleanu wrote:
> >
> >
> >>This is quite possible, since the current code doesn't break the build
> >>when a dependency is not found...
> >>
> >>
> >>
> >
> >Ok, I just tried what you described with HEAD and got:
> >
> >-----
> > __ __
> >| \/ |__ Jakarta _ ___
> >| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> >|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9
> >
> >
> >Attempting to download crapola-1.0.jar.
> >WARNING: Failed to download crapola-1.0.jar.
> >The build cannot continue because of the following unsatisfied
> >dependency:
> >
> >crapola-1.0.jar
> >
> >Total time: 4 seconds
> >
> >-----
> >
> >Where do we have the mismatch?
> >
> >
> >
> Maybe it's an OS thing. I am running Win2k, and I think you are running
> Linux?
Yes, I have Linux. Do you have multiple repositories set? Maybe that's
it.
> The other thing I just verified is that while dIon had said he
> was going to change the ignoreErrors flag to false (in
> DependencyVerifier), it's still true. So actually, I understand why it's
> not failing for me, I don't understand why it's failing for you.
We should probably change the logic to just let the downloads occur and
then check again afterward which artifacts are present. That way it wil
always depend on what is actually present in the local repository.
> I think
> in my case what is happening is that an expected error happens (in
> HttpUtils), and because of the ignoreErrors that doesn't get returned as
> an error.
> In your case, an exception of another sort gets thrown, which
> doesn't get filtered by the ignoreErrors flag but comes through to
> DependencyVerifier, so the artifact is not treated as downloaded.
>
> Will try to figure this out in more depth.
Ok, thanks. Things are in better shape now so patches can be applied a
little faster now.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-maven-user-help@jakarta.apache.org
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Colin Sampaleanu <co...@exis.com>.
Jason van Zyl wrote:
>On Thu, 2003-02-13 at 09:40, Colin Sampaleanu wrote:
>
>
>>This is quite possible, since the current code doesn't break the build
>>when a dependency is not found...
>>
>>
>>
>
>Ok, I just tried what you described with HEAD and got:
>
>-----
> __ __
>| \/ |__ Jakarta _ ___
>| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
>|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9
>
>
>Attempting to download crapola-1.0.jar.
>WARNING: Failed to download crapola-1.0.jar.
>The build cannot continue because of the following unsatisfied
>dependency:
>
>crapola-1.0.jar
>
>Total time: 4 seconds
>
>-----
>
>Where do we have the mismatch?
>
>
>
Maybe it's an OS thing. I am running Win2k, and I think you are running
Linux? The other thing I just verified is that while dIon had said he
was going to change the ignoreErrors flag to false (in
DependencyVerifier), it's still true. So actually, I understand why it's
not failing for me, I don't understand why it's failing for you. I think
in my case what is happening is that an expected error happens (in
HttpUtils), and because of the ignoreErrors that doesn't get returned as
an error. In your case, an exception of another sort gets thrown, which
doesn't get filtered by the ignoreErrors flag but comes through to
DependencyVerifier, so the artifact is not treated as downloaded.
Will try to figure this out in more depth.
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Jason van Zyl <ja...@zenplex.com>.
On Thu, 2003-02-13 at 09:40, Colin Sampaleanu wrote:
> This is quite possible, since the current code doesn't break the build
> when a dependency is not found...
>
Ok, I just tried what you described with HEAD and got:
-----
__ __
| \/ |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9
Attempting to download crapola-1.0.jar.
WARNING: Failed to download crapola-1.0.jar.
The build cannot continue because of the following unsatisfied
dependency:
crapola-1.0.jar
Total time: 4 seconds
-----
Where do we have the mismatch?
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Colin Sampaleanu <co...@exis.com>.
Jason van Zyl wrote:
>On Thu, 2003-02-13 at 09:40, Colin Sampaleanu wrote:
>
>
>>This is quite possible, since the current code doesn't break the build
>>when a dependency is not found...
>>
>>
>Yes it does, this is what happens when building the XMLRPC component
>when the javamail JAR is not present:
>
>-----
>| \/ |__ Jakarta _ ___
>| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
>|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9
>
>
>Attempting to download javamail-1.2.jar.
>WARNING: Failed to download javamail-1.2.jar.
>The build cannot continue because of the following unsatisfied
>dependency:
>
>javamail-1.2.jar
>
>Total time: 4 seconds
>-----
>
>I believe your condition is multiple repostories. Please don't make
>blanket statements that aren't correct.
>
>
Please give me a bit of credit :-) I have looked at the code, stepped
through it in a debugger, and emailed with you (and dIon) about this.
Below is an example of maven b8 with one remote repo (ibiblio), with a
project generated via genapp, where I have added a bs (non-existent)
dependency called 'crapola'.
D:\devt\maventest1>maven
__ __
| \/ |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-8
Attempting to download crapola-1.0.0.jar.
BUILD SUCCESSFUL
Total time: 2 seconds
There is no such jar, it can't download it, there is no error printed
about it (as per my email before), and if I try to build it again it
will try to download it again.
Now based on your email, it's obviously breaking for you in some cases,
but to the best of (what I thought was my reasonably informed knowledge)
I thought I was making a correct statement...
Colin
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Jason van Zyl <ja...@zenplex.com>.
On Thu, 2003-02-13 at 09:40, Colin Sampaleanu wrote:
> This is quite possible, since the current code doesn't break the build
> when a dependency is not found...
Yes it does, this is what happens when building the XMLRPC component
when the javamail JAR is not present:
-----
| \/ |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9
Attempting to download javamail-1.2.jar.
WARNING: Failed to download javamail-1.2.jar.
The build cannot continue because of the following unsatisfied
dependency:
javamail-1.2.jar
Total time: 4 seconds
-----
I believe your condition is multiple repostories. Please don't make
blanket statements that aren't correct.
> Ben Walding wrote:
>
> > Note that several jars have been removed from the repository (notably
> > javamail and activation). This is in order to comply with the
> > licenses. You may now be missing some jars from repository.
> >
> > Which platform are you experiencing difficulties with?
> >
> > Off hand I can't tell you what problem is with junit report.
> > Attaching the stack trace may help.
> > maven -X maven-junit-report-plugin:report
> >
> >
> > With the changelog report, it would pay to have a look at end of
> > maven.log
> > just do
> > maven maven-changelog-plugin:report
> > to generate the changelog report alone (and then attach the maven.log
> > for us to see).
> >
> >
> > Age Mooy wrote:
> >
> >> Is there some kind of migration document available. After installing b8
> >> and letting it download all of its dependencies, I ran "maven site" on
> >> my current project and got some weird behaviour:
> >>
> >> - maven-junit-report-plugin:report fails all unit tests (while test:test
> >> has no problems) and then goes into a major stacktrace-producing loop
> >> for about 30 seconds before giving up.
> >> - maven-changelog-plugin:report doesn't find a single change while my
> >> usual b7 installation finds more than 1000 changes. The activity report
> >> is also empty of course.
> >>
> >> I assume these things have something to do with the settings in
> >> project.xml/project.properties.... anyone know how to solve these ?
> >>
> >> Age
> >>
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: Kurt Schrader [mailto:kschrader@karmalab.org] Sent: Thursday,
> >>> February 13, 2003 00:26
> >>> To: turbine-maven-user@jakarta.apache.org
> >>> Subject: [ANNOUNCEMENT] Maven Beta-8 Release
> >>>
> >>>
> >>> Maven Beta-8 has been released and can be found here:
> >>>
> >>> http://jakarta.apache.org/builds/jakarta-turbine-maven/release
> >>>
> >>
> >> /1.0-beta-8/
> >>
> >>
> >>> This release should be considered a mostly feature complete, but not
> >>> bug free, version of Maven 1.0. The website will be updated over
> >>> the next few days to reflect the changes in Beta 8. Please help us
> >>> by upgrading to Beta 8 and reporting any problems that you
> >>> experience to our bug tracker.
> >>>
> >>> Thanks,
> >>> The Maven Team
> >>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-maven-user-help@jakarta.apache.org
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Colin Sampaleanu <co...@exis.com>.
I saw an email from you that you were going to test it and then check it
in, but I think it never made it in, at least DependencyVerifier is
still setting ignoreErrors to true. Before doing that though, I still
think it's worth it to establish why it's working ok for Jason (and
presumably some other people). As per another email from me, tracing
through the code, I would think it shouldn't work ok for anybody with
ignoreErrors the way it is right now, unless some other exception is
being thrown at another point in the download sequence...
dion@multitask.com.au wrote:
>Colin,
>
>I thought I committed a change to the DependencyVerifier and the Project
>class to turn off ignoreErrors?
>--
>dIon Gillard, Multitask Consulting
>Blog: http://www.freeroller.net/page/dion/Weblog
>Work: http://www.multitask.com.au
>
>
>Colin Sampaleanu <co...@exis.com> wrote on 14/02/2003 01:40:16 AM:
>
>
>
>>This is quite possible, since the current code doesn't break the build
>>when a dependency is not found...
>>
>>Ben Walding wrote:
>>
>>
>>
>>>Note that several jars have been removed from the repository (notably
>>>javamail and activation). This is in order to comply with the
>>>licenses. You may now be missing some jars from repository.
>>>
>>>Which platform are you experiencing difficulties with?
>>>
>>>Off hand I can't tell you what problem is with junit report.
>>>Attaching the stack trace may help.
>>>maven -X maven-junit-report-plugin:report
>>>
>>>
>>>With the changelog report, it would pay to have a look at end of
>>>maven.log
>>>just do
>>>maven maven-changelog-plugin:report
>>>to generate the changelog report alone (and then attach the maven.log
>>>for us to see).
>>>
>>>
>>>Age Mooy wrote:
>>>
>>>
>>>
>>>>Is there some kind of migration document available. After installing
>>>>
>>>>
>b8
>
>
>>>>and letting it download all of its dependencies, I ran "maven site"
>>>>
>>>>
>on
>
>
>>>>my current project and got some weird behaviour:
>>>>
>>>>- maven-junit-report-plugin:report fails all unit tests (while
>>>>
>>>>
>test:test
>
>
>>>>has no problems) and then goes into a major stacktrace-producing
>>>>
>>>>
>loop
>
>
>>>>for about 30 seconds before giving up.
>>>>- maven-changelog-plugin:report doesn't find a single change while my
>>>>usual b7 installation finds more than 1000 changes. The activity
>>>>
>>>>
>report
>
>
>>>>is also empty of course.
>>>>
>>>>I assume these things have something to do with the settings in
>>>>project.xml/project.properties.... anyone know how to solve these ?
>>>>
>>>>Age
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>-----Original Message-----
>>>>>From: Kurt Schrader [mailto:kschrader@karmalab.org] Sent: Thursday,
>>>>>February 13, 2003 00:26
>>>>>To: turbine-maven-user@jakarta.apache.org
>>>>>Subject: [ANNOUNCEMENT] Maven Beta-8 Release
>>>>>
>>>>>
>>>>>Maven Beta-8 has been released and can be found here:
>>>>>
>>>>>http://jakarta.apache.org/builds/jakarta-turbine-maven/release
>>>>>
>>>>>
>>>>>
>>>>/1.0-beta-8/
>>>>
>>>>
>>>>
>>>>
>>>>>This release should be considered a mostly feature complete, but not
>>>>>
>>>>>
>
>
>
>>>>>bug free, version of Maven 1.0. The website will be updated over
>>>>>the next few days to reflect the changes in Beta 8. Please help us
>>>>>by upgrading to Beta 8 and reporting any problems that you
>>>>>experience to our bug tracker.
>>>>>
>>>>>Thanks,
>>>>>The Maven Team
>>>>>
>>>>>
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by di...@multitask.com.au.
Colin,
I thought I committed a change to the DependencyVerifier and the Project
class to turn off ignoreErrors?
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
Colin Sampaleanu <co...@exis.com> wrote on 14/02/2003 01:40:16 AM:
> This is quite possible, since the current code doesn't break the build
> when a dependency is not found...
>
> Ben Walding wrote:
>
> > Note that several jars have been removed from the repository (notably
> > javamail and activation). This is in order to comply with the
> > licenses. You may now be missing some jars from repository.
> >
> > Which platform are you experiencing difficulties with?
> >
> > Off hand I can't tell you what problem is with junit report.
> > Attaching the stack trace may help.
> > maven -X maven-junit-report-plugin:report
> >
> >
> > With the changelog report, it would pay to have a look at end of
> > maven.log
> > just do
> > maven maven-changelog-plugin:report
> > to generate the changelog report alone (and then attach the maven.log
> > for us to see).
> >
> >
> > Age Mooy wrote:
> >
> >> Is there some kind of migration document available. After installing
b8
> >> and letting it download all of its dependencies, I ran "maven site"
on
> >> my current project and got some weird behaviour:
> >>
> >> - maven-junit-report-plugin:report fails all unit tests (while
test:test
> >> has no problems) and then goes into a major stacktrace-producing
loop
> >> for about 30 seconds before giving up.
> >> - maven-changelog-plugin:report doesn't find a single change while my
> >> usual b7 installation finds more than 1000 changes. The activity
report
> >> is also empty of course.
> >>
> >> I assume these things have something to do with the settings in
> >> project.xml/project.properties.... anyone know how to solve these ?
> >>
> >> Age
> >>
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: Kurt Schrader [mailto:kschrader@karmalab.org] Sent: Thursday,
> >>> February 13, 2003 00:26
> >>> To: turbine-maven-user@jakarta.apache.org
> >>> Subject: [ANNOUNCEMENT] Maven Beta-8 Release
> >>>
> >>>
> >>> Maven Beta-8 has been released and can be found here:
> >>>
> >>> http://jakarta.apache.org/builds/jakarta-turbine-maven/release
> >>>
> >>
> >> /1.0-beta-8/
> >>
> >>
> >>> This release should be considered a mostly feature complete, but not
> >>> bug free, version of Maven 1.0. The website will be updated over
> >>> the next few days to reflect the changes in Beta 8. Please help us
> >>> by upgrading to Beta 8 and reporting any problems that you
> >>> experience to our bug tracker.
> >>>
> >>> Thanks,
> >>> The Maven Team
> >>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
turbine-maven-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-maven-user-help@jakarta.apache.org
>
> ForwardSourceID:NT000B12FE
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Colin Sampaleanu <co...@exis.com>.
This is quite possible, since the current code doesn't break the build
when a dependency is not found...
Ben Walding wrote:
> Note that several jars have been removed from the repository (notably
> javamail and activation). This is in order to comply with the
> licenses. You may now be missing some jars from repository.
>
> Which platform are you experiencing difficulties with?
>
> Off hand I can't tell you what problem is with junit report.
> Attaching the stack trace may help.
> maven -X maven-junit-report-plugin:report
>
>
> With the changelog report, it would pay to have a look at end of
> maven.log
> just do
> maven maven-changelog-plugin:report
> to generate the changelog report alone (and then attach the maven.log
> for us to see).
>
>
> Age Mooy wrote:
>
>> Is there some kind of migration document available. After installing b8
>> and letting it download all of its dependencies, I ran "maven site" on
>> my current project and got some weird behaviour:
>>
>> - maven-junit-report-plugin:report fails all unit tests (while test:test
>> has no problems) and then goes into a major stacktrace-producing loop
>> for about 30 seconds before giving up.
>> - maven-changelog-plugin:report doesn't find a single change while my
>> usual b7 installation finds more than 1000 changes. The activity report
>> is also empty of course.
>>
>> I assume these things have something to do with the settings in
>> project.xml/project.properties.... anyone know how to solve these ?
>>
>> Age
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: Kurt Schrader [mailto:kschrader@karmalab.org] Sent: Thursday,
>>> February 13, 2003 00:26
>>> To: turbine-maven-user@jakarta.apache.org
>>> Subject: [ANNOUNCEMENT] Maven Beta-8 Release
>>>
>>>
>>> Maven Beta-8 has been released and can be found here:
>>>
>>> http://jakarta.apache.org/builds/jakarta-turbine-maven/release
>>>
>>
>> /1.0-beta-8/
>>
>>
>>> This release should be considered a mostly feature complete, but not
>>> bug free, version of Maven 1.0. The website will be updated over
>>> the next few days to reflect the changes in Beta 8. Please help us
>>> by upgrading to Beta 8 and reporting any problems that you
>>> experience to our bug tracker.
>>>
>>> Thanks,
>>> The Maven Team
>>
maven-b8 junit-report plugin crashes when one or more tests fail.
Posted by Age Mooy <am...@home.nl>.
Hi,
The junit-report plugin that comes with maven-b8 has major problems
processing output from failed unit tests. While the plugin is procesing
the junit xml output into xdocs, I get a long Velocity stacktrace for
each failed test method it encounters. I can reproduce this in all my
projects by simply adding a call to fail() in one of my (normally
successful) unit test methods. One identical stacktrace for each test
method failure.
Here's the snipped version of the stacktrace. I attached the full
console output for a normal run and a -X run as text files
ASTIdentifier : java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException:
java.lang.NullPointerException
at org.apache.velocity.anakia.Escape.getText(Escape.java:81)
at java.lang.reflect.Method.invoke(Native Method)
at
org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.i
nvok
at
org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:56)
at
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:10
6)
at
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:88)
at
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:123)
at
org.apache.commons.jelly.expression.jexl.JexlExpression.evaluate(JexlExp
ress
I get this with
- no velocity jar in the maven/lib dir
- velocity-1.3.jar in the maven/lib dir
- velocity-1.4-dev.jar in the maven/lib dir
OS = win2k
VM = 1.3.1_06
Can anyone reproduce this ?
Age
RE: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Age Mooy <am...@home.nl>.
> Off hand I can't tell you what problem is with junit report.
> Attaching the stack trace may help. maven -X
> maven-junit-report-plugin:report
Addin velocity-1.4-dev.jar to the maven-b8/lib dir solved this one....
it might be a good idea to keep the velocity jar in the distribution for
now...
> With the changelog report, it would pay to have a look at end
> of maven.log just do maven maven-changelog-plugin:report to
> generate the changelog report alone (and then attach the maven.log
> for us to see).
Turns out the latest version of the changelog plugin was a little more
critical about slashes at the end of the repository URI. Thanks for
pointing me at the maven.log.
Age
Re: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Ben Walding <be...@walding.com>.
Note that several jars have been removed from the repository (notably
javamail and activation). This is in order to comply with the
licenses. You may now be missing some jars from repository.
Which platform are you experiencing difficulties with?
Off hand I can't tell you what problem is with junit report.
Attaching the stack trace may help.
maven -X maven-junit-report-plugin:report
With the changelog report, it would pay to have a look at end of maven.log
just do
maven maven-changelog-plugin:report
to generate the changelog report alone (and then attach the maven.log
for us to see).
Age Mooy wrote:
>Is there some kind of migration document available. After installing b8
>and letting it download all of its dependencies, I ran "maven site" on
>my current project and got some weird behaviour:
>
>- maven-junit-report-plugin:report fails all unit tests (while test:test
>has no problems) and then goes into a major stacktrace-producing loop
>for about 30 seconds before giving up.
>- maven-changelog-plugin:report doesn't find a single change while my
>usual b7 installation finds more than 1000 changes. The activity report
>is also empty of course.
>
>I assume these things have something to do with the settings in
>project.xml/project.properties.... anyone know how to solve these ?
>
>Age
>
>
>
>
>>-----Original Message-----
>>From: Kurt Schrader [mailto:kschrader@karmalab.org]
>>Sent: Thursday, February 13, 2003 00:26
>>To: turbine-maven-user@jakarta.apache.org
>>Subject: [ANNOUNCEMENT] Maven Beta-8 Release
>>
>>
>>Maven Beta-8 has been released and can be found here:
>>
>>http://jakarta.apache.org/builds/jakarta-turbine-maven/release
>>
>>
>/1.0-beta-8/
>
>
>>This release should be considered a mostly feature complete,
>>but not bug free, version of Maven 1.0. The website will be
>>updated over the next few days to reflect the changes in Beta
>>8. Please help us by upgrading to Beta 8 and reporting any
>>problems that you experience to our bug tracker.
>>
>>Thanks,
>>The Maven Team
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail:
>>turbine-maven-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail:
>>turbine-maven-user-help@jakarta.apache.org
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-maven-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-maven-user-help@jakarta.apache.org
>
>
>
>
RE: [ANNOUNCEMENT] Maven Beta-8 Release
Posted by Age Mooy <am...@home.nl>.
Is there some kind of migration document available. After installing b8
and letting it download all of its dependencies, I ran "maven site" on
my current project and got some weird behaviour:
- maven-junit-report-plugin:report fails all unit tests (while test:test
has no problems) and then goes into a major stacktrace-producing loop
for about 30 seconds before giving up.
- maven-changelog-plugin:report doesn't find a single change while my
usual b7 installation finds more than 1000 changes. The activity report
is also empty of course.
I assume these things have something to do with the settings in
project.xml/project.properties.... anyone know how to solve these ?
Age
> -----Original Message-----
> From: Kurt Schrader [mailto:kschrader@karmalab.org]
> Sent: Thursday, February 13, 2003 00:26
> To: turbine-maven-user@jakarta.apache.org
> Subject: [ANNOUNCEMENT] Maven Beta-8 Release
>
>
> Maven Beta-8 has been released and can be found here:
>
> http://jakarta.apache.org/builds/jakarta-turbine-maven/release
/1.0-beta-8/
>
> This release should be considered a mostly feature complete,
> but not bug free, version of Maven 1.0. The website will be
> updated over the next few days to reflect the changes in Beta
> 8. Please help us by upgrading to Beta 8 and reporting any
> problems that you experience to our bug tracker.
>
> Thanks,
> The Maven Team
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> turbine-maven-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> turbine-maven-user-help@jakarta.apache.org
>