On Fri, Mar 28, 2008 at 9:38 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Niall Pemberton wrote:
> > On Tue, Feb 5, 2008 at 11:20 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> >> I have four issues left on my radar, that I'd like to solve or reject
> >> before doing the next release:
>
This RC has the following changes over RC4:
*Webdav 1.0-beta-2 instead of beta-1 (This fixes James' issue)
*The webdav extension version that is bundled in core can be
overridden by an extension element, thus no longer locking in the users.
This plays a little with the classloadin
>Unfortunately I think this has an unwanted side effect. Because you
>can only load an extension once in the build, it would mean if you
>wanted to override it, it would have to be in the root of the reactor
>build (or a parent of that). If you happen to declare it in the child,
>the super
On 29/03/2008, at 2:04 AM, John Casey wrote:
Here's a question:
Could we specify the wagon-webdav in the super-POM as a build
extension? Even if there are no project POMs in the current build,
the super POM should be built, right? Also, I would think (though
I'd have to investigate to be
+1
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Friday, March 28, 2008 6:40 PM
To: Maven Developers List
Subject: [VOTE] Release maven plugins parent 11 (take 2)
Hi
Another try to get the latest version of maven-source-plugin into our
toolchain and use the (
Hi
Another try to get the latest version of maven-source-plugin into our
toolchain and use the (even more) recently released maven-plugin-plugin
2.4.1, I'd like to release the plugins parent r642413 as version 11.
Source:
https://svn.apache.org/viewvc/maven/plugins/trunk/pom.xml?r1=587343&r2=
which tests ?
the unit tests when building on windows ?
Raphaël
2008/3/28, Brian E. Fox <[EMAIL PROTECTED]>:
> I'm having issues with the tests that need to be fixed first.
>
>
> -Original Message-
> From: Raphaël Piéroni [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 28, 2008 4:37 PM
Vote canceled, due to problems in plugin-plugin 2.4.
Dennis Lundberg wrote:
Hi
To get the latest version of maven-source-plugin into our toolchain and
use the recently release maven-plugin-plugin 2.4, I'd
like to release the plugins parent r638340 as version 11.
Source:
https://svn.apache.or
Niall Pemberton wrote:
On Tue, Feb 5, 2008 at 11:20 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
I have four issues left on my radar, that I'd like to solve or reject
before doing the next release:
Just wondering whether the release is likely soon or not?
Sorry, I wanted to wait for the r
I've committed a fix and integration tests for the issue (MNG-3221).
-john
On Mar 28, 2008, at 3:20 PM, John Casey wrote:
See my post in the eclipse plugin thread...I think it may be
related to the fix for MNG-3221. I'm trying to work up a test case
to see if I can debug it quickly.
-john
I'm having issues with the tests that need to be fixed first.
-Original Message-
From: Raphaël Piéroni [mailto:[EMAIL PROTECTED]
Sent: Friday, March 28, 2008 4:37 PM
To: Maven Developers List
Subject: releasing archetype plugin 2.0-alpha-3
Hi
If no one objects, i will call
a vote for r
I think I've found a fix for the issue in the 2.0.9 code. I've
committed it along with two new integration tests under the issue
MNG-3221. Hopefully there will be a new RC soon that you can check
against.
Thanks,
-john
On Mar 28, 2008, at 6:06 AM, nicolas de loof wrote:
I found the caus
Hi
If no one objects, i will call
a vote for releasing the
mentioned version saturday
or sunday.
Regards,
Raphaël
See my post in the eclipse plugin thread...I think it may be related
to the fix for MNG-3221. I'm trying to work up a test case to see if
I can debug it quickly.
-john
On Mar 28, 2008, at 2:16 PM, Brian E. Fox wrote:
I think someone else commented about a similar problem on the eclipse
vot
I think the issue probably has something to do with the fix I added
to maven-core for MNG-3221. I'm looking into that code now to see if
I can figure out how the modification breaks this case.
-john
On Mar 28, 2008, at 6:06 AM, nicolas de loof wrote:
I found the cause of this issue :
As I
I think someone else commented about a similar problem on the eclipse
vote thread. I'm honestly not sure what to make of it without a test
case. Anyone else have more info?
-Original Message-
From: Sejal Patel [mailto:[EMAIL PROTECTED]
Sent: Friday, March 28, 2008 1:57 PM
To: Maven Develo
Ok well I've run into a very wierd problem dealing with the eclipse plugin
and maven RC4. Thus I'm going to have to vote -1 on this version as well. I
haven't opened up a bug report yet (been quite a busy day) but I will. I'll
give the quick rundown though.
I have a reactor based project (8 module
It's on my todo list.
I began to prepare a big refactoring/rewrite of this plugin.
it will be a 3.0. I'll give more details about what I have in mind in some weeks
cheers
arnaud
On Fri, Mar 28, 2008 at 6:03 PM, nicolas de loof <[EMAIL PROTECTED]> wrote:
> +1
>
> please cleanup the plugin that is
+1
please cleanup the plugin that is allready not so simple to maintain ;-p
2008/3/28, Richard van Nieuwenhoven <[EMAIL PROTECTED]>:
>
> Hi,
>
> just created the JIRA http://jira.codehaus.org/browse/MECLIPSE-415 and
> attached the patch. This problem seems to be connected to the wrongly
> used e
Hi,
just created the JIRA http://jira.codehaus.org/browse/MECLIPSE-415 and
attached the patch. This problem seems to be connected to the wrongly
used executedProject parameter and maven 2.0.9.
The stage thing is that "testProject11" fails when i remove the usage of
the executedProject.
Also i am
Hrm, if it allows overrides and still works for deploy:deploy-file, this
might be the safest approach.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, March 28, 2008 11:04 AM
To: Maven Developers List
Subject: Re: Wagon changes and WebDAV
Here's a question:
C
Here's a question:
Could we specify the wagon-webdav in the super-POM as a build
extension? Even if there are no project POMs in the current build,
the super POM should be built, right? Also, I would think (though I'd
have to investigate to be sure) that respecifying the wagon-webdav
buil
It sounds like a fine idea to me. Not sure what else to say.
-john
On Mar 28, 2008, at 7:11 AM, Benjamin Bentmann wrote:
If I don't miss an aspect, we could narrow the exclusions for the
shade
plugin to
org.codehaus.plexus.util.xml.pull.Xml*
to allow plugins to benefit from updates to the M
On 28/03/2008, at 9:41 PM, Brett Porter wrote:
I've taken a look at the code and found two problems:
a) the wagon in core was reverted to beta-1, which is probably the
root of James' problems. beta-2 corrects the redirects and has been
stable for some time. I presume this was an accident a
Today is a busy day unfortunately (fridays always are), I won't be able to
run through our 200+ project suite with the new version until Monday.
On Fri, Mar 28, 2008 at 5:28 AM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Thanks !
> I have tested this rc on some corporate builds and all builds are
Ok. Thx a lot. I'll fix it with the executedProject the next week.
Arnaud
On Fri, Mar 28, 2008 at 12:16 PM, Richard van Nieuwenhoven <[EMAIL PROTECTED]>
wrote:
> hmmm, that seems to be a relict of the old usage of the workspace
> variable usage (that Arnaud removed). Later today i will create a
hmmm, that seems to be a relict of the old usage of the workspace
variable usage (that Arnaud removed). Later today i will create an jira
issue and a patch. (this should not be hard to find).
Ritchie
nicolas de loof wrote:
> Also had this issue since 2.5-SNAPSHOTs, but never took the time to repo
If I don't miss an aspect, we could narrow the exclusions for the shade
plugin to
org.codehaus.plexus.util.xml.pull.Xml*
to allow plugins to benefit from updates to the MXParser and MXSerializer
independently of Maven.
What do you think?
No thoughts on this?
Benjamin
--
Also had this issue since 2.5-SNAPSHOTs, but never took the time to report
in Jira :-/
Setting eclipse.projectDir=${basedir} in the POM eclipse-plugin
configuration solves this, but this is only a workaround.
Nicolas.
2008/3/28, Arnaud HERITIER <[EMAIL PROTECTED]>:
>
> Hi all,
>
> I just disco
I've taken a look at the code and found two problems:
a) the wagon in core was reverted to beta-1, which is probably the
root of James' problems. beta-2 corrects the redirects and has been
stable for some time. I presume this was an accident as it came in
with Milos toolkits commit. Milos -
On 28/03/2008, nicolas de loof <[EMAIL PROTECTED]> wrote:
>
> I found the cause of this issue :
>
> As I added the SysdeoMojo.generate execution to this setup profile, two
> plugins (eclipse + sysdeo-tomcat) request for a forked @execute
> phase="generate-resources".
>
> In both case, maven remove
I found the cause of this issue :
As I added the SysdeoMojo.generate execution to this setup profile, two
plugins (eclipse + sysdeo-tomcat) request for a forked @execute
phase="generate-resources".
In both case, maven remove the requesting plugin from the forked lifecycle
to prevent recursive cal
On Fri, Mar 28, 2008 at 10:09 AM, nicolas de loof <[EMAIL PROTECTED]> wrote:
> I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with latest maven
> 2.0.9 RC4 :
>
> I've set a custom profile in my corporate POM to setup eclipse. It runs the
> validate phase and attach eclipse:eclipse pl
Hi all,
I just discovered a bug, or an hidden feature in 2.5 :-)
Richard, I think it is related to MECLIPSE-344.
I store my projects in a directory which isn't my eclipse workspace.
If I define the workspace attribute to be able to read its settings,
when I call eclipse:eclipse, my projec
Thanks !
I have tested this rc on some corporate builds and all builds are fine.
Here my : +1.
--
Olivier
2008/3/28, Brian E. Fox <[EMAIL PROTECTED]>:
> RC4 corrects the version issue identified by Olivier and the Duplicate
> artifacts exception identified by several testers. It's staged at:
>
We ran our tricky builds with RC-4 and everything seems OK.
Some of our builds have locked down plugin versions to earlier than
specified in 2.0.9-RC4 and they did not seem to break
-Stephen
On Fri, Mar 28, 2008 at 6:19 AM, James William Dumay <[EMAIL PROTECTED]>
wrote:
> Brian,
> We ran most o
I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with latest maven
2.0.9 RC4 :
I've set a custom profile in my corporate POM to setup eclipse. It runs the
validate phase and attach eclipse:eclipse plugin goal to this phase. Using
this, a fresh SVN checkout can configure eclipse by runnin
Hi,
here is my +1
Thanks for the fast release!
Ritchie
Arnaud HERITIER wrote:
> Hi,
>
> Since the 2.5 release we did 10 days ago, we solved 3 annoying issues:
> * [MECLIPSE-266] - plugin applies java facet to ear project
> * [MECLIPSE-411] - manifest property usage is only for ogsi m
38 matches
Mail list logo
