On Mon, 2008-08-11 at 11:50 -0500, Leonardo Uribe wrote:
>
>
> On Mon, Aug 11, 2008 at 10:57 AM, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I just tried to build core 1.2.x trunk, and got a failure due
> to a missing dependency:
> org.apache.tomcat:catalina:6.0.10
> which is in the impl/pom.xml.
>
> The error is right: the available catalina versions in the
> main repos available start from 6.0.13. But I have been
> building this code regularly and not had this problem. Does
> anyone else have this?
>
> I have this artifact on my local repo (6.0.10) (if does not exist on
> main repo how that code compiles before?).
That's exactly what I was puzzled about before. It used to compile, but
now on my work computer it didn't. And there was no trace of that
artifact in the standard repositories.
I've tracked down the answer now: the tomcat project runs its own maven
repository!
<repository>
<id>tomcat</id>
<url>http://tomcat.apache.org/dev/dist/m2-repository</url>
</repository>
And somehow this repo is defined by default (maybe in the master apache
pom).
At work, we now have a maven repository manager that proxies everything
- but this special tomcat repo was not in the repo-manager's list of
things to proxy, so the artifact could not be found.
So technically there is no problem; it was an issue with the mvn repo
manager configuration at my workplace. However having a special tomcat
repository is rather weird I think. I would rather that our releases
depend only on artifacts from the "standard" repositories. So what do
people think about changing the dependency to use version 6.0.13 (which
is in the main repos)?
By the way, it is currently a "provided" dependency. Perhaps we should
add "optional" too? As Leonardo showed, it is used only by one myfaces
class: TomcatAnnotationLifecycleProvider.
Regards,
Simon
>
