I rebased the ITs for Maven I have and I notice now that the setup I had now
fails to run ITs in parallel.
I do a touchstone build on Java 1.5, and then run Java 1.6 and 1.7 in parallel.
This no longer works as it seems some tests are messing around with the local
repository and cause failures
We solved 4 issues:
** Bug
* [MSHADE-103] - maven-shade-plugin does not resolve from
user-defined repositories
* [MSHADE-124] - Need better plan for getting
dependency-reduced-pom.xml out of basedir
* [MSHADE-130] - Mark mojo as threadSafe for parallel builds
** New Feature
* [MSH
2012/8/31 Benson Margulies :
> OK, now that I've cleaned up my previous mistake, I'll ask: is it a
> good time to actually do the 2.0 release?
yes ! it's always good time to release :-)
>
> -
> To unsubscribe, e-mail: dev-unsubscr.
why not, the changes are good and it's a mature plugin now.
LieGrue,
strub
- Original Message -
> From: Benson Margulies
> To: Maven Developers List
> Cc:
> Sent: Friday, August 31, 2012 8:02 PM
> Subject: Is it, in fact, time for maven-shade-plugin 2.0?
>
> OK, now that I've clea
OK, now that I've cleaned up my previous mistake, I'll ask: is it a
good time to actually do the 2.0 release?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
This vote is cancelled due to my being confused. Stand by for a 2.0.
On Fri, Aug 31, 2012 at 1:25 PM, Benson Margulies wrote:
> We solved 2 issues:
>
> ** Bug
> * [MSHADE-124] - Need better plan for getting
> dependency-reduced-pom.xml out of basedir
> * [MSHADE-130] - Mark mojo as threa
On Fri, Aug 31, 2012 at 1:44 PM, Olivier Lamy wrote:
> You tag from trunk.
> AFAIK there are other issues to include (marked closed for 2.0:
> MSHADE-103 and MSHADE-112)
> Some weeks ago, we agree to bump version to 2.0 due to a non backward
> compatible change (see http://markmail.org/message/ywi
You tag from trunk.
AFAIK there are other issues to include (marked closed for 2.0:
MSHADE-103 and MSHADE-112)
Some weeks ago, we agree to bump version to 2.0 due to a non backward
compatible change (see http://markmail.org/message/ywiw2mak7ltgo3qs )
2012/8/31 Benson Margulies :
> We solved 2 issu
Hi folks!
I need a bit feedback about forcing mojo execution in incremental builds [1].
As already explained, the main problem in this area is that some plugins (e.g.
maven-compiler-plugin) already have some kind of incremental build logic, but
do this way too lazily (see 'Rational' in the link
We solved 2 issues:
** Bug
* [MSHADE-124] - Need better plan for getting
dependency-reduced-pom.xml out of basedir
* [MSHADE-130] - Mark mojo as threadSafe for parallel builds
There are still plenty more fish in this sea.
Stating repo:
https://repository.apache.org/content/repositories/
I cannot currently get to maven.apache.org to look at the cheat-sheet
and remember all the release procedure steps. So it's out there on
repository.apache.org, and I'll finish the job as soon as I can.
-
To unsubscribe, e-mail: de
I bumped to 2.0 due to non backward compatible change in Shader interface.
See
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/Shader.java?r1=1367221&r2=1367220&pathrev=1367221
2012/8/31 :
> Author: bimargulies
> Date: Fri Aug 31 1
> Btw, while we are at it please all make sure that your svn:eol-style is set
> up correctly [1]. That is often missing as well.
That should already be fixed. But I guess others have been in that
state of mind as well:-)
/Anders
>
>
> LieGrue,
> strub
>
>
>
> [1] http://www.apache.org/dev/s
In SVN you need to do this an all subfolders afaik.
Btw, while we are at it please all make sure that your svn:eol-style is set up
correctly [1]. That is often missing as well.
LieGrue,
strub
[1] http://www.apache.org/dev/svn-eol-style.txt
- Original Message -
> From: Anders Hamma
.git
.gitignores
as well.
LieGrue,
strub
- Original Message -
> From: Tony Chemit
> To: dev@maven.apache.org
> Cc:
> Sent: Friday, August 31, 2012 2:39 PM
> Subject: Re: svn:ignore
>
> On Fri, 31 Aug 2012 14:25:27 +0200
> Anders Hammar wrote:
>
>> Doing some reading in the deve
2012/8/31 Anders Hammar :
> Just to verify:
> The idea is to set this property on the "root" folder of any Maven
> project, right? Not on all sub-folders as well? The document says "on
> the directory".
with svn that must be on all projects (ie all plugins etc...) for idea
*.iml are generated for a
Just to verify:
The idea is to set this property on the "root" folder of any Maven
project, right? Not on all sub-folders as well? The document says "on
the directory".
/Anders
On Fri, Aug 31, 2012 at 2:42 PM, Olivier Lamy wrote:
> 2012/8/31 Anders Hammar :
>> Doing some reading in the developer
Yes, working.
Thanks,
/Anders
On Fri, Aug 31, 2012 at 2:32 PM, Arnaud Héritier wrote:
> I found (afloom) :-)
> I was int trouble with the new xircles UI.
>
> it should be good now
>
> cheers
>
> On Fri, Aug 31, 2012 at 2:30 PM, Arnaud Héritier wrote:
>> We need to add you in the maven developer
2012/8/31 Anders Hammar :
> Doing some reading in the developer section, I see that the example
> svnignores ([1]) doesn't really match what seems to be applied to svn.
> Is there a recommended value for the svn:ignore property? I'd be happy
> to update [1] with that.
Sure feel free to update the d
On Fri, 31 Aug 2012 14:25:27 +0200
Anders Hammar wrote:
> Doing some reading in the developer section, I see that the example
> svnignores ([1]) doesn't really match what seems to be applied to svn.
> Is there a recommended value for the svn:ignore property? I'd be happy
> to update [1] with that
I found (afloom) :-)
I was int trouble with the new xircles UI.
it should be good now
cheers
On Fri, Aug 31, 2012 at 2:30 PM, Arnaud Héritier wrote:
> We need to add you in the maven developers group.
> what is your identifier ?
>
> Arnaud
>
> On Fri, Aug 31, 2012 at 2:05 PM, Anders Hammar wro
We need to add you in the maven developers group.
what is your identifier ?
Arnaud
On Fri, Aug 31, 2012 at 2:05 PM, Anders Hammar wrote:
> What kind of privs should I have in (Codehaus) JIRA for the Maven
> projects there (as a committer)? I should be be able to edit tickets,
> right? Well, I do
Doing some reading in the developer section, I see that the example
svnignores ([1]) doesn't really match what seems to be applied to svn.
Is there a recommended value for the svn:ignore property? I'd be happy
to update [1] with that.
Currently it has an example of:
target
*~
*.log
.classpath
.pro
What kind of privs should I have in (Codehaus) JIRA for the Maven
projects there (as a committer)? I should be be able to edit tickets,
right? Well, I don't... Is there something that needs to be fixed
manually by someone?
/Anders
--
On Wed, 29 Aug 2012 19:18:36 +0200
Stephane Nicoll wrote:
+1,
looks fine to me,
thanks,
tony.
> Hi,
>
> We solved 7 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132&styleName=Html&version=18269
>
> There are still around 15 issues left in JIRA:
> http://jira.codehau
I've created
https://jira.codehaus.org/browse/MSHARED-239
to cover this.
LieGrue,
strub
- Original Message -
> From: Aleksandar Kurtakov
> To: Maven Developers List
> Cc:
> Sent: Friday, August 31, 2012 8:46 AM
> Subject: Re: Any maven-shared or maven-core release pending?
>
> -
26 matches
Mail list logo
