[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/3/12 2:24 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):
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!
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!
Config.ini is slightly different - PDE installer includes {code}org.eclipse.update.reconcil=false{code}; tycho installer does not:
!jbds2176_config.ini.png!
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, 10 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/3/12 2:18 PM:
----------------------------------------------------------
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!
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!
Config.ini is slightly different - PDE installer includes {code}org.eclipse.update.reconcil=false{code}; tycho installer does not:
!jbds2176_config.ini.png!
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):
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!
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!
Config.ini is slightly different:
!jbds2176_config.ini.png!
jbdevstudio.ini is also different:
!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, 10 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/3/12 2:19 PM:
----------------------------------------------------------
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!
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!
Config.ini is slightly different - PDE installer includes {code}org.eclipse.update.reconcil=false{code}; tycho installer does not:
!jbds2176_config.ini.png!
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):
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!
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!
Config.ini is slightly different - PDE installer includes {code}org.eclipse.update.reconcil=false{code}; tycho installer does not:
!jbds2176_config.ini.png!
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, 10 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 updated JBDS-2176:
-----------------------------
Attachment: jbds2176_orphans.png
jbds2176_jbdevstudio.ini.png
jbds2176_config.ini.png
jbds2176_bundles.info.png
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!
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!
Config.ini is slightly different:
!jbds2176_config.ini.png!
jbdevstudio.ini is also different:
!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, 10 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:
-------------------------------------------
hmm - read this again, you are saying parent pom includes dependencies by default, but where is that default since Tycho normally don't include optionalDependencies does it ?
> 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: 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, 10 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:
-------------------------------------------
Denis - we really should not be including optional dependencies if there is no need for them.
Those we need should be explicitly included IMO when packaging runtime.
WDYT ?
p.s. not sure why we include optional dependencies by default in parent pom - I was happy when Tycho changed it defaults since it revealed quite a few "non-considered" dependencies for tests etc.
> 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: 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, 10 months
[JBoss JIRA] (JBDS-2169) Installer fails to load jvm selection page if some system properties current jvm have '\u' patterns
by Denis Golovin (JIRA)
Denis Golovin created JBDS-2169:
-----------------------------------
Summary: Installer fails to load jvm selection page if some system properties current jvm have '\u' patterns
Key: JBDS-2169
URL: https://issues.jboss.org/browse/JBDS-2169
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: installer
Affects Versions: 5.0.0.Beta3
Environment: Winows 7 Server
Reporter: Denis Golovin
Priority: Blocker
Fix For: 5.0.0.CR1
Exception occurs when installation process gets to Java Configuration page in installer. Page is empty and exception thrown at console
{code}PROCESSOR_ARCHITEW6432=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 15 Stepping 2, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0f02
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files (x86)
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
PUBLIC=C:\Users\Public
SESSIONNAME=Console
SFUDIR=C:\Windows\SUA\
SFUDIR_INTERIX=/dev/fs/C/Windows/SUA/
SUA_ROOT=/dev/fs/C/Windows/SUA/
SUA_ROOT_WIN=C:\Windows\SUA\
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\LLU~1.CIN\AppData\Local\Temp
TMP=C:\Users\LLU~1.CIN\AppData\Local\Temp
USERDNSDOMAIN=CINCOM.COM
USERDOMAIN=CINCOM
USERNAME=llu
USERPROFILE=C:\Users\llu.CINCOM
VBOX_INSTALL_PATH=C:\Program Files\Oracle\VirtualBox\
windir=C:\Windows
XAPPLRESDIR=/usr/X11R6/lib/X11/app-defaults
XCMSDB=/usr/X11R6/lib/X11/Xcms.txt
XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB
XNLSPATH=/usr/X11R6/lib/X11/locale
stderr:
exit status: 0
checking if os constraints [Os family unix name null version null arch null jre
null ] match current OS
no match with current OS!
checking if os constraints [Os family windows name null version null arch null
jre null ] match current OS
matched current OS.
Making temp file: iz-JBoss Developer Studio 5.0.0.Beta3.tmp
In temp directory: C:\Users\LLU~1.CIN\AppData\Local\Temp\
Temp file created
Initializing RulesEngine
RulesEngine.init()
Initializing builtin conditions for packs.
Pack.getCondition(): null for pack jbds
Pack.getCondition(): null for pack jbosseap
Custom langpack for eng available.
Resource customicons.xml not defined. No custom icons available.
Current Panel: licence
can show panel with id licence ?
no condition, show panel
Current Panel: introduction
can show panel with id introduction ?
no condition, show panel
Current Panel: target
can show panel with id target ?
no condition, show panel
Current focus owner: null
Current focus owner: null
Current Panel: target
can show panel with id target ?
no condition, show panel
Current Panel: licence
can show panel with id licence ?
no condition, show panel
Current Panel: jre
can show panel with id jre ?
no condition, show panel
Current focus owner: null
Current Panel: jre
can show panel with id jre ?
no condition, show panel
Current Panel: target
can show panel with id target ?
no condition, show panel
Current Panel: as
can show panel with id as ?
no condition, show panel
/F:/jbdevstudio-product-win32-x86_64-5.0.0.v201205141759M-H140-Beta3.jar
C:\Program Files (x86)\Java\jdk1.6.0_32\jre\bin\java -showversion
executeCommand
params: C:\Program Files (x86)\Java\jdk1.6.0_32\jre\bin\java
params: -showversion
params: -classpath
params: /F:/jbdevstudio-product-win32-x86_64-5.0.0.v201205141759M-H140-B
eta3.jar;jbdevstudio-product-win32-x86_64-5.0.0.v201205141759M-H140-Beta3.jar
params: com.jboss.jbds.installer.JREPathPanel
stdout:
java.runtime.name = Java(TM) SE Runtime Environment
sun.boot.library.path = C:\Program Files (x86)\Java\jdk1.6.0_32\jre\bin
java.vm.version = 20.7-b02
java.vm.vendor = Sun Microsystems Inc.
java.vendor.url = http://java.sun.com/
path.separator = ;
java.vm.name = Java HotSpot(TM) Client VM
file.encoding.pkg = sun.io
sun.java.launcher = SUN_STANDARD
user.country = US
sun.os.patch.level = Service Pack 1
java.vm.specification.name = Java Virtual Machine Specification
user.dir = F:\
java.runtime.version = 1.6.0_32-b05
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.endorsed.dirs = C:\Program Files (x86)\Java\jdk1.6.0_32\jre\lib\endorsed
os.arch = x86
java.io.tmpdir = C:\Users\LLU~1.CIN\AppData\Local\Temp\
line.separator =
java.vm.specification.vendor = Sun Microsystems Inc.
user.variant =
os.name = Windows 7
sun.jnu.encoding = Cp1252
java.library.path = C:\Program Files (x86)\Java\jdk1.6.0_32\jre\bin;C:\Windows\S
un\Java\bin;C:\Windows\system32;C:\Windows;ProC:\Windows\system32;C:\Windows;C:\
Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\SUA
\common\;C:\Windows\SUA\usr\lib\;C:\Program Files (x86)\Java\jdk1.6.0_32\bin;.
java.specification.name = Java Platform API Specification
java.class.version = 50.0
sun.management.compiler = HotSpot Client Compiler
os.version = 6.1
user.home = C:\Users\llu.CINCOM
user.timezone =
java.awt.printerjob = sun.awt.windows.WPrinterJob
file.encoding = Cp1252
java.specification.version = 1.6
java.class.path = /F:/jbdevstudio-product-win32-x86_64-5.0.0.v201205141759M-H140
-Beta3.jar;jbdevstudio-product-win32-x86_64-5.0.0.v201205141759M-H140-Beta3.jar
user.name = llu
java.vm.specification.version = 1.0
sun.java.command = com.jboss.jbds.installer.JREPathPanel
java.home = C:\Program Files (x86)\Java\jdk1.6.0_32\jre
sun.arch.data.model = 32
user.language = en
java.specification.vendor = Sun Microsystems Inc.
awt.toolkit = sun.awt.windows.WToolkit
java.vm.info = mixed mode, sharing
java.version = 1.6.0_32
java.ext.dirs = C:\Program Files (x86)\Java\jdk1.6.0_32\jre\lib\ext;C:\Windows\S
un\Java\lib\ext
sun.boot.class.path = C:\Program Files (x86)\Java\jdk1.6.0_32\jre\lib\resources.
jar;C:\Program Files (x86)\Java\jdk1.6.0_32\jre\lib\rt.jar;C:\Program Files (x86
)\Java\jdk1.6.0_32\jre\lib\sunrsasign.jar;C:\Program Files (x86)\Java\jdk1.6.0_3
2\jre\lib\jsse.jar;C:\Program Files (x86)\Java\jdk1.6.0_32\jre\lib\jce.jar;C:\Pr
ogram Files (x86)\Java\jdk1.6.0_32\jre\lib\charsets.jar;C:\Program Files (x86)\J
ava\jdk1.6.0_32\jre\lib\modules\jdk.boot.jar;C:\Program Files (x86)\Java\jdk1.6.
0_32\jre\classes
java.vendor = Sun Microsystems Inc.
file.separator = \
java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
sun.io.unicode.encoding = UnicodeLittle
sun.cpu.endian = little
sun.desktop = windows
sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
stderr:
java version "1.6.0_32"
Java(TM) SE Runtime Environment (build 1.6.0_32-b05)
Java HotSpot(TM) Client VM (build 20.7-b02, mixed mode, sharing)
exit status: 0
java.runtime.name = Java(TM) SE Runtime Environment
sun.boot.library.path = C:\Program Files (x86)\Java\jdk1.6.0_32\jre\bin
java.vm.version = 20.7-b02
java.vm.vendor = Sun Microsystems Inc.
java.vendor.url = http://java.sun.com/
path.separator = ;
java.vm.name = Java HotSpot(TM) Client VM
file.encoding.pkg = sun.io
sun.java.launcher = SUN_STANDARD
user.country = US
sun.os.patch.level = Service Pack 1
java.vm.specification.name = Java Virtual Machine Specification
user.dir = F:\
java.runtime.version = 1.6.0_32-b05
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.endorsed.dirs = C:\Program Files (x86)\Java\jdk1.6.0_32\jre\lib\endorsed
os.arch = x86
java.io.tmpdir = C:\Users\LLU~1.CIN\AppData\Local\Temp\
line.separator =
java.vm.specification.vendor = Sun Microsystems Inc.
user.variant =
os.name = Windows 7
sun.jnu.encoding = Cp1252
java.library.path = C:\Program Files (x86)\Java\jdk1.6.0_32\jre\bin;C:\Windows\S
un\Java\bin;C:\Windows\system32;C:\Windows;ProC:\Windows\system32;C:\Windows;C:\
Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\SUA
\common\;C:\Windows\SUA\usr\lib\;C:\Program Files (x86)\Java\jdk1.6.0_32\bin;.
java.specification.name = Java Platform API Specification
java.class.version = 50.0
sun.management.compiler = HotSpot Client Compiler
os.version = 6.1
user.home = C:\Users\llu.CINCOM
user.timezone =
java.awt.printerjob = sun.awt.windows.WPrinterJob
file.encoding = Cp1252
java.specification.version = 1.6
java.class.path = /F:/jbdevstudio-product-win32-x86_64-5.0.0.v201205141759M-H140
-Beta3.jar;jbdevstudio-product-win32-x86_64-5.0.0.v201205141759M-H140-Beta3.jar
user.name = llu
java.vm.specification.version = 1.0
sun.java.command = com.jboss.jbds.installer.JREPathPanel
java.home = C:\Program Files (x86)\Java\jdk1.6.0_32\jre
sun.arch.data.model = 32
user.language = en
java.specification.vendor = Sun Microsystems Inc.
awt.toolkit = sun.awt.windows.WToolkit
java.vm.info = mixed mode, sharing
java.version = 1.6.0_32
java.ext.dirs = C:\Program Files (x86)\Java\jdk1.6.0_32\jre\lib\ext;C:\Windows\S
un\Java\lib\ext
sun.boot.class.path = C:\Program Files (x86)\Java\jdk1.6.0_32\jre\lib\resources.
jar;C:\Program Files (x86)\Java\jdk1.6.0_32\jre\lib\rt.jar;C:\Program Files (x86
)\Java\jdk1.6.0_32\jre\lib\sunrsasign.jar;C:\Program Files (x86)\Java\jdk1.6.0_3
2\jre\lib\jsse.jar;C:\Program Files (x86)\Java\jdk1.6.0_32\jre\lib\jce.jar;C:\Pr
ogram Files (x86)\Java\jdk1.6.0_32\jre\lib\charsets.jar;C:\Program Files (x86)\J
ava\jdk1.6.0_32\jre\lib\modules\jdk.boot.jar;C:\Program Files (x86)\Java\jdk1.6.
0_32\jre\classes
java.vendor = Sun Microsystems Inc.
file.separator = \
java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
sun.io.unicode.encoding = UnicodeLittle
sun.cpu.endian = little
sun.desktop = windows
sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
java.lang.IllegalArgumentException: Malformed \uxxxx encoding.
at java.util.Properties.loadConvert(Properties.java:552)
at java.util.Properties.load0(Properties.java:375)
at java.util.Properties.load(Properties.java:325)
at com.jboss.jbds.installer.JREPathPanel.getJavaPlatformProperties(JREPa
thPanel.java:300)
at com.jboss.jbds.installer.JREPathPanel.verifyVersion(JREPathPanel.java
:274)
at com.jboss.jbds.installer.JREPathPanel.panelActivate(JREPathPanel.java
:229)
at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFram
e.java:839)
at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFra
me.java:1450)
at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFra
me.java:1418)
at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP
erformed(InstallerFrame.java:1560)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:19
95)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.jav
a:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel
.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242
)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonL
istener.java:236)
at java.awt.Component.processMouseEvent(Component.java:6290)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6055)
at java.awt.Container.processEvent(Container.java:2039)
at java.awt.Component.dispatchEventImpl(Component.java:4653)
at java.awt.Container.dispatchEventImpl(Container.java:2097)
at java.awt.Component.dispatchEvent(Component.java:4481)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4575
)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4236)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4166)
at java.awt.Container.dispatchEventImpl(Container.java:2083)
at java.awt.Window.dispatchEventImpl(Window.java:2482)
at java.awt.Component.dispatchEvent(Component.java:4481)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:648)
at java.awt.EventQueue.access$000(EventQueue.java:84)
at java.awt.EventQueue$1.run(EventQueue.java:607)
at java.awt.EventQueue$1.run(EventQueue.java:605)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessCo
ntrolContext.java:87)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessCo
ntrolContext.java:98)
at java.awt.EventQueue$2.run(EventQueue.java:621)
at java.awt.EventQueue$2.run(EventQueue.java:619)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessCo
ntrolContext.java:87)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:618)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThre
ad.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.
java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre
ad.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122){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, 10 months
[JBoss JIRA] (JBIDE-11676) java.lang.NoClassDefFoundError: javax/ws/rs/HttpMethod
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-11676:
------------------------------------
Summary: java.lang.NoClassDefFoundError: javax/ws/rs/HttpMethod
Key: JBIDE-11676
URL: https://issues.jboss.org/browse/JBIDE-11676
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.3.0.Beta3
Environment: JBT 3.3.0.beta3-trunk, L64
Reporter: Jiri Peterka
Assignee: Brian Fitzpatrick
Fix For: 3.3.0.CR1
java.lang.NoClassDefFoundError: javax/ws/rs/HttpMethod
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElement(JaxrsElementFactory.java:74)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAddition(JavaElementChangedProcessor.java:314)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedElement(JavaElementChangedProcessor.java:132)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedJavaElements(JavaElementChangedProcessor.java:75)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuildJob.run(JaxrsMetamodelBuildJob.java:56)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
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, 10 months