that is fine if it is only in the reactor, but it will still kill backwards build reproducibility
also this is what I see now: [INFO] ------------------------------------------------------------------------ [INFO] Building Glassfish :: Jasper JSP 2.1 [INFO] task-segment: [clean, install] [INFO] ------------------------------------------------------------------------ [INFO] [clean:clean] [INFO] Deleting directory /Users/jesse/src/codehaus/trunks/jetty/modules/jsp/jsp-2.1-jetty/target [WARNING] POM for 'org.mortbay.jetty:jsp-2.1-glassfish:pom:9.1.02.B04.p0:compile' is invalid. It will be ignored for artifact resolution. Reason: Parse error reading POM. Reason: Unrecognised association: 'includes' (position: START_TAG seen ...<includes>\n <includes>... @27:21) for project org.mortbay.jetty:jsp-2.1-glassfish at /Users/jesse/.m2/repository/org/mortbay/jetty/jsp-2.1-glassfish/9.1.02.B04.p0/jsp-2.1-glassfish-9.1.02.B04.p0.pom [WARNING] POM for 'org.mortbay.jetty:jsp-2.1-glassfish:pom:9.1.02.B04.p0:compile' is invalid. It will be ignored for artifact resolution. Reason: Parse error reading POM. Reason: Unrecognised association: 'includes' (position: START_TAG seen ...<includes>\n <includes>... @27:21) for project org.mortbay.jetty:jsp-2.1-glassfish at /Users/jesse/.m2/repository/org/mortbay/jetty/jsp-2.1-glassfish/9.1.02.B04.p0/jsp-2.1-glassfish-9.1.02.B04.p0.pom On Thu, Jul 24, 2008 at 12:54 PM, John Casey <[EMAIL PROTECTED]> wrote: > IIRC, strict POM validation is only for those POMs in the current reactor, > not for dependency POMs. If that's not what you're seeing, please let me > know, as this is a bug that I'll have to fix for 2.0.10. > > -john > > Jesse McConnell wrote: >> >> strict validation of the pom is going to cause some problems with >> already deployed artifacts.. >> >> take for instance this jetty artifact >> >> >> http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-2.1-glassfish/9.1.02.B04.p0/jsp-2.1-glassfish-9.1.02.B04.p0.pom >> >> the pom has <includes><includes>**/**</includes></includes> in it >> which kills the usage of that artifact...I know there will be a number >> of older jetty artifacts affected by this as well. >> >> Is this strict validation required for 2.0.x maven releases or is this >> something more appropriate to look at for the switch to 2.1? I have >> fixed these artifacts in jetty7 trunk and the jetty6 branch but this >> will effect a lot of previous versions of at least the jetty jsp-2.1 >> releases (and some others I fixed during testing the last RC. >> >> when this happens on a bad release we just have someone re-release and >> people have to use those new artifacts...but this will break existing >> builds because of people upgrading their build tooling with a minor >> release... >> >> I talked over those other ones with john last RC...just seeing this >> one crop up this time made me want to at least bring it up. >> >> jesse >> >> On Thu, Jul 24, 2008 at 12:06 PM, Vincent Siveton >> <[EMAIL PROTECTED]> wrote: >>> >>> Hi Julien, >>> >>> 2008/7/24, Julien HENRY <[EMAIL PROTECTED]>: >>>> >>>> During my build, Maven try to download artifacts from >>>> http://cvs.apache.org/maven-snapshot-repository >>>> I don't know where this repository come from (it's not in my pom.xml >>>> nor in my settings.xml). Is it a bug? >>> >>> Nope. I already noticed that when I worked on MPIR. >>> >>> It is due that some repositories like cvs.apache.org was specifiedin >>> the transitive dependencies pom or in the plugins pom. >>> In MPIR, I blacklisted wrong repo url like cvs.a.o. I guess this logic >>> could be include in the core. >>> >>> Cheers, >>> >>> Vincent >>> >>>> Regards >>>> >>>> >>>> >>>> ----- Message d'origine ---- >>>> De : Brett Porter <[EMAIL PROTECTED]> >>>> À : Maven Developers List <dev@maven.apache.org> >>>> Envoyé le : Jeudi, 24 Juillet 2008, 6h52mn 20s >>>> Objet : Re: [PLEASE TEST] Maven 2.0.10-RC2 >>>> >>>> >>>> Fixed in SVN (you can also see comment on the RC1 thread for the >>>> reason this was occuring). >>>> >>>> - Brett >>>> >>>> On 24/07/2008, at 1:10 PM, Michael McCallum wrote: >>>> >>>> > I'm getting stack traces rather than the nice message when an >>>> > artifact does >>>> > not exist the repository... >>>> > >>>> > Downloading: >>>> > >>>> http://mvn.somedomaindev.co.nz/central/nz/co/somedomain/nz.co.somedomain.parent/14-java4/nz.co.somedomain.parent-14-java4.pom >>>> > org.apache.maven.wagon.ResourceDoesNotExistException: Unable to >>>> locate >>>> > resource in repository >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .wagon >>>> > .providers >>>> > .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java: >>>> > 132) >>>> > at >>>> > org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java: >>>> > 116) >>>> > at >>>> > org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) >>>> > at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .artifact >>>> > .manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java: >>>> > 474) >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .artifact >>>> > >>>> .manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:363) >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .artifact >>>> > >>>> .manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:318) >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .artifact >>>> > .resolver >>>> > .DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:200) >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .artifact >>>> > .resolver >>>> > .DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .project >>>> > .DefaultMavenProjectBuilder >>>> > .findModelFromRepository(DefaultMavenProjectBuilder.java:557) >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .project >>>> > .DefaultMavenProjectBuilder >>>> > .assembleLineage(DefaultMavenProjectBuilder.java:1393) >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .project >>>> > .DefaultMavenProjectBuilder >>>> > .buildInternal(DefaultMavenProjectBuilder.java:822) >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .project >>>> > .DefaultMavenProjectBuilder >>>> > .buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:507) >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .project >>>> > >>>> .DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:199) >>>> > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java: >>>> > 578) >>>> > at >>>> > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) >>>> > at >>>> > org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) >>>> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: >>>> > 292) >>>> > at >>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) >>>> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) >>>> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> > at >>>> > sun >>>> > .reflect >>>> > .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>> > at >>>> > sun >>>> > .reflect >>>> > .DelegatingMethodAccessorImpl >>>> > .invoke(DelegatingMethodAccessorImpl.java:25) >>>> > at java.lang.reflect.Method.invoke(Method.java:597) >>>> > at >>>> > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >>>> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >>>> > at >>>> > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >>>> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >>>> > Caused by: java.io.FileNotFoundException: >>>> > >>>> http://mvn.somedomaindev.co.nz/central/nz/co/somedomain/nz.co.somedomain.parent/14-java4/nz.co.somedomain.parent-14-java4.pom >>>> > at >>>> > sun >>>> > .net >>>> > .www >>>> > .protocol >>>> > .http.HttpURLConnection.getInputStream(HttpURLConnection.java:1239) >>>> > at >>>> > org >>>> > .apache >>>> > .maven >>>> > .wagon >>>> > .providers >>>> > .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java: >>>> > 115) >>>> > >>>> > -- >>>> > Michael McCallum >>>> > Development Lead >>>> > somedomain Ltd >>>> > cell: 021.576.907 >>>> > msn: [EMAIL PROTECTED] >>>> > jabber: [EMAIL PROTECTED] >>>> > aim: gholamses >>>> > http://www.somedomain.co.nz >>>> > -- >>>> > Michael McCallum >>>> > Enterprise Engineer >>>> > mailto:[EMAIL PROTECTED] >>>> > >>>> > --------------------------------------------------------------------- >>>> > To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> > For additional commands, e-mail: [EMAIL PROTECTED] >>>> > >>>> >>>> -- >>>> Brett Porter >>>> [EMAIL PROTECTED] >>>> http://blogs.exist.com/bporter/ >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>>> >>>> >>>> >>>> _____________________________________________________________________________ >>>> Envoyez avec Yahoo! Mail. Une boite mail plus intelligente >>>> http://mail.yahoo.fr >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >> >> > > -- > John Casey > Developer, PMC Member - Apache Maven (http://maven.apache.org) > Blog: http://www.ejlife.net/blogs/buildchimp/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jesse mcconnell [EMAIL PROTECTED]
