m.g.o-public -> repo.jenkins-ci.org/public

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

m.g.o-public -> repo.jenkins-ci.org/public

kohsuke Kawaguchi (CB)

We've been using http://maven.glassfish.org/ for resolving all the
artifacts for building core and plugins. But it has been down for the
past two days and we have no ETA.

So I propose we switch to http://repo.jenkins-ci.org/public.


This issue was raised several times in the past that we rely on a 3rd
party repository we have on control over. It was simply an inertia from
earlier days when I was in the Glassfish team (and even had the physical
access to the system!), and the migration never really came high enough
in the priority list, until this outage.

http://repo.jenkins-ci.org/ is a hosted Artifactory, operated by JFrog.
They kindly let us use their service for free (thanks JFrog!) It was
started several weeks ago after a discussion in the project meeting, and
the original motivation was to migrate from self-managed
http://maven.jenkins-ci.org/

That migration work is still in the proof-of-concept phase, and more on
that in the upcoming project meeting, but in the mean time, we can and
we should fast-track maven.glassfish.org migration since it has a bigger
impact on our development.

The core and super POM have already been modified to use this new
repository, and it works well. The plugin parent POM will have this new
location starting 1.453, but if you depend on earlier parent POMs, you
can specify the following fragment in your plugin POM to make this resolve:

   <repositories>
     <repository>
       <id>repo.jenkins-ci.org</id>
       <url>http://repo.jenkins-ci.org/public/</url>
     </repository>
   </repositories>

   <pluginRepositories>
     <pluginRepository>
       <id>repo.jenkins-ci.org</id>
       <url>http://repo.jenkins-ci.org/public/</url>
     </pluginRepository>
   </pluginRepositories>


Also, adding the following fragment to your ~/.m2/settings.xml will make
your Maven use the new repository whenever m.g.o-public is referenced.

<settings>
   <mirrors>
     <mirror>
       <id>repo.jenkins-ci.org</id>
       <url>http://repo.jenkins-ci.org/public/</url>
       <mirrorOf>m.g.o-public</mirrorOf>
     </mirror>

This time, we are using the *.jenkins-ci.org URL. Even if JFrog goes
belly up tomorrow, we just need to make a few DNS/redirect adjustments
to be able to keep this new URL working. So this should be the last time
we need to make this kind of migration.



--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins
Reply | Threaded
Open this post in threaded view
|

Re: m.g.o-public -> repo.jenkins-ci.org/public

cactusman
If jenkins/pom.xml was changed to repo.jenkins-ci.org from
m.g.o-public, building jenkins was success.

thx kohsuke!


2012/3/1 Kohsuke Kawaguchi <[hidden email]>:

>
> We've been using http://maven.glassfish.org/ for resolving all the artifacts
> for building core and plugins. But it has been down for the past two days
> and we have no ETA.
>
> So I propose we switch to http://repo.jenkins-ci.org/public.
>
>
> This issue was raised several times in the past that we rely on a 3rd party
> repository we have on control over. It was simply an inertia from earlier
> days when I was in the Glassfish team (and even had the physical access to
> the system!), and the migration never really came high enough in the
> priority list, until this outage.
>
> http://repo.jenkins-ci.org/ is a hosted Artifactory, operated by JFrog. They
> kindly let us use their service for free (thanks JFrog!) It was started
> several weeks ago after a discussion in the project meeting, and the
> original motivation was to migrate from self-managed
> http://maven.jenkins-ci.org/
>
> That migration work is still in the proof-of-concept phase, and more on that
> in the upcoming project meeting, but in the mean time, we can and we should
> fast-track maven.glassfish.org migration since it has a bigger impact on our
> development.
>
> The core and super POM have already been modified to use this new
> repository, and it works well. The plugin parent POM will have this new
> location starting 1.453, but if you depend on earlier parent POMs, you can
> specify the following fragment in your plugin POM to make this resolve:
>
>  <repositories>
>    <repository>
>      <id>repo.jenkins-ci.org</id>
>      <url>http://repo.jenkins-ci.org/public/</url>
>    </repository>
>  </repositories>
>
>  <pluginRepositories>
>    <pluginRepository>
>      <id>repo.jenkins-ci.org</id>
>      <url>http://repo.jenkins-ci.org/public/</url>
>    </pluginRepository>
>  </pluginRepositories>
>
>
> Also, adding the following fragment to your ~/.m2/settings.xml will make
> your Maven use the new repository whenever m.g.o-public is referenced.
>
> <settings>
>  <mirrors>
>    <mirror>
>      <id>repo.jenkins-ci.org</id>
>      <url>http://repo.jenkins-ci.org/public/</url>
>      <mirrorOf>m.g.o-public</mirrorOf>
>    </mirror>
>
> This time, we are using the *.jenkins-ci.org URL. Even if JFrog goes belly
> up tomorrow, we just need to make a few DNS/redirect adjustments to be able
> to keep this new URL working. So this should be the last time we need to
> make this kind of migration.
>
>
>
> --
> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
> Try Nectar, our professional version of Jenkins



