I've looked over the code and thought a bit further about the
constraints involved, and given that:
- Multi module reactor builds are the only interesting targets of
multithreading.
- Reactor builds do not use the "install" output of their upstream
dependencies (I was not aware of that ;)
You do
On 22/11/2009, at 2:27 AM, Michael wrote:
> Brett Porter schrieb:
>> Hi,
>> I have staged a first release candidate here:
>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/2.0.11-RC1/
>> Here are the issues that have been fixed:
>> http://jira.codehau
+1
Hervé
Le vendredi 20 novembre 2009, Dennis Lundberg a écrit :
> Hi,
>
> We solved 18 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&version=14
> 696
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=tr
+1
Hervé
Le samedi 21 novembre 2009, Dennis Lundberg a écrit :
> Hi,
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137&version=13
> 995
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&
+1
Hervé
Le samedi 21 novembre 2009, Dennis Lundberg a écrit :
> Hi,
>
> This is the first of a series of releases to get Maven Site Plugin 2.1
> released.
>
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=14
> 385
>
> There are no issues lef
Brett Porter schrieb:
Hi,
I have staged a first release candidate here:
https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/2.0.11-RC1/
Here are the issues that have been fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=141
+1
2009/11/21 Dennis Lundberg :
> Hi,
>
> This is the first of a series of releases to get Maven Site Plugin 2.1
> released.
>
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=14385
>
> There are no issues left in JIRA!
>
> Staging repo:
> https://
+1
2009/11/21 Dennis Lundberg :
> Hi,
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137&version=13995
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11137&status=1
>
> Staging repo:
+1
2009/11/20 Dennis Lundberg :
> Hi,
>
> We solved 18 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&version=14696
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&status=1
>
> Staging repo:
Dennis Lundberg wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-014/
Staging site:
http://maven.apache.org/shared/maven-doxia-tools-1.1/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@m
Dennis Lundberg wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-013/
Staging site:
http://maven.apache.org/plugins/maven-jar-plugin-2.3/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@m
Dennis Lundberg wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-012/
Staging site:
http://maven.apache.org/plugins/maven-changes-plugin-2.2/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr.
Hi,
I have staged a first release candidate here:
https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/2.0.11-RC1/
Here are the issues that have been fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14118
in this version.
Pl
Hi, just a question:
Is it correct that the link to the Changes Report (Project Documentation
-> Project Reports -> Changes Reported) is showing me the example report ?
Is this just a relationship based on the staging site ?
Kind Regards
Karl Heinz Marbaise
Arnaud HERITIER wrote:
+1
Arnaud
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Sat, Nov 21, 2009 at 12:48 AM, Dennis Lundberg wrote:
> Hi,
>
> This is the first of a series of releases to get Maven Site Plugin 2.1
> released.
>
>
> We solved 4 issues:
>
>
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Fri, Nov 20, 2009 at 11:37 PM, Michael wrote:
> Dennis Lundberg schrieb:
>
> Hi,
>>
>> We solved 18 issues:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Sat, Nov 21, 2009 at 12:23 AM, Dennis Lundberg wrote:
> Hi,
>
> We solved 4 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137&version=13995
>
> There
In m3 (which is what we are talking about) AFAIK we can have a
listener that waits for the end of the start of the deploy phase
and/or the end of execution.
With a customized install plugin, we could just install to the
"transaction" repository. The listener can then block until the
criteria have
I seem to understand that there's room for several different
types of solution here;
Starting with the single-machine solution; I now understand that
you could start forking downstream builds straight after
compile in a reactor build, maybe after install in other cases.
In this scenario I think
On 21/11/2009, at 3:30 PM, Brian E. Fox wrote:
> All joking aside, 2.0.9 and 2.0.10 have proven to be very stable. We need to
> keep the same bar for 2.0.11 especially if we intend this to be the end of
> 2.0.x. That means we need lots of participation during the rc process.
Yep, there's no re
20 matches
Mail list logo
