July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20187: --------------------------------------------- moved to JBIDE since not JBDS specific, made bug since not feature request and finally set component to central since that is what this relates to. > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Misha Ali > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > http://pastebin.test.redhat.com/294840 > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3480) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3480?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3480: ------------------------------------------- please try and avoid to use vpn only accessible links for stacktraces etc. uploaded copy to http://pastebin.com/3XKt9x5i > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3480 > URL: https://issues.jboss.org/browse/JBDS-3480 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Affects Versions: 9.0.0.Beta1 > Reporter: Misha Ali > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > http://pastebin.test.redhat.com/294840 > Please let me know if any further information is required for this bug. -- 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20185?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20185: ---------------------------------------- I took care of merging everything under a single entry, as planned a few days ago: https://marketplace.eclipse.org/content/jboss-tools-0 About the -0 suffix in URL, I opened a request to marketplace admins: https://bugs.eclipse.org/bugs/show_bug.cgi?id=471897 > 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 > 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] (JBIDE-20185) create just one marketplace entry for jboss tools

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20185?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-20185: -------------------------------------- Assignee: Mickael Istria > 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 > 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] (JBIDE-20134) Can't run default Ionic Project on device and on emulator

by Ramo Gündogdu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20134?page=com.atlassian.jira.plugi... ] Ramo Gündogdu commented on JBIDE-20134: --------------------------------------- Yes [~nickboldt], i tried. The same result. The app icons and splash screen are the problem i think. If I comment out the icons and splash screen, it is working. With icons and splash screens ionic compiles by CLI commands without any problems > 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 > 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20164?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20164: --------------------------------------------- Do I get this TL;DR right ? "when using the nightly build updatesite everything works as expected" (all the steps are great but not sure if you found the result to be correct or missing something ? it seems okey on first look at least) > 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] (TOOLSDOC-610) FeedHenry: Document how to change icon for mobile application

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-610?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-610: ------------------------------- Sprint: 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT (was: 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT) > FeedHenry: Document how to change icon for mobile application > ------------------------------------------------------------- > > Key: TOOLSDOC-610 > URL: https://issues.jboss.org/browse/TOOLSDOC-610 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Optional > Labels: cordova, feedhenry > Fix For: 4.3.0.Final > > > As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen. > Also part of a Did You Know? probably. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-595) Update Install doc when offline zip is finalized

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-595?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-595: ------------------------------- Sprint: 2015/S7 (30-Mar > 12-Apr), 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT (was: 2015/S7 (30-Mar > 12-Apr), 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT) > Update Install doc when offline zip is finalized > ------------------------------------------------ > > Key: TOOLSDOC-595 > URL: https://issues.jboss.org/browse/TOOLSDOC-595 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Installation Guide > Affects Versions: 4.2.0.Final, 4.2.1.Final, 4.2.2.Final, 4.2.3.Beta1 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.3.CR1 > > > See JBDS-3361. > Right now the 8.1 install doc states that you need 2 .zip files for installing JBDS BYOE when offline. This might be changed to 1 .zip or the 2 .zips might be downloadable from the same URL. This doc will need updating to reflect the outcome. > Also affects offline install of JBDS-IS in Eclipse - so that install doc needs updating to reflect the outcome. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-646) Add info about installing Android SDK in Create Mobile Hybrid

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-646?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-646: ------------------------------- Sprint: 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT (was: 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT) > Add info about installing Android SDK in Create Mobile Hybrid > -------------------------------------------------------------- > > Key: TOOLSDOC-646 > URL: https://issues.jboss.org/browse/TOOLSDOC-646 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: General documentation issues > Affects Versions: 4.2.3.Final > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Priority: Minor > Fix For: 4.2.3.Final > > > Add data about installing Android SDK as a pre-requisite in the article (https://access.redhat.com/articles/1295913) > Also, add steps to add another emulator/change skin of existing one. > Discuss with [~mhusnain] where exactly to add these in the doc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-658) JBDS-IS 8.0.2 Install Guide: Implement installation information

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-658?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-658: ------------------------------- Sprint: 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT (was: 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT) > JBDS-IS 8.0.2 Install Guide: Implement installation information > --------------------------------------------------------------- > > Key: TOOLSDOC-658 > URL: https://issues.jboss.org/browse/TOOLSDOC-658 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > > [1] - > > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > I really find these instructions waay to complicated and since > everything is on the same level they all look equally important. > They also don't actually use the fastest way for marketplace. > Here is what I would focus on: > 1. Install into existing Eclipse: > Use > http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-int... > Link to #2 about Early access > 2. Install into existing JBoss Developer Studio > Use JBoss Central > Explain additional features available under Early access > 3. Other > Install/uninstall additional features from JBoss Central > Install offline: the instructions should not be different for > eclipse or devstudio. > (section 9 could be here but I would just not worry about > documenting it) > That's it. > This makes it much less complicated IMO. > Can we make that happen ? > /max -- 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