May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19754) Red Deer using very old target platforms from Eclipse 4.3 (Kepler)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19754?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-19754. ----------------------------------- Resolution: Rejected We never used these properties in the build so they have no effect. I assume one of your scripts added them there just like it does for every other master job in jenkins. But then perhaps at some point your script stopped updating this job's config? In any case, we don't rely on this, so it has zero effect. In fact out master pom uses Eclipse Luna update site directly. See https://github.com/jboss-reddeer/reddeer/blob/master/pom.xml#L14 : {code} <eclipse-target-site>http://download.eclipse.org/releases/luna</eclipse-target-site> {code} It is our goal to update this to Mars soon, but it's tracked elsewhere (I'm not in charge of it so I don't have a link to an issue tracker). > Red Deer using very old target platforms from Eclipse 4.3 (Kepler) > ------------------------------------------------------------------ > > Key: JBIDE-19754 > URL: https://issues.jboss.org/browse/JBIDE-19754 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Martin Malina > > Noticed today that the RedDeer master branch job, https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/RedDeer_master/ , uses TARGET_PLATFORM_VERSION = 4.30.6.Final and TARGET_PLATFORM_VERSION_MAXIMUM = 4.32.0.Final, which are from the JBoss Tools 4.1 (Eclipse 4.3 Kepler) days. > Shouldn't you be building with Eclipse 4.5 Mars, or at least Eclipse 4.4 Luna? > cc: [~mmalina] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19687) Web Service wizard buttons act strangely if an error occurs creating CXF service

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19687?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19687: --------------------------------------------- [~bfitzpat] does that error of empty namespace rings a bell for you ? > Web Service wizard buttons act strangely if an error occurs creating CXF service > -------------------------------------------------------------------------------- > > Key: JBIDE-19687 > URL: https://issues.jboss.org/browse/JBIDE-19687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 20 x64, openjdk 1.7.0_75 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > Attachments: errorMessage > > > Trying to create a bottom up Apache CXF web service. If after the "Apache CXF Wbe Service Java2WS Configuration" step an error occurs, the "back" and "next" buttons stop behaving in the expected fashion. > So far I've found these cases: > - The back button will loop through the last 3 pages of the wizard, while pressing "next" on any of these pages will return you to the first page. > - You can return with the back button, but pressing next will open an error dialog with the same message as the original error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19697: --------------------------------------- OK, so I went to the forums: http://www.eclipse.org/forums/index.php?t=thread&frm_id=287 And found your post asking how to skip it: https://www.eclipse.org/forums/index.php/t/991029/ It turns out that the property is slightly different, it's actually: -Doomph.setup.skip=true With this, the property file is no longer copied over to a new instance of Eclipse. And then I installed JBT nightly and restarted Eclipse and the prefs file is still not there and I was not asked to install any runtimes. So all is good. So the mystery is solved - we now know that it's Oomph doing this. Now what do we do? Just close this as won't fix? Fine with me. Or do we want to do anything about it? > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 4.3.0.Beta1 > > Attachments: preference-recorder.png > > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18542) NPE during "Check installation for Early Access"

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18542?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18542. ------------------------------ > NPE during "Check installation for Early Access" > ------------------------------------------------ > > Key: JBIDE-18542 > URL: https://issues.jboss.org/browse/JBIDE-18542 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR2 > Reporter: Rob Cernich > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > I got the following exception upon restart after updating to CR2 from the following site: http://download.jboss.org/jbosstools/updates/staging/luna/ > {noformat} > java.lang.NullPointerException > at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99) > at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79) > at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72) > at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:574) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Consider using main JBT site for server discovery

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19757: ---------------------------------------- Actually, the error while parsing the site.xml doesn't prevent to run a comparison, but it makes unclear which strategy discovery will use: * Time to discover AS adapter with the dedicated site ( http://download.jboss.org/jbosstools/updates/webtools/mars/ ): a bit less than 5 seconds * Time to discover AS adapter with the JBT site ( http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... , keeping site.xml so the old-style category is there): a bit less 5 seconds * Time to discovery AS adapter with the JBT site without site.xml (temporarily renamed remotely): a bit more than 5 seconds So overall, I believe dropping the webtools site and using directly the JBoss Tools one doesn't have a noticeable performance reduction that would reduce user experience. So +1 to drop webtools site then. > Consider using main JBT site for server discovery > ------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19735) Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)"

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19735?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-19735. ------------------------------ Verified in JBT 4.3.0.Alpha2. Closing. > Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19735 > URL: https://issues.jboss.org/browse/JBIDE-19735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 4.3.0.Alpha2 > > Attachments: jbosstools-diagnostics-20150428160436.zip > > > To recreate: > * Create from scratch a new AngularJS with Forge project. > * Have the project creation install AngularJS Eclipse > Observe this error reported in a dialog in the UI: > An error has occurred. See error log for more details. > invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > The full .log is in the attached diagnostic file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Consider using main JBT site for server discovery

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19757: ---------------------------------------- The site.xml prevents discovery from working with main JBT site, it's the blocking point before we can think about comparing performance. > Consider using main JBT site for server discovery > ------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19697: ---------------------------------------- Yes, skip=true. I advise you ask directly on the Oomph forum. > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 4.3.0.Beta1 > > Attachments: preference-recorder.png > > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Consider using main JBT site for server discovery

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19757: --------------------------------------------- I would put the site.xml question to a separate jira since that seem to be a general issue. about moving to main server discovery then the important part is the performance difference. Have you tested how it will behave with the simple site vs the composite one that is much larger ? > Consider using main JBT site for server discovery > ------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19327) Empty categories should be hidden

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19327?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-19327. ------------------------------ > Empty categories should be hidden > --------------------------------- > > Key: JBIDE-19327 > URL: https://issues.jboss.org/browse/JBIDE-19327 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Alpha1 > Reporter: Radim Hopp > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Currently in 4.3.0.Alpha1 there are few categories of examples defined (http://download.jboss.org/jbosstools/examples/4.3/project-examples-catego...), which are empty. For example "JBoss Quickstarts", "GateIn Portal Quickstarts" or "Portal Applications". > I think it would be nice not having empty categories shown in New Project Example wizard. > Another question is... We stopped shipping those examples, or is this a bug? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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