Hi there,
first of all I want to say again that maven is very cool and since
1.0-rc3 supports inheriting project.xml I really start loving it.
(When talkin about maven now, I include the plugins shipped with the
maven release).
On the other hand for me there are lots of little things that are
quite inconvenient:
-Maven does not handle XML properly! I do not have a clue what its doing
inside but maybe some developers might think that XML ist just some little
ASCII standard extension (quite a point of view). Here are some examples
I can rember right now:
When I use some special chars xml encoded in my POM e.g. & in the team
list, maven does convert them to & in the generated team-list.xml template
and then fails converting it to html.
Another issue is that the XML standard supports including of XML fragemnts
from seperate files giving a relative path. (you know that thingy like
<!DOCTYPE mytag [
<!ENTITY myentity SYSTEM "file:../fragment.xml">
]>
...
&myentity;
...
Now maven (e.g. multiproject) sometimes copies files from xdocs to another
location before parsing them what breaks the relative includes.
-Maven exception handling is sometimes inconvenient because it does not give
you a clue what the actual problem is. Especially when maven is failing to
parse an XML file, it does not give you an idea which file is wrong. I am
using maven for a project that is build out of 20 components realized as
subprojects. You all know what can happen when CVS or SVN prove their
intelligence on merging files - especially XML. It is completly driving me
nuts when maven multiproject:site gives me an error message saying
your XML is not well formed and I have to hunt for the evil file.
The coolest thing is when I then run maven with -X is does almost nothing
and writes BUILD COMPLETE while the same maven call with the same target
but without -X produces BUILD FAILED.
I think such error-messages are the overkill for maven newbies.
-Maven documentation is a nice thing to start, but when doing something
more it gets really hard. If there is no time for improving the doc,
then maybe give the hint to look in all the referenced maven driven open
source projects and see their sites and according maven source config.
-when using subprojects that extend a parent POM then multiproject does
not detect if logos (project and organization) are not overridden and
their paths are not fixed if its relative. Of course one can make it
absolute but that wont work for a local site that is viewed offline.
To make it clear
project
/xdocs/images/logo-project.png
/xdocs/images/logo-organization.png
/subproject
/target
/images/logo-*
/multiproject/subproject
Files in project/target/multiproject/subproject will point to
/images/logo-* but should point to /../../images/logo-*
Now I can set this in every project.xml file of every subproject
with repect that if I do
<organization>
<logo>/../../images/logo-organization.png</logo>
</organization>
I see that this does not only override the pom/organization/logo
but the complete pom/organization meaning that the name and url of the
organization are then set to "".
Well all not too bad cause there are workarounds to go but not really nice.
I suppose an intention of maven is to reduce redundancies what is
missed by various workarounds one has to make things right.
-Why does maven not know about scm:svn and I have to set
maven.changelog.factory=org.apache.maven.svnlib.SvnChangeLogFactory
when using a subversion repository connection?
Better go to bed for now but there is more to come...
However dont wory be happy and thanks for doing maven
Regards
J�rg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
