On Tue, Feb 14, 2012 at 7:46 PM, Stephen Connolly
wrote:
> And he didn't replace Y.Z either ;-)
I blame sleep deprivation.
Hopefully I didn't stuff up anything else of the process...
-
To unsubscribe, e-mail: dev-unsubscr...@mav
And he didn't replace Y.Z either ;-)
On 14 February 2012 03:02, Barrie Treloar wrote:
> On Tue, Feb 14, 2012 at 12:46 PM, Barrie Treloar wrote:
>> Hi,
>> The vote has passed with the following result :
>>
>> +1 (binding): Barrie Treloar, Benson Margulies, Olivier Lamy, Hervé Boutemy
>> +1 (non b
Hi Barrie!
the version X.Y needed to be replaced as well :P At a first sight, it
looked spam :D
All the best, have a nice day,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Tue, Feb 14, 2012 at 4
On Tue, Feb 14, 2012 at 12:46 PM, Barrie Treloar wrote:
> Hi,
> The vote has passed with the following result :
>
> +1 (binding): Barrie Treloar, Benson Margulies, Olivier Lamy, Hervé Boutemy
> +1 (non binding): Robert Scholte
>
> I will promote the artifacts to the central repo.
Apologies for no
+1
Hervé
Le vendredi 13 janvier 2012 09:52:34 Barrie Treloar a écrit :
> Hi,
>
> We solved 25 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&version=162
> 40
>
> There are still a large backlog of issues left in JIRA: (extra support
> would be appreciated)
> http://j
+1
2012/1/19 Barrie Treloar :
> I'm going to need more +1 to push this through.
> From the other threads it looks like mostly everyone else is using intellij.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For
+1
On Jan 19, 2012, at 3:55 PM, Barrie Treloar wrote:
> I'm going to need more +1 to push this through.
> From the other threads it looks like mostly everyone else is using intellij.
>
> -
> To unsubscribe, e-mail: dev-unsubscr.
I'm going to need more +1 to push this through.
>From the other threads it looks like mostly everyone else is using intellij.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@mav
The marriage of eclipse and maven poses fundamental challenges that
don't exist for Intellij or Netbeans.
Of the three major Java IDE's, only Eclipse incorporates its own
classpath and compiler system. IJ and NB 'just run maven' and analyze
the output for display. Eclipse, on the other hand, actua
On Mon, Jan 16, 2012 at 12:34 AM, Barrie Treloar wrote:
> 2012/1/16 Arnaud Héritier :
> > Thanks a lot for this hard wok Barrie
> >
> > yes it was my problem too Robert.
> > ITs are now very difficult to use/maintain and sadly are covering only
> the
> > fact that what we generate is always the s
2012/1/16 Arnaud Héritier :
> Thanks a lot for this hard wok Barrie
>
> yes it was my problem too Robert.
> ITs are now very difficult to use/maintain and sadly are covering only the
> fact that what we generate is always the same and not that it is working in
> eclipse.
> As far as I remember this
Thanks a lot for this hard wok Barrie
yes it was my problem too Robert.
ITs are now very difficult to use/maintain and sadly are covering only the
fact that what we generate is always the same and not that it is working in
eclipse.
As far as I remember this is the larger plugin we have in lines of
Hi Barrie,
thanks for picking this up.
I've fixed some critical issues we faced during development on one of my
projects, but lost motivation to continue because of the current structure
of the ITs, which take ages to run.
Anyhow, here's my +1
-Robert
On Fri, 13 Jan 2012 00:22:34 +0100, B
Hi,
We solved 25 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&version=16240
There are still a large backlog of issues left in JIRA: (extra support
would be appreciated)
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MECLIP
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Arnaud Héritier,
Barrie Treloar
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
--
+1
Apologies for the delay.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Mon, Feb 22, 2010 at 4:28 AM, Jason van Zyl wrote:
> +1
>
> On Feb 21, 2010, at 8:32 PM, Benjamin Bentmann wrote:
>
> > Hi,
> >
> > We solved 14 issues:
> >
> http://jira.codeh
+1
On Feb 21, 2010, at 8:32 PM, Benjamin Bentmann wrote:
> Hi,
>
> We solved 14 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&version=14813
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=1113
Hi,
We solved 14 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&version=14813
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
Staging repo:
https://repository.apache.org/content/reposito
Hi,
The vote has passed with the following result :
+1 (binding): Benjamin Bentmann, Arnaud Heritier, Olivier Lamy
+1 (non binding): Nicolas Deloof, Barrie Treloar
I will promote the artifacts to the central repo.
-
To unsubscri
+1
--
Olivier
2009/6/13 Barrie Treloar :
> The vote is still missing some binding numbers, currently there are:
>
> +1 (binding): Benjamin Bentmann, Arnaud Heritier
> +1 (non binding): Nicolas Deloof, Barrie Treloar
>
> -
> To uns
The vote is still missing some binding numbers, currently there are:
+1 (binding): Benjamin Bentmann, Arnaud Heritier
+1 (non binding): Nicolas Deloof, Barrie Treloar
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
On Wed, Jun 10, 2009 at 8:31 PM, Vincent
Siveton wrote:
> 2009/6/9, nicolas de loof :
>> +1
>> Could we move the assembly plugin configuration to the plugins parent /
>> apache-release profile for future plugin releases to conform ASF rules ?
>
> I tried to add it on Doxia, and I think we need to
2009/6/9, nicolas de loof :
> +1
> Could we move the assembly plugin configuration to the plugins parent /
> apache-release profile for future plugin releases to conform ASF rules ?
I tried to add it on Doxia, and I think we need to add this stuff in
the release profile.
The more important thin
+1
Could we move the assembly plugin configuration to the plugins parent /
apache-release profile for future plugin releases to conform ASF rules ?
2009/6/8 Arnaud HERITIER
> +1Thanks a lot for your help
>
> Arnaud
>
> On Mon, Jun 8, 2009 at 10:30 PM, Benjamin Bentmann <
> benjamin.bentm...@udo.
On Tue, Jun 9, 2009 at 6:00 AM, Benjamin
Bentmann wrote:
> Barrie Treloar wrote:
>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-staging-008/
>
> +1
>
>> Staging site:
>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7/
>
> The staging site refers to plugin v
+1Thanks a lot for your help
Arnaud
On Mon, Jun 8, 2009 at 10:30 PM, Benjamin Bentmann <
benjamin.bentm...@udo.edu> wrote:
> Barrie Treloar wrote:
>
> Staging repo:
>> https://repository.apache.org/content/repositories/maven-staging-008/
>>
>
> +1
>
> Staging site:
>> http://maven.apache.org/p
Barrie Treloar wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-008/
+1
Staging site:
http://maven.apache.org/plugins/maven-eclipse-plugin-2.7/
The staging site refers to plugin version 2.8-SNAPSHOT. Just keep in
mind to deploy the final site from the
(source-release should be correct now)
Hi,
We solved 11 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&styleName=Html&version=15130
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=11133&resolu
On Sun, Jun 7, 2009 at 10:15 PM, Benjamin
Bentmann wrote:
> Barrie Treloar wrote:
>
>> * Added source-release assembly
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-staging-006/
>
> It appears the source-release packages are missing the LICENSE and NOTICE
> files [
Barrie Treloar wrote:
* Added source-release assembly
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-006/
It appears the source-release packages are missing the LICENSE and
NOTICE files [0].
The descriptor you copied isn't fully worked out yet. For a plugin,
Ok here are the steps I took:
Copied
https://svn.apache.org/repos/asf/maven/resources/trunk/apache-source-release-assembly-descriptor/src/main/resources/assemblies/source-release.xml
to src/assemble/
Modified pom to include
maven-assembly-plugin
Note:
* Changed wording of index.html as per Arnaud suggestion.
* Added source-release assembly
Hi,
We solved 11 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&styleName=Html&version=15130
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/
If you need an example, you can look at what I did for the ant tasks [1]. The
same assembly should work fine for the eclipse plugin. You probably just want
to make minor changes for any files that do/don't exist.
[1]http://svn.apache.org/repos/asf/maven/ant-tasks/tags/maven-ant-tasks-2.0.10/s
My understanding of the problems that are being had with the assembly stuff
is around releasing multi-module projects (e.g. surefire, enforcer). If all
you are releasing is a single module (e.g. maven-eclipse-plugin), then
assembly does exactly what you want right now.
The issue that John and Bri
Seriously just use the assembly plugin to zip up the source folder,
excluding target. There are several examples in the related threads.
On Thu, Jun 4, 2009 at 5:04 PM, Arnaud HERITIER wrote:
> I thought we needed to have a fix in the assembly plugin to be able to
> release with ASF rules.If we
I thought we needed to have a fix in the assembly plugin to be able to
release with ASF rules.If we can do it with just some local changes in our
pom, we have to do it.
However I agree with Barry and we cannot loose too many time to do the
release.
Is there someone who can help us to setup the ecl
On Fri, Jun 5, 2009 at 7:13 AM, Brian Fox wrote:
> On Thu, Jun 4, 2009 at 11:43 AM, Benjamin Bentmann <
> benjamin.bentm...@udo.edu> wrote:
>
>> Arnaud HERITIER wrote:
>>
>> I think there's no value to block all releases, waiting for this fix.I
>>> agree, support this change, but it won't help ou
On Thu, Jun 4, 2009 at 11:43 AM, Benjamin Bentmann <
benjamin.bentm...@udo.edu> wrote:
> Arnaud HERITIER wrote:
>
> I think there's no value to block all releases, waiting for this fix.I
>> agree, support this change, but it won't help our users to have them
>> waiting
>> all our releases for sev
Arnaud HERITIER wrote:
I think there's no value to block all releases, waiting for this fix.I
agree, support this change, but it won't help our users to have them waiting
all our releases for several weeks.
I don't really understand why fixing a project to produce a proper
source bundle (e.g.
I believe adding the previous assembly plugin release with:
src
is sufficient for our plugins. The purpose of the updated plugin is to
make it possible to put that in a parent POM without generating
unwanted assemblies and ensuring the content is correct rather than
duplicating the abo
On Jun 3, 2009, at 4:36 PM, Barrie Treloar wrote:
On Thu, Jun 4, 2009 at 8:54 AM, David Jencks
wrote:
On Jun 3, 2009, at 3:55 PM, Arnaud HERITIER wrote:
To be conform with ASF requirements, I understand that we have to
wait the
new assembly plugin to be able to produce the new sources di
On Thu, Jun 4, 2009 at 8:54 AM, David Jencks wrote:
>
> On Jun 3, 2009, at 3:55 PM, Arnaud HERITIER wrote:
>
>> To be conform with ASF requirements, I understand that we have to wait the
>> new assembly plugin to be able to produce the new sources distro. There
>> are
>> already 3 or 4 attempts to
On Jun 3, 2009, at 3:55 PM, Arnaud HERITIER wrote:
To be conform with ASF requirements, I understand that we have to
wait the
new assembly plugin to be able to produce the new sources distro.
There are
already 3 or 4 attempts to vote the release and it's not yet ended.
I think also that oth
To be conform with ASF requirements, I understand that we have to wait the
new assembly plugin to be able to produce the new sources distro. There are
already 3 or 4 attempts to vote the release and it's not yet ended.
I think also that others ASF projects using Maven won't wait for this fix if
the
On Thu, Jun 4, 2009 at 7:18 AM, Benjamin Bentmann
wrote:
> Barrie Treloar wrote:
>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-staging-005/
>
> -1
>
> As far as I understand the recent discussions about proper releases [0] and
> the current docs [1], we are require
The new assembly plugin makes it trivially easy to have the release
profile build the source distro, which is really amazingly nice.
However you can easily have a separate profile to run an earlier
assembly plugin to construct just the required source distro and run
it with -N so it only r
I think there's no value to block all releases, waiting for this fix.I
agree, support this change, but it won't help our users to have them waiting
all our releases for several weeks.
We are doing it like that (yes badly) for a long time now. Thus I don't
think that one or two releases will change
Barrie Treloar wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-005/
-1
As far as I understand the recent discussions about proper releases [0]
and the current docs [1], we are required to provide "a source package,
which must be sufficient for a user to
+1
Just a remark about the note on the home page. I think it's better to say
that "Starting at version 2.6, *by default,* the generated .classpath now
includes "... And you can add a link on the page which explains how to
change it.
Arnaud
Cheers,
Arnaud
# Arnaud Héritier
# http://blog.aheriti
Hi,
We solved 11 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&styleName=Html&version=15130
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=11133&resolution=-1&sorter/field=updated&sorter/orde
2009, 11h16mn 26s
Objet : Re : Maven eclipse plugin 2.6 regression with xmlbeans (was: [VOTE]
Release Maven eclipse plugin version 2.6)
I've submitted a bug: MECLIPSE-549
- Message d'origine
De : Julien HENRY
À : Maven Developers List
Envoyé le : Mercredi, 8 Avril 2009, 10
I've submitted a bug: MECLIPSE-549
- Message d'origine
De : Julien HENRY
À : Maven Developers List
Envoyé le : Mercredi, 8 Avril 2009, 10h37mn 07s
Objet : Re : [VOTE] Release Maven eclipse plugin version 2.6
Same problem for me.
- Message d'origine
De :
I just would like to repeat a good practice when you use Maven :- lock
plugins versions in your pluginsManagement.
I'll try to find some hours this week to work on the issues you discovered.
For next vote to release the plugin we'll put in copy the users list and
I'll hope you'll be able to valida
Same problem for me.
- Message d'origine
De : Barrie Treloar
À : Maven Developers List
Envoyé le : Mardi, 24 Mars 2009, 3h13mn 30s
Objet : Re: [VOTE] Release Maven eclipse plugin version 2.6
Does anyone else use xmlbeans in their projects?
Could they check that generated so
On Fri, Mar 27, 2009 at 5:45 AM, Barrie Treloar wrote:
> There is definitely a defect introduced with setting inclusions to
> **/*.java (MECLIPSE-443 added inclusions) for Apsect developers (see
> MECLIPSE-538).
>
> But that shouldn't stop the release.
I'd rather had it would've stopped the relea
On Fri, Mar 27, 2009 at 5:21 PM, Barrie Treloar wrote:
> On Fri, Mar 27, 2009 at 4:48 PM, Arnaud HERITIER wrote:
>> No, there's no reason to stop it.We'll publish a 1.6.1 in few days if
>> necessary
>
> Except the current vote count :)
>
> +1 (binding):
> aherit...@gmail.com
benjamin.bentm...@ud
Barrie Treloar wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-52acfb2f215fcf/
Staging site:
http://maven.apache.org/plugins/maven-eclipse-plugin-2.6/
+1
Benjamin
-
To unsubscribe, e-m
Ok I just wasn't sure because there was lots of talk about eclipse
plugin fixes in parallel so I lost track.
-Original Message-
From: Barrie Treloar [mailto:baerr...@gmail.com]
Sent: Friday, March 27, 2009 2:52 AM
To: Maven Developers List
Subject: Re: Re : Re : [VOTE] Release
+1
--
Olivier
2009/3/27 Barrie Treloar :
> On Fri, Mar 27, 2009 at 1:15 PM, Brian E. Fox
> wrote:
>> Has this vote been officially cancelled?
>
> No, why?
>
> There is definitely a defect introduced with setting inclusions to
> **/*.java (MECLIPSE-443 added inclusions) for Apsect developers (see
If I do +3 ?? :-)
On Fri, Mar 27, 2009 at 7:51 AM, Barrie Treloar wrote:
> On Fri, Mar 27, 2009 at 4:48 PM, Arnaud HERITIER
> wrote:
> > No, there's no reason to stop it.We'll publish a 1.6.1 in few days if
> > necessary
>
> Except the current vote count :)
>
> +1 (binding):
> aherit...@gmail.
On Fri, Mar 27, 2009 at 4:48 PM, Arnaud HERITIER wrote:
> No, there's no reason to stop it.We'll publish a 1.6.1 in few days if
> necessary
Except the current vote count :)
+1 (binding):
aherit...@gmail.com
+1 (non binding):
belling...@gmail.com
nicolas.del...@gmail.com
baerr...@gmail.c
No, there's no reason to stop it.We'll publish a 1.6.1 in few days if
necessary
Arnaud
On Fri, Mar 27, 2009 at 4:45 AM, Barrie Treloar wrote:
> On Fri, Mar 27, 2009 at 1:15 PM, Brian E. Fox
> wrote:
> > Has this vote been officially cancelled?
>
> No, why?
>
> There is definitely a defect intr
On Fri, Mar 27, 2009 at 1:15 PM, Brian E. Fox wrote:
> Has this vote been officially cancelled?
No, why?
There is definitely a defect introduced with setting inclusions to
**/*.java (MECLIPSE-443 added inclusions) for Apsect developers (see
MECLIPSE-538).
But that shouldn't stop the release.
I
Has this vote been officially cancelled?
-Original Message-
From: Julien HENRY [mailto:henr...@yahoo.fr]
Sent: Tuesday, March 24, 2009 11:27 AM
To: Maven Developers List
Subject: Re : Re : [VOTE] Release Maven eclipse plugin version 2.6
Done:
http://jira.codehaus.org/browse/MECLIPSE
yes
- Message d'origine
De : Arnaud HERITIER
À : Maven Developers List
Envoyé le : Mardi, 24 Mars 2009, 14h35mn 20s
Objet : Re: Re : [VOTE] Release Maven eclipse plugin version 2.6
did you try to remove your 2.6 copy locally to retry to download the pom ?
2009/3/24 Julien
Done:
http://jira.codehaus.org/browse/MECLIPSE-536
- Message d'origine
De : Arnaud HERITIER
À : Maven Developers List
Envoyé le : Mardi, 24 Mars 2009, 10h23mn 10s
Objet : Re: Re : [VOTE] Release Maven eclipse plugin version 2.6
yes please.
2009/3/24 Julien HENRY
>
>
/central),
> staged-releases (
> https://repository.apache.org/content/repositories/maven-staging-52acfb2f215fcf/
> )
>
>
> [DEBUG] Using defaults for missing POM
> org.apache.maven.plugins:maven-eclipse-plugin:pom:2.6
> [DEBUG] Trying repository staged-releases
> [DEB
-eclipse-plugin-2.6.jar
[...]
Now only the JAR is downloaded and not the pom.xml.
Any idea?
Julien
----- Message d'origine ----
De : Barrie Treloar
À : Maven Developers List
Envoyé le : Mardi, 24 Mars 2009, 1h05mn 40s
Objet : [VOTE] Release Maven eclipse plugin version 2.6
Hi,
We so
ome: C:\j2sdk1.4.2_17\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>
> Do you want I open an issue in JIRA with full stack trace?
>
> Regards,
>
> Julien
>
"x86" Family: "windows"
Do you want I open an issue in JIRA with full stack trace?
Regards,
Julien
- Message d'origine
De : Barrie Treloar
À : Maven Developers List
Envoyé le : Mardi, 24 Mars 2009, 1h05mn 40s
Objet : [VOTE] Release Maven eclipse plugin versio
+1
On Tue, Mar 24, 2009 at 9:43 AM, Fabrice Bellingard wrote:
> +1
>
> - Fabrice
> belling...@apache.org
>
>
> On Tue, Mar 24, 2009 at 1:05 AM, Barrie Treloar
> wrote:
>
> > Hi,
> >
> > We solved 35 issues:
> >
> >
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14163&styleName=Html&
+1
- Fabrice
belling...@apache.org
On Tue, Mar 24, 2009 at 1:05 AM, Barrie Treloar wrote:
> Hi,
>
> We solved 35 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14163&styleName=Html&projectId=11133
>
> There remaining issues left in JIRA:
>
> http://jira.codehaus.org/secu
On Tue, Mar 24, 2009 at 12:43 PM, Barrie Treloar wrote:
> Does anyone else use xmlbeans in their projects?
> Could they check that generated sources get added to the classpath correctly.
>
> I'm noticing that they aren't.
> I'm not sure if that is a regression or a problem my end.
>
I'll take tha
Does anyone else use xmlbeans in their projects?
Could they check that generated sources get added to the classpath correctly.
I'm noticing that they aren't.
I'm not sure if that is a regression or a problem my end.
-
To unsubscr
+1
Arnaud
2009/3/24 Barrie Treloar
> Hi,
>
> We solved 35 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14163&styleName=Html&projectId=11133
>
> There remaining issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
>
>
Hi,
We solved 35 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14163&styleName=Html&projectId=11133
There remaining issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
Staging repo:
https://repository.apache.org/content/reposi
08 4:33 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER<[EMAIL PROTECTED]>
wrote:
Hi Jerome,
As you noticed, this plugin requires to be build with maven>= 2.0.8
because of some tests with encodin
e:
>
> > This only works on single module builds, the prerequisite field is not
> > inherited.
> >
> > -Original Message-
> > From: Jerome Lacoste [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, April 03, 2008 4:33 AM
> > To: Maven Developers Li
Rahul
Brian E. Fox wrote:
This only works on single module builds, the prerequisite field is not
inherited.
-Original Message-
From: Jerome Lacoste [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2008 4:33 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven Eclipse plugin v
nded for tools and isn't
> > > > inherited (making it not good for normal builds) but does apply at
> > > > runtime. In this instance, the prerequisite is the most appropriate
> way
> > > > to require the maven version.
> > > >
>
rerequisite is the most appropriate way
> > > to require the maven version.
> > >
> > >
> > > -Original Message-----
> > > From: Richard van Nieuwenhoven [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, April 03, 2008 6:08
normal builds) but does apply at
> > > > runtime. In this instance, the prerequisite is the most appropriate
> way
> > > > to require the maven version.
> > > >
> > > >
> > > > -Original Message-
> > > > Fro
ce, the prerequisite is the most appropriate
> way
> > > to require the maven version.
> > >
> > >
> > > -----Original Message-----
> > > From: Richard van Nieuwenhoven [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, April 03, 2008
Maven Developers List
Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Hi,
the requireMavenVersion also applies to the runtime, but 2.0.8 is just
required for the testing during the build. As far as i know not for the
runtime. We use the plugin in a lot of projects that are locke
OTECTED]
> Sent: Thursday, April 03, 2008 6:08 AM
> To: Maven Developers List
> Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
>
>
>
> Hi,
>
> the requireMavenVersion also applies to the runtime, but 2.0.8 is just
> required for the testing
IL PROTECTED]
> > Sent: Thursday, April 03, 2008 6:08 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
> >
> >
> >
> > Hi,
> >
> > the requireMavenVersion also applies to the runti
> To: Maven Developers List
> Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
>
>
>
> Hi,
>
> the requireMavenVersion also applies to the runtime, but 2.0.8 is just
> required for the testing during the build. As far as i know not for the
> runtime.
euwenhoven [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2008 6:08 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Hi,
the requireMavenVersion also applies to the runtime, but 2.0.8 is just
required for the testing during the build. As far as i know n
This only works on single module builds, the prerequisite field is not
inherited.
-Original Message-
From: Jerome Lacoste [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2008 4:33 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
On Wed, Apr
Hi,
the requireMavenVersion also applies to the runtime, but 2.0.8 is just
required for the testing during the build. As far as i know not for the
runtime. We use the plugin in a lot of projects that are locked to maven
2.0.7.
So please limit it only for the build time.
regards,
Ritchie
Jerom
ok thanks. I'll close the vote this evening and I'll release it.
I'll probably release a version 2.5.2 the next week.
cheers
arnaud
On Thu, Apr 3, 2008 at 10:32 AM, Jerome Lacoste
<[EMAIL PROTECTED]> wrote:
> On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > Hi Jer
On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> 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.
I had added a patch to the issue hat use
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 Fri, Mar 28, 2008 at 2:37 AM, Arnaud HERITIER <[EMAIL PROTECTED]>
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 maifests
>
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
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
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
1 - 100 of 151 matches
Mail list logo
