[JBoss JIRA] Created: (JBIDE-2899) Allow export of server definitions without resetting launch config
by Gabriele Garuglieri (JIRA)
Allow export of server definitions without resetting launch config
------------------------------------------------------------------
Key: JBIDE-2899
URL: https://jira.jboss.org/jira/browse/JBIDE-2899
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.0.0.alpha
Reporter: Gabriele Garuglieri
Priority: Minor
Currently we can export a JBoss Tools server definition using the default WTP server panel.
There right clicking on the server opens a context menu whose last item is "Properties".
Clicking it opens a panel where the "Switch Location" button cause the server definition to be exported from workspace metadata to "Servers" project.
The problem is that doing so resets the launch configuration to the default values loosing any customization the user could have done.
The "Switch Location" function for JBoss Tools server definition should not loose launch config customizations.
(This is not strictly related but while you are at it, in the "Export Launch Configurations" panel the "JBoss Application Server Startup Configurations" items are missing the icons).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (JBIDE-3897) Creation of core module
by Rob Stryker (JIRA)
Creation of core module
-----------------------
Key: JBIDE-3897
URL: https://jira.jboss.org/jira/browse/JBIDE-3897
Project: Tools (JBoss Tools)
Issue Type: Task
Components: core
Affects Versions: 3.0.0.GA, 3.0.1.GA
Reporter: Rob Stryker
Assignee: Nick Boldt
Fix For: 3.1.0
Time to recreate the core module. Tasks are as follows:
1) The module folder, with plugins / features / test category
2) an (empty) test plugin
3) an empty core plugin
4) an empty ui plugin
5) a feature
6) properly added into build
7) properly added to build download page
8) properly added to update site
The purpose of this module will be to hold common well-designed multi-functional classes that will be usable by others. This will help reduce dependencies between modules by providing a common base.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (JBDS-712) cannot edit or delete XPaths in JBoss Server View after a rename (view does not refresh?)
by Nick Boldt (JIRA)
cannot edit or delete XPaths in JBoss Server View after a rename (view does not refresh?)
-----------------------------------------------------------------------------------------
Key: JBDS-712
URL: https://jira.jboss.org/jira/browse/JBDS-712
Project: Developer Studio
Issue Type: Bug
Components: servers
Affects Versions: 2.0.0.GA
Reporter: Nick Boldt
1. Open the JBoss Server View
2. Expand XML Configuration > Ports.
3. Right-click > New XPath
4. Enter a name "foo", a pattern "//server/mbean[@name='jboss:service=Naming']/attribute[@name='Port']"
5. Click preview - note there are 3 child nodes (if server is running; 2 if not).
6. Click OK
7. Expand new "foo" node; note the same three child nodes / files as seen in the preview
So far, so good. Now to break things...
8. Right-click the new "foo" XPath > Edit XPath. Rename the new XPath "foo2". View updates w/ new label
9. Right-click the new "foo2" XPath > Delete XPath. Nothing happens.
10. Right-click the new "foo2" XPath > Edit XPath. Change the pattern to "//attribute[@name='Port']"; preview and note that there are now nested nodes.
11. Click OK; view does not update w/ change.
12. If your server is not running, you can rename it back to "foo" and then delete it, but after renaming the pattern still won't refresh.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (JBIDE-4056) cooperation with mylyn?
by arne anka (JIRA)
cooperation with mylyn?
-----------------------
Key: JBIDE-4056
URL: https://jira.jboss.org/jira/browse/JBIDE-4056
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.0.0.GA
Reporter: arne anka
Priority: Minor
Attachments: jboss.png
i work on two projects alternately, one is a jboss seam project (say, A), one is totally unrelated (say, B).
both projects are, in eclipse terms, always open. i swotch between them by using mylyn and working sets.
the last week i worked on B and frequently experienced rather heavy resource usage because jboss tools did some operations, which were unnecessary because nothing changed in in A.
looking into the progress view there was an entry about building workspace, "invoking JProject ARchives Builder on A", "System: Jboss Tools Update" (see attached screenshot).
i don't know, if there's a more intelligent way, but maybe jboss tools could try to detect if the project is part of the mylyn task currently active and if not, stop any activity?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (JBIDE-3874) Maven integration
by Max Rydahl Andersen (JIRA)
Maven integration
-----------------
Key: JBIDE-3874
URL: https://jira.jboss.org/jira/browse/JBIDE-3874
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: common
Affects Versions: 3.0.0.GA
Reporter: Max Rydahl Andersen
Priority: Critical
Fix For: 3.1.0
It is time to make sure our stuff works well with Maven, at least to the extent that the underline runtimes support it.
First shot would be to add an adapter that allows m2eclipse controlled projects to activate the seam features.
That would allow us still to bundle JBoss Tools without any dependencies to m2eclipse which still seem to drag in non-compatible plugins which we need to look into before tying us to m2eclipse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months