Alright guys! You know I love maven - I harass you on IIRC often
enough. But let me give some ...let's call it "user feedback".
I have to say I am impressed how much documentation is actually
available on the website! And the book is awesome! Congrats!
Unfortunately both are missing out on multi-projects ...which
(according to the user's list) is obviously where quite a few people
are struggling at the moment.
Some things I came across when I moved commons jci to maven2...
I wanted the different jci compiler implementations to be available as
different jars and be able to compile them individually. Multi-project
- clear choice. So I went ahead and found out this can be done with
the "module" tags. First thought: Why "modules"? Everyone talks about
"multi-projects" and "artifacts" ...but anyway. So I changed the
layout and and created poms for all the compiler sub-projects.
When I tried to build the (main) project I got told off that packaging
was meant to be "pom" not "jar" ...ok - but why? (I mean
conceptually?) ...anyway, I changed that but then I had to realize
that my core classes (meant to be build from the main pom) where not
getting compiled. Hm... so obviously package type "pom" means the
build section gets ignored and ...well, no package is getting created.
Well, fair enough - having a separate jar for the core is not too bad.
So I changed that. Cool - builds!
I've ignored the tests so far. But let's look into that now. Hm... the
core tests do need a compiler implementation to run. Hm... the
compilers depend on the core so the test would need to run after both
compilers and the core are compiled ..crap! That doesn't work. Hm...
it would be more than just a PITA to mock a compiler for the core. So
I ended up creating another "test" modules that depends on core and a
compiler implementation. Ok. Not fantastic but works. Well ...maybe
not a bad idea in the end anyway.
Still a happy camper so far - now this is where the real pain begins.
Let's look into the reports and project documentation generation. So I
defined a few reports in the parent pom, built the site and had a
look. Hm ...the general information from the parent pom is there - but
where is the stuff that comes from the sub-projects?! I would have
expected to get at least a project node for each sub-project in the
left navigation bar. Searching on the web I found a "${modules}" tag
that might need to be included into the site.xml. Hm.... still no
luck. Further reading through the archives.... "What is this skin
plugin thingy?" Confused. Ok. Different approach.
Although I really hate to move the documentation and the site into the
core sub-project I gave it a try. So the idea is that the core site
will become the main site. If I don't get the reports for the compiler
sub-projects ....well, I could live without them - they are only
wrappers. But this sucks! But let's try it.
So I moved all the reports from the parent pom into the core pom. No
defined reports for the parent, nothing to inherrit to the
sub-projects and I will just define my site in the core. I expected
that a call to site will just get ignored by the parent and passed on
to the core site goal which will do the actual work ...but now
-although I haven't defined a single report- a whole bunch of reports
(more than I ever had defined) get generated for the parent pom - WTF?
If anyone could help me get the commons-jci site up and running that
would be great.
I am currently feeling a bit lost in this area of maven.
http://svn.apache.org/repos/asf/jakarta/commons/sandbox/jci/trunk/
And BTW:
On the front page "Information for Maven 1.0 Users" should include a link to
http://maven.apache.org/guides/mini/guide-m1-m2.html
You guys should also provide a stylesheet for migrating at least
something from the project.xml to the pom.xml.
And IMO maven is way too verbose. Guys you are talking to a user.
"[INFO]" and stuff like that is good for log a file but not for a user
output. If you output less you could also get rid of some of the
"---------------------------------------------"
...lines.
Puuh! Thanks for listening ...feels better now :)
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
