Sorry
for the delay in responding.
1. Open a bug report against the Technology->Dash->Maven
component. Asking for a deployment userid and password.
Entered bug 351206 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=351206)
2.
We'll need to get the Webmasters involved so they know what is
happening and so we can establish a common set of practices for
all projects going forward. My preference would be to setup on id
that Hudson can use for automatic deployments, and maybe some
other ids. Webmasters have had concerns in the past about
tracking and access, but I think we can address these.
Okay. I won't know any answers to questions they might ask me so it
might be better if you talk to the Webmasters.
3. I'll document the steps as we go, but mostly it is getting the
server portion of the settings.xml file setup right. For this
though we need to establish the userid and password. to be used
for deployment.
A Beginners Guide would be really great. We kind of need to
be spoon-fed at this point, but would be happy to document what we
see on the spoon as we eat (if that would help).
Dave
On 06/29/2011 12:11 PM, Mike Keith wrote:
Dave,
Thanks for your help. I have a few questions about the next
steps.
What account do we need and how do we get it?
Should we get an account for all of RT, or on a per-project
basis?
Is there some way we can get a step-by-step description of how
to get release bundles in the repo?
(A number of us are not strong Maven users so we would need a
fairly concise recipe to follow.)
I was wanting to enter a bug against the Nexus project but I
couldn't find the Nexus project in Bugzilla.
Where should we track this?
Thanks,
-Mike
On 6/27/2011 2:46 PM, David Carver wrote:
Yes, it is public, and anybody can
consume from it.
There is even an settings.xml that projects can use.
Dave
On 06/27/2011 11:21 AM, Mike Keith wrote:
Thanks, Dave!
We were thinking of creating a Gemini project-specific repo
but process-wise I thought it made more sense to have an
RT-wide one to save everyone creating their own. It would be
great if we could use the Nexus one to put our released
bundles in for our community that prefers maven. I assume
this repo is visible to the public to consume from?
The url is:
https://maven.eclipse.org/nexus/
If you want to deploy artifacts, I suggest inheriting from
the eclipse-parent pom file as it has the necessary
profiles setup. We'll need to figure out a user id for
you to use, if you want to use a comon id, we'll probably
need a bug request setup, so we can configure a user with
deployment rights to the Nexus repo.
Dave
On 06/27/2011 10:51 AM, Jesse McConnell wrote:
There is a nexus repo for all of
eclipse, and David is the master of it :)
As for just and RT one, I am -1 that, we should have per
project ones
for deployment, snapshots, etc and then one master
aggregate of all of
eclipse
which is what I believe david has going on
jesse
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx
On Mon, Jun 27, 2011 at 08:33, Mike
Keith<michael.keith@xxxxxxxxxx> wrote:
All,
Is there a shared maven repository that we can use to
put the releases of
our projects into?
Seems like it would be a good idea for RT to have
one...
-Mike
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc
|
