[ 
http://jira.codehaus.org/browse/MECLIPSE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148613#action_148613
 ] 

Jacob Northey commented on MECLIPSE-459:
----------------------------------------

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.

> missing artifact references with pde mode enabled
> -------------------------------------------------
>
>                 Key: MECLIPSE-459
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-459
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Dependencies resolution and build path, PDE 
> support
>    Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.5.1
>         Environment: Maven version: 2.0.9
> Java version: 1.5.0_11
> OS name: "linux" version: "2.6.15-51-686" arch: "i386" Family: "unix"
>            Reporter: Benjamin Voigt
>            Priority: Critical
>         Attachments: pde_dep_missing.zip
>
>
> Some artifacts are not referenced after executing mvn eclipse:eclipse and 
> having pde mode enabled. The strange thing is, that this does only happen for 
> particluar versions of an artifact.
> Two artifacts that I found with this problem are jetty (org.mortbay.jetty) 
> and slf4j-log4j12 (org.slf4j-log4j12). Jetty versions beyond 6.1.5 work with 
> pde enabled, higher versions do not. Same for slf4j-log4j12 versions =< 1.1.0.
> Attached is an example project demonstrating the problem. Turn pde mode 
> on/off in the pom and execute mvn eclipse:eclipse.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to