November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15860) Show a warning when enterprise maven repo is missing for enterprise quickstarts

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15860?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15860: -------------------------------- Description: Since the newest quickstarts now require the maven eap and/or wfk repos, generated projects won't build OOTB if these repos are not defined in the user's settings.xml. Maven archetype based wizards show a warning if essential dependencies can't be resolved. We need to add the same thing for zipped quickstarts. was: Since the newest quickstarts now require the maven eap and/or wfk repos, generated projects won't build OOTB if these repos are not defined in the user's settings.xml. Maven archetype based wizards show a warning is essential dependencies can't be resolved. We need to add the same thing for zipped quickstarts. > Show a warning when enterprise maven repo is missing for enterprise quickstarts > ------------------------------------------------------------------------------- > > Key: JBIDE-15860 > URL: https://issues.jboss.org/browse/JBIDE-15860 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Affects Versions: 4.1.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.1.CR1 > > > Since the newest quickstarts now require the maven eap and/or wfk repos, generated projects won't build OOTB if these repos are not defined in the user's settings.xml. > Maven archetype based wizards show a warning if essential dependencies can't be resolved. We need to add the same thing for zipped quickstarts. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15896) RuntimeWorkbenchUtils.refreshServersView() throws exception sometimes when running tycho tests

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15896?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15896: ---------------------------------- Description: The issue can happen in a component that requires the runtime component. See build #307 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-portlet_m... {code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.19.0:test (default-test) on project org.jboss.tools.portlet.core.test: An unexpected error occured (return code 13). See log for details. -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.19.0:test (default-test) on project org.jboss.tools.portlet.core.test: An unexpected error occured (return code 13). See log for details. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoFailureException: An unexpected error occured (return code 13). See log for details. at org.eclipse.tycho.surefire.TestMojo.runTest(TestMojo.java:970) at org.eclipse.tycho.surefire.TestMojo.execute(TestMojo.java:668) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more {code} was: The issue can happen in a component that requires the runtime component. See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-portlet_m... > RuntimeWorkbenchUtils.refreshServersView() throws exception sometimes when running tycho tests > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-15896 > URL: https://issues.jboss.org/browse/JBIDE-15896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.1.x > Reporter: Snjezana Peco > Assignee: Rob Stryker > > The issue can happen in a component that requires the runtime component. > See build #307 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-portlet_m... > {code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.19.0:test (default-test) on project org.jboss.tools.portlet.core.test: An unexpected error occured (return code 13). See log for details. -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.19.0:test (default-test) on project org.jboss.tools.portlet.core.test: An unexpected error occured (return code 13). See log for details. > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoFailureException: An unexpected error occured (return code 13). See log for details. > at org.eclipse.tycho.surefire.TestMojo.runTest(TestMojo.java:970) > at org.eclipse.tycho.surefire.TestMojo.execute(TestMojo.java:668) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > {code} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12646) web.xml servlet-name validation is not case-sensitive

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12646?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-12646: ----------------------------------------------- [~xcoulon], good news, it is supposed to fail on a case insensitive OS. > web.xml servlet-name validation is not case-sensitive > ----------------------------------------------------- > > Key: JBIDE-12646 > URL: https://issues.jboss.org/browse/JBIDE-12646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.0.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha1 > > Attachments: JBIDE-12646 - Wi-Fi.m4v, ServletNameValidation.png > > > [Using the HTML5 sample project generated from Central] > I'm adding a servlet declaration in the web.xml file but the web.xml editor does not report a warning when the servlet name case is wrong: > {code} > <servlet-mapping> > <servlet-name>org.jboss.tools.example.html5.rest.JaxrsActivator</servlet-name> > <url-pattern>/hello/*</url-pattern> > </servlet-mapping> > {code} > In the example above, the class name should be JaxRsActivator, not JaxrsActivator. > On the other hand, it properly reports a warning when a letter is missing in the classname. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2715) provide script & instructions for performing headless commandline installations of JBDS

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2715?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2715: --------------------------------------- +1 based on screen capture above > provide script & instructions for performing headless commandline installations of JBDS > --------------------------------------------------------------------------------------- > > Key: JBDS-2715 > URL: https://issues.jboss.org/browse/JBDS-2715 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: JBDS2823.png > > > Script for linux: > https://gist.github.com/nickboldt/6041754 > Need a windows version & then to provide this somewhere along w/ the JBDS installer, perhaps on the CSP / EA pages? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-14544: ------------------------------------- In the case of Android, the world market contains many, many Android 2.3 devices still - it is important that our tools be able to create apps that are testable and deployable to Android 2.3 devices. In the case of XCode, well iOS does not have the upgrade problem, most folks move to the latest iOS quickly, causing developers to also have to upgrade their XCode's fairly quickly. I have never tried to have two versions of XCode on my machine...anybody try that? > Cannot run Cordova project on Android Emulator/Device > ----------------------------------------------------- > > Key: JBIDE-14544 > URL: https://issues.jboss.org/browse/JBIDE-14544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.0.Beta1 > Environment: Fedora 17 32bit > Android 4.1.2 > Reporter: Stefan Bunciak > Assignee: Gorkem Ercan > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > {code} > java.io.IOException: No such file or directory > at java.io.UnixFileSystem.createFileExclusively(Native Method) > at java.io.File.createNewFile(File.java:883) > at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99) > at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2715) provide script & instructions for performing headless commandline installations of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2715?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2715 at 11/7/13 11:24 AM: ------------------------------------------------------------ PR applied: https://github.com/jbdevstudio/jbdevstudio-website/pull/50 New layout for scripted install page: !JBDS2823.png! Pages to review: https://devstudio.jboss.com/updates/7.0-staging/ https://devstudio.jboss.com/updates/7.0-development/ https://devstudio.jboss.com/updates/7.0/ https://devstudio.jboss.com/download/scripted-install/ Aside: also fixed references to "EAP" -> "JBoss EAP" on download/* pages. https://devstudio.jboss.com/download/7.x.html https://devstudio.jboss.com/download/6.x.html https://devstudio.jboss.com/download/5.x.html https://devstudio.jboss.com/download/4.x.html was (Author: nickboldt): PR applied: https://github.com/jbdevstudio/jbdevstudio-website/pull/50 New layout for scripted install page: !JBDS2823.png! Also fixed references to "EAP" -> "JBoss EAP" on download/* pages. Pages to review: https://devstudio.jboss.com/updates/7.0-staging/ https://devstudio.jboss.com/updates/7.0-development/ https://devstudio.jboss.com/updates/7.0/ https://devstudio.jboss.com/download/7.x.html https://devstudio.jboss.com/download/6.x.html https://devstudio.jboss.com/download/5.x.html https://devstudio.jboss.com/download/4.x.html https://devstudio.jboss.com/download/scripted-install/ > provide script & instructions for performing headless commandline installations of JBDS > --------------------------------------------------------------------------------------- > > Key: JBDS-2715 > URL: https://issues.jboss.org/browse/JBDS-2715 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: JBDS2823.png > > > Script for linux: > https://gist.github.com/nickboldt/6041754 > Need a windows version & then to provide this somewhere along w/ the JBDS installer, perhaps on the CSP / EA pages? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2715) provide script & instructions for performing headless commandline installations of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2715?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2715: ----------------------------- CDW release: + (was: ?) > provide script & instructions for performing headless commandline installations of JBDS > --------------------------------------------------------------------------------------- > > Key: JBDS-2715 > URL: https://issues.jboss.org/browse/JBDS-2715 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: JBDS2823.png > > > Script for linux: > https://gist.github.com/nickboldt/6041754 > Need a windows version & then to provide this somewhere along w/ the JBDS installer, perhaps on the CSP / EA pages? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2715) provide script & instructions for performing headless commandline installations of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2715?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2715: ----------------------------- CDW qa_ack: + (was: ?) > provide script & instructions for performing headless commandline installations of JBDS > --------------------------------------------------------------------------------------- > > Key: JBDS-2715 > URL: https://issues.jboss.org/browse/JBDS-2715 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: JBDS2823.png > > > Script for linux: > https://gist.github.com/nickboldt/6041754 > Need a windows version & then to provide this somewhere along w/ the JBDS installer, perhaps on the CSP / EA pages? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2715) provide script & instructions for performing headless commandline installations of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2715?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-2715. ------------------------------ Resolution: Done Resolving again, pending further input from [~maxandersen], [~mmusaji] or [~mmurray]. > provide script & instructions for performing headless commandline installations of JBDS > --------------------------------------------------------------------------------------- > > Key: JBDS-2715 > URL: https://issues.jboss.org/browse/JBDS-2715 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: JBDS2823.png > > > Script for linux: > https://gist.github.com/nickboldt/6041754 > Need a windows version & then to provide this somewhere along w/ the JBDS installer, perhaps on the CSP / EA pages? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-14544: -------------------------------------- So far I have been quite relaxed with our XCode and Android SDK requirements. Perhaps we should start to be picky about it and force the latest. For examples. in the case of android target API levels I now demand level 17 or better and I am thinking that perhaps it should be 19 or better. I guess the question is demanding the latest of XCode and Android tools a great burden for the users? > Cannot run Cordova project on Android Emulator/Device > ----------------------------------------------------- > > Key: JBIDE-14544 > URL: https://issues.jboss.org/browse/JBIDE-14544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.0.Beta1 > Environment: Fedora 17 32bit > Android 4.1.2 > Reporter: Stefan Bunciak > Assignee: Gorkem Ercan > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > {code} > java.io.IOException: No such file or directory > at java.io.UnixFileSystem.createFileExclusively(Native Method) > at java.io.File.createNewFile(File.java:883) > at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99) > at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- 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, 5 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 November 2013