This really sucks IMO... we don't want to add more repositories. The more we add, the slower the build will be and the more unstable the build will be, since if one of those repos is offline, the build will fail.

Why on earth isn't Tomcat just publishing to the m2-ibiblio-rsync- repository ?

I don't think we should continue to adapt to changes like this by simply adding new repos when we find them. We need to work with the community to find a better solution... otherwise we may well end up with a repository per dependency, or per projects dependency, which would be a massive failure.

But for now I guess we don't have a choice.

I don't like it though... :-(

--jason


On Jan 19, 2007, at 12:46 PM, Paul McMahan wrote:

I'll go ahead and add tomcat's m2 repo to the root pom and bump the
version to 6.0.8.  If there are any concerns with that approach then
please let me know and I'll move the repo to the specific modules.
We can remove this reference altogether when tomcat starts deploying
to the ASF ibiblio sync repo.

Best wishes,
Paul

On 1/19/07, Paul McMahan <[EMAIL PROTECTED]> wrote:
In Filip's post on [EMAIL PROTECTED] :
http://www.nabble.com/Tomcat-Jars---Maven2-repo- tf3023226.html#a8397986 > We can run with this setup for a while, once outside folks are happy > with the "release" jars, we can start deploying to ASF Ibiblio sync
>  repo, so they get copied to the central repository.



On 1/19/07, Jeff Genender <[EMAIL PROTECTED]> wrote:
> Is there a reason they won't post them to the usual places to get picked
> up by ibiblio?
>
> Jeff
>
> Paul McMahan wrote:
> > The tomcat6 jars are currently being imported into geronimo from the
> > apache snapshot repo.  The tomcat team is now also publishing
> > officially released jars to a maven repo at
> > http://tomcat.apache.org/dev/dist/m2-repository (thanks Filip!). I > > would like to import the jars from that repo instead of the snapshot > > repo so we can avoid using snapshot versions. Is it OK to enable the > > tomcat repo in the root pom or should I only enable it in the specific > > module(s) that needs it? I prefer to enable in the root pom but as I
> > recall adding new repos has caused some problems in the past.
> >
> > Best wishes,
> > Paul
>


Reply via email to