I think org.eclipse.equinox.internal.p2.tools.mirror.RepositoryMirroring
is obsolete, I'm not sure it ever really worked at all.
There is a new
but it seems to only be available through the <p2.mirror> ant
task implemented by MirrorTask. It is not exposed as a command line
which is the org.eclipse.equinox.p2.metadat.repository.mirrorApplication
command line app.
is the org.eclipse.equinox.p2.artifact.repository.mirrorApplication app.
David Perli <david.perli@xxxxxxxxxxxxxxxx> Sent by: p2-dev-bounces@xxxxxxxxxxx
05/13/2009 12:52 PM
Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>
[p2-dev] Regression in RepositoryMirroring
I am currently prototyping some experimental "p2 tools", relative
to the p2 framework.
I know that it is internal, so maybe not intended to be reused as an API.
However, I have managed a way to reuse it, but encountered one main issue
I saw that the metadata/artifact names can not be customized,
and are unconditionnally set to a default value :
String repositoryName = destinationLocation + " - metadata";
I was wondering if that was intentionnal, or a regression ?
I mean that, referring to the Eclipsepedia API, the destination repository
name could be set (in the past ?)
with the -destinationName argument.
I said it before, it can no longer be defined with this application.
However, any repository XML file still have got a name !
So, in case that it is a regression, I would modestly suggest to create
a couple of setters
(setMetadataRepositoryName, setArtifactRepositoryname) in order to correct
Am I supposed to set the name manually, reloading the created repository
with the p2 API ?
Or is this restricted access fully intentionnal ?
Thanks for the help,
Trainee at Anyware Technologies, France. _______________________________________________
p2-dev mailing list