--
cactusman
Reply | Threaded
Open this post in threaded view
|

Re: m.g.o-public -> repo.jenkins-ci.org/public

Ulli Hafner
In reply to this post by kohsuke Kawaguchi (CB)
Does that mean we should release plug-ins to repo.jenkins-ci.org instead
of maven.jenkins-ci.org now?

Ulli


On 03/01/2012 04:11 AM, Kohsuke Kawaguchi wrote:

>
> We've been using http://maven.glassfish.org/ for resolving all the
> artifacts for building core and plugins. But it has been down for the
> past two days and we have no ETA.
>
> So I propose we switch to http://repo.jenkins-ci.org/public.
>
>
> This issue was raised several times in the past that we rely on a 3rd
> party repository we have on control over. It was simply an inertia
> from earlier days when I was in the Glassfish team (and even had the
> physical access to the system!), and the migration never really came
> high enough in the priority list, until this outage.
>
> http://repo.jenkins-ci.org/ is a hosted Artifactory, operated by
> JFrog. They kindly let us use their service for free (thanks JFrog!)
> It was started several weeks ago after a discussion in the project
> meeting, and the original motivation was to migrate from self-managed
> http://maven.jenkins-ci.org/
>
> That migration work is still in the proof-of-concept phase, and more
> on that in the upcoming project meeting, but in the mean time, we can
> and we should fast-track maven.glassfish.org migration since it has a
> bigger impact on our development.
>
> The core and super POM have already been modified to use this new
> repository, and it works well. The plugin parent POM will have this
> new location starting 1.453, but if you depend on earlier parent POMs,
> you can specify the following fragment in your plugin POM to make this
> resolve:
>
>   <repositories>
>     <repository>
>       <id>repo.jenkins-ci.org</id>
>       <url>http://repo.jenkins-ci.org/public/</url>
>     </repository>
>   </repositories>
>
>   <pluginRepositories>
>     <pluginRepository>
>       <id>repo.jenkins-ci.org</id>
>       <url>http://repo.jenkins-ci.org/public/</url>
>     </pluginRepository>
>   </pluginRepositories>
>
>
> Also, adding the following fragment to your ~/.m2/settings.xml will
> make your Maven use the new repository whenever m.g.o-public is
> referenced.
>
> <settings>
>   <mirrors>
>     <mirror>
>       <id>repo.jenkins-ci.org</id>
>       <url>http://repo.jenkins-ci.org/public/</url>
>       <mirrorOf>m.g.o-public</mirrorOf>
>     </mirror>
>
> This time, we are using the *.jenkins-ci.org URL. Even if JFrog goes
> belly up tomorrow, we just need to make a few DNS/redirect adjustments
> to be able to keep this new URL working. So this should be the last
> time we need to make this kind of migration.
>
>
>
   
