[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Installing plug-ins from a local folder

Sorry, there were quite a few issues we faced with p2 and links. It took some time for me to gather the info and summarize. Here is the list

1) The plugins & features installed via links through p2 don't have uninstall enabled from the software update manager UI. However, they are shown under the installed software tab. Every plugin if its installed through p2 should be uninstalled through p2. That's the p2 rule, right. So, i find this missing for the links approach.
2) If the link file is deleted from the dropins/links folder, then the plugins are still loaded. Effective, once plugins and features are installed into eclipse via links there is no way to uninstall them !!
3) Deleting the directory referred in the links file seems to work properly, but sometimes we observed that the eclipse crashed without loading. This is intermittent and can be ignored i guess.
4) If the directory referred in the links file is updated, then the update is not reflected properly. For example, i had an old clear case plugin installed. I copied a new clearcase version into the same directory. p2 still loaded the previous version. Then I deleted the previous version and loaded the new plugin alone from the same directory, it too didn't work. p2 update manager showed the older version still in the installed software tab, while "manage configuration" showed some errors. The basic motto is the service pack installation. We ship our plugins and service pack plugins in the same directory and the directory is referred by links file and we want the newest plugins to be picked up from this directory. The workaround we found for this problem is to run clean using p2 director application.

eclipse.exe -nosplash -consolelog -application org.eclipse.equinox.p2.director.app.application -clean

5) Sometimes, I don't have the exact reproducible steps, but observed it quite often, is the following annoying behavior. When the release and service pack features and plugins are in the same directory, and that directory is referred by the links file, then the feature picked up is always the latest. However, some of the plugins are of release version and some of service pack version. Here is a post that describes the problem.
http://dev.eclipse.org/newslists/news.eclipse.technology.equinox/msg05430.html

I am not sure if there are bugs logged concerning these issues, but some of the above are blockers for us to use the links approach using p2. Its so painful to try a lot of approaches for a simple case of loading local plugins and yet no working solution. This should have been one of the basic use case that p2 should support right?

So, back to my original question.
I want to know the p2 recommended mechanism in eclipse 3.4 of loading plug-ins using p2 from a local folder.
However,
1) there shouldn't be any copy of the plug-ins created for this purpose (using local site copies the plugins/features to eclipse plugins/features) and
2) if the local folder gets updated the p2 should automatically install/uninstall the plug-ins (this is not working using links).



Thanks,
Ravi.
2009/2/26 DJ Houghton <DJ_Houghton@xxxxxxxxxx>

What problems are you experiencing with p2 and link files? I did a quick bugzilla search and see no bugs that you've entered or are CC'd on.




Inactive hide details for Ravi Sankar V <v.r.sankar@xxxxxxxxx>Ravi Sankar V <v.r.sankar@xxxxxxxxx>



To

P2 developer discussions <p2-dev@xxxxxxxxxxx>

cc


Subject

Re: [p2-dev] Installing plug-ins from a local folder

There are some problems with p2 & link files. Link files are supported only for backward compatibility. Thats why I asked for p2 recommended approach.

--
Ravi.

2009/2/26 Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
    Why can't you use link files then?

    Inactive hide details for Ravi Sankar V ---02/26/2009 11:11:38 AM---I am not too acquanited with the bundle pool and touchpointRavi Sankar V ---02/26/2009 11:11:38 AM---I am not too acquanited with the bundle pool and touchpoints. I'll read up the wiki. The ideal case,


From:

Ravi Sankar V <v.r.sankar@xxxxxxxxx>

To:

P2 developer discussions <p2-dev@xxxxxxxxxxx>

Date:

02/26/2009 11:11 AM

Subject:

Re: [p2-dev] Installing plug-ins from a local folder





    I am not too acquanited with the bundle pool and touchpoints. I'll read up the wiki. The ideal case, I need is something similar to the links file, I would need p2 to update its configuration if the folder pointed by the link file is modified or the link file itself is removed.


    Cheers,
    Ravi.


    2009/2/26 Pascal Rapicault <
    Pascal_Rapicault@xxxxxxxxxx>
        The current behaviour is to copy because p2 does not trust the user to not delete the folder and break himself. What would be needed for this to work is to have the eclipse touchpoint see this folder as a bundle pool.
        As long as the folder is listed in the repository, then the update detected.

        Inactive hide details for Ravi Sankar V ---02/26/2009 07:34:47 AM---Hi, I want to know the p2 recommended mechanism in eclipse Ravi Sankar V ---02/26/2009 07:34:47 AM---Hi, I want to know the p2 recommended mechanism in eclipse 3.4 of loading

    From:

    Ravi Sankar V <
    v.r.sankar@xxxxxxxxx>

    To:

    p2-dev@xxxxxxxxxxx

    Date:

    02/26/2009 07:34 AM

    Subject:

    [p2-dev] Installing plug-ins from a local folder





        Hi,

        I want to know the p2 recommended mechanism in eclipse 3.4 of loading plug-ins using p2 from a local folder.
        However,
        1) there shouldn't be any copy of the plug-ins created for this purpose (using local site copies the plugins/features to eclipse plugins/features) and
        2) if the local folder gets updated the p2 should automatically install/uninstall the plug-ins (this is not working using links).

        Thanks in anticipation,
        Ravi.

        _______________________________________________
        p2-dev mailing list

        p2-dev@xxxxxxxxxxx
        https://dev.eclipse.org/mailman/listinfo/p2-dev



        _______________________________________________
        p2-dev mailing list

        p2-dev@xxxxxxxxxxx
        https://dev.eclipse.org/mailman/listinfo/p2-dev
    _______________________________________________
    p2-dev mailing list

    p2-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/p2-dev



    _______________________________________________
    p2-dev mailing list

    p2-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev


_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev


GIF image

GIF image

GIF image

GIF image