[
https://issues.apache.org/jira/browse/IVYDE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619331#action_12619331
]
hibou edited comment on IVYDE-89 at 8/3/08 7:43 AM:
--------------------------------------------------------------
I have taken your patch Matt , I have improved the logging, the exception
catching, simplified the function {{findModuleDescriptor}} (some code already
exist to do that job) and make it compile on java 1.4.
I have tested and it works fine.
Thanks both of you for your contributions !
was (Author: hibou):
I have taken you patch Matt , I have improved the logging, the exception
catching, simplified the function {{findModuleDescriptor}} (some code already
exist to do that job) and make it compile on java 1.4.
I have tested and it works fine.
Thanks both of you for your contributions !
> Option to resolve to local eclipse projects
> -------------------------------------------
>
> Key: IVYDE-89
> URL: https://issues.apache.org/jira/browse/IVYDE-89
> Project: IvyDE
> Issue Type: Wish
> Components: classpath container
> Affects Versions: 2.0.0.alpha1
> Reporter: Antony James Wilkins
> Assignee: Nicolas Lalevée
> Priority: Minor
> Fix For: 2.0
>
> Attachments: eclipse_project_resolve.patch,
> ivyde_workspace_dependency_resolver.patch
>
>
> It would be nice if the classpath container were able to resolve local
> eclipse projects for dependencies on modules with
> revision="latest.integration".
> One approach might be to simply match eclipse projects against the names of
> the modules in the ResolveReport, although ideally the eclipse project should
> be identified by it's ivy module defined in that projects associated ivy.xml.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
