January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3583) Cannot start JBDS 9 with jdk 1.9 EA

by Martin Malina (JIRA)

Martin Malina created JBDS-3583: ----------------------------------- Summary: Cannot start JBDS 9 with jdk 1.9 EA Key: JBDS-3583 URL: https://issues.jboss.org/browse/JBDS-3583 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.Beta1 Reporter: Martin Malina Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 But even if I select jdk 1.8 in the installed and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). It just shows and error saying where to look for log. The log is linked here: https://issues.jboss.org/secure/attachment/12396824/1453206771791.log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3581) Installer does not allow Java 9 EA

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3581?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3581: ------------------------------------- OK, I created a new JIRA here: JBDS-3583 > Installer does not allow Java 9 EA > ---------------------------------- > > Key: JBDS-3581 > URL: https://issues.jboss.org/browse/JBDS-3581 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Environment: jdk build 9-ea+100-2016-01-06-195905 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > When I try to install using Java 9 EA I get the following on JRE selection screen: > "JBoss Developer Studio does not work with selected version of Java." > AFAIK JBDS 9 did work with Java 9 before, just with a warning. So I guess the version is not properly recognized. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21431) [OpenShift Explorer] Occasionally, ConnectionNotFoundExceptions are thrown

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21431?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21431. --------------------------------- Verified in nigthly build of JBDS with OpenShift tools plugin of version 3.1.0.Beta2-v20160119-1135-B153. > [OpenShift Explorer] Occasionally, ConnectionNotFoundExceptions are thrown > -------------------------------------------------------------------------- > > Key: JBIDE-21431 > URL: https://issues.jboss.org/browse/JBIDE-21431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.1.Beta2 > > > Occasionally, I haven't found a pattern yet, an exception is thrown when trying to access some of the resources in the openshift explorer. Simply click on a resource and boom : > {noformat} > org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named tac > at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41) > at org.jboss.tools.openshift.internal.core.WatchManager.startWatch(WatchManager.java:71) > at org.jboss.tools.openshift.internal.core.WatchManager.startWatch(WatchManager.java:66) > at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:187) > at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3581) Installer does not allow Java 9 EA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3581?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3581: -------------------------------------- [~mmalina], if you can't start (successfully installed) JBDS on JDK 1.9 then it's a different issue. Could you please create a separate JIRA for that? > Installer does not allow Java 9 EA > ---------------------------------- > > Key: JBDS-3581 > URL: https://issues.jboss.org/browse/JBDS-3581 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Environment: jdk build 9-ea+100-2016-01-06-195905 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > When I try to install using Java 9 EA I get the following on JRE selection screen: > "JBoss Developer Studio does not work with selected version of Java." > AFAIK JBDS 9 did work with Java 9 before, just with a warning. So I guess the version is not properly recognized. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-542) contents of http://download.jboss.org/jbosstools/mars/stable/updates/integration-stack/earlyaccess/ differ from github sources and contains invalid child site pointer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-542?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-542. ---------------------------- Resolution: Done I'll keep an eye out for this when I create 4.3.0.Beta1 in early Feb. > contents of http://download.jboss.org/jbosstools/mars/stable/updates/integration-stac... differ from github sources and contains invalid child site pointer > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-542 > URL: https://issues.jboss.org/browse/JBTIS-542 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > > Error logged in Eclipse when loading JBT update site: > {code}!MESSAGE No repository found at http://download.jboss.org/jbosstools/mars/stable/updates/integration-stac... > Reason: > I'm looking at http://download.jboss.org/jbosstools/mars/stable/updates/integration-stac... because the composite*.xml files attempt to reference the p2.index file instead of being an empty repo. This is what causes the error above. > {code} > <?xml version='1.0' encoding='UTF-8'?><?compositeArtifactRepository version='1.0.0'?> > <repository name='JBoss Tools Builds - updates/stable/mars/integration-stack/earlyaccess' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'> > <properties size='2'><property name='p2.timestamp' value='1450295308000'/><property name='p2.compressed' value='true'/></properties> > <children size='1'> > <child location='p2.index/'/> > </children> > </repository>{code} > But when I look at the sources in github [1], I see a completely different site. > Which is correct? Should the site be empty (no child sites), or should it ref 4.3.0.Alpha2 ? > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Also, how did this site get corrupted? Was it some automatic generation step? Or...? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3581) Installer does not allow Java 9 EA

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3581?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3581: ------------------------------------- BTW, [~jrichter1], did you try to work around this? I faced the same issue today, so I tried to install using JDK 1.8 and then changed jbdevstudio.ini to point to JDK 1.9 EA install, but it wouldn't start. Log is in JBDS-3582 or [here|https://issues.jboss.org/secure/attachment/12396824/1453206771791.log] > Installer does not allow Java 9 EA > ---------------------------------- > > Key: JBDS-3581 > URL: https://issues.jboss.org/browse/JBDS-3581 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Environment: jdk build 9-ea+100-2016-01-06-195905 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > When I try to install using Java 9 EA I get the following on JRE selection screen: > "JBoss Developer Studio does not work with selected version of Java." > AFAIK JBDS 9 did work with Java 9 before, just with a warning. So I guess the version is not properly recognized. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21368) jboss-runtimes are still not scanned under windows

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21368?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-21368. ------------------------------ Verified in JBDS 9.1.0.Beta2-v20160117-1428-B237. Closing. > jboss-runtimes are still not scanned under windows > -------------------------------------------------- > > Key: JBIDE-21368 > URL: https://issues.jboss.org/browse/JBIDE-21368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > JBDS-2515 requested that ~/jboss-runtimes would be scanned but seem to have ended up being to only add this on new workspaces and *only* if the location exist when creating the new workspace. > I found no way to have restore defaults or any way to actually have the scan happen. > Why are we not always adding ~/jboss-runtimes to the list of locations to scan no matter if the location exists or not ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-543) Add missing JBDS TP bits to JBDS IS update site zip

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-543?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-543: ---------------------------------- [~nickboldt] - we're you going to tweek the TP? We're getting close to finalizing the 4.3.1.Beta1 TP. > Add missing JBDS TP bits to JBDS IS update site zip > --------------------------------------------------- > > Key: JBTIS-543 > URL: https://issues.jboss.org/browse/JBTIS-543 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha1 > Environment: Customer Support Portal > Reporter: Mustafa Musaji > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip. > This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-543) Add missing JBDS TP bits to JBDS IS update site zip

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-543?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-543: ----------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha1) > Add missing JBDS TP bits to JBDS IS update site zip > --------------------------------------------------- > > Key: JBTIS-543 > URL: https://issues.jboss.org/browse/JBTIS-543 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha1 > Environment: Customer Support Portal > Reporter: Mustafa Musaji > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip. > This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-471) Unify component versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-471 at 1/19/16 10:56 AM: ------------------------------------------------------------ Either it's an identical rebuild that just adds the suffix, or he forgot to upversion to 1.0.6. Looks like the master branch is 1.0.6.qualifier / 1.0.6-SNAPSHOT (for neon, and JDK 8) [0], while the mars branch is at 1.0.5.qualifier / 1.0.5-SNAPSHOT (requires JDK 6) [1]. [0] http://git.eclipse.org/c/bpel/org.eclipse.bpel.git/commit/?id=43aa3f65772... [1] http://git.eclipse.org/c/bpel/org.eclipse.bpel.git/log/?h=mars Unclear from the commit log [1] whether the stuff in the mars branch should be at 1.0.6 and master at 1.1.0, or if the commits in mars branch are irrelevant, and the old 1.0.5.Final was really just a pre-Final, with this new build being "more close to Final". was (Author: nickboldt): Either it's an identical rebuild that just adds the suffix, or he forgot to upversion to 1.0.6. Looks like the master branch is 1.0.6.qualifier / 1.0.6-SNAPSHOT (for neon, and JDK 8) [1], while the mars branch is at 1.0.5.qualifier / 1.0.5-SNAPSHO (requires JDK 6) [0]. http://git.eclipse.org/c/bpel/org.eclipse.bpel.git/commit/?id=43aa3f65772... http://git.eclipse.org/c/bpel/org.eclipse.bpel.git/log/?h=mars Unclear from the commit log whether the stuff in the mars branch should be at 1.0.6 and master at 1.1.0, or if the commits in mars branch are irrelevant, and the old 1.0.5.Final was really just a pre-Final, with this new build being "more close to Final". > Unify component versions > ------------------------ > > Key: JBTIS-471 > URL: https://issues.jboss.org/browse/JBTIS-471 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Attachments: junit4.8vs4.12.png > > > Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as > BPMN2 1.1.3.Final > Fuse 7.3.1.v20150728-1330-H54-Final > Teiid Designer 9.0.3.Final-v20150728-2029-B1148 > I suggest to use the format used by Teiid Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 January 2016