Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 45885 invoked from network); 15 Sep 2009 16:06:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Sep 2009 16:06:52 -0000 Received: (qmail 14595 invoked by uid 500); 15 Sep 2009 16:06:52 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 14518 invoked by uid 500); 15 Sep 2009 16:06:52 -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 14377 invoked by uid 99); 15 Sep 2009 16:06:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2009 16:06:52 +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, 15 Sep 2009 16:06:48 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A3F75234C1E9 for ; Tue, 15 Sep 2009 09:05:57 -0700 (PDT) Message-ID: <766823250.1253030757670.JavaMail.jira@brutus> Date: Tue, 15 Sep 2009 09:05:57 -0700 (PDT) From: "Jason Dilley (JIRA)" To: notifications@ant.apache.org Subject: [jira] Commented: (IVYDE-200) The gui wizard crash when adding a IvyDE Managed Dependencies library to a .launch file's classpath In-Reply-To: <2138865548.1252685217475.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/IVYDE-200?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12755= 546#action_12755546 ]=20 Jason Dilley commented on IVYDE-200: ------------------------------------ Yes, when I mentioned that I had done an install from the trunk I was using= the Hudson builds as referenced on the IvyDE download page (It refers us t= o use http://hudson.zones.apache.org/hudson/view/Ant/job/IvyDE-updatesite/l= astSuccessfulBuild/artifact/trunk/build) I hadn't paid attention to the build date in the Hudson builds. I did a man= ual build from the svn trunk source just now, and the gui now displays prop= erly when adding the Ivy library to a launch classpath.=20 One issue, though, regarding the Resolve issue you were mentioning. You ha= d previously said that a launch wasn't tied to a project, so we'd need to p= rovide an explicit file path. We never did, as it appeared that the launch= es were properly tied to a project. I assumed that at least for JUnit's wh= ere you have to specify a project and a class that would always be the case= . Whatever the reason, all of our JUnit launches did properly find and use= the right ivy.xml without providing anything on the path other than 'ivy.x= ml'. With the latest trunk changes, though, it's now requiring an explicit file = path. This would seem to not be desired, as an explicit path includes evid= ence of my OS and the location of my workspace i.e. c:/appWorkspaces/worksp= ace1/project1/ivy.xml whereas another developer's path for the same file ma= y be /home/developer1/workspaceA/project1/ivy.xml (We often pull the same c= ode into multiple workspaces for parallel development efforts). In these c= ases, developers can't share .launches, which is a significant issue as we = have dozens of JUnit's with corresponding launches, all checked into CVS to= allow reuse. Is it possible to either change it back to recognize the project as it was = before, or if we need to supply a path to the ivy file have that path be re= lative to the workspace root, and not the file system root? For my example= above, this would be: '/project1/ivy.xml' > The gui wizard crash when adding a IvyDE Managed Dependencies library to = a .launch file's classpath > -------------------------------------------------------------------------= -------------------------- > > Key: IVYDE-200 > URL: https://issues.apache.org/jira/browse/IVYDE-200 > Project: IvyDE > Issue Type: Bug > Affects Versions: 2.0.0.final > Environment: Windows XP sp3, Springsource Tool Suite 2.1 (Eclipse= 3.5), IvyDE 2.0.0 Final, Ivy 2.1 RC1 > Reporter: Jason Dilley > Assignee: Nicolas Lalev=C3=A9e > Fix For: 2.1.0 > > > When adding an IvyDE library to the build path for a Java project, everyt= hing goes fine. I receive the gui wizard which locates the ivy.xml file an= d let's me pick which confs I want to use. > However, when I try to do the same thing for a .launch file (i.e. setting= up the launch for a JUnit Test case), once I choose Add Library and select= IvyDE Managed Dependencies and hit Next, the wizard should proceed to the = next screen, but instead it stays on the 'Select library type to add' scree= n. It acts as if it's proceeding though the flow, however. It does pop up= a error "balloon" which says 'Ivy file not found' even though it's still o= n the 'Select library screen'. The ivy.xml is in the correct place, as I c= an add an Ivy library to the project's build path just fine. I can then cl= ick the Next button again, which takes me to a screen which says "Choose iv= y file and its configurations", but the screen is completely blank (no labe= ls, form fields, etc.) and I still have the error "balloon" mentioned earli= er. From here I can click Finish, and the library is added to the .launch'= s classpath, but something about it causes the JUnit to not load any depend= encies contained in the ivy.xml file. > In my particular case it was obvious as I would get the exception below = when running the JUnit: > java.lang.NoClassDefFoundError: org/junit/runner/notification/RunListener > Here's the classpath entry which was added from the above steps. > > Instead of adding the library individually like outline above, if I choos= e to add the project to the .launch's classpath accepting all of it's expor= ted entries and required projects, I get the entry below. Note the differe= nce - confs=3Ddefault instead of confs=3D* from the first entry. > > If I change the first entry to match the second in regards to confs=3Ddef= ault, then the dependencies contained in the ivy.xml are loaded properly. --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.