On 18 February 2013 00:50, Gabriele Catania wrote:
> The problem here is that the maven-eclipse-plugin's to-maven mojo, which is
> intended to serve as the default tool to create maven artifact from eclipse
> distributions
Here is where you are reasoning is incorrect.
"to-maven" was always a sto
+1 (non-binding) (tested with two simple multi-module projects,
however I already disabled the aggregation report because of the
doubled entries).
Regards Mirko
On Sun, Feb 17, 2013 at 3:48 PM, Dennis Lundberg wrote:
> Hi,
>
> We solved N issues:
> http://jira.codehaus.org/secure/ReleaseNote.jsp
Sorry.
Now fixed.
The issue was with r1444046. (using locally git svn which doesn't like
empty directories)
2013/2/17 Dennis Lundberg :
> Hi Olivier,
>
> This commit seems to have broken the IT-buils.
> I'm not sure if this commit was an attempt to fix the problem, or just
> adding an IT to highl
Hi,
We solved N issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&styleName=Html&version=18318
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11127&status=1
Staging repo:
https://repository.apache.org/con
Gabriele
classifier always comes after the version e.g:
artifact-name-1.0-bin.jar
artifact-name-1.0-dev.jar
artifact-name-1.0-prod.jar
>From the above artifact names, classifiers can be located between the version
>and extension name of the artifact.
It appears that in this specific corner case th
Hi Olivier,
This commit seems to have broken the IT-buils.
I'm not sure if this commit was an attempt to fix the problem, or just
adding an IT to highlight the problem...
On 2013-02-08 16:06, ol...@apache.org wrote:
> Author: olamy
> Date: Fri Feb 8 15:06:56 2013
> New Revision: 1444045
>
> URL
