[ http://jira.codehaus.org/browse/MEJB-13?page=comments#action_69121 ]
Fredrik Vraalsen commented on MEJB-13: -------------------------------------- Trygve, Remember that the ejb plugin generates _two_ artifacts from the _same_ pom, but both artifacts should not necessarily contain the same resources. If I'm understanding you correctly, you are suggesting that the ejb plugin should be configured with two <resources> sections in the pom, one for the ejb jar and one for the ejb-client jar? But as far as I can tell, you can only have one <resources> section in the pom? The ejb plugin already contains clientExcludes/clientIncludes parameters which are used to further filter the resources to be included in the ejb-client jar. These filters are applied on top of the include and exclude filters specified in the <resources> section in the pom, as far as I know. What I'm asking for is a similar way to configure what should be excluded from the ejb jar, instead of accepting the default exclude filter (hardcoded in the ejb plugin). If there is a way to do this using the <resources> section in the pom instead, could someone please provide an example? Then it should also be possible to get rid of the clientExcludes and clientIncludes properties of the ejb plugin... > Add support for configuring exclusion filter for main ejb jar > ------------------------------------------------------------- > > Key: MEJB-13 > URL: http://jira.codehaus.org/browse/MEJB-13 > Project: Maven 2.x Ejb Plugin > Type: New Feature > Versions: 2.1, 2.0 > Environment: Maven 2.0.4, maven-ejb-plugin 2.1-SNAPSHOT, JBoss 4.0.3sp1 > Reporter: Fredrik Vraalsen > Attachments: MEJB-configure-excludes.patch, > maven-ejb-plugin-configure-main-jar-excludes-2.patch, > maven-ejb-plugin-configure-main-jar-excludes.patch > > > In my ejb project I have certain files that must only be included in the > ejb-client jar and not the main ejb jar (jboss-client.xml, > application-client.xml and jndi.properties). When these files are present in > the main ejb jar, JBoss refuses to deploy my ejbs. > Thus, I need a way to configure the exclusion filter for the main ejb jar. > This is currently hardcoded in EjbMojo.java. I am attaching a patch to make > this configurable in the same way as clientExcludes. > Below is an example of the kind of configuration I am using: > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-ejb-plugin</artifactId> > <version>2.1-SNAPSHOT</version> > <configuration> > <excludes> > > <exclude>jndi.properties</exclude> > > <exclude>META-INF/*-client.xml</exclude> > > <exclude>**/interfaces/</exclude> > > <exclude>**/assetrepository/Asset.class</exclude> > </excludes> > <generateClient>true</generateClient> > <clientExcludes> > > <clientExclude>META-INF/ejb-jar.xml</clientExclude> > > <clientExclude>META-INF/jboss.xml</clientExclude> > > <clientExclude>**/dao/</clientExclude> > > <clientExclude>**/entity/</clientExclude> > > <clientExclude>**/jaxb/</clientExclude> > > <clientExclude>**/session/</clientExclude> > > <clientExclude>**/xmldb/</clientExclude> > </clientExcludes> > </configuration> > </plugin> -- 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