[jbosstools-issues] [JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows

Denis Golovin (JIRA) issues at jboss.org
Fri Jan 24 13:54:29 EST 2014


    [ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12938690#comment-12938690 ] 

Denis Golovin commented on JBDS-2635:
-------------------------------------

{quote}Okey, but we would need similar mechanisms that izpack provides. splashscreen, legal text, panels etc.{quote}
Current solution is a hack into IzPack which runs p2Director app as external process, reads process output, analyze it and reports progress in IzPack panel. It also checks process return code to see if it is finished correctly or failed. All this is working fine in most cases but:
1. It is slower than just running installation process inside the same JVM
2. It doesn't support Unicode names for target folder under windows (see JBDS-2260)
3. It is a hack done in forked class that needs migration every time we migrate to new IzPack.

Why Eclipse RCP? Because we know how eclipse works and can match every feature IzPack has like:
1. Multi-platform support
2. Panels are just wizards steps
3. What is going to be installed should be provided as p2repository instead of IzPack packs (additional files can be delivered as root file features (?))
4. UI translation do different languages (can be done, but we're not using it)
5. Splashscreen

What is missing in eclipse (n):
1. Support for creating Groups and Launchers in menu under windows and linux
2. Native installers (but we don't use it)
3. Launching eclipse RCP from jar file

{quote}Just trying to understand what the value we get by reimplementing these ?{quote}
We would have everything eclipse based, even installer (y)
Installation would be faster (y)
Installer would be smaller if packed pack200 (y)


                
> Installation sometimes fail with bundle was not found on Windows
> ----------------------------------------------------------------
>
>                 Key: JBDS-2635
>                 URL: https://issues.jboss.org/browse/JBDS-2635
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: installer
>    Affects Versions: 7.0.0.Beta1
>         Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07
>            Reporter: Jiri Peterka
>            Assignee: Denis Golovin
>             Fix For: 8.0.0.Alpha2
>
>         Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log
>
>
> For the first time JBDS 7.0.0.Beta1 failed on windows8: 
> {code}
> An error occurred while installing the items
>  session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
>  The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found.
> Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log
> {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


More information about the jbosstools-issues mailing list