| Re: [p2-dev] touchpoint actions and feature artifacts |
> Simon Kaegi wrote:
> >
> > > <stuff deleted>
> > > I was looking to get a hold of the feature.jar. That code was an
> > > attempt to get the feature.jar via featureIU.getArtifacts()[0].
> > >
> >
> > A feature is broken into a feature group IU and feature jar IU. What I
> > was getting at was that you were likely looking at the group iu
> > instead of the feature jar IU.
> >
>
> How would the feature jar IU be accessed from inside the
> touchpoint/action parameters?
>
Hmm... I'm not sure how to answer that as I think you might be misunderstanding what happens to a feature when it becomes an IU.
A feature "x" when published results in 2 IUs (3 if you're using root files)
1) x.feature.group (this IU will "require" the other two)
2) x.feature.jar (this contains the branding jar file)
3) x_root (if your feature's build.properties uses a root file - see http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.pde.doc.user/tasks/pde_rootfiles.htm)
If you want actions to act on the artifacts in the x.feature.jar IU then they have to be in that IU or else in an IUFragment. Here's an example I posted where I used an IUFragment to work with a root file IU -- http://dev.eclipse.org/mhonarc/lists/p2-dev/msg01567.html. The feature.jar IU could be similarly customized however unlike the root file be aware that the feature.jar IU is filtered by default as it is a holdback to how we did feature branding with update manager. For this reason I'd suggest customizing the root IU instead of the feature jar IU for now.
> >
> > > <stuff deleted>
> > >
> > > Any ideas about why this doesn't work or pointers would be appreciated.
> > >
> >
> > That code will find the artifact file for a Native artifact however
> > you are using an artifact collected by the Eclipse Touchpoint.
> >
>
> Ah so. Just for my information: are any artifacts collected by the
> native touchpoint? If so, which/what ones?
>
> > Instead you should look at
> >
> org.eclipse.equinox.internal.p2.touchpoint.eclipse.Util.getArtifactFile(...)
> > for inspiration.
> > (keep in mind that this is not and will likely never be api so a
> > snapshot might be the best approach)
> >
>
> ok.
>
> >
> > That ugliness is temporary as the artifact location can and should be
> > provided in the parameter map -- see
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=275404
> >
>
> ok, sounds good.
>
> Scott
>
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev