November 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12229) Error properly when server start fails because of -server parameter

by Martin Malina (JIRA)

13 years, 4 months

3
25
0 / 0

[JBoss JIRA] Created: (JBIDE-8997) CLONE - 2010 in the copyright headers should be replaced by 2011

by Max Rydahl Andersen (JIRA)

CLONE - 2010 in the copyright headers should be replaced by 2011 ---------------------------------------------------------------- Key: JBIDE-8997 URL: https://issues.jboss.org/browse/JBIDE-8997 Project: Tools (JBoss Tools) Issue Type: Bug Components: Legal Reporter: Lukas Jungmann Fix For: 3.2.1.CR1 applies to all JBT features (JMX, Hibernate Tools, ESB Tools...) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

10
28
0 / 0

[JBoss JIRA] (JBDS-2387) Scala jars added to deployment when they should not

by Galder Zamarreño (JIRA)

Galder Zamarreño created JBDS-2387: -------------------------------------- Summary: Scala jars added to deployment when they should not Key: JBDS-2387 URL: https://issues.jboss.org/browse/JBDS-2387 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.GA Reporter: Galder Zamarreño Hmmm, seems like we've gone the opposite way now. My lift dependencies, which bring in Scala, are defined as provided: {code}<dependency> <groupId>net.liftweb</groupId> <artifactId>lift-mapper_${version.scala}</artifactId> <version>2.4</version> <scope>provided</scope> </dependency>{code} And now, you're adding the Scala jars to the WAR when it shouldn't? See screenshot: https://dl.dropbox.com/u/6148072/Screen%20Shot%202012-11-14%20at%206.26.4... Who's responsibility is this? -- 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
5
0 / 0

[JBoss JIRA] (JBIDE-12245) Document Maven How-Tos

by Burr Sutter (JIRA)

13 years, 4 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-12563) Show in MBean Explorer not available when it should be

by Martin Malina (JIRA)

Martin Malina created JBIDE-12563: ------------------------------------- Summary: Show in MBean Explorer not available when it should be Key: JBIDE-12563 URL: https://issues.jboss.org/browse/JBIDE-12563 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 4.0.0.Alpha1 Environment: JBT 4.0.0.Alpha1 B6 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.0.0.Alpha2 When you start EAP 5.1.2 and then try to invoke server -> Show in -> MBean Explorer, it is grayed out and cannot be clicked. But when I open the MBean Explorer manually I can access the server's mbeans no problem. -- 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
21
0 / 0

[JBoss JIRA] (JBIDE-12987) HTML5 Archetype - JBoss Central

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-12987: ----------------------------------- Summary: HTML5 Archetype - JBoss Central Key: JBIDE-12987 URL: https://issues.jboss.org/browse/JBIDE-12987 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter Priority: Critical Attachments: 2012-11-02_1412.png Simply broken in JBDS6 Beta1 - ArtifactDescriptorException: Failed to read artifact descriptor for org.jboss.as:jboss-as-arquillian-container-remote:jar:${version.org.jboss.as.arquillian.container}: ArtifactResolutionException: Failure to transfer org.jboss.as:jboss-as-arquillian-container-remote:pom:${version.org.jboss.as.arquillian.container} from http://maven.repository.redhat.com/techpreview/all/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap has elapsed or updates are forced. Original error: Could not transfer artifact org.jboss.as:jboss-as-arquillian-container-remote:pom:${version.org.jboss.as.arquillian.container} from/to jboss-eap (http://maven.repository.redhat.com/techpreview/all/): Illegal character in path at index 102: http://maven.repository.redhat.com/techpreview/all/org/jboss/as/jboss-as-... -- 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

6
13
0 / 0

[JBoss JIRA] (JBIDE-11410) Crash in Eclipse when running JBoss Server

by Muh Khairul Lukman W. (JIRA)

