March 2014 - jbosstools-issues - Jboss List Archives

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-2913: ----------------------------------- I've just tested again using a patch build as follows: {code} [rob@rawbdor eap621test]$ ls jboss-eap-6.2.0.zip jboss-eap-6.2.1.zip [rob@rawbdor eap621test]$ unzip jboss-eap-6.2.0.zip (trimmed for brevity) [rob@rawbdor eap621test]$ cd jboss-eap-6.2/bin/ [rob@rawbdor eap621test]$ ./jboss-cli.sh [disconnected /] patch apply /home/rob/apps/jboss/zipped/eap621test/jboss-eap-6.2.1.zip { "outcome" : "success", "result" : {} } [disconnected /] exit {code} I then made a server adapter for eap-6.1+ server type in eclipse and verified the launch args included the no-color flags. Everything works as expected. Can you verify for me your operating system and any other details that may help? > 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-2913) Console log when running EAP 6.2.x not formatted correctly

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-2913: ----------------------------------- When using jboss-eap-6.2.1-full-build.zip I am unable to replicate. I will see the results on the other patch zips, but I'm not quite sure how to ensure they are installed. > 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-2848) Usage Stats for actual used features

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2848: ------------------------------- Labels: (was: QE_JBDS80_needinfo) > Usage Stats for actual used features > ------------------------------------ > > Key: JBDS-2848 > URL: https://issues.jboss.org/browse/JBDS-2848 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements, usage > Reporter: Burr Sutter > Assignee: Alexey Kazakov > Priority: Critical > > We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage". > Areas worth tracking include (in priority order): > - Use of the OpenShift Wizard to successful completion vs error > - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8) > - Successful installation of the features found on Software/Update tab of JBoss Central > - Use of the JSF/RichFaces Visual Page Editor > - Use of the Hibernate Tooling > - Use of the jQuery Mobile Palette > - Use of BrowserSim > - Use of CordovaSim > We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/ > Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool) > Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future. -- 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-16681) For JBIDE 4.1.2.CR1: Prepare for CR1 release [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16681?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16681: ------------------------------------- I've committed the pom change and built. THere is still one jira open for the release, though I doubt I can discover the cause in time. I'll investigate it now. > For JBIDE 4.1.2.CR1: Prepare for CR1 release [Server] > ----------------------------------------------------- > > Key: JBIDE-16681 > URL: https://issues.jboss.org/browse/JBIDE-16681 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.1.2.CR1 > > > For JBIDE 4.1.2.CR1 [Server]: Please perform the following tasks: > 0. If nothing has changed in your component since JBT 4.1.1.Final or JBDS 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise, for all other projects: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.2.CR1 or 7.1.1.CR1 > [Unresolved JIRAs with fixVersion = 4.1.2.CR1, 4.1.2.Final, 7.1.1.CR1, 7.1.1.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.2.Final-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.30.6.Final > mvn clean verify -Dtpc.version=4.32.0.Final > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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-16681) For JBIDE 4.1.2.CR1: Prepare for CR1 release [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16681?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-16681: ----------------------------------- Assignee: Rob Stryker > For JBIDE 4.1.2.CR1: Prepare for CR1 release [Server] > ----------------------------------------------------- > > Key: JBIDE-16681 > URL: https://issues.jboss.org/browse/JBIDE-16681 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.1.2.CR1 > > > For JBIDE 4.1.2.CR1 [Server]: Please perform the following tasks: > 0. If nothing has changed in your component since JBT 4.1.1.Final or JBDS 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise, for all other projects: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.2.CR1 or 7.1.1.CR1 > [Unresolved JIRAs with fixVersion = 4.1.2.CR1, 4.1.2.Final, 7.1.1.CR1, 7.1.1.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.2.Final-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.30.6.Final > mvn clean verify -Dtpc.version=4.32.0.Final > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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-15548) Use JUnit @Rules instead of inheritance in test cases

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15548?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15548: ---------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.x) > Use JUnit @Rules instead of inheritance in test cases > ----------------------------------------------------- > > Key: JBIDE-15548 > URL: https://issues.jboss.org/browse/JBIDE-15548 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta1 > > -- 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 Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16659?page=com.atlassian.jira.plugi... ] Karel Piwko commented on JBIDE-16659: ------------------------------------- [~vineet.reynolds] I'm ok with an CLI alternative, given it would support major OS platforms (Linux, Mac OS X, Windows). > 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] (JBTIS-254) JBoss Developer Studio 7 fails in Camel Editor under "Properties" when click on "Documentation"

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBTIS-254?page=com.atlassian.jira.plugin.... ] Lars Heinemann reassigned JBTIS-254: ------------------------------------ Assignee: Lars Heinemann > JBoss Developer Studio 7 fails in Camel Editor under "Properties" when click on "Documentation" > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-254 > URL: https://issues.jboss.org/browse/JBTIS-254 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Fuse IDE > Environment: JBDS 7.1 and Integration Stack 7.0 > Reporter: Roger Hui > Assignee: Lars Heinemann > > Trying to use the Camel editor in JBoss Developer Studio 7 fails as soon as we try to access the "Documentation" tab in the "Properties" View. -- 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] (JBTIS-254) JBoss Developer Studio 7 fails in Camel Editor under "Properties" when click on "Documentation"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-254?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-254: ------------------------------------------- [~lhein] for you. Can you verify if you are force/requiring webkit in Fuse ? [~roger.hui] webkit mode on eclipse only require Safari if you are running on Windows - on fedora it should use the webkit bundled with the OS, but I know that can give problems on Fedora 20. Does it fail on Fedora 19 too ? > JBoss Developer Studio 7 fails in Camel Editor under "Properties" when click on "Documentation" > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-254 > URL: https://issues.jboss.org/browse/JBTIS-254 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Fuse IDE > Environment: JBDS 7.1 and Integration Stack 7.0 > Reporter: Roger Hui > > Trying to use the Camel editor in JBoss Developer Studio 7 fails as soon as we try to access the "Documentation" tab in the "Properties" View. -- 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-2953) JBoss Developer Studio 7 fails in Camel Editor under "Properties" when click on "Documentation"

by Roger Hui (JIRA)

Roger Hui created JBDS-2953: ------------------------------- Summary: JBoss Developer Studio 7 fails in Camel Editor under "Properties" when click on "Documentation" Key: JBDS-2953 URL: https://issues.jboss.org/browse/JBDS-2953 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: integration Affects Versions: 7.1.0.GA Environment: JBDS 7.1 and Integration Stack 7.0 Reporter: Roger Hui Trying to use the Camel editor in JBoss Developer Studio 7 fails as soon as we try to access the "Documentation" tab in the "Properties" View. -- 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