[jbosstools-issues] [JBoss JIRA] Resolved: (JBDS-1334) Change of JBDS installation folder name causes errors

[Nick Boldt (JIRA)]

     [ https://jira.jboss.org/browse/JBDS-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt resolved JBDS-1334.
------------------------------

    Resolution: Rejected


I believe this is a limitation of the way p2 stores absolute paths in its metadata for installed plugins/features. Short of opening a bug against Eclipse 3.7 and waiting until June 2011, I don't see a solution.

Workaround 1: don't rename the folder after update, or install into /opt/ide/jbds/3.0 so that the maintenance releases need not be reflected in the path

Workaround 2: use a symlink to make /opt/ide/jbds/3.0.2.ga point at /opt/ide/jbds/3.0.1.ga

Workaround 3: uninstall and install fresh from 3.0.2 installer

> Change of JBDS installation folder name causes errors
> -----------------------------------------------------
>
>                 Key: JBDS-1334
>                 URL: https://jira.jboss.org/browse/JBDS-1334
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: runtime
>    Affects Versions: 3.0.1.GA
>         Environment: JBDS 3.0.1.ga, resp 3.0.2ga, Linux 64
>            Reporter: Jiri Peterka
>         Attachments: repo-not-found-after-renaming.png
>
>
> Situation can be like this:
> 1. you have installed JBDS 3.0.1.ga into /opt/ide/jbds-3.0.1.ga
> 2. when 3.0.2 is ready you want to  upgrade JBDS 3.0.2 through p2 update site
> 3. after upgrade you would like to rename your jbds foldet to /opt/ide/jbds/3.0.2.ga
> After that you will get p2 repo errors after JBDS start 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira