You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by vm...@apache.org on 2003/12/05 15:48:21 UTC

cvs commit: maven-plugins/jboss plugin.jelly

vmassol     2003/12/05 06:48:21

  Modified:    jboss/xdocs changes.xml goals.xml
               jboss    plugin.jelly
  Log:
  Added feature to add custom lib jars to the JBoss configuration created when using the <code>jboss:configure</code> goal.
  
  Revision  Changes    Path
  1.20      +4 -0      maven-plugins/jboss/xdocs/changes.xml
  
  Index: changes.xml
  ===================================================================
  RCS file: /home/cvs/maven-plugins/jboss/xdocs/changes.xml,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- changes.xml	27 Nov 2003 17:05:21 -0000	1.19
  +++ changes.xml	5 Dec 2003 14:48:21 -0000	1.20
  @@ -8,6 +8,10 @@
     <body>
   
       <release version="1.4" date="in CVS">
  +      <action dev="vmassol" type="add" issue="MPJBOSS-6">
  +        Added feature to add custom lib jars to the JBoss configuration
  +        created when using the <code>jboss:configure</code> goal.
  +      </action>
         <action dev="vmassol" type="fix" issue="MPJBOSS-3" due-to="Archimedes Trajano">
           Fixed deploy/undeploy URLs for JBoss 3.2.
         </action>
  
  
  
  1.5       +4 -1      maven-plugins/jboss/xdocs/goals.xml
  
  Index: goals.xml
  ===================================================================
  RCS file: /home/cvs/maven-plugins/jboss/xdocs/goals.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- goals.xml	19 Jun 2003 14:06:20 -0000	1.4
  +++ goals.xml	5 Dec 2003 14:48:21 -0000	1.5
  @@ -17,7 +17,10 @@
           <name>jboss:configure</name>
           <description>
             Creates a custom JBoss server configuration directory structure
  -          (with no J2EE modules deployed in it).
  +          (with no J2EE modules deployed in it). Custom lib jars can be
  +          specified in the <code>project.xml</code> by taggin them with
  +          the <code>&lt;jboss.lib.bundle&gt;true&lt;/jboss.lib.bundle&gt;</code> 
  +          property.
           </description>
         </goal>
         <goal>
  
  
  
  1.18      +11 -1     maven-plugins/jboss/plugin.jelly
  
  Index: plugin.jelly
  ===================================================================
  RCS file: /home/cvs/maven-plugins/jboss/plugin.jelly,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- plugin.jelly	27 Nov 2003 17:05:21 -0000	1.17
  +++ plugin.jelly	5 Dec 2003 14:48:21 -0000	1.18
  @@ -92,13 +92,23 @@
       description="Creates a specific JBoss server configuration"
       prereqs="jboss:init">
   
  -    <!-- Copy the JBoss jars from an existing JBoss default server
  +    <!-- Copy the JBoss lib jars from an existing JBoss default server
            configuration to our specific configuration -->
       <ant:copy todir="${maven.jboss.build.lib.dir}">
         <ant:fileset dir="${maven.jboss.default.lib.dir}"
           includes="${maven.jboss.default.lib.includes}"
           excludes="${maven.jboss.default.lib.excludes}"/>
       </ant:copy>
  +
  +    <!-- Copy user-specific lib jars defined in project.xml and tagged with
  +         <jboss.lib.bundle> -->
  +    <j:forEach var="lib" items="${pom.artifacts}">
  +      <j:set var="dep" value="${lib.dependency}"/>
  +      <j:if test="${dep.getProperty('jboss.lib.bundle') == 'true'}">
  +        <ant:echo>Bundling: (${dep.groupId}, ${dep.artifactId}, ${dep.type})</ant:echo>
  +        <ant:copy todir="${maven.jboss.build.lib.dir}" file="${lib.path}"/>
  +      </j:if>
  +    </j:forEach>
   
       <!-- Copy the JBoss default conf files from an existing JBoss
       	 server configuration to our specific configuration -->
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org