[JBoss JIRA] (JBIDE-10327) Add org.jboss.tools.maven.jaxrs.feature to JBT Abridged category
by Fred Bricon (Created) (JIRA)
Add org.jboss.tools.maven.jaxrs.feature to JBT Abridged category
----------------------------------------------------------------
Key: JBIDE-10327
URL: https://issues.jboss.org/browse/JBIDE-10327
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng, maven
Affects Versions: 3.3.0.M5
Reporter: Fred Bricon
Assignee: Nick Boldt
Fix For: 3.3.0.M5
JAX-RS being a critical piece of the "JBoss Way", we're gonna need it being available from both the Abridged Category for the JBT update site and being installed by default with JBDS (see related JIRA)
Eventually, all this Maven related plugins should be available from the Abridged Category :
* org.jboss.tools.maven.feature
* org.jboss.tools.maven.jaxrs.feature
* org.jboss.tools.maven.cdi.feature
* org.jboss.tools.maven.hibernate.feature
* org.jboss.tools.maven.jsf.feature
* org.jboss.tools.maven.seam.feature
* org.jboss.tools.maven.portlet.feature
* org.jboss.tools.maven.project.examples.feature
The JBoss Maven category will contain all the above and org.jboss.tools.maven.jbosspackaging.feature
--
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
14 years, 4 months
[JBoss JIRA] Created: (JBDS-1509) JBDS thread looping after call to OS - Seen in DTP connection profile-setting
by Paul Nittel (JIRA)
JBDS thread looping after call to OS - Seen in DTP connection profile-setting
-----------------------------------------------------------------------------
Key: JBDS-1509
URL: https://issues.jboss.org/browse/JBDS-1509
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: integration
Affects Versions: 4.0.0.CR1
Environment: JBDS 4.0 H65 CR1, Fedora 12, Java SE Runtime Environment (build 1.6.0_21-b06)
Reporter: Paul Nittel
While testing Teiid Designer, I found the software wold go into a loop when I was interacting with the new connection profile process. The point at which the looping started was sonewhat variable, but seemed repeatable within the new CP set of dialogs. To simplify things, I started JBDS and went to the Database Development perspective (rather than Teiid Designer) and stepped through the new CP process. While completing the database connection information, the looping began. Here's part of the stack trace from running it in debug:
Thread [main] (Suspended)
OS.Call(int, int, int, int) line: not available [native method]
Display.sleep() line: 4021
WizardDialog(Window).runEventLoop(Shell) line: 826
WizardDialog(Window).open() line: 801
NewProfileAction(AddProfileViewAction).run() line: 246
NewProfileAction(Action).runWithEvent(Event) line: 498
ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584
ActionContributionItem.access$2(ActionContributionItem, Event, boolean) line: 501
ActionContributionItem$5.handleEvent(Event) line: 411
EventTable.sendEvent(Event) line: 84
MenuItem(Widget).sendEvent(Event) line: 1258
Display.runDeferredEvents() line: 3540
Display.readAndDispatch() line: 3161
Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2640
Workbench.runUI() line: 2604
Workbench.access$4(Workbench) line: 2438
Workbench$7.run() line: 671
Realm.runWithDefault(Realm, Runnable) line: 332
Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 664
PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
IDEApplication.start(IApplicationContext) line: 115
EclipseAppHandle.run(Object) line: 196
EclipseAppLauncher.runApplication(Object) line: 110
EclipseAppLauncher.start(Object) line: 79
EclipseStarter.run(Object) line: 369
EclipseStarter.run(String[], Runnable) line: 179
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 597
Main.invokeFramework(String[], URL[]) line: 619
Main.basicRun(String[]) line: 574
Main.run(String[]) line: 1407
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBDS-1600) Creating mysql data source creates wrong JAR reference
by Peter Larsen (JIRA)
Creating mysql data source creates wrong JAR reference
------------------------------------------------------
Key: JBDS-1600
URL: https://issues.jboss.org/browse/JBDS-1600
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Environment: RHEL6
Reporter: Peter Larsen
Fix For: 4.0.0.GA
When adding a driver, for instance mySQL, to JBDS, the dialog puts a wrong reference to the JAR file which needs to be corrected by the user.
If there's no automatic way to detect the location my the driver file, I suggest changing the dialog so the user is told to locate the file instead of hiding the option and having the user correct auto-generated material.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] (JBIDE-10314) Back out "Seam 2" changes, reverting to just "Seam"
by Daniel Azarov (Resolved) (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10314?page=com.atlassian.jira.plugi... ]
Daniel Azarov resolved JBIDE-10314.
-----------------------------------
Assignee: Alexey Kazakov (was: Daniel Azarov)
Resolution: Done
verified
> Back out "Seam 2" changes, reverting to just "Seam"
> ---------------------------------------------------
>
> Key: JBIDE-10314
> URL: https://issues.jboss.org/browse/JBIDE-10314
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: Seam 2
> Affects Versions: 3.3.0.M4
> Reporter: mark yarborough
> Assignee: Alexey Kazakov
> Fix For: 3.3.0.Beta1
>
>
> Multiple locations in the JBDS code that formerly referred to "Seam" now refer to "Seam 2". This was based on need to distinguish Seam 2 from Seam 3, which is no longer relevant. The code has already been changed to denote Seam 2, but this alters the screens and may necessitate re-shoot of many screenshots for the JBDS 5 documentation. So, a decision to be made... Which is easier and/or more appropriate? To back out the "Seam 2" code changes (and skip the need for new screenshots) or to leave the "Seam 2" label in the existing M4 code and re-shoot the screens for the docs? Personal opinion: If the need to distinguish Seam 2 from Seam 3 has gone away, then using "Seam 2" instead of "Seam" clutters things up...
--
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
14 years, 4 months
[JBoss JIRA] (JBDS-1892) Use "JBoss Tools Palette" as default palette instead of generic Eclipse palette
by Isaac Rooskov (Created) (JIRA)
Use "JBoss Tools Palette" as default palette instead of generic Eclipse palette
-------------------------------------------------------------------------------
Key: JBDS-1892
URL: https://issues.jboss.org/browse/JBDS-1892
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: integration
Affects Versions: 5.0.0.M3
Reporter: Isaac Rooskov
I have just downloaded and tried the latest 5.0.0.M4 nightly build and was confused as to why the Palette view on the right said "A palette is not available." when I expected a list of folders relating to JBoss components to appear. After a while I found that you have to specifically open the "JBoss Tools Palette" from Window -> Show View -> Other.
It would make sense to have the defauly palette that is opened to be the JBoss Tools Palette for JBDS 5; leaving it as the Eclipse default palette could cause customer/user confusion.
--
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
14 years, 4 months