Stephen wrote:
Daniel Frey wrote:
Hi there,
I try to get my multi-project up and running with Maven RC2. However, the avalon:meta goal has disapeared. Maybe somebody has a hint how to get this goal running again.
I've just downloaded RC2 but haven't installed it yet. If avalon:meta isn't available it means that the avalon-meta-plugin-XXX.jar is not installed under maven's plugin directory (at least that's the story with RC1 and earlier). I have a hunch that some things may have changed in RC2 concerning plugin management as I've seen some references to [group-id]/plugins/[artifact-id] which is a bit different to the way things were.
I've switched back to RC1 until more experienced developers have had success with it.
Guess what - just a few seconds ago I completed a build with RC2. I had to modify a couple of maven related files to get the build complete and I haven't tested the runtime yet - but so far the transition is looking ok. Another item is doc generation which I know will be problematic. Anyway - I'll be committing some updates in the next few hours that will ensure a clean build with RC2 (doc related updates will come later).
I tried the following: Supposing I have to build avalon from scratch, I read the README.txt:
"The avalon buildfiles use a common buildsystem which utilizes maven and forrest. You will need to download and install maven, the maven-forrest-plugin, and the avalon-buildsystem module. After doing so, change into the buildsystem directory and type `maven avalon:info` to get yourself started."
Urgh!
Where do you find this? We dropped forrest related stuff ages ago. Basically the buildsystem stuff is only used to support gump based builds
so
you should need to worry about this at all.
Avalon root directory: ./README.txt
OK - updates need here.
<snip>
Just for reference - what products are you interested in building?
I just thought when I build all the I certainly have at least the right component. Just a dummies approach to the system. Actually, are the maven plugins not part of the avalon distribution?
Today there is no nice top-level avalon build procedure. This will change as we move legacy content out of the picture. In the coming weeks - if your tracking CVS - expect to see updates on the Avalon documentation reflecting the decision to move to one container, one architecture, one solution - and related actions concerning end-of-life management of a number of CVS projects. Effectively Avalon is consolidating on a single reference implementation which will make things much simpler and easier to understand and manage and use.
Cheers, Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
