[JBoss JIRA] (JBDS-2455) automated install-grinder install tests for JBDS will always fail because Jenkins can't see https://devstudio.jboss.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2455?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-2455.
----------------------------
Resolution: Done
Helpdesk has resolved this problem. Jenkins can now run install tests using devstudio.jboss.com as the update site source.
> automated install-grinder install tests for JBDS will always fail because Jenkins can't see https://devstudio.jboss.com
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2455
> URL: https://issues.jboss.org/browse/JBDS-2455
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 6.0.0.GA, 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Install-grinder tests [1] attempt to install from JBDS Central, via this URL [2]
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
> [2] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... -> plugins/com.jboss.jbds.central.discovery_6.0.1.GA-v20130130-1759-B206.jar
> When you look in the discovery jar [3], you see that the URLs referenced within the plugin.xml are on devstudio.jboss.com [4], rather than www.qa.jboss.com [5].
> [3] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable...
> [4] https://devstudio.jboss.com/updates/6.0/central/core/
> [5] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable...
> So, we need to implement Central somehow so that the plugin.xml (with a plugin.properties) can have those URLs overridden by a commandline flag.
> This is somewhat already done for the SOA Tooling discovery plugin, using %jboss.soa.update.url:
> https://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product-so...
> However, IIRC it's only implemented at BUILD time, not RUN time, which means we would have to manually adjust the plugin within the Jenkins job workspace (with unzip, sed, zip) to make the change stick at RUN time, or wed have to rebuild it as part of the test run.
> Is there a better way?
--
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
[JBoss JIRA] (JBDS-2455) automated install-grinder install tests for JBDS will always fail because Jenkins can't see https://devstudio.jboss.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2455?page=com.atlassian.jira.plugin.... ]
Nick Boldt reopened JBDS-2455:
------------------------------
> automated install-grinder install tests for JBDS will always fail because Jenkins can't see https://devstudio.jboss.com
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2455
> URL: https://issues.jboss.org/browse/JBDS-2455
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 6.0.0.GA, 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Install-grinder tests [1] attempt to install from JBDS Central, via this URL [2]
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
> [2] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... -> plugins/com.jboss.jbds.central.discovery_6.0.1.GA-v20130130-1759-B206.jar
> When you look in the discovery jar [3], you see that the URLs referenced within the plugin.xml are on devstudio.jboss.com [4], rather than www.qa.jboss.com [5].
> [3] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable...
> [4] https://devstudio.jboss.com/updates/6.0/central/core/
> [5] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable...
> So, we need to implement Central somehow so that the plugin.xml (with a plugin.properties) can have those URLs overridden by a commandline flag.
> This is somewhat already done for the SOA Tooling discovery plugin, using %jboss.soa.update.url:
> https://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product-so...
> However, IIRC it's only implemented at BUILD time, not RUN time, which means we would have to manually adjust the plugin within the Jenkins job workspace (with unzip, sed, zip) to make the change stick at RUN time, or wed have to rebuild it as part of the test run.
> Is there a better way?
--
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
[JBoss JIRA] (JBIDE-13736) TP should Support Servlet 3 and Jetty 8
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13736?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-13736.
------------------------------
Release Notes Docs Status: Not Required
Resolution: Done
Closing again now that clarification is achieved.
> 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
[JBoss JIRA] (JBIDE-13712) TP should not contain old org.mortbay.jetty plugins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13712?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-13712.
--------------------------------
Release Notes Docs Status: Not Required
Resolution: Done
Removed from Kepler M6 target platform.
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3...
> 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
[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x (JBDS70_1211)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2484:
-----------------------------
Description:
For JBDS 7, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682
* gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486
* springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395
* subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
* testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
These are currently unchanged since December when we released JBDS 6.0.0:
* eclipsecs/5.6.0.201209221626 - nothing new as of 2013.03.22
* findbugs/2.0.2.20121210 - nothing new as of 2013.03.22
* pmd/3.2.6 - nothing new as of 2013.03.22
Additionally:
* egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but in M6; not part of Central as this is included in TP / Core)
* swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
See comments below for latest site URLs.
was:
For JBDS 7, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682
* gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486
* springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395
* subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
* testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
These are currently unchanged since December when we released JBDS 6.0.0:
* eclipsecs/5.6.0.201209221626 - nothing new as of 2013.03.22
* findbugs/2.0.2.20121210 - nothing new as of 2013.03.22
* pmd/3.2.6 - nothing new as of 2013.03.22
Additionally:
* egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
* swtbot 2.1 / junit4 - JBIDE-13843
See comments below for latest site URLs.
> 3rd party certification for JBDS 7.x (JBDS70_1211)
> --------------------------------------------------
>
> Key: JBDS-2484
> URL: https://issues.jboss.org/browse/JBDS-2484
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.0.0.Alpha2
>
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682
> * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486
> * springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395
> * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
> * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
> These are currently unchanged since December when we released JBDS 6.0.0:
> * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.03.22
> * findbugs/2.0.2.20121210 - nothing new as of 2013.03.22
> * pmd/3.2.6 - nothing new as of 2013.03.22
> Additionally:
> * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but in M6; not part of Central as this is included in TP / Core)
> * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> See comments below for latest site URLs.
--
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
[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x (JBDS70_1211)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2484 at 3/22/13 11:35 AM:
------------------------------------------------------------
New composites (Spring 3.2, Atlassian 3.2, GWT 3.2.1):
http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.2/
https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.2/
New TPs:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3...
http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/4...
was (Author: nickboldt):
New composites (Spring 3.2, Atlassian 3.2, GWT 3.2.1):
http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.2/
https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.2/
> 3rd party certification for JBDS 7.x (JBDS70_1211)
> --------------------------------------------------
>
> Key: JBDS-2484
> URL: https://issues.jboss.org/browse/JBDS-2484
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.0.0.Alpha2
>
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682
> * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486
> * springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395
> * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
> * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
> These are currently unchanged since December when we released JBDS 6.0.0:
> * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.03.22
> * findbugs/2.0.2.20121210 - nothing new as of 2013.03.22
> * pmd/3.2.6 - nothing new as of 2013.03.22
> Additionally:
> * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but in M6; not part of Central as this is included in TP / Core)
> * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> See comments below for latest site URLs.
--
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
[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x (JBDS70_1211)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2484:
-----------------------------
Description:
For JBDS 7, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682
* gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486
* springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395
* subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
* testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
These are currently unchanged since December when we released JBDS 6.0.0:
* eclipsecs/5.6.0.201209221626 - nothing new as of 2013.03.22
* findbugs/2.0.2.20121210 - nothing new as of 2013.03.22
* pmd/3.2.6 - nothing new as of 2013.03.22
Additionally:
* egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
* swtbot 2.1 / junit4 - JBIDE-13843
See comments below for latest site URLs.
was:
For JBDS 7, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682
* gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486
* springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395
* subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
* testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
These are currently unchanged since December when we released JBDS 6.0.0:
* eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28
* findbugs/2.0.2.20121210 - nothing new as of 2013.02.28
* pmd/3.2.6 - nothing new as of 2013.02.28
Additionally:
* egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
* swtbot 2.1 / junit4 - JBIDE-13843
See comments below for latest site URLs.
> 3rd party certification for JBDS 7.x (JBDS70_1211)
> --------------------------------------------------
>
> Key: JBDS-2484
> URL: https://issues.jboss.org/browse/JBDS-2484
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.0.0.Alpha2
>
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682
> * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486
> * springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395
> * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
> * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
> These are currently unchanged since December when we released JBDS 6.0.0:
> * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.03.22
> * findbugs/2.0.2.20121210 - nothing new as of 2013.03.22
> * pmd/3.2.6 - nothing new as of 2013.03.22
> Additionally:
> * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
> * swtbot 2.1 / junit4 - JBIDE-13843
> See comments below for latest site URLs.
--
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