Yes, at first I thought, duh that seems so obvious. But then we'd need
to preserve all those versions and they would also pollute the fixed in
drop down too. I think for this purpose it's not needed.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Paul Ben
I do not think it's worth doing.
RCs for Maven are not used like they are for at other projects, e.g., the
Spring Framework. Spring uses each RC to apply about 100 new issues to bring
the product to a "feature complete" stage. At Maven, the use of RC is to
eliminate regressions after features are
It is so much logic that I didn' think about it
What do you think guys ?
It seems to be the good idea ?
Arnaud
On Thu, Jul 17, 2008 at 12:37 AM, Samuel Le Berrigaud <[EMAIL PROTECTED]>
wrote:
> Hi all,
> if you want to have both you surely could.
>
> Why not adding the 2.0.10 RC1 version to Jira
I will be out of the office starting 12.07.2008 and will not return until
28.07.2008.
I will respond to your message when I return. In urgent cases please refer
to Elena Tonoyan ([EMAIL PROTECTED]) or Daria Ignatieva
([EMAIL PROTECTED])
Hi all,
if you want to have both you surely could.
Why not adding the 2.0.10 RC1 version to Jira and any issue that is
found in the RC1 would have its affected version field set to 2.0.10
RC1 and the fix for to 2.0.10. That you get the nice release notes and
the metrics of what was found in the RC
Vincent Siveton wrote:
What are the minimalist things that we need to check for a good Maven release?
[...]
Any others ideas?
Cross-compiling against the intended minimum JDK to catch accidental
usage of newer types/methods.
Checking for properly declared dependencies with the help of
depe
the error in clirr would need to be fixed too. I'll try to find some
time during the weekend to rollback and post a new release
On Wed, Jul 16, 2008 at 1:27 PM, Vincent Siveton
<[EMAIL PROTECTED]> wrote:
> Thanks Dennis to fix them.
>
> BTW Carlos, could you also include a release notes link on th
Sure! It is the goal of my question ;)
Vincent
2008/7/16, Carlos Sanchez <[EMAIL PROTECTED]>:
> whatever it is needs to be added to
> http://maven.apache.org/developers/release/releasing.html
>
>
> On Wed, Jul 16, 2008 at 1:35 PM, Vincent Siveton
> <[EMAIL PROTECTED]> wrote:
> > Hi guys,
> >
whatever it is needs to be added to
http://maven.apache.org/developers/release/releasing.html
On Wed, Jul 16, 2008 at 1:35 PM, Vincent Siveton
<[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> What are the minimalist things that we need to check for a good Maven release?
> Dennis points that we need to re
Hi guys,
What are the minimalist things that we need to check for a good Maven release?
Dennis points that we need to reduce Checkstyle errors, checking Clirr
report and licenses.
Any others ideas?
Cheers,
Vincent
-- Forwarded message --
From: Dennis Lundberg <[EMAIL PROTECTED]>
Thanks Dennis to fix them.
BTW Carlos, could you also include a release notes link on the jira
report? We discussed about it recently.
Cheers,
Vincent
2008/7/16, Dennis Lundberg <[EMAIL PROTECTED]>:
> Thanks for pushing for this release Carlos!
>
> Unfortunately there are a couple of things th
Thanks for pushing for this release Carlos!
Unfortunately there are a couple of things that needs to be fixed before
we can release 1.2, for which I have to vote -1 to the current release
candidate.
- The POM is missing the license header (I fixed this in svn)
- The Source files have the old
Benjamin Bentmann wrote:
I did some major changes in the relocator component for MSHADE-28 which
according to the plugin's release history is quite the only change that
might be related. Maybe I managed to get something wrong in there.
OK, I called that MSHADE-38 and have fixed the relocator t
Hi,
9 issues fixed. Last release was 2.5 years ago
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125&styleName=Html&version=12210
Staging repo:
http://people.apache.org/~carlos/staging-repo
Staging site:
http://maven.apache.org/plugins/maven-antrun-plugin-1.2/
Guide to testing s
This is fixed. I'm formalizing things and adding an integration test now.
Arnaud HERITIER wrote:
Done.
http://jira.codehaus.org/browse/MNG-3667
cheers,
arnaud
On Wed, Jul 16, 2008 at 4:16 PM, John Casey <[EMAIL PROTECTED]> wrote:
Please file with fix-for of 2.0.10, with that test case if y
I just verified with CXF that if I use maven 2.0.7, the reduced pom
has many extra excludes. I've gone ahead and added some code to the
ShadeMojo to double check if it's an irrelevant exclude and not
bother. This isn't needed with 2.0.9, but it is with 2.0.7. Can
you checkout the co
Previously in wagon, the "transferError" event was used haphazardly
(ie, not for all errors, inconsistently across providers, etc). It's
use is now uniform.
However, it is firing for all exceptions (including not found and
authorization failures). On second thought that is probably not the
One more thought while you're playing around try different
versions of maven. This is something that might be working correctly
with maven 2.0.9 (and probably 2.0.8) but may not be with 2.0.7 and
earlier due to all the fixes that were put in the dependency tree
resolution stuff.
I'll try to knock up a few test cases tomorrow to get to the bottom of this.
Cheers,
Mark
2008/7/16 Daniel Kulp <[EMAIL PROTECTED]>:
>
> I just checked and if I reverse that logic, I get things like:
>
>
> org.springframework
> spring-core
> 2.0.8
> compile
>
>
Done.
http://jira.codehaus.org/browse/MNG-3667
cheers,
arnaud
On Wed, Jul 16, 2008 at 4:16 PM, John Casey <[EMAIL PROTECTED]> wrote:
> Please file with fix-for of 2.0.10, with that test case if you have it. :-)
>
> Thanks,
>
> -john
>
> Arnaud HERITIER wrote:
>
>> With RC1, maven tries to down
Fair enough, I was just trying to get some metrics around what
surfaces after we call the RC, but we could probably do that if we
noted the date as a filter.
On 16-Jul-08, at 10:34 AM, Brian E. Fox wrote:
I would just continue to use 2.0.10, that way the release notes at the
end are complet
Sounds good. All I can tell you is that I've been doing quite a bit of
testing using 2.0.10-snapshot builds that had 1.2-snapshot configured
for use in the apache-maven project build (the one that assembles the
final distro), and I haven't noticed a problem with it yet.
I'll change my local co
I would just continue to use 2.0.10, that way the release notes at the
end are complete and under a single version.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 16, 2008 9:11 AM
To: Maven Developers List
Subject: Re: [PLEASE TEST] Maven 2.0.10-RC1
John Casey wrote:
For what it's worth, this works fine in 1.2-SNAPSHOT
Are you sure? I have identified a regression in 1.1 over 1.0.1 that
really seems to arise from my changes in SimpleRelocator. I.e. I
boostrapped Maven 2.0.x once with Shade 1.0.1 (passed ITs) and once with
1.1 (failed mn
Nope, I hadn't closed the issue - I did this morning.
Right now I'm waiting to see what comes of Mark and Daniel's
discussion, then one of us can roll that one along.
- Brett
On 17/07/2008, at 12:09 AM, John Casey wrote:
My mistake; I must have been looking at the wrong page when I
though
Please file with fix-for of 2.0.10, with that test case if you have it. :-)
Thanks,
-john
Arnaud HERITIER wrote:
With RC1, maven tries to download this dependency
org/apache/ws/commons/XmlSchema/SNAPSHOT/XmlSchema-SNAPSHOT.jar whereas with
2.0.9 it retreives the version 1.1.
What I have is a p
Please file this with fix-for of 2.0.10. I'll take a look.
-john
nicolas de loof wrote:
Running mvn eclipse:eclipse on my project dump many stacktrace on the
console :
Downloading:
http://sai1rennes:/archiva/repository/releases/org/jmock/jmock/2.4.0/jmock-2.4.0-javadoc.jar
org.apache.maven
Hang on a second though; since we're attempting to release 2.0.10, why
not file the issues under there?
I think I'd rather see that happen, since then the final release notes
for 2.0.10 will incorporate any issues we find along the way.
-john
Jason van Zyl wrote:
John, maybe a new version in
I'll set that up now.
Jason van Zyl wrote:
John, maybe a new version in JIRA to help track issues/regressions for
the RC cycle would help. Brian ended up doing 9 RCs so I'm sure we'll
get close to that again. Especially given what look like fundament
problems with wagon/artifact resolution.
For what it's worth, this works fine in 1.2-SNAPSHOT, but I can't
release with that plugin version in there.
Let's try to get that release going...
-john
Benjamin Bentmann wrote:
Brett Porter wrote:
Any idea what is wrong in 1.1+?
I did some major changes in the relocator component for MS
My mistake; I must have been looking at the wrong page when I thought I
saw there was nothing closed for 1.2...
-j
Brett Porter wrote:
On 16/07/2008, at 7:32 AM, [EMAIL PROTECTED] wrote:
Author: jdcasey
Date: Tue Jul 15 14:32:01 2008
New Revision: 677049
URL: http://svn.apache.org/viewvc?r
Call the vote. I looked on the road map for that plugin in the MSHADE
jira, but didn't see anything as closed for 1.2...
what's the change?
-john
Brett Porter wrote:
On 16/07/2008, at 7:32 AM, [EMAIL PROTECTED] wrote:
Author: jdcasey
Date: Tue Jul 15 14:32:01 2008
New Revision: 677049
URL
John, maybe a new version in JIRA to help track issues/regressions for
the RC cycle would help. Brian ended up doing 9 RCs so I'm sure we'll
get close to that again. Especially given what look like fundament
problems with wagon/artifact resolution.
On 16-Jul-08, at 8:12 AM, nicolas de loof
With RC1, maven tries to download this dependency
org/apache/ws/commons/XmlSchema/SNAPSHOT/XmlSchema-SNAPSHOT.jar whereas with
2.0.9 it retreives the version 1.1.
What I have is a project with a dependency to
org.codehaus.xfire:xfire-core:1.2.6
In the xfire-core pom we have a dependency to
org.apac
Running mvn eclipse:eclipse on my project dump many stacktrace on the
console :
Downloading:
http://sai1rennes:/archiva/repository/releases/org/jmock/jmock/2.4.0/jmock-2.4.0-javadoc.jar
org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate
resource in repository
at
org
it was just in the management section... removed :)
On 16/07/2008, at 6:49 PM, Benjamin Bentmann wrote:
Hi,
just in case this wasn't noticed before: The core's trunk is still
using the old version of Shade from Mojo (i.e. shade-maven-plugin)
instead of the new version maintained by Apache.
Hi,
just in case this wasn't noticed before: The core's trunk is still using
the old version of Shade from Mojo (i.e. shade-maven-plugin) instead of
the new version maintained by Apache. Is that intentional?
Benjamin
-
To u
Brett Porter wrote:
> Any idea what is wrong in 1.1+?
I did some major changes in the relocator component for MSHADE-28 which
according to the plugin's release history is quite the only change that
might be related. Maybe I managed to get something wrong in there. Will try
to reproduce the issue
+1
On Wed, Jul 16, 2008 at 12:40 AM, Brian E. Fox <[EMAIL PROTECTED]>
wrote:
> I say start out using the new interpolator apis so we don't have to
> consolidate more later.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Olivier Lamy
> Sent: Tuesd
39 matches
Mail list logo
