May 2015 - jbosstools-issues - Jboss List Archives

[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'm not sure how to say it more clear. It is exactly what this fix does and it is exactly what Mickael tested. Notice: "then removed site.xml on the remote site and tried again". This will only work from Mars M7 and onward I believe. > 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-19711) WTP servertools integration with CDT launchbar

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19711: --------------------------------------------- Will it list the wtp servers dynamically so if I add or delete servers it will just automatically keep the list uptodate or does it require us to listen for add/remove/rename of servers to keep the list correct ? > 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Martin Malina edited comment on JBDS-3411 at 5/7/15 5:43 AM: ------------------------------------------------------------- [~maxandersen], I read this somewhere also (perhaps in some eclipse docs/bugzilla) that on OS X you should use the Info.plist file. But in fact the ini has always worked in the past on OS X and it still does now. I think we never did anything with the Info.plist during installation. How did I start JBDS? By double-clicking the jbdevstudio.app symlink inside the installation folder. I was curious which one takes precedence if you set -vm in both. So I checked. It turns out Info.plist has higher priority over jbdevstudio.ini - when you use both, the JDK set in the plist will be used to run JBDS. was (Author: mmalina): [~maxandersen], I read this somewhere also (perhaps in some eclipse docs/bugzilla) that on OS X you should use the Info.plist file. But in fact the ini has always worked in the past on OS X and it still does now. I think we never did anything with the Info.plist during installation. How did I start JBDS? By double-clicking the jbdevstudio.app symlink inside the installation folder. > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3411: ------------------------------------- [~maxandersen], I read this somewhere also (perhaps in some eclipse docs/bugzilla) that on OS X you should use the Info.plist file. But in fact the ini has always worked in the past on OS X and it still does now. I think we never did anything with the Info.plist during installation. How did I start JBDS? By double-clicking the jbdevstudio.app symlink inside the installation folder. > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3411: ------------------------------------------- note, to be clear I think the .ini file should be modifed equally on windows/linux and osx. Just wondered by your are seeing osx honoring .ini file. > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3411: ------------------------------------------- hmm - OSX shouldn't be listening to jbdevstudio.ini for vm but uses the info.plist ... at least when running the jbdevstudio.app. How did you run it ? via jbdevstudio.app or the embedded eclipse inside ? > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19773) Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19773?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19773: ---------------------------------------- Fix Version/s: 4.3.0.Beta1 Priority: Critical (was: Major) > Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do? > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19773 > URL: https://issues.jboss.org/browse/JBIDE-19773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Priority: Critical > Fix For: 4.3.0.Beta1 > > > It was suggested today on build.next call by Max that it would be great if when gtk/swt/browser/webkit problems occur as a result of Central loading that we could notify the user what when wrong and suggest a solution. > Context: > {quote} > * No more handles with install-grinder https://issues.jboss.org/browse/JBIDE-19750 and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... > * SWT problem? GTK problem? xvnc/xvfb problem? > * missing webkit package on RHEL7 ? > * @mickael to ping Fred; see what is missing on RHEL7 (need GTK3 packages) > * what about x86 bundles for x86_64 platform? - https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_... {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14609) server adapter wizard: does not switch output directory when I switch app (type)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14609?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-14609. --------------------------------- > server adapter wizard: does not switch output directory when I switch app (type) > -------------------------------------------------------------------------------- > > Key: JBIDE-14609 > URL: https://issues.jboss.org/browse/JBIDE-14609 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13708) openshift-java-client: make sure is not affected by REST response without Reason phrase

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13708?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-13708. --------------------------------- > openshift-java-client: make sure is not affected by REST response without Reason phrase > --------------------------------------------------------------------------------------- > > Key: JBIDE-13708 > URL: https://issues.jboss.org/browse/JBIDE-13708 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > the latest OpenShift REST service is apparently responding without reason phrase: > It will respond with *"HTTP/1.1 200 "* and ommit the reason phrase it usually reported before *"HTTP/1.1 200 OK"*. According to RFC 1945 a server doesn't have to give a reason phrase. The reason phrase is optional:http://www.w3.org/Protocols/rfc1945/rfc1945 / Section 6.1.1. > This issue is filed in the OpeShift bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=913796 > We have to make sure openshift-java-client can deal with it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13660) openshift-java-client: clean up ApplicationResource class

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13660?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-13660. --------------------------------- > openshift-java-client: clean up ApplicationResource class > --------------------------------------------------------- > > Key: JBIDE-13660 > URL: https://issues.jboss.org/browse/JBIDE-13660 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > In the ApplicationResource class there's a private sax parser class that noone uses. It should get removed. -- 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