6:15 a.m.
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://jira.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Fix For: 3.2.0.Beta2
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:40 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.s...
]
Max Andersen updated JBIDE-7524:
--------------------------------
Component/s: JBossAS
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://jira.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Fix For: 3.2.0.Beta2
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:31 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco commented on JBIDE-7524:
--------------------------------------
1) The list of links to "JBoss Runtimes" is bad ui - fills
up the screen with alot of whitespace (and its Runtimes not runtime)
Agree.
2) The import/export buttons does not seem to do anything beyound
calling import/export dialog.
JBT Export/Import would need to export/import WTP and jBPM server definitions. That was
working correctly before (JBDS 4.0.0.Beta1, for instance). Will check what was changed in
the meantime (JBIDE-7373 and JBIDE-7370 include a lot of changes in the runtime plugin).
3) Search has a cancel button but it doesn't do anything
Can't reproduce on Windows and Linux. The Cancel button stops searching. Try to search
the root folder and cancel it to check the issue.
4) Seam webapps seem to be picked up as seam runtimes - is that
intended ?
The function has been copied from the installer. Will check and try to fix that.
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
Seam, AS, jBPM and Drools are part of EAP/SOA-P and aren't shown in the list that the
user can see, but they are recognized and configured if they exist.
Do you think we need to show AS/Seam/Drools/jBPM runtimes when the engine recognizes
EAP/SOA-P ?
7) The import/export of WTP servers seem to be a very bad hack...we
probably have to live with it but at least we should try and make our import/export
simply wrap the relevant runtimes
Runtime Export transfers WTP's servers.xml to the Eclipse preferences. Import loads
these servers using the WTP API. The only problem is that the preference pages aren't
refreshed and the user has to close/open Window>Preferences to see new runtimes.
That's why I propose to move the JBoss Runtimes preference page to an Eclipse wizard,
that would have the UI Max described in JBIDE-7527. The runtime plugin doesn't
export/import the WTP/JBT Server Runtimes, but delegates that function to WTP.
> JBoss Tools Runtimes improvements
> ---------------------------------
>
> Key: JBIDE-7524
> URL: https://jira.jboss.org/browse/JBIDE-7524
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JBossAS
> Affects Versions: 3.2.0.Beta1
> Reporter: Max Andersen
> Assignee: Snjezana Peco
> Fix For: 3.2.0.Beta2
>
>
> After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
> I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills
up the screen with alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound
calling import/export dialog.
3) Search has a
cancel button but it doesn't do anything
4) Seam webapps
seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
> 7) The import/export of WTP servers
seem to be a very bad hack...we probably have to live with it but at least we should try
and make our import/export simply wrap the relevant runtimes
> Furthermore these settings seem to not persist between workspaces and does not handle
the original usecase of having runtimes configured when starting up a new workspace
(requiring users to import/export is not the solution)
> I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:55 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.s...
]
Max Andersen commented on JBIDE-7524:
-------------------------------------
2) The import/export buttons does not seem to do anything beyound
calling import/export dialog.
By this I mean the buttons simply does not seem to do anything that isn't already
available from the normal import/export wizards.
I was not talking about the import/export not actually working. I assumed they work within
the limits discussed elsewhere.
I was just suggesting that since this search are not working well from within the
preferences pane no reason to have import/export
button just start the general import/export wizard when users can just use the normal
import/export.
3) Search has a cancel button but it doesn't do anything
Here is a screencast showing me scanning my home folder and root:
http://screencast.com/t/mRwL0QcY
The search does stop, but it is not a very instant stop - it takes a few seconds,
and sometimes many seconds.
Seam, AS, jBPM and Drools are part of EAP/SOA-P and aren't shown
in the list that the user can see, but they are recognized and configured if they exist.
Ok - didn't notice that but that does seem to be what happens. Might been the
"preferences doesn't refresh" issue ?
Do you think we need to show AS/Seam/Drools/jBPM runtimes when the
engine recognizes EAP/SOA-P ?
Wouldn't that be the most consistent ?
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://jira.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Fix For: 3.2.0.Beta2
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:26 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco commented on JBIDE-7524:
--------------------------------------
By this I mean the buttons simply does not seem to do anything that
isn't already available from the normal import/export wizards.
I was not talking about the import/export not actually working. I assumed they work
within the limits discussed elsewhere.
I was just suggesting that since this search are not working well from within the
preferences pane no reason to have import/export
button just start the general import/export wizard when users can just use the normal
import/export.
The standard Eclipse export/import wizard (File>Export/Import>Preferences)
exports/imports Eclipse preferences. It doesn't export/import WTP and jBPM servers
because the jBPM and WTP plugin configure their own servers in a specific way (using
servers.xml and jbpm-installations.xml).
The runtime plugin exports/imports all standard Eclipse preferences as well as WTP and
jBPM servers. It does that in the following way:
When you click the Export button on the JBoss Runtimes preference page, the runtime plugin
does the following:
- converts WTP and jBPM server definition files (servers.xml and jbpm-installations.xml)
to string and set the specific the runtime preferences I have created in order to convert
those server definitions to the Eclipse preferences ("servers" and
"jbpms")
- calls the standard Eclipse export preference wizard that exports Eclipse preferences
including the "servers" and "jbpms" preferences
When you click the Import button on the JBoss Runtimes preference page, the runtime plugin
does the following:
- calls the standard Eclipse import preference wizard and imports Eclipse preferences
including the "servers" and "jbpms" preferences
- converts the "servers" and "jbpms" preference values to the
servers.xml and jbpm-installations.xml files and configures WTP and jBPM servers using WTP
and jBPM API.
JBDS also creates these servers when starting the first time. That is the reason why I
have added that functionality to the JBoss Runtimes preference page.
If we don't need to export/import WTP and jBPM servers (because we don't need them
or because WTP and jBPM will implement them), we can remove the Export/Import button from
the JBoss Runtimes preference page.
The search does stop, but it is not a very instant stop - it takes a
few seconds,
and sometimes many seconds.
Cancel is called for every directory. If a directory has a lot of children (especially of
the directory type), Cancel can be slow. Will try to call the Cancel action more
frequently.
> Do you think we need to show AS/Seam/Drools/jBPM runtimes when
the engine recognizes EAP/SOA-P ?
Wouldn't that be the most consistent ?
I will add them if you want.
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://jira.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Fix For: 3.2.0.Beta2
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:10 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco commented on JBIDE-7524:
--------------------------------------
The attached patch includes the following changes:
- when calling the Search and Import action, the Preferences dialog is closed and opened
again which solves the problem with refreshing preference pages
Now you can create servers and runtimes using the Search button, export, import them and
the changes will be visible immediately.
- Runtime is renamed to Runtimes in the links
- the Seam recognizer is improved (web aplications are not recognized as Seam Runtimes)
- Cancel is called more frequently
- created a jira and patch for the problem with export/import Seam preferences (see
https://jira.jboss.org/browse/JBIDE-7577)
- when the runtime plugin recongizes EAP or SOA-P, the user is notified if the runtime
includes Seam, Drools and/or jBPM (see runtimeDialog.png)
In order to see the difference between the standard Eclipse Export/Import preferences and
JBoss Runtimes Export/Import preferences, you can do the following:
- create some Seam, Drools, JBoss AS, WTP, jBPM runtimes
- call File>Export>Preferences
- call File>Export>Preferences
- choose "JBoss Runtimes" preferences (or Export All Preferences)
- export the preferences to a file (testEclipseStandard.epf, for instance)
- call Window>Preferences>JBoss Tools>JBoss Runtimes
- click the Export button
- export the preferences to a file (testJBossRuntimes.epf, for instance)
- close Eclipse
- restart Eclipse in a new workspace
- call File>Import>Preferences
- choose the "JBoss Runtimes" preferences (or Import All Preferences)
- point to the file you previously exported using the standard Eclipse Export
wizard(testEclipseStandard.epf)
- import the preferences
You will see that WTP servers and jBPM runtimes aren't imported. They aren't
imported with the standard Eclipse Import wizard even if you use the testJBossRuntimes.epf
file.
- close Eclipse
- restart Eclipse in a new workspace
- call Window>Preferences>JBoss Tools>JBoss Runtimes
- click the Import button
- point to the file you previously exported using the JBoss Runtimes Export action
(testJBossRuntimes.epf)
- import the preferences
Now, all the runtimes including WTP and jBPM servers are imported correctly (the patch for
https://jira.jboss.org/browse/JBIDE-7577 has to be applied in order Seam Runtimes to work)
and shown immediately.
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://jira.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Fix For: 3.2.0.Beta2
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:12 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco updated JBIDE-7524:
---------------------------------
Attachment: runtimeDialog.png
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://jira.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Fix For: 3.2.0.Beta2
Attachments: runtimeDialog.png
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:16 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco updated JBIDE-7524:
---------------------------------
Attachment: org.jboss.tools.runtime.patch
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://jira.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Fix For: 3.2.0.Beta2
Attachments: org.jboss.tools.runtime.patch, runtimeDialog.png
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:09 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco commented on JBIDE-7524:
--------------------------------------
The patch is applied. The includeXXX methods are moved from Activator to handlers.
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://jira.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Fix For: 3.2.0.Beta2
Attachments: org.jboss.tools.runtime.patch, runtimeDialog.png
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:18 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://jira.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin.s...
]
Max Andersen updated JBIDE-7524:
--------------------------------
Fix Version/s: 3.2.0.CR1
(was: 3.2.0.Beta2)
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://jira.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Fix For: 3.2.0.CR1
Attachments: org.jboss.tools.runtime.patch, runtimeDialog.png
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:23 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://issues.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin...
]
Snjezana Peco updated JBIDE-7524:
---------------------------------
Priority: Critical (was: Major)
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://issues.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.2.0.CR1
Attachments: org.jboss.tools.runtime.patch, runtimeDialog.png
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:48 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://issues.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin...
]
Snjezana Peco resolved JBIDE-7524.
----------------------------------
Resolution: Out of Date
This issue will be fixed within JBIDE-7527.
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://issues.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Max Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.2.0.CR1
Attachments: org.jboss.tools.runtime.patch, runtimeDialog.png
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:28 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-7524) JBoss Tools Runtimes improvements
[
https://issues.jboss.org/browse/JBIDE-7524?page=com.atlassian.jira.plugin...
]
Dominik Pospisil closed JBIDE-7524.
-----------------------------------
Verified (jbdevstudio-product-eap-linux-gtk-x86_64-4.0.0.v201101192139R-H84-CR1.jar
).
JBoss Tools Runtimes improvements
---------------------------------
Key: JBIDE-7524
URL: https://issues.jboss.org/browse/JBIDE-7524
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.2.0.CR1
Attachments: org.jboss.tools.runtime.patch, runtimeDialog.png
After the discussion on mailing list we need to fix the current jboss tools runtime
page/functionallity.
I've found the following issues in my current testing:
1) The list of links to "JBoss Runtimes" is bad ui - fills up the screen with
alot of whitespace (and its Runtimes not runtime)
2) The import/export buttons does not seem to do anything beyound calling import/export
dialog.
3) Search has a cancel button but it doesn't do anything
4) Seam webapps seem to be picked up as seam runtimes - is that intended ?
5) Seam inside EAP is not detected
6) Drools inside SOA-P is not detected
7) The import/export of WTP servers seem to be a very bad hack...we probably have to live
with it but at least we should try and make our import/export simply wrap the relevant
runtimes
Furthermore these settings seem to not persist between workspaces and does not handle the
original usecase of having runtimes configured when starting up a new workspace (requiring
users to import/export is not the solution)
I'm creating a few subtasks for this to outline the ideas.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5008
days inactive
5080
days old
jbosstools-issues@lists.jboss.org
12 comments
3 participants
participants (3)
-
Dominik Pospisil (JIRA) -
Max Andersen (JIRA)
-
Snjezana Peco (JIRA)