You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Fredrik Vraalsen (JIRA)" <ji...@codehaus.org> on 2006/05/09 07:58:41 UTC
[jira] Created: (MEJB-13) Add support for configuring exclusion
filter for main ejb jar
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
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
[jira] Commented: (MEJB-13) Add support for configuring exclusion
filter for main ejb jar
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEJB-13?page=comments#action_69049 ]
Trygve Laugstol commented on MEJB-13:
-------------------------------------
I'm -1 to this solution. The ejb.jar's resources should be completly controlled with the normal <resources> section inside the <build> as all other JARs. The client jar should have a similar <resources> section to control what goes in the client jar.
> 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
[jira] Updated: (MEJB-13) Add support for configuring exclusion
filter for main ejb jar
Posted by "Fredrik Vraalsen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEJB-13?page=all ]
Fredrik Vraalsen updated MEJB-13:
---------------------------------
Attachment: maven-ejb-plugin-configure-main-jar-excludes.patch
> 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.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
[jira] Commented: (MEJB-13) Add support for configuring exclusion
filter for main ejb jar
Posted by "Jayson Raymond (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEJB-13?page=comments#action_79254 ]
Jayson Raymond commented on MEJB-13:
------------------------------------
I disagree with Trygve here.
Build resources are assigned to the entire build process - and made available to all defined plugins.
This particular plugin will generate multiple artifacts (ejb.jar and client.jar). It will need to narrow the set of resources in different ways for each of those artifacts.
Because of this, defining the resource subset must occur within the plugin definition, as has already been done with the client resources. The same needs to occur for the ejb.jar itself.
I am currently faced with this exact problem and will be using (and am grateful for) Fredriks contribution. I hope it will be in the next release, so I won't need to maintain a seperate copy.
> 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
> Issue Type: New Feature
> Affects Versions: 2.0, 2.1
> Environment: Maven 2.0.4, maven-ejb-plugin 2.1-SNAPSHOT, JBoss 4.0.3sp1
> Reporter: Fredrik Vraalsen
> Attachments: maven-ejb-plugin-configure-main-jar-excludes-2.patch, maven-ejb-plugin-configure-main-jar-excludes.patch, MEJB-configure-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
[jira] Commented: (MEJB-13) Add support for configuring exclusion
filter for main ejb jar
Posted by "Fredrik Vraalsen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEJB-13?page=comments#action_69152 ]
Fredrik Vraalsen commented on MEJB-13:
--------------------------------------
Another issue: The exclude/include filters in the ejb plugin also control which class files are put in the ejb-client jar. My other reason for wanting to be able to configure the ejb jar exludes is that there are some class files that I only want in the ejb-client jar.
> 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
[jira] Commented: (MEJB-13) Add support for configuring exclusion
filter for main ejb jar
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEJB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=164705#action_164705 ]
Dennis Lundberg commented on MEJB-13:
-------------------------------------
Trygve,
The normal JAR Plugin has an excludes parameter, that works in pretty much the same way as the proposed patch. I don't see how they are different. I'd like to apply the patch.
> 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
> Issue Type: New Feature
> Affects Versions: 2.0, 2.1
> Environment: Maven 2.0.4, maven-ejb-plugin 2.1-SNAPSHOT, JBoss 4.0.3sp1
> Reporter: Fredrik Vraalsen
> Attachments: maven-ejb-plugin-configure-main-jar-excludes-2.patch, maven-ejb-plugin-configure-main-jar-excludes.patch, MEJB-configure-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
[jira] Commented: (MEJB-13) Add support for configuring exclusion
filter for main ejb jar
Posted by "Fredrik Vraalsen (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MEJB-13) Add support for configuring exclusion
filter for main ejb jar
Posted by "Fredrik Vraalsen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEJB-13?page=all ]
Fredrik Vraalsen updated MEJB-13:
---------------------------------
Attachment: maven-ejb-plugin-configure-main-jar-excludes-2.patch
> 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
[jira] Commented: (MEJB-13) Add support for configuring exclusion
filter for main ejb jar
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEJB-13?page=comments#action_69168 ]
Trygve Laugstol commented on MEJB-13:
-------------------------------------
I suggested that the ejb plugin had a <resources> section that it could apply to the ejb client jar. The ejb jar itself has to behave in the exact same way as the normal jar plugin. This will give you what you are asking for without breaking the normal Maven way of packaging an artifact.
The bug here is that the ejb plugin applies the includes and excludes in addition to the one specified in the pom.
> 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
[jira] Closed: (MEJB-13) Add support for configuring exclusion
filter for main ejb jar
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEJB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MEJB-13.
-------------------------------
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 2.2
Fixed in r747974.
The patch was old and couldn't be applied to trunk, so I made the changes manually. Thanks!
I also added a test case.
New 2.2-SNAPSHOT deployed for testing.
> 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
> Issue Type: New Feature
> Affects Versions: 2.0, 2.1
> Environment: Maven 2.0.4, maven-ejb-plugin 2.1-SNAPSHOT, JBoss 4.0.3sp1
> Reporter: Fredrik Vraalsen
> Assignee: Dennis Lundberg
> Fix For: 2.2
>
> Attachments: maven-ejb-plugin-configure-main-jar-excludes-2.patch, maven-ejb-plugin-configure-main-jar-excludes.patch, MEJB-configure-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