Reply | Threaded
Open this post in threaded view
|

Re: m.g.o-public -> repo.jenkins-ci.org/public

Ramón Rial
In reply to this post by kohsuke Kawaguchi (CB)
Sorry, but it doesn't works for my plugin.

My plugin is based on 1.436.

My settings.xml is:


        <pluginGroups>
                <pluginGroup>org.jenkins-ci.tools</pluginGroup>
        </pluginGroups>
        <mirrors>
                <mirror>
                        <id>repo.jenkins-ci.org</id>
                        <url>http://repo.jenkins-ci.org/public/</url>
                        <mirrorOf>m.g.o-public</mirrorOf>
                </mirror>
        </mirrors>
        <profiles>
    <!-- Give access to Jenkins plugins -->
                <profile>
                        <id>jenkins</id>
                        <activation>
                                <activeByDefault>true</activeByDefault> <!-- change this to false,
if you don't like to have it on per default -->
                        </activation>
                        <repositories>
                                <repository>
                                        <id>maven.jenkins-ci.org</id>
                                        <url>http://maven.jenkins-ci.org/content/groups/artifacts/</url>
                                </repository>
                        </repositories>
                        <pluginRepositories>
                                <pluginRepository>
                                        <id>maven.jenkins-ci.org</id>
                                        <url>http://maven.jenkins-ci.org/content/groups/artifacts/</url>
                                </pluginRepository>
                        </pluginRepositories>
                </profile>
        </profiles>

And my pom.xml has the repositories:

        <repositories>
                <repository>
                        <id>m.g.o-public</id>
                        <url>http://maven.glassfish.org/content/groups/public/</url>
                </repository>
                <repository>
                        <id>repo.jenkins-ci.org</id>
                        <url>http://repo.jenkins-ci.org/public/</url>
                </repository>
        </repositories>

        <pluginRepositories>
                <pluginRepository>
                        <id>m.g.o-public</id>
                        <url>http://maven.glassfish.org/content/groups/public/</url>
                </pluginRepository>
                <pluginRepository>
                        <id>repo.jenkins-ci.org</id>
                        <url>http://repo.jenkins-ci.org/public/</url>
                </pluginRepository>
        </pluginRepositories>

Is anything wrong with my configuration?

On 1 mar, 04:11, Kohsuke Kawaguchi <[hidden email]> wrote:

> We've been usinghttp://maven.glassfish.org/for resolving all the
> artifacts for building core and plugins. But it has been down for the
> past two days and we have no ETA.
>
> So I propose we switch tohttp://repo.jenkins-ci.org/public.
>
> This issue was raised several times in the past that we rely on a 3rd
> party repository we have on control over. It was simply an inertia from
> earlier days when I was in the Glassfish team (and even had the physical
> access to the system!), and the migration never really came high enough
> in the priority list, until this outage.
>
> http://repo.jenkins-ci.org/is a hosted Artifactory, operated by JFrog.
> They kindly let us use their service for free (thanks JFrog!) It was
> started several weeks ago after a discussion in the project meeting, and
> the original motivation was to migrate from self-managedhttp://maven.jenkins-ci.org/
>
> That migration work is still in the proof-of-concept phase, and more on
> that in the upcoming project meeting, but in the mean time, we can and
> we should fast-track maven.glassfish.org migration since it has a bigger
> impact on our development.
>
> The core and super POM have already been modified to use this new
> repository, and it works well. The plugin parent POM will have this new
> location starting 1.453, but if you depend on earlier parent POMs, you
> can specify the following fragment in your plugin POM to make this resolve:
>
>    <repositories>
>      <repository>
>        <id>repo.jenkins-ci.org</id>
>        <url>http://repo.jenkins-ci.org/public/</url>
>      </repository>
>    </repositories>
>
>    <pluginRepositories>
>      <pluginRepository>
>        <id>repo.jenkins-ci.org</id>
>        <url>http://repo.jenkins-ci.org/public/</url>
>      </pluginRepository>
>    </pluginRepositories>
>
> Also, adding the following fragment to your ~/.m2/settings.xml will make
> your Maven use the new repository whenever m.g.o-public is referenced.
>
> <settings>
>    <mirrors>
>      <mirror>
>        <id>repo.jenkins-ci.org</id>
>        <url>http://repo.jenkins-ci.org/public/</url>
>        <mirrorOf>m.g.o-public</mirrorOf>
>      </mirror>
>
> This time, we are using the *.jenkins-ci.org URL. Even if JFrog goes
> belly up tomorrow, we just need to make a few DNS/redirect adjustments
> to be able to keep this new URL working. So this should be the last time
> we need to make this kind of migration.
>
> --
> Kohsuke Kawaguchi | CloudBees, Inc. |http://cloudbees.com/
> Try Nectar, our professional version of Jenkins
Reply | Threaded
Open this post in threaded view
|

