May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11685) Forge doesn't start on windows

by Koen Aers (JIRA)

Koen Aers created JBIDE-11685: --------------------------------- Summary: Forge doesn't start on windows Key: JBIDE-11685 URL: https://issues.jboss.org/browse/JBIDE-11685 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.Beta3 Since the layout change of the Forge embedded runtime plugin, Forge does not start anymore on Windows -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11801) something is looking for GWT 2.6, but 2.5.1 is on TP and composite reqs site

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11801: ---------------------------------- Summary: something is looking for GWT 2.6, but 2.5.1 is on TP and composite reqs site Key: JBIDE-11801 URL: https://issues.jboss.org/browse/JBIDE-11801 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: GWT, maven Affects Versions: 3.3.0.Beta3 Reporter: Nick Boldt Assignee: Denis Golovin Fix For: 3.3.0.Beta3 Any idea why the continuous build (cd ~/branches/jbosstools-3.3.0.Beta3/build; mvn clean install) thinks that it needs GWT 2.6 when we only have 2.5 in the TP and all the features/plugins I've checked either have NO version number requirement stated or want 2.5? {code} [INFO] Resolving dependencies of MavenProject: org.jboss.tools.maven.features:org.jboss.tools.maven.gwt.feature:1.3.0-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-3.3_stable_branch.continuous/sources/maven/features/org.jboss.tools.maven.gwt.feature/pom.xml [ERROR] Internal error: java.lang.RuntimeException: Could not download artifacts from any repository [ERROR] osgi.bundle,com.google.gdt.eclipse.platform,2.6.0.v201205021203-rel-r37 [ERROR] osgi.bundle,com.google.gdt.eclipse.core,2.6.0.v201205021203-rel-r37 [ERROR] osgi.bundle,com.google.gdt.eclipse.platform.e37,2.6.0.v201205021203-rel-r37 [ERROR] osgi.bundle,com.google.gdt.eclipse.platform.shared,2.6.0.v201205021203-rel-r37 [ERROR] osgi.bundle,com.google.gwt.eclipse.core,2.6.0.v201205021203-rel-r37 [ERROR] -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not download artifacts from any repository osgi.bundle,com.google.gdt.eclipse.platform,2.6.0.v201205021203-rel-r37 osgi.bundle,com.google.gdt.eclipse.core,2.6.0.v201205021203-rel-r37 osgi.bundle,com.google.gdt.eclipse.platform.e37,2.6.0.v201205021203-rel-r37 osgi.bundle,com.google.gdt.eclipse.platform.shared,2.6.0.v201205021203-rel-r37 osgi.bundle,com.google.gwt.eclipse.core,2.6.0.v201205021203-rel-r37 {code} http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_5.0.indig... -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] (JBIDE-11483) AS7 / EAP6 management port should be exposed via api rather than hard-coded for as71 jmx connection

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-11483: ----------------------------------- Summary: AS7 / EAP6 management port should be exposed via api rather than hard-coded for as71 jmx connection Key: JBIDE-11483 URL: https://issues.jboss.org/browse/JBIDE-11483 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers, jmx Affects Versions: 3.3.0.Beta3 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.Beta3 Currently in the jmx connection for as71 / eap6, the management port is hard-coded. This should make use of the management port stored in JBoss7Server. -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-10903) Deploy folder sometimes not added to JBoss deployment path list

by Daniel Atallah (JIRA)

