[JBoss JIRA] (JBIDE-13687) Project wizard from central: requirements should be recommendations
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13687?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-13687:
-------------------------------------
For JBDS 7.1.1/JBT4.12?
> Project wizard from central: requirements should be recommendations
> -------------------------------------------------------------------
>
> Key: JBIDE-13687
> URL: https://issues.jboss.org/browse/JBIDE-13687
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.1.x
>
> Attachments: no-server.png
>
>
> In the new project wizard in Central, there is the table with required plugins and runtimes. In fact these are recommendations - even if you don't have the required server, the project can be created and if you have a compatible server, you can deploy the project to it.
> So the table's title should be changed to Recommendations.
--
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, 3 months
[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project with Seam 2.3.Final
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-14629:
-------------------------------------
I think this should be addressed in JBDS7.1.1/JBT4.12
> 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: Viacheslav Kabanovich
> Priority: Critical
> 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, 3 months
[JBoss JIRA] (JBIDE-15107) JBoss EAP 6.1 Server cannot be started with 32-bit JVM on Windows 7
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15107?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-15107:
-------------------------------------
[~maxandersen]is this still a real problem? Seems critical to fix if it is
> 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
> 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, 3 months
[JBoss JIRA] (JBIDE-15934) Run on Android Device does not work on OS X
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15934?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-15934:
--------------------------------
Priority: Critical (was: Major)
> 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
> 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, 3 months
[JBoss JIRA] (JBIDE-15934) Run on Android Device does not work on OS X
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15934?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-15934:
-------------------------------------
critical for JBDS 7.1.1/JBT 4.1.2
> 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
> 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, 3 months