You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2010/08/24 12:18:15 UTC
[jira] Resolved: (IVYDE-240) WorkspaceResolver: deal with
self-dependencies
[ https://issues.apache.org/jira/browse/IVYDE-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée resolved IVYDE-240.
-----------------------------------
Assignee: Nicolas Lalevée
Fix Version/s: 2.2.0
Resolution: Fixed
Self dependencies are now supported. Thanks for your report.
> WorkspaceResolver: deal with self-dependencies
> ----------------------------------------------
>
> Key: IVYDE-240
> URL: https://issues.apache.org/jira/browse/IVYDE-240
> Project: IvyDE
> Issue Type: Improvement
> Components: workspace resolver
> Affects Versions: 2.0.0.final
> Reporter: Stepan Koltsov
> Assignee: Nicolas Lalevée
> Fix For: 2.2.0
>
>
> I have several ivy modules (sources with ivy.xml files) imported as *single* Eclipse project (to ease Eclipse configuration). Those modules have internal dependencies (one ivy.xml rererences jar that is provided by another ivy.xml in the same Eclipse project). These internal dependencies should be evicted by WorkspaceResolver. Currently WorkspaceResolver fails to recognize those internal dependencies because of explicit self-reference check:
> {code}
> for (int i = 0; i < projects.length; i++) {
> IJavaProject javaProject = projects[i];
> if (resolvingJavaProject.equals(javaProject)) {
> // we don't want to introduce self dependency
> continue;
> }
> ...
> }
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.