Daniel Atallah created JBIDE-10903: -------------------------------------- Summary: Deploy folder sometimes not added to JBoss deployment path list Key: JBIDE-10903 URL: https://issues.jboss.org/browse/JBIDE-10903 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Environment: Windows 7 / Eclipse Indigo SR1 / JBoss 4.2.3 Reporter: Daniel Atallah Assignee: Rob Stryker A number of people in my team have run into intermittent issues where when the Server is started, the deploy folder that is specified in the Server "Deployment" tab doesn't seem to ever get added to the list of locations that JBoss looks for stuff to deploy. We're using a custom deploy folder (it's an ordinary directory on a local drive). The normal course of operations is that JBoss starts up successfully and outputs the following line: {noformat}19:41:06,117 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 15s:550ms{noformat} Then, if things work successfully, a few seconds later the following output appears and my EAR is deployed (my custom deploy folder is "C:/export/spare/Devl-JBoss/development/dev/deploy"): {noformat}19:41:14,948 INFO [EARDeployer] Init J2EE application: file:/C:/export/spare/Devl-JBoss/development/dev/deploy/Foo.ear/{noformat} If things don't work successfully, the second line never appears and the server just sits there without any of the deployed resources being available. Not being familiar with how the JBoss Tools integration works, it looks to me that JBoss Tools is somehow waiting for the Server to start up fully before adding the deploy folder and in the cases where it doesn't work, it never notices that the Server has started up so it never adds the deploy folder. I've tried setting the server logging to TRACE level and when it isn't working, the custom deploy folder doesn't appear anywhere in the log output. This issue is intermittent, I haven't been able to identify any specific scenarios under which it is triggered. When it does happen, sometimes restarting the server will resolve it, but other times we need to do a "Clean" publish to the server, and sometimes even that will not fix the issue (more than once deleted my workspace .metadata and started clean to get it working). -- 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, 10 months

4
11
0 / 0

[JBoss JIRA] (JBIDE-11785) jbosstools-3.3_stable_branch.continuous failing to compile -- java.lang.OutOfMemoryError: GC overhead limit exceeded

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11785: ---------------------------------- Summary: jbosstools-3.3_stable_branch.continuous failing to compile -- java.lang.OutOfMemoryError: GC overhead limit exceeded Key: JBIDE-11785 URL: https://issues.jboss.org/browse/JBIDE-11785 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng Affects Versions: 3.3.0.Beta3 Reporter: Nick Boldt Assignee: Mickael Istria Priority: Blocker Fix For: 3.3.0.Beta3 {code} [INFO] --- maven-resources-plugin:2.4.1:testResources (default-testResources) @ org.jboss.tools.seam220GA.core.test --- [INFO] Using 'ISO-8859-1' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /mnt/hudson_workspace/workspace/jbosstools-3.3_stable_branch.continuous/sources/seam/tests/org.jboss.tools.seam220GA.core.test/src/test/resources [INFO] [INFO] --- tycho-compiler-plugin:0.14.1:testCompile (default-testCompile) @ org.jboss.tools.seam220GA.core.test --- [ERROR] GC overhead limit exceeded -> [Help 1] java.lang.OutOfMemoryError: GC overhead limit exceeded {code} http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_5.0.indig... -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11414) Run on .java file should not result in .java url being opened

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11414: ------------------------------------------- Summary: Run on .java file should not result in .java url being opened Key: JBIDE-11414 URL: https://issues.jboss.org/browse/JBIDE-11414 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.Beta3 >From JBIDE-10218: Another example of Run not working. 1) Import the jboss-as-helloworld quickstart (listed on JBoss Central as HelloWorld) 2) Open the HelloService.java in the editor 3) Hit the green run button 4) It does deploy jboss-as-helloworld but loads the internal browser with http://localhost:8080/jboss-as-helloworld/WEB-INF/classes/org/jboss/as/qu... Both observed on Burr and Max's Beta1 installations. Need to find if this is us returning this since it makes no sense to run this .java as anything. only if it was a servlet should it return something runnable. I would expect it to fall back to run what was previously run in this case OR simply the project of the selection. -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-11501) JBoss AS 7.1. "Browse ..." for configuration file looks ugly under Windows 7

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-11501: ------------------------------------- Summary: JBoss AS 7.1. "Browse ..." for configuration file looks ugly under Windows 7 Key: JBIDE-11501 URL: https://issues.jboss.org/browse/JBIDE-11501 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta3 Reporter: Denis Golovin Assignee: Rob Stryker Priority: Minor -- 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, 10 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-10232) exploded deploy does not work on windows because of use of File#renameTo

