Steinar Bang wrote:
Dennis Lundberg <[EMAIL PROTECTED]>:
Thanks for your input Steinar.
But this isn't at all helpful. Because is to vague. In order for us
(the Maven devs) to fix things we need you (the Maven users) to let us
know *exactly* what is wrong. Please give us concrete examples, then
we can fix them.
Two things have locked us to 2.0.4:
- a bug in maven proper (I think) where maven will ungzip a tar.gz
or tgz file it downloads, before dropping it in the local maven
repo, still with the same name, which breaks when an attempt is
made at using the file
- our use of <profile> gave maven 2.0.5 a nullpointer exception, and
still breaks with error messages I don't understand, and haven't
had time to look closer at, on 2.0.7
If you can't find issues for these problems in JIRA, please create new
ones. Add the stack trace to the issue, by running 'mvn -e ...'
The profile problem is the reason I haven't been able to verify that
we have the unpack issue on 2.0.7, which is why I haven't reported it
as a bug.
Trying to find out about the two above have been _major_ time
wasters. We have spent days trying to track down what has been
happening with the first one, and have spent days trying to understand
<profiles> enought to fix the second one.
So I guess <profiles> should definitely be classified as _hard_.
Of course this does not really apply when documentation is totally missing.
Well, the plugin that had documentation preceeding the currently
released plugin was maven-dependency-plugin a way back. I was trying
to use the analysis goal, which the documentation showed but the
plugin didn't have. And also there were some <exclude*> parameters in
copy-dependencies that were in the online docs, but not in the
released plugin.
This has been a source of confusion and frustration for users before.
What we have done to improve the situation is to add support for @since
annotations for mojo classes and parameters. If these annotations are
added in the source code for a plugin, and they should be, the generated
documentation for goals and parameters shows this.
The dependency-plugin has a good example of this, where the class (goal)
is available since 2.0-alpha-3 and a couple of parameters since 2.0-alpha-5:
http://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html
This is hopefully outdated information, and has been fixed a long time
back. However I avoid doing "mvn -U", since I'm still on 2.0.4 (see
above).
Thanks
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
