July 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8838) add source feature to JBT components; generate source plugins w/ Tycho

by Nick Boldt (JIRA)

add source feature to JBT components; generate source plugins w/ Tycho ---------------------------------------------------------------------- Key: JBIDE-8838 URL: https://issues.jboss.org/browse/JBIDE-8838 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.M2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M2 As per example done in https://bugs.eclipse.org/bugs/show_bug.cgi?id=344515 and http://wiki.eclipse.org/Minerva#Source, the rest of JBT needs source features/plugins. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

8
63
0 / 0

[JBoss JIRA] Created: (JBIDE-9309) Easily adding full JBoss AS source

by arjan tijms (JIRA)

Easily adding full JBoss AS source ---------------------------------- Key: JBIDE-9309 URL: https://issues.jboss.org/browse/JBIDE-9309 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: arjan tijms Assignee: Rob Stryker The JBoss AS server runtime from JBoss tools adds a library container to the classpath of an Eclipse project. This container provides a large amount of jar files that make up JBoss AS itself and the Java EE services it offers. Attaching the source code for this is notoriously difficult. Because it concerns a large amount of jar files, attaching source code for each jar is a rather tedious job. For JBoss AS 5, the fact that the location of jars in the source archive was completely different from the structure exposed in Eclipse or the binary build of JBoss AS, made it very hard to actually locate the correct source jar. Sometimes even names were different, making it even harder. For JBoss AS 6, the source archive does not even contain the source for the majority of the JBoss AS artifacts. Source for 'core functionality' (from the point of view of the Java EE developer), like Servlet and JSF is missing. The user has to hunt the Internet to find the correct source for the correct version that JBoss AS 6 uses. This makes an already tedious job even more tedious. I would like to request functionality where the user can point to a single _jboss-src.xyz_ file that contains all sources. JBoss tools should then automatically attach the right source from the archive to the right jar from the library container. Alternatively the user could point to a maven repository (but this should not make the Eclipse project dependent on maven). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

10
30
0 / 0

[JBoss JIRA] Created: (JBIDE-8208) Improve how annotation processors are setup/detected via maven/m2eclipse

by Max Rydahl Andersen (JIRA)

Improve how annotation processors are setup/detected via maven/m2eclipse ------------------------------------------------------------------------ Key: JBIDE-8208 URL: https://issues.jboss.org/browse/JBIDE-8208 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Fix For: 3.2.1 Any way m2eclipse can setup and detect annotation processors ? Why isn't annotation processor not enabled by default when generating the .settings files for it ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

9
26
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-189) modify ws user guide documents

by Feng Qian (JIRA)

modify ws user guide documents ------------------------------ Key: TOOLSDOC-189 URL: https://issues.jboss.org/browse/TOOLSDOC-189 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Feng Qian Assignee: Isaac Rooskov After fix the issue: JBIDE-8490,need to modify the ws docs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
14
0 / 0

[JBoss JIRA] Created: (JBDS-1379) JBDS 4 Beta 1 installer fails on Create Shortcuts (8 of 9)

by Burr Sutter (JIRA)

JBDS 4 Beta 1 installer fails on Create Shortcuts (8 of 9) ---------------------------------------------------------- Key: JBDS-1379 URL: https://jira.jboss.org/browse/JBDS-1379 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 4.0.0.Beta1 Environment: Win7 64-bit, Java 6 64-bit running the installer Reporter: Burr Sutter D:\Users\Burr\Downloads>java -jar jbdevstudio-win32-4.0.0.v201010160636R-H52-Bet a1.jar C:\Program Files\Java\jre6 calltarget: main: [echo] Run p2 metadata generator [p2] Generating metadata for D:\tools\jbdevstudio4_beta1_again\eclipse. [p2] Generation completed with success [0 seconds]. [delete] Deleting: C:\Users\Burr\AppData\Local\Temp\artifacts.jar [delete] Deleting: C:\Users\Burr\AppData\Local\Temp\content.jar [delete] Deleting directory C:\Users\Burr\AppData\Local\Temp\binary could not create shortcut instance java.lang.Exception: error loading library java.lang.Exception: can't locate library at com.izforge.izpack.util.Librarian.loadArchSpecificLibrary(Unknown Sou rce) at com.izforge.izpack.util.Librarian.loadLibrary(Unknown Source) at com.izforge.izpack.util.os.ShellLink.initialize(Unknown Source) at com.izforge.izpack.util.os.ShellLink.<init>(Unknown Source) at com.izforge.izpack.util.os.Win_Shortcut.initialize(Unknown Source) at com.izforge.izpack.panels.ShortcutPanel.panelActivate(Unknown Source) at com.izforge.izpack.installer.InstallerFrame.switchPanel(Unknown Sourc e) at com.izforge.izpack.installer.InstallerFrame.navigateNext(Unknown Sour ce) at com.izforge.izpack.installer.InstallerFrame.skipPanel(Unknown Source) at com.jboss.jbds.installer.CreateLinkPanel.panelActivate(CreateLinkPane l.java:61) at com.izforge.izpack.installer.InstallerFrame.switchPanel(Unknown Sourc e) at com.izforge.izpack.installer.InstallerFrame.navigateNext(Unknown Sour ce) at com.izforge.izpack.installer.InstallerFrame.navigateNext(Unknown Sour ce) at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP erformed(Unknown Source) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour ce) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) java.lang.NullPointerException at com.izforge.izpack.util.os.Win_Shortcut.getProgramsFolder(Unknown Sou rce) at com.izforge.izpack.panels.ShortcutPanel.getProgramsFolder(Unknown Sou rce) at com.izforge.izpack.panels.ShortcutPanel.panelActivate(Unknown Source) at com.izforge.izpack.installer.InstallerFrame.switchPanel(Unknown Sourc e) at com.izforge.izpack.installer.InstallerFrame.navigateNext(Unknown Sour ce) at com.izforge.izpack.installer.InstallerFrame.skipPanel(Unknown Source) at com.jboss.jbds.installer.CreateLinkPanel.panelActivate(CreateLinkPane l.java:61) at com.izforge.izpack.installer.InstallerFrame.switchPanel(Unknown Sourc e) at com.izforge.izpack.installer.InstallerFrame.navigateNext(Unknown Sour ce) at com.izforge.izpack.installer.InstallerFrame.navigateNext(Unknown Sour ce) at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP erformed(Unknown Source) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour ce) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) D:\Users\Burr\Downloads>java -version java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) -- 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

