[
https://issues.apache.org/jira/browse/IVYDE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862153#action_12862153
]
Erik-Berndt Scheper commented on IVYDE-236:
-------------------------------------------
I think the title of this issue should be updated to reflect the comment above.
Please change it to:
>> IVYDE changes defaultResolveMode in global Ivy settings to 'dynamic'
Also, the priority should be changed to blocker (or at least critical), because
it is a very serious regression in the sense that the default configuration now
makes IvyDE totally unusable for anything other than trivial projects.
People unaware of this change now get the wrong transitive dependencies for
every workspace project that depends on a module with transitive dependencies
using rev-contraints. Also any overrides are now ignored.
Another problem is that IvyDE now resolves differently from 'standard' IVY
(using Ant from the command-line) which I believe is unacceptable.
However, I believe that this new behavior MAY be useful in some exceptional
circumstances. But it should be an option in the global IVY configuration, so
that this behavior is configurable and a developer is aware of the fact that
the way to resolve dependencies has changed.
> Spring transitive dependencies resolved as latest.integration
> -------------------------------------------------------------
>
> Key: IVYDE-236
> URL: https://issues.apache.org/jira/browse/IVYDE-236
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
> Affects Versions: 2.1.0
> Reporter: AngerClown
> Attachments: IvyDE-236_testcase+logs.zip
>
>
> I am receiving resolution errors using IvyDE 2.1.0.201002011748-hudson-99 for
> Spring Framework related libraries. This may ultimately be an issue with
> Spring's ivy files, but the exact same setup is working with the
> 2.1.0.200911161501-hudson-79.log. Something appears to have changed with how
> resolution is being done between these two builds. In addition, running Ivy
> in Ant works so this is related to IvyDE and not base Ivy. Please see the
> attached for a testcase along with logs of the issue with both Hudson builds
> of IvyDE.
> I am listing Spring Beans as a dependency in my project and it appears that
> Spring Core and it's dependencies are failing. Spring beans lists Spring Core
> as a dependency
> <dependency org="org.springframework" name="org.springframework.core"
> rev="3.0.0.RELEASE" revConstraint="latest.integration"
> conf="compile->compile"/>.
> IvyDE looks like it's trying to find the revConstraint of latest.integration
> for Core even though my project's ivy.xml specifies 3.0.0.RELEASE. IvyDE does
> download Spring Core but then ignores it and errors because it cannot find
> latest.integration.
> Note that I have a <resolver> setup in ivysettings that uses the Spring Ivy
> repositories; I am not using the default ibiblio Maven repository. So, this
> issue appears with the Spring defined ivy.xml, not the ivy generated from M2
> conversion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
