[
https://issues.jboss.org/browse/JBIDE-20577?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-20577:
-------------------------------------
With JBIDE-22157 being fixed, what is needed now is a way to display the embedded modules
in the deployment page.
Filtering is done "By deployable" by default, which hides embedded jar projects.
At the very least the default filter should be "By Module Name".
As a side note, the UI os visually pretty confusing, in OSX at least, as the widgets
appear active, but are effectively read-only, in the deployment page. You can't change
the filter for instance. There's a tiny message about the server needing 0 modules,
but it's really not obvious.
!http://content.screencast.com/users/fbricon/folders/Jing/media/e7e63f36-0962-4aea-a692-a45e217d5565/00000413.png|width=800!
Allow setting exploded or zipped on per-module basis
----------------------------------------------------
Key: JBIDE-20577
URL:
https://issues.jboss.org/browse/JBIDE-20577
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.3.0.CR1
Reporter: Rob Stryker
Fix For: 4.4.0.Alpha2
While in the past, we automatically zipped up dependent utility projects, we recently
switched to allowing exploded utility projects for appserver versions that suppoort it.
Some users have determined this is slower for their usecase, and we should investigate
giving users more control over this feature.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)