February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16408) Use hybrid mobile engines from local directories

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16408?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16408: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 4.2.0.Beta1 Assignee: Gorkem Ercan > Use hybrid mobile engines from local directories > ------------------------------------------------ > > Key: JBIDE-16408 > URL: https://issues.jboss.org/browse/JBIDE-16408 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > It is only possible to get cordova engines from the apache repository in this release. This is a request to make it possible to configure a custom engine that exists on a directory. > This means selecting directories per supported platform. -- 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-16408) Use hybrid mobile engines from local directories

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16408?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-16408. ---------------------------------- Resolution: Done > Use hybrid mobile engines from local directories > ------------------------------------------------ > > Key: JBIDE-16408 > URL: https://issues.jboss.org/browse/JBIDE-16408 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > It is only possible to get cordova engines from the apache repository in this release. This is a request to make it possible to configure a custom engine that exists on a directory. > This means selecting directories per supported platform. -- 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-2032) Help button works not in all wizards.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ] Denis Golovin commented on JBIDE-2032: -------------------------------------- It looks like we can finally get decent help for all JBossTools/JBDS related features. It could be done by installing documentation features from p2 repo or by connecting local help information center to remote one: 1. We should deploy remote Information Center with JBT/JBDS documentation in eclipse format (I hope it cold be generated out of current documentation). 2. Every JBoss Tools UI Element like: New Wizard, Editor, Dialog, View should have set help context through call {code}PlatformUI.getWorkbench().getHelpSystem().setHelp(container, "plugin.id.<uielementname>_<name>");{code} where: * <uielementname> could be one of: newwizard, dialog, editor, view and e.t.c * <name> is readable feature name For example for new JSF Project Wizard it would be "org.jboss.tools.jsf.ui.newwizard_jsfproject If no context help requires then default context id should be used for example "org.jboss.tools.foundation.help.default" 3. org.jboss.tools.foundation.help registers so called Global Help Context Provider which process requested help context if itis not found by other context providers: * RemoteContextProvider (loads context from remote Info Center server(s) registered in preferences Help->Content) * FileContextProvider (load conext help form xml files defined through org.eclipse.help.bas.contexts extension point, which is usually done in documentation bundles) So if doc plugins (which usually defines context help) are not installed or not available from remote info center then control gets int global provider and it generates default page for context help with: * short description * link to external site * command to call documentation feature installation out of JBoss Central * command to register remote info center with JBoss Tools documentation Default context help by default is generated for JBoss Tools, but could be overriden in JBDS or other JBoss Tools Based product. Tested this approach on local build with local info center and it works as expected. > Help button works not in all wizards. > ------------------------------------- > > Key: JBIDE-2032 > URL: https://issues.jboss.org/browse/JBIDE-2032 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: help > Affects Versions: 2.1.0.beta1 > Reporter: Anton Klimkovich > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.2.x > > Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG, Resource - Eclipse Platform _028.png > > > Wizards with non-working help button attached. -- 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-16643) JSF composite component validation does not support http://xmlns.jcp.org name space

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16643?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16643: ----------------------------------- Description: 1. Create JSF 2.2 KickStartProject 2. Open <project>/WebContent/resources/demo/input.xhtml 3. Failure: There is a validation problem: "Unknown composite component "interface"" > JSF composite component validation does not support http://xmlns.jcp.org name space > ----------------------------------------------------------------------------------- > > Key: JBIDE-16643 > URL: https://issues.jboss.org/browse/JBIDE-16643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.2.0.Beta1 > > > 1. Create JSF 2.2 KickStartProject > 2. Open <project>/WebContent/resources/demo/input.xhtml > 3. Failure: There is a validation problem: "Unknown composite component "interface"" -- 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-16643) JSF composite component validation does not support http://xmlns.jcp.org name space

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-16643: -------------------------------------- Summary: JSF composite component validation does not support http://xmlns.jcp.org name space Key: JBIDE-16643 URL: https://issues.jboss.org/browse/JBIDE-16643 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.2.0.Beta1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov 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-16592) Allow to update/remove software installed from Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16592: --------------------------------------------- it depends how early access is implemented but if it is a new extra catalog then it would simply be the one we activate that will "overlay" the default catalog. i.e. connector with same name, only show the newest one. the early access can have a new connector that is not available in early access (for example Integration Stack release that is not yet relaseed etc.) > Allow to update/remove software installed from Central > ------------------------------------------------------ > > Key: JBIDE-16592 > URL: https://issues.jboss.org/browse/JBIDE-16592 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Fix For: 4.2.0.Beta1 > > Attachments: JBIDE-16592-wip.jpeg, JBIDE_16592_shot2.jpeg > > > Central software page should allow user to update or uninstall some modules. -- 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-16592) Allow to update/remove software installed from Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16592: --------------------------------------------- Not even p2 allow to uninstall and add in same workflow - central UI is not about being as complete/complex as possible - it is about simplifying. "check enable early-access" -> show the early-access instead of the supported version (of course only if early access is newer) > Allow to update/remove software installed from Central > ------------------------------------------------------ > > Key: JBIDE-16592 > URL: https://issues.jboss.org/browse/JBIDE-16592 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Fix For: 4.2.0.Beta1 > > Attachments: JBIDE-16592-wip.jpeg, JBIDE_16592_shot2.jpeg > > > Central software page should allow user to update or uninstall some modules. -- 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-15896) RuntimeWorkbenchUtils.refreshServersView() throws exception sometimes when running tycho tests

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15896?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15896: --------------------------------------- Currently, I can't find a failed build, but the issue happens when Eclipse shuts down before calling the method. The portlet component contains just one test so that Eclipse shuts down very fast. > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15394) Add arquillian.xml GUI editor to jbosstools-arquillian

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15394?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15394: --------------------------------------- {quote} snjezana - if you got a branch with your sapphire version why not share that on github ? then Masao Kunii and others can compare/see it ? {quote} I have meant you don't want to add the feature until the Saphire framework isn't stable. I will create a separate project. > Add arquillian.xml GUI editor to jbosstools-arquillian > ------------------------------------------------------ > > Key: JBIDE-15394 > URL: https://issues.jboss.org/browse/JBIDE-15394 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: testing-tools > Reporter: Masao Kunii > Assignee: Snjezana Peco > Priority: Optional > Fix For: 4.2.0.Beta1 > > > The arquillian.xml editor is an editor to edit arquillian.xml easily and visually. This is a feature for jbosstools-arquillian(https://github.com/jbosstools/jbosstools-arquillian) and enables to: > - Edit containers, container groups, extensions, protocols and engines > - Modify pom.xml automatically corresponding settings in arquillian.xml > - Register favorite container/container groups from Eclipse preferences -- 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-9115) Quick fix for "Multiple beans are eligible for injection point" problem markers works wrong in case of working with generic beans

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9115?page=com.atlassian.jira.plugin... ] Alexey Kazakov resolved JBIDE-9115. ----------------------------------- Fix Version/s: 4.2.0.Beta1 (was: LATER) Resolution: Won't Fix > Quick fix for "Multiple beans are eligible for injection point" problem markers works wrong in case of working with generic beans > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-9115 > URL: https://issues.jboss.org/browse/JBIDE-9115 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi-extensions > Affects Versions: 3.3.0.M1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Fix For: 4.2.0.Beta1 > > Attachments: CDIQuickFix.png > > > We have at least two problems: > 1. There are duplicate Beans in quick fix menu > 2. "Specify '<bean>' bean for injection to the injection point" quick fix does not work with generic beans > Test case 1: > EXECUTE: Import http://anonsvn.jboss.org/repos/jbosstools/trunk/cdi/tests/org.jboss.tools... CDI Project > EXECUTE: Open org.jboss.generic2.DurableMessageLogger in Java Editor > EXECUTE: Point mouse to @Inject annotations and wait > ASSERT: Quick fix tool tip appears > ASSERT: There is no duplicate quick fixes -- 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 February 2014