Muh Khairul Lukman W. created JBIDE-11410: --------------------------------------------- Summary: Crash in Eclipse when running JBoss Server Key: JBIDE-11410 URL: https://issues.jboss.org/browse/JBIDE-11410 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta1 Environment: JRE version: 7.0_147-b147 Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) Derivative: IcedTea7 2.0 Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10. Eclipse 3.7.2 64 bit Reporter: Muh Khairul Lukman W. Assignee: Rob Stryker Attachments: hs_err_pid25114.log {code} Mar 27, 2012 2:14:48 PM org.xnio.Xnio <clinit> INFO: XNIO Version 3.0.3.GA Mar 27, 2012 2:14:48 PM org.xnio.nio.NioXnio <clinit> INFO: XNIO NIO Implementation Version 3.0.3.GA Mar 27, 2012 2:14:48 PM org.jboss.remoting3.EndpointImpl <clinit> INFO: JBoss Remoting version 3.2.2.GA # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f6542da4697, pid=25114, tid=140073270568704 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [libplds4.so+0x1697] PL_HashTableLookupConst+0x17 # # 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/rully/eclipse_jee/hs_err_pid25114.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. {code} When i start to run JBoss server in eclipse, it start to crash and shut down.. JBoss service server won't running on my desktop. -- 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

13 years, 4 months

11
37
0 / 0

[JBoss JIRA] (JBIDE-13099) org.jboss.ide.eclipse.archives.test.core.ant.SimpleAntTest.testOne has failed for the last 22 builds

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13099: ---------------------------------- Summary: org.jboss.ide.eclipse.archives.test.core.ant.SimpleAntTest.testOne has failed for the last 22 builds Key: JBIDE-13099 URL: https://issues.jboss.org/browse/JBIDE-13099 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 4.0.0.CR1 Reporter: Nick Boldt Assignee: Rob Stryker Priority: Blocker {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--server/22/testReport/} >>> org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest.testJBIDE6184_Odd_Republish_Error[0] 11 sec 1 >>> org.jboss.tools.as.test.core.parametized.server.ServerBeanLoader3Test.testServerBeanLoaderFromRuntimes[9] 11 ms 10 >>> org.jboss.tools.as.test.core.parametized.server.publishing.DeploymentAssemblyFilesetReferenceTest.testRootFolder 0.74 sec 10 >>> org.jboss.tools.as.test.core.parametized.server.publishing.DeploymentAssemblyFilesetReferenceTest.testRootFolderExcludeZ 0.75 sec 10 {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

4
9
0 / 0

[JBoss JIRA] (JBIDE-12732) jboss-packaging-maven-plugin jboss-sar + m2e + JBT = NPE

by Manosh C (JIRA)

Manosh C created JBIDE-12732: -------------------------------- Summary: jboss-packaging-maven-plugin jboss-sar + m2e + JBT = NPE Key: JBIDE-12732 URL: https://issues.jboss.org/browse/JBIDE-12732 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Environment: Eclipse Helios, indigo and Juno Reporter: Manosh C Assignee: Fred Bricon Not able to use maven SAR project inside eclipse (Tried Helios, indigo and even Juno with latest jboss tools dev build). In fact I have to close SAR project in order to add any other web/esb projects to JBoss EAP/ESB. I am also attaching the maven code to recreate the issue. One thing I observed is maven jboss packaging m2e plugin is not generating the eclipse files correctly for SAR. Contents of the "org.eclipse.wst.common.component", in .setting folder, is missing an attribute 'handle'(in this case it should be handle="module:/resource/test-common/test-common"). With out the "handle" attribute, i could not open "deployment Assembly" page in properties (right click on sar project -> properties -> Deployment Assembly). Once I have the handle defined i could open Deployment Assembly page and SAR project shows up in the list to add to the server. Here is the .settings/"org.eclipse.wst.common.component" file contents <?xml version="1.0" encoding="UTF-8"?> <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="test-sar"> <wb-resource deploy-path="/" source-path="/src/main/resources"/> <wb-resource deploy-path="/" source-path="/src/main/java"/> <wb-resource deploy-path="/" source-path="/src/test/java"/> <dependent-module archiveName="test-common-1.0-SNAPSHOT.jar" deploy-path="/lib"> <dependency-type>uses</dependency-type> </dependent-module> <property name="java-output-path" value="target/classes"/> </wb-module> </project-modules> Please let me know if you need any more details. -- 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
6
0 / 0

[JBoss JIRA] (JBIDE-12995) When converting a PDE plugin to Maven, dependencies should not be converted

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12995: ----------------------------------- Summary: When converting a PDE plugin to Maven, dependencies should not be converted Key: JBIDE-12995 URL: https://issues.jboss.org/browse/JBIDE-12995 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.0.0.Beta1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Beta2 With tycho's Manifest-first approach, converting classpath entries to maven dependencies is irrelevant for Eclipse plugins, thus the Dependency Conversion wizard should not be invoked. -- 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
2
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