Hi,
We are in the process of integrating Maven in to Gentoo. Currently, we are
trying to bootstrap maven. Our strategy is to integrate each and every
sub-project of Maven-2.2.1 [1] separately. So, we first transformed these to
an ant projects by generating the build.xml via `mvn ant:ant`. I know
a very good idea
+1
LieGrue,
strub
--- On Sun, 6/19/11, Benson Margulies bimargul...@gmail.com wrote:
From: Benson Margulies bimargul...@gmail.com
Subject: Re: The JIRA chocolate box
To: Maven Developers List dev@maven.apache.org
Date: Sunday, June 19, 2011, 3:05 AM
I am only proposing
Nice idea +1.
BTW asking a test case is not very easy.
As most of the time issues happen on corpo/private *complex* project.
So extracting a test case can be hard.
2011/6/19 Benson Margulies bimargul...@gmail.com:
If no one objects to this idea, I'd like to add a component, which is
an email
I opened MNG-5119 to track this. We can use the Wiki too [2], if useful at any
time.
I already did some minor improvements and published 3.0.4-SNAPSHOT site [3]
(sync pending) to see the actual state, to be compared with 3.0.3 [4]
I'm starting to test ideas on shared components, since they are
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com]
Sent: Sunday, 19 June 2011 6:08 AM
To: Maven Developers List; Maven Project Management Committee List
Subject: [VOTE]: release maven-changes-plugin 2.6
Hi,
We solved 3 issues:
Really? You'd release a
Dont know if we're looking at the same jira; I see 10 issues being
resolved.
+1 binding
Given the amount of *work* staging a release is, I hardly doubt anyone
does a release they don't think is worth it.
Kristian
sø., 19.06.2011 kl. 18.34 +1000, skrev Gavin McDonald:
-Original
don't knock somebody who is taking the time and effort to actually run a
release.
any improvement is an improvement... you could quibble that maybe it should
have been a 2.5.1 and not a 2.6 but it is down to the person who steps up to
make the release.
speaking with my pmc hat on, any
On 2011-06-19 00:30, Benson Margulies wrote:
I just looked at the 'blocker' issues. We have a variety of very old
JIRAs here. None of the ones I looked at have a self-contained test
case that would can be downloaded, run, and converted to an
integration test, etc.
This is one of the major
This is a great idea.
Some minor comments inline.
On 2011-06-19 04:22, Benson Margulies wrote:
If no one objects to this idea, I'd like to add a component, which is
an email like the following to the user list.
--snip--
Dear Maven Users,
Over the years, the JIRA for core Maven
On 19 June 2011 11:52, Dennis Lundberg denn...@apache.org wrote:
On 2011-06-19 00:30, Benson Margulies wrote:
I just looked at the 'blocker' issues. We have a variety of very old
JIRAs here. None of the ones I looked at have a self-contained test
case that would can be downloaded, run, and
Hmm, I not quite sure what happened here. Benson?
On 2011-06-18 22:00, bimargul...@apache.org wrote:
Author: bimargulies
Date: Sat Jun 18 20:00:55 2011
New Revision: 1137235
URL: http://svn.apache.org/viewvc?rev=1137235view=rev
Log:
[maven-release-plugin] rollback the release of
FWIW, I've spent plenty of time on the 'trying to make a test case'
side of the fence and I appreciate how hard it can be.
If someone makes a cogent case that they can't come with a testcase,
then there are possible outcomes:
1: A dev finds the story sufficiently compelling to try to build a
I know what I think I did.
1) my copy of the pom was one back from Dennis' change for the locale.
2) I started the release process.
3) I got an error to the effect that pom.xml was out of date.
4) release:rollback
5) svn up, with a G on the pom, which I thought merged Dennis in.
I can't rule out
I'd rather see a release with 3 bug fixes if they code base is idle than see
not see a release for weeks/months whilst someone waits for N more issues to
be resolved.
--
Great artists are extremely selfish and arrogant things — Steven Wilson,
Porcupine Tree
On Sun, Jun 19, 2011 at 8:34 PM,
1: This [VOTE] is cancelled due to a merge snafu in the prep.
2: for Gavin: I spent several days fixing up a very broken feature to
render the plugin actually usable with customized JIRA installations.
I want to put that work to work in the real world, and I didn't see
any other outstanding
Kristian,
How are you seeing 10?
--benson
On Sun, Jun 19, 2011 at 5:50 AM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
Dont know if we're looking at the same jira; I see 10 issues being
resolved.
+1 binding
Given the amount of *work* staging a release is, I hardly doubt anyone
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212version=17375
??
Den 19. juni 2011 kl. 13:40 skrev Benson Margulies bimargul...@gmail.com:
Kristian,
How are you seeing 10?
--benson
On Sun, Jun 19, 2011 at 5:50 AM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
On 2011-06-19 13:39, Benson Margulies wrote:
Kristian,
How are you seeing 10?
In the release notes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17375styleName=TextprojectId=11212
In JIRA 4 the default layout changed so that it shows some sort of
summary, which I don't understand
Well, that explains that. 2.6 it is, and new vote coming soon.
On Sun, Jun 19, 2011 at 8:02 AM, Dennis Lundberg denn...@apache.org wrote:
On 2011-06-19 13:39, Benson Margulies wrote:
Kristian,
How are you seeing 10?
In the release notes:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17375styleName=TextprojectId=11212
There are plenty of issues left in JIRA:
+1
BTW: Your reply-to and send-to headings are not totally according to
maven common release procedure;
http://maven.apache.org/developers/release/maven-project-release-procedure.html
Kristian
sø., 19.06.2011 kl. 08.16 -0400, skrev Benson Margulies:
Hi,
We solved 10 issues:
Hi
I would like to create this scenario on running a maven project:
Do you want to enter module-name? ( Y / N)
(on entering Y , i should ask for the parameter)
*Y
module-name: nameofthename
*
(on entering N , i should terminate the asking process and the rest of the
project build should be
+1
Great idea!
On 6/18/11 10:22 PM, Benson Margulies wrote:
If no one objects to this idea, I'd like to add a component, which is
an email like the following to the user list.
--snip--
Dear Maven Users,
Over the years, the JIRA for core Maven
(http://jira.codehaus.org/browse/MNG) has
Is there any smart way to tag a bug as processed in a triaging process
so we can focus on the remaining bugs?
I've always wondered if there's any option to tag an issue or create
shared custom lists...?
K
Den 19. juni 2011 kl. 18:42 skrev John Casey jdca...@commonjava.org:
+1
Great idea!
Hi,
i've checked the web site and found that the link
(http://maven.apache.org/plugins/maven-changes-plugin-2.6/index.html)
to the changes.xsd file does not work...
Furthermore the link Cobertura Test Coverage links to the index.html
page...and not to a cobertura test coverage...
And a
On 2011-06-19 18:46, Kristian Rosenvold wrote:
Is there any smart way to tag a bug as processed in a triaging process
so we can focus on the remaining bugs?
I've always wondered if there's any option to tag an issue or create
shared custom lists...?
We should be able to use Labels for this:
Benson,
Did you use Maven 3 to deploy the site?
I recommend using Maven 2 for site deployment until we get
maven-site-plugin 3.0-beta-4 released.
On 2011-06-19 19:00, Karl Heinz Marbaise wrote:
Hi,
i've checked the web site and found that the link
1) yes. WHen I use 2 I got stumped on authentication in the deploy.
2) I can redeploy. Little did I know.
I don't see any reason to rewind the vote. I'll redeploy.
On Sun, Jun 19, 2011 at 1:15 PM, Dennis Lundberg denn...@apache.org wrote:
Benson,
Did you use Maven 3 to deploy the site?
I
Labels are now a native feature in recent releases of Jira and they are
really useful to tag issues for a need like this one.
We could use them also to give a complexity level of the issue, ...
The need is to define them and follow a common convention
Another solution is to have a custom workflow
On Sunday, June 19, 2011 7:13:11 PM Dennis Lundberg wrote:
On 2011-06-19 18:46, Kristian Rosenvold wrote:
Is there any smart way to tag a bug as processed in a triaging process
so we can focus on the remaining bugs?
I've always wondered if there's any option to tag an issue or create
I have redeployed using 2.x.
On Sun, Jun 19, 2011 at 1:42 PM, Benson Margulies bimargul...@gmail.com wrote:
1) yes. WHen I use 2 I got stumped on authentication in the deploy.
2) I can redeploy. Little did I know.
I don't see any reason to rewind the vote. I'll redeploy.
On Sun, Jun 19,
labels seems reasonable, assuming that Codehaus deploys them.
Given the positive response to this idea, I plan to send the email
tomorrow some time and start on MNG.
On Sun, Jun 19, 2011 at 3:24 PM, Daniel Kulp dk...@apache.org wrote:
On Sunday, June 19, 2011 7:13:11 PM Dennis Lundberg wrote:
as far as I know ben made you me and brett admins... but that might be for
maven stuff only... I can always bash ben on the head if we want to ;-) (our
at least ask someone to bash ben on the head)
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and
Since my lame attempt at humor on the last thread led to some
confusion, I'll keep this relatively straight.
Consider, if you please, http://jira.codehaus.org/browse/MNG-2258.
For one thing, this report is marked as 'superceded by' another, but
it's still open. What's that mean?
For another, it
Yes I am admin on the codehaus instance thus technically it is possible for
now.
It will be perhaps less easy when we'll be @ Apache.
Arnaud
On Sun, Jun 19, 2011 at 9:28 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
as far as I know ben made you me and brett admins... but that
yes label are available @ Codehaus
Arnaud
On Sun, Jun 19, 2011 at 9:26 PM, Benson Margulies bimargul...@gmail.comwrote:
labels seems reasonable, assuming that Codehaus deploys them.
Given the positive response to this idea, I plan to send the email
tomorrow some time and start on MNG.
We're good here. I just added the label maven-messy to
http://jira.codehaus.org/browse/MNG-2258 as an experiment.
I suggest that we use a specific label for the backlog, so:
Old report, no test case:
maven-backlog-cleanup
New report, no testcase:
maven-needs-testcase
All committers will have access to 'edit' issues at Apache, and that's
all you need to work with labels.
2011/6/19 Arnaud Héritier aherit...@gmail.com:
Yes I am admin on the codehaus instance thus technically it is possible for
now.
It will be perhaps less easy when we'll be @ Apache.
It was about to (re-)define the workflow which requires full jira admin
Arnaud
On Sun, Jun 19, 2011 at 9:35 PM, Benson Margulies bimargul...@gmail.comwrote:
All committers will have access to 'edit' issues at Apache, and that's
all you need to work with labels.
2011/6/19 Arnaud Héritier
Yes, indeed.
2011/6/19 Arnaud Héritier aherit...@gmail.com:
It was about to (re-)define the workflow which requires full jira admin
Arnaud
On Sun, Jun 19, 2011 at 9:35 PM, Benson Margulies
bimargul...@gmail.comwrote:
All committers will have access to 'edit' issues at Apache, and that's
On 2011-06-19 19:42, Benson Margulies wrote:
1) yes. WHen I use 2 I got stumped on authentication in the deploy.
2) I can redeploy. Little did I know.
I don't see any reason to rewind the vote. I'll redeploy.
Me neither. A redeploy will do nicely, thanks.
I'll try to review tomorrow.
On
-Original Message-
From: Kristian Rosenvold [mailto:kristian.rosenv...@gmail.com]
Sent: Sunday, 19 June 2011 7:50 PM
To: 'Maven Developers List'
Subject: RE: [VOTE]: release maven-changes-plugin 2.6
Dont know if we're looking at the same jira; I see 10 issues being resolved.
-Original Message-
From: Mark Derricutt [mailto:m...@talios.com]
Sent: Sunday, 19 June 2011 9:37 PM
To: Maven Developers List; ga...@16degrees.com.au
Subject: Re: [VOTE]: release maven-changes-plugin 2.6
I'd rather see a release with 3 bug fixes if they code base is idle than see
http://maven.apache.org/developers/java5.html
Should we update the above?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Is there a reason you can't use the build.xml we've already provided for those
that need to bootstrap? Hopefully that would simplify things for you.
The problem you're seeing is probably related to an incorrect definition of a
META-INF/plexus/components.xml file related to that SecDispatcher
IMO yep, no need to go through that much effort - we haven't supported running
Maven on Java 1.4 in the core for quite some time now.
On 20/06/2011, at 8:29 AM, Benson Margulies wrote:
http://maven.apache.org/developers/java5.html
Should we update the above?
Thanks for initiating this. The cleanup is something I've worked on from time
to time and each time burned out before getting to the end :) It's definitely a
case of many hands make light work.
At the moment, we use versions to measure triage, but labels sound like a much
better alternative. I
On 20/06/2011, at 5:30 AM, Benson Margulies wrote:
Since my lame attempt at humor on the last thread led to some
confusion, I'll keep this relatively straight.
Consider, if you please, http://jira.codehaus.org/browse/MNG-2258.
For one thing, this report is marked as 'superceded by'
It's closed because I, myself, closed it today :-)
On Sun, Jun 19, 2011 at 8:47 PM, Brett Porter br...@apache.org wrote:
On 20/06/2011, at 5:30 AM, Benson Margulies wrote:
Since my lame attempt at humor on the last thread led to some
confusion, I'll keep this relatively straight.
Consider,
There is one critical issue open only because it was never ported to
2.0.x. Presumably that also gets closed?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Yes.
On 20/06/2011, at 11:10 AM, Benson Margulies wrote:
There is one critical issue open only because it was never ported to
2.0.x. Presumably that also gets closed?
-
To unsubscribe, e-mail:
Hi Brett,
On Mon, Jun 20, 2011 at 5:41 AM, Brett Porter br...@apache.org wrote:
The problem you're seeing is probably related to an incorrect definition of
a META-INF/plexus/components.xml file related to that SecDispatcher
component. You're probably pulling in a file you didn't intend to.
52 matches
Mail list logo
