The vote has passed with the following result :
+6 (binding): Jason, Brian, Jesse, Olivier, Arnaud, Herve
+1 (non binding): Oleg
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail: dev-unsubscr...@mav
Benjamin,
I might have messed up: promotion refused to cooperate and I remember
manually supplying password for each single artifact. PGP sigs were OK,
so I did not look at other checksums. I cannot pinpoint the exact
reason, and - given the new Nexus-based process, I doubt it will happen
aga
Herve,
I'd like to move it into it's own project in the future, as well as
mercury ITs
Thanks,
Oleg
Hervé BOUTEMY wrote:
+1 (coding style, even if important, doesn't deserve a -1 at this point)
mercury-ant-tasks is not part of the staged artifacts (not included in the
reactor): do you inte
Yep, I'll double check it before I call the vote and push the site
(probably tonight or tomorrow) and update it appropriately.
-Original Message-
From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com]
On Behalf Of Paul Benedict
Sent: Saturday, February 14, 2009 3:51 PM
To:
If the --showVersion patch wasn't applied to 2.0.10, can someone
check? I'd like to bump the ticket to 2.0.11 so it does not appear in
this version's release notes before it gets published.
Paul
On Sat, Feb 14, 2009 at 7:03 AM, Brett Porter wrote:
> ++1
>
> I ran the integration tests as confirm
On 14-Feb-09, at 12:25 PM, Benjamin Bentmann wrote:
Hi,
from trunk's DefaultMavenExecutionRequestPopulator:
snapshots
.setChecksumPolicy( ArtifactRepositoryPolicy.UPDATE_POLICY_DAILY );
snapshots
.setUpdatePolicy( ArtifactRepositoryPolicy.CHECKSUM_POLICY_WARN );
And, who spotted the typo a
Hi,
from trunk's DefaultMavenExecutionRequestPopulator:
snapshots.setChecksumPolicy( ArtifactRepositoryPolicy.UPDATE_POLICY_DAILY );
snapshots.setUpdatePolicy( ArtifactRepositoryPolicy.CHECKSUM_POLICY_WARN );
And, who spotted the typo at first glance ;-) ?
Do we have technical reasons to no
Hi,
I noticed there are a bunch of checksum failures for recent Mercury
artifacts:
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/mercury/mercury-artifact/1.0.0-alpha-4/mercury-artifact-1.0.0-alpha-4-sources.jar
46K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on d
>I do like the hook to get people to actually use the parent POM, but
>at the same time it feels back to front (We probably don't need
>another pom release, but if we did that would then have to be a
>fork...). What about having them use the properties as their distMgmt
>settings for now?
On 14/02/2009, at 10:11 PM, Brian E. Fox wrote:
Isn't modifying the ASF POM premature? I'm not sure if other projects
are using the POM or not (they should be), but they may not be using
this system.
There are a few other projects looking to use the new structure and
this
would make it ea
>Isn't modifying the ASF POM premature? I'm not sure if other projects
>are using the POM or not (they should be), but they may not be using
>this system.
There are a few other projects looking to use the new structure and this
would make it easier for them to do. Projects not using the new
++1
I ran the integration tests as confirmation.
On 10/02/2009, at 12:32 PM, Brian E. Fox wrote:
It's finally time after 8 Release Candidates:
Issues fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName
=Html&projectId=10500&Create=Create
NOTE: The urls below
So, there seems to be some agreement.
However, I've come back from underground and now there are *two*
snapshots on trunk. I'm already spending valentine's day alone, so I
didn't really need another reason to curl up in the corner and cry :)
I would really like to pull an M2 release in the
Thanks for this!
I was just wondering if it is intended to be duplicated in the wiki or
was that just an editing ground before putting it on the site?
On 13/02/2009, at 2:30 AM, ogusa...@apache.org wrote:
Author: ogusakov
Date: Thu Feb 12 18:30:12 2009
New Revision: 743828
URL: http://svn.
Hi Oleg,
I've updated MNG-553 with the same fix for version - this is the
pattern we've been using for other tickets rather than creating dupes.
Last Brian indicated, the docs was the last thing needed before 553
could be closed - is that the case now, once the current snapshot is
release
Brian,
On 14/02/2009, at 7:43 AM, bri...@apache.org wrote:
Modified: maven/pom/trunk/asf/pom.xml
URL:
http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?rev=744288&r1=744287&r2=744288&view=diff
=
=
=
=
=
=
=
=
==
--- mav
I think this is a bug in Safari that we haven't figured out how to get
around yet. Is that what you were using?
On 14/02/2009, at 2:38 AM, David A Smith wrote:
Gentlemen,
There is a defect on the Maven download web page:
http://maven.apache.org/download.html
If you click on the "mirror"
Jason van Zyl wrote:
We might as well give the resources back, I think we're well covered
with the Hudson instance on the grid.
Alright, I just requested infra to remove the jobs [0].
Benjamin
[0] http://issues.apache.org/jira/browse/INFRA-1901
Gentlemen,
There is a defect on the Maven download web page:
http://maven.apache.org/download.html
If you click on the "mirror" column of the "Maven 2.0.9 (tar.gz)" row,
instead of getting a link to a page of mirror names (as you do with other
rows of this column) you get a gzipped html fi
+1 (coding style, even if important, doesn't deserve a -1 at this point)
mercury-ant-tasks is not part of the staged artifacts (not included in the
reactor): do you intend to release it separately?
Regards,
Hervé
Le mercredi 11 février 2009, Oleg Gusakov a écrit :
> Hi,
>
> Main reason for thi
Hervé BOUTEMY wrote:
Sorry to bug you about coding style, but this is important for the whole team
to be able to maintain code.
+1, also considering that "team" does not only include the committers
but also contributors who can more easily create clean patches when they
don't need to worry a
+1
- compiled maven-ant-tasks 2.0.10 with corresponding core dependency: ok
- deployed core site [1]: ok
Regards,
Hervé
[1] http://maven.apache.org/ref/2.0.10/
Le mardi 10 février 2009, Brian E. Fox a écrit :
> It's finally time after 8 Release Candidates:
>
>
>
> Issues fixed:
>
> http://jira
Oleg,
Sorry to bug you about coding style, but this is important for the whole team
to be able to maintain code.
For conditional (and loops):
- one space after if/for statement
- always add a block, even if it's not technically necessary
Regards,
Hervé
Le samedi 14 février 2009, ogusa...@apac
23 matches
Mail list logo
