You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Antony James Wilkins (JIRA)" <ji...@apache.org> on 2008/04/22 02:09:23 UTC
[jira] Created: (IVYDE-89) Option to resolve to local eclipse
projects
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
Reporter: Antony James Wilkins
Priority: Minor
Fix For: 2.0.0
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.
[jira] Issue Comment Edited: (IVYDE-89) Option to resolve to local
eclipse projects
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (IVYDE-89) Option to resolve to local eclipse
projects
Posted by "Antony James Wilkins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antony James Wilkins updated IVYDE-89:
--------------------------------------
Attachment: eclipse_project_resolve.patch
Patch file showing the simple approach of matching project name against dependency module name.
> 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
> Reporter: Antony James Wilkins
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: eclipse_project_resolve.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.
[jira] Resolved: (IVYDE-89) Option to resolve to local eclipse
projects
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée resolved IVYDE-89.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0
Assignee: Nicolas Lalevée
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.
[jira] Reopened: (IVYDE-89) Option to resolve to local eclipse
projects
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée reopened IVYDE-89:
----------------------------------
Reopening, this feature need better documentation (there are actually none).
> 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.
[jira] Updated: (IVYDE-89) Option to resolve to local eclipse
projects
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée updated IVYDE-89:
---------------------------------
Fix Version/s: (was: 2.0.0.alpha1)
> 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
> Priority: Minor
> Attachments: eclipse_project_resolve.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.
[jira] Updated: (IVYDE-89) Option to resolve to local eclipse
projects
Posted by "Matt Goldspink (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Goldspink updated IVYDE-89:
--------------------------------
Attachment: ivyde_workspace_dependency_resolver.patch
I've put together a patch which takes some of the code from a patch on [http://issues.apache.org/jira/browse/IVYDE-89] and on [https://issues.apache.org/jira/browse/IVYDE-43] but removes the workspace resolver requirement and instead does a post process of the container to resolve dependencies within the Eclipse workspace after a normal ivy resolve. I also add a config option on the Ivy configuration page to turn this on and off for individual projects.
Our team has been using this code for several months now and found it very beneficial. It would be great if this could be included in a future IvyDE? release.
Limitations: At the moment the code only matches projects in the workspace based on the _org_ and _module_ of a dependency. It ignores the _revision_ and does not match based on that because we want to just use a _"latest.revision"_ version and match only to projects in the same workspace with the same _org_ and _module_ . Therefore the limitation is that if you have two versions of the same project in your workspace the resolution code will only pick one of these versions. This is not an issue I expect many find a problem but I wanted to make any users aware of this.
This patch is provided subject to Apache License 2.0:
COPYRIGHT NOTICE AND DISCLAIMER:
Copyright (c) 2008, Contributor
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
> 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
> Priority: Minor
> 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.
[jira] Resolved: (IVYDE-89) Option to resolve to local eclipse
projects
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée resolved IVYDE-89.
----------------------------------
Resolution: Fixed
Some minimal documentation added.
> 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.