You don't need to give anybody access to your proprietary artifacts.
You can add an additional repository within the same Nexus instance and
have that repo proxy the Tapestry staging repo.
On Mon, 10 Oct 2011 21:35:19 +0200, Lenny Primak <[email protected]>
wrote:
Not all users can have access to our proprietary artifacts in our nexus
repository,
so having everyone through it and it having to proxy tapestry staging is
a no-go.
And yes, given all that you said, I would still like to request an
'official' RC
or beta release, including all the processes involved.
Given all the 'no' I already heard its probably not going to happen,
but I still would like to put a request for it.
Perhaps other people would like an official beta/RC release as well.
Thank you!
On Oct 10, 2011, at 3:29 PM, Ulrich Stärk wrote:
Every release done by any Apache project has to be voted upon. If you
see "pre-releases" of other
projects in central, chances are that they have been formally approved
and voted upon by the
respective PMC. We don't do that here (anymore). Instead we make
preview builds available to the
interested audience which allows us to get feedback more frequently. We
could make a formal release,
even if it's not stable. The process is not trivial since it involves a
code freeze, creating a
branch and tag in SVN, formal checking (are the license headers ok,
etc.), updating JIRA, packaging
and signing the artifacts, etc. So we did a trade-off: Less frequent
voted-upon releases, more
preview builds. Since non-stable releases often won't find their way
into production anyway, we felt
that this modus operandi would benefit the majority. I'm sorry that
your case is different.
And I don't understand why you'd need to create a new Nexus instance.
Just proxy the Tapestry
staging repo...
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
