There are a few issues with the pom.xml and MANIFEST.MF.
1) Abuse of maven transitive dependencies, for example, we listed
tuscany-binding-ws-xml as a "compile" dependency to pull in
"tuscany-binding-ws". But in fact, tuscany-binding-ws-xml is not required
for compilation and it's only for runtime or test.
2) Unused OSGi Import-Package, for example, we had
org.apache.tuscany.sca.xsd.xml in the Import-Package and PDE added
tuscany-xsd-xml to the classpath. Meanwhile, the tuscany-xsd-xml is declared
in pom.xml as a runtime or test dependency. We create an explicit classpath
entry for that and it leads to duplicate classpath entries.
I have fixed the issues but I still cannot run the test cases as the current
contribution processing aggressively loads all composites in the
contribution and some of the policy declarations fail the loading.
Thanks,
Raymond
--------------------------------------------------
From: "Mike Edwards" <[EMAIL PROTECTED]>
Sent: Tuesday, December 09, 2008 3:16 PM
To: <[email protected]>
Subject: Re: [2.0] Problems with the Eclipse Maven plugin?
Raymond Feng wrote:
Hi,
Can you point me to the project you see problems? I already have all the
modules loaded in my Eclipse workspace and I can probably try what you
are doing.
Thanks,
Raymond
Raymond,
Sure, the ones I was having most problems with were the ones in the
binding-ws-axis2 module, many of which start up complete composites
containing a variety of artifacts, each of which places a runtime
dependency on its related processing module (eg interface-wsdl-xml, etc).
Yours, Mike.
