Maven and RAD produce different EARs

Question

I have to build a project(Parent and EAR, which contains jar, ejb, and 2 war modules) from RAD 9.5 and with maven.

When I build a project from maven command-line, everything works fine. It's creating skinny wars archive that runs on WebSphere 8.5.5.

When trying to update project from RAD, or to export EAR I'm getting the file that is different and won't work, with ClassNotFoundException for one of dependencies of the EJB.

Looking further, I found out that there is a difference in MANIFEST.MF in classpath section. Maven project put there instances with lib/ prefix and m2e/RAD without, like this:

Class-Path: lib/log4j-api-2.6.jar lib/log4j-core-2.6.jar lib/junit-4.12.jar lib/hamcrest-core-1.3.

in pure maven and:

Class-Path: log4j-api-2.6.jar log4j-core-2.6.jar junit-4.12.jar hamcrest-core-1.3.

I've tried to update a project, played with settings in pom. This is the closest I've got to working application.

My current ejb plugin configuration:

        <plugin>
            <artifactId>maven-ejb-plugin</artifactId>
            <version>2.5</version>
            <configuration>
                <archive>
                    <manifest>
                        <addClasspath>true</addClasspath>
                    </manifest>
                </archive>
                <ejbVersion>3.1</ejbVersion>
            </configuration>
        </plugin>

And the exception(the lowest level):

Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.LogManager
at java.net.URLClassLoader.findClass(URLClassLoader.java:600)
at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:243)
at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:786)
at java.lang.ClassLoader.loadClass(ClassLoader.java:764)
at com.ibm.ws.bootstrap.ExtClassLoader.loadClass(ExtClassLoader.java:134)
at java.lang.ClassLoader.loadClass(ClassLoader.java:741)
at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:62)
at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:58)
at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:585)
at java.lang.ClassLoader.loadClass(ClassLoader.java:741)
... 75 more

I suppose that it's the issue, but I do not know hot to fix it.

Update: tried adding to manifest section:

<classpathPrefix>lib/</classpathPrefix>

same result.

If you create an EAR file support of skinny wars those files which have been extracted must be located somewhere which mean in case of an EAR into lib folder of the EAR level. I don't know what RAD is doing here... — khmarbaise, Jun 20 '16 at 10:41
Yes, they are there. Just not referenced from nowhere. Also, see update for a question. — Anton, Jun 20 '16 at 10:43
The exceptions are being emitted by Websphere application server if you have deployed the EAR file ? — khmarbaise, Jun 20 '16 at 10:52
Yes. I may post whole exception, but I'm pretty sure that core exception is what I put in the question. — Anton, Jun 20 '16 at 10:56
The EAR file you have deployed has been built by Maven or with RAD ? — khmarbaise, Jun 20 '16 at 12:50
Means in other words the problem is located in RAD or usage of RAD? — khmarbaise, Jun 20 '16 at 12:54
Yes. I believe there is some misconfiguration or bug in m2e plugin. — Anton, Jun 20 '16 at 12:55
Sorry for delay, was away from computer - 1.6.2.20150902-0002 — Anton, Jun 20 '16 at 13:59

score 0 · Answer 1 · edited May 23 '17 at 11:58

0

This is a roundabout answer, but you might find more success starting with the EE projects: WAR, EAR, etc. and then using the "Convert to Maven projects" option.

You can find info here and here.

Once you know a Maven structure that will map back to the EE project structure in RAD you'd also be able to work in the other direction. Not sure how much work that leaves you if you're happy with your existing project format.

Not sure I answered your question, but this was too long for a comment so here it is...

edited May 23 '17 at 11:58

Community

1
1

answered Jun 21 '16 at 09:43

Scott Kurz

4,985
1
18
40

This is done already, the project started as RAD project (which hides ant under its skin) and had to be converted to maven, because CI and ant didn't worked well. After conversion I spotted that RAD behaves differently from native maven. – Anton Jun 21 '16 at 09:52

score 0 · Accepted Answer · edited May 23 '17 at 11:44

0

I've noticed that if I copy manifest.mf generated by maven to the project and then build the project with RAD, it takes the right file to the final EAR. It's a workaround. Also, according to this: m2e-wtp will only generate manifest if does not exist.

edited May 23 '17 at 11:44

Community

1
1

answered Jun 30 '16 at 09:34

Anton

1,409
1
19
37

Maven and RAD produce different EARs

2 Answers2