Hi Steve,
sorry, but building fails for me.
I know what the problem is!
To handle plugin builds we had to do some transformation of project.xml file using xslt. However to run the xstl goal you need to have an addition jar file in your maven/lib/endorsed directory. I don't immediately recall which one it is - but you should be able to figure out what you need simply by making sure you have the following three jar files in maven/lib/endorsed
xalan-2.5.1.jar xerces-2.4.0.jar xml-apis-1.0.b2.jar
Stephen.
I just did a vanilla checkout of the whole avalon stuff. A
maven --debug plugins
gave me
.... Finished initializing Plugins! Using userBuildPropertiesFile: C:\Dokumente und Einstellungen\Otto Berg\build.properties Using projectPropertiesFile: C:\Quelltexte\OBergner\CVSCheckout\ApacheGroup\Avalon\avalon\project.propert ies Using projectBuildPropertiesFile: C:\Quelltexte\OBergner\CVSCheckout\ApacheGroup\Avalon\avalon\build.propertie s [DEBUG] Adding reference: maven.dependency.classpath -> Fatal Error [line 11, row 24]: The content of elements must consist of well-formed character data or markup. org.xml.sax.SAXParseException: The content of elements must consist of well-formed character data or markup. at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:146 ) at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:151 ) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:463) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:265) at org.apache.maven.cli.App.doMain(App.java:466) at org.apache.maven.cli.App.main(App.java:1117) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Total time: 3 seconds Finished at: Thu Apr 22 11:35:11 CEST 2004
Dunno which file maven is parsing here, though. How would I find out?
Olaf
-----Original Message----- From: Stephen McConnell [mailto:[EMAIL PROTECTED] Sent: Thursday, April 22, 2004 8:09 AM To: Avalon Developers List Cc: Avalon framework users Subject: Re: Building from CVS
OK - things seem to be working:
$ maven plugins <--- builds core plugins $ maven meta <--- builds framework, meta and meta-plugin $ maven merlin <--- builds util, repository, logging, composition, activation and merlin
Steve.
Stephen McConnell wrote:
You may want to hold off on this for an hour or two - seems
like we have
an issue to resolve.
SJM
Stephen McConnell wrote:
Olaf:
I've just finished a bunch of build system updates. To build merlin from cvs you need to go though three steps following completion of a checkout or update. From the root avalon directory issue the following commands:
$ maven plugins $ maven meta $ maven merlin
The reason for the multiple steps is that the maven system does not update itself in terms of plugin builds - so we need to build the initial set of core plugins, then build meta and its plugin, then build merlin and its plugin.
Stephen.
Olaf Bergner wrote:
FYI: The file maven.xml under avalon/ declares "avalon:install" as its default goal (default="avalon:install") yet never defines this goal. It's probably a copy and paste error. Thus if you issue an innocent 'maven' from the avalon-directory you will get 'no goal: [avalon:install]'.
Another question: once the dust has settled, what will be the recommended build procedure?
Cheers, Olaf
-----Original Message----- From: Stephen McConnell [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 5:19 PM To: Avalon framework users Subject: Re: Building from CVS
Niclas Hedhman wrote:
On Tuesday 20 April 2004 21:36, Olaf Bergner wrote:
Should I rather wait until the grounds stop shifting?
Yes, but thanks for pointing it out. Stephen reported to me that it now builds, but I am normally the 'double-checker' and I haven't
had time to do
so yet.
Just for reference - Timothy ran into a problem yesterday -
seems that
we have a bug in the build system somewhere concerning the default merlin properties. I'm digging into that at the moment.
Steve.
Expect it to be fixed in one or two days max.
Niclas
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
