Our issue isn't with deploying some artifacts prematurely when an install
fails - that's not normally a problem, since we've generally done at least
one successful mvn install before doing an mvn deploy.
The issue is that when we're in RC phase, we want to give our artifacts
version numbers as
We can run mvn deploy whenever we make an RC build - however, the problem
with that ends up being that we are deploying artifacts to our repository
that may not be the final release. That's what we want to avoid - while we
can re-deploy if we end up doing a second RC, the lack of version
Hi,
Our project has many Maven artifacts, the vast majority of which are OSGi
bundles. These bundles are distributed together as part of our application
(Cytoscape), but may also be used by third-party developers using our API.
Given this, we have been deploying our artifacts to a Maven
