[
https://issues.jboss.org/browse/JBIDE-12603?page=com.atlassian.jira.plugi...
]
Snjezana Peco resolved JBIDE-12603.
-----------------------------------
Resolution: Done
The issue isn't related to Runtime Detection, but to JBoss AS.
It happens because the org.jboss.ide.eclipse.archives.webtools plugin isn't started
when calling the Runtime Detection preference page.
It is started when calling the New Server wizard.
The plugin adds IServerLifecycleListener that creates the default fileset.
Default fileset not added for first detected runtime
----------------------------------------------------
Key: JBIDE-12603
URL:
https://issues.jboss.org/browse/JBIDE-12603
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Alpha1
Environment: JBDS 6.0.0.Alpha1b H25
Reporter: Martin Malina
Assignee: Snjezana Peco
Fix For: 4.0.0.Alpha2
Attachments: no-fileset.png
With JBIDE-12453 in place, there now is an example fileset added for AS7.0, AS7.1 and
EAP6 server adapters.
However, if you have a new workspace and add one of these servers using the runtime
detection, no fileset gets created. When you add another one, it will have a fileset
defined. Also, if you add a server manually rather than using runtime detection, it will
have a fileset as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira