March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16390) CordovaSim: need to implement multiple version support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16390?page=com.atlassian.jira.plugi... ] Ilya Buziuk edited comment on JBIDE-16390 at 3/3/14 4:15 AM: ------------------------------------------------------------- < Ilya Buziuk Just curious, have you checked the cordova device plug-in does it report the correct version? [~gercan], sure, it shows the right version was (Author: ibuziuk): < Ilya Buziuk Just curious, have you checked the cordova device plug-in does it report the correct version? [~gercan], sure > CordovaSim: need to implement multiple version support > ------------------------------------------------------ > > Key: JBIDE-16390 > URL: https://issues.jboss.org/browse/JBIDE-16390 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta1 > > Attachments: multiple-version-support.png > > > Cordovasim should get the version info from HMT (hybrid mobile tools) and handle it in an appropriate way > "Cordova Versioning Challenge" meeting minutes: http://rhatlog:festisub2010@people.redhat.com/~manderse/irc.devel.redhat.... -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16390) CordovaSim: need to implement multiple version support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16390?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-16390: ------------------------------------- < Ilya Buziuk Just curious, have you checked the cordova device plug-in does it report the correct version? [~gercan], sure > CordovaSim: need to implement multiple version support > ------------------------------------------------------ > > Key: JBIDE-16390 > URL: https://issues.jboss.org/browse/JBIDE-16390 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta1 > > Attachments: multiple-version-support.png > > > Cordovasim should get the version info from HMT (hybrid mobile tools) and handle it in an appropriate way > "Cordova Versioning Challenge" meeting minutes: http://rhatlog:festisub2010@people.redhat.com/~manderse/irc.devel.redhat.... -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2913) Console log when running EAP 6.2.x not formatted correctly

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ] Mustafa Musaji commented on JBDS-2913: -------------------------------------- I used eap 6.2.0+patch.zip but this happens when I use EAP 6.2.0 too. I don't have any logmanager VM arguments presents. > Console log when running EAP 6.2.x not formatted correctly > ---------------------------------------------------------- > > Key: JBDS-2913 > URL: https://issues.jboss.org/browse/JBDS-2913 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: server > Affects Versions: 7.1.0.GA > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Fix For: 7.1.1.CR1 > > Attachments: EAP-6.1.0.png, EAP-6.2.1.png > > > When running EAP from JBDS the console logging shows strange characters from the logging. See screen shots comparing EAP 6.1.0 to EAP 6.2.1 (this also happens on EAP 6.2.0) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2940) Verify mockito/1.9.5 with JBDS 8.0

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2940?page=com.atlassian.jira.plugin.... ] Vlado Pakan updated JBDS-2940: ------------------------------ Assignee: Radim Hopp (was: Vlado Pakan) > Verify mockito/1.9.5 with JBDS 8.0 > ---------------------------------- > > Key: JBDS-2940 > URL: https://issues.jboss.org/browse/JBDS-2940 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Radim Hopp > Fix For: 8.0.0.Alpha2 > > > See: https://issues.jboss.org/browse/JBIDE-12971 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16588) Remote EAP 6.2 fails to stop

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16588?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-16588: ----------------------------------- Assignee: Martin Malina (was: Rob Stryker) Give this a try for me, see if it works. Thanks. > Remote EAP 6.2 fails to stop > ---------------------------- > > Key: JBIDE-16588 > URL: https://issues.jboss.org/browse/JBIDE-16588 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2a B70 > EAP 6.2.0.GA > Reporter: Martin Malina > Assignee: Martin Malina > Priority: Critical > Fix For: 4.2.0.Beta1 > > Attachments: remote-server-stop-error.png > > > When I create a remote EAP 6.2 server (ssh connection) without using the management port, the server starts and deploys ok, but when I try to stop it, I get this error: > {code} > !ENTRY org.eclipse.wst.server.core 4 0 2014-02-14 16:44:14.239 > !MESSAGE Server JBoss EAP 6.2 Server marvin failed to stop. > {code} > Very informative ;) > !remote-server-stop-error.png! > The server remains "Started" and the java process on the remote machine is still running. If I try it again and again, the result is the same. So the only way of stopping the server is killing the java process on the remote machine. But Eclipse will still show Started, so need a restart. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15162) User must install and reference an installed local EAP instance to create a remote server definition

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15162?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-15162: ----------------------------------- Assignee: Martin Malina (was: Rob Stryker) Martin: Another patch was committed (commit id 02f3cfb) to fix this error. Please give it another try. Thanks. > User must install and reference an installed local EAP instance to create a remote server definition > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-15162 > URL: https://issues.jboss.org/browse/JBIDE-15162 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.2.0.Beta1 > > Attachments: Van_1.png, Van_2.png, Van_3.png > > > See the attached screenshots - it seems counter-intuitive for a user to have to reference an installed local EAP instance to too create a remote server definition > - open the "Servers" tab (where servers are stopped/started) > - click in the area > - now right mouse click and select "New->Server" > - select JBoss Middleware EAP 6.1, click next > - this next panel requires you to enter a directory to a local EAP install -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16659) Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16659?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-16659: ------------------------------------ Affects: Documentation (Ref Guide, User Guide, etc.) > Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure > -------------------------------------------------------------------------------------- > > Key: JBIDE-16659 > URL: https://issues.jboss.org/browse/JBIDE-16659 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid > Affects Versions: 4.1.1.Final > Reporter: Vineet Reynolds > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Currently the Hybrid Mobile project structure is very nearly similar to the project structure created by the Cordova CLI. It simply lacks the {{platforms}} and {{merges}} sub-directories. > When attempting to use the Cordova CLI, the {{platforms}} directory needs to be created at the very least, followed by execution of the {{cordova platform add android}} or {{cordova platform add ios}} CLI commands. This eventually sets up the native SDK projects that can be built with ADT or XCode. > We should attempt to create a {{platforms}} sub-dir so that the hybrid mobile project is compatible with Cordova CLI. Additionally, if possible (due to the presence of a nested ADT sub-project), we should try and use the {{platforms}} directory as the default export location of the created native projects. This would ensure that exporting of the project in Eclipse is more or less equivalent to the {{cordova platform add android}} + {{cordova prepare android}} or {{cordova platform add ios}} + {{cordova prepare ios}} group of commands that create the native SDK projects and update their contents. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16661) Eclipse Console Logging for CordovaSim

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16661?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-16661: ------------------------------------ Affects: Documentation (Ref Guide, User Guide, etc.) > Eclipse Console Logging for CordovaSim > -------------------------------------- > > Key: JBIDE-16661 > URL: https://issues.jboss.org/browse/JBIDE-16661 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.Beta1 > > Attachments: Screenshot 2014-02-27 16.23.47.png > > > If I understand everything correct from email thread [~maxandersen] wants to have something like in attached screenshot(standart console where error log and terminate button presents) for BrowserSim and CordovaSim launching. > My point that it could be done for CordovaSim because it's a launch tool, but not for BrowserSim because it's "just a browser". -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2949) Require Java 7 for the IDE

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2949?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2949: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > Require Java 7 for the IDE > -------------------------- > > Key: JBDS-2949 > URL: https://issues.jboss.org/browse/JBDS-2949 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > > Run the IDE with Java 7 (Java 6 no longer supported) (Users applications and servers can still use older and newer JDK’s like Java 1.4,5,6, 8 etc.) P1 > Java 6 is no longer supported by Oracle and by requiring Java 7 we can use better native IO and JavaFX (only on oracle) > Forge already requires Java 7. > Concerns: If we do not run with Java 6 we cannot support Xulrunner based VPE on OSX. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16467) Streamline server groups in New Server dialog

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16467?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-16467: --------------------------------------- bugzilla for removing generic jboss from server tools is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=427598 > Streamline server groups in New Server dialog > --------------------------------------------- > > Key: JBIDE-16467 > URL: https://issues.jboss.org/browse/JBIDE-16467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > > Today I noticed that the group for JBoss EAP servers is now called Red Hat JBoss Middleware (JBIDE-15269). Seeing it got me thinking that the way it is now is actually pretty confusing and looks like a mess. Let me explain. > When you have JBoss Tools installed today, you get 3 JBoss-related groups in the New Server dialog. > 1. JBoss - this is in Eclipse by default. It contains very old servers only - up to JBoss AS 5. Could we possibly lobby for getting this removed/replaced with our own adapters? > 2. JBoss Community - this is where all our JBoss AS and Wildfly adapters are. > 3. Red Hat JBoss Middleware - this contains all EAP servers. > When you try to look at it from a new user's perspective, somebody who doesn't work at RH, it can give the impression that probably nobody took the time to put some order to this - there are 3 different groups, not even next to one another (because it's sorted alphabetically of course). > Granted, the Eclipse's JBoss group is not in our control, but maybe we can try to do something there, too? > I'm not sure what's the solution here. But if we must use Red Hat JBoss Middleware, couldn't we put everything in this group? Or are there any other alternatives to the current state? Or is it just me who finds this confusing? Opinions welcome. -- 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, 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 2014