Re: m.g.o-public -> repo.jenkins-ci.org/public

kohsuke Kawaguchi (CB)
In reply to this post by Ulli Hafner
On 03/01/2012 01:41 AM, Ullrich Hafner wrote:
> Does that mean we should release plug-ins to repo.jenkins-ci.org instead
> of maven.jenkins-ci.org now?

That's the work in the "proof of concept" phase. For now, just continue
to deploy to maven.jenkins-ci.org.

If PoC is successful, we should be able to proxy maven.jenkins-ci.org
such that you won't see any changes in your deployment workflow.

>
> Ulli
>
>
> On 03/01/2012 04:11 AM, Kohsuke Kawaguchi wrote:
>>
>>  We've been using http://maven.glassfish.org/ for resolving all the
>>  artifacts for building core and plugins. But it has been down for the
>>  past two days and we have no ETA.
>>
>>  So I propose we switch to http://repo.jenkins-ci.org/public.
>>
>>
>>  This issue was raised several times in the past that we rely on a 3rd
>>  party repository we have on control over. It was simply an inertia
>>  from earlier days when I was in the Glassfish team (and even had the
>>  physical access to the system!), and the migration never really came
>>  high enough in the priority list, until this outage.
>>
>>  http://repo.jenkins-ci.org/ is a hosted Artifactory, operated by
>>  JFrog. They kindly let us use their service for free (thanks JFrog!)
>>  It was started several weeks ago after a discussion in the project
>>  meeting, and the original motivation was to migrate from self-managed
>>  http://maven.jenkins-ci.org/
>>
>>  That migration work is still in the proof-of-concept phase, and more
>>  on that in the upcoming project meeting, but in the mean time, we can
>>  and we should fast-track maven.glassfish.org migration since it has a
>>  bigger impact on our development.
>>
>>  The core and super POM have already been modified to use this new
>>  repository, and it works well. The plugin parent POM will have this
>>  new location starting 1.453, but if you depend on earlier parent POMs,
>>  you can specify the following fragment in your plugin POM to make this
>>  resolve:
>>
>>    <repositories>
>>      <repository>
>>        <id>repo.jenkins-ci.org</id>
>>        <url>http://repo.jenkins-ci.org/public/</url>
>>      </repository>
>>    </repositories>
>>
>>    <pluginRepositories>
>>      <pluginRepository>
>>        <id>repo.jenkins-ci.org</id>
>>        <url>http://repo.jenkins-ci.org/public/</url>
>>      </pluginRepository>
>>    </pluginRepositories>
>>
>>
>>  Also, adding the following fragment to your ~/.m2/settings.xml will
>>  make your Maven use the new repository whenever m.g.o-public is
>>  referenced.
>>
>>  <settings>
>>    <mirrors>
>>      <mirror>
>>        <id>repo.jenkins-ci.org</id>
>>        <url>http://repo.jenkins-ci.org/public/</url>
>>        <mirrorOf>m.g.o-public</mirrorOf>
>>      </mirror>
>>
>>  This time, we are using the *.jenkins-ci.org URL. Even if JFrog goes
>>  belly up tomorrow, we just need to make a few DNS/redirect adjustments
>>  to be able to keep this new URL working. So this should be the last
>>  time we need to make this kind of migration.
>>
>>
>>
>
> .
>


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins
Reply | Threaded
Open this post in threaded view
|

