On Thu, Dec 3, 2009 at 7:44 PM, Brian Fox bri...@infinity.nu wrote:
Something like duplicate dependencies likely means you have a real
problem you didn't know about in your poms. I think failing is
appropriate in this case.
I fail to grok what you just said there. So if i have in my pom
On Fri, Dec 4, 2009 at 2:16 AM, Jorg Heymans jorg.heym...@gmail.com wrote:
On Thu, Dec 3, 2009 at 7:44 PM, Brian Fox bri...@infinity.nu wrote:
Something like duplicate dependencies likely means you have a real
problem you didn't know about in your poms. I think failing is
appropriate in this
On Tue, Nov 24, 2009 at 12:18 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Jorg Heymans wrote:
[ERROR] The project build-tools:1-SNAPSHOT
(D:\src\myproject\pom.xml) has 1 error
[ERROR]
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
must be
2009/12/3 Jorg Heymans jorg.heym...@gmail.com
On Tue, Nov 24, 2009 at 12:18 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Jorg Heymans wrote:
[ERROR] The project build-tools:1-SNAPSHOT
(D:\src\myproject\pom.xml) has 1 error
[ERROR]
On Thu, Dec 3, 2009 at 11:10 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
2009/12/3 Jorg Heymans jorg.heym...@gmail.com
On Tue, Nov 24, 2009 at 12:18 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Jorg Heymans wrote:
[ERROR] The project build-tools:1-SNAPSHOT
2009/12/3 Jorg Heymans jorg.heym...@gmail.com
On Thu, Dec 3, 2009 at 11:10 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
2009/12/3 Jorg Heymans jorg.heym...@gmail.com
On Tue, Nov 24, 2009 at 12:18 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Jorg Heymans
2009/12/3 Stephen Connolly stephen.alan.conno...@gmail.com
2009/12/3 Jorg Heymans jorg.heym...@gmail.com
On Thu, Dec 3, 2009 at 11:10 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
2009/12/3 Jorg Heymans jorg.heym...@gmail.com
On Tue, Nov 24, 2009 at 12:18 PM, Benjamin
On Fri, Nov 27, 2009 at 3:42 PM, Brett Porter br...@apache.org wrote:
Brian,
I'm not sure if you were replying to me or others, but you quoted me and
snipped my actual point:
I'm fine with either more or less frequent releases... I'm not fine with
circumventing review or pushing releases
I'm also not pushing for duration for testing purposes. That's part of it,
but as Jason said
automation can reduce the need over time (though it's never going to be 100%
so there's some value
in testing). However, it is mostly for an opportunity to review changes. If we
do 8 releases a day,
Brian,
I'm not sure if you were replying to me or others, but you quoted me and
snipped my actual point:
I'm fine with either more or less frequent releases... I'm not fine with
circumventing review or pushing releases outside the ASF.
I agree with everything you said below. I was saying we
-
From: paulus.benedic...@gmail.com
[mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict
Sent: Wednesday, November 25, 2009 9:21 PM
To: Maven Developers List
Subject: Re: voting was: [VOTE] Release Apache Maven 3.0-alpha-5
I would also like to contribute my frustration
, November 25, 2009 9:21 PM
To: Maven Developers List
Subject: Re: voting was: [VOTE] Release Apache Maven 3.0-alpha-5
I would also like to contribute my frustration with the
current build process. It's great the alpha releases are
coming out often, but I cannot possibly be testing them
: Wednesday, November 25, 2009 9:21 PM
To: Maven Developers List
Subject: Re: voting was: [VOTE] Release Apache Maven 3.0-alpha-5
I would also like to contribute my frustration with the
current build process. It's great the alpha releases are
coming out often, but I cannot possibly be testing them
On Nov 26, 2009, at 5:04 AM, Todd Thiessen wrote:
I can only speak from experience with what we have done here internally but I
can also attest that releasing too often is a real pain. You end up having a
bunch of releases publicized that no one cares about. It only serves to
clutter a
On Nov 26, 2009, at 5:56 AM, Jason van Zyl wrote:
On 2009-11-26, at 8:04 AM, Todd Thiessen wrote:
I can only speak from experience with what we have done here internally but
I can also attest that releasing too often is a real pain. You end up having
a bunch of releases publicized that
On 2009-11-26, at 11:04 AM, Ralph Goers wrote:
On Nov 26, 2009, at 5:04 AM, Todd Thiessen wrote:
I can only speak from experience with what we have done here
internally but I can also attest that releasing too often is a real
pain. You end up having a bunch of releases publicized that no
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Arnaud Héritier, Olivier
Lamy
+1 (non-binding): Nicolas De Loof, Stephen Connolly, Igor Fedorenko
I will promote the artifacts to the central repository and continue with
the release.
On 27/11/2009, at 2:27 AM, Todd Thiessen wrote:
The logic here is flawed because it is from a single
perspective of an
individual who finds it burdensome to validate each and every release.
It isn't just me. Both Paul and Brett expressed similar concerns ;-).
I don't think this was my
On Mon, Nov 23, 2009 at 7:59 PM, Paul Gier pg...@redhat.com wrote:
I wonder if we really need a full vote for every alpha. Especially if this
is going to happen every two weeks. Why not just vote for a 2 week alpha
release schedule and then don't do another vote until it's time for beta 1?
Niall Pemberton wrote:
On Mon, Nov 23, 2009 at 7:59 PM, Paul Gier pg...@redhat.com wrote:
I wonder if we really need a full vote for every alpha. Especially if this
is going to happen every two weeks. Why not just vote for a 2 week alpha
release schedule and then don't do another vote until
If ever we really needed to push out builds more frequently I would
just do it from Sonatype. I've given up trying to be truly agile at
Apache, it's just not going to happen.
On 2009-11-25, at 2:10 PM, Dan Fabulich wrote:
Niall Pemberton wrote:
On Mon, Nov 23, 2009 at 7:59 PM, Paul Gier
On 26/11/2009, at 6:24 AM, Jason van Zyl wrote:
If ever we really needed to push out builds more frequently I would just do
it from Sonatype. I've given up trying to be truly agile at Apache, it's just
not going to happen.
I don't understand what the issue is with the current process.
Let's not beat the dead horse. No one cares. There's not good reason
for not releasing something immediately if there are fixes available.
That's just not the way it works here, that's fine and not a big deal.
On 2009-11-25, at 7:52 PM, Brett Porter wrote:
On 26/11/2009, at 6:24 AM, Jason
I would also like to contribute my frustration with the current build
process. It's great the alpha releases are coming out often, but I
cannot possibly be testing them at the frequency you guys are
currently tagging and voting. I thought the once a week alpha was a
good idea until it actually
2009/11/26 Paul Benedict pbened...@apache.org:
I would also like to contribute my frustration with the current build
process. It's great the alpha releases are coming out often, but I
cannot possibly be testing them at the frequency you guys are
currently tagging and voting. I thought the once
Tried it out on our project, and i'm getting this:
[ERROR] The project build-tools:1-SNAPSHOT
(D:\src\myproject\pom.xml) has 1 error
[ERROR]
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: junit:junit:jar - duplicate declaration of
Jorg Heymans wrote:
[ERROR] The project build-tools:1-SNAPSHOT
(D:\src\myproject\pom.xml) has 1 error
[ERROR]
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: junit:junit:jar - duplicate declaration of version
3.8.2
Shall i log an issue
+1
2009/11/23 Benjamin Bentmann benjamin.bentm...@udo.edu:
Hi,
We solved some more issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14952
There are still a couple of issues left in JIRA:
Hi,
We solved some more issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14952
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1
Staging repo:
+1
On 2009-11-23, at 11:33 AM, Benjamin Bentmann wrote:
Hi,
We solved some more issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14952
There are still a couple of issues left in JIRA:
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Mon, Nov 23, 2009 at 5:38 PM, Jason van Zyl ja...@maven.org wrote:
+1
On 2009-11-23, at 11:33 AM, Benjamin Bentmann wrote:
Hi,
We solved some more issues:
+1
2009/11/23 Arnaud HERITIER aherit...@gmail.com
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Mon, Nov 23, 2009 at 5:38 PM, Jason van Zyl ja...@maven.org wrote:
+1
On 2009-11-23, at 11:33 AM, Benjamin
+1
2009/11/23 nicolas de loof nicolas.del...@gmail.com:
+1
2009/11/23 Arnaud HERITIER aherit...@gmail.com
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Mon, Nov 23, 2009 at 5:38 PM, Jason van Zyl ja...@maven.org
I wonder if we really need a full vote for every alpha. Especially if this is
going to happen every two weeks. Why not just vote for a 2 week alpha release
schedule and then don't do another vote until it's time for beta 1?
Benjamin Bentmann wrote:
Hi,
We solved some more issues:
+1
--
Regards,
Igor
Benjamin Bentmann wrote:
Hi,
We solved some more issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14952
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1
35 matches
Mail list logo
