JBoss EAP 6.0.0GA (AS 7.1.2.Final) Fix to make this work

[WPOSullivan]

You need to add the file jboss-deployment-structure.xml to the META-INF folder at the highest level.

<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
    <deployment>
        <dependencies>
            <module name="org.infinispan" />
        </dependencies>
    </deployment>
</jboss-deployment-structure>
```xml

[galderz]

To make what work? The jboss-as7 quickstart?

Does the same trick work if the quickstart is deployed in community AS 7.1.1.Final?

If it does, send a pull req with the addition of the file to src/ folder in such way that it gets included in the deployment script and we'll review.

If it doesn't, I'd suggest creating a new quickstart for eap6 (send pull req)

[lkrzyzanek]

I'm just trying the jboss-as7 quickstart and it really fails to deploy to EAP 6.3 without that xml file.
When I put jboss-deployment-structure.xml to the WEB-INF directory as @WPOSullivan above then it works.

It looks like some bug in EAP because EAP 6 docs says that dependency in MANIFEST.MF should be enough.

@galderz could you please clarify what is the official way how to require the dependency on infinispan in EAP 6.3?

Thanks.

[galderz]

@WPOSullivan @lkrzyzanek I've just tried with JBoss EAP 6.3.0 and it works fine. These are my steps:

• Download EAP 6.3.0 from here.
• Start it with: ./bin/standalone.sh
• From jboss-as7 folder, call: mvn clean package jboss-as:deploy

These set of steps work without any problems.

@WPOSullivan If you use that method, the deploy target takes care of adding a manifest entry with the needed dependencies in infinispan-jboss-as7.war /META-INF/MANIFEST.MF:

Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: g
Build-Jdk: 1.7.0_60
Dependencies: org.infinispan export

^ The last line is needed, but if you build the war any other way, you either add that manually or have the XML that you suggest.

@lkrzyzanek The manifest part works fine for me :|

[galderz]

I've sent a PR to add this file to avoid problems in the future.

[lkrzyzanek]

Thanks @galderz for checking that again.
I tried mvn clean package jboss-as:deploy and it works as you said.

However deployment from Intellij Idea doesn't. So it seems that Idea doesn't generates manifest correctly from maven configuration.

[galderz]

No idea about Intellij, I never deploy directly from it. Probably an issue that should be raised with them? It would appear to be a Maven integration bug IMO.

[galderz]

Regardless, my PR should solve the problem since you're no longer relying on the manifest generation.