[JBoss JIRA] (JBDS-2176) Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2176?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2176 at 6/4/12 2:20 PM:
----------------------------------------------------------
Down to 4 major differences:
1.
JBDS installer from Tycho (left): org.eclipse.net4j.jms.api plugin is included.
JBDS installer from PDE (right): no such plugin included.
Also, the Tycho installer is missing the about_files/ folder and the about.html root file.
!jbds2176_orphans.png!
2.
Here's how bundles.info varies, showing the difference between jarred and unpacked plugins, and the addition of the additional org.eclipse.net4j.jms.api plugin:
!jbds2176_bundles.info.png!
3. {color:red}*NOT IMPORTANT*{color}
Config.ini is slightly different - PDE installer includes
{code}org.eclipse.update.reconcil=false{code}
This is because of PDE/Build's default configuration settings (http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.pde.doc.user...). Tycho does not set this default.
Do we need it? Given the help docs state the property is called "org.eclipse.update.reconcile", not ".reconcil", I would guess that this isn't actually doing anything.
!jbds2176_config.ini.png!
4.
jbdevstudio.ini is also different - PDE installer includes
{code}
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505{code}
whereas Tycho installer includes
{code}-Dosgi.bundles=reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110815-1438.jar@1:start{code}
!jbds2176_jbdevstudio.ini.png!
was (Author: nickboldt):
Down to 4 major differences:
1.
JBDS installer from Tycho (left): org.eclipse.net4j.jms.api plugin is included.
JBDS installer from PDE (right): no such plugin included.
Also, the Tycho installer is missing the about_files/ folder and the about.html root file.
!jbds2176_orphans.png!
2.
Here's how bundles.info varies, showing the difference between jarred and unpacked plugins, and the addition of the additional org.eclipse.net4j.jms.api plugin:
!jbds2176_bundles.info.png!
-3. -
-Config.ini is slightly different - PDE installer includes -
{code}org.eclipse.update.reconcil=false{code}
-This is because of PDE/Build's default configuration settings (http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.pde.doc.user...). Tycho does not set this default.-
-Do we need it? Given the help docs state the property is called "org.eclipse.update.reconcile", not ".reconcil", I would guess that this isn't actually doing anything.-
!jbds2176_config.ini.png!
4.
jbdevstudio.ini is also different - PDE installer includes
{code}
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505{code}
whereas Tycho installer includes
{code}-Dosgi.bundles=reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110815-1438.jar@1:start{code}
!jbds2176_jbdevstudio.ini.png!
> Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2176
> URL: https://issues.jboss.org/browse/JBDS-2176
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 5.0.0.CR1
>
> Attachments: jbds2176_bundles.info.png, jbds2176_config.ini.png, jbds2176_jbdevstudio.ini.png, jbds2176_orphans.png, lucene.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png
>
>
> Comparing the on-disk footprints for the two installers, I see some discrepancies.
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png!
> Left: jarred plugins for ch.qos. org.eclipse.equinox, org.slf4j
> Right: unpcked plugins
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png!
> Left: javax.servlet 3.0; no org.apache.lucene
> Right: no javax.servlet; org.apache.lucene 2.9.1
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png!
> Left: org.eclipse.jetty
> Right: no jetty
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png!
> Left: org.eclipse.mylyn.commons.workbench, org.jdom
> Right: no org.eclipse.mylyn.commons.workbench; no org.jdom
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBDS-2176) Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2176?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2176 at 6/4/12 2:19 PM:
----------------------------------------------------------
Down to 4 major differences:
1.
JBDS installer from Tycho (left): org.eclipse.net4j.jms.api plugin is included.
JBDS installer from PDE (right): no such plugin included.
Also, the Tycho installer is missing the about_files/ folder and the about.html root file.
!jbds2176_orphans.png!
2.
Here's how bundles.info varies, showing the difference between jarred and unpacked plugins, and the addition of the additional org.eclipse.net4j.jms.api plugin:
!jbds2176_bundles.info.png!
---3.
Config.ini is slightly different - PDE installer includes
{code}org.eclipse.update.reconcil=false{code}
This is because of PDE/Build's default configuration settings (http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.pde.doc.user...). Tycho does not set this default.
Do we need it? Given the help docs state the property is called "org.eclipse.update.reconcile", not ".reconcil", I would guess that this isn't actually doing anything.
!jbds2176_config.ini.png!
---
4.
jbdevstudio.ini is also different - PDE installer includes
{code}
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505{code}
whereas Tycho installer includes
{code}-Dosgi.bundles=reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110815-1438.jar@1:start{code}
!jbds2176_jbdevstudio.ini.png!
was (Author: nickboldt):
Down to 4 major differences:
1.
JBDS installer from Tycho (left): org.eclipse.net4j.jms.api plugin is included.
JBDS installer from PDE (right): no such plugin included.
Also, the Tycho installer is missing the about_files/ folder and the about.html root file.
!jbds2176_orphans.png!
2.
Here's how bundles.info varies, showing the difference between jarred and unpacked plugins, and the addition of the additional org.eclipse.net4j.jms.api plugin:
!jbds2176_bundles.info.png!
3.
Config.ini is slightly different - PDE installer includes
{code}org.eclipse.update.reconcil=false{code}
This is because of PDE/Build's default configuration settings (http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.pde.doc.user...). Tycho does not set this default.
Do we need it? Given the help docs state the property is called "org.eclipse.update.reconcile", not ".reconcil", I would guess that this isn't actually doing anything.
!jbds2176_config.ini.png!
4.
jbdevstudio.ini is also different - PDE installer includes
{code}
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505{code}
whereas Tycho installer includes
{code}-Dosgi.bundles=reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110815-1438.jar@1:start{code}
!jbds2176_jbdevstudio.ini.png!
> Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2176
> URL: https://issues.jboss.org/browse/JBDS-2176
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 5.0.0.CR1
>
> Attachments: jbds2176_bundles.info.png, jbds2176_config.ini.png, jbds2176_jbdevstudio.ini.png, jbds2176_orphans.png, lucene.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png
>
>
> Comparing the on-disk footprints for the two installers, I see some discrepancies.
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png!
> Left: jarred plugins for ch.qos. org.eclipse.equinox, org.slf4j
> Right: unpcked plugins
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png!
> Left: javax.servlet 3.0; no org.apache.lucene
> Right: no javax.servlet; org.apache.lucene 2.9.1
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png!
> Left: org.eclipse.jetty
> Right: no jetty
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png!
> Left: org.eclipse.mylyn.commons.workbench, org.jdom
> Right: no org.eclipse.mylyn.commons.workbench; no org.jdom
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBDS-2176) Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2176?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2176:
-------------------------------------------
http://wiki.eclipse.org/Equinox_Launcher:
"--launcher.library <path/to/eclipse shared lib>. This indicates the path to the eclipse shared library to use. By default, the launcher looks in the plugins directory for the matching org.eclipse.equinox.launcher.[config] fragment with the highest version. The shared library is found in that fragment.
If the path points to a directory, we use the file eclipse_<version>[.<extension>] with the highest version number.
[04/06/12 20:12:21] Max Rydahl Andersen: -startup <path/to/launcher.jar>. This indicates the path to the launcher jar. By default, the launcher looks in the plugins directory for the org.eclipse.equinox.launcher bundle with the highest version and uses it. If this bundle is not found, then the launcher will revert to old behaviour and look for startup.jar in the root.
If a relative path is given, the launcher will check first relative to the working directory, and second relative to the root of the eclipse install (which is the location of the eclipse.exe)"
thus without these it will take latest which should be fine for us - less metadata to update.
> Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2176
> URL: https://issues.jboss.org/browse/JBDS-2176
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 5.0.0.CR1
>
> Attachments: jbds2176_bundles.info.png, jbds2176_config.ini.png, jbds2176_jbdevstudio.ini.png, jbds2176_orphans.png, lucene.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png
>
>
> Comparing the on-disk footprints for the two installers, I see some discrepancies.
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png!
> Left: jarred plugins for ch.qos. org.eclipse.equinox, org.slf4j
> Right: unpcked plugins
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png!
> Left: javax.servlet 3.0; no org.apache.lucene
> Right: no javax.servlet; org.apache.lucene 2.9.1
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png!
> Left: org.eclipse.jetty
> Right: no jetty
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png!
> Left: org.eclipse.mylyn.commons.workbench, org.jdom
> Right: no org.eclipse.mylyn.commons.workbench; no org.jdom
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBDS-2176) Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2176?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2176:
-------------------------------------
according to org.eclipse.equinox.p2.discovery.feature equinox plugins should be installed as jars
{code}
<plugin
id="org.eclipse.equinox.p2.discovery"
download-size="0"
install-size="0"
version="1.0.100.v20110502-1955"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.discovery.compatibility"
download-size="0"
install-size="0"
version="1.0.1.v20110502-1955"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.ui.discovery"
download-size="0"
install-size="0"
version="1.0.0.v20110502-1955"
unpack="false"/>
{code}
> Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2176
> URL: https://issues.jboss.org/browse/JBDS-2176
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 5.0.0.CR1
>
> Attachments: jbds2176_bundles.info.png, jbds2176_config.ini.png, jbds2176_jbdevstudio.ini.png, jbds2176_orphans.png, lucene.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png
>
>
> Comparing the on-disk footprints for the two installers, I see some discrepancies.
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png!
> Left: jarred plugins for ch.qos. org.eclipse.equinox, org.slf4j
> Right: unpcked plugins
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png!
> Left: javax.servlet 3.0; no org.apache.lucene
> Right: no javax.servlet; org.apache.lucene 2.9.1
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png!
> Left: org.eclipse.jetty
> Right: no jetty
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png!
> Left: org.eclipse.mylyn.commons.workbench, org.jdom
> Right: no org.eclipse.mylyn.commons.workbench; no org.jdom
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBIDE-12089) LaunchConfiguration can be edited, but will be lost because of deferred delete
by Thomas Frühbeck (JIRA)
Thomas Frühbeck created JBIDE-12089:
---------------------------------------
Summary: LaunchConfiguration can be edited, but will be lost because of deferred delete
Key: JBIDE-12089
URL: https://issues.jboss.org/browse/JBIDE-12089
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: forge
Reporter: Thomas Frühbeck
Assignee: Koen Aers
Priority: Minor
The Forge LaunchConfiguration can be changed to allow source lookup.
Due to the fact that the name of the launch config is artificial, it will be destroyed.
By defining a name for LauchConfiguration in the ForgePreferences we can allow for persistent configurations:
- a (list of) names can be defined in ForgePreferences
- each LaunchConfiguration will be associated with a specific Runtime
- Forge development can be assisted by integrating Forge core/dist/target as Runtime
- development of plugins can be assisted be integration of other project's source
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBIDE-11960) Error when expanding user node when password is not saved in secure store
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-11960:
-------------------------------------
Summary: Error when expanding user node when password is not saved in secure store
Key: JBIDE-11960
URL: https://issues.jboss.org/browse/JBIDE-11960
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta3
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Priority: Critical
Fix For: 3.3.0.CR1
Error log is:
{code}
com.openshift.client.OpenShiftEndpointException: Could not request https://openshift.redhat.com/broker/rest/domains: <!DOCTYPE html>
<html>
<head>
<title>We're sorry, but something went wrong (500)</title>
<style type="text/css">
body { background-color: #fff; color: #666; text-align: center; font-family: arial, sans-serif; }
div.dialog {
width: 25em;
padding: 0 4em;
margin: 4em auto 0 auto;
border: 1px solid #ccc;
border-right-color: #999;
border-bottom-color: #999;
}
h1 { font-size: 100%; color: #f00; line-height: 1.5em; }
</style>
</head>
<body>
<!-- This file lives in public/500.html -->
<div class="dialog">
<h1>We're sorry, but something went wrong.</h1>
<p>We've been notified about this issue and we'll take a look at it shortly.</p>
</div>
</body>
</html>
at com.openshift.internal.client.RestService.request(RestService.java:102)
at com.openshift.internal.client.RestService.request(RestService.java:90)
at com.openshift.internal.client.RestService.request(RestService.java:75)
at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:154)
at com.openshift.internal.client.APIResource$ListDomainsRequest.execute(APIResource.java:173)
at com.openshift.internal.client.APIResource.loadDomains(APIResource.java:81)
at com.openshift.internal.client.APIResource.getDomains(APIResource.java:74)
at com.openshift.internal.client.UserResource.hasDomain(UserResource.java:92)
at org.jboss.tools.openshift.express.internal.core.console.UserDelegate.hasDomain(UserDelegate.java:207)
at org.jboss.tools.openshift.express.internal.ui.wizard.ApplicationConfigurationWizardPage.checkForDomainExistance(ApplicationConfigurationWizardPage.java:679)
at org.jboss.tools.openshift.express.internal.ui.wizard.ApplicationConfigurationWizardPage.onPageActivated(ApplicationConfigurationWizardPage.java:630)
at org.jboss.tools.openshift.express.internal.ui.wizard.AbstractOpenShiftWizardPage$1.pageChanged(AbstractOpenShiftWizardPage.java:76)
at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1554)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.wizard.WizardDialog.firePageChanged(WizardDialog.java:1552)
at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1337)
at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1265)
at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1239)
at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1228)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1226)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.jboss.tools.central.editors.GettingStartedPage$9.linkActivated(GettingStartedPage.java:618)
at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199)
at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
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:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: com.openshift.internal.client.httpclient.HttpClientException: <!DOCTYPE html>
<html>
<head>
<title>We're sorry, but something went wrong (500)</title>
<style type="text/css">
body { background-color: #fff; color: #666; text-align: center; font-family: arial, sans-serif; }
div.dialog {
width: 25em;
padding: 0 4em;
margin: 4em auto 0 auto;
border: 1px solid #ccc;
border-right-color: #999;
border-bottom-color: #999;
}
h1 { font-size: 100%; color: #f00; line-height: 1.5em; }
</style>
</head>
<body>
<!-- This file lives in public/500.html -->
<div class="dialog">
<h1>We're sorry, but something went wrong.</h1>
<p>We've been notified about this issue and we'll take a look at it shortly.</p>
</div>
</body>
</html>
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:180)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:90)
at com.openshift.internal.client.RestService.request(RestService.java:135)
at com.openshift.internal.client.RestService.request(RestService.java:96)
... 71 more
Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://openshift.redhat.com/broker/rest/domains
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:85)
... 73 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBDS-2075) Forge console goes crazy when running forge-from-scratch quickstart in JBDS Forge Console
by Pete Muir (JIRA)
Pete Muir created JBDS-2075:
-------------------------------
Summary: Forge console goes crazy when running forge-from-scratch quickstart in JBDS Forge Console
Key: JBDS-2075
URL: https://issues.jboss.org/browse/JBDS-2075
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.0.0.Beta1
Reporter: Pete Muir
{code}
? [named=The name of the new project (of type java.lang.String)]: acme
? [topLevelPackage=The top-level java package for the project [e.g: "com.example.project"] (of type java.lang.String)]: com.acme
? Use [/Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme] as project directory? [Y/n]
***SUCCESS*** Created project [acme] in new working directory [/Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme]
Wrote /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme
Wrote /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/pom.xml
Wrote /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java
Wrote /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/test/java
Wrote /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/resources
Wrote /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/test/resources
Wrote /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme
Wrote /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/resources/META-INF/forge.xml
EC: rest endpoint-from-entity CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: org.jboss.forge.shell.util.PipeOutImpl@3726b44d [Ljava.lang.String;@410927f7 POM File Modified: acme EC: build build CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: org.jboss.forge.shell.util.PipeOutImpl@71a52b88 null null null EC: set set CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: ACCEPT_DEFAULTS [Ljava.lang.String;@12cd2802 EC: cd cd CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: ~~ EC: run run CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: generate.fsh null EC: rest setup CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: org.jboss.forge.shell.util.PipeOutImpl@1f865b82 EC: cd cd CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: ~~ EC: scaffold from-entity CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: [Ljava.lang.String;@42357933 faces true null org.jboss.forge.shell.util.PipeOutImpl@6ef1dd49 EC: cd cd CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: .. EC: cd cd CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: .. EC: cd cd CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: .. EC: field oneToOne CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Customer.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: profile com.acme.domain.Profile.java null Wrote /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/ZipCode.java
Wrote /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Profile.java
EC: entity entity CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/ProductOrder.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: ProductOrder null EC: pick-up pick-up CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/ProductOrder.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/ProductOrder.java null EC: cd cd CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: .. EC: field int CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Item.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: stock true EC: field number CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Item.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: price java.lang.Double EC: field string CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Item.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: name EC: entity entity CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Item.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: Item null EC: pick-up pick-up CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Item.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Item.java null EC: field temporal CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Customer.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: DATE birthDate EC: field string CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Customer.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: lastName EC: field string CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Customer.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: firstName EC: entity entity CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Customer.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: Customer com.acme.domain EC: pick-up pick-up CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Customer.java CRT: JavaResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme/src/main/java/com/acme/domain/Customer.java null EC: persistence setup CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: HIBERNATE null JBOSS_AS7 DEFAULT null null null null null null forge-default org.jboss.forge.shell.util.PipeOutImpl@ce9c417 POM File Modified: acme EC: scaffold setup CRN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme CRT: DirectoryResource CPN: /Users/pmuir/workspace/jboss-as-quickstart/forge-from-scratch/acme PAR: org.jboss.forge.shell.util.PipeOutImpl@b68d372 faces null null
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBIDE-11919) Forge Console in JBDS/Tools - Screen "Garbage"f
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-11919:
-----------------------------------
Summary: Forge Console in JBDS/Tools - Screen "Garbage"f
Key: JBIDE-11919
URL: https://issues.jboss.org/browse/JBIDE-11919
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Environment: 3.3.Beta3 or JBDS5 Beta3
Reporter: Burr Sutter
Assignee: Koen Aers
_____
| ___|__ _ __ __ _ ___
EC: echo echo CRN: /Users/burr/gettingstarted/workspaceToolsBeta2v3 CRT: DirectoryResource CPN: PAR: [Ljava.lang.String;@1371098d org.jboss.forge.shell.util.PipeOutImpl@622a11f3 EC: echo echo CRN: /Users/burr/gettingstarted/workspaceToolsBeta2v3 CRT: DirectoryResource CPN: PAR: [Ljava.lang.String;@38009ade org.jboss.forge.shell.util.PipeOutImpl@2fb7818b EC: echo echo CRN: /Users/burr/gettingstarted/workspaceToolsBeta2v3 CRT: DirectoryResource CPN: PAR: [Ljava.lang.String;@421dc8c8 org.jboss.forge.shell.util.PipeOutImpl@3004ed34
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBDS-2176) Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2176?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2176:
-------------------------------------------
About reconciler: http://wiki.eclipse.org/Equinox/p2/FAQ#Why_are_my_uninstalled_bundles_bei...
If we have org.eclipse.update.configurator bundled then we need it - but with "pure p2" that should not happen.
In my JBDS install from last week I do though find "/studio/p2/director/plugins/org.eclipse.update.configurator_3.3.100.v20100512.jar" thus this seem to be rather important to avoid uninstalls to not have an effect?!
> Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2176
> URL: https://issues.jboss.org/browse/JBDS-2176
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 5.0.0.CR1
>
> Attachments: jbds2176_bundles.info.png, jbds2176_config.ini.png, jbds2176_jbdevstudio.ini.png, jbds2176_orphans.png, lucene.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png
>
>
> Comparing the on-disk footprints for the two installers, I see some discrepancies.
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png!
> Left: jarred plugins for ch.qos. org.eclipse.equinox, org.slf4j
> Right: unpcked plugins
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png!
> Left: javax.servlet 3.0; no org.apache.lucene
> Right: no javax.servlet; org.apache.lucene 2.9.1
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png!
> Left: org.eclipse.jetty
> Right: no jetty
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png!
> Left: org.eclipse.mylyn.commons.workbench, org.jdom
> Right: no org.eclipse.mylyn.commons.workbench; no org.jdom
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBIDE-9735) Refactor the forge plugins to get rid of the ui console dependencies and make it easier to handle ansi commands
by Koen Aers (JIRA)
Refactor the forge plugins to get rid of the ui console dependencies and make it easier to handle ansi commands
---------------------------------------------------------------------------------------------------------------
Key: JBIDE-9735
URL: https://issues.jboss.org/browse/JBIDE-9735
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: forge
Reporter: Koen Aers
Fix For: 3.3.0.M4
Following things need to be done:
- create a ForgeTextViewer that inherits from jface TextViewer
- the ForgeTextViewer initializes a filter chain to filter all the escaped input
- the ForgeHiddenOutputFilter will filter the hidden input (new escape sequence : 27 + '%'
- the ForgeAnsiCommandFilter filters the ansi commands that come from the runtime : 27 + '['
- the ForgeTextViewer will execute the ansi commands and interpret the hidden output
- the dependencies on the Eclipse Console classes can be eliminated: Console, ConsolePage, ConsoleViewer
- ForgeInputReadJob is not needed anymore
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months