Class-Path entry in MANIFEST.MF not created when using ejb3Module
-----------------------------------------------------------------

                 Key: MEAR-93
                 URL: http://jira.codehaus.org/browse/MEAR-93
             Project: Maven 2.x Ear Plugin
          Issue Type: Bug
    Affects Versions: 2.3.1
         Environment: Windows XP
            Reporter: Aleksander Adamowski


Maven fails to add Class-Path entries to MANIFEST.MF for a module marked as 
ejb3.
E.g.:
In EJB module's pom.xml:

...
        <modelVersion>4.0.0</modelVersion>
        <groupId>somegroup</groupId>
        <artifactId>someejb</artifactId>
        <packaging>ejb3</packaging>
...
        <build>
        <plugins>
                <plugin>
                        <artifactId>maven-ejb-plugin</artifactId>
                        <configuration>
                                <ejbVersion>3.0</ejbVersion>
                                <archive>
                                        <manifest>
                                                
<addClasspath>true</addClasspath>
                                        </manifest>
                                </archive>
                        </configuration>
                </plugin>
        </plugins>
    </build>
...
        <dependencies>
                <dependency>
                        <groupId>somegroup</groupId>
                        <artifactId>somecomponent</artifactId>
                        <version>0.0.1</version>
                </dependency>
        </dependencies>
</project>

In EAR packaging artifact's pom.xml:

...
  <groupId>somegroup</groupId>
  <artifactId>jboss-ear</artifactId>
  <version>0.0.1</version>
  <packaging>ear</packaging>
  <name>Some project's J2EE bundle</name>
...
<dependencies>
    <dependency>
      <groupId>somegroup</groupId>
      <artifactId>someejb</artifactId>
      <version>0.0.1</version>
      <type>ejb3</type>
    </dependency>
    <dependency>
        <groupId> somegroup </groupId>
        <artifactId> somecomponent</artifactId>
        <version>0.0.1</version>
    </dependency>
...
<modules>
          <ejb3Module>
               <groupId>somegroup</groupId>
               <artifactId>someejb</artifactId>
          </ejb3Module>
          <jarModule>
               <groupId>somegroup</groupId>
               <artifactId>somecomponent</artifactId>
          </jarModule>
          </modules>
          <jboss>
            <version>4</version>
            
<loader-repository>com.domain.someproject:app=ejb3</loader-repository>
          </jboss>
...

What's interesting, all works fine if I change all occurences of "ejb3" to 
simple "ejb", but leave the <ejbVersion>3.0</ejbVersion> in build section of my 
EJB artifact.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to