May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19542) Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19542?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19542. ------------------------------- Verified with JBT 4.3.0-Beta1-v20150527-0620-B9985 > Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19542 > URL: https://issues.jboss.org/browse/JBIDE-19542 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.3.Final > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Steps to recreate the error: > * Install Eclipse (eclipse-jee-luna-SR2-linux-gtk-x86_64.tar.gz) > * Configure JBoss Tools as an update site (http://download.jboss.org/jbosstools/updates/staging/luna/) > * Install JBoss Tools Common - Mylyn (3.6.2.Final-v20150325-0456-B99, org.jboss.tools.common.mylyn.feature.feature.group) > * Whenever eclipse is started, this error is written to the .log > ============================================================================ > cat .log > !SESSION 2015-03-31 14:33:50.481 ----------------------------------------------- > eclipse.buildId=4.4.2.M20150204-1700 > java.version=1.7.0_55 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product > !ENTRY org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231 > !MESSAGE Unexpected error while loading repository template extensions > !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231 > !MESSAGE Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira' > ============================================================================ > Workaround: > * From JBoss Central, install: "Mylyn Issue Tracker Connectors" > * This results in the following packages being installed > * Mylyn Commons 3.14.2.v20150217-2244 org.eclipse.mylyn.commons.feature.group > * Mylyn Context Connector: Eclipse IDE 3.14.2.v20150218-0125 org.eclipse.mylyn.ide_feature.feature.group > * Mylyn Context Connector: Java Development 3.14.2.v20150218-0125 org.eclipse.mylyn.java_feature.feature.group > * Mylyn Context Connector: Plug-in Development 3.14.2.v20150218-0125 org.eclipse.mylyn.pde_feature.feature.group > * Mylyn Context Connector: Team Support 3.14.2.v20150218-0125 org.eclipse.mylyn.team_feature.feature.group > * Mylyn Task List 3.14.2.v20150217-2341 org.eclipse.mylyn_feature.feature.group > * Mylyn Task-Focused Interface 3.14.2.v20150218-0125 org.eclipse.mylyn.context_feature.feature.group > * Mylyn Tasks Connector: Bugzilla 3.14.2.v20150217-2341 org.eclipse.mylyn.bugzilla_feature.feature.group > * Mylyn Versions 1.6.2.v20150217-2249 org.eclipse.mylyn.versions.feature.group > After installing this^, the error is not generated -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19852) Set default path for runtimes downloaded and installed via java -jar

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19852?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19852: ------------------------------------- > if the user changes the installation path in the installer, it would be nice if the tooling noticed this and still added the right path. I've also looked into this... the problem is that the installation log (the only logical place I could get the installed location) is... ... .. IN the folder it was installed into. Therefore I'd need to know the install folder to find the installation log to find the install folder ;) Clearly doesn't work. > Set default path for runtimes downloaded and installed via java -jar > -------------------------------------------------------------------- > > Key: JBIDE-19852 > URL: https://issues.jboss.org/browse/JBIDE-19852 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > > I'm not sure if this is possible, but it would be nice if the installer would fill the installation path from Download Runtime wizard. > The same for runtime detection after the download and installation is finished. > Example scenario: > 1. Select JBoss DV 6.1 for download&installation > 2. On "Download Runtime" page of wizard fill some install folder (for example /home/<user>/downloadedDV) > 3. Click Finish - DV is downloaded and it's installer executed > ASSERT: /home/<user>/downloadedDV is default installation path in installer > 4. In the installer select different installation folder (for example /home/<user>/DV) > 5. Finish installer > ASSERT: /home/<user>/DV is added to runtime-detection paths instead of /home/<user>/downloadedDV -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19711: ------------------------------------- It's in SR1. The plugins are also in M7... the problem is the API changed a lot over the past few weeks, so the code I have does not work with what's in M7. > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-19711.png > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. > Relevant bugzillas upstream: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466786 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466660 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466658 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466490 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466489 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466488 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19834) Change Base's Bundle-RequireExecutionEnvironment to require Java8 (not 7)

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19834?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-19834: ------------------------------------- Verified with JBT 4.3.0-Beta1-v20150527-0620-B9985 > Change Base's Bundle-RequireExecutionEnvironment to require Java8 (not 7) > ------------------------------------------------------------------------- > > Key: JBIDE-19834 > URL: https://issues.jboss.org/browse/JBIDE-19834 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > > To support new target platform (JBIDE-19776) which includes new Sapphire, here's a new proposal to update JBDS 9 / JBT 4.3 to require JDK 8 runtime. > {quote} > Proposal support matrix: > * IDE installer will run wtih Java 6+ (but then user needs 8 to run it) [NO CHANGE] > * IDE will ONLY run on Java 8+ [NEW for JBDS 9] > * Server runtimes will run on existing JREs (from 4 - 9) [NO CHANGE] > * QE actually does not test on 4 or 5, only 6+ > * Java 9 is "preview / smoketest" only, not supported yet > {quote} > To force users to use a JDK 8 runtime to run Eclipse Mars / JBDS 9, we need to change the Base component's Bundle-RequireExecutionEnvironment to require Java8 (not 7). > Not sure how many plugins should be updated this way. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19834) Change Base's Bundle-RequireExecutionEnvironment to require Java8 (not 7)

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19834?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19834. ------------------------------- > Change Base's Bundle-RequireExecutionEnvironment to require Java8 (not 7) > ------------------------------------------------------------------------- > > Key: JBIDE-19834 > URL: https://issues.jboss.org/browse/JBIDE-19834 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > > To support new target platform (JBIDE-19776) which includes new Sapphire, here's a new proposal to update JBDS 9 / JBT 4.3 to require JDK 8 runtime. > {quote} > Proposal support matrix: > * IDE installer will run wtih Java 6+ (but then user needs 8 to run it) [NO CHANGE] > * IDE will ONLY run on Java 8+ [NEW for JBDS 9] > * Server runtimes will run on existing JREs (from 4 - 9) [NO CHANGE] > * QE actually does not test on 4 or 5, only 6+ > * Java 9 is "preview / smoketest" only, not supported yet > {quote} > To force users to use a JDK 8 runtime to run Eclipse Mars / JBDS 9, we need to change the Base component's Bundle-RequireExecutionEnvironment to require Java8 (not 7). > Not sure how many plugins should be updated this way. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19602) "Warning: NLS unused message" in org.jboss.tools.common.jdt.debug

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19602?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19602. ------------------------------- Verified > "Warning: NLS unused message" in org.jboss.tools.common.jdt.debug > ----------------------------------------------------------------- > > Key: JBIDE-19602 > URL: https://issues.jboss.org/browse/JBIDE-19602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > {code}Warning: NLS unused message: updatePeriodNotEnteredMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: illegalUpdatePeriodMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: updatePeriodOutOfRangeMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: loadAgentFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: agentJarNotFoundMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: agentJarFoundMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: corePluginNoFoundMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: charsetNotSupportedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: readInputStreamFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: updateTimerCanceledMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: getMonitoredJvmFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: getLocalConnectorAddressFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: connectTargetJvmFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: fileNotFoundMsg in: org.jboss.tools.common.jdt.debug.messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19689) Add isWarning to JobUtils

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19689?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19689. ------------------------------- Verified on Jenkins added tests passed > Add isWarning to JobUtils > ------------------------- > > Key: JBIDE-19689 > URL: https://issues.jboss.org/browse/JBIDE-19689 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19852) Set default path for runtimes downloaded and installed via java -jar

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19852?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19852: --------------------------------------- Max suggested this: {quote} B) if the installer is a izpack based installer there might be ways to do it already: http://docs.codehaus.org/display/IZPACK/Unattended+Installations Try with java -DINSTALL_PATH=/opt/myplace -jar myinstaller.jar to see if that works ? {quote} I tried it and it didn't work anywhere. Encouraged by Max, I created these issues :) JBDS-3446 for JBDS (although we're not gonna install JBDS from within JBDS, it may still be a good thing to have there) https://bugzilla.redhat.com/show_bug.cgi?id=1225450 for JBoss DV https://bugzilla.redhat.com/show_bug.cgi?id=1225457 for JBoss FSW > Set default path for runtimes downloaded and installed via java -jar > -------------------------------------------------------------------- > > Key: JBIDE-19852 > URL: https://issues.jboss.org/browse/JBIDE-19852 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > > I'm not sure if this is possible, but it would be nice if the installer would fill the installation path from Download Runtime wizard. > The same for runtime detection after the download and installation is finished. > Example scenario: > 1. Select JBoss DV 6.1 for download&installation > 2. On "Download Runtime" page of wizard fill some install folder (for example /home/<user>/downloadedDV) > 3. Click Finish - DV is downloaded and it's installer executed > ASSERT: /home/<user>/downloadedDV is default installation path in installer > 4. In the installer select different installation folder (for example /home/<user>/DV) > 5. Finish installer > ASSERT: /home/<user>/DV is added to runtime-detection paths instead of /home/<user>/downloadedDV -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19852) Set default path for runtimes downloaded and installed via java -jar

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19852?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated JBIDE-19852: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1225450, https://bugzilla.redhat.com/show_bug.cgi?id=1225457 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1225450) > Set default path for runtimes downloaded and installed via java -jar > -------------------------------------------------------------------- > > Key: JBIDE-19852 > URL: https://issues.jboss.org/browse/JBIDE-19852 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > > I'm not sure if this is possible, but it would be nice if the installer would fill the installation path from Download Runtime wizard. > The same for runtime detection after the download and installation is finished. > Example scenario: > 1. Select JBoss DV 6.1 for download&installation > 2. On "Download Runtime" page of wizard fill some install folder (for example /home/<user>/downloadedDV) > 3. Click Finish - DV is downloaded and it's installer executed > ASSERT: /home/<user>/downloadedDV is default installation path in installer > 4. In the installer select different installation folder (for example /home/<user>/DV) > 5. Finish installer > ASSERT: /home/<user>/DV is added to runtime-detection paths instead of /home/<user>/downloadedDV -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-18837: ------------------------------------- Please provide steps to verify this issue > because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18837 > URL: https://issues.jboss.org/browse/JBIDE-18837 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, central, common/jst/core, project-examples > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > Attachments: generated-vs-soource-zip.png > > > When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. > Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating. > And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 May 2015