March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13756) Maven GWT Configurator and Maven Packaging Configurator cannot be installed

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13756?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-13756: -------------------------------------- For alpha1 - after Nick sets it up - the URL for download will be: https://devstudio.jboss.com/updates/7.0-development/central/core > Maven GWT Configurator and Maven Packaging Configurator cannot be installed > --------------------------------------------------------------------------- > > Key: JBIDE-13756 > URL: https://issues.jboss.org/browse/JBIDE-13756 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > Attachments: maven-gwt.png, maven-gwt.png, maven-gwt2.png, maven-gwt2.png, maven-packaging.png, maven-packaging.png, maven-packaging2.png, maven-packaging2.png > > > how did I test: > Step 1 - create a devstudio-discovery.xml file, file contents are: > <directory> >  > <entry url="com.jboss.jbds.central.discovery_7.0.0.Alpha1-v20130306-0101-B124.jar" permitCategories="true"/> > </directory> > Step 2 - download Central discovery plugin jar > http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1c.c... > Step 3 - Edit plugin.xml in the Central discovery plugin jar > change siteUrl="https://devstudio.jboss.com/updates/7.0-development/central/core/"> > to siteUrl="http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1c.c..."> > Step 4 - make the devstudio-discovery.xml and jar file available via a www server (in this case in the top html dir for an httpd server) > Step 5 - Add this to jbdevstudio.ini, start JBDS > -Djboss.discovery.directory.url=http://localhost/devstudio-discovery.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2495) Cannot install 6.0.1 BYOE into Eclipse EE Indigo SR1 or SR2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2495?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2495. ---------------------------- Resolution: Rejected Rejected. JBDS 6 runs on Juno, not Indigo. https://community.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTec... > Cannot install 6.0.1 BYOE into Eclipse EE Indigo SR1 or SR2 > ----------------------------------------------------------- > > Key: JBDS-2495 > URL: https://issues.jboss.org/browse/JBDS-2495 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.1.GA > Environment: http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1.core/ > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > > Today I wanted to install JBDS BYOE into a clean Eclipse. > I first tried Eclipse EE Indigo SR2 and got an error of conflicting debug plugin (only one of two can be installed...). So I though it might be because the current CR1 build didn't use SR2 yet. So I tried with SR1 but got the same error (or looking the same): > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Developer Studio (Core Features) 6.0.1.GA-v20130304-0526-B338 (com.jboss.jbds.product.feature.feature.group 6.0.1.GA-v20130304-0526-B338) > Software currently installed: Eclipse IDE for Java EE Developers 1.4.1.20110909-1818 (epp.package.jee 1.4.1.20110909-1818) > Only one of the following can be installed at once: > Debug Core 3.7.0.v20110518 (org.eclipse.debug.core 3.7.0.v20110518) > Debug Core 3.7.100.v20120521-2012 (org.eclipse.debug.core 3.7.100.v20120521-2012) > Cannot satisfy dependency: > From: JBoss Developer Studio (Core Features) 6.0.1.GA-v20130304-0526-B338 (com.jboss.jbds.product.feature.feature.group 6.0.1.GA-v20130304-0526-B338) > To: org.jboss.ide.eclipse.as.feature.feature.group [2.4.1.Final-v20130302-0014-B66] > Cannot satisfy dependency: > From: Eclipse IDE for Java EE Developers 1.4.1.20110909-1818 (epp.package.jee 1.4.1.20110909-1818) > To: org.eclipse.epp.package.jee.feature.feature.group [1.4.1.20110909-1818] > Cannot satisfy dependency: > From: Java EE IDE Feature 1.4.1.20110909-1818 (org.eclipse.epp.package.jee.feature.feature.group 1.4.1.20110909-1818) > To: org.eclipse.platform.feature.group [3.7.1.r37x_v20110729-9gF7UHOxFtniV7mI3T556iZN9AU8bEZ1lHMcVK] > Cannot satisfy dependency: > From: Eclipse Platform 3.7.1.r37x_v20110729-9gF7UHOxFtniV7mI3T556iZN9AU8bEZ1lHMcVK (org.eclipse.platform.feature.group 3.7.1.r37x_v20110729-9gF7UHOxFtniV7mI3T556iZN9AU8bEZ1lHMcVK) > To: org.eclipse.debug.core [3.7.0.v20110518] > Cannot satisfy dependency: > From: JBossAS Tools 2.4.1.Final-v20130302-0014-B66 (org.jboss.ide.eclipse.as.feature.feature.group 2.4.1.Final-v20130302-0014-B66) > To: org.jboss.ide.eclipse.as.wtp.core 2.3.0 > Cannot satisfy dependency: > From: WTP Overrides Core 2.4.0.Final-v20121205-2029-B41 (org.jboss.ide.eclipse.as.wtp.core 2.4.0.Final-v20121205-2029-B41) > To: bundle org.eclipse.debug.core 3.7.100 > Cannot satisfy dependency: > From: WTP Overrides Core 2.4.1.Final-v20130302-0014-B66 (org.jboss.ide.eclipse.as.wtp.core 2.4.1.Final-v20130302-0014-B66) > To: bundle org.eclipse.debug.core 3.7.100 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2491) JBDS unity icon shows only one version when more than one version of JBDS is installed

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2491?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2491: ------------------------------------- No idea, but I guess it is related to launcher name. Thus it could be not fixable. Need to test it locally to see if there is any config option to distinguish different JBDS installations in unity. > JBDS unity icon shows only one version when more than one version of JBDS is installed > -------------------------------------------------------------------------------------- > > Key: JBDS-2491 > URL: https://issues.jboss.org/browse/JBDS-2491 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 7.0.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Denis Golovin > Priority: Minor > Fix For: 7.0.0.Alpha2 > > Attachments: Workspace 1_001.png > > > JBDS icon in unity panel says JBDS 6.0.0.CR1. It should be 7.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13201) BYOE - Marketplace Installation on Mac - fails to start JBoss EAP

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13201?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-13201: ------------------------------------- More details - the problem shows up for servers added manually (Servers tab, right-click, New Server). If the EAP 6.0 or 6.1 Alpha1 is copied into the runtimes directory, then it is "auto-detected" when a new workspace is created and that works great - the servers start/stop/debug/restart with no problem. Error log: org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:87) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:143) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:127) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:116) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:233) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:225) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) Caused by: java.lang.RuntimeException: Operation failed with status WAITING at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:216) at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:143) at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:71) ... 6 more --- eclipse.buildId=unknown java.version=1.6.0_41 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -product com.jboss.jbds.product.product -product com.jboss.jbds.product.product -product com.jboss.jbds.product.product -keyring /Users/burr/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.jbds.product.product -product com.jboss.jbds.product.product -data /Users/burr/gettingstarted/workspace_jbds7alpha1_with_EAP_4 -product com.jboss.jbds.product.product -keyring /Users/burr/.eclipse_keyring -consoleLog -showlocation > BYOE - Marketplace Installation on Mac - fails to start JBoss EAP > ----------------------------------------------------------------- > > Key: JBIDE-13201 > URL: https://issues.jboss.org/browse/JBIDE-13201 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Environment: Mac OSX Lion (10.7) > Eclipse Java EE IDE for Web Developers for Mac OS X 64bit > * Version: Juno Service Release 1 > * Build id: 20121004-1855 > * Oracle Java 1.7.0_04 > EAP 6.0.0 > * Oracle Java 1.7.0_04 > Reporter: Burr Sutter > Assignee: Denis Golovin > Labels: respin-a > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > Attachments: Configuration.txt, EAP6_FirstPage.png, EAP_Stack.txt, JBDS_Stack.txt, jbosstools-diagnostics-20121129152254.zip, Server_Starting.png > > > The IDE does not recognize that JBoss EAP 6.0.0 is started - it eventually times out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2491) JBDS unity icon shows only one version when more than one version of JBDS is installed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2491?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2491: ----------------------------- Summary: JBDS unity icon shows only one version when more than one version of JBDS is installed (was: JBDS unity icon shows wrong version when more than one version of JBDS is installed) > JBDS unity icon shows only one version when more than one version of JBDS is installed > -------------------------------------------------------------------------------------- > > Key: JBDS-2491 > URL: https://issues.jboss.org/browse/JBDS-2491 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 7.0.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Denis Golovin > Priority: Minor > Fix For: 7.0.0.Alpha2 > > Attachments: Workspace 1_001.png > > > JBDS icon in unity panel says JBDS 6.0.0.CR1. It should be 7.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2491) JBDS shows wrong version

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2491?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2491: ---------------------------------- [~dgolovin]: any idea how we can make the Unity entries unique across releases? Can't fix 5.0.2 but we might have time to fix 6.0.1 (and then a similar fix for 7.0). > JBDS shows wrong version > ------------------------ > > Key: JBDS-2491 > URL: https://issues.jboss.org/browse/JBDS-2491 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 7.0.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Denis Golovin > Priority: Minor > Fix For: 7.0.0.Alpha2 > > Attachments: Workspace 1_001.png > > > JBDS icon in unity panel says JBDS 6.0.0.CR1. It should be 7.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2491) JBDS unity icon shows wrong version when more than one version of JBDS is installed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2491?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2491: ----------------------------- Summary: JBDS unity icon shows wrong version when more than one version of JBDS is installed (was: JBDS shows wrong version) > JBDS unity icon shows wrong version when more than one version of JBDS is installed > ----------------------------------------------------------------------------------- > > Key: JBDS-2491 > URL: https://issues.jboss.org/browse/JBDS-2491 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 7.0.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Denis Golovin > Priority: Minor > Fix For: 7.0.0.Alpha2 > > Attachments: Workspace 1_001.png > > > JBDS icon in unity panel says JBDS 6.0.0.CR1. It should be 7.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13682) Investigate use of Atlassian 3.0.7 or 3.2 in JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13682: ------------------------------------ [~mickael_istria] said: {quote} Atlassian 3.2.0 mirror created: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/b6b52b... http://download.jboss.org/jbosstools/updates/requirements/atlassian/3.2.0... {quote} Note that this site is not yet on devstudio.jboss.com nor composited into the next version of the extras sites (JBT or JBDS). That should wait until this investigation is complete (as well as the addition of any new atlassian stuff to the TP). > Investigate use of Atlassian 3.0.7 or 3.2 in JBoss Central > ---------------------------------------------------------- > > Key: JBIDE-13682 > URL: https://issues.jboss.org/browse/JBIDE-13682 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Fix For: 4.1.0.Alpha2 > > > Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno. > There is also a 3.2 available: > https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo... > available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13682) Investigate use of Atlassian 3.2 in JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13682: ------------------------------- Summary: Investigate use of Atlassian 3.2 in JBoss Central (was: Investigate use of Atlassian 3.0.7 or 3.2 in JBoss Central) > Investigate use of Atlassian 3.2 in JBoss Central > ------------------------------------------------- > > Key: JBIDE-13682 > URL: https://issues.jboss.org/browse/JBIDE-13682 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Fix For: 4.1.0.Alpha2 > > > Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno. > There is also a 3.2 available: > https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo... > available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2469) Cannot install all extras from central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2469?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2469 at 3/8/13 1:11 PM: ---------------------------------------------------------- >From [~maxandersen] {quote} Fixed this, here is how to use it: blah (details hhere after fater {quote} -------- Now have a simpler approach to building/testing Central. *README* (re: building/testing): http://svn.jboss.org/repos/devstudio/trunk/product/discovery/README.md Jenkins job (currently just for trunk but can be cloned to work for 4.1.x/7.0.x stable branch too): https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Generated sites: http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/ http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/ Generated metadata: http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/compos... http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/composi... Generated directory.xml files: http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/jbossto... http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/devstu... To use with Eclipse or JBDS: {code} eclipse -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/jbosstools-directory.xml or jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/devstudio-directory.xml {code} Then, install JBoss Community Central feature from http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/ or Install JBoss Developer Studio (Core Features) feature from http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/ 4. Restart. Review Central's Software/Update tab. Choose connectors/feature groups to install. was (Author: nickboldt): OK, now have a simpler approach to building/testing Central. README (building/testing): http://svn.jboss.org/repos/devstudio/trunk/product/discovery/README.md Jenkins job (currently just for trunk but can be cloned to work for 4.1.x/7.0.x stable branch too): https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Generated sites: http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/ http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/ Generated metadata: http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/compos... http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/composi... Generated directory.xml files: http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/jbossto... http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/devstu... To use with Eclipse or JBDS: {code} eclipse -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/jbosstools-directory.xml or jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/devstudio-directory.xml {code} Then, install JBoss Community Central feature from http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/ or Install JBoss Developer Studio (Core Features) feature from http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/ 4. Restart. Review Central's Software/Update tab. Choose connectors/feature groups to install. > Cannot install all extras from central > -------------------------------------- > > Key: JBDS-2469 > URL: https://issues.jboss.org/browse/JBDS-2469 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.0.0.Alpha1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 7.0.0.Alpha2 > > Attachments: central-install.png, central-install2.png > > > devstudio-directory.xml is: > <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/"> > <entry url="plugins/com.jboss.jbds.central.discovery_7.0.0.Alpha1-v20130211-0546-B6.jar" permitCategories="true"/> > </directory> > I selected all components in the list and could not complete the install. Please see screenshots. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
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 March 2013