They would but we are attempting to rev the versions internally and then publish. So if we accidentally publish a bad artifact, we'd like to remove it and then re-publish without changing the version. Also repository size may be a concern.
Thanks for your help!
No, this is not a capability that the publisher applications have. Their goal is to be straightforward and dumb J Read
some files produce some metadata.
But I would ask, if you have different features what would not they have a different version?
Sorry, I misspoke earlier. We *are* using the Features and Bundles publisher (org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher). Is there an option that we can pass in to remove a feature that has already been published? I see the p2.remove.iu
task. Is there a command line option to pass this to the features and bundles publisher application?
There is an ant task called p2.remove.iu  that allows to remove IUs from a repository. Note that if this repo has been “put in production” this is not recommended
as users may rely on the IUs you want to remove.
Another way to easily deal with repos is to use composite repository and publish different builds (assuming that this is what you are trying to do) in different repos.
Finally the p2 director is not used to add and remove to a repo. This is the role of the publisher. The director is the tool that performs the installation
We are using the p2 director to publish features and bundles to a p2 site. Is there a way to uninstall features from the p2 update site?
p2-dev mailing list