missing artifact references with pde mode enabled

Mistake: I meant to say [...] jetty versions below 6.1.5 [...].

No solution or even similar issues for somebody ?
Meanwhile, the issue extends to the wicket library (org.apache.wicket:wicket) which, in version 1.3.x is included in the eclipse classpath while version 1.4-m2 is not.

Ok, after some investigation I found that this problem seems to be caused by two factors:
1. my project has pde enabled
2. the specific dependencies not working are osgi bundles.
This seems to be a bad combination as we have the following in the EclipseClasspathWriter Class:
...
if ( config.isPde() && ( dep.isProvided() || dep.isOsgiBundle() ) )
{
return;
...(line 415)
Thus, not adding for example, jetty 6.1.10 (or any of the above mentioned dependencies) to the classpath file.
Now my problem is that I neither understand why this is nor what I can do to add these dependencies to my project.

I am thankful for any suggestions

I am also hit by this problem. As Benjamin pointed out I also think the problem is on line 415. It should have been

if ( config.isPde() && dep.isProvided() && dep.isOsgiBundle() )

i.e, don't add the dependency to the classpath if the dependency is provided AND it is a bundle AND the project is a PDE project.
It needs to be added to the class path if the dependency was not provided or it is not a OSGi bundle. Here is the patch

Index: src/main/java/org/apache/maven/plugin/eclipse/writers/EclipseClasspathWriter.java
===================================================================
— src/main/java/org/apache/maven/plugin/eclipse/writers/EclipseClasspathWriter.java (revision 674713)
+++ src/main/java/org/apache/maven/plugin/eclipse/writers/EclipseClasspathWriter.java (working copy)
@@ -412,7 +412,7 @@

// if the dependency is not provided and the plugin runs in "pde mode", the dependency is
// added to the Bundle-Classpath:

• if ( config.isPde() && ( dep.isProvided() || dep.isOsgiBundle() ) )
  + if ( config.isPde() && dep.isProvided() && dep.isOsgiBundle() ) { return; }

Gopal

Oops! Just figured out that the patch doesn't work. needs more work.

Any progress on this ? I would try to solve this myself but a "mvn install" on the maven-eclipse-plugin sources keeps stuck at the unit/integration tests with nearly 100 % cpu being used.

The build can take 10 minutes or minutes depending of the hardware.
You can try to patch the code and launch the build bypassing tests to quickly the result on a project.

If it only were 10 minutes. After 40 minutes I killed the process because my system became totally unresponsive. Seems that the temporary files cause the trouble. Maybe it's an os specific problem, I'll look for that.

yes, 40 minutes is too long. You can have a look at surefire reports which store integration tests results to see if something is wrong with your plateform.

Is there a resolution for this? It would be nice to not have to download the source and maintain it internally.

Does anybody require the current implementation? i.e. is anybody using OSGi bundle dependencies that aren't marked as provided? It seems like most people use provided scope.

We are using commons-math as a compile scope dependency, which has been an OSGi bundle since 1.2 (https://issues.apache.org/jira/browse/MATH-180).

@Edd Steel: Do you have pde mode enabled in the project where you use the commons-math bundle ?

I am working on the same project as Edd Steel (above) - we have pde mode enabled in the project which depends on commons-math. We have got round it by downgrading to 1.1. There appears to be a similar issue with commons-io.

I see the same problem. When <pde> is enabled, some bundle dependencies are missing.

Maybe plugin's author had reasons for implementing such a skipping
but nowadays the more and more maven artifacts became osgi-fied,
so skipping osgi-bundled artifact from being included in MANIFEST classpath (and skipping it beign linked to project as linkedResource)
looks as unpractical.

Currently there are at least 2 places in src where fixes should be applied:
already mentioned EclipseClasspathWriter.java and also EclipseProjectWriter.java around the code:
if ( dep.isAddedToClasspath() && !dep.isProvided() && !dep.isReferencedProject()
&& !dep.isTestDependency() && !dep.isOsgiBundle() )
{

Actually it would be great to have ability to specify whether include osgi bundles or not in plugin configuration options.
Thanks.

Patch file that's working for me.

Same problem here with slf4j-api-1.6.1 which is an OSGi bundle: dependency is not in provided scope, and PDE mode is enabled.
I used the patch against the 2.9 tagged source of the plugin, and it worked as expected: the .project and the .classpath contain now the slf4j-api reference.
Is there any hope to see this issue fixed in future release? Either not skipping the OSGi artefacts or a config option as proposed by Eugene.
Maintaining a custom MEP will not be easy in my current project context.