[
https://issues.apache.org/jira/browse/IVY-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Coene updated IVY-1063:
-------------------------------
Fix Version/s: (was: 2.1.0)
> add accessors to conflictManagers in
> org.apache.ivy.core.module.descriptor.DefaultModuleDescriptor to allow better
> maven pom generation
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: IVY-1063
> URL: https://issues.apache.org/jira/browse/IVY-1063
> Project: Ivy
> Issue Type: Wish
> Components: Maven Compatibility
> Affects Versions: 2.0
> Reporter: Felix Simmendinger
>
> One of the major drawbacks in ant-ivy development is that maven is the
> defacto standard so we need to produce best fitted pom files.
> To generate poms where local excludes are transferred is easy when you stick
> to conventions. To map overrides and conflicts to explicit dependencies is
> the most straight forward solution to transfer ivys superior dependency
> management to maven boiler plate. For overrides its quite easy but for
> conflicts we need to access the conflictManagers ModuleRules. Its private and
> there is no accessor in the interface.
> Another Point is how to deal with global excludes. It would be nice if
> canExclude(ModuleId id) would also work transitively or if there would be a
> transitive method, then it would be possible to work with global excludes for
> our own modules and local exlcludes for third party.
> We are building 50+ modules with overall 1.000K+ lines of code and we have to
> produce maven poms as best as possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
