On Tue, Jun 23, 2009 at 1:46 PM, Barrie Treloar wrote:
> On Tue, Jun 23, 2009 at 10:14 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 the path from the a
On Tue, Jun 23, 2009 at 10:14 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 the path from the antrun plugin, or else use an
> absolute path like:
>
> ${proj
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 e
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,
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 the path from the antrun plugin, or else use
an absolute path like:
${project.basedir}/verify-integration-tests-checks.bsh
Just a few
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-s
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 mor
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, w
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 upd
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
> I've added this sort of configuration, but I need to document it. I've got
> a proposed next relea
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
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
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
13 matches
Mail list logo
