[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-1354) Runtimes should be configurable with respect to what jars to return for certain runtimes

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-1354.
--------------------------------

    Resolution: Done


Hey Max: 

  for 1)  These settings are stored in an xml file in /.plugins/org.jboss.ide.eclipse.as.core/.global/filesets/runtimeClasspaths/org.jboss.ide.eclipse.as.runtime.32  (or any other runtiume id as the filename).  So it's not EASY to share, but, its possible. 

Currently it stores the data as filesets but there is no requirement in the API for this. This could definitely be enhanced with some effort (for (2))

> 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: 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira