[JBoss JIRA] (JBIDE-15834) Server error while deleting application on Openshift Enterprise
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15834?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-15834 at 11/3/13 1:45 PM:
----------------------------------------------------------------
I thought it too, but... I was trying to get that error in web interface (reproduce it) - no success. It showed just in JBDS (/JBT). Maybe it´s worth of notice - when you try to delete application you get that error, but (even immediately) second attempt to delete application it delete application as fast as I have never seen.
I´m afraid of more complex problem, bcs there are another server side errors (e.g. see JBIDE-15831)
was (Author: mlabuda):
I thought it too, but... I was trying to get that error in web interface (reproduce it) - no success. It showed just in JBDS (/JBT).
I´m afraid of more complex problem, bcs there are another server side errors (e.g. see JBIDE-15831)
> Server error while deleting application on Openshift Enterprise
> ---------------------------------------------------------------
>
> Key: JBIDE-15834
> URL: https://issues.jboss.org/browse/JBIDE-15834
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
>
> Sometimes attempt to delete application in Openshift Enterprise (in Openshift Online I didn't notice such bug) cause internal server error - HTTP error 500.
> Application (after showed dialog) is not deleted in Openshift Enterprise. Second attempt delete application succesfully.
> Unfortunately, I have no idea how to reproduce it (many various attempts done). It occurs sometimes.
> Eclipse log:
> {code}
> com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>500 Internal Server Error</title>
> </head><body>
> <h1>Internal Server Error</h1>
> <p>The server encountered an internal error or
> misconfiguration and was unable to complete
> your request.</p>
> <p>Please contact the server administrator,
> root@localhost and inform them of the time the error occurred,
> and anything you might have done that may have
> caused the error.</p>
> <p>More information about this error may be available
> in the server error log.</p>
> <hr>
> <address>Apache/2.2.15 (Red Hat) Server at console.itos.redhat.com Port 80</address>
> </body></html>
> at com.openshift.internal.client.RestService.request(RestService.java:136)
> at com.openshift.internal.client.RestService.request(RestService.java:109)
> at com.openshift.internal.client.RestService.request(RestService.java:92)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:142)
> at com.openshift.internal.client.ApplicationResource.destroy(ApplicationResource.java:256)
> at org.jboss.tools.openshift.express.internal.ui.job.DeleteApplicationsJob.doRun(DeleteApplicationsJob.java:47)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: com.openshift.internal.client.httpclient.InternalServerErrorException: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>500 Internal Server Error</title>
> </head><body>
> <h1>Internal Server Error</h1>
> <p>The server encountered an internal error or
> misconfiguration and was unable to complete
> your request.</p>
> <p>Please contact the server administrator,
> root@localhost and inform them of the time the error occurred,
> and anything you might have done that may have
> caused the error.</p>
> <p>More information about this error may be available
> in the server error log.</p>
> <hr>
> <address>Apache/2.2.15 (Red Hat) Server at console.itos.redhat.com Port 80</address>
> </body></html>
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:169)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.delete(UrlConnectionHttpClient.java:113)
> at com.openshift.internal.client.RestService.request(RestService.java:183)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 7 more
> Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> ... 11 more
> {code}
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15834) Server error while deleting application on Openshift Enterprise
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15834?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-15834 at 11/3/13 1:42 PM:
----------------------------------------------------------------
I thought it too, but... I was trying to get that error in web interface (reproduce it) - no success. It showed just in JBDS (/JBT).
I´m afraid of more complex problem, bcs there are another server side errors (e.g. see JBIDE-15831)
was (Author: mlabuda):
I thought it too, but... I was trying to get that error in web interface (reproduce it) - no success. It showed just in JBDS (/JBT).
> Server error while deleting application on Openshift Enterprise
> ---------------------------------------------------------------
>
> Key: JBIDE-15834
> URL: https://issues.jboss.org/browse/JBIDE-15834
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
>
> Sometimes attempt to delete application in Openshift Enterprise (in Openshift Online I didn't notice such bug) cause internal server error - HTTP error 500.
> Application (after showed dialog) is not deleted in Openshift Enterprise. Second attempt delete application succesfully.
> Unfortunately, I have no idea how to reproduce it (many various attempts done). It occurs sometimes.
> Eclipse log:
> {code}
> com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>500 Internal Server Error</title>
> </head><body>
> <h1>Internal Server Error</h1>
> <p>The server encountered an internal error or
> misconfiguration and was unable to complete
> your request.</p>
> <p>Please contact the server administrator,
> root@localhost and inform them of the time the error occurred,
> and anything you might have done that may have
> caused the error.</p>
> <p>More information about this error may be available
> in the server error log.</p>
> <hr>
> <address>Apache/2.2.15 (Red Hat) Server at console.itos.redhat.com Port 80</address>
> </body></html>
> at com.openshift.internal.client.RestService.request(RestService.java:136)
> at com.openshift.internal.client.RestService.request(RestService.java:109)
> at com.openshift.internal.client.RestService.request(RestService.java:92)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:142)
> at com.openshift.internal.client.ApplicationResource.destroy(ApplicationResource.java:256)
> at org.jboss.tools.openshift.express.internal.ui.job.DeleteApplicationsJob.doRun(DeleteApplicationsJob.java:47)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: com.openshift.internal.client.httpclient.InternalServerErrorException: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>500 Internal Server Error</title>
> </head><body>
> <h1>Internal Server Error</h1>
> <p>The server encountered an internal error or
> misconfiguration and was unable to complete
> your request.</p>
> <p>Please contact the server administrator,
> root@localhost and inform them of the time the error occurred,
> and anything you might have done that may have
> caused the error.</p>
> <p>More information about this error may be available
> in the server error log.</p>
> <hr>
> <address>Apache/2.2.15 (Red Hat) Server at console.itos.redhat.com Port 80</address>
> </body></html>
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:169)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.delete(UrlConnectionHttpClient.java:113)
> at com.openshift.internal.client.RestService.request(RestService.java:183)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 7 more
> Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> ... 11 more
> {code}
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15834) Server error while deleting application on Openshift Enterprise
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15834?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-15834:
---------------------------------------
I thought it too, but... I was trying to get that error in web interface (reproduce it) - no success. It showed just in JBDS (/JBT).
> Server error while deleting application on Openshift Enterprise
> ---------------------------------------------------------------
>
> Key: JBIDE-15834
> URL: https://issues.jboss.org/browse/JBIDE-15834
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
>
> Sometimes attempt to delete application in Openshift Enterprise (in Openshift Online I didn't notice such bug) cause internal server error - HTTP error 500.
> Application (after showed dialog) is not deleted in Openshift Enterprise. Second attempt delete application succesfully.
> Unfortunately, I have no idea how to reproduce it (many various attempts done). It occurs sometimes.
> Eclipse log:
> {code}
> com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>500 Internal Server Error</title>
> </head><body>
> <h1>Internal Server Error</h1>
> <p>The server encountered an internal error or
> misconfiguration and was unable to complete
> your request.</p>
> <p>Please contact the server administrator,
> root@localhost and inform them of the time the error occurred,
> and anything you might have done that may have
> caused the error.</p>
> <p>More information about this error may be available
> in the server error log.</p>
> <hr>
> <address>Apache/2.2.15 (Red Hat) Server at console.itos.redhat.com Port 80</address>
> </body></html>
> at com.openshift.internal.client.RestService.request(RestService.java:136)
> at com.openshift.internal.client.RestService.request(RestService.java:109)
> at com.openshift.internal.client.RestService.request(RestService.java:92)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:142)
> at com.openshift.internal.client.ApplicationResource.destroy(ApplicationResource.java:256)
> at org.jboss.tools.openshift.express.internal.ui.job.DeleteApplicationsJob.doRun(DeleteApplicationsJob.java:47)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: com.openshift.internal.client.httpclient.InternalServerErrorException: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>500 Internal Server Error</title>
> </head><body>
> <h1>Internal Server Error</h1>
> <p>The server encountered an internal error or
> misconfiguration and was unable to complete
> your request.</p>
> <p>Please contact the server administrator,
> root@localhost and inform them of the time the error occurred,
> and anything you might have done that may have
> caused the error.</p>
> <p>More information about this error may be available
> in the server error log.</p>
> <hr>
> <address>Apache/2.2.15 (Red Hat) Server at console.itos.redhat.com Port 80</address>
> </body></html>
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:169)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.delete(UrlConnectionHttpClient.java:113)
> at com.openshift.internal.client.RestService.request(RestService.java:183)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 7 more
> Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> ... 11 more
> {code}
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15815) NPE when adding parameter via Cordova Configuration Editor
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15815?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15815:
--------------------------------------
released a fix that guarantees a feature is always selected. Fix is in master now
> NPE when adding parameter via Cordova Configuration Editor
> ----------------------------------------------------------
>
> Key: JBIDE-15815
> URL: https://issues.jboss.org/browse/JBIDE-15815
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1a Beta1-v20131026-0906-B486, Linux KDE 64bit
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.1.1.CR1
>
>
> 1. Create new Hybrid Mobile project
> 2. Open config.xml file in Cordova Configuration Editor
> 3. Click Add to add parameters
> 4. Fill opened dialog and click OK
> ERROR: No parameters added and exception in Error log:
> {noformat}
> Unhandled event loop exception
> java.lang.NullPointerException
> at org.jboss.tools.aerogear.hybrid.ui.config.internal.PropertiesPage$6.widgetSelected(PropertiesPage.java:264)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {noformat}
--
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
12 years, 5 months
[JBoss JIRA] (JBDS-2555) JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2555?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2555 at 11/2/13 3:52 PM:
-----------------------------------------------------------
Seeing as we now have:
* JBDS installer jar,
* JBDS update site zip,
* JBDS Central TP zip (JBDS-2623),
* JBDS Examples/Archtypes cache script (JBDS-2543), and
* JBDS headless install script (JBDS-2715),
I think we're done here (from a technical implementation point of view).
HOWEVER, we could do a better job of communicating the existence and use of all these various pieces.
For example, we could:
* provide a link to the Central TP zip from the early access page for JBDS 7.1.0.Beta1
* create a new page on devstudio.jboss.com talking about the steps needed to set up JBDS offline (including caching archtypes & examples)
* add a new section to the Getting Started Guide or User Guide for JBDS 7.1?
[~maxandersen] [~mmurray] [~mmusaji] WDYT?
was (Author: nickboldt):
Seeing as we now have a Central TP zip (JBDS-2623), a JBDS update site zip and the archtype offline install script (JBDS-2543), plus a script for installing JBDS headlessly (JBDS-2715), I think we're done here.
Only thing left to do, I suppose, is to provide a link to the Central TP zip from the early access page for JBDS 7.1.0.Beta1.
[~maxandersen] [~mmurray] [~mmusaji] - do you agree with the above? Should we link to the Central TP (and anything else) from the Early Access page so as to better explain offline JBDS usage? Or keep all that in a separate section of the JBDS GSG/UG docs?
> JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip
> ----------------------------------------------------------------------------
>
> Key: JBDS-2555
> URL: https://issues.jboss.org/browse/JBDS-2555
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, updatesite
> Reporter: Jiri Pallich
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1, 7.1.0.CR1
>
>
> Offline Usage of JBoss Central (Customers without or very slow Internet access)
> On-line once, then off-line - aka a user demo/instructional class - the testLocal cache is usable/complete after one on-line install. Provide a script that pre-caches everything for an instructor/demo'er in the field (online once, then offline).
> Related to: https://issues.jboss.org/browse/JBDS-2535
--
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
12 years, 5 months
[JBoss JIRA] (JBDS-2555) JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2555?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2555:
----------------------------------
Seeing as we now have a Central TP zip (JBDS-2623), a JBDS update site zip and the archtype offline install script (JBDS-2543), plus a script for installing JBDS headlessly (JBDS-2715), I think we're done here.
Only thing left to do, I suppose, is to provide a link to the Central TP zip from the early access page for JBDS 7.1.0.Beta1.
[~maxandersen] [~mmurray] [~mmusaji] - do you agree with the above? Should we link to the Central TP (and anything else) from the Early Access page so as to better explain offline JBDS usage? Or keep all that in a separate section of the JBDS GSG/UG docs?
> JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip
> ----------------------------------------------------------------------------
>
> Key: JBDS-2555
> URL: https://issues.jboss.org/browse/JBDS-2555
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, updatesite
> Reporter: Jiri Pallich
> Fix For: 7.1.0.Beta1
>
>
> Offline Usage of JBoss Central (Customers without or very slow Internet access)
> On-line once, then off-line - aka a user demo/instructional class - the testLocal cache is usable/complete after one on-line install. Provide a script that pre-caches everything for an instructor/demo'er in the field (online once, then offline).
> Related to: https://issues.jboss.org/browse/JBDS-2535
--
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
12 years, 5 months
[JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2710:
-----------------------------
Description:
For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
Proposed *new* connectors for JBDS 7.1:
* Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
* SpringSource's Quick Search - JBDS-2686 *TBD* (affects JBDS installer/Central TP)
The current list of connectors in 7.0 *which can be updated* in 7.1 are:
* atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
* gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
* pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
* springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808
* subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
* testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
* VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677
* eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129
These are currently unchanged since December when we released JBDS 6.0.0:
* findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
Additionally (Target Platform):
* swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
* mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
* fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
See comments below for latest site URLs.
[1] https://github.com/jbosstools/jbosstools-locus/
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
[3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
was:
For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
Proposed *new* connectors for JBDS 7.1:
* Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
* SpringSource's Quick Search - JBDS-2686 *TBD* (affects JBDS installer/Central TP)
The current list of connectors in 7.0 *which can be updated* in 7.1 are:
* atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
* gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
* pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
* springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808
* subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
* testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
* VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677
* eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128
These are currently unchanged since December when we released JBDS 6.0.0:
* findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
Additionally (Target Platform):
* swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
* mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
* fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
See comments below for latest site URLs.
[1] https://github.com/jbosstools/jbosstools-locus/
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
[3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
> 3rd party certification for JBDS 7.1.0.GA
> -----------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.1.0.GA
>
>
> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
> Proposed *new* connectors for JBDS 7.1:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
> * SpringSource's Quick Search - JBDS-2686 *TBD* (affects JBDS installer/Central TP)
> The current list of connectors in 7.0 *which can be updated* in 7.1 are:
> * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
> * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
> * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
> * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677
> * eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129
> These are currently unchanged since December when we released JBDS 6.0.0:
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
--
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
12 years, 5 months