BTW, we also need to add the extra modules to distribution/pdetarget/pom.xml
so that we can generate the 3rd party bundles and configure the Eclipse
target platform so that the OSGi imports to 3rd party packages can be
resolved by PDE.
Thanks,
Raymond
--------------------------------------------------
From: "Raymond Feng" <[EMAIL PROTECTED]>
Sent: Monday, December 08, 2008 3:02 PM
To: <[email protected]>
Subject: Re: [2.0] Problems with the Eclipse Maven plugin?
Hi,
Please see my clarification on the following thread:
http://markmail.org/message/66wfto6z4ryfmx2r
Thanks,
Raymond
--------------------------------------------------
From: "Mike Edwards" <[EMAIL PROTECTED]>
Sent: Monday, December 08, 2008 2:54 PM
To: <[email protected]>
Subject: [2.0] Problems with the Eclipse Maven plugin?
Folks,
When running mvn -Peclipse on the 2.0 code, I am noticing that the
Eclipse project files generated by the plugin seem to have some problems.
Basically, I find that the project files have runtime dependencies
missing so that tests either fail entirely or report non-fatal warnings.
The problem area seems to relate to dependencies that are runtime
dependencies of the testcases (principally) - say, for example, that a
testcase uses a composite file that requires handling of
<interface.wsdl/> elements which requires the interface-wsdl-xml module
present at test runtime. It seems as if the plugin does not handle such
things correctly. If the dependency is not marked with a <scope/> in the
POM, it is ignored entirely. If it is marked <scope>test</scope> in the
POM, then it has been my experience to get duplicate entries in the
Eclipse dependencies, which have required manual exclusions in the POM to
deal with.
Is this a bug in the Eclipse plugin or is it meant to work like this?
Yours, Mike.
