From notifications-return-10270-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org Tue Oct 06 09:30:59 2009 Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 30410 invoked from network); 6 Oct 2009 09:30:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Oct 2009 09:30:59 -0000 Received: (qmail 74223 invoked by uid 500); 6 Oct 2009 09:30:59 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 74169 invoked by uid 500); 6 Oct 2009 09:30:59 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 74160 invoked by uid 99); 6 Oct 2009 09:30:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2009 09:30:59 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2009 09:30:55 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5E054234C053 for ; Tue, 6 Oct 2009 02:30:31 -0700 (PDT) Message-ID: <916425949.1254821431383.JavaMail.jira@brutus> Date: Tue, 6 Oct 2009 02:30:31 -0700 (PDT) From: "Ivica Loncar (JIRA)" To: notifications@ant.apache.org Subject: [jira] Updated: (IVYDE-210) Dependencies marked for export into WEB-INF/lib should be fully exported regardles of the ordering in Java Build Path In-Reply-To: <1411717652.1254821431377.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ 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} {code} h3. Scenario 1 h4. 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.) h4. 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 h3. Scenario 2 h4. 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 h4. 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} {code} h3. Scenario 1 h4. 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.) h4. 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 h3. Scenario 2 h4. 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 h4. 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 > 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} > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > h3. Scenario 1 > h4. 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.) > h4. 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 > > h3. Scenario 2 > h4. 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 > h4. 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.