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] Commented: (IVYDE-255) Turning on Ivy's 'Resolve dependencies in workspace' prevents PDE's 'Plugin dependencies' container from working properly
Date Mon, 11 Oct 2010 15:09:36 GMT

    [ https://issues.apache.org/jira/browse/IVYDE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919861#action_12919861
] 

Konstantin Bakaras commented on IVYDE-255:
------------------------------------------

Thanks for the response, but now I can't give you such a thorough
explanation. I had hard deadlines and decided to choose completely different
way to build product for development. As a result I disabled Ivy's workspace
resolver, so now I can't reproduce that problem.


2010/10/11 Nicolas Lalevée (JIRA) <jira@apache.org>



> 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