Author: hboutemy
Date: Sun Mar 30 05:03:00 2008
New Revision: 642720
URL: http://svn.apache.org/viewvc?rev=642720&view=rev
Log:
fixed encoding when writing interpolated POM file
Modified:
maven/plugins/trunk/maven-invoker-plugin/src/main/java/org/apache/maven/plugin/invoker/InvokerMojo.java
-
Thank you everyone for the testing and confirmatory responses so far. It
helps to gauge the progress. There was one regression identified in
2.0.9 RC6: (MNG-3495: NPE at
org.apache.maven.wagon.repository.Repository.hashCode). This has been
fixed and RC7 posted.
Various users have identified some
Thank you everyone for the testing and confirmatory responses so far. It
helps to gauge the progress. There was one regression identified in
2.0.9 RC6: (MNG-3495: NPE at
org.apache.maven.wagon.repository.Repository.hashCode). This has been
fixed and RC7 posted.
Various users have identified some
I think it's safer to leave it at beta-6. Most people aren't expressing any
issues and if anyone has trouble, they can manually lock to beta-5. This is
safer than potentially downgrading everyone.
-Original Message-
From: Bouiaw [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2008
This is true - but the tree was available elsewhere, I think the help
plugin had it for a while.
A
On 2 Apr 2008, at 00:39, Jason Chaffee wrote:
Also, this may have been written before the dependency plugin had the
current feature set. I know when I first started using maven2 and the
depend
Don't worry, you can test RC7 shortly ;-) The site plugin is just
generally a mess in beta-6, particularly with multimodule sites.
-Original Message-
From: Sejal Patel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2008 12:31 PM
To: Maven Developers List
Subject: Re: [2.0.9 RC6]
Ah
Ah man that sucks. I just finished checking the results of the 217 projects
we have in cruise control using RC5 (which all worked perfectly as far as I
can tell) and now there is an RC6. Can I just blindly say I accept it :)
What is the problem with the site plugin quickly? I'd like to see if it
i
Hi,
Just an information that is important (from my point of view) to know.
Site plugin beta-6 has an important issue (
http://jira.codehaus.org/browse/MSITE-270) : with multi modules projects,
menus are wrong, making site plugin unusable for the majority of
multi-modules sites.
beta-5 plugin has
2.0.9 defines the plugins in the superpom now. He probably have beta-5
kicking around from who-knows-when. We can drop back to beta-5 in 2.0.9
but that may potentially downgrade some users.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2008 4:3
> From: "Barrie Treloar" <[EMAIL PROTECTED]>
>
> On the users lists I asked about seeding the repo with 3.2.2 eclipse jars.
>
> There is some talk about doing so and the naming convention that would be
> used.
>
> Jason knows who he has been talking to in the Eclipse world.
>From the user maili
Not sure if this is the cause of these failures, but archetype's got
serious issues with generating resources on Windows. It assumes '/'
file separator in archetype zips, but on Windows this can also be '\'.
Thus file sets don't work for me at all on Windows (not a duplicate
of ARCHETYPE-146).
I
David found a minor regression that I've just fixed. He is also having
problems with 2.0-beta-6 of the site plugin as is seen in a separate
thread.
I'm still reviewing and testing.
- Brett
On 02/04/2008, at 8:34 AM, Brian E. Fox wrote:
We made a minor tweak to the dependency order process
Yep, tests fail on Windows with:
---
Test set: org.apache.maven.archetype.generator.DefaultArchetypeGeneratorTest
---
Tests run: 12, Failures: 10,
Hi Jason,
2008/4/1, Jason van Zyl <[EMAIL PROTECTED]>:
> Are you using the contribution that was contributed long ago? Some guy
Nope since I am not aware about it. Could you give me a pointer?
> implemented an editor for Eclipse. Eugene at one point tried to integrate it
> into m2e but it wasn't
It was... I cloned them first :)
On 02/04/2008, at 8:16 PM, Emmanuel Venisse wrote:
Why a move and not a copy? same question for MRM-760
Emmanuel
On Wed, Apr 2, 2008 at 5:44 AM, Brett Porter (JIRA)
<[EMAIL PROTECTED]>
wrote:
[
http://jira.codehaus.org/browse/MRM-759?page=com.atlassia
Just used it to build and release about 10 modules in my project, worked
fine.
Thanks for the consistence in quality btw, the RC process is really a step
up from what was done before.
Jorg
On Tue, Apr 1, 2008 at 11:34 PM, Brian E. Fox <[EMAIL PROTECTED]>
wrote:
> We made a minor tweak to the de
Why a move and not a copy? same question for MRM-760
Emmanuel
On Wed, Apr 2, 2008 at 5:44 AM, Brett Porter (JIRA) <[EMAIL PROTECTED]>
wrote:
>
> [
> http://jira.codehaus.org/browse/MRM-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Brett Porter moved CONTINUUM-170
Hi Jerome,
As you noticed, this plugin requires to be build with maven >= 2.0.8
because of some tests with encodings.
I'll add an enforcer rule as Benjamin proposed.
Arnaud
On Mon, Mar 31, 2008 at 12:55 PM, Jerome Lacoste
<[EMAIL PROTECTED]> wrote:
> On Fri, Mar 28, 2008 at 2:37 AM, Arnaud HER
On Wed, Apr 2, 2008 at 10:18 AM, <[EMAIL PROTECTED]> wrote:
>
> Ran 209rc6 and as a side effect the site-plugin version got resolved to
> 2.0-beta-6 which gave me the following problem:
...
>
> [INFO] [site:attach-descriptor]
> [DEBUG] Mapped url: /tmp/dnbnorapi-trunk/src/site to relative path:
I've had problems with beta-6 too - I wonder if we should stick with
beta-5 in 2.0.9?
I'm unsure why 2.0.8 was using beta-5 while 2.0.9 uses beta-6, as
David said that it was not specified in his POMs on IRC.
Cheers,
Brett
On 02/04/2008, at 7:18 PM, [EMAIL PROTECTED] wrote:
Ran 209rc6 a
Ran 209rc6 and as a side effect the site-plugin version got resolved to
2.0-beta-6 which gave me the following problem:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6:attach-descriptor'
-->
[DEBUG] (f) artifact = no.dnbnor.api:api:pom:1.3-SNAPSHOT
[DEBUG]
21 matches
Mail list logo
