[
https://issues.apache.org/jira/browse/IVYDE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767831#action_12767831
]
Ivica Loncar edited comment on IVYDE-159 at 10/20/09 3:26 PM:
--------------------------------------------------------------
I believe this can be solved using multiple classpath containers.
Create classpath container for each ivy configuration and reorder containers in
the Java Build Path settings.
Be careful if it's a WTP project: the order in Java Build Path causes
unexpected results on WAR export and deployment (for more info see link in
IVYDE-210).
was (Author: iloncar):
I believe this can be solved using multiple classpath containers.
Create classpath container for each ivy configuration and reorder containers in
the Java Build Path settings.
Be careful if it's a WTP project since because of the way WTP behaves right now
the order in Java Build Path has effect on the WAR export and deployment (for
more info see link in IVYDE-210)
> Explicit ordering of configurations
> -----------------------------------
>
> Key: IVYDE-159
> URL: https://issues.apache.org/jira/browse/IVYDE-159
> Project: IvyDE
> Issue Type: Improvement
> Reporter: Will Gorman
>
> In IvyDE, I can select which configurations are used in the eclipse
> environment, but I can't specify in which order the jar files are listed in
> the classpath. This is important in our JUnit environment, because we have
> mock jars that override the default jars for testing. In our Ant
> environment, the test configuration appears in the classpath before the
> default configuration, but I can't specify that in IvyDE.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
