You have been extremely helpful, which has been the most promising thing so far.
Thank you. On the other hand, it does seem like maven still needs a heck of a lot of
work.
It also seems like maven has a very singular way of working that doesn't really suit
the way I want to work. Is there interest in broadening the way maven can work (say,
satisfying dependencies with CVS), or should efforts to that end be devoted to a
different project?
Re: task appearance
Odd, that. Does the annoying ASCII art supercede task labels?
Re: dependencies
This behavior also suggests that it would be impossible to "lock down" a potential set
of dependencies that a project can use. Even if you create your own repository and
ensure all projects use only it, compiling any other maven project would allow
compilation of projects that shouldn't be able to fufill their dependencies. I
suppose I could force projects to set a different local repository, but that seems
slippery.
Re: return codes
I'll submit an issue for it tomorrow, but if anyone was curious, here's a snippet:
<snip>
[exec] +----------------------------------------
[exec] | Building Maven VDoclet Plug-in
[exec] | Memory: 156M/158M
[exec] +----------------------------------------
<snip>
[exec] java:compile:
[exec] [echo] Compiling to
C:\blah\jbuild\maven\src\plugins-build\vdoclet/target/classes
[exec] [javac] Compiling 1 source file to
C:\blah\jbuild\maven\src\plugins-build\vdoclet\target\classes
[exec] BUILD FAILED
[exec] com.werken.werkz.UnattainableGoalException: Unable to obtain goal [plugin]
-- file:/C:/Documents and Settings/hornc/.maven/plugins/java/:55:48: <ant:javac> Error
starting modern compiler
<snip very long error description>
[exec] Unable to obtain goal [plugin] -- file:/C:/Documents and
Settings/hornc/.maven/plugins/java/:55:48: <ant:javac> Error starting modern compiler
[echo]
[echo] +------------------------------------------------------------------+
[echo] | |
[echo] | I N S T A L L I N G T H E P L U G I N S |
[echo] | |
[echo] +------------------------------------------------------------------+
[echo]
<snip happily continuing build>
-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 05, 2003 10:32 PM
To: 'Maven Users List'
Subject: RE: Building Maven
> Tried again, got the right ant-optional. Current maven
> wouldn't build (test failure, I think), but that's ok.
Yeah, I noticed that. Changelog plugin doesn't build "offline" or behind a
firewall.
I'll put it in JIRA.
> So, questions:
> 1) Why the corrupt dependency? How do I prevent this in the
> future? It seems like once you have a broken jar in your
> local repository, you're screwed. Also seems like if you
> have two projects getting the "same" dependency from
> different sites, it will only get the first one. Could be
> wrong here, love to know.
I've seen this before. There's some preliminary md5 support in Maven. If
that were enforced, then the deps can be validated.
As for only getting the first one, this is the expected behaviour, unless
they are SNAPSHOTs in which case the newest one is downloaded.
> 2) How does a compilation error and a failed build result in
> a successful build? I can paste the log, but it's rather long.
I think it is to do with Maven return codes. Feel free to file an issue in
JIRA.
You don't need to pass in the whole compilation, just the relevant part of
the bootstrap and a snippet of the error message (eg was it building the
plugins, installing the plugins, building maven with itself?)
> 3) Does it seem odd to anyone else that compilation occurs
> under a "clean-maven-home" task?
It just looks that way. Its not actually occurring in that task.
Glad you got it going!
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
