On Fri, Jul 18, 2008 at 6:00 AM, Jason van Zyl [EMAIL PROTECTED] wrote:
They are not being shared. Hudson is running as a sand-boxed user where I
have setup my credentials, so that the releases can be fully automated where
the same set of attributes are used across the board. I tested my
On 20-Jul-08, at 9:42 PM, Wendy Smoak wrote:
On Fri, Jul 18, 2008 at 6:00 AM, Jason van Zyl [EMAIL PROTECTED]
wrote:
They are not being shared. Hudson is running as a sand-boxed user
where I
have setup my credentials, so that the releases can be fully
automated where
the same set of
On 18/07/2008, at 11:54 PM, Jason van Zyl wrote:
I am actually trying to work with a developer who knows Hudson very
well to create a better bridge from Maven and Hudson. Basically
using Maven SCM (instead of the proliferation of Hudson plugins
doing exactly the same thing), creating a
On 20-Jul-08, at 10:13 PM, Brett Porter wrote:
On 18/07/2008, at 11:54 PM, Jason van Zyl wrote:
I am actually trying to work with a developer who knows Hudson very
well to create a better bridge from Maven and Hudson. Basically
using Maven SCM (instead of the proliferation of Hudson
On 21/07/2008, at 12:20 PM, Jason van Zyl wrote:
The important thing is that the release process does not use your
credentials for either SVN or SSH when it's not you doing the
release.
I don't think that's important at all, but I can easily fix it.
Do I have to SSH into your account
On Sun, Jul 20, 2008 at 7:12 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
On 20-Jul-08, at 9:42 PM, Wendy Smoak wrote:
Yes. The svn commits need to show the person who actually made the
change to svn.
I can fix that, is that the only problem?
No, but I think Brett has it covered. :)
--
On 17-Jul-08, at 11:12 PM, Wendy Smoak wrote:
I gather this is the reason that the commits (r677787 to r677789) for
the Maven Artifact release that Oleg just called a vote on look like
they were done by Jason?
I'm really not comfortable with svn credentials being shared like
that.
They
On Fri, Jul 18, 2008 at 3:00 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
On 17-Jul-08, at 11:12 PM, Wendy Smoak wrote:
I gather this is the reason that the commits (r677787 to r677789) for
the Maven Artifact release that Oleg just called a vote on look like
they were done by Jason?
I'm
I'm not saying there is only one developer, the core group just
represents the group doing the majority of the work in a time period.
That graph was the last few months in your new location.
It's just the natural evolution of projects.
I am actually trying to work with a developer who knows
ok, I prefer when it is explain like that.
It's a good thing to try to reuse existing librairies and plugins
Emmanuel
On Fri, Jul 18, 2008 at 3:54 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
I'm not saying there is only one developer, the core group just represents
the group doing the
I gather this is the reason that the commits (r677787 to r677789) for
the Maven Artifact release that Oleg just called a vote on look like
they were done by Jason?
I'm really not comfortable with svn credentials being shared like that.
FWIW, Continuum lets you enter your svn credentials when you
I tried to build the latest maven 2.1 from trunk with mvn install but
it still failed in tests.
What should be done to get a build of maven 2.1 ?
I need it to track a classloader issue with jaxws-maven-plugin even if
it seems to be a general problem with the system scope.
Regards and thanks for
Henri,
Here's the most recent build:
http://ci.sonatype.org/view/Maven%202.1x/job/maven-2.1.x-bootstrap/ws/trunk/maven-distribution/target/
On 10-Jul-08, at 10:02 AM, Henri Gomez wrote:
I tried to build the latest maven 2.1 from trunk with mvn install but
it still failed in tests.
What
Well
I 'll put your maven 2.1 build to our Hudson instance :)
2008/7/10 Jason van Zyl [EMAIL PROTECTED]:
Henri,
Here's the most recent build:
http://ci.sonatype.org/view/Maven%202.1x/job/maven-2.1.x-bootstrap/ws/trunk/maven-distribution/target/
On 10-Jul-08, at 10:02 AM, Henri Gomez
If you have 2.0.x installed you need to bootstrap.
It builds fine for me now with 2.0.9, we've never needed to bootstrap to
build 2.1 before, so what's different now?
If we can't trust Maven to build our own applications here, then we have
a serious problem IMO that needs to be fixed. Maven 2.1
It builds fine for me now with 2.0.9, we've never needed to bootstrap to
build 2.1 before, so what's different now?
You got it works with 2.0.9 ?
Just with mvn install ?
If we can't trust Maven to build our own applications here, then we have
a serious problem IMO that needs to be fixed.
On 10-Jul-08, at 11:01 AM, Brian E. Fox wrote:
If you have 2.0.x installed you need to bootstrap.
It builds fine for me now with 2.0.9, we've never needed to
bootstrap to
build 2.1 before, so what's different now?
If you ever change APIs where the JARs in the distribution come first
It builds fine for me now with 2.0.9, we've never needed to bootstrap
to
build 2.1 before, so what's different now?
You got it works with 2.0.9 ?
Yes.
Just with mvn install ?
Yes.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
I always bootstrap.
On 10-Jul-08, at 11:12 AM, Henri Gomez wrote:
It builds fine for me now with 2.0.9, we've never needed to
bootstrap to
build 2.1 before, so what's different now?
You got it works with 2.0.9 ?
Just with mvn install ?
If we can't trust Maven to build our own
It builds fine for me now with 2.0.9, we've never needed to
bootstrap to
build 2.1 before, so what's different now?
If you ever change APIs where the JARs in the distribution come first
on the classpath you need to start from scratch. Most of the time we
don't do that so it never
On 8-Jul-08, at 12:19 AM, Brett Porter wrote:
On 08/07/2008, at 1:47 AM, John Casey wrote:
Jason's referring to a ruby script I wrote to lookup the version
string for a particular staged project, for use in the stage:copy
mojo. This allows us to setup generic promotion scripts in a CI
On Mon, Jul 7, 2008 at 5:47 PM, John Casey [EMAIL PROTECTED] wrote:
Jason van Zyl wrote:
There are groups there for Maven 2.1, Plexus, Maven IDE (really embedder
consumers), and I will also limit the plugins to the default lifecycles of
the commonly used packagings like JAR, and WAR. John
Is the code anywhere?
I'm interested in the process, but have gone down the Drools workflow
way, and I'm trying to work on the promotion from Nexus. But I'll
definitely take a look at code.
On 8-Jul-08, at 3:40 PM, Tom Huybrechts wrote:
On Mon, Jul 7, 2008 at 5:47 PM, John Casey [EMAIL
There's a setup section on the wiki page which has the necessary info
on setting up Hudson.
The staging plugin is part of the 'tom' branch which is linked to from the page.
On Tue, Jul 8, 2008 at 9:59 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
Is the code anywhere?
I'm interested in the
Jason van Zyl wrote:
There are groups there for Maven 2.1, Plexus, Maven IDE (really
embedder consumers), and I will also limit the plugins to the default
lifecycles of the commonly used packagings like JAR, and WAR. John has
also started creating automated ways to release to stage, and
On 08/07/2008, at 1:47 AM, John Casey wrote:
Jason's referring to a ruby script I wrote to lookup the version
string for a particular staged project, for use in the stage:copy
mojo. This allows us to setup generic promotion scripts in a CI
environment like Hudson. I've committed this
On 06/07/2008, at 3:56 AM, Jason van Zyl wrote:
I am also working with the Apache Infrastructure team to integrate
the Contegix folks who are the ones who currently host all the
hardware we're using. Maven's central repository, our Hudson
instance, and our Nexus instance. So, in short
On 6-Jul-08, at 10:08 AM, Brett Porter wrote:
On 06/07/2008, at 3:56 AM, Jason van Zyl wrote:
I am also working with the Apache Infrastructure team to integrate
the Contegix folks who are the ones who currently host all the
hardware we're using. Maven's central repository, our Hudson
I have put together a visual of the system, some information on using
m2eclipse to debug the entire platform, and the use of Hudson for
testing the resulting system.
http://docs.codehaus.org/display/MAVEN/Developing+Maven+2.1
The guide included there (put together by Igor) should allow
29 matches
Mail list logo
