February 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-10758) Wrong project name in the JBoss quickstart 'Login' cheatsheet

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-10758: -------------------------------------- Summary: Wrong project name in the JBoss quickstart 'Login' cheatsheet Key: JBIDE-10758 URL: https://issues.jboss.org/browse/JBIDE-10758 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.3.0.M5 Reporter: Stefan Bunciak Assignee: Snjezana Peco Fix For: 3.3.0.Beta1 Attachments: Screenshot-4.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-10836) AssertionFailedException: null argument when updating project configuration

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-10836: ---------------------------------------- Summary: AssertionFailedException: null argument when updating project configuration Key: JBIDE-10836 URL: https://issues.jboss.org/browse/JBIDE-10836 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.Beta1 Reporter: Rastislav Wagner Assignee: Fred Bricon Priority: Minor org.eclipse.core.runtime.AssertionFailedException: null argument: at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) at org.eclipse.jface.viewers.AbstractTreeViewer.assertElementsNotNull(AbstractTreeViewer.java:1386) at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1354) at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:391) at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:917) at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:605) at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2620) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1908) at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1883) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1840) at org.eclipse.ui.navigator.CommonViewer.internalRefresh(CommonViewer.java:561) at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1535) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443) at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1533) at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:548) at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:350) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$3.run(PackageExplorerContentProvider.java:944) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.runUpdates(PackageExplorerContentProvider.java:195) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.runPendingUpdates(PackageExplorerContentProvider.java:187) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$1.runInUIThread(PackageExplorerContentProvider.java:165) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) 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:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-10516) New OpenShift Express application wizard issues

by Jiri Peterka (Created) (JIRA)

New OpenShift Express application wizard issues ----------------------------------------------- Key: JBIDE-10516 URL: https://issues.jboss.org/browse/JBIDE-10516 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Environment: JBDS 5.0.M5a H62, L64 Reporter: Jiri Peterka Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 Steps: Start on New Openshift App wizard on application selection page - Click New - Write app name, click Next, wait... - Then click "Back" Then there are some scenarios that should be tuned: 1. When you click Cancel, you'll get back to table where Application is missing. You have to go back and forward to have it updated. 2. When you click Forward, you'll get message that application is created although wizard wasn't finished (I understand that app was created after "Next" button click" which is strange but so be it) How this can be fixed: 1. Disable Back button when app is created and 2. After cancel, app table list needs to be updated -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
5
0 / 0

[JBoss JIRA] (JBIDE-10513) management ports in 7.1 as using properties causing automatic detection to fail

by Max Rydahl Andersen (Created) (JIRA)

management ports in 7.1 as using properties causing automatic detection to fail ------------------------------------------------------------------------------- Key: JBIDE-10513 URL: https://issues.jboss.org/browse/JBIDE-10513 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.Beta1 Seems CR1 made the following changes: < <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/> < <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/> --- > <socket-binding name="management-native" interface="management" port="9999"/> > <socket-binding name="management-http" interface="management" port="9990"/> Two things should happen: 1) we should handle this style 2) we should fallback to default if we can't parse the file instead of creating a "broken" editor. Should add warning about it not being detected, just doing default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
4
0 / 0

[JBoss JIRA] (JBIDE-10797) compile failed in as.ui

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10797: ---------------------------------- Summary: compile failed in as.ui Key: JBIDE-10797 URL: https://issues.jboss.org/browse/JBIDE-10797 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JBossAS/Servers Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Rob Stryker Fix For: 3.3.0.Beta1 With updated target platform, we get this compilation error: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.13.0:compile (default-compile) on project org.jboss.ide.eclipse.as.ui: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.continuous/sources/as/plugins/org.jboss.ide.eclipse.as.ui/jbossui/org/jboss/ide/eclipse/as/ui/editor/DeploymentTypeUIUtil.java (at line 94):[-1,-1] [ERROR] public void setErrorMessage(String msg) { [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [ERROR] The method setErrorMessage(String) of type DeploymentTypeUIUtil.NewServerWizardBehaviourCallback must override a superclass method [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.13.0:compile (default-compile) on project org.jboss.ide.eclipse.as.ui: Compilation failure {code} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/35... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9185) Create preference page for Seam Config validation

by Alexey Kazakov (JIRA)

Create preference page for Seam Config validation ------------------------------------------------- Key: JBIDE-9185 URL: https://issues.jboss.org/browse/JBIDE-9185 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: cdi (jsr-299) Affects Versions: 3.3.0.M2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8680) Rename Seam UI artifacts to Seam 2.

by Alexey Kazakov (JIRA)

Rename Seam UI artifacts to Seam 2. ----------------------------------- Key: JBIDE-8680 URL: https://issues.jboss.org/browse/JBIDE-8680 Project: Tools (JBoss Tools) Issue Type: Task Components: Seam Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M1 Since Seam 3.0 final has been released and we are working on support of Seam 3 extensions it's time to rename our Seam tools to Seam 2 not to confuse users. We should update UI stuff such as Wizard titles, perspective, views, editors, etc. And BTW the component name in JIRA :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7141) Provide details about selected runtime in the facet configuration dialog

by Lukas Jungmann (JIRA)

Provide details about selected runtime in the facet configuration dialog ------------------------------------------------------------------------ Key: JBIDE-7141 URL: https://jira.jboss.org/browse/JBIDE-7141 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.1.1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Attachments: screenshot.png It would be nice if we could tell user some details about JBossWS runtime he is going to use. See attached screenshot for how it could look like -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
19
0 / 0

[JBoss JIRA] Created: (JBIDE-5045) JSF 2: Support annotated manage beans in EL

by Alexey Kazakov (JIRA)

JSF 2: Support annotated manage beans in EL ------------------------------------------- Key: JBIDE-5045 URL: https://jira.jboss.org/jira/browse/JBIDE-5045 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: LATER We have to create JSF builder to load annotated manage beans to provide JSF model which should be used be JSF EL Resolver. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9793) Openshift Express: create a publishing method that would allow you to publish a project to the openshift PaaS

by Andre Dietisheim (JIRA)

Openshift Express: create a publishing method that would allow you to publish a project to the openshift PaaS ------------------------------------------------------------------------------------------------------------- Key: JBIDE-9793 URL: https://issues.jboss.org/browse/JBIDE-9793 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 * new Openshift publishing method * the publishing method would only show up as choice in the "Server Behavior" combo for: deploy only and AS7 server adapter. * the publishing method would contribute an appropriate composite: - combo/list that shows all available applications on Openshift Express - a link to a wizard to create new application * as soon as you select the application, we would clone the git repo * as soon as you add a project to the adapter, we would add the openshift clone repo to the repo of that project (as remote repo) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2012