One downside to this kind of parallelism that you should consider is the
output. If all these tasks are writing to stdout or stderr simultaneously it is
going to make the build output hard to understand. It might be preferable to
pipe the output from a thread into a cache and then write the who
Larry Shatzer, Jr. wrote:
I attached a patch (with a test too!) for MSHADE-52, and would love
that to get included
Sorry, not in this release.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
I like it!
Well, except for the "1 thread per module" part; that's clearly too many
threads. You'd want a fixed thread pool.
But restructuring the multithreading around the individual phases and
*scheduling* phases from later projects when earlier project phases are
done seems workable.
W
Karl Heinz Marbaise wrote:
> 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 ?
Yes, that is correct.
If you look closely at the menu, you will see that both "Sample Change
I attached a patch (with a test too!) for MSHADE-52, and would love
that to get included, or at the very least, looked at.
On Sun, Nov 22, 2009 at 5:43 AM, Benjamin Bentmann
wrote:
> Hi,
>
> We solved 7 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&version=15525
>
> T
+1 nb. works with the 2 projects where I use the shade plugin.
LieGrue,
strub
--- Benjamin Bentmann schrieb am So, 22.11.2009:
> Von: Benjamin Bentmann
> Betreff: [VOTE] Release Maven Shade Plugin 1.2.2
> An: "Maven Developers List"
> Datum: Sonntag, 22. November 2009, 13:43
> Hi,
>
> We sol
Hi,
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&version=15525
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11540&status=1
Staging repo:
https://repository.apache.org/content/repositor
+1
Vincent
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
>
> Stag
+1
Vincent
2009/11/20 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
>
> Stagi
+1
Vincent
2009/11/20 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:
>
+1 works 4 me
LieGrue,
strub
--- Brett Porter schrieb am Sa, 21.11.2009:
> Von: Brett Porter
> Betreff: [2.0.11 RC] Please test - RC1
> An: "Maven Developers List"
> Datum: Samstag, 21. November 2009, 14:14
> Hi,
>
> I have staged a first release candidate here:
> https://repository.apache
Brett Porter schrieb:
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.
12 matches
Mail list logo