June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-644) JBDS 9: Request users to choose java 8 or higher when installing

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-644?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-644: ------------------------------------ Implemented as a prerequisite for all JBDS install topics: http://docbuilder.usersys.redhat.com/23020/ [~mmalina] Please review this as part of the Install Guide review. Thank you! > JBDS 9: Request users to choose java 8 or higher when installing > ---------------------------------------------------------------- > > Key: TOOLSDOC-644 > URL: https://issues.jboss.org/browse/TOOLSDOC-644 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Supriya Bharadwaj > Fix For: 4.3.0.Final > > > If we only support running the JBDS 9.0 IDE with Java 8, then the installer should request that users choose java 8 or higher when installing JBDS 9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-656) JBDS 9 Beta1: Test Install Guide

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-656?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-656: ------------------------------------ I've disabled the advanced options via script for now and just updated the four basic ways to install: http://docbuilder.usersys.redhat.com/23020/ [~mmalina] please have a look when you can. Thank you! > JBDS 9 Beta1: Test Install Guide > -------------------------------- > > Key: TOOLSDOC-656 > URL: https://issues.jboss.org/browse/TOOLSDOC-656 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > > Supriya needs to install JBDS 9 Beta 1 so she will test the install guide from 8.1 instructions against the new version as she does this. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-657) JBDS 9 Beta1 Release Notes Intro Content

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-657?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-657: ------------------------------------ Thanks, [~mmalina]. I've updated the Known Issues query and added one more customer case from the new query. Additionally, I don't have the text for docker, etc. yet so I've taken on Max's suggestion to add a link to the What's New Page, assuming this will be updated and we can update the page in the enterprise release notes after release. And yes, the text is indeed copied over from there. > JBDS 9 Beta1 Release Notes Intro Content > ---------------------------------------- > > Key: TOOLSDOC-657 > URL: https://issues.jboss.org/browse/TOOLSDOC-657 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Reporter: Misha Ali > Assignee: Misha Ali > > Hi Martin, > I haven't included the release note issues yet, but I wanted to get some review on the introductory text (i.e. everything but the known and resolved issue pages) here: > http://docbuilder.usersys.redhat.com/23108/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-657) JBDS 9 Beta1 Release Notes Intro Content

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-657?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-657: ---------------------------------------- [~mhusnain], your Known issues query doesn't seem right. You have this: {code} (project in (JBDS) AND affectedVersion >= "8.1.0.GA" AND affectedVersion <= 9.0.0.Beta2 AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "8.1.0.GA") OR project in (JBIDE) AND affectedVersion >= 4.3.0.Beta1 AND affectedVersion <= 4.3.0.Final AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > 4.2.3.Final)) AND type in (Bug) {code} It should be more like this: {code} (project in (JBDS) AND affectedVersion >= "8.1.0.GA" AND affectedVersion <= 9.0.0.Beta1 AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "9.0.0.Beta1") OR project in (JBIDE) AND affectedVersion >= 4.2.3.Final AND affectedVersion <= 4.3.0.Beta1 AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > 4.3.0.Beta1)) AND type in (Bug) {code} As for the New Features section, I did not read all the text carefully as I expect that this is copied from the N&N pages that were QE'd. But there is still nothing about Docker or the new Central. I guess you're still waiting for the N&N to copy from there? > JBDS 9 Beta1 Release Notes Intro Content > ---------------------------------------- > > Key: TOOLSDOC-657 > URL: https://issues.jboss.org/browse/TOOLSDOC-657 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Reporter: Misha Ali > Assignee: Misha Ali > > Hi Martin, > I haven't included the release note issues yet, but I wanted to get some review on the introductory text (i.e. everything but the known and resolved issue pages) here: > http://docbuilder.usersys.redhat.com/23108/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20134) Can't run default Ionic Project on device and on emulator

by Ramo Gündogdu (JIRA)

