Re: [Vote] Release Doxia-1.1.1 and Doxia-Sitetools-1.1.1 (take two)
Benjamin Bentmann wrote: Lukas Theussl wrote: Staging repos: https://repository.apache.org/content/repositories/maven-staging-019/ https://repository.apache.org/content/repositories/maven-staging-020/ +1 in general, only the signatures for the POMs would need to be double-checked and fixed. This release was apparently made with Maven 2.1.0 and hence POMs like doxia-1.1.1.pom and doxia-sitetools-1.1.1.pom suffer from MGPG-14. The signatures are wrong indeed, thanks for spotting this. I believe this can be fixed on the repo side so I don't want to stop the release just yet unless I can't find anybody (Brian?) to fix it, or it's deemed too much hassle or anybody has another objection. This release provides source-release packages for each individual sub module. Is that a strict requirement by ASF policy or didn't we conclude that a single source-release for the root project would be sufficient? As I understand, it's not necessary but doesn't hurt. I won't do it next time anymore though as it's just unnecessary overhead. I also think that one source bundle for the top-parent artifact, where everything can be built from, should be enough. Thanks, -Lukas Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CANCELED] [VOTE] Maven 2.2.0 (Second Attempt)
done. I'll finish up the log4j stuff this morning and hopefully have a new RC out for testing this afternoon. Benjamin Bentmann wrote: John Casey wrote: Okay, I'm retracting this vote to fix: MNG-4210 MNG-4213 As a suggestion, probably worth to consider merging MNG-4179 in from the 2.2.x branch as well. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Maven 2.2.0 (Second Attempt)
I've added this sort of configuration, but I need to document it. I've got a proposed next release of wagon staged, and as soon as I get the documentation for this configuration done, I'll call the vote. -john Brett Porter wrote: On 20/06/2009, at 2:29 AM, Brian Fox wrote: This is probably a rare situation but does present itself like a regression. On the flip side, I would love to be able to enable pre-emptive authentication but I would want to do it per server. This would have the effect of halving the requests and upload data for authenticated servers, but we shouldn't do it by default. If this is added as a configuration parameter of the HTTP wagon in the next release it'll be configurable per-server. - Brett - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Maven 2.2.0 (Second Attempt)
Just as a side note, I don't thing the wiki page http://docs.codehaus.org/display/MAVEN/Maven+2.2.0+Release+Plan is up to date with current release candidate, is it ? Nicolas 2009/6/22 John Casey jdca...@commonjava.org I've added this sort of configuration, but I need to document it. I've got a proposed next release of wagon staged, and as soon as I get the documentation for this configuration done, I'll call the vote. -john Brett Porter wrote: On 20/06/2009, at 2:29 AM, Brian Fox wrote: This is probably a rare situation but does present itself like a regression. On the flip side, I would love to be able to enable pre-emptive authentication but I would want to do it per server. This would have the effect of halving the requests and upload data for authenticated servers, but we shouldn't do it by default. If this is added as a configuration parameter of the HTTP wagon in the next release it'll be configurable per-server. - Brett - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[PLEASE TEST] Maven 2.2.0-RC4 Maven Wagon 1.0-beta-6
Hi everyone, As I'm sure you're aware, I've tried twice now to get a clean vote done for Maven 2.2.0. In each case, we've run into blocking bugs that have caused me to retract the vote and fix the code. Well, with the latest bug that Brian found, we're now dependent on some configuration updates that are available on the trunk of Maven Wagon. I've added configuration for the non-lightweight http wagon to address: WAGON-270 - preemptive auth in non-lightweight http wagon causes Unauthorized responses from some servers WAGON-264 - compressed tarball download problems WAGON-271 - Provide configurability of httpclient parameters to allow user to tell Maven to ignore cookies The top issue relates to Brian's problem, and the bottom issue relates to MNG-4165, which is also in the release notes for Maven 2.2.0. The middle issue was a side-effect of fixing the other two. I'd like to have as many eyes on this release candidate as I can get. I'm doing another RC instead of a new vote thread because I don't want to push it too much and wind up with a profusion of different artifacts in people's local repositories marked as being part of Maven 2.2.0 when they are really part of failed votes for 2.2.0... Once I'm confident this RC is good to go, I'll call votes for both Wagon 1.0-beta-6 and Maven 2.2.0. You can find the staging repositories here: Wagon: https://repository.apache.org/content/repositories/maven-staging-002/ Maven 2.2.0-RC4: https://repository.apache.org/content/repositories/maven-staging-006/ You can find release notes here: Wagon: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335styleName=Htmlversion=15403 Maven: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=15103 Please give these a try, and let me know what you find! Thanks, -john --- John Casey Developer and PMC Member, Apache Maven (http://maven.apache.org) Member, Apache Software Foundation What we have to learn to do, we learn by doing. -Aristotle - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Maven 2.2.0-RC4 Maven Wagon 1.0-beta-6
Ugh, that Maven repository location is wrong. I'm re-staging this RC, and I'll post the staging repository once that's done. Sorry for the confusion. -john John Casey wrote: Hi everyone, As I'm sure you're aware, I've tried twice now to get a clean vote done for Maven 2.2.0. In each case, we've run into blocking bugs that have caused me to retract the vote and fix the code. Well, with the latest bug that Brian found, we're now dependent on some configuration updates that are available on the trunk of Maven Wagon. I've added configuration for the non-lightweight http wagon to address: WAGON-270 - preemptive auth in non-lightweight http wagon causes Unauthorized responses from some servers WAGON-264 - compressed tarball download problems WAGON-271 - Provide configurability of httpclient parameters to allow user to tell Maven to ignore cookies The top issue relates to Brian's problem, and the bottom issue relates to MNG-4165, which is also in the release notes for Maven 2.2.0. The middle issue was a side-effect of fixing the other two. I'd like to have as many eyes on this release candidate as I can get. I'm doing another RC instead of a new vote thread because I don't want to push it too much and wind up with a profusion of different artifacts in people's local repositories marked as being part of Maven 2.2.0 when they are really part of failed votes for 2.2.0... Once I'm confident this RC is good to go, I'll call votes for both Wagon 1.0-beta-6 and Maven 2.2.0. You can find the staging repositories here: Wagon: https://repository.apache.org/content/repositories/maven-staging-002/ Maven 2.2.0-RC4: https://repository.apache.org/content/repositories/maven-staging-006/ You can find release notes here: Wagon: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335styleName=Htmlversion=15403 Maven: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=15103 Please give these a try, and let me know what you find! Thanks, -john --- John Casey Developer and PMC Member, Apache Maven (http://maven.apache.org) Member, Apache Software Foundation What we have to learn to do, we learn by doing. -Aristotle - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
maven-eclipse-plugin failing on hudson - help needed.
This builds fine on my machine (windows xp) and on people.apache.org. I dont know why this is failing on hudson. I do not have ANT on my path for either of the machines that build successfully - that is why the dependencies are included in the antrun plugin configuration. Could I ask for some more devs to checkout and install with -Prun-its and see that it works on their environment. And if by chance someone knows what the problems is please let me know. === pom.xml plugin def === plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-antrun-plugin/artifactId executions execution idverify-integration-tests-checks/id phasepost-integration-test/phase configuration tasks script language=beanshell src=verify-integration-tests-checks.bsh / /tasks /configuration goals goalrun/goal /goals /execution /executions dependencies dependency groupIdorg.apache.ant/groupId artifactIdant-nodeps/artifactId version1.7.1/version /dependency dependency groupIdorg.apache.ant/groupId artifactIdant-apache-bsf/artifactId version1.7.1/version /dependency dependency groupIdorg.beanshell/groupId artifactIdbsh/artifactId version2.0b4/version /dependency /dependencies /plugin === hudson console output === org.apache.maven.lifecycle.LifecycleExecutionException: An Ant BuildException has occured: file verify-integration-tests-checks.bsh not found. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:585) 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: org.apache.maven.plugin.MojoExecutionException: An Ant BuildException has occured: file verify-integration-tests-checks.bsh not found. at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:131) at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:98) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) ... 16 more Caused by: file verify-integration-tests-checks.bsh not found. at org.apache.tools.ant.util.ScriptRunnerBase.setSrc(ScriptRunnerBase.java:197) at org.apache.tools.ant.util.ScriptRunnerHelper.getScriptRunner(ScriptRunnerHelper.java:57) at org.apache.tools.ant.taskdefs.optional.Script.execute(Script.java:52) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) 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:585) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:118) ... 19 more - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional
Re: [PLEASE TEST] Maven 2.2.0-RC4 Maven Wagon 1.0-beta-6
Okay, the correct staging repository URL for Maven 2.2.0-RC4 is: https://repository.apache.org/content/repositories/maven-staging-007/ Remember, this version contains the staged version of Wagon 1.0-beta-6. Thanks, -john John Casey wrote: Ugh, that Maven repository location is wrong. I'm re-staging this RC, and I'll post the staging repository once that's done. Sorry for the confusion. -john John Casey wrote: Hi everyone, As I'm sure you're aware, I've tried twice now to get a clean vote done for Maven 2.2.0. In each case, we've run into blocking bugs that have caused me to retract the vote and fix the code. Well, with the latest bug that Brian found, we're now dependent on some configuration updates that are available on the trunk of Maven Wagon. I've added configuration for the non-lightweight http wagon to address: WAGON-270 - preemptive auth in non-lightweight http wagon causes Unauthorized responses from some servers WAGON-264 - compressed tarball download problems WAGON-271 - Provide configurability of httpclient parameters to allow user to tell Maven to ignore cookies The top issue relates to Brian's problem, and the bottom issue relates to MNG-4165, which is also in the release notes for Maven 2.2.0. The middle issue was a side-effect of fixing the other two. I'd like to have as many eyes on this release candidate as I can get. I'm doing another RC instead of a new vote thread because I don't want to push it too much and wind up with a profusion of different artifacts in people's local repositories marked as being part of Maven 2.2.0 when they are really part of failed votes for 2.2.0... Once I'm confident this RC is good to go, I'll call votes for both Wagon 1.0-beta-6 and Maven 2.2.0. You can find the staging repositories here: Wagon: https://repository.apache.org/content/repositories/maven-staging-002/ Maven 2.2.0-RC4: https://repository.apache.org/content/repositories/maven-staging-006/ You can find release notes here: Wagon: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335styleName=Htmlversion=15403 Maven: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=15103 Please give these a try, and let me know what you find! Thanks, -john --- John Casey Developer and PMC Member, Apache Maven (http://maven.apache.org) Member, Apache Software Foundation What we have to learn to do, we learn by doing. -Aristotle - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-eclipse-plugin failing on hudson - help needed.
This would seem to be the result of some path that's taken for granted
to be a certain way, but for some reason is different out on hudson.
Have you tried to echo.. the path from the antrun plugin, or else use
an absolute path like:
${project.basedir}/verify-integration-tests-checks.bsh
Just a few ideas...
-john
Barrie Treloar wrote:
This builds fine on my machine (windows xp) and on people.apache.org.
I dont know why this is failing on hudson. I do not have ANT on my
path for either of the machines that build successfully - that is why
the dependencies are included in the antrun plugin configuration.
Could I ask for some more devs to checkout and install with -Prun-its
and see that it works on their environment.
And if by chance someone knows what the problems is please let me know.
=== pom.xml plugin def ===
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idverify-integration-tests-checks/id
phasepost-integration-test/phase
configuration
tasks
script language=beanshell
src=verify-integration-tests-checks.bsh /
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdorg.apache.ant/groupId
artifactIdant-nodeps/artifactId
version1.7.1/version
/dependency
dependency
groupIdorg.apache.ant/groupId
artifactIdant-apache-bsf/artifactId
version1.7.1/version
/dependency
dependency
groupIdorg.beanshell/groupId
artifactIdbsh/artifactId
version2.0b4/version
/dependency
/dependencies
/plugin
=== hudson console output ===
org.apache.maven.lifecycle.LifecycleExecutionException: An Ant
BuildException has occured: file verify-integration-tests-checks.bsh
not found.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
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:585)
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: org.apache.maven.plugin.MojoExecutionException: An Ant
BuildException has occured: file verify-integration-tests-checks.bsh
not found.
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:131)
at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:98)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
... 16 more
Caused by: file verify-integration-tests-checks.bsh not found.
at
org.apache.tools.ant.util.ScriptRunnerBase.setSrc(ScriptRunnerBase.java:197)
at
org.apache.tools.ant.util.ScriptRunnerHelper.getScriptRunner(ScriptRunnerHelper.java:57)
at org.apache.tools.ant.taskdefs.optional.Script.execute(Script.java:52)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
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:585)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at
Re: maven-eclipse-plugin failing on hudson - help needed.
You might try adding ${basedir} into the src attribute, but strange
that it would try to run anywhere but the current directory. I assume
that that file is properly checked out, which you should be able to
check in Hudson.
FTR, it runs fine on my machine too (Mac).
- Brett
On 23/06/2009, at 10:44 AM, John Casey wrote:
This would seem to be the result of some path that's taken for
granted to be a certain way, but for some reason is different out on
hudson.
Have you tried to echo.. the path from the antrun plugin, or else
use an absolute path like:
${project.basedir}/verify-integration-tests-checks.bsh
Just a few ideas...
-john
Barrie Treloar wrote:
This builds fine on my machine (windows xp) and on people.apache.org.
I dont know why this is failing on hudson. I do not have ANT on my
path for either of the machines that build successfully - that is why
the dependencies are included in the antrun plugin configuration.
Could I ask for some more devs to checkout and install with -Prun-its
and see that it works on their environment.
And if by chance someone knows what the problems is please let me
know.
=== pom.xml plugin def ===
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idverify-integration-tests-checks/id
phasepost-integration-test/phase
configuration
tasks
script language=beanshell
src=verify-integration-tests-checks.bsh /
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdorg.apache.ant/groupId
artifactIdant-nodeps/artifactId
version1.7.1/version
/dependency
dependency
groupIdorg.apache.ant/groupId
artifactIdant-apache-bsf/artifactId
version1.7.1/version
/dependency
dependency
groupIdorg.beanshell/groupId
artifactIdbsh/artifactId
version2.0b4/version
/dependency
/dependencies
/plugin
=== hudson console output ===
org.apache.maven.lifecycle.LifecycleExecutionException: An Ant
BuildException has occured: file verify-integration-tests-checks.bsh
not found.
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor
.executeGoals(DefaultLifecycleExecutor.java:703)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor
.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:
519)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor
.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor
.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
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:585)
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: org.apache.maven.plugin.MojoExecutionException: An Ant
BuildException has occured: file verify-integration-tests-checks.bsh
not found.
at
org
.apache
.maven
.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:131)
at
org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:98)
at
org
.apache
.maven
.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:
483)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor
.executeGoals(DefaultLifecycleExecutor.java:678)
... 16 more
Caused by: file verify-integration-tests-checks.bsh not found.
at
org
.apache
.tools.ant.util.ScriptRunnerBase.setSrc(ScriptRunnerBase.java:197)
at
org
.apache
.tools
.ant
.util.ScriptRunnerHelper.getScriptRunner(ScriptRunnerHelper.java:57)
at
org.apache.tools.ant.taskdefs.optional.Script.execute(Script.java:52)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at
Re: [PLEASE TEST] Maven 2.2.0-RC4 Maven Wagon 1.0-beta-6
I'll try and get some time to look through these, as I have some questions from what I've seen at a glance. It looks like you need to temporarily add the Wagon staging repo to the POM so that the hudson build will succeed though. - Brett On 23/06/2009, at 10:03 AM, John Casey wrote: Hi everyone, As I'm sure you're aware, I've tried twice now to get a clean vote done for Maven 2.2.0. In each case, we've run into blocking bugs that have caused me to retract the vote and fix the code. Well, with the latest bug that Brian found, we're now dependent on some configuration updates that are available on the trunk of Maven Wagon. I've added configuration for the non-lightweight http wagon to address: WAGON-270 - preemptive auth in non-lightweight http wagon causes Unauthorized responses from some servers WAGON-264 - compressed tarball download problems WAGON-271 - Provide configurability of httpclient parameters to allow user to tell Maven to ignore cookies The top issue relates to Brian's problem, and the bottom issue relates to MNG-4165, which is also in the release notes for Maven 2.2.0. The middle issue was a side-effect of fixing the other two. I'd like to have as many eyes on this release candidate as I can get. I'm doing another RC instead of a new vote thread because I don't want to push it too much and wind up with a profusion of different artifacts in people's local repositories marked as being part of Maven 2.2.0 when they are really part of failed votes for 2.2.0... Once I'm confident this RC is good to go, I'll call votes for both Wagon 1.0-beta-6 and Maven 2.2.0. You can find the staging repositories here: Wagon: https://repository.apache.org/content/repositories/maven-staging-002/ Maven 2.2.0-RC4: https://repository.apache.org/content/repositories/maven-staging-006/ You can find release notes here: Wagon: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335styleName=Htmlversion=15403 Maven: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=15103 Please give these a try, and let me know what you find! Thanks, -john --- John Casey Developer and PMC Member, Apache Maven (http://maven.apache.org) Member, Apache Software Foundation What we have to learn to do, we learn by doing. -Aristotle - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-eclipse-plugin failing on hudson - help needed.
On Tue, Jun 23, 2009 at 10:14 AM, John Caseyjdca...@commonjava.org wrote:
This would seem to be the result of some path that's taken for granted to be
a certain way, but for some reason is different out on hudson.
Have you tried to echo.. the path from the antrun plugin, or else use an
absolute path like:
${project.basedir}/verify-integration-tests-checks.bsh
Just a few ideas...
Thanks, they should help me.
I'm reluctant to add ${project.basedir} as I suspect that the other
file I am sourcing will need basedir too.
Oh well, if it does I can hack around that.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-eclipse-plugin failing on hudson - help needed.
On Tue, Jun 23, 2009 at 1:46 PM, Barrie Treloarbaerr...@gmail.com wrote:
On Tue, Jun 23, 2009 at 10:14 AM, John Caseyjdca...@commonjava.org wrote:
This would seem to be the result of some path that's taken for granted to be
a certain way, but for some reason is different out on hudson.
Have you tried to echo.. the path from the antrun plugin, or else use an
absolute path like:
${project.basedir}/verify-integration-tests-checks.bsh
Just a few ideas...
Thanks, they should help me.
I'm reluctant to add ${project.basedir} as I suspect that the other
file I am sourcing will need basedir too.
Oh well, if it does I can hack around that.
[echo] cwd =
/home/hudson/workspace/plugins-CI-with-maven-2.1.x/jdk/1.5/label/ubuntu/trunk/maven-eclipse-plugin
Which makes me go hmm why can't it find the file then.
Its in the workspace
https://grid.sonatype.org/ci/job/plugins-CI-with-maven-2.1.x/jdk=1.5,label=ubuntu/ws/trunk/maven-eclipse-plugin/
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
