May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-320) JBDS BYOE can also be installed via Eclipse Marketplace

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-320?page=com.atlassian.jira.plug... ] Len DiMaggio closed TOOLSDOC-320. --------------------------------- The book looks great - closing the JIRA. http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo... > JBDS BYOE can also be installed via Eclipse Marketplace > ------------------------------------------------------- > > Key: TOOLSDOC-320 > URL: https://issues.jboss.org/browse/TOOLSDOC-320 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Getting Started Guide > Affects Versions: 4.0.0.Final > Reporter: Burr Sutter > Assignee: Len DiMaggio > Attachments: eclipse_marketplace.png > > > This says BYOE is focused on Help-Install New Software > https://access.redhat.com/site/documentation/en-US/JBoss_Developer_Studio... > When we recommend Eclipse Marketplace installation for BYOE. > Or did I miss an email someplace? > Also this doc does not say what version of Eclipse should be used. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-320) JBDS BYOE can also be installed via Eclipse Marketplace

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-320?page=com.atlassian.jira.plug... ] Len DiMaggio reassigned TOOLSDOC-320: ------------------------------------- Assignee: Len DiMaggio (was: Jiri Peterka) > JBDS BYOE can also be installed via Eclipse Marketplace > ------------------------------------------------------- > > Key: TOOLSDOC-320 > URL: https://issues.jboss.org/browse/TOOLSDOC-320 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Getting Started Guide > Affects Versions: 4.0.0.Final > Reporter: Burr Sutter > Assignee: Len DiMaggio > Attachments: eclipse_marketplace.png > > > This says BYOE is focused on Help-Install New Software > https://access.redhat.com/site/documentation/en-US/JBoss_Developer_Studio... > When we recommend Eclipse Marketplace installation for BYOE. > Or did I miss an email someplace? > Also this doc does not say what version of Eclipse should be used. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14663) Source lookup dialog shown twice on maven projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14663?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-14663: ------------------------------------- Ok I managed to reproduce the behavior you showed. This is clearly inconsistent IMO. > Source lookup dialog shown twice on maven projects > -------------------------------------------------- > > Key: JBIDE-14663 > URL: https://issues.jboss.org/browse/JBIDE-14663 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: respin-b > Fix For: 4.1.0.Beta1 > > > Source lookup dialog is shown twice on maven projects : http://screencast.com/t/3yESat96FIw > I think our source lookup should ignore projects with the maven nature, since a m2e's source lookup mechanism is already running in the background. > If maven nature is enabled AND source is set but missing THEN, it'd be ok to show our own stuff -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14680) Missing icons in forge wizards

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14680?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-14680: ---------------------------------------- [~koen.aers] if you don't have good icons for the wizards we can ask [~dazarov] to create some. > Missing icons in forge wizards > ------------------------------ > > Key: JBIDE-14680 > URL: https://issues.jboss.org/browse/JBIDE-14680 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta1 > Reporter: Pavol Srna > Fix For: 4.1.0.Beta2 > > Attachments: forge-wizards.png > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11881) Display application state in OpenShift Explorer and Properties view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11881?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11881: ------------------------------------- Labels: new_and_noteworthy (was: ) > Display application state in OpenShift Explorer and Properties view > ------------------------------------------------------------------- > > Key: JBIDE-11881 > URL: https://issues.jboss.org/browse/JBIDE-11881 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta2 > > > From Bugzilla#805989 > The state of the application on each gear can be checked using the gear_groups > rest api. > /broker/rest/domains/<domain-name>/applications/<app-name>/gear_groups > This rest call reflects the state of the application on each gear based on the > contents of the file $OPENSHIFT_GEAR_DIR/runtime/.state > The following states should be tracked in ~/runtime/.state > stopped > building > deploying > started > idle > unknown -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-343) NeedInfo: Disabling validation to remove/reduce false warnings

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-343?page=com.atlassian.jira.plug... ] Alexey Kazakov commented on TOOLSDOC-343: ----------------------------------------- IMO Facelet validation (Eclipse WTP) is... not perfect ;) So I would not be surprised if there are still some false problems reported by this validation (JSF and others). But I don't recall the particular issues right now besides the issue with faces converters declared via CDI. Anyway I think it's a good idea to have a quick fix which we provide to disable this validation if user believes he is dealing with a false warning/error. > NeedInfo: Disabling validation to remove/reduce false warnings > -------------------------------------------------------------- > > Key: TOOLSDOC-343 > URL: https://issues.jboss.org/browse/TOOLSDOC-343 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - JSF Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Alexey Kazakov > Fix For: 4.1.0 > > > I came across: http://docs.jboss.org/tools/whatsnew/jst/jst-news-3.3.0.M5.html > It states: > 1) JSF @FacesConverter validation: faces converter validation is an issue in eclipse > 2) Configuring Problem Severity via Quick Fix: problems if you use CDI programatically or you use CDI components that are not detectable by the tooling > *Are these instances of validation still issues?* > I tested (1) with <f:converter converterID="test"></f:converter> and didn't get any error or warning messages so thought it might be fixed in eclipse. Not sure how to test CDI yet (haven't got to that chapter!). -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11903) OpenShift Explorer: add Application start/stop/restart

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11903?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11903: ------------------------------------- Labels: new_and_noteworthy (was: ) > OpenShift Explorer: add Application start/stop/restart > ------------------------------------------------------- > > Key: JBIDE-11903 > URL: https://issues.jboss.org/browse/JBIDE-11903 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta2 > Environment: Eclipse plugin > Reporter: Nam Duong > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta2 > > > The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14588) Create OpenShift Application from remote repository

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14588?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14588: ------------------------------------- Labels: new_and_noteworthy (was: ) > Create OpenShift Application from remote repository > --------------------------------------------------- > > Key: JBIDE-14588 > URL: https://issues.jboss.org/browse/JBIDE-14588 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta2 > > > It'd be nice to create an OpenShift app directly from a remote git repo, to be consistent with the Web UI : > !http://content.screencast.com/users/fbricon/folders/Jing/media/3fcb6305-5340-4529-91c9-2466266d32c4/2013-05-22_1857.png! -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13882) Allow users to easily "binary deploy"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13882?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13882: ------------------------------------- Labels: new_and_noteworthy (was: ) > Allow users to easily "binary deploy" > ------------------------------------- > > Key: JBIDE-13882 > URL: https://issues.jboss.org/browse/JBIDE-13882 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta2 > > Attachments: 2013-05-29 13.33.bmml, 2013-05-29 13.33.png > > > We should have an option in the wizard that allows easy "binary only" deployment > {quote} > 'binary deployment only' option which will go disable the the build marker...but what do we do about the existing project content - just leave it in place I would say.{quote} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14537) BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14537?page=com.atlassian.jira.plugi... ] Yahor Radtsevich edited comment on JBIDE-14537 at 5/29/13 12:44 PM: -------------------------------------------------------------------- We could use something like {{@Category}} annotation ([see example|http://craigpardey.com/wp/2012/07/junit-categories-with-maven/]). The only problem with it is that we will have to move the tests in this plugin from JUnit 3 to JUnit 4. was (Author: yradtsevich): We could use something like {{@Category}} annotation ([see example|http://craigpardey.com/wp/2012/07/junit-categories-with-maven/]). > BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent > -------------------------------------------------------------------------------- > > Key: JBIDE-14537 > URL: https://issues.jboss.org/browse/JBIDE-14537 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.Beta1 > Reporter: Yahor Radtsevich > Assignee: Nick Boldt > Fix For: 4.1.0.Beta2 > > > https://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.1.keple... > org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent > {code} > org.eclipse.swt.SWTError: No more handles > at org.eclipse.swt.SWT.error(SWT.java:4418) > at org.eclipse.swt.SWT.error(SWT.java:4307) > at org.eclipse.swt.SWT.error(SWT.java:4278) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:103) > at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:9) > at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:24) > at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:38) > at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:36) > at org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent(WebKitTests.java:39) > 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 junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3692) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > 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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {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, 10 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 May 2013