RE: Jar instead of classes dir in War
Yes, You need another POM. One of the downsides (IMHO) of maven. I need 7 projects (with pom.xml) to get my project build (including the seperate pom's for the war and ear). Edwin -Oorspronkelijk bericht- Van: Wouter de Vaal [mailto:[EMAIL PROTECTED] Verzonden: donderdag 11 mei 2006 10:17 Aan: Maven Users List Onderwerp: Re: Jar instead of classes dir in War Thanks for you suggestions. Simply put, create an extra pom? I would like to keep all code within the same eclipse project because of testability. Wouter On 5/11/06, Tim Kettler <[EMAIL PROTECTED]> wrote: > -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.5.5/335 - Release Date: 9-5-2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jar instead of classes dir in War
Hoi Wouter, You have to create multiple projects (I use maven 2 to do this kind of stuff). Then, make the 'war' project depend on the 'jar' project. Edwin van der Elst -Oorspronkelijk bericht- Van: Wouter de Vaal [mailto:[EMAIL PROTECTED] Verzonden: donderdag 11 mei 2006 9:47 Aan: Maven Users List Onderwerp: Jar instead of classes dir in War Hi, I would like know how to go about this scenario. I would like to create an exploded war with the following differences to what the standard war plugin created * instead of placing all compiled classes from src/main/java into WEB-INF/classes/com/comp/etc I would like them to be compiled into a jar and put in the WEB-INF/lib. * I would like to assign certain resource not to be put in the above described jar, and some to be put into the jar. e.g., some properties files need not be changed except bij the developer, but log4j files for instance could be changed by the deployer. Any idea's on how to automate this process? Regards, Wouter -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.5.5/335 - Release Date: 9-5-2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.5.5/335 - Release Date: 9-5-2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Applets
Completely correct!
I have a war that contains a webstart application (more or less the same issues
getting that to work).
THis is in the pom.xml of the WAR project (I have subprojects for war, shared,
client)
app-war
org.codehaus.mojo
dependency-maven-plugin
process-resources
unpack
nl.finalist.app
client
${version}
zip
${project.build.directory}/${project.build.finalName}/
-Oorspronkelijk bericht-
Van: Max Cooper [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 27 april 2006 2:40
Aan: Maven Users List
Onderwerp: Re: Applets
You need a multi-project.
I have not setup a maven2 project to build an applet that is deployed as
part of a webapp, so take my advice with a grain of salt.
I would think that you would first need to have a subproject to build a
jar file that contains your applet. The applet code should probably be
separate from your webapp code anyway. Any code that is shared by the
webapp and the applet should be moved to third "shared jar" project that
both the webapp and applet project will depend on.
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.5.0/325 - Release Date: 26-4-2006
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: M1 or M2?
Hi, This actually works, thanks! What is annoying, is that the commons-logging is required by multiple dependencies of the ear. So I have to put an exclusion in each dependency. Edwin -Oorspronkelijk bericht- Van: Alexandre Poitras [mailto:[EMAIL PROTECTED] Verzonden: donderdag 5 januari 2006 14:33 Aan: Maven Users List Onderwerp: Re: M1 or M2? The jar probably come from transitive dependencies. Use the exclude options to get ride of it in the dependencies declaration providing the jar. It should do the trick. I have no idea about Java WebStart since I haven't use it myself. On 1/4/06, Edwin van der Elst <[EMAIL PROTECTED]> wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: M1 or M2?
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]
RE: configure plugin (jboss-maven)
Ok, thank you for trying this out. It is probably something wrong in my configuration. If I have some time left I will try to reinstall the plugins and try again (cannot do this now, I need to get some work done first :-) Edwin -Oorspronkelijk bericht- Van: Edwin Punzalan [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 3 januari 2006 2:49 Aan: Maven Users List Onderwerp: Re: configure plugin (jboss-maven) I understand. Anyway, I tried and configured the jboss plugin on my maching and got this: -- snip [DEBUG] Configuring mojo 'org.codehaus.mojo:jboss-maven-plugin:1.0:harddeploy' --> [DEBUG] (f) fileName = F:\mergere\maven\web-pom-generator\trunk\target/web-pom-generator.war [DEBUG] (f) jbossHome = app\jboss-4.0.3\ [DEBUG] (f) serverName = default [DEBUG] -- end configuration -- [INFO] [jboss:harddeploy] -- snip notice jbossHome got the correct configuration I put in my pom.xml so the jira isn't needed. Sorry if I'm not of great help, but that's as far as I can go if can't reproduce it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: configure plugin (jboss-maven)
Hi, I didn't setup profiles (tried it, but undid the changes). Putting the settings in the pom should be the easies way to configure I guess. But never mind, I gave up and wrote a .bat file to copy the ear (cannot afford to spend anymore time on this) Cheers, Edwin -Oorspronkelijk bericht- Van: Rinku [mailto:[EMAIL PROTECTED] Verzonden: maandag 2 januari 2006 8:37 Aan: Maven Users List Onderwerp: Re: configure plugin (jboss-maven) Have you set up any profile(s) in pom.xml? If so, can you check if a profile is being activated? Cheers, Rahul - Original Message - From: "Edwin van der Elst" <[EMAIL PROTECTED]> To: "Maven Users List" Sent: Thursday, December 29, 2005 9:07 PM Subject: RE: configure plugin (jboss-maven) Hi, Below is the full stacktrace. (mvn -X jboss:harddeploy) It isn't picking up the parameters. Edwin [DEBUG] Configuring mojo 'org.codehaus.mojo:jboss-maven-plugin:1.0:harddeploy' --> [DEBUG] (f) fileName = C:\cvs\wfz-leda\target/Leda-1.0-SNAPSHOT.pom [DEBUG] (f) jbossHome = NONE [DEBUG] (f) serverName = default [DEBUG] -- end configuration -- [INFO] [jboss:harddeploy] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] jbossHome configuration parameter is not set. [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: jbossHome configuration parameter is not set. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.ja a:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: jbossHome configuration parameter is not set. at org.codehaus.mojo.jboss.AbstractJBossMojo.checkConfig(AbstractJBossMojo.java:52) at org.codehaus.mojo.jboss.HardDeployMojo.execute(HardDeployMojo.java:43) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530) ... 16 more -Oorspronkelijk bericht- Van: Edwin Punzalan [mailto:[EMAIL PROTECTED] Verzonden: donderdag 29 december 2005 2:59 Aan: Maven Users List Onderwerp: Re: configure plugin (jboss-maven) That seems to be the correct configuration... can you give the full stack trace of the error you encountered? Btw, if you want to specify a path relative to your current dir, don't put the leading backslash "\" in Edwin van der Elst wrote: >Hi, > >I'm going nuts here, trying to use the jboss-maven plugin in Maven2. >I downloaded the plugin from codehause and installed locally. > >Now > >In my pom.xml > ... > > org.codehause.mojo > jboss-maven-plugin > 1.0 > false > > \apps\Jboss-4.0.3\ > > > > - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: configure plugin (jboss-maven)
Hi, Below is the full stacktrace. (mvn -X jboss:harddeploy) It isn't picking up the parameters. Edwin [DEBUG] Configuring mojo 'org.codehaus.mojo:jboss-maven-plugin:1.0:harddeploy' --> [DEBUG] (f) fileName = C:\cvs\wfz-leda\target/Leda-1.0-SNAPSHOT.pom [DEBUG] (f) jbossHome = NONE [DEBUG] (f) serverName = default [DEBUG] -- end configuration -- [INFO] [jboss:harddeploy] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] jbossHome configuration parameter is not set. [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: jbossHome configuration parameter is not set. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.ja a:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: jbossHome configuration parameter is not set. at org.codehaus.mojo.jboss.AbstractJBossMojo.checkConfig(AbstractJBossMojo.java:52) at org.codehaus.mojo.jboss.HardDeployMojo.execute(HardDeployMojo.java:43) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530) ... 16 more -Oorspronkelijk bericht- Van: Edwin Punzalan [mailto:[EMAIL PROTECTED] Verzonden: donderdag 29 december 2005 2:59 Aan: Maven Users List Onderwerp: Re: configure plugin (jboss-maven) That seems to be the correct configuration... can you give the full stack trace of the error you encountered? Btw, if you want to specify a path relative to your current dir, don't put the leading backslash "\" in Edwin van der Elst wrote: >Hi, > >I'm going nuts here, trying to use the jboss-maven plugin in Maven2. >I downloaded the plugin from codehause and installed locally. > >Now > >In my pom.xml > ... > > org.codehause.mojo > jboss-maven-plugin > 1.0 > false > > \apps\Jboss-4.0.3\ > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
configure plugin (jboss-maven)
Hi, I'm going nuts here, trying to use the jboss-maven plugin in Maven2. I downloaded the plugin from codehause and installed locally. Now In my pom.xml ... org.codehause.mojo jboss-maven-plugin 1.0 false \apps\Jboss-4.0.3\ I always get the error 'jbossHome' not set. I tried a lot of combinations (almost), putting this in the pom, the settings.xml, using different syntax (jboss.home), etc. Does anyone know if it is possible at all to use this plugin with maven 2.0.1? (Maybe I should just give up and write an Ant file and get on working.....) Edwin van der Elst - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problems using ejb3
Thank you very much, it works after aplying the patch. Edwin -Oorspronkelijk bericht- Van: Tim Kettler [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 20 december 2005 16:23 Aan: Maven Users List Onderwerp: Re: Problems using ejb3 Hi, see http://jira.codehaus.org/browse/MNG-1690 -Tim Edwin van der Elst schrieb: > Hi, > > I compiled the latest Maven from SVN and did the same for the > maven-ejb3-plugin and maven-ear-plugin. > I am trying to get the ejb.jar in the ear file with the .ejb3 extension for > deployment under JBoss. The ear file will probably be ok, once I get Maven to > store my jar file with the corerct extension in the repository. > > Some fragments from my pom.xml: > > ... > ejb3 > ... > > > > > org.apache.maven.plugins > maven-ejb3-plugin > 2.1-SNAPSHOT > > > package > > ejb3 > > > > > > I now get a NPE during the build: > [INFO] [ejb3:ejb3] > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error assembling EJB3 > > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling EJB3 > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472) > .. > .. > Caused by: java.lang.NullPointerException > at org.apache.maven.plugin.ejb3.Ejb3Mojo.execute(Ejb3Mojo.java:136) > ... 18 more > > > Has anyone got a clue how to get this working? > Being used to Ant, this seems such a trivial problem (In Ant: just name the > jar 'myejbs.ejb3' and be done with it). > > Any help appreciated, > > Edwin van der Elst > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Freundliche Grüße / Best Regards Tim Kettler _ Lieterweg 24 58285 Gevelsberg Tel.: +49 2332 149814 Fax: +49 2332 149814 e-mail: [EMAIL PROTECTED] Internet : http://www.tk-ai.de - 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]
Problems using ejb3
Hi, I compiled the latest Maven from SVN and did the same for the maven-ejb3-plugin and maven-ear-plugin. I am trying to get the ejb.jar in the ear file with the .ejb3 extension for deployment under JBoss. The ear file will probably be ok, once I get Maven to store my jar file with the corerct extension in the repository. Some fragments from my pom.xml: ... ejb3 ... org.apache.maven.plugins maven-ejb3-plugin 2.1-SNAPSHOT package ejb3 I now get a NPE during the build: [INFO] [ejb3:ejb3] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error assembling EJB3 [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling EJB3 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472) .. .. Caused by: java.lang.NullPointerException at org.apache.maven.plugin.ejb3.Ejb3Mojo.execute(Ejb3Mojo.java:136) ... 18 more Has anyone got a clue how to get this working? Being used to Ant, this seems such a trivial problem (In Ant: just name the jar 'myejbs.ejb3' and be done with it). Any help appreciated, Edwin van der Elst - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
