On 05/10/2008, at 6:51 AM, [EMAIL PROTECTED] wrote:
Author: jvanzyl
Date: Sat Oct 4 12:51:42 2008
New Revision: 701702
URL: http://svn.apache.org/viewvc?rev=701702&view=rev
Log:
o revert my ordering, i'll have to investigate why property set on
the CLI which conflicts with an internal prope
I think it already makes sense to put the default generation of the
resource into the lifecycles for 2.1 - 3.0... it should have no
adverse affect even though the JAR plugin bundles a different once
since the content is the same. A future release of the JAR plugin can
check for it's existen
Cool. It sounds like one of those things people would use more if they
knew it existed.
In the long run, what do you think about unifying it's handling of the
POM with the release plugin?
On 07/10/2008, at 5:22 AM, Jesse McConnell wrote:
hi all,
A long while back I added a plugin into th
Sorry, I mistranslated my notes and missed the most important thing -
the POMs still contain references to 1.0.0-alpha-1-SNAPSHOT properties
as well.
- Brett
On 07/10/2008, at 3:39 PM, Brett Porter wrote:
The current release artifacts have a number of problems. At first
glance:
- the SCM
On 04/10/2008, at 1:41 AM, Oleg Gusakov wrote:
James,
James William Dumay wrote:
Hey Oleg,
Curious, will the Mecury wagon provider be the new handler for the
dav:
protocol extension?
Yes - Mercury replaces a dav protocol wagon handler if this is the
question.
It does not claim to hand
The current release artifacts have a number of problems. At first
glance:
- the SCM will be pinned to the sandbox, one reason we generally
promote first, then release.
- the POMs still contain references to sonatype repositories
- I don't think mercury-it can be released due to GPL dependencie
+1
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 07, 2008 12:05 AM
To: Maven Developers List
Subject: Re: [VOTE] release and promote Mercury 1.0.0-alpha-1
+1
On 4-Oct-08, at 1:02 AM, Oleg Gusakov wrote:
> I open this vote to release mercury 1.0
+1
On 4-Oct-08, at 1:02 AM, Oleg Gusakov wrote:
I open this vote to release mercury 1.0.0-alpha-1 and promote it out
of sandbox, so that we can start using the transport piece - mercury
wagon - right away.
For the past several months a group of some 5 community members has
been working o
James William Dumay wrote:
Very cool :) - Can't wait to try this out.
You can - right away :) I opened a vote to promote it - subject "[VOTE]
release and promote Mercury 1.0.0-alpha-1" and attached maven 2.1-M2-SN
binary bundle for folks to try it out.
I myself am using this version si
Oleg,
On Fri, 2008-10-03 at 08:41 -0700, Oleg Gusakov wrote:
> Yes - Mercury replaces a dav protocol wagon handler if this is the
> question.
>
> It does not claim to handle entire DAV protocol, including
> versioning,
> etc. It implements a subset that allows to PUT resources to the
> server:
Cheers...
I'd just finished getting update-child-modules (which fixes when the
child modules are out of sync and you cannot build) working this
morning when we found that a big build with 40+ modules had fallen out
of sync...
serendipity strikes ;-)
I'll have to push another alpha once I get all
ya, I am aware of that one...it does some awesome stuff but totally
unrelated to the use case I had need for originally and recently..
jesse
On Mon, Oct 6, 2008 at 3:16 PM, Stephen Connolly
<[EMAIL PROTECTED]> wrote:
> FYI, we've also go the versions-maven-plugin over on mojo for
> manipulating v
FYI, we've also go the versions-maven-plugin over on mojo for
manipulating version related stuff
2008/10/6 John Casey <[EMAIL PROTECTED]>:
> I think this is a great idea, especially if it can process a reactor full of
> POMs, and handle multiple xpaths where a target value might show up (the
> set
I think this is a great idea, especially if it can process a reactor
full of POMs, and handle multiple xpaths where a target value might show
up (the set:
{project/parent/version,
project/version,
project/properties/mavenVersion}
would be one good first use case, for instance). I've got a plug
hi all,
A long while back I added a plugin into the maven sandbox for
modifying one or more pom files in the process of the build, not the
active pom's in a reactor but at least in instances where you had a
scm checkout process in your build and needed to modify the checked
out project before buil
I have already seen suggested to register your CI to the notification mails.
Gilles
2008/10/6 Jamie Whitehouse <[EMAIL PROTECTED]>:
> On Fri, 2008-10-03 at 23:31 +0200, Arnaud HERITIER wrote:
>
>> you're right there's no need to poll scm. There no tests, nor integration to
>> do.
>> I just kept d
We can ask to apache infra team but I'm not sure it is possible because our
integration server is outside the apache infra.
On Mon, Oct 6, 2008 at 3:11 PM, Jamie Whitehouse <
[EMAIL PROTECTED]> wrote:
> On Fri, 2008-10-03 at 23:31 +0200, Arnaud HERITIER wrote:
>
> > you're right there's no need
On Fri, 2008-10-03 at 23:31 +0200, Arnaud HERITIER wrote:
> you're right there's no need to poll scm. There no tests, nor integration to
> do.
> I just kept daily schedule
>
> About version control polling rules @ Apache it's a little bit annoying. An
> integration cycle launched every hour is no
Verify/change folder permissions to 0775 and files permissions to 0664 i.e.:
find . -type d -exec chmod a+rx {} \;
find . -type d -exec chmod g+w {} \;
find . -type f -exec chmod 664 {} \;
Can't this be replaced with
chmod -R a+rX,g+w,o-w /www/maven.apache.org/plugins/maven-XXX-plugin-Y.Z
-
Hi,
This is mainly a release to upgrade the version of Ant to 1.7.1
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14447&styleName=Html&projectId=11125&Create=Create
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11125
+1
Olivier Lamy wrote:
Hi,
In preparation of resources plugin, I'd like to release the shared
library maven-filtering version 1.0-beta-2.
We solved 6 issues :
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14488&styleName=Html&projectId=11761&Create=Create
Staging repo:
http://people.
On Tue, Mar 18, 2008 at 9:11 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> The problem is that the site-stage mojo doesn't set my user's name and
> the one @ apache is different from the one on my laptop.
> I updated the doc.
I'm having the same problem.
I'm not sure site:stage-deploy is using
22 matches
Mail list logo
