really, here is the link...
https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-check-source-release.html
Le mardi 10 décembre 2013 23:50:26 Hervé BOUTEMY a écrit :
> (better with link)
> /> Do we have any metrics on how many mono- to multi- module builds we
> have?/
(better with link)
/> Do we have any metrics on how many mono- to multi- module builds we have?/
indirectly, yes: dist-tool [1] tells we have 101 releases
plugins, shared, skins, poms, reporting and resources are mono-modules:
44+20+6+2+3+5 = 80
other ones are multi-modules: 101-80 = 21 (-3 gi
> Do we have any metrics on how many mono- to multi- module builds we have?
indirectly, yes: dist-tool [1] tells we have 101 releases
plugins, shared, skins, poms, reporting and resources are mono-modules:
44+20+6+2+3+5 = 80
other ones are multi-modules: 101-80 = 21 (-3 given we have Maven 2.0,
Hi,
We solved 11 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17492&styleName=Html&projectId=11085
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11085&status=1
Staging repo:
https://repository.apache.org/c
Am 2013-12-10 01:56, schrieb Hervé BOUTEMY:
on my machine, build with Maven 3.1.1 works actually
old 2.4 m-pir-p is used, which doesn't use Aether, so it works both for Maven
3.0.x and 3.1.x
To test a skin, I suppose this old version is sufficient
do you have issues?
Yes, I do. Maven 3.1.1 an
Am 2013-12-10 01:54, schrieb Hervé BOUTEMY:
Le mardi 10 décembre 2013 01:05:30 Michael-O a écrit :
Am 2013-12-10 00:58, schrieb Hervé BOUTEMY:
${project.build.directory}/staging/${maven.site.path}
is not really necessary here, since skins are never multi-module, then no
need to site:stage
th
