Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: http://jira.jboss.com/jira/browse/JBIDE-1354 Project: JBoss Tools Issue Type: Feature Request Components: JBossAS Reporter: Max Andersen Fix For: 2.1 deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: http://jira.jboss.com/jira/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, libmanagement Reporter: Max Andersen Fix For: 2.1 deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: http://jira.jboss.com/jira/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, libmanagement Reporter: Max Andersen Assigned To: Rob Stryker Fix For: 2.2.x deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: https://jira.jboss.org/jira/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, libmanagement Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.0.0.cr1 deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: https://jira.jboss.org/jira/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, libmanagement Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.1.0 deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: https://jira.jboss.org/jira/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, libmanagement Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: LATER deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: https://issues.jboss.org/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, libmanagement Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Fix For: 3.3.0.M3 deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: https://issues.jboss.org/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, libmanagement Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Fix For: 3.3.0.M3 Attachments: 2011-07-20 13.56.bmml, 2011-07-20 13.56.png, 2011-07-20 14.00.bmml, 2011-07-20 14.00.png deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: https://issues.jboss.org/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, libmanagement Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Fix For: 3.3.0.M3 Attachments: 2011-07-20 13.56.bmml, 2011-07-20 13.56.png, 2011-07-20 14.00.bmml, 2011-07-20 14.00.png deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: https://issues.jboss.org/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, libmanagement Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Fix For: 3.3.0.M3 Attachments: 2011-07-20 13.56.bmml, 2011-07-20 13.56.png, 2011-07-20 14.00.bmml, 2011-07-20 14.00.png deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: https://issues.jboss.org/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, libmanagement Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Fix For: 3.3.0.M3 Attachments: 2011-07-20 13.56.bmml, 2011-07-20 13.56.png, 2011-07-20 14.00.bmml, 2011-07-20 14.00.png deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: https://issues.jboss.org/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, libmanagement Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Fix For: 3.3.0.M3 Attachments: 2011-07-20 13.56.bmml, 2011-07-20 13.56.png, 2011-07-20 14.00.bmml, 2011-07-20 14.00.png, JBIDE-1354_20110729.png deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: https://issues.jboss.org/browse/JBIDE-1354 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers, z - Legacy - libmanagement Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.3.0.M3 Attachments: 2011-07-20 13.56.bmml, 2011-07-20 13.56.png, 2011-07-20 14.00.bmml, 2011-07-20 14.00.png, JBIDE-1354_20110729.png deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.