July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3479) create just one marketplace entry for developer studio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3479?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3479: ----------------------------- Affects Version/s: 9.0.0.Beta1 > create just one marketplace entry for developer studio > ------------------------------------------------------ > > Key: JBDS-3479 > URL: https://issues.jboss.org/browse/JBDS-3479 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 9.0.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 9.0.0.Beta2 > > > As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace. > To avoid full states rename Red Hat JBoss Developer Studio (Kepler): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kep... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20185) create just one marketplace entry for jboss tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20185?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20185: ------------------------------- Affects Version/s: 4.3.0.Beta1 > create just one marketplace entry for jboss tools > ------------------------------------------------- > > Key: JBIDE-20185 > URL: https://issues.jboss.org/browse/JBIDE-20185 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Beta2 > > > As discussed on JBIDE-20024 it now makes sense to have just one jboss tools entry on markteplace. > To avoid full loss of stats the entry to rename is JBoss Tools (Luna): http://marketplace.eclipse.org/content/jboss-tools-luna/metrics since it has the highest count by far currently. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3479) create just one marketplace entry for developer studio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3479?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-3479: -------------------------------- Assignee: Nick Boldt > create just one marketplace entry for developer studio > ------------------------------------------------------ > > Key: JBDS-3479 > URL: https://issues.jboss.org/browse/JBDS-3479 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: marketplace > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 9.0.0.Beta2 > > > As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace. > To avoid full states rename Red Hat JBoss Developer Studio (Kepler): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kep... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3479) create just one marketplace entry for developer studio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3479?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3479: ----------------------------- Fix Version/s: 9.0.0.Beta2 > create just one marketplace entry for developer studio > ------------------------------------------------------ > > Key: JBDS-3479 > URL: https://issues.jboss.org/browse/JBDS-3479 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: marketplace > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 9.0.0.Beta2 > > > As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace. > To avoid full states rename Red Hat JBoss Developer Studio (Kepler): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kep... -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20134?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20134: ------------------------------- Affects Version/s: 4.3.0.Beta1 > 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: aerogear-hybrid > Affects Versions: 4.3.0.Beta1 > Environment: Win: 8.1 > JBoss Dev. Studio Version: 8.1.0.GA > Cordova: 4.1.2 > Reporter: Ramo Gündogdu > Assignee: Gorkem Ercan > Fix For: 4.3.x > > > 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] (JBIDE-20164) webtools server adapter installation UI is non-informative

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20164?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20164: ------------------------------------ {quote} "when using the nightly build updatesite everything works as expected" {quote} Yes, that's why I marked this JIRA *Resolved*. > webtools server adapter installation UI is non-informative > ---------------------------------------------------------- > > Key: JBIDE-20164 > URL: https://issues.jboss.org/browse/JBIDE-20164 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > Attachments: install-jbossas-connector-from-nightly.png, Install_New_Extension_and_New_Server.png > > > When using the "download additional adapters" for JBoss Tools it has a few issues. > a) shows "null" for vendor > b) does not actually say it is for WildFly nor EAP servers > c) (idea) should we add OpenShift to this ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20188) when invoking "Refresh" on a JMX node it causes the whole JMX tree to collapse

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20188?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20188: --------------------------------------------- is this a regression of https://issues.jboss.org/browse/JBIDE-18085 ? > when invoking "Refresh" on a JMX node it causes the whole JMX tree to collapse > ------------------------------------------------------------------------------ > > Key: JBIDE-20188 > URL: https://issues.jboss.org/browse/JBIDE-20188 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.3.0.Beta1, 4.3.x > Reporter: Lars Heinemann > Assignee: Rob Stryker > > When you expand an entry in the JMX Navigator into a deeper level ( for instance java.lang -> Compilation ) and then invoke the context menu "Refresh" on that node (Compilation) it collapses the whole tree and you loose your selection. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20188) when invoking "Refresh" on a JMX node it causes the whole JMX tree to collapse

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20188?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-20188: ---------------------------------------- same issue also occurs for fuse related entries in the jmx tree > when invoking "Refresh" on a JMX node it causes the whole JMX tree to collapse > ------------------------------------------------------------------------------ > > Key: JBIDE-20188 > URL: https://issues.jboss.org/browse/JBIDE-20188 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.3.0.Beta1, 4.3.x > Reporter: Lars Heinemann > Assignee: Rob Stryker > > When you expand an entry in the JMX Navigator into a deeper level ( for instance java.lang -> Compilation ) and then invoke the context menu "Refresh" on that node (Compilation) it collapses the whole tree and you loose your selection. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20188) when invoking "Refresh" on a JMX node it causes the whole JMX tree to collapse

by Lars Heinemann (JIRA)

Lars Heinemann created JBIDE-20188: -------------------------------------- Summary: when invoking "Refresh" on a JMX node it causes the whole JMX tree to collapse Key: JBIDE-20188 URL: https://issues.jboss.org/browse/JBIDE-20188 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: jmx Affects Versions: 4.3.0.Beta1, 4.3.x Reporter: Lars Heinemann Assignee: Rob Stryker When you expand an entry in the JMX Navigator into a deeper level ( for instance java.lang -> Compilation ) and then invoke the context menu "Refresh" on that node (Compilation) it collapses the whole tree and you loose your selection. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19990) "See JBoss Tools Visual Editor FAQ" link is not working.

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19990?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-19990: ------------------------------------------------ Vlado, please clarify what do you have in Web Browser preferences? > "See JBoss Tools Visual Editor FAQ" link is not working. > -------------------------------------------------------- > > Key: JBIDE-19990 > URL: https://issues.jboss.org/browse/JBIDE-19990 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, visual-page-editor-core > Affects Versions: 4.3.0.Beta1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.3.0.Beta2 > > > When the browser cannot be instantiated, error is shown and on the bottom of the editor is "See JBoss Tools Visual Editor FAQ" link (see here: http://i.imgur.com/F2l9Hgi.png). > This link is not working. Clicking on it just writes into console, from where JBDS/JBT was started, this: > _env: /home/rhopp/http:/tools.jboss.org/documentation/faq/visualeditor.html: Directory or file does not exist_ -- 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 July 2015