[
https://issues.apache.org/jira/browse/IVYDE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVYDE-306.
-----------------------------------
Resolution: Fixed
Fix Version/s: trunk
Assignee: Nicolas Lalevée
> Support Accepted Types: *
> -------------------------
>
> Key: IVYDE-306
> URL: https://issues.apache.org/jira/browse/IVYDE-306
> Project: IvyDE
> Issue Type: Improvement
> Components: classpath container, ivy editor
> Affects Versions: 2.2.0.beta1
> Environment: Windows 7 Enterprise 64-bit, MyEclipse 9.1 64-bit, Java
> 1.6.0_31 64-bit
> Reporter: J.C. Hamlin
> Assignee: Nicolas Lalevée
> Labels: accepted, ivy, resolve, types
> Fix For: trunk
>
>
> IVYDE-24 introduced a capability to limit what types will be part of the
> resolve, called "accepted types". However, it did not retain the original
> functionality of allowing all types to be accepted. In an Ivy resolve, if the
> types are not specified, it defaults to not limiting the types (i.e.
> basically all types are accepted).
> We tried using an empty string, and a *, for the Accepted Types field, and in
> both cases, the Ivy classpath container disappeared from the project
> (presumably resolved to no types).
> We have multiple Ivy jar file types (jar, module-lib, webapp-lib, ear-lib,
> etc), and more are being added every day. We don't want to have to keep this
> list in sync, and would prefer to just be able to leave the field blank, or
> put in * for its value and allow it to do the Ivy resolve without limiting
> the types in the resolve.
> Is there currently a way to do this? If not, we'd like the feature added.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