Ramo Gündogdu created JBIDE-20134: ------------------------------------- Summary: Can't run default Ionic Project on device and on emulator Key: JBIDE-20134 URL: https://issues.jboss.org/browse/JBIDE-20134 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: build Environment: Win: 8.1 JBoss Dev. Studio Version: 8.1.0.GA Cordova: 4.1.2 Reporter: Ramo Gündogdu I try to build my Ionic project with JBoss Developer Studio. But constantly I get the following problem. I can't build the project on the "Android device" and on the "Android emulator". Error: BUILD FAILED C:\Users\GSG-NB\AppData\Local\Android\sdk\tools\ant\build.xml:396: Problem: failed to create task or type checkenv Cause: The name is undefined. Action: Check the spelling. Action: Check that any custom tasks/types have been declared. Action: Check that any <presetdef>/<macrodef> declarations have taken place. Message: C:\Users\GSG-NB\AppData\Local\Android\android-sdk\tools\ant\build.xml:716: The following error occurred while executing this line: C:\Users\GSG-NB\AppData\Local\Android\android-sdk\tools\ant\build.xml:730: Compile failed; see the compiler error output for details. Excention Stack Trace: C:\Users\GSG-NB\AppData\Local\Android\android-sdk\tools\ant\build.xml:716: The following error occurred while executing this line: C:\Users\GSG-NB\AppData\Local\Android\android-sdk\tools\ant\build.xml:730: Compile failed; see the compiler error output for details. at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:568) at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:399) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.Project.executeTarget(Project.java:1364) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703) at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371) at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265) at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) at org.eclipse.thym.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97) at org.eclipse.thym.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58) at org.eclipse.thym.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53) at org.eclipse.thym.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:855) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: C:\Users\GSG-NB\AppData\Local\Android\android-sdk\tools\ant\build.xml:730: Compile failed; see the compiler error output for details. at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:1174) at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:930) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68) at com.android.ant.IfElseTask.execute(IfElseTask.java:120) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:396) ... 32 more Session Data: eclipse.buildId=unknown java.version=1.8.0_40 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE Framework arguments: -product com.jboss.devstudio.core.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product Code lines in C:\Users\GSG-NB\AppData\Local\Android\android-sdk\tools\ant\build.xml:716: und C:\Users\GSG-NB\AppData\Local\Android\android-sdk\tools\ant\build.xml:730: <do-only-if-manifest-hasCode elseText="hasCode = false. Skipping...">  <path id="project.javac.classpath"> <path refid="project.all.jars.path" /> <path refid="tested.project.classpath" /> <path path="${java.compiler.classpath}" /> </path> <javac encoding="${java.encoding}" source="${java.source}" target="${java.target}" debug="true" extdirs="" includeantruntime="false" destdir="${out.classes.absolute.dir}" bootclasspathref="project.target.class.path" verbose="${verbose}" classpathref="project.javac.classpath" fork="${need.javac.fork}"> Thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-657) JBDS 9 Beta1 Release Notes Intro Content

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-657?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-657: ------------------------------------ Hi [~mmalina], I've updated: * The What's New text. * The Known and Resolved issues with new queries and one customer issue. Could you have a look and give me your feedback please: http://docbuilder.usersys.redhat.com/23108/ > JBDS 9 Beta1 Release Notes Intro Content > ---------------------------------------- > > Key: TOOLSDOC-657 > URL: https://issues.jboss.org/browse/TOOLSDOC-657 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Reporter: Misha Ali > Assignee: Misha Ali > > Hi Martin, > I haven't included the release note issues yet, but I wanted to get some review on the introductory text (i.e. everything but the known and resolved issue pages) here: > http://docbuilder.usersys.redhat.com/23108/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3470) Toolbars + Icons unusable on high resolution screens

by Mustafa Musaji (JIRA)

Mustafa Musaji created JBDS-3470: ------------------------------------ Summary: Toolbars + Icons unusable on high resolution screens Key: JBDS-3470 URL: https://issues.jboss.org/browse/JBDS-3470 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: ui/branding Affects Versions: 9.0.0.Alpha2 Environment: Windows + UHD screens Reporter: Mustafa Musaji When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly. Upstream: https://bugs.eclipse.org/bugs/show_bug.cgi?id=382972 I'm raising this for QE to ensure we test this in the next release as it was fixed upstream. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20133) Test failure in ConnectionPersistencyTest.shouldNotLoadMalformedUrl

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-20133: ---------------------------------------- Summary: Test failure in ConnectionPersistencyTest.shouldNotLoadMalformedUrl Key: JBIDE-20133 URL: https://issues.jboss.org/browse/JBIDE-20133 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta2 Reporter: Andre Dietisheim Currently there is a test failure in {code} Tests in error: ConnectionPersistencyTest.shouldNotLoadMalformedUrl:101 » NullPointer Tests run: 121, Failures: 0, Errors: 1, Skipped: 0 {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20133) Test failure in ConnectionPersistencyTest.shouldNotLoadMalformedUrl

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20133?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20133: ------------------------------------- Fix Version/s: 4.3.0.Beta2 > Test failure in ConnectionPersistencyTest.shouldNotLoadMalformedUrl > ------------------------------------------------------------------- > > Key: JBIDE-20133 > URL: https://issues.jboss.org/browse/JBIDE-20133 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > > Currently there is a test failure in > {code} > Tests in error: > ConnectionPersistencyTest.shouldNotLoadMalformedUrl:101 » NullPointer > Tests run: 121, Failures: 0, Errors: 1, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20133) Test failure in ConnectionPersistencyTest.shouldNotLoadMalformedUrl

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20133?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20133: ---------------------------------------- Assignee: Andre Dietisheim > Test failure in ConnectionPersistencyTest.shouldNotLoadMalformedUrl > ------------------------------------------------------------------- > > Key: JBIDE-20133 > URL: https://issues.jboss.org/browse/JBIDE-20133 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > > Currently there is a test failure in > {code} > Tests in error: > ConnectionPersistencyTest.shouldNotLoadMalformedUrl:101 » NullPointer > Tests run: 121, Failures: 0, Errors: 1, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 June 2015