maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenney Westerhof (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MECLIPSE-147) Dependencies that are inherited from subprojects that are specified in Require-Bundle or Import-Package should be excluded
Date Sat, 07 Oct 2006 01:31:26 GMT
    [ http://jira.codehaus.org/browse/MECLIPSE-147?page=comments#action_76869 ] 
            
Kenney Westerhof commented on MECLIPSE-147:
-------------------------------------------

I'm sorry but this patch is totally useless :)

Where did you specify the 'Require-Bundle'?

I don't think you can just drop the dep, even if the OSGI header imports the packages.
The difference is just that when you create a bundle, you don't want to incorporate
dependencies that you declare as Require-Bundle. This looks to me like
a PDE configuration issue that cannot be solved by just removing dependencies
between projects. 

Maybe you can clarify a bit? I don't see how specifying a Require-Bundle somewhere in project
A
automatically adds B to the classpath - doesn't it have to be a project-reference or other
dependency?


> Dependencies that are inherited from subprojects that are specified in Require-Bundle
or Import-Package should be excluded
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-147
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-147
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: PDE support
>            Reporter: David Boden
>         Attachments: patch.txt
>
>
> Project A depends on Project B
> Project A adds Project B in as a "Require-Bundle".
> Project B exports its dependencies.
> Project A therefore does not want to link resources in .project and .classpath. It already
inherits them by depending on Project B.
> I've attached a patch which is, apologies, completely specific to my project. What I'm
trying to do in the patch is to not just exclude any reactor projects but also exclude *any
dependencies that originate from reactor dependencies*. I wanted to take the "node" variable
and ask whether its parent was a reactor project. However, I don't think the ResolutionNode
API allows me to traverse up the hierarchy towards the parent.

-- 
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

        

Mime
View raw message