Re: m.g.o-public -> repo.jenkins-ci.org/public

kohsuke Kawaguchi (CB)
In reply to this post by Ramón Rial

What is this plugin, and what's the error you get?

On 03/01/2012 02:27 AM, Coutemeier wrote:

> Sorry, but it doesn't works for my plugin.
>
> My plugin is based on 1.436.
>
> My settings.xml is:
>
>
> <pluginGroups>
> <pluginGroup>org.jenkins-ci.tools</pluginGroup>
> </pluginGroups>
> <mirrors>
> <mirror>
> <id>repo.jenkins-ci.org</id>
> <url>http://repo.jenkins-ci.org/public/</url>
> <mirrorOf>m.g.o-public</mirrorOf>
> </mirror>
> </mirrors>
> <profiles>
>      <!-- Give access to Jenkins plugins -->
> <profile>
> <id>jenkins</id>
> <activation>
> <activeByDefault>true</activeByDefault>  <!-- change this to false,
> if you don't like to have it on per default -->
> </activation>
> <repositories>
> <repository>
> <id>maven.jenkins-ci.org</id>
> <url>http://maven.jenkins-ci.org/content/groups/artifacts/</url>
> </repository>
> </repositories>
> <pluginRepositories>
> <pluginRepository>
> <id>maven.jenkins-ci.org</id>
> <url>http://maven.jenkins-ci.org/content/groups/artifacts/</url>
> </pluginRepository>
> </pluginRepositories>
> </profile>
> </profiles>
>
> And my pom.xml has the repositories:
>
> <repositories>
> <repository>
> <id>m.g.o-public</id>
> <url>http://maven.glassfish.org/content/groups/public/</url>
> </repository>
> <repository>
> <id>repo.jenkins-ci.org</id>
> <url>http://repo.jenkins-ci.org/public/</url>
> </repository>
> </repositories>
>
> <pluginRepositories>
> <pluginRepository>
> <id>m.g.o-public</id>
> <url>http://maven.glassfish.org/content/groups/public/</url>
> </pluginRepository>
> <pluginRepository>
> <id>repo.jenkins-ci.org</id>
> <url>http://repo.jenkins-ci.org/public/</url>
> </pluginRepository>
> </pluginRepositories>
>
> Is anything wrong with my configuration?
>
> On 1 mar, 04:11, Kohsuke Kawaguchi<[hidden email]>  wrote:
>>  We've been usinghttp://maven.glassfish.org/for resolving all the
>>  artifacts for building core and plugins. But it has been down for the
>>  past two days and we have no ETA.
>>
>>  So I propose we switch tohttp://repo.jenkins-ci.org/public.
>>
>>  This issue was raised several times in the past that we rely on a 3rd
>>  party repository we have on control over. It was simply an inertia from
>>  earlier days when I was in the Glassfish team (and even had the physical
>>  access to the system!), and the migration never really came high enough
>>  in the priority list, until this outage.
>>
>>  http://repo.jenkins-ci.org/is a hosted Artifactory, operated by JFrog.
>>  They kindly let us use their service for free (thanks JFrog!) It was
>>  started several weeks ago after a discussion in the project meeting, and
>>  the original motivation was to migrate from self-managedhttp://maven.jenkins-ci.org/
>>
>>  That migration work is still in the proof-of-concept phase, and more on
>>  that in the upcoming project meeting, but in the mean time, we can and
>>  we should fast-track maven.glassfish.org migration since it has a bigger
>>  impact on our development.
>>
>>  The core and super POM have already been modified to use this new
>>  repository, and it works well. The plugin parent POM will have this new
>>  location starting 1.453, but if you depend on earlier parent POMs, you
>>  can specify the following fragment in your plugin POM to make this resolve:
>>
>>      <repositories>
>>        <repository>
>>          <id>repo.jenkins-ci.org</id>
>>          <url>http://repo.jenkins-ci.org/public/</url>
>>        </repository>
>>      </repositories>
>>
>>      <pluginRepositories>
>>        <pluginRepository>
>>          <id>repo.jenkins-ci.org</id>
>>          <url>http://repo.jenkins-ci.org/public/</url>
>>        </pluginRepository>
>>      </pluginRepositories>
>>
>>  Also, adding the following fragment to your ~/.m2/settings.xml will make
>>  your Maven use the new repository whenever m.g.o-public is referenced.
>>
>>  <settings>
>>      <mirrors>
>>        <mirror>
>>          <id>repo.jenkins-ci.org</id>
>>          <url>http://repo.jenkins-ci.org/public/</url>
>>          <mirrorOf>m.g.o-public</mirrorOf>
>>        </mirror>
>>
>>  This time, we are using the *.jenkins-ci.org URL. Even if JFrog goes
>>  belly up tomorrow, we just need to make a few DNS/redirect adjustments
>>  to be able to keep this new URL working. So this should be the last time
>>  we need to make this kind of migration.
>>
>>  --
>>  Kohsuke Kawaguchi | CloudBees, Inc. |http://cloudbees.com/
>>  Try Nectar, our professional version of Jenkins
>


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins
Reply | Threaded
Open this post in threaded view
|

