ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Bakaras (JIRA)" <j...@apache.org>
Subject [jira] Created: (IVYDE-255) Turning on Ivy's 'Resolve dependencies in workspace' prevents PDE's 'Plugin dependencies' container from working properly
Date Wed, 08 Sep 2010 10:19:32 GMT
Turning on Ivy's 'Resolve dependencies in workspace' prevents PDE's 'Plugin dependencies' container
from working properly
-------------------------------------------------------------------------------------------------------------------------

                 Key: IVYDE-255
                 URL: https://issues.apache.org/jira/browse/IVYDE-255
             Project: IvyDE
          Issue Type: Bug
          Components: workspace resolver
    Affects Versions: 2.1.0
         Environment: Eclipse Helios x64 (win), Windows 7 x64, JDK 1.6.21 x64 (for Eclipse),
JDK 1.6.21 32-bit (as default jre runtime for projects).
            Reporter: Konstantin Bakaras


When I turn on Ivy's feature to resolve dependencies in workspace I have such a trouble. RCP's
Plug-in projects that even doesn't have Ivy-managed dependencies begin to report errors 'Access
restriction: The type [MyClass] is not accessible due to restriction on required project [OnePlugin]'.
All the dependencies set right in plug-in's dependencies part of MANIFEST.
And if I turn off the feature to resolve Ivy's dependencies in workspace and restart Helios,
all such errors go away after rebuild.
Also such an issue affects plug-in projects with Ivy dependency management but in that case
I can move Ivy container above 'Plug-in's dependencies' container so classes are being found
with Ivy.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message