[ https://issues.apache.org/jira/browse/IVYDE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivica Loncar updated IVYDE-210:
-------------------------------
Description:
Create dynamic web project and create ivy configuration.
This is a relevant part of ivy.xml that can be used to demonstrate bug.
{code:xml}
{code}
_Scenario 1_
_Steps_
* go to the Java Build Path and reorder libraries (last tab under Java Build Path) in the following order:
# source folder
# JRE System library
# Apache Tomcat
# _runtime_
# _compile_
* under J2EE Module dependecies we mark ivy.xml [compile] for export
* we can see that compile classpath container contains libraries like aopalliance, commons-fileupload, etc. (more than 4 jars)
* publish direclty to the tomcat installation (Do not use workspace as server location. You have to setup server path and deploy path.)
_Result_
- under TOMCAT_HOME\webapps\APPNAME\WEB-INF\lib we get:
- jms-1.1.jar
- jstl-1.2.jar
- spring-jdbc-2.5.6.jar
_Scenario 2_
_Steps_
- go to the Java Build Path and reorder libraries such that compile comes before runtime:
1. source folder
1. JRE System library
1. Apache Tomcat
1. _compile_
1. _runtime_
- publish project to tomcat installation
_Result_
- under {TOMCAT_HOME}\webapps\{APPNAME}\WEB-INF\lib we get all of the libraries that we can see under compile configuration in ivy classpath container
The first scenario demonstrates the bug and should be fixed:
- dependencies marked for J2EE export into WEB-INF/lib should be fully exported in all circumstances and Java Build Path ordering should not have influence on it
was:
Create dynamic web project and create ivy configuration.
This is a relevant part of ivy.xml that can be used to demonstrate bug.
{code:xml}
{code}
_Scenario 1_
_Steps_
- go to the Java Build Path and reorder libraries (last tab under Java Build Path) in the following order:
1. source folder
1. JRE System library
1. Apache Tomcat
1. _runtime_
1. _compile_
- under J2EE Module dependecies we mark ivy.xml [compile] for export
- we can see that compile classpath container contains libraries like aopalliance, commons-fileupload, etc. (more than 4 jars)
- publish direclty to the tomcat installation (Do not use workspace as server location. You have to setup server path and deploy path.)
_Result_
- under {TOMCAT_HOME}\webapps\{APPNAME}\WEB-INF\lib we get:
- jms-1.1.jar
- jstl-1.2.jar
- spring-jdbc-2.5.6.jar
_Scenario 2_
_Steps_
- go to the Java Build Path and reorder libraries such that compile comes before runtime:
1. source folder
1. JRE System library
1. Apache Tomcat
1. _compile_
1. _runtime_
- publish project to tomcat installation
_Result_
- under {TOMCAT_HOME}\webapps\{APPNAME}\WEB-INF\lib we get all of the libraries that we can see under compile configuration in ivy classpath container
The first scenario demonstrates the bug and should be fixed:
- dependencies marked for J2EE export into WEB-INF/lib should be fully exported in all circumstances and Java Build Path ordering should not have influence on it
Btw. JIRA doesn'f format this entry correctly.
> Dependencies marked for export into WEB-INF/lib should be fully exported regardles of the ordering in Java Build Path
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: IVYDE-210
> URL: https://issues.apache.org/jira/browse/IVYDE-210
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
> Environment: latest ivy from trunk, eclipse 3.5, WTP 3.1
> Reporter: Ivica Loncar
>
> Create dynamic web project and create ivy configuration.
> This is a relevant part of ivy.xml that can be used to demonstrate bug.
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> _Scenario 1_
> _Steps_
> * go to the Java Build Path and reorder libraries (last tab under Java Build Path) in the following order:
> # source folder
> # JRE System library
> # Apache Tomcat
> # _runtime_
> # _compile_
> * under J2EE Module dependecies we mark ivy.xml [compile] for export
> * we can see that compile classpath container contains libraries like aopalliance, commons-fileupload, etc. (more than 4 jars)
> * publish direclty to the tomcat installation (Do not use workspace as server location. You have to setup server path and deploy path.)
> _Result_
> - under TOMCAT_HOME\webapps\APPNAME\WEB-INF\lib we get:
> - jms-1.1.jar
> - jstl-1.2.jar
> - spring-jdbc-2.5.6.jar
> _Scenario 2_
> _Steps_
> - go to the Java Build Path and reorder libraries such that compile comes before runtime:
> 1. source folder
> 1. JRE System library
> 1. Apache Tomcat
> 1. _compile_
> 1. _runtime_
> - publish project to tomcat installation
> _Result_
> - under {TOMCAT_HOME}\webapps\{APPNAME}\WEB-INF\lib we get all of the libraries that we can see under compile configuration in ivy classpath container
> The first scenario demonstrates the bug and should be fixed:
> - dependencies marked for J2EE export into WEB-INF/lib should be fully exported in all circumstances and Java Build Path ordering should not have influence on it
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.