13 years, 11 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-4926) Provide Integration plugin to allow monitoring of Hibernate Preformance through JMX using JMX Plugin

by Denis Golovin (JIRA)

Provide Integration plugin to allow monitoring of Hibernate Preformance through JMX using JMX Plugin ---------------------------------------------------------------------------------------------------- Key: JBIDE-4926 URL: https://jira.jboss.org/jira/browse/JBIDE-4926 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate, jmx Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Integration plug-in should provide a way to start monitoring hibernate project performance. It can be a wizard that ask what metrics should be monitored and then show it in graphic. -- 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

13 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBDS-1771) JBDS50_0450: [COMMIT] (PM) Document Bit Delivery Channels

by mark yarborough (JIRA)

JBDS50_0450: [COMMIT] (PM) Document Bit Delivery Channels --------------------------------------------------------- Key: JBDS-1771 URL: https://issues.jboss.org/browse/JBDS-1771 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-9257) Runtime detectors for SOA are missing in updatesite

by Libor Zoubek (JIRA)

Runtime detectors for SOA are missing in updatesite --------------------------------------------------- Key: JBIDE-9257 URL: https://issues.jboss.org/browse/JBIDE-9257 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite, drools, jbpm Affects Versions: 3.3.0.M2 Reporter: Libor Zoubek Assignee: Douglas Palmer Priority: Critical Fix For: 3.3.0.M3 I just installed http://download.jboss.org/jbosstools/builds/development/3.3.0.M2.soa-tool... (H6) on top of indigo with http://download.jboss.org/jbosstools/builds/development/3.3.0.M2/ (H6), Detection of runtimes does not work, for SOA technologies like drools, jBPM (and others?) AFAIK this functionality is provided by several plugins (1 per technology) which are missing. Without these plugins SOA-P builds are not fully recognized by Runtime Detection Preference page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
7
0 / 0

[JBoss JIRA] Created: (JBDS-1620) CLONE - Enable dropin folder reconciling by default for JBDS product

by Denis Golovin (JIRA)

CLONE - Enable dropin folder reconciling by default for JBDS product -------------------------------------------------------------------- Key: JBDS-1620 URL: https://issues.jboss.org/browse/JBDS-1620 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Build Affects Versions: 4.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 4.1.0.GA Now to get that supported several additions steps should be done: To activate dropins reconciling you need to do the following: - open studio/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info - find the line org.eclipse.equinox.p2.reconciler.dropins,1.1.0.v20100525,plugins/org.eclipse.equinox.p2.reconciler.dropins_1.1.0.v20100525.jar,4,false and change it to org.eclipse.equinox.p2.reconciler.dropins,1.1.0.v20100525,plugins/org.eclipse.equinox.p2.reconciler.dropins_1.1.0.v20100525.jar,4,true - create the studio/dropins directory and add plugins as is usual - start JBDS with the -clean option at least once To eliminate this steps plugin org.eclipse.equinox.p2.reconciler.dropins should be marked as auto started in jbds-all.product definition which is used to build JBDS product -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-8700) Add Configure>Detect Project Configuration menu to runtime plugin

by Snjezana Peco (JIRA)

Add Configure>Detect Project Configuration menu to runtime plugin ----------------------------------------------------------------- Key: JBIDE-8700 URL: https://issues.jboss.org/browse/JBIDE-8700 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtimes Affects Versions: 3.2.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.M1 The action would detect different project configurations. For the first time, it would detect CDI based on the existence of cdi-api in the project's classpath. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2011