I'd like to merge a few older released versions together in Jira (to
help in reducing the noise on some of the reports.)
What I'd like to do ...
Take versions:
* 0.9
* 1.0-alpha-1
* 1.0-alpha-2
* 1.0-beta-1
* 1.0-beta-2
* 1.0-beta-3
* 1.0-beta-4
And merge them into:
* 1.0
Any
I'm unsure. I'd definitely leave 0.9 out on it's own regardless.
I kind of like the idea of merging, but I also hate to irreversibly
lose information :)
Does archiving the alpha/beta releases achieve what you need? What is
the noise in the reports you are referring to?
Thanks,
Brett
On
On Feb 18, 2008 12:05 PM, Joakim Erdfelt [EMAIL PROTECTED] wrote:
I'd like to merge a few older released versions together in Jira (to
help in reducing the noise on some of the reports.)
I don't think issues for 0.9 should be merged into 1.0-- it's a
different codebase.
--
Wendy
Archiving the version might accomplish the same thing.
I see some checkboxes to exclude archived versions in the reports.
(heh, still spelling archive wrong)
As for reports, I can't find perma-links for most of them.
But here's an example: http://urltea.com/2qf2
- Joakim
Brett Porter wrote:
On Feb 18, 2008 8:23 PM, Joakim Erdfelt [EMAIL PROTECTED] wrote:
I've been checking out some performance / scalability / tooling /
testing tests recently at my office with regards to web frameworks.
SpringMVC beat everything but Struts 1.x in performance.
And SpringMVC makes testing really
Hi Wendy,
2008/2/17, [EMAIL PROTECTED] [EMAIL PROTECTED]:
Author: wsmoak
Date: Sun Feb 17 18:21:26 2008
New Revision: 628597
URL: http://svn.apache.org/viewvc?rev=628597view=rev
Log:
Fix example for M2_HOME value.
Modified:
maven/components/branches/maven-2.0.x/README.txt
This new plugin seems to be a great improvement and I welcome the further
development.
However, i'm not sure if it was intended to be picked up by the whole maven
user population?
This is because:
- There is no backwards compatability, suddenly maven no longer works as it
used to
- The
On Feb 18, 2008 4:56 AM, Vincent Siveton [EMAIL PROTECTED] wrote:
In addition, the last part of the M2_HOME path MUST be of the form
maven-$version, eg:
-/usr/local/maven-2.1-SNAPSHOT
+/usr/local/apache-maven-2.0.9-SNAPSHOT
I think that a generic version would be better, i.e.
On Feb 17, 2008, at 3:48 PM, Brett Porter wrote:
- decent integration of code coverage plugins (we never got this
forked lifecycle quite right)
Can you shed some more light on this? Do we have specific test cases
that we can put into the build?
I'll have to read over the rest of your
On 18-Feb-08, at 4:55 AM, Richard Chamberlain wrote:
This new plugin seems to be a great improvement and I welcome the
further development.
However, i'm not sure if it was intended to be picked up by the
whole maven user population?
It is as a consequence of Maven auto-updating which
Hi,
Brett/Raphael I know that both of you talked about doing a release,
and if you're around and are going to do it now great. I'll wait an
hour, and if neither of you respond I'll start preparing the release.
I can live the create-from-archetype not working on Windows. We have
to fix
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas of
Maven that I can't list them all here (various plugins, surefire,
doxia,...), including documentation and translations, and he has not
been afraid to actively discuss
+1
Ralph
Lukas Theussl wrote:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas
of Maven that I can't list them all here (various plugins, surefire,
doxia,...), including documentation and translations, and he has not
+1
On 18-Feb-08, at 9:38 AM, Lukas Theussl wrote:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas
of Maven that I can't list them all here (various plugins, surefire,
doxia,...), including documentation and
Definitely +1
Vincent
2008/2/18, Lukas Theussl [EMAIL PROTECTED]:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas of
Maven that I can't list them all here (various plugins, surefire,
doxia,...), including
+1
Milos
On Feb 18, 2008 6:38 PM, Lukas Theussl [EMAIL PROTECTED] wrote:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas of
Maven that I can't list them all here (various plugins, surefire,
doxia,...), including
+1
--
Olivier
2008/2/18, Vincent Siveton [EMAIL PROTECTED]:
Definitely +1
Vincent
2008/2/18, Lukas Theussl [EMAIL PROTECTED]:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas of
Maven that I can't list them
I don't object.
Raphaël
2008/2/18, Jason van Zyl [EMAIL PROTECTED]:
Ok, unless anyone objects I'm going to try and get this thing out.
On 18-Feb-08, at 9:29 AM, Jason van Zyl wrote:
Hi,
Brett/Raphael I know that both of you talked about doing a release,
and if you're around and are
Ok, unless anyone objects I'm going to try and get this thing out.
On 18-Feb-08, at 9:29 AM, Jason van Zyl wrote:
Hi,
Brett/Raphael I know that both of you talked about doing a release,
and if you're around and are going to do it now great. I'll wait an
hour, and if neither of you respond
+1
-john
On Feb 18, 2008, at 12:38 PM, Lukas Theussl wrote:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many
areas of Maven that I can't list them all here (various plugins,
surefire, doxia,...), including documentation
Well ask us to do something rather than blabber on and we shut up...
I lost two managers and a developer which has chewed up all my time...
On Thu, 31 Jan 2008 02:14:59 Stephen Connolly wrote:
IMHO
I think a vote with the two positions clearly identified (perhaps with pros
and cons for both
On 19/02/2008, at 3:15 AM, John Casey wrote:
On Feb 17, 2008, at 3:48 PM, Brett Porter wrote:
- decent integration of code coverage plugins (we never got this
forked lifecycle quite right)
Can you shed some more light on this? Do we have specific test cases
that we can put into the
No objections of course, I was waiting for you since it sounded like
you'd said the windows issue was a blocker and that Brian was looking
into it.
On 19/02/2008, at 5:47 AM, Raphaël Piéroni wrote:
I don't object.
Raphaël
2008/2/18, Jason van Zyl [EMAIL PROTECTED]:
Ok, unless anyone
+1
On 19/02/2008, at 4:38 AM, Lukas Theussl wrote:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas
of Maven that I can't list them all here (various plugins, surefire,
doxia,...), including documentation and
Hi Nicolas,
Neat change - I like it.
I just wonder if ${mirrorOf} instead of {0} might be more intuitive?
Also - don't forget to merge your change to artifact/trunk!
Cheers,
Brett
On 19/02/2008, at 1:55 AM, [EMAIL PROTECTED] wrote:
Author: nicolas
Date: Mon Feb 18 06:55:12 2008
New
+1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I just got the roundtrip tests working on windows,
Do i wait for the release to commit?
Another issue could be to update the internal catalog to grab
the latest MAVENUSER wiki page.
Raphaël
2008/2/18, Brett Porter [EMAIL PROTECTED]:
No objections of course, I was waiting for you since it
+1
Rahul
Lukas Theussl wrote:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas
of Maven that I can't list them all here (various plugins, surefire,
doxia,...), including documentation and translations, and he has
On 19/02/2008, at 8:16 AM, Raphaël Piéroni wrote:
I just got the roundtrip tests working on windows,
Do i wait for the release to commit?
Commit away - an RM can prepare a release based on a previous revision
if they see fit, though it sounds like these changes should be pulled
in.
2008/2/18, Brett Porter [EMAIL PROTECTED]:
On 19/02/2008, at 8:16 AM, Raphaël Piéroni wrote:
I just got the roundtrip tests working on windows,
Do i wait for the release to commit?
Commit away - an RM can prepare a release based on a previous revision
if they see fit, though it sounds
+1. Lets get the current fix out and do another release as soon as the
windows issue is fixed. (it only affects creating a new archetype iirc)
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, February 18, 2008 12:29 PM
To: Maven Developers List
Subject:
+1 for sure
Lukas Theussl wrote:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas of
Maven that I can't list them all here (various plugins, surefire,
doxia,...), including documentation and translations, and he has
+1
Fabrice
On Feb 18, 2008 6:38 PM, Lukas Theussl [EMAIL PROTECTED] wrote:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas of
Maven that I can't list them all here (various plugins, surefire,
doxia,...), including
I am only speaking in regard to MNG-3092, there are several other related
issues which I think all should be fixed
Cons
--
1) Continuous integration of trunks
I would like to be able to run the tests of all of my artifacts against a
build of trunk of every other. How I
+1
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Monday, February 18, 2008 12:39 PM
To: Maven Developers List
Subject: [vote] Benjamin Bentmann as Maven committer
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided
URL to the release?
On 18-Feb-08, at 3:04 PM, Brian E. Fox wrote:
The most important early issues have been fixed and we need to get
this
out there. The site is updated and here's the list of issues fixed:
Release Notes - Maven Archetype - Version 2.0-alpha-2
** Bug
*
Hi Wendy
Did you mean for this to go into Maven parent pom?
The URL in your change suggests to me that is intended for Maven
components pom. If left in Maven parent pom there will be URL clashes
between say Maven 2.1 and Maven Project Info reports Plugin 2.1
[EMAIL PROTECTED] wrote:
The most important early issues have been fixed and we need to get this
out there. The site is updated and here's the list of issues fixed:
Release Notes - Maven Archetype - Version 2.0-alpha-2
** Bug
* [ARCHETYPE-128] - Unable to create a Cocoon app with Maven
archetype:
+1. Gave it a spin on a big project for :create and :generate, scanned
the commit logs.
Not blockers as they are matters of policy:
* I'd prefer is consistency in the tag name - it's 2.0-alpha-2 instead
of maven-archetype-2.0-alpha-2
* MavenArchetypeMojo, site.xml have out of date license
Woop: http://people.apache.org/~brianf/staging-repository/
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, February 18, 2008 6:14 PM
To: Maven Developers List
Subject: Re: [vote] release maven-archetype-plugin-2.0-alpha-2
URL to the release?
On 18-Feb-08,
On Feb 18, 2008 4:12 PM, Dennis Lundberg [EMAIL PROTECTED] wrote:
Hi Wendy
Did you mean for this to go into Maven parent pom?
The URL in your change suggests to me that is intended for Maven
components pom. If left in Maven parent pom there will be URL clashes
between say Maven 2.1 and
On 19/02/2008, at 10:49 AM, Brian E. Fox wrote:
... I had to enter all the
values by hand ...
That's unusual - is something not configured right?
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
Yeah, the versions in the pom where 2.0-SNAPSHOT instead of
2.0-alpha-2-SNAPSHOT
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, February 18, 2008 7:04 PM
To: Maven Developers List
Subject: Re: [vote] release maven-archetype-plugin-2.0-alpha-2
On
I'll reroll it to correct the tag and licenses. I had to enter all the
values by hand and didn't catch the tag.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, February 18, 2008 6:46 PM
To: Maven Developers List
Subject: Re: [vote] release
Rerolled to correct the tag and 2 header issues identified by Brett.
The most important early issues have been fixed and we need to get this
out there. The site is updated and here's the list of issues fixed:
Staging repo: http://people.apache.org/~brianf/staging-repository
Release
+1 - retested the new version.
On 19/02/2008, at 11:18 AM, Brian E. Fox wrote:
Rerolled to correct the tag and 2 header issues identified by Brett.
The most important early issues have been fixed and we need to get
this
out there. The site is updated and here's the list of issues fixed:
+1
I could make my archetypes, deploy, and use mvn archetype:generate no
problem. The old way works fine too now as I've had a bunch of scripts
forever I've used and they all spit out project that build.
On 18-Feb-08, at 4:18 PM, Brian E. Fox wrote:
Rerolled to correct the tag and 2
Continuum doesn't seem to be deploying snapshots correctly from Zones
anymore. The latest maven snapshots have carlos' paths in them
builddef.lst file:
-classpath
C:\Documents and
Settings\csanchez\.m2\repository\aspectj\aspectjrt\1.5.3\aspectjrt-1.5.3
.jar;C:\Documents and
Hi everyone, I apologize for asking a rudimentary question. I'm currently
developing a plugin to manage Globus Toolkit related tasks (create GAR, flatten
WSDLs, etc.) for Maven. I just wanted to know if it was better to have
generated source as a submodule or as a classifier.
Here is a quick
On Feb 18, 2008 9:58 PM, Wendy Smoak [EMAIL PROTECTED] wrote:
I'd like to do the first release of the Maven Stage Plugin. This
plugin is already being used for Maven releases, and although it has
limited functionality, it seems to be stable.
...
Staging repo:
I'd like to do the first release of the Maven Stage Plugin. This
plugin is already being used for Maven releases, and although it has
limited functionality, it seems to be stable.
There are four open issues in JIRA:
MSTAGE-1RepositoryCopierTest fails on Windows
MSTAGE-2The
+1
On 18-Feb-08, at 8:58 PM, Wendy Smoak wrote:
I'd like to do the first release of the Maven Stage Plugin. This
plugin is already being used for Maven releases, and although it has
limited functionality, it seems to be stable.
There are four open issues in JIRA:
MSTAGE-1
+1
Arnaud
On Feb 18, 2008 11:46 PM, Dennis Lundberg [EMAIL PROTECTED] wrote:
+1 for sure
Lukas Theussl wrote:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas of
Maven that I can't list them all here (various
+1
2008/2/19, Arnaud HERITIER [EMAIL PROTECTED]:
+1
Arnaud
On Feb 18, 2008 11:46 PM, Dennis Lundberg [EMAIL PROTECTED] wrote:
+1 for sure
Lukas Theussl wrote:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so
2008/2/18, Joakim Erdfelt [EMAIL PROTECTED]:
I've felt that we need to migrate our choice of IoC (plexus) towards a
better documented and better supported container (I'm leaning towards
Spring)
+1000 : I was never very confortable with plexus and lack of documentation
on available
I'd like to get some feedback in MNG-3410, particularly from John as
he has been working on this.
If you build and install a plugin with managed versions that affect
plugin transitive dependencies, when it's used the dependency
management is ignored
If the dependency management affects the
56 matches
Mail list logo
