bob mcwhirter wrote:
Howdy--
Sometime in the past few days, the bootstrap seems to have been broken.
When was the most recent time someone has successfully bootstrapped?
Jeff Brekke and I are noticing that immediately after java:jar towards
the end of the bootstrap, an exception in thread 'main' is puked up,
with no stack-trace or other debug, even when using -X or -e.
I think I've tracked it roughly to Script.run(...) or invokeBody(..)
being called from the org.apache.commons.jelly.tags.werkz.GoalTag
to execute the body.
Though, it's happening after the goal and its post-goals run, so
it's not actual bogus jellyscript.
James-- Are you doing any post-run cleanup within the Script
implementations to handle threadsafety issues, possibly?
Anyone else want to claim breaking maven? :)
Hi,
I am the last one to have committed something, so
it could well be me who broke the build.
Though, the changes don't affect the compilation
neither the tests, and the error appears after that,
so ...
It's been a long time since I last bootstrapped (I
prefer maven:jar-install), and decided yesterday to
bootstrap to check if I didn't break anything and
voila!
But, there is something that sucks and that appeared
with my commits: I added a dir src/templates to store
POM templates, and there was already a src/templates
in the old B4 days, so now if you checkout maven from
scratch, you end up with the old stuff mixed with the
new one, until you update -d. I hate that you can't
remove dirs permanently in CVS.
Sorry about that, but if anyone knows another way of
doing it without this kind of problem, please tell me!
St�phane
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais !
Yahoo! Mail : http://fr.mail.yahoo.com
--
To unsubscribe, e-mail: <mailto:turbine-maven-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-maven-dev-help@;jakarta.apache.org>
