Thanks for the link John.
This is a great document.
So let's assume following scenario:
I bought 1000 licenses of RAD or JBoss Developer Studio, they're 3.5
based.
I need to customize them to simplify the deployment: set only single
intranet repo with approved packages (checkstyle, findbugs, etc...)
So I would create a feature and co-locate with it p2.inf file which has
the following content:
removeRepository(*,*);
addRepository(http://intranet.company.com/metadata,0,true);
addRepository(http://intranet.company.com/artifacts,1,true);
as a last step, I'd have to install that feature before distributing my
custom app.
correct?
John Arthorne pisze:
In 3.5 you no longer need to
manually
hack these files. There are touchpoint instructions that all your
bundle/feature/product
to add or remove repositories from the profile programmatically. See
the
"AddRepository" and "RemoveRepository" actions on this
page:
http://wiki.eclipse.org/Equinox_p2_Touchpoint_Instructions
John
Hello p2 :-)
In 3.4 I learned to love and take care of this two files:
configuration\.settings\org.eclipse.equinox.p2.artifact.repository.prefs
configuration\.settings\org.eclipse.equinox.p2.metadata.repository.prefs
thanks to them I was able to set predefined p2 repositories list, or
remove the Ganymede default ones in my custom product.
Now since 3.5M6 I don't see those files, so how could I remove default
update sites or add my custom ones?
Thanks!
Jacek
_______________________________________________
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
|
