I also found out that we use 4 different versions of shale-test in tomahawk. And shale-test-1.0.3 is pulling in the dev.java.net repository.
I now removed all <repositories> from tomcat and until yet it at least builds fine. We btw also have a repository.jboss.org repo in myfaces-core. But this is way better maintained than the dev.java.net one. Another point would be to better utilise <dependencyManagement> and <pluginManagement>. Is it really necessary to use 3 different maven-builder-plugin versions in tomahawk? LieGrue, strub ----- Original Message ---- > From: Michael Kurz <[email protected]> > To: [email protected] > Sent: Thu, August 19, 2010 6:00:00 PM > Subject: Re: [DISCUSS] getting rid of all java.net maven repositories > > Am 19.08.2010 16:58, schrieb Mark Struberg: > > I just figured that we still pretty often use the java.net maven >repositories. > > They are not well maintained and often lead to weird problems. Today I > > tried >to > > compile tomahawk and got a weird exception that shale-master-1.pom is >broken. > > Had the same problem some time ago. I think what happened was that the >specified repository location issued a redirect which was, for whatever >reason, >stored in my local pom file! I think what I did then was to manually download >the pom. > > > Also, if we use Java JSR spec APIs we should always rely on geronimo spec >jars > > [1] instead of pulling them from the java.net repo! Geronimo spec jars are > > always IP cleared which is _not_ guaranteed in the java.net repo. > > +1 > > > We should upgrade tomahawk to myfaces-parent-9 and try to get rid of >arbitrary > > <repositories>. > > +1 > > Michi >
