[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Issue running p2 director

If you want to install an entire update site you can use repo2runnable to fetch the site's contents and unpack the jars that need unpacking. Put the resulting files in eclipse/dropins, and you'll have everything "installed."

[1] http://wiki.eclipse.org/Equinox/p2/Ant_Tasks#Repo2Runnable

Of course this approach means you can't easily uninstall using the p2 UI (only by moving/deletind files by hand), and you'll end up installing way more than you actually need. But it's a single operation, which might be what you want.

Aside: is pasta A "incompatible" with pasta B? Seems a bad analogy - perhaps a better one would be sauces -- mixing teriyaki with bolognese would be bad, for example. :)


Pascal Rapicault wrote:
The short answer is no. There is no mechanism to install all the elements found in a category and there is no problem with the EMF repo.

The top level node you select in the UI is a category. It is a user-focused grouping mechanism that allows for "better / easier" presentation of content when browsing a repository. The fact that such a category is selectable in the UI is a result of backward compatibility behaviour with the previous Eclipse Update Manager. To me this has always been a weird thing to select a group, since it may contains things that are incompatible with each others. When you go to the grocery store in the past alley, do you buy a package of each sort of pasta?

Inactive hide details for RE: [p2-dev] Issue running p2 directorRE: [p2-dev] Issue running p2 director

*RE: [p2-dev] Issue running p2 director*

*Dalton, Tom * to: P2 developer discussions 09/11/2009 09:47 AM

Sent by:	

*Please respond to P2 developer discussions*	


I have one more slightly-related question. I am installing the features from the EMP .zip update site by using org.eclipse.emf.feature.group and org.eclipse.xsd.feature.group. However, when I run up eclipse and look at the installed plugins, not everything from the site is installed. I can go back and manually point the UI at the zip and install the extra components, but I don't understand how/why the feature groups don't pick up all the features - all features in the site .zip are org.eclipse.emf.* or org.eclipse.xsd.*

Is this another bug in the EMF site? As a workaround, rather than have to specify every feature to be installed one by one, is it possible to tell P2 director to install every feature from the site, mirroring the UI behaviour as if you click the top-level group in the "feature tree"?

Thanks for your help so far!



*From:* p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Dalton, Tom*
Sent:* 11 September 2009 12:27*
To:* P2 developer discussions*
Subject:* RE: [p2-dev] Issue running p2 director

            Thank you for the response - I'll let the EMF team know
            there's a problem at their end.

            Using the jar:file type URI to point at the .zip seems to
            work in the meantime, so I'm a very happy bunny.


                        *From:* p2-dev-bounces@xxxxxxxxxxx
                        [mailto:p2-dev-bounces@xxxxxxxxxxx] *On Behalf
                        Of *Pascal Rapicault*
                        Sent:* 10 September 2009 18:00*
                        To:* P2 developer discussions*
                        Cc:* p2-dev@xxxxxxxxxxx; p2-dev-bounces@xxxxxxxxxxx*
                        Subject:* Re: [p2-dev] Issue running p2 director

                        The artifact repository contained in this
                        archive is inconsistent. It has been made
                        inconsistent by the EMF build process which
                        deletes the canonical jars to only leave the
                        pack'ed one, but does not update the artifact
                        repository index (artifacts.jar) to reflect this
                        change. Please report this problem to the EMF team.

                        The reason why this is working in the case of a
                        zip'ed repo is because p2 treats it as a
                        non-local repo and installs from the pack file
                        which it finds. However when the repository is
                        exploded on the file system, p2 first tries to
                        download the JAR because the artifact repository
                        index (artifacts.jar) indicates that it contains
                        it even though it does not have it. If this
                        reference had not been available in the artifact
                        repo index, then p2 would have resorted to use
                        the pack'ed files.
                        That said, the code in MirrorRequest#perform in
                        the p2.artifact.repository bundle could be made
                        for insistent and try every descriptor rather
                        than just the first one.

                        Did you try to point the director app at the
                        archive using as a repository the JAR URI
                        (jar:file:/c:/archive.zip!/ or see the URI that
                        gets created for you when you add the archive
                        through the UI)?

                        Inactive hide details for [p2-dev] Issue running
                        p2 director[p2-dev] Issue running p2 director

*[p2-dev] Issue running p2 director*

                        Dalton, Tom *	
                        09/10/2009 06:57 AM

                        Sent by:	*

                        *Please respond to P2 developer discussions*	



                        I'm using the Eclipse 3.5 CDT on a non-networked
                        machine and I want to add the EMF framework to
                        it. I have downloaded the EMF update site .zip from


                        Specifically I got

Now, if I install that update though the Eclipse UI by selecting the zip file itself, everything works. However, if I unzip the file to somewhere temporary and then try to install from that location, it gets to about 60% though and then bombs out with a mass of 'file not found' errors, because it seems to be looking for the plugins as plain .jar files instead of the actual .jar.pack.gz files.

                        This difference in behaviours seems to me to be
                        a bug, albeit with a workaround (install direct
                        from the zip rather than extracting it myself).
                        So that would be fine, except that I need to
                        automat the eclipse build (I need to add a lot
                        more than just EMF and need to do this for a lot
                        of people).

                        So I started looking at the P2 director command
                        line stuff described at:


                        And _

However, when using these methods, if I set the -repository to point at the zip file itself, it moans that its not a valid repository. If I point it at my manually unzipped directory, it starts off ok, but then bombs out with the same file not found errors as described above.

                        So two questions:
                        1. Are these file not found errors the symptoms
                        of a bug?
                        2. Is there a way to duplicate the UI
                        install-from-zip behaviour via the command line
                        P2 director (which would provide me with a
                        solution to my problem).

                        Thanks a lot for any help provided!

                        *Tom Dalton*
                        p2-dev mailing list
                        p2-dev mailing list


p2-dev mailing list

-- Nick Boldt :: http://nick.divbyzero.com Release Engineer :: Eclipse Modeling & Dash Athena