by Jim Sellers (Created) (JIRA)

exploded deploy does not work on windows because of use of File#renameTo ------------------------------------------------------------------------ Key: JBIDE-10232 URL: https://issues.jboss.org/browse/JBIDE-10232 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Environment: JBossAS Tools: Version: 2.3.0.v20111104-1515-H45-M4 Java version: 1.5.0_22, vendor: Sun Microsystems Inc. Java home: C:\devtools\java\jdk1.5.0_22\jre Default locale: en_CA, platform encoding: Cp1252 OS name: "windows xp", version: "5.1", arch: "x86", family: "windows" Reporter: Jim Sellers Assignee: Rob Stryker Setup: in a project on windows with an ear / war / jar in an exploded format and having started the server in debug mode. If you make any changes to a file in the jar, the jar will be rebuilt and try to be deployed. This seems to work but it pops up an error dialog box *every time*. The error message looks like the following: {code} Error renaming C:\devtools\jboss\jboss-4.2.3.GA\server\default\tmp\jbosstoolsTemp\tmp2587902707203199490.jar to C:\devtools\jboss\jboss-4.2.3.GA\server\default\deploy\MyExampleEAR.ear\MyExampleWAR.war\WEB-INF\lib\MyDependantJar-2.3-SNAPSHOT.jar. This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. You may adjust these settings in the server editor. {code} For the method org.jboss.ide.eclipse.as.core.server.xpl.PublishCopyUtil#safeRename(File,File,int) it calls File#renameTo(File) for moving the file from the temp directory to WEB-INF/lib. From the javadocs for renameTo it says that this might not work if the file in the destination already exists. Possible fixes: # before calling the rename, try to delete on the destination file ( to.delete() ) # org.apache.commons.io.FileUtils#moveFile(File,File) tries to call the renameTo and if that fails it falls back to coping the file to the destination. {code:JAVA|title=Sample Unit test} /* This test needs to be run on windows. */ @Test public void testCopyForWindows() throws IOException { File from = File.createTempFile("source", ".txt"); File to = File.createTempFile("target", ".txt"); File[] files = {from, to}; for (File file : files) { // set for cleanup file.deleteOnExit(); assertTrue("file should exist" + file.getAbsolutePath(), file.exists()); assertTrue("file should be writable" + file.getAbsolutePath(), file.canWrite()); } // if safeRename was not private! assertTrue("should have been able to rename the file", safeRename(from, to, 10)); } {code} -- 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, 10 months

6
5
0 / 0

[JBoss JIRA] (JBIDE-11251) when associated project gets deleted the openshift server errors with NPE on publish

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11251: ------------------------------------------- Summary: when associated project gets deleted the openshift server errors with NPE on publish Key: JBIDE-11251 URL: https://issues.jboss.org/browse/JBIDE-11251 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.Beta2 its not an uncommon scenario to delete projects so the server adapter should be able to handle this. -- 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, 10 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-10218) Run button in toolbar needs to run the newly generated project

by Burr Sutter (Created) (JIRA)

Run button in toolbar needs to run the newly generated project -------------------------------------------------------------- Key: JBIDE-10218 URL: https://issues.jboss.org/browse/JBIDE-10218 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter The Run icon in the Eclipse toolbar is where a new developer (new to JBoss Tools) expects to go directly after he has generated a new project from either File-New or JBoss Central by using one of the archetypes or project examples/quickstarts. This means the generated project needs to be highlighted in the Project Explorer and the Run button should "just work". There is also an issue with Run vs Debug - if the server is in "debug mode" then Run should just assume that is OK and not prompt the user. Run on Server should be the default so the user can use a single click on OK -- 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, 10 months

10
19
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 2012