November 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-13053) Cannot remove several connections at once

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13053: ---------------------------------------- Summary: Cannot remove several connections at once Key: JBIDE-13053 URL: https://issues.jboss.org/browse/JBIDE-13053 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.0.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.0.x Attachments: several-connections.png The *OpenShift Explorer* allows you to remove a single connection from the context-menu: select your connection and pick *Remove from View*. Your connection will be removed from the OpenShift Explorer. This is currently not possible for several connections at once - the menu entry is missing from the context menu. !several-connections.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

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] (JBIDE-13052) Move the JAX-RS configurator to m2e-wtp

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-13052: ----------------------------------- Summary: Move the JAX-RS configurator to m2e-wtp Key: JBIDE-13052 URL: https://issues.jboss.org/browse/JBIDE-13052 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: maven Affects Versions: 4.0.0.Beta1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Final Move the JAX-RS configurator to m2e-wtp -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13050) Move the JPA configurator to m2e-wtp

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-13050: ----------------------------------- Summary: Move the JPA configurator to m2e-wtp Key: JBIDE-13050 URL: https://issues.jboss.org/browse/JBIDE-13050 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: maven Affects Versions: 4.0.0.Beta1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Final Move the JPA configurator to m2e-wtp -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13051) Move the JSF configurator to m2e-wtp

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-13051: ----------------------------------- Summary: Move the JSF configurator to m2e-wtp Key: JBIDE-13051 URL: https://issues.jboss.org/browse/JBIDE-13051 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: maven Affects Versions: 4.0.0.Beta1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Final Move the JSF configurator to m2e-wtp -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12920) Java EE Project -> Java EE EAR Project

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-12920: ----------------------------------- Summary: Java EE Project -> Java EE EAR Project Key: JBIDE-12920 URL: https://issues.jboss.org/browse/JBIDE-12920 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Burr Sutter On JBoss Central, we have found a number of people are defaulting to "Java EE Project" instead of "Java EE Web Project". Normally, we want users to select the "Java EE Web Project" as part of the getting started experience described in http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/ Hopefully making "Java EE Project" -> "Java EE EAR Project" will make it more clear. -- 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

13 years, 4 months

4
4
0 / 0

[JBoss JIRA] (JBIDE-12528) Create standalone wizard for conversion to maven dependencies

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12528: ----------------------------------- Summary: Create standalone wizard for conversion to maven dependencies Key: JBIDE-12528 URL: https://issues.jboss.org/browse/JBIDE-12528 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 4.0.0.Alpha1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Alpha2 As a follow up on JBIDE-8973, we should be able to also convert project dependencies that are not classpath entries. Use case : convert an EAR project to maven. All the jars in <earproject>/lib/ and all jars referenced as virtual components in .settings/org.eclipse.wst.common.component should be identified and converted -- 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

13 years, 4 months

1
6
0 / 0

[JBoss JIRA] (JBIDE-12902) Project runtime pref page modifies original model without call to performOK or performApply

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12902: ----------------------------------- Summary: Project runtime pref page modifies original model without call to performOK or performApply Key: JBIDE-12902 URL: https://issues.jboss.org/browse/JBIDE-12902 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime detection Affects Versions: 4.0.0.Beta1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.0.0.CR1 Add, edit, and remove, all edit the core model of runtime paths in this preference page. Also, the preference page is often closed and re-opened when this doesn't need to happen. Possible fixes are 1) to ensure NO ONE saves a model until performOK or performApply is called, 2) keep track of if the page is dirty or not 3) show a dialog when clicking 'link' on a dirty page asking to save and re-open the page -- 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

13 years, 4 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-12964) cdi test failure

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12964: -------------------------------------- Summary: cdi test failure Key: JBIDE-12964 URL: https://issues.jboss.org/browse/JBIDE-12964 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 4.0.0.CR1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.0.0.CR1 {code} # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007ff8bf8cb5a0, pid=15421, tid=140708811110144 # # JRE version: 7.0_09-b05 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.5-b02 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libwebkitgtk-1.0.so.0+0x14245a0] void WTF::freeOwnedGPtr<_GdkEvent>(_GdkEvent*)+0x15df0 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/igels/Projects/jbt-4.0/requests/jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/hs_err_pid15421.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # {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

13 years, 4 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-12969) importing invalid project archives descriptor causes view to freeze

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12969: ----------------------------------- Summary: importing invalid project archives descriptor causes view to freeze Key: JBIDE-12969 URL: https://issues.jboss.org/browse/JBIDE-12969 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 4.0.0.Alpha2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.0.0.CR1 1) Import a project with an invalid project archives descriptor. 2) Open the project archives view. 3) expand the project The registration job will continue over and over and over, never failing cleanly or alerting the user of the error. -- 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

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-12968) NPE after deleting project containing archives, creating new one w new archives

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12968: ----------------------------------- Summary: NPE after deleting project containing archives, creating new one w new archives Key: JBIDE-12968 URL: https://issues.jboss.org/browse/JBIDE-12968 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 4.0.0.Alpha2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.0.0.CR1 open a workspace containing 1 project with 2 project archives in it. delete the project create a new project, add an archive to it stack trace: 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.core.runtime.Path.initialize(Path.java:577) at org.eclipse.core.runtime.Path.<init>(Path.java:163) at org.jboss.ide.eclipse.archives.core.util.PathUtils.getAbsoluteLocation(PathUtils.java:70) at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory$DirectoryScannerExtension.setBasedir2(DirectoryScannerFactory.java:106) at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory$DirectoryScannerExtension.<init>(DirectoryScannerFactory.java:102) at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:63) at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:45) at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveFileSetImpl.getScanner(ArchiveFileSetImpl.java:133) at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveFileSetImpl.matchesPath(ArchiveFileSetImpl.java:95) at org.jboss.ide.eclipse.archives.core.util.ModelUtil$1.visit(ModelUtil.java:64) -- 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

13 years, 4 months

2
3
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 2012