Re: m.g.o-public -> repo.jenkins-ci.org/public

Ramón Rial
It is a new plugin.
I am using maven 2.2.1 to develop the plugin, with jdk 1.6. and
Eclipse Indigo with embbeded Maven 3.0.
When I try to compile from command line I get this errors:

/mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/myPlugin/
PomXmlManager.java:[20,19] package hudson.maven does not exist
[ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/
myPlugin/PomXmlManager.java:[21,19] package hudson.maven does not
exist
[ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/
myPlugin/PomXmlManager.java:[20,19] package hudson.maven does not
exist
[ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/
myPlugin/PomXmlManager.java:[21,19] package hudson.maven does not
exist
[ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/
myPlugin/PomXmlManager.java:[70,2] cannot find symbol
[ERROR] symbol  : class MavenModuleSetBuild
[ERROR] location: class myPlugin.PomXmlManager
[ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/
myPlugin/PomXmlManager.java:[70,32] cannot find symbol
[ERROR] symbol  : class MavenModuleSetBuild
[ERROR] location: class myPlugin.PomXmlManager
[ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/
myPlugin/PomXmlManager.java:[225,10] cannot find symbol
[ERROR] symbol  : class AbstractMavenProject
[ERROR] location: class myPlugin.PomXmlManager.DescriptorImpl

The errors indicates that maven (from commandline) can not find some
classes, like hudson.maven.MavenModuleSetBuild.

But when I compile from Eclipse all it's ok. I've tried to compile
from command line with maven 3.0, but with no luck. Also I've tried
deleting the folder repository of maven (.m2).
The plugin HelloWorldPlugin works fine, but if I add the class
hudson.maven.MavenModuleSetBuild, it gives me the same error as my
plugin: hudson.maven does not exist.

Any idea?

On 1 mar, 18:13, Kohsuke Kawaguchi <[hidden email]> wrote:

> What is this plugin, and what's the error you get?
>
> On 03/01/2012 02:27 AM, Coutemeier wrote:
>
>
>
>
>
>
>
>
>
> > Sorry, but it doesn't works for my plugin.
>
> > My plugin is based on 1.436.
>
> > My settings.xml is:
>
> >    <pluginGroups>
> >            <pluginGroup>org.jenkins-ci.tools</pluginGroup>
> >    </pluginGroups>
> >    <mirrors>
> >            <mirror>
> >                    <id>repo.jenkins-ci.org</id>
> >                    <url>http://repo.jenkins-ci.org/public/</url>
> >                    <mirrorOf>m.g.o-public</mirrorOf>
> >            </mirror>
> >    </mirrors>
> >    <profiles>
> >      <!-- Give access to Jenkins plugins -->
> >            <profile>
> >                    <id>jenkins</id>
> >                    <activation>
> >                            <activeByDefault>true</activeByDefault>  <!-- change this to false,
> > if you don't like to have it on per default -->
> >                    </activation>
> >                    <repositories>
> >                            <repository>
> >                                    <id>maven.jenkins-ci.org</id>
> >                                    <url>http://maven.jenkins-ci.org/content/groups/artifacts/</url>
> >                            </repository>
> >                    </repositories>
> >                    <pluginRepositories>
> >                            <pluginRepository>
> >                                    <id>maven.jenkins-ci.org</id>
> >                                    <url>http://maven.jenkins-ci.org/content/groups/artifacts/</url>
> >                            </pluginRepository>
> >                    </pluginRepositories>
> >            </profile>
> >    </profiles>
>
> > And my pom.xml has the repositories:
>
> >    <repositories>
> >            <repository>
> >                    <id>m.g.o-public</id>
> >                    <url>http://maven.glassfish.org/content/groups/public/</url>
> >            </repository>
> >            <repository>
> >                    <id>repo.jenkins-ci.org</id>
> >                    <url>http://repo.jenkins-ci.org/public/</url>
> >            </repository>
> >    </repositories>
>
> >    <pluginRepositories>
> >            <pluginRepository>
> >                    <id>m.g.o-public</id>
> >                    <url>http://maven.glassfish.org/content/groups/public/</url>
> >            </pluginRepository>
> >            <pluginRepository>
> >                    <id>repo.jenkins-ci.org</id>
> >                    <url>http://repo.jenkins-ci.org/public/</url>
> >            </pluginRepository>
> >    </pluginRepositories>
>
> > Is anything wrong with my configuration?
>
> > On 1 mar, 04:11, Kohsuke Kawaguchi<[hidden email]>  wrote:
> >>  We've been usinghttp://maven.glassfish.org/forresolving all the
> >>  artifacts for building core and plugins. But it has been down for the
> >>  past two days and we have no ETA.
>
> >>  So I propose we switch tohttp://repo.jenkins-ci.org/public.
>
> >>  This issue was raised several times in the past that we rely on a 3rd
> >>  party repository we have on control over. It was simply an inertia from
> >>  earlier days when I was in the Glassfish team (and even had the physical
> >>  access to the system!), and the migration never really came high enough
> >>  in the priority list, until this outage.
>
> >>  http://repo.jenkins-ci.org/isa hosted Artifactory, operated by JFrog.
> >>  They kindly let us use their service for free (thanks JFrog!) It was
> >>  started several weeks ago after a discussion in the project meeting, and
> >>  the original motivation was to migrate from self-managedhttp://maven.jenkins-ci.org/
>
> >>  That migration work is still in the proof-of-concept phase, and more on
> >>  that in the upcoming project meeting, but in the mean time, we can and
> >>  we should fast-track maven.glassfish.org migration since it has a bigger
> >>  impact on our development.
>
> >>  The core and super POM have already been modified to use this new
> >>  repository, and it works well. The plugin parent POM will have this new
> >>  location starting 1.453, but if you depend on earlier parent POMs, you
> >>  can specify the following fragment in your plugin POM to make this resolve:
>
> >>      <repositories>
> >>        <repository>
> >>          <id>repo.jenkins-ci.org</id>
> >>          <url>http://repo.jenkins-ci.org/public/</url>
> >>        </repository>
> >>      </repositories>
>
> >>      <pluginRepositories>
> >>        <pluginRepository>
> >>          <id>repo.jenkins-ci.org</id>
> >>          <url>http://repo.jenkins-ci.org/public/</url>
> >>        </pluginRepository>
> >>      </pluginRepositories>
>
> >>  Also, adding the following fragment to your ~/.m2/settings.xml will make
> >>  your Maven use the new repository whenever m.g.o-public is referenced.
>
> >>  <settings>
> >>      <mirrors>
> >>        <mirror>
> >>          <id>repo.jenkins-ci.org</id>
> >>          <url>http://repo.jenkins-ci.org/public/</url>
> >>          <mirrorOf>m.g.o-public</mirrorOf>
> >>        </mirror>
>
> >>  This time, we are using the *.jenkins-ci.org URL. Even if JFrog goes
> >>  belly up tomorrow, we just need to make a few DNS/redirect adjustments
> >>  to be able to keep this new URL working. So this should be the last time
> >>  we need to make this kind of migration.
>
> >>  --
> >>  Kohsuke Kawaguchi | CloudBees, Inc. |http://cloudbees.com/
> >>  Try Nectar, our professional version of Jenkins
>
> --
> Kohsuke Kawaguchi | CloudBees, Inc. |http://cloudbees.com/
> Try Nectar, our professional version of Jenkins
Reply | Threaded
Open this post in threaded view
|

Re: m.g.o-public -> repo.jenkins-ci.org/public

rin_ne
In reply to this post by kohsuke Kawaguchi (CB)
When I built gerrit-trigger-plugin with suggested repository, It
failed due to dependency.

gerrit-trigger-plugin -> git-plugin 1.1.10 -> jgit 0.12.1

jgit 0.12.1 is not hosted in this repository (Also eclipse one)

Next, I changed jgit version to hosted version(1.3.0.201202151440-r)
in git-plugin source then built. But it still failed due to "missing
org/apache/maven/project/ProjectBuildngRequest".

I found below thread:
http://jenkins.361315.n4.nabble.com/Error-building-Jenkins-td3454428.html

I think my facing error is the same since I build it on Ubuntu (maven 2.2.1).
Reply | Threaded
Open this post in threaded view
|

Re: m.g.o-public -> repo.jenkins-ci.org/public

nicolas de loof-2
Indeed, maven 3 is a requirement
I suppose you installed maven using the system package, so are loked to 2.2.x ?
precise will have maven 3 (http://packages.ubuntu.com/precise/maven), in the meantime you can simply install the tar.gz distribution from apache.org

2012/3/15 柏木りんね <[hidden email]>
When I built gerrit-trigger-plugin with suggested repository, It
failed due to dependency.

gerrit-trigger-plugin -> git-plugin 1.1.10 -> jgit 0.12.1

jgit 0.12.1 is not hosted in this repository (Also eclipse one)

Next, I changed jgit version to hosted version(1.3.0.201202151440-r)
in git-plugin source then built. But it still failed due to "missing
org/apache/maven/project/ProjectBuildngRequest".

I found below thread:
http://jenkins.361315.n4.nabble.com/Error-building-Jenkins-td3454428.html

I think my facing error is the same since I build it on Ubuntu (maven 2.2.1).

Reply | Threaded
Open this post in threaded view
|

Re: m.g.o-public -> repo.jenkins-ci.org/public

rin_ne
Yes it will success with maven3. I can build git-plugin using maven3 PPA.

But gerrit-trigger-plugin needs one setting. It's jgit-repository.
repo.jenkins-ci.org does not have the past packages (e.g. jgit 0.12.1)

It means that almost plugin owner should rebuild plugin if switch repository.
Reply | Threaded
Open this post in threaded view
|

Re: m.g.o-public -> repo.jenkins-ci.org/public

rin_ne