[jbosstools-issues] [JBoss JIRA] (JBIDE-10463) Runtime detection doesn't consider additions to "Default Classpath Entries"... cached results require refresh

[Max Rydahl Andersen (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650747#comment-12650747 ] 

Max Rydahl Andersen commented on JBIDE-10463:
---------------------------------------------

Juergen, we both aren't happy with this issue not being in M5 but the issue exists for all other servers too and is an unfortunate caching bug which for M5 need an eclipse restart once you created the server adapter to take effect.

I would rather have a working M5 with this restart kludge than risk accepting a patch the last minute that can potentially do worse. 

And please open jiras with the jars you find missing for your usecases - that is a much better way to get a default working set of jars on the classpath. This mechanism is just the "if everything else fails"-way out.

Thanks!

                
> Runtime detection doesn't consider additions to "Default Classpath Entries"... cached results require refresh
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-10463
>                 URL: https://issues.jboss.org/browse/JBIDE-10463
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.M4, 3.3.0.M5
>            Reporter: Juergen Zimmermann
>            Assignee: Rob Stryker
>             Fix For: 3.3.0.Beta1
>
>         Attachments: incomplete-jboss-7.1-runtime.jpg, JBIDE-10463.patch, JBIDE-10463.v2.patch
>
>
> I tried build 2011-12-12_16-41-07-H58. However, when I invoke Preferences > JBoss Tools > JBoss Tools Runtime Detection the resulting server config doesn't contain JARs that are configured in Preferences > Server > Runtime Environments > Default Classpath Entries. For instance I added:
> Name: JBoss EJB3 Extensions
> Root Directory: modules/org/jboss/ejb3/main
> Includes: **/*.jar
> The resulting classpath should contain jboss-ejb3-ext-api-2.0.0-beta-1.jar being located in $JBOSS_HOME/modules/org/jboss/ejb3/main.
> I'll attach a screenshot to illustrate the issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira