June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19900) Installing only V3 feature results is limited capability, need to know to install V2

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19900?page=com.atlassian.jira.plugi... ] Jeff Cantrill resolved JBIDE-19900. ----------------------------------- Fix Version/s: 4.3.0.Beta1 Resolution: Done Moving to resolved unless someone finds out otherwise. > Installing only V3 feature results is limited capability, need to know to install V2 > ------------------------------------------------------------------------------------ > > Key: JBIDE-19900 > URL: https://issues.jboss.org/browse/JBIDE-19900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: eclipse.buildId=4.5.0.I20150522-2000 > org.jboss.tools.openshift.client (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > org.jboss.tools.openshift.common.core (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > org.jboss.tools.openshift.common.ui (3.0.0.Beta1-v20150528-1036-B807) "OpenShift Common UI" [Active] > org.jboss.tools.openshift.core (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > org.jboss.tools.openshift.egit.core (3.0.0.Beta1-v20150528-1036-B807) "OpenShift EGit Core" [Starting] > org.jboss.tools.openshift.egit.ui (3.0.0.Beta1-v20150528-1036-B807) "OpenShift EGit UI" [Starting] > org.jboss.tools.openshift.ui (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > Reporter: Steve Speicher > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: Screen Shot 2015-05-29 at 5.11.03 PM.png > > > If a user is interested in only V3, they are tempted to just install the V3 feature. The issue is that a number of things don't work, namely the "Create"/"New" paths. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19873) Usage Analytics New and Noteworthy for 4.3.0.Beta1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19873?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19873: -------------------------------------- Assignee: Konstantin Marmalyukov (was: Alexey Kazakov) There is nothing new besides JBIDE-19899 So, assigning the issue to [~kmarmaliykov] to add some information about the new event of browser usage in Central to the Usage N&N page. > Usage Analytics New and Noteworthy for 4.3.0.Beta1 > -------------------------------------------------- > > Key: JBIDE-19873 > URL: https://issues.jboss.org/browse/JBIDE-19873 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Usage Analytics is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Usage Analytics by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19900) Installing only V3 feature results is limited capability, need to know to install V2

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19900?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-19900: ------------------------------------- Assignee: Jeff Cantrill > Installing only V3 feature results is limited capability, need to know to install V2 > ------------------------------------------------------------------------------------ > > Key: JBIDE-19900 > URL: https://issues.jboss.org/browse/JBIDE-19900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: eclipse.buildId=4.5.0.I20150522-2000 > org.jboss.tools.openshift.client (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > org.jboss.tools.openshift.common.core (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > org.jboss.tools.openshift.common.ui (3.0.0.Beta1-v20150528-1036-B807) "OpenShift Common UI" [Active] > org.jboss.tools.openshift.core (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > org.jboss.tools.openshift.egit.core (3.0.0.Beta1-v20150528-1036-B807) "OpenShift EGit Core" [Starting] > org.jboss.tools.openshift.egit.ui (3.0.0.Beta1-v20150528-1036-B807) "OpenShift EGit UI" [Starting] > org.jboss.tools.openshift.ui (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > Reporter: Steve Speicher > Assignee: Jeff Cantrill > Attachments: Screen Shot 2015-05-29 at 5.11.03 PM.png > > > If a user is interested in only V3, they are tempted to just install the V3 feature. The issue is that a number of things don't work, namely the "Create"/"New" paths. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3450: ------------------------------------- It uses the same jvm that used to run installer through java.home system property. If installer started with direct path to java different from default JBDS might not start after installation. Name "Default" is not right until it is initialized through running actual default jvm as "java -version". Problem is running "java -version" might not always work as expected and requires additional logic. > installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3450 > URL: https://issues.jboss.org/browse/JBDS-3450 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Beta2 > > Attachments: jbds-installer_step4-jvm-selection.png > > > {quote} > (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min > (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS. > (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK) > (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine > (2015-06-02 16:39:02) joshuaw: was found after searching the following locations: > (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java > (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java? > (2015-06-02 16:39:40) joshuaw: let me check > 16:40 > (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it > (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :( > (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist? > (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file > (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update? > (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist > (2015-06-02 16:42:32) nickboldt: aha > (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8* > (2015-06-02 16:42:48) nickboldt: pwd > (2015-06-02 16:42:52) nickboldt: put that in your ini file > (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file > (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk > (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39 > (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39 > (2015-06-02 16:46:33) joshuaw: stupid minor minor version update > (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ? > (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file > (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion > (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini > (2015-06-02 17:55:27) nickboldt: -vm > (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java > (2015-06-02 17:55:36) maxandersen: thats bad > (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :( > (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ? > {quote} > It's possible the installer is using the CURRENT value of alternatives path for JDK... > {code} > $➔ alternatives --display java > java - status is manual. > link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071 > {code} > So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3450: ----------------------------------- Assignee: Denis Golovin (was: Nick Boldt) > installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3450 > URL: https://issues.jboss.org/browse/JBDS-3450 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > Attachments: jbds-installer_step4-jvm-selection.png > > > {quote} > (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min > (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS. > (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK) > (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine > (2015-06-02 16:39:02) joshuaw: was found after searching the following locations: > (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java > (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java? > (2015-06-02 16:39:40) joshuaw: let me check > 16:40 > (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it > (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :( > (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist? > (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file > (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update? > (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist > (2015-06-02 16:42:32) nickboldt: aha > (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8* > (2015-06-02 16:42:48) nickboldt: pwd > (2015-06-02 16:42:52) nickboldt: put that in your ini file > (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file > (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk > (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39 > (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39 > (2015-06-02 16:46:33) joshuaw: stupid minor minor version update > (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ? > (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file > (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion > (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini > (2015-06-02 17:55:27) nickboldt: -vm > (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java > (2015-06-02 17:55:36) maxandersen: thats bad > (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :( > (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ? > {quote} > It's possible the installer is using the CURRENT value of alternatives path for JDK... > {code} > $➔ alternatives --display java > java - status is manual. > link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071 > {code} > So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19801) Why is skipTestOrITest only defined for jbosstools-server/as/itests, but not wtp/itests/ ?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19801?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19801. --------------------------------- Resolution: Done Done > Why is skipTestOrITest only defined for jbosstools-server/as/itests, but not wtp/itests/ ? > ------------------------------------------------------------------------------------------ > > Key: JBIDE-19801 > URL: https://issues.jboss.org/browse/JBIDE-19801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > 3 questions: > a) why is the variable skipTestOrITest, and not skipTestsOrITests ? > b) why isn't it defined in your root pom such that it can be reused in other itests/ folders? I see skipITests being used in as/itests/ and wtp/itests/ but only as/itests is resolving the skipTestOrITest flag. > c) was there a JIRA to push this into the parent pom, too? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19801) Why is skipTestOrITest only defined for jbosstools-server/as/itests, but not wtp/itests/ ?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19801?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19801: ------------------------------------- https://github.com/jbosstools/jbosstools-devdoc/pull/46 > Why is skipTestOrITest only defined for jbosstools-server/as/itests, but not wtp/itests/ ? > ------------------------------------------------------------------------------------------ > > Key: JBIDE-19801 > URL: https://issues.jboss.org/browse/JBIDE-19801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > 3 questions: > a) why is the variable skipTestOrITest, and not skipTestsOrITests ? > b) why isn't it defined in your root pom such that it can be reused in other itests/ folders? I see skipITests being used in as/itests/ and wtp/itests/ but only as/itests is resolving the skipTestOrITest flag. > c) was there a JIRA to push this into the parent pom, too? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19867) CDI New and Noteworthy for 4.3.0.Beta1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19867?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19867. ---------------------------------- Resolution: Rejected No N&N for Beta1. > CDI New and Noteworthy for 4.3.0.Beta1 > -------------------------------------- > > Key: JBIDE-19867 > URL: https://issues.jboss.org/browse/JBIDE-19867 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If CDI is not listed here check if there are issues that should be added and add them. > Document the ones relevant for CDI by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-444) Update composites and meta data to JBTIS 4.2.2.CR3/ JBDSIS 8.0.2.CR3

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-444?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-444. ------------------------------ Fix Version/s: 4.2.2.CR3 Resolution: Done https://github.com/jbosstools/jbosstools-download.jboss.org/commit/cd65a8... > Update composites and meta data to JBTIS 4.2.2.CR3/ JBDSIS 8.0.2.CR3 > -------------------------------------------------------------------- > > Key: JBTIS-444 > URL: https://issues.jboss.org/browse/JBTIS-444 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.0.CR2 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.2.2.CR3 > > > Update release composites and related metadata to CR3 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19950) Fix publishing of integration-tests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19950?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19950: ------------------------------------ FYI to [~mickael_istria]: https://github.com/jbdevstudio/jbdevstudio-ci/commit/b8887e97fab4df71e5c1... (merge changes from master to 4.3.mars job) https://github.com/jbdevstudio/jbdevstudio-ci/commit/8dcce489c7ec41e1456f... (add -Djbosstools_site_stream=${jbosstools_site_stream} to mvn deploy calls) FYI to [~mmalina]]: https://github.com/jbdevstudio/jbdevstudio-ci/commit/2430d3e777972f4f4c57... (automate creation of Task JIRA to branch integration-tests) > Fix publishing of integration-tests > ----------------------------------- > > Key: JBIDE-19950 > URL: https://issues.jboss.org/browse/JBIDE-19950 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.0.Beta1 > > > {quote} > Lucia just built a new build of integration tests: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... > But this page only contains the older build: > http://download.jboss.org/jbosstools/updates/nightly/integrationtests/mas... > Whereas here you can see the latest build: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-int... > > So the question is: Why is the latest build missing from the nightly > update site? Is the new publishing mechanism not working correctly? > {quote} -- 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 June 2015