- Original Message -
From: Kristian Rosenvold kristian.rosenv...@gmail.com
To: Maven Developers List dev@maven.apache.org
Sent: Thursday, August 30, 2012 11:42:21 PM
Subject: Re: Removing unused code from maven-shared-utils
2012/8/30 Jason van Zyl ja...@tesla.io:
That is simply
- Original Message -
From: Kristian Rosenvold kristian.rosenv...@gmail.com
To: Maven Developers List dev@maven.apache.org
Sent: Friday, August 31, 2012 8:46:23 AM
Subject: Re: Any maven-shared or maven-core release pending?
Are you actively looking for external help in this
The Maven team is pleased to announce the release of the Maven Fluido
Skin, version 1.3.0
The Apache Maven Fluido Skin is an Apache Maven site skin built on top
of Twitter's bootstrap.
http://maven.apache.org/skins/maven-fluido-skin/
You should specify the version in site.xml:
project
...
I've created
https://jira.codehaus.org/browse/MSHARED-239
to cover this.
LieGrue,
strub
- Original Message -
From: Aleksandar Kurtakov akurt...@redhat.com
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Friday, August 31, 2012 8:46 AM
Subject: Re: Any maven-shared or
On Wed, 29 Aug 2012 19:18:36 +0200
Stephane Nicoll stephane.nic...@gmail.com wrote:
+1,
looks fine to me,
thanks,
tony.
Hi,
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132styleName=Htmlversion=18269
There are still around 15 issues left in JIRA:
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
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
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 and...@hammar.net 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,
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 aherit...@gmail.com 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,
On Fri, 31 Aug 2012 14:25:27 +0200
Anders Hammar and...@hammar.net 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
2012/8/31 Anders Hammar and...@hammar.net:
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
Yes, working.
Thanks,
/Anders
On Fri, Aug 31, 2012 at 2:32 PM, Arnaud Héritier aherit...@gmail.com 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 aherit...@gmail.com wrote:
We need to
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 ol...@apache.org wrote:
2012/8/31 Anders Hammar and...@hammar.net:
Doing
2012/8/31 Anders Hammar and...@hammar.net:
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
.git
.gitignores
as well.
LieGrue,
strub
- Original Message -
From: Tony Chemit che...@codelutin.com
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 and...@hammar.net wrote:
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
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]
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=1367221r2=1367220pathrev=1367221
2012/8/31 bimargul...@apache.org:
Author: bimargulies
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:
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:
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
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
On Fri, Aug 31, 2012 at 1:44 PM, Olivier Lamy ol...@apache.org 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
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 bimargul...@gmail.com wrote:
We solved 2 issues:
** Bug
* [MSHADE-124] - Need better plan for getting
dependency-reduced-pom.xml out of basedir
* [MSHADE-130] -
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
why not, the changes are good and it's a mature plugin now.
LieGrue,
strub
- Original Message -
From: Benson Margulies bimargul...@gmail.com
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Friday, August 31, 2012 8:02 PM
Subject: Is it, in fact, time for
2012/8/31 Benson Margulies bimargul...@gmail.com:
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,
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
*
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
29 matches
Mail list logo
