I don't know exactly where the issue lies for my problem; if it is a
problem with the way I am attempting to use m2e-wtp, the maven-ear-plugin,
or something with the connector that publishes my Eclipse project to the
server.  I am hoping someone could at least point me in the right direction.

I have an EAR that I am trying to build and deploy to WebSphere.  In my
pom, my configuration is as follows:

<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<version>2.10.1</version>
<configuration>
<version>5</version>
<defaultLibBundleDir>lib/</defaultLibBundleDir>
<modules>

<webModule>
<groupId>com.ics.strongauth</groupId>
<artifactId>AuthRenfClientWeb</artifactId>
<contextRoot>strongauth</contextRoot>
</webModule>
<jarModule>
<groupId>${project.groupId}</groupId>
<artifactId>ComCommons</artifactId>
<bundleDir>/lib</bundleDir>
</jarModule>
<jarModule>
<groupId>${project.groupId}</groupId>
<artifactId>ComConfiguration</artifactId>
<bundleDir>/lib</bundleDir>
</jarModule>
</modules>
</configuration>
</plugin>
</plugins>
</build>


Each of the listed modules are listed as dependencies in the pom.xml file.

If I check the deployment assembly for my project, I see things
appropriately structured.  A bunch of files have been added to the EAR's
/lib folder (dependencies from AuthRenfClientWeb) as well as the my two
projects ComCommons and ComConfiguration.

If I right-click my project and Export -> Ear, I find a ComCommons.jar and
ComConfiguration.jar in my /lib folder.

However, if I try to publish my project to my WebSphere server, it
ignores/skips the jarModules.  There are no entries in any Classloader
pointing to the classpaths for ComCommons/target and
ComConfiguration/target, as I would expect.

If I close the projects, then it publishes the actual ComCommon.jar and
ComConfiguration.jar files to the /lib folder (as expected).

So the problem only occurs if the projects are opened, as it is supposed to
just add an entry to the target folder in the classpath.

Is this an m2e-wtp integration issue?  Is this a WebSphere Developer Tools
error?  I tend to believe it is a problem with the WebSphere connector, but
not sure.

Thanks!

Eric




However
_______________________________________________
m2e-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to