January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2669: ------------------------------------------- +1 for com.jboss.devstudio if really necessary. But does one of you have a feature branch to show the above changes since I honestly is loosing track of the suggested result ;) > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14002) Application wizard: wizard fields are blank when use 'Back' button

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14002?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14002: ------------------------------------- Assignee: Andre Dietisheim > Application wizard: wizard fields are blank when use 'Back' button > ------------------------------------------------------------------ > > Key: JBIDE-14002 > URL: https://issues.jboss.org/browse/JBIDE-14002 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Labels: application_wizard > Fix For: 4.2.0.Alpha2 > > > 1. Start the 'New OpenShift Application' wizard. > 2. Complete the 'Name', 'Type', 'Gear Profile' fields. > 3. Click Next. > 4. Decide you want to add a gear so click Back. > All of the information you had entered is gone and you have to input it again. :( -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14002) Application wizard: wizard fields are blank when use 'Back' button

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14002?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14002: ------------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.x) > Application wizard: wizard fields are blank when use 'Back' button > ------------------------------------------------------------------ > > Key: JBIDE-14002 > URL: https://issues.jboss.org/browse/JBIDE-14002 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Labels: application_wizard > Fix For: 4.2.0.Alpha2 > > > 1. Start the 'New OpenShift Application' wizard. > 2. Complete the 'Name', 'Type', 'Gear Profile' fields. > 3. Click Next. > 4. Decide you want to add a gear so click Back. > All of the information you had entered is gone and you have to input it again. :( -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project with Seam 2.3.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14629: ------------------------------- Labels: jbds711 (was: ) > Errors when creating and deploying seam2 project with Seam 2.3.Final > --------------------------------------------------------------------- > > Key: JBIDE-14629 > URL: https://issues.jboss.org/browse/JBIDE-14629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.1.0.Beta1 > Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206 with bundled JBoss EAP 6.1.0.Beta1 > Reporter: Vlado Pakan > Assignee: Rob Stryker > Priority: Critical > Labels: jbds711 > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > Attachments: seamerror.png > > > ERROR: DefaultDS Database connection is defined with incorrect link to hsqldb.jar file with JDBC driver for HSQLDB. > 1. Fix DefaultDS Database connection definition > ASSERT: It's possible to connect to DefaultDS > 2. Create new seam project with bundled JBoss EAP and JBoss Seam 2.3.Final > ERROR: There is error in Problems view: > !seamerror.png! > 3. Start seam project on server > ERROR: This error appear in Server log. Application is not deployed: > {noformat} > 3:58:45,950 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012: Deployment deployment "seam.war" contains CDI annotations but beans.xml was not found. > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam-ds.xml" (runtime-name : "seam-ds.xml") > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam.war" (runtime-name : "seam.war") > 13:58:46,431 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "hsqldb.jar" (runtime-name : "hsqldb.jar") > 13:58:46,436 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.jdbc-driver.hsqldb_jar (missing) dependents: [service jboss.data-source.java:/seamDatasource] > {noformat} > Is this supported scenario? -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2370) Could not create new projects through JBoss Central in JBDS 5

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2370?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2370: ----------------------------- Labels: jbds711 (was: ) > Could not create new projects through JBoss Central in JBDS 5 > ------------------------------------------------------------- > > Key: JBDS-2370 > URL: https://issues.jboss.org/browse/JBDS-2370 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: upstream > Affects Versions: 5.0.0.GA > Environment: JDK 1.7 32-bit, Windows > Reporter: David Chia > Assignee: Snjezana Peco > Priority: Critical > Labels: jbds711 > Fix For: 7.1.x > > > After a successful install, I tried to create a "Java EE Web Project" and run into an error dialog "Failed to load Wizard - Wizard metadata could not be loaded". I've also tried all other projects and result in the same error. The only project I could create is the "Dynamic Web Project". Looking at the error log, there are a lot of these "Connection errors" like below. > !SESSION 2012-10-23 15:28:07.909 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.7.0_07 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US > Framework arguments: -product com.jboss.jbds.product.product > Command-line arguments: -os win32 -ws win32 -arch x86 -product com.jboss.jbds.product.product > !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.086 > !MESSAGE Permission denied: connect > !STACK 0 > java.net.SocketException: Permission denied: connect > at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) > at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) > at java.net.Socket.connect(Socket.java:579) > at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65) > at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) > at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) > at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) > at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576) > at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206) > at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.132 > !MESSAGE Permission denied: connect > !STACK 0 > java.net.SocketException: Permission denied: connect > at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) > at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) > at java.net.Socket.connect(Socket.java:579) > at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65) > at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) > at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) > at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) > at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576) > at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206) > at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15107) JBoss EAP 6.1 Server cannot be started with 32-bit JVM on Windows 7

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15107?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15107: ------------------------------- Labels: jbds711 (was: ) > JBoss EAP 6.1 Server cannot be started with 32-bit JVM on Windows 7 > ------------------------------------------------------------------- > > Key: JBIDE-15107 > URL: https://issues.jboss.org/browse/JBIDE-15107 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Beta2 > Environment: 64-bit Windows 7 > 32-bit JDK 7u25 > Reporter: Yahor Radtsevich > Priority: Critical > Labels: jbds711 > Fix For: 4.1.x > > Attachments: screenshot.png > > > I cannot run JBoss EAP 6.1 with its default launch configuration. > The default launch configuration has {{-Xms1303m}} and {{-Xmx1303m}} in its parameters, which is obviously the reason of this bug. > *Steps to reproduce:* > # Install JBDS 7.0.0.Beta2 bundled with JBoss EAP 6.1 Server > # Open JBoss Central and create new HTML5 Project > # Try to run this project on the server > *Actual result:* > Server cannot be started. The following message is shown in the console: > {code:title=console output} > Error occurred during initialization of VM > Could not reserve enough space for object heap > {code} > And this pop-up appears: > !screenshot.png! -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15934) Run on Android Device does not work on OS X

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15934?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15934: ------------------------------- Labels: jbds711 (was: ) > Run on Android Device does not work on OS X > ------------------------------------------- > > Key: JBIDE-15934 > URL: https://issues.jboss.org/browse/JBIDE-15934 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Environment: OS X Mavericks > Latest Android SDK > JBDS 7.1.0.Beta1 > Nexus 7 > Reporter: Martin Malina > Assignee: Gorkem Ercan > Priority: Critical > Labels: jbds711 > Fix For: 4.1.2.Final > > > Following the instructions in JBIDE-15904 I am trying to run an app on an Android Device. > This fails for me - I get: No developer enabled android device is attached to this computer please attach your device and try again. (Punctuation is missing, btw.) > When I try to run adb devices, I can see the device is not there. Development mode is enabled on the device and it works for Vlado on Linux. > I found out that using Run on Android Device somehow breaks the connection with the device - before I run that, "adb devices" shows the device just fine. After I run that, the device is no longer displayed. > We even tried to deploy the app using adb install and it worked (while the device was still connected) -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2862) During install, I should be able to create a new directory to install into

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2862: ----------------------------- Labels: jbds711 (was: ) > During install, I should be able to create a new directory to install into > -------------------------------------------------------------------------- > > Key: JBDS-2862 > URL: https://issues.jboss.org/browse/JBDS-2862 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.CR1 > Environment: Mac OS X > Reporter: Jim Tyrrell > Assignee: Denis Golovin > Labels: jbds711 > Fix For: 7.1.1.GA, 8.0.0.Alpha2 > > Attachments: 2013-12-19_1512.png, Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png > > > See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install JBDS. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15932: ------------------------------- Labels: jbds711 (was: ) > CordovaSim needs to display console logs > ---------------------------------------- > > Key: JBIDE-15932 > URL: https://issues.jboss.org/browse/JBIDE-15932 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: jbds711 > Fix For: 4.2.0.Alpha2 > > > When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-226) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-226?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-226. ------------------------------ Fix Version/s: 4.1.3.Final 7.0.0.Final-JBDSIS Resolution: Done All component sub-tasks completed. > Please update target platform dependencies to .Final > ---------------------------------------------------- > > Key: JBTIS-226 > URL: https://issues.jboss.org/browse/JBTIS-226 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BPEL, drools/ jBPM, ESB, Fuse IDE, modeshape, switchyard, teiid > Affects Versions: 7.0.0.Final-JBDSIS > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.3.Final, 7.0.0.Final-JBDSIS > > > Please respin your component to include JBTIS TP 4.1.5.Final > On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... > These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: > 1. Know as early as possible if the .Final broke anyone > 2. Establish a stable TP for subsequent kepler releases > This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. > Thanks! -- 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

12 years, 2 months

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 January 2014