Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 44178 invoked from network); 1 Oct 2009 12:31:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Oct 2009 12:31:50 -0000 Received: (qmail 69773 invoked by uid 500); 1 Oct 2009 12:31:50 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 69719 invoked by uid 500); 1 Oct 2009 12:31:50 -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 69710 invoked by uid 99); 1 Oct 2009 12:31:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2009 12:31:50 +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; Thu, 01 Oct 2009 12:31:47 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id F339D234C052 for ; Thu, 1 Oct 2009 05:31:23 -0700 (PDT) Message-ID: <479967924.1254400283987.JavaMail.jira@brutus> Date: Thu, 1 Oct 2009 05:31:23 -0700 (PDT) From: "Jon Schneider (JIRA)" To: notifications@ant.apache.org Subject: [jira] Created: (IVYDE-208) Ivy Resolve Visualizer 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 Ivy Resolve Visualizer ---------------------- Key: IVYDE-208 URL: https://issues.apache.org/jira/browse/IVYDE-208 Project: IvyDE Issue Type: New Feature Reporter: Jon Schneider I am kind of excited about this one. I would like to be able to see the resolve report depicted graphically, showing me clearly how particular dependencies wound up on the classpath, what nodes got evicted, what dependencies a particular transitive dependency has, etc etc. Ivy can sometimes fall into the category of "automagically" doing so much for us on the classpath, that developers can take it for granted. Especially when a version conflict arises out of a resolution (by which two different revisions are resolved that aren't under the same eviction context), I see developers getting very confused. I hope this visualization will help them understand. So far I have built this visualizer with the following features: 1. Automatic highlights of: - Shortest path to root - All paths to root - All callers - All dependencies - Other revisions 2. Filtering options: - Hide evictions - Limit depth (only show up to the n-th level transitive dependency) - Hide selection 3. Focusing: - Focus on an ivy classpath container - Focus on a selection 4. Zooming 5. Print screen -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.