|
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>. 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> 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. 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. Best regards Wofgang |
- [mojo-user] JBoss maven 2 plugin Wolfgang Weiss
- Re: [mojo-user] JBoss maven 2 plugin Jeff Smith
