April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent

by Denis Golovin (JIRA)

Project Explorer has child node looking exactly the same as parent ------------------------------------------------------------------ Key: JBIDE-8306 URL: https://issues.jboss.org/browse/JBIDE-8306 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.3.0.M1 Attachments: screenshot68.png Project with Enabled JSF/Struts capabilities contains child node that looks exactly the same as parent in Project Explorer view !screenshot68.png! It contains information about configuration (web deployment descriptor, JSF/Struts configuration, taglibs, beans and etc) and resources from web root. We have several way to give it a better look and usability: 1. (simple) find a right name/icon for it to describe content in it and remove redundant nodes from it (WebContent and web deployment descriptor, for instance, are already present under project in Projects Explorer) 2. Split it in several nodes to be shown as Project node siblings. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-8661) ModeShape Tools' SLF4J LoggerFactoryBinder Implementation Not Found On Classpath

by Dan Florian (JIRA)

ModeShape Tools' SLF4J LoggerFactoryBinder Implementation Not Found On Classpath -------------------------------------------------------------------------------- Key: JBIDE-8661 URL: https://issues.jboss.org/browse/JBIDE-8661 Project: Tools (JBoss Tools) Issue Type: Bug Components: modeshape Affects Versions: 3.2.0.Final Reporter: Dan Florian Assignee: Dan Florian Fix For: 3.2.1 With ModeShape 2.5.0.Beta1, the ModeShape jar no longer contains an implementation of LoggerFactoryBinder. This change in the MS jar revealed the MS Tools LoggerFactoryBinder implementation (which directs logging to the Eclipse logger) was not being found. This is because the MS Tools implementation was not in the correct package. SLF4J requires instances of LoggerFactoryBinder be in the "org.slf4j.impl" package. Need to repackage the MS Tools' impl. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8827) Cheatsheet's broken and incomplete for Seam 2.2 booking example

by Max Rydahl Andersen (JIRA)

Cheatsheet's broken and incomplete for Seam 2.2 booking example --------------------------------------------------------------- Key: JBIDE-8827 URL: https://issues.jboss.org/browse/JBIDE-8827 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.2.0.Final Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Fix For: 3.2.1.M1, 3.3.0.M1 Chose "Seam 2.2 Booking Example - Ear (including a tutorial)" shows a great cheat sheet but the actions in there fails with IllegalArgumentExceptions and there seem to be missing links for large sections of the tutorial ? java.lang.IllegalArgumentException at org.eclipse.ui.part.FileEditorInput.getPath(FileEditorInput.java:208) at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:662) at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:638) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2860) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2768) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2760) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2711) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2707) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2691) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2682) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:651) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:610) at org.jboss.tools.project.examples.cheatsheet.actions.Ope -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8818) org.jboss.tools.seam.core.test.refactoring.SeamRefactoringAllTests.testSeamComponentRename failed: Can't load component best

by Nick Boldt (JIRA)

org.jboss.tools.seam.core.test.refactoring.SeamRefactoringAllTests.testSeamComponentRename failed: Can't load component best ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8818 URL: https://issues.jboss.org/browse/JBIDE-8818 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.1.M1 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.2.1.M1 https://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-3.2_stab... Regression org.jboss.tools.seam.core.test.refactoring.SeamRefactoringAllTests.testSeamComponentRename Failing for the past 1 build (Since Failed#169 ) Took 4 sec. add description Error Message Can't load component best Stacktrace junit.framework.AssertionFailedError: Can't load component best at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at org.jboss.tools.seam.core.test.refactoring.SeamComponentRefactoringTest.renameComponent(SeamComponentRefactoringTest.java:133) at org.jboss.tools.seam.core.test.refactoring.SeamComponentRefactoringTest.testSeamComponentRename(SeamComponentRefactoringTest.java:81) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8707) maven configurators have redundant names

by Max Rydahl Andersen (JIRA)

maven configurators have redundant names ---------------------------------------- Key: JBIDE-8707 URL: https://issues.jboss.org/browse/JBIDE-8707 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.2.0.Final Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Priority: Minor Fix For: 3.2.1, 3.3.0.M1 Our Maven configurators as redundant configurator in their name - see screenshot. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8533) Add migration path for SOA-P 5.1 to 5.2 for BPEL project facets

by Robert (Bob) Brodt (JIRA)

Add migration path for SOA-P 5.1 to 5.2 for BPEL project facets --------------------------------------------------------------- Key: JBIDE-8533 URL: https://issues.jboss.org/browse/JBIDE-8533 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpel Affects Versions: 3.2.0.CR1 Environment: all Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.2.1 SOA-P 5.2 PRD document requirement SOA-MGUP-1: If we decide to change the BPEL project facet ID from "jbt.bpel.facet.core" to "bpel.facet.core" (as it is defined in the eclipse.org BPEL Designer) then we will need to provide the user with some sort of migration path for SOA-P 5.1 projects. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8633) Instance wizard: starting wizard may freeze UI

by Andre Dietisheim (JIRA)

Instance wizard: starting wizard may freeze UI ---------------------------------------------- Key: JBIDE-8633 URL: https://issues.jboss.org/browse/JBIDE-8633 Project: Tools (JBoss Tools) Issue Type: Bug Components: core Affects Versions: 3.1.x, 3.2.x Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.1.x, 3.2.x the fix for JBIDE-8102 makes sure that the images are loaded if you request an image. If the images were not loaded before, launching the instance wizard may therefore load all images. It unfortunately does not do that in the background and it therefore may the UI. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8723) Run m2eclipse-wtp tests on windows

