October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13180) Improve Error Handling When Specifying VM Arguments For Forge

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13180?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13180: ----------------------------------- With Forge 2 around the corner and the start of phasing out the Forge 1 integration, this bug is not going to be fixed. I'll resolve it as "Won't Fix". > Improve Error Handling When Specifying VM Arguments For Forge > ------------------------------------------------------------- > > Key: JBIDE-13180 > URL: https://issues.jboss.org/browse/JBIDE-13180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Koen Aers > Assignee: Koen Aers > > When specifying erroneously arguments like "-Xmx=512m" the VM halts. The error message is not properly forwarded to the user leaving him in doubt as to what has happened. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2787) prepare for JBDS 7.0.1 patch release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2787?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2787 at 10/9/13 11:59 AM: ------------------------------------------------------------ TODO: Probably want to update these pages: https://www.jboss.org/tools/download/stable/4_1 https://www.jboss.org/tools/download/dev/4_1_x with a note about: {quote} The createTempFile issue has been fixed in Java 8 and is set to be included in Java 7 update 45: https://bugs.openjdk.java.net/browse/JDK-8025128 and the Backports section. Recommendation is to use a version of Oracle JDK 7 up to and including 1.7.0_39 or 1.7.0_45 and after. {quote} Matching Oracle issue: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8025128 (same ID number) was (Author: nickboldt): TODO: Probably want to update these pages: https://www.jboss.org/tools/download/stable/4_1 https://www.jboss.org/tools/download/dev/4_1_x with a note about: {quote} The createTempFile issue has been fixed in Java 8 and is set to be included in Java 7 update 45: https://bugs.openjdk.java.net/browse/JDK-8025128 and the Backports section. Recommendation is to use a version of Oracle JDK 7 up to and including 1.7.0_39 or 1.7.0_45 and after. {quote} > prepare for JBDS 7.0.1 patch release > ------------------------------------ > > Key: JBDS-2787 > URL: https://issues.jboss.org/browse/JBDS-2787 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.1.GA > > Attachments: 15509_JBDS701.CR1.png, 15509_JBT4101.CR1.png, jbds701ga-updates-avail.png, note-jdk7u40.png > > > Placeholder JIRA to contain work needed to do to release JBDS 7.0.1.GA: > 1. branch jbosstools-central from 4.1.x to 4.1.0.x > 2. adjust jbosstools-central/site/category.xml so it only contains the affected features (and feature.sources) > 3. build Central using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_410/ which gets its sources from the correct fork/branch > 4. create new composite staging site containing the last stable release + the new staging site for jbosstools-central, eg., > http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... > 5. branch jbdevstudio-product from 4.1.x to 4.1.0.x > 6. ensure that JBDS sources are correctly versioned (eg., 7.0.1 not 7.1.0) > 7. build JBDS using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_70/ which sets -DBUILD_ALIAS=GA, pulls from the correct branch origin/jbosstools-4.1.0.x, and sets these overrides in the maven configuration: > {code} > jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools... > jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c... > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13192) pick-up new project automatically after creation

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13192?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13192: ----------------------------------- With Forge 2 around the corner and the start of phasing out the Forge 1 integration, I am going to reject this feature request. > pick-up new project automatically after creation > ------------------------------------------------ > > Key: JBIDE-13192 > URL: https://issues.jboss.org/browse/JBIDE-13192 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.0.0.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13192) pick-up new project automatically after creation

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13192?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13192. ------------------------------- Resolution: Rejected > pick-up new project automatically after creation > ------------------------------------------------ > > Key: JBIDE-13192 > URL: https://issues.jboss.org/browse/JBIDE-13192 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.0.0.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13192) pick-up new project automatically after creation

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13192?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13192: ------------------------------ Fix Version/s: (was: 4.0.x) > pick-up new project automatically after creation > ------------------------------------------------ > > Key: JBIDE-13192 > URL: https://issues.jboss.org/browse/JBIDE-13192 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.0.0.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13637) 'Go to Selection' command throws error

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13637?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13637: ------------------------------ Fix Version/s: (was: 4.0.x) > 'Go to Selection' command throws error > -------------------------------------- > > Key: JBIDE-13637 > URL: https://issues.jboss.org/browse/JBIDE-13637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.x > > > When clicked on 'Go to Selection' button in Forge view the selected resource in Project Explorer should be picked-up in forge console. But what I get is: ***ERROR*** No such command. This happens only when using the command for the first time, all the following attempts to use that command are working. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13637) 'Go to Selection' command throws error

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13637?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13637: ----------------------------------- Can you give me an exact sequence to follow to reproduce this? I cannot reproduce it here on my machine. > 'Go to Selection' command throws error > -------------------------------------- > > Key: JBIDE-13637 > URL: https://issues.jboss.org/browse/JBIDE-13637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.x > > > When clicked on 'Go to Selection' button in Forge view the selected resource in Project Explorer should be picked-up in forge console. But what I get is: ***ERROR*** No such command. This happens only when using the command for the first time, all the following attempts to use that command are working. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13194) Ask user to restart forge after changing VM arguments

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13194?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13194: ----------------------------------- With Forge 2 around the corner, this feature request for the Forge 1 integration is not needed anymore. I'm going to resolve it as "Won't Fix". > Ask user to restart forge after changing VM arguments > ------------------------------------------------------ > > Key: JBIDE-13194 > URL: https://issues.jboss.org/browse/JBIDE-13194 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.0.0.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.0.x > > > It could be useful to ask user to restart forge when VM arguments are changed or debug mode is switched on/off in preferences. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13194) Ask user to restart forge after changing VM arguments

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13194?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13194. ------------------------------- Resolution: Won't Fix > Ask user to restart forge after changing VM arguments > ------------------------------------------------------ > > Key: JBIDE-13194 > URL: https://issues.jboss.org/browse/JBIDE-13194 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.0.0.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.0.x > > > It could be useful to ask user to restart forge when VM arguments are changed or debug mode is switched on/off in preferences. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13165) Forge Launches are not Correctly Removed

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13165?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13165. ------------------------------- Resolution: Out of Date > Forge Launches are not Correctly Removed > ---------------------------------------- > > Key: JBIDE-13165 > URL: https://issues.jboss.org/browse/JBIDE-13165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.CR1 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Minor > > * Start Forge in a new workspace > * Stop Forge > * Start Forge again > => 2 errors in Error View > This is the stack trace: > java.lang.NullPointerException > at org.jboss.tools.forge.core.process.ForgeLaunchHelper$ForgeLaunchListener.launchRemoved(ForgeLaunchHelper.java:184) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:443) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:428) > at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1017) > at org.eclipse.debug.internal.core.LaunchManager.removeLaunch(LaunchManager.java:2224) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.removeTerminatedLaunches(LaunchConfigurationManager.java:329) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.launchAdded(LaunchConfigurationManager.java:315) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:440) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:428) > at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1017) > at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:688) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:844) > at org.jboss.tools.forge.core.process.ForgeLaunchHelper.doLaunch(ForgeLaunchHelper.java:69) > at org.jboss.tools.forge.core.process.ForgeLaunchHelper.launch(ForgeLaunchHelper.java:53) > at org.jboss.tools.forge.core.process.ForgeAbstractRuntime.start(ForgeAbstractRuntime.java:50) > at org.jboss.tools.forge.ui.util.ForgeHelper$1.run(ForgeHelper.java:41) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- 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

12 years, 6 months

1
0
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 October 2013