Re: [mojo-user] JBoss maven 2 plugin

[Jeff Smith]

I'll try to answer these since I recently submitted the patch that provided that functionality. My answers are inline.  On Mar 20, 2006, at 3:47 AM, Wolfgang Weiss wrote: Dear everybody!   I’m currently testing the JBoss Maven 2 plug in for a project; I have following questions / problems: 1) Why copies the “jboss:configure” goal the content of “${basedir}/jboss/conf” for the deploy directory instead of the “deploy” directory? – It is necessary to configure the deploy directory explicitly <deployDir>${basedir}/jboss/deploy</deployDir>.   It should copy the contents of the jboss installation and then overlay any additional or changed files on top of that. If its not doing that, then its a bug on my part. I did this so this plugin would work similarly to the maven 1.x plugin for jboss. It was a pretty quick addition for a proof of concept that I ended up sending a patch in for, so let me know if its broken. 2) It would be much easier for us if the “jboss:configure” goal copies the default server to the specified server name. e.g. following configuration copies the content of “C:\Programme\jboss\server\default\” to “C:\Programme\jboss\server\newServer\”. Afterwards I have a new server configuration. <plugin>         <groupId>org.codehaus.mojo</groupId>         <artifactId>jboss-maven-plugin</artifactId>                     <configuration>                         <serverName>newServer</serverName>                         <jbossHome>C:\Programme\jboss</jbossHome>                         <outputDirectory>C:\Programme\jboss\server</outputDirectory>                         <port>8080</port>                     </configuration> </plugin> I didn't do this because it didn't seem like the "maven way". I put everything in the target directory so its easily cleaned up.   3) It would be nice if I can define my own “bin” directory. i.e. I can define my own “run.bat” and “run.sh” files, which are copied while the “jboss:configure” goal is executed. I'm not sure I understand the need for this, although I'm sure there is one, what is your use case? I have been meaning to at least at the ability to add additional VM parameters via the JAVA_OPTS environment variable.   4) Is it possible to mark dependencies in the pom.xml that they belong to the JBoss - server - lib Directory? In the maven 1 version it was possible to add following property to a dependency “<jboss.lib.bundle>true</jboss.lib.bundle>”. While executing the configure goal all dependencies the “<jboss.lib.bundle>true</jboss.lib.bundle>” are copied to the lib directory of the specified server.   That's a good idea, but I didn't get around to implementing it. Would you like to submit a patch for this?   Best regards Wofgang