by Fred Bricon (JIRA)

Run m2eclipse-wtp tests on windows ---------------------------------- Key: JBIDE-8723 URL: https://issues.jboss.org/browse/JBIDE-8723 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Fred Bricon Snjeza, m2eclipse-wtp tests fail on windows (https://grid.sonatype.org/ci/job/m2eclipse-wtp/jdk=java-6x,label=m2e/46/t...), since I'm not using windows at the moment, could you please check what the problem is? I successfully build against e35 (mvn clean install) and e36 (mvn clean install -Dtarget.platform=m2e-wtp-e36) target platforms; Thanks. Fred Bricon -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8552) OutOfMemoryError in org.jboss.tools.seam.xml.test 3.2.0-SNAPSHOT

by Nick Boldt (JIRA)

OutOfMemoryError in org.jboss.tools.seam.xml.test 3.2.0-SNAPSHOT ---------------------------------------------------------------- Key: JBIDE-8552 URL: https://issues.jboss.org/browse/JBIDE-8552 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam, testing Affects Versions: 3.2.1 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.2.1 http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_stable_branch.compon... unpack-zip: [unzip] Expanding: /qa/hudson_ws/workspace/jbosstools-3.2_stable_branch.component--seam/requirements/download/seam-2.1.1.GA/jboss-seam-2.1.1.GA.zip into /qa/hudson_ws/workspace/jbosstools-3.2_stable_branch.component--seam/requirements/target [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building org.jboss.tools.seam.xml.test 3.2.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ Downloading: http://snapshots.jboss.org/maven2/org/apache/maven/plugins/maven-install-... Downloading: http://repository.jboss.org/maven2/org/apache/maven/plugins/maven-install... Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/... Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/apache/ma... Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plug... Exception in thread "pool-225-thread-1" java.lang.OutOfMemoryError at java.util.zip.Inflater.init(Native Method) at java.util.zip.Inflater.<init>(Inflater.java:83) at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:56) at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:68) at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:127) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:590) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/... (481 B at 1.0 KB/sec) Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/apache/ma... (669 B at 0.9 KB/sec) Downloading: http://repository.jboss.org/maven2/org/apache/maven/plugins/maven-resourc... Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/apache/ma... Downloading: http://snapshots.jboss.org/maven2/org/apache/maven/plugins/maven-resource... Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/... Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-pl... Exception in thread "pool-231-thread-1" java.lang.OutOfMemoryError at java.util.zip.Inflater.init(Native Method) at java.util.zip.Inflater.<init>(Inflater.java:83) at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:56) at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:68) at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:127) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:590) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/... (405 B at 0.8 KB/sec) # # A fatal error has been detected by the Java Runtime Environment: # # java.lang.OutOfMemoryError: requested 32756 bytes for ChunkPool::allocate. Out of swap space? # # Internal Error (allocation.cpp:117), pid=21825, tid=1129044880 # Error: ChunkPool::allocate # # JRE version: 6.0_20-b02 # Java VM: Java HotSpot(TM) Server VM (16.3-b01 mixed mode linux-x86 ) # An error report file with more information is saved as: # /qa/hudson_ws/workspace/jbosstools-3.2_stable_branch.component--seam/sources/hs_err_pid21825.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8725) OutOfMemoryError in org.jboss.tools.seam.ui.test

by Nick Boldt (JIRA)

OutOfMemoryError in org.jboss.tools.seam.ui.test ------------------------------------------------ Key: JBIDE-8725 URL: https://issues.jboss.org/browse/JBIDE-8725 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.1 Reporter: Nick Boldt Assignee: Alexey Kazakov Priority: Blocker Fix For: 3.2.1 http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/jbosst... /mnt/hudson_workspace/workspace/jbosstools-3.2_stable_branch.component--seam/results/jbosstools-3.2_stable_branch.component--seam/logs/ERRORLOG.txt: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.3:run (download-plugin-requirements) on project org.jboss.tools.seam.ui.test: An Ant BuildException has occured: The following error occurred while executing this line: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.2_stable_branch.component--seam/requirements/build.xml:18: The following error occurred while executing this line: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.2_stable_branch.component--seam/requirements/buildRequirements.xml:13: The following error occurred while executing this line: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.2_stable_branch.component--seam/requirements/buildRequirements.xml:21: The following error occurred while executing this line: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.2_stable_branch.component--seam/requirements/buildRequirements.xml:111: The following error occurred while executing this line: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.2_stable_branch.component--seam/requirements/generic/build.xml:25: The following error occurred while executing this line: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.2_stable_branch.component--seam/requirements/seam-2.0.1.GA/buildRequirement.xml:5: java.lang.OutOfMemoryError [ERROR] -> [Help 1] [ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-packaging-plugin:0.10.0:package-feature (default-package-feature) on project org.jboss.tools.seam.test.feature: Execution default-package-feature of goal org.sonatype.tycho:maven-osgi-packaging-plugin:0.10.0:package-feature failed: At least ``package'' phase execution is required -> [Help 2] [INFO] org.jboss.tools.seam.ui.test ...................... FAILURE [1:36.763s] [INFO] org.jboss.tools.seam.test.feature ................. FAILURE [3.411s] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
17
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 April 2011