Re: [p2-dev] Why is the director needed during install?

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

This dependency is from the eclipse touchpoint to the publisher. It is necessary in order to generate the complete IUs for the bundles being installed from the legacy update sites (becasue when we are generating metadata for UM site we don't pull down all the bundles, but just the features).
The code is written this way so we can honor the fact that the dependency on the publisher is optional. For example if you know you only contact p2 repos.


Thomas Hallgren ---09/24/2009 08:57:36 AM---Hi,

From:	Thomas Hallgren <thomas@xxxxxxx>
To:	P2 developer discussions <p2-dev@xxxxxxxxxxx>
Date:	09/24/2009 08:57 AM
Subject:	[p2-dev] Why is the director needed during install?

---

Hi,
During install with our headless version of the director application, we 
sometimes see this error:

!ENTRY org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2009-09-24 
12:31:15.429
!MESSAGE The partial IU could not be updated. Publisher not available: 
org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.

it seems to indicate that the publisher is needed during install. After 
some investigation, I found the following code:

         Class c = null;
         try {
             c = 
Class.forName("org.eclipse.equinox.p2.publisher.eclipse.BundlesAction"); 
//$NON-NLS-1$
             if (c != null)
                 c = 
Class.forName("org.eclipse.osgi.service.resolver.PlatformAdmin"); 
//$NON-NLS-1$
         } catch (ClassNotFoundException e) {
             
LogHelper.log(Util.createError(NLS.bind(Messages.publisher_not_available, e.getMessage())));
             return null;
         }

Am I correct to assume that the if statement here is incorrect and 
really should be if (c == null)? Or is the presence of the publisher a 
prerequisite for using the PlatformAdmin?

- thomas

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