My personal short-list on MNG-3004 now only contains 1 thing, getting order on log output. I need some help on this one;
It seems like there's two sensible ways to handle this A) Intercept plexus "Logger" and sort according to calling thread. B) Intercept System.out/err and sort according to calling thread. I know B is going to work, but I really think A is a nicer option. But plexus scares me (it reminds me of a teenager, capable of throwing fits for no understandable reason and providing no explanation). Assuming I am able to proxy the plexus logger, it should be able to capture output of all plugins too, right ? Anyone have any examples/explanation of how to proxy the logger ? Anyone have any thoughts/preferences on this ? Kristian P.S: The last time I tried to run with the integration tests they worked. Assuming i ran them correctly, that is. Maybe a good idea to update http://maven.apache.org/guides/development/guide-building-m2.html with descriptions on how to do run them correctly ? fr., 04.12.2009 kl. 18.58 -0800, skrev Jason van Zyl: > I'm just starting to take a look now. > > Have you buy chance run what you've built against the integration tests? > > http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/ > > If not, happy to help, or we can pull it into the grid and try it out there. > > On 2009-12-03, at 1:05 AM, Kristian Rosenvold wrote: > > > It's getting close enough, as long as you satisfy the > > following constraints: > > > > - Make sure your build works with "regular" maven3 snapshots first ;) > > - You're not too reliant on snapshot artifacts (MNG-2802 is next on my > > TODO list now) > > - You're not generating source code in generate-sources > > - Running aggregating tasks (javadoc etc) is largely untested as of yet. > > > > The last two should be easily fixable but I've been concentrating on > > the main concurrency concerns (safe publication, deadlock avoidance etc) > > until now, but this seems to be rock solid with my build as of now. This > > is really also the stuff I need input on, since this is usually quite > > timing sensitive. (I have 2 different builds I run on C2D, i7 and dual > > xenons without hiccups right now) > > > > Get the install from > > > > http://cloud.github.com/downloads/krosenvold/maven3/apache-maven-3.0-SNAPSHOT-bin.tar.gz > > > > > > mvn -e -Dmaven.threads.experimental=6 clean install > > > > On my build, 1 thread per core gives best results. Maybe "3" for Core 2 > > duo. > > > > This version is up-to-date with maven3 trunk as of Thu Dec 3 09:01:44 > > 2009 +0100. If you run without the -Dmaven.threads.experimental=6 > > option, you should basically by running regular maven3 trunk. > > > > > > Kristian > > > > > > > > > > On Thu, 2009-12-03 at 09:21 +0100, Jorg Heymans wrote: > >> On Tue, Dec 1, 2009 at 9:49 PM, Kristian Rosenvold > >> <[email protected]> wrote: > >>> I am pleased to announce that the "weave" mode now does a > >>> "mvn clean install" of a fairly regular project with any number of > >>> threads, and at great speed improvement - 2-4x is not uncommon. > >>> > >>> There are still issues to be sorted out, and I'd be really grateful > >>> for any reports of problems. > >>> > >>> See http://github.com/krosenvold/maven3 for a *lot* more details > >>> on problems & issues and how to test this out on your builds. > >> > >> Looks incredibly promising ! > >> > >> I would be more than happy to give you test feedback if you could > >> supply a binary dist with this feature. Or is it not yet ready to be > >> tested by the 'masses' ? > >> > >> Jorg > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > ---------------------------------------------------------- > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
