March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13599: --------------------------------------- {quote} Yes, but i'm looking for feedback/comments on it. Does it look ok to you ? We do need to add/check the proper error handling in the UI in case of exceptions. {quote} It looks OK for me. I have tried the tests and they all passed. If you merge the PR, I will add te proper error handling to the UI. > externalize Central site URL into a commandline property so that testing or mirroring is easier > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-13599 > URL: https://issues.jboss.org/browse/JBIDE-13599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE. > A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. > This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13761) openshift-java-client: remove IUser#getAuthKey and IUser#getAuthIV

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13761: ---------------------------------------- Summary: openshift-java-client: remove IUser#getAuthKey and IUser#getAuthIV Key: JBIDE-13761 URL: https://issues.jboss.org/browse/JBIDE-13761 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.0.Alpha2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.0.Alpha2 In UserResource/IUser there are still #getAuthIV #getAuthKey methods that we inherited from the legacy client. They're currently not implement and return <code>null</code>. In the new client the auth keys are passed over to the http client via connection builder. They're not handled by the user any more. {code:title=com.openshift.client.OpenShiftConnectionFactory} final IHttpClient httpClient = new UrlConnectionHttpClientBuilder().setCredentials(login, password, authKey, authIV) .client(); {code} We should simply get rid of them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13736) TP should Support Servlet 3 and Jetty 8

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13736?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13736: ---------------------------------------- Mirror site created: * https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7c3de3... * http://download.jboss.org/jbosstools/updates/requirements/jetty/8.1.9.v20... TP updated: * https://github.com/jbosstools/jbosstools-target-platforms/commit/7896f16b... * Build https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... You can use this TP in IDE by making getting latest version and "reloading" it. When TP jobs are ready, you can consume at build-time by setting -DTARGET_PLATFORM_VERSION=4.30.5.Alpha2-SNAPSHOT > TP should Support Servlet 3 and Jetty 8 > --------------------------------------- > > Key: JBIDE-13736 > URL: https://issues.jboss.org/browse/JBIDE-13736 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > The org.eclipse.jetty.websocket bundle is required by the upcoming livereload tooling (will be certainly part of the VPE component) > Also, older version of Jetty should be removed from TP if they're not useful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-3628) Plugins should be .jar's not directories for efficiency sake

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3628?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen reassigned JBIDE-3628: ------------------------------------------ Assignee: Rob Stryker (was: Denis Golovin) Seems the last question from Denis means this is for Rob. > Plugins should be .jar's not directories for efficiency sake > ------------------------------------------------------------ > > Key: JBIDE-3628 > URL: https://issues.jboss.org/browse/JBIDE-3628 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.x > > Attachments: exception.log > > > 65 of our plugins are bundled exploded instead of a .jar > Some are probably just mistakes and can easily be packed others are because of legacy code assuming it can access the files directly and even store data in the plugins - that should be fixed. > What should be fixed: > 1. The way how plug-ins use images in plugin.xml, in java code and in .meta xmodel files > 2. Plug-ins that loads resources should be aware that they are in jar now (VPE should be able to load templates from plugin jar files) > 3. Some plug-ins contain resources registered in XML catalog > 4. common.projecttemplates contains resources that is used as template for new projects > 5. TBD -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13599: --------------------------------------------- Yes, but i'm looking for feedback/comments on it. Does it look ok to you ? We do need to add/check the proper error handling in the UI in case of exceptions. > externalize Central site URL into a commandline property so that testing or mirroring is easier > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-13599 > URL: https://issues.jboss.org/browse/JBIDE-13599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE. > A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. > This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13712) TP should not contain old org.mortbay.jetty plugins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13712?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13712: ----------------------------------- Component/s: target-platform (was: Build/Releng) > TP should not contain old org.mortbay.jetty plugins > ---------------------------------------------------- > > Key: JBIDE-13712 > URL: https://issues.jboss.org/browse/JBIDE-13712 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.0.0.Final > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > I'm hitting a problem where a plugin I'm working on cannot be loaded at startup. > {code} > ENTRY org.eclipse.osgi 2 0 2013-03-05 09:17:56.748 > !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists: > !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.748 > !MESSAGE Bundle com.google.gdt.eclipse.platform.e42_3.1.3.v201212122042-rel-r42 [46] was not resolved. > !SUBENTRY 2 com.google.gdt.eclipse.platform.e42 2 0 2013-03-05 09:17:56.749 > !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.servlet; bundle-version="0.0.0" > !SUBENTRY 2 com.google.gdt.eclipse.platform.e42 2 0 2013-03-05 09:17:56.749 > !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.server; bundle-version="0.0.0" > !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.749 > !MESSAGE Bundle org.eclipse.equinox.http.servletbridge_1.0.300.v20120912-125810 [477] was not resolved. > !SUBENTRY 2 org.eclipse.equinox.http.servletbridge 2 0 2013-03-05 09:17:56.750 > !MESSAGE Missing imported package org.eclipse.equinox.servletbridge_1.0.0. > !SUBENTRY 2 org.eclipse.equinox.http.servletbridge 2 0 2013-03-05 09:17:56.750 > !MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(|(&(osgi.ee=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))". > !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.750 > !MESSAGE Bundle org.eclipse.wst.server.preview_1.1.102.v20130123_1813 [949] was not resolved. > !SUBENTRY 2 org.eclipse.wst.server.preview 2 0 2013-03-05 09:17:56.751 > !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.server; bundle-version="[8.0.4,9.0.0)" > !SUBENTRY 2 org.eclipse.wst.server.preview 2 0 2013-03-05 09:17:56.751 > !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.servlet; bundle-version="[8.0.4,9.0.0)" > !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.751 > !MESSAGE Bundle org.jboss.tools.web.pagereloader_1.0.0.qualifier [1101] was not resolved. > !SUBENTRY 2 org.jboss.tools.web.pagereloader 2 0 2013-03-05 09:17:56.751 > !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.continuation; bundle-version="8.1.3" > {code} > After a bit of investigation, I managed get it started by removing the old org.mortbay.jetty plugins from the TP of the runtime workbench > Furthermore, Max found this: http://www.eclipse.org/eclipse/development/porting/4.2/incompatibilities.... > BUT > Attlassian Connector v3.0.7 depends on the org.mortbay.jetty bundles, and they have an open issue to migrate to the recommended org.eclipse.jetty bundles: https://ecosystem.atlassian.net/browse/PLE-1405 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13736) TP should Support Servlet 3 and Jetty 8

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13736?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13736: ----------------------------------- Component/s: target-platform (was: Build/Releng) > TP should Support Servlet 3 and Jetty 8 > --------------------------------------- > > Key: JBIDE-13736 > URL: https://issues.jboss.org/browse/JBIDE-13736 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > The org.eclipse.jetty.websocket bundle is required by the upcoming livereload tooling (will be certainly part of the VPE component) > Also, older version of Jetty should be removed from TP if they're not useful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13736) TP should Support Servlet 3 and Jetty 8

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13736?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13736: ---------------------------------------- [~xcoulon] > Why not using Jetty 8.1.9 instead of 8.1.3 ? (http://download.eclipse.org/jetty/updates/jetty-bundles-8.x/8.1.9.v20130131/) Jetty 8.1.3 is currently the one shipped with Kepler. We could use Jetty 8.1.9 from the Jetty update-site if it's necessary, but in general, we prefer using the version of the release train. > Also, the TP misses the following plugins: org.eclipse.jetty.websocket, org.eclipse.jetty.servlets, (PLURAL), org.eclipse.jetty.client Ok those ones are not part of default Kepler installation. So we'll need to use the Jetty update-site. I'll mirror it and change the TP to use it. > (sorry, this will require a new build of the TP) I think this is now made easier with the release process of Target Platform. That's what it's designed for: be able to do multiple SNAPSHOTs of a TP without confusion ;) > TP should Support Servlet 3 and Jetty 8 > --------------------------------------- > > Key: JBIDE-13736 > URL: https://issues.jboss.org/browse/JBIDE-13736 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > The org.eclipse.jetty.websocket bundle is required by the upcoming livereload tooling (will be certainly part of the VPE component) > Also, older version of Jetty should be removed from TP if they're not useful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13740) 'Switch Location' button in Server->Properties dialog works different from Deployment tab in Server editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13740?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13740. --------------------------------- Resolution: Rejected The Deployment tab does not have a "Switch Location" section. it has a section for switching the default deploy location. The "Switch Location" property page is to switch where the server itself is stored. When in metadata, the server and all of its key/value pairs is stored as an xml file in the server plugin's metadata folder. When in "Workspace", the server itself is stored as an xml file inside the workspace in a project named "Servers". This is to fascilitate sharing of the actual server adapter... not to change the deployment location of where a server adapter representation itself lives and is stored. > 'Switch Location' button in Server->Properties dialog works different from Deployment tab in Server editor > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13740 > URL: https://issues.jboss.org/browse/JBIDE-13740 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final, 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Optional > Attachments: Properties for jboss-eap _008.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13282) JBT Wiki & build docs need updating

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13282?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13282: ---------------------------------------- Closing as this is covered by https://github.com/jbosstools/jbosstools-build/wiki/ and https://github.com/jbosstools/jbosstools-target-platfroms/wiki/Faq > JBT Wiki & build docs need updating > ----------------------------------- > > Key: JBIDE-13282 > URL: https://issues.jboss.org/browse/JBIDE-13282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > > These docs need updates / new screenshots: > https://community.jboss.org/wiki/JBossToolsDevelopmentEnvironment > https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3 > http://download.jboss.org/jbosstools/builds/cascade/swimlanes.html (JavaEE (maven) depends on Hibernate) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

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 March 2013