Well, despite of all the help from this mailing list, I found using Maven 2 is not easy...
Problems I encountered: - building an ear (had a lot of trouble getting the plugin in the first place) - hot-deploy to jboss doesn't work for me (seems to work for others on this list) - my .ear file contains a jar file which I do not want to be included because this conflicts with the one already in the classpath from JBoss (commons-logging). I tried many things with scope 'provided' etc, it still ends up in the ear.... I have yet to start including my client application in the war as a download (webstart). This probably will give me another headache (how do I get jars in the root of the war, not in the web-inf/lib ?) Edwin -----Oorspronkelijk bericht----- Should new users start w/ Maven1? Or should I bravely press on w/ Maven2? Will I suffer? -Babak. --------------------------------------------------------------------- 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]
