[
https://issues.apache.org/jira/browse/IVYDE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVYDE-141.
-----------------------------------
Resolution: Fixed
I have to admit I didn't understand your use case, but I made IVY_HOME exported
as a classpath variable in Eclipse set to {{System.getProperty("user.home") +
"/.ivy2"}}.
I let that classpath variable editable as the home of Ivy can be set to another
path in Ivy.
> Export IVY_HOME as a classpath variable
> ---------------------------------------
>
> Key: IVYDE-141
> URL: https://issues.apache.org/jira/browse/IVYDE-141
> Project: IvyDE
> Issue Type: Improvement
> Affects Versions: 2.0.0.beta1
> Reporter: Robert Munteanu
> Assignee: Nicolas Lalevée
> Fix For: 2.0.0.final
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> It would be quite convenient to export a classpath variable ( IVY_HOME )
> which would then be usable in eclipse. The reason is that some classpaths (
> notably the anontation processor factory path ) do not use the project build
> path but there is the possibility of specifying a classpath based on a
> variable ( e.g. IVY_HOME/.cache/... ).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
