WARNING: Mavenizing Thirdparty (2nd try)

Clebert Suconic

Tuesday, 25 March Tue, 25 Mar

4:46 p.m.

I'm considering to move JBossMessaging configuration files to thirdparty. This will require some sort of script to place the files in place after the build. Like doing this for several files: Copy ./thirdparty/jbm/resources/som-file.xml into its proper place How the creationg of /default and /all is being done with Maven? Paul Gier wrote:

...

Hi Everyone, I'd like to make a second attempt at replacing build-thirdparty.xml with maven. I'm going to add a new file called build-maven.xml to the build directory. This will allow anyone who is interested to try it out before the actual switch. I'm planning to do some additional testing and dependency checking this afternoon (I still need to make some updates to jbossws dependencies), and then make the change to build.xml at the end of the day today. I will leave the build-thirdparty.xml file in the build directory for testing this week, and then if everything is working fine, it can be removed next week. If this conflicts with any changes you had planned, or you have concerns about this please let me know. Thanks! _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Reply

Paul Gier

8:43 p.m.

I'm still having some problems in the testsuite on hudson with the maven built thirdparty directory, so I'm going to hold off on this a little bit longer until I can get it resolved. The build-maven.xml file is not in svn, so if you want to test it out, just use "ant -f build-maven.xml". Paul Gier wrote:

...

Hi Everyone, I'd like to make a second attempt at replacing build-thirdparty.xml with maven. I'm going to add a new file called build-maven.xml to the build directory. This will allow anyone who is interested to try it out before the actual switch. I'm planning to do some additional testing and dependency checking this afternoon (I still need to make some updates to jbossws dependencies), and then make the change to build.xml at the end of the day today. I will leave the build-thirdparty.xml file in the build directory for testing this week, and then if everything is working fine, it can be removed next week. If this conflicts with any changes you had planned, or you have concerns about this please let me know. Thanks!

Reply

Paul Gier

Wednesday, 26 March Wed, 26 Mar

9:38 p.m.

Today's test run with the mavenized thirdparty on hudson went much better (results were similar to the non-maven test run). So I'm planning to make the switch end of day tomorrow. It would be helpful if anyone can run the build locally and confirm if it seems to be working or not working for them. Paul Gier wrote:

...

I'm still having some problems in the testsuite on hudson with the maven built thirdparty directory, so I'm going to hold off on this a little bit longer until I can get it resolved. The build-maven.xml file is not in svn, so if you want to test it out, just use "ant -f build-maven.xml". Paul Gier wrote: > Hi Everyone, > > I'd like to make a second attempt at replacing build-thirdparty.xml > with maven. I'm going to add a new file called build-maven.xml to > the build directory. This will allow anyone who is interested to try > it out before the actual switch. I'm planning to do some additional > testing and dependency checking this afternoon (I still need to make > some updates to jbossws dependencies), and then make the change to > build.xml at the end of the day today. > > I will leave the build-thirdparty.xml file in the build directory for > testing this week, and then if everything is working fine, it can be > removed next week. > > If this conflicts with any changes you had planned, or you have > concerns about this please let me know. > > Thanks! >

Reply

Dimitris Andreadis

Thursday, 27 March Thu, 27 Mar

3:58 a.m.

It fails for me, too, somewhat differently (15 dependency validation errors rather than Scott's 62) Those build differences depending on who/what is building are IMHO completely unacceptable. If we cannot guarantee that everyone sees the same results, we are toast. I was looking also at the last build: http://hudson.qa.jboss.com/hudson/view/JBoss%20AS%20Maven/job/JBoss-AS-5.... - I understand that it caches stuff in its local maven repository. E.g. I don't see it downloading MicroContainer libraries, so they must have been there from a previous run. Do we really want that? Shouldn't the hudson builds start always from a clean slate? - Why it goes first in the snapshot.jboss.org repository and then to repository.jboss.org? [java] Downloading: http://snapshots.jboss.org/maven2/sun-jaxws/jaxws-rt/2.1.1/jaxws-rt-2.1.1... [java] Downloading: http://repository.jboss.org/maven2/sun-jaxws/jaxws-rt/2.1.1/jaxws-rt-2.1.... Shouldn't it try the snapshot repo for snapshot dependencies *only*? - Why it still references external repositories, like: http://repo1.maven.org/maven2/apache-avalon-logkit/logkit/1.2/logkit-1.2.pom ========= [java] [INFO] Error building POM (may not be this project's POM). [java] Project ID: org.jboss.jbossas:jboss-as-thirdparty [java] POM Location: X:\cvs\jboss-public\jboss-head\thirdparty\pom.xml [java] Validation Messages: [java] [0] 'dependencies.dependency.version' is missing for sun-jaxws: jaxws-rt [java] [1] 'dependencies.dependency.version' is missing for sun-jaxws: sjsxp [java] [2] 'dependencies.dependency.version' is missing for sun-jaxws: saaj-api [java] [3] 'dependencies.dependency.version' is missing for sun-jaxws: http [java] [4] 'dependencies.dependency.version' is missing for sun-jaxws: FastInfoset [java] [5] 'dependencies.dependency.version' is missing for jboss.jbos sws:jbossws-context [java] [6] 'dependencies.dependency.version' is missing for sun-jaxws: stax-ex [java] [7] 'dependencies.dependency.version' is missing for sun-jaxws: saaj-impl [java] [8] 'dependencies.dependency.version' is missing for sun-jaxws: streambuffer [java] [9] 'dependencies.dependency.version' is missing for wutka-dtdp arser:dtdparser [java] [10] 'dependencies.dependency.version' is missing for sun-jaxws :jaxws-tools [java] [11] 'dependencies.dependency.version' is missing for jboss.jbo ssws:jbossws-client [java] [12] 'dependencies.dependency.version' is missing for sun-jaxws :jsr173_api [java] [13] 'dependencies.dependency.version' is missing for jboss.mes saging:jboss-messaging-client [java] [14] 'dependencies.dependency.version' is missing for xdoclet:x javadoc [java] [15] 'dependencies.dependency.version' is missing for sun-jaxws :jsr250-api [java] Reason: Failed to validate POM for project org.jboss.jbossas:jboss-a s-thirdparty at X:\cvs\jboss-public\jboss-head\thirdparty\pom.xml Scott M Stark wrote:

...

Its not working for me. I just threw away my thirdparty, updated it from svn and then tried to run: [starksm@succubus build]$ ant -f build-maven.xml Buildfile: build-maven.xml check.inhibit.downloads: check.proxy: set.proxy.withoutauth: set.proxy.auth: set.proxy: createthirdparty: [java] [INFO] Scanning for projects... [java] [INFO] ------------------------------------------------------------------------ [java] [ERROR] FATAL ERROR [java] [INFO] ------------------------------------------------------------------------ [java] [INFO] Error building POM (may not be this project's POM). [java] Project ID: org.jboss.jbossas:jboss-as-thirdparty [java] POM Location: /home/svn/JBossHead/jboss-head/thirdparty/pom.xml [java] Validation Messages: [java] [0] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:integration-mdb20-selector [java] [1] 'dependencies.dependency.version' is missing for jboss.web:jsp-api [java] [2] 'dependencies.dependency.version' is missing for jboss.web:jasper-jdt [java] [3] 'dependencies.dependency.version' is missing for sun-jaxws:jaxws-rt [java] [4] 'dependencies.dependency.version' is missing for apache-slide:jakarta-slide-webdavlib [java] [5] 'dependencies.dependency.version' is missing for org.jboss.cl:jboss-classloader [java] [6] 'dependencies.dependency.version' is missing for jboss.web:servlet-api [java] [7] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:integration-mdb20 [java] [8] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-vfs [java] [9] 'dependencies.dependency.version' is missing for sun-jaxws:sjsxp [java] [10] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:integration-mdb20-userTransactionDups [java] [11] 'dependencies.dependency.version' is missing for jacorb:jacorb_g [java] [12] 'dependencies.dependency.version' is missing for sun-jaxws:saaj-api [java] [13] 'dependencies.dependency.version' is missing for org.jboss:jboss-mdr [java] [14] 'dependencies.dependency.version' is missing for apache-myfaces:myfaces-api [java] [15] 'dependencies.dependency.version' is missing for sun-jaxws:http [java] [16] 'dependencies.dependency.version' is missing for sun-jaxws:FastInfoset [java] [17] 'dependencies.dependency.version' is missing for sun-opends:OpenDS [java] [18] 'dependencies.dependency.version' is missing for sun-xacml:sunxacml-support [java] [19] 'dependencies.dependency.version' is missing for org.jboss.man:jboss-metatype [java] [20] 'dependencies.dependency.version' is missing for org.jboss.cl:jboss-classloading-vfs [java] [21] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-client-spi [java] [22] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:integration-mdb20-userTransaction [java] [23] 'dependencies.dependency.version' is missing for org.jboss.cl:jboss-classloading [java] [24] 'dependencies.dependency.version' is missing for sun-jaxws:stax-ex [java] [25] 'dependencies.dependency.version' is missing for jboss.common:namespace [java] [26] 'dependencies.dependency.version' is missing for sun-jaxb:jaxb-api [java] [27] 'dependencies.dependency.version' is missing for javassist:javassist [java] [28] 'dependencies.dependency.version' is missing for sun-jaxws:saaj-impl [java] [29] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-impl [java] [30] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-spi [java] [31] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-vfs-spi [java] [32] 'dependencies.dependency.version' is missing for jboss.common:jboss-common-client [java] [33] 'dependencies.dependency.version' is missing for jboss.aop:jboss-aop-jdk50 [java] [34] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-core-spi [java] [35] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-client [java] [36] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-structure-spi [java] [37] 'dependencies.dependency.version' is missing for org.jboss:jboss-reflect [java] [38] 'dependencies.dependency.version' is missing for sun-jaxws:streambuffer [java] [39] 'dependencies.dependency.version' is missing for wutka-dtdparser:dtdparser [java] [40] 'dependencies.dependency.version' is missing for org.jboss:jboss-integration [java] [41] 'dependencies.dependency.version' is missing for jboss.aop:jboss-standalone-aspect-library-jdk50 [java] [42] 'dependencies.dependency.version' is missing for jacorb:idl_g [java] [43] 'dependencies.dependency.version' is missing for sun-jaxws:jaxws-tools [java] [44] 'dependencies.dependency.version' is missing for sun-fi:FastInfosetUtilities [java] [45] 'dependencies.dependency.version' is missing for jboss.jbossws:jboss-jaxws-ext [java] [46] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:integration-mdb20-durable [java] [47] 'dependencies.dependency.version' is missing for jboss.jbossws:jbossws-client [java] [48] 'dependencies.dependency.version' is missing for jboss.jbossws:jbossws-core [java] [49] 'dependencies.dependency.version' is missing for apache-myfaces:myfaces-impl [java] [50] 'dependencies.dependency.version' is missing for sun-jaxws:jsr173_api [java] [51] 'dependencies.dependency.version' is missing for sun-javamail:mail [java] [52] 'dependencies.dependency.version' is missing for org.jboss.man:jboss-managed [java] [53] 'dependencies.dependency.version' is missing for sun-jaxb:jaxb-xjc [java] [54] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:jms-integration-tests [java] [55] 'dependencies.dependency.version' is missing for jboss.jbossws-common:jbossws-common [java] [56] 'dependencies.dependency.version' is missing for jboss.remoting:jboss-remoting [java] [57] 'dependencies.dependency.version' is missing for sun-fi:FastInfoset [java] [58] 'dependencies.dependency.version' is missing for jboss.messaging:jboss-messaging-client [java] [59] 'dependencies.dependency.version' is missing for jboss.web:el-api [java] [60] 'dependencies.dependency.version' is missing for sun-jaxb:jaxb-impl [java] [61] 'dependencies.dependency.version' is missing for xdoclet:xjavadoc [java] [62] 'dependencies.dependency.version' is missing for sun-jaxws:jsr250-api [java] Reason: Failed to validate POM for project org.jboss.jbossas:jboss-as-thirdparty at /home/svn/JBossHead/jboss-head/thirdparty/pom.xml [java] [INFO] ------------------------------------------------------------------------ [java] [INFO] Trace [java] org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for project org.jboss.jbossas:jboss-as-thirdparty at /home/svn/JBossHead/jboss-head/thirdparty/pom.xml [java] at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:376) [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:289) [java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [java] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [java] at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [java] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [java] Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to validate POM for project org.jboss.jbossas:jboss-as-thirdparty at /home/svn/JBossHead/jboss-head/thirdparty/pom.xml [java] at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:996) [java] at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:799) [java] at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:476) [java] at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197) [java] at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:548) [java] at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:458) [java] at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:362) [java] ... 11 more [java] [INFO] ------------------------------------------------------------------------ [java] [INFO] Total time: < 1 second [java] [INFO] Finished at: Wed Mar 26 20:55:30 PDT 2008 [java] [INFO] Final Memory: 3M/74M [java] [INFO] ------------------------------------------------------------------------ [java] Java Result: 1 _buildmagic:init: Trying to override old definition of task property _buildmagic:init:local-properties: _buildmagic:init:buildlog: configure: [echo] groups: default [echo] modules: main,bootstrap,j2se,mbeans,jmx,system,system-jmx,security,server,deployment,jbossas/remoting,jmx-remoting,jbossas/jmx-remoting,messaging,jbossmq,cluster,varia,iiop,aspects,profileservice,connector,management,ejb3,tomcat,webservices,hibernate-int,console,spring-int init: _buildmagic:modules:most: ====================================================================== == Executing 'most' in module 'main'... == /home/svn/JBossHead/jboss-head/thirdparty/libraries.ent could not be found BUILD FAILED /home/svn/JBossHead/jboss-head/tools/etc/buildmagic/buildmagic.ent:1029: java.io.FileNotFoundException: /home/svn/JBossHead/jboss-head/thirdparty/libraries.ent (No such file or directory) Total time: 2 seconds [starksm@succubus build]$ type mvn mvn is /home/starksm/java/maven-2.0.7/bin/mvn _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Reply

Adrian Brock

8:17 a.m.

I get the same results as Dimitris. Scott probably got a different result because of the "stale" local maven repository issue. I blew away my local maven repository before starting so I could see it downloading the latest component-matrix snapshot (build 13) createthirdparty: [java] [INFO] Scanning for projects... [java] [INFO] snapshot org.jboss.jbossas:jboss-as-component-matrix:5.0.0-SNAPSHOT: checking for updates from snapshots.jboss.org [java] Downloading: http://snapshots.jboss.org/maven2/org/jboss/jbossas/jboss-as-component-ma... [java] 1/41K [java] 2/41K4/41K5/41K7/41K8/41K9/41K11/41K12/41K14/41K15/41K16/41K18/41K19/41K21/41K22/41K24/41K25/41K26/41K28/41K29/41K31/41K32/41K33/41K35/41K36/41K40/41K41/41K41K downloaded[INFO] snapshot org.jboss:jboss-parent:4-SNAPSHOT: checking for updates from snapshots.jboss.org [java] Downloading: http://snapshots.jboss.org/maven2/org/jboss/jboss-parent/4-SNAPSHOT/jboss... [java] 1/11K [java] 4/11K5/11K7/11K8/11K9/11K11/11K11K downloaded[INFO] ------------------------------------------------------------------------ [java] [ERROR] FATAL ERROR [java] [INFO] ------------------------------------------------------------------------ [java] [INFO] Error building POM (may not be this project's POM). [java] Project ID: org.jboss.jbossas:jboss-as-thirdparty [java] POM Location: /home/ejort/jboss-head/thirdparty/pom.xml [java] Validation Messages: [java] [0] 'dependencies.dependency.version' is missing for sun-jaxws:jaxws-rt [java] [1] 'dependencies.dependency.version' is missing for sun-jaxws:sjsxp [java] [2] 'dependencies.dependency.version' is missing for sun-jaxws:saaj-api [java] [3] 'dependencies.dependency.version' is missing for sun-jaxws:http [java] [4] 'dependencies.dependency.version' is missing for sun-jaxws:FastInfoset [java] [5] 'dependencies.dependency.version' is missing for jboss.jbossws:jbossws-context [java] [6] 'dependencies.dependency.version' is missing for sun-jaxws:stax-ex [java] [7] 'dependencies.dependency.version' is missing for sun-jaxws:saaj-impl [java] [8] 'dependencies.dependency.version' is missing for sun-jaxws:streambuffer [java] [9] 'dependencies.dependency.version' is missing for wutka-dtdparser:dtdparser [java] [10] 'dependencies.dependency.version' is missing for sun-jaxws:jaxws-tools [java] [11] 'dependencies.dependency.version' is missing for jboss.jbossws:jbossws-client [java] [12] 'dependencies.dependency.version' is missing for sun-jaxws:jsr173_api [java] [13] 'dependencies.dependency.version' is missing for jboss.messaging:jboss-messaging-client [java] [14] 'dependencies.dependency.version' is missing for xdoclet:xjavadoc [java] [15] 'dependencies.dependency.version' is missing for sun-jaxws:jsr250-api None of these have a version in the component-matrix pom. On Thu, 2008-03-27 at 06:07 -0500, Paul Gier wrote:

...

That looks like it's not finding an up to date component-matrix pom for some reason. You can try installing that pom locally, and see if these errors go away. I brought up possibly moving the dependencyManagement stuff back into the app server poms on the build forum (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=132452). Do you get the same thing if you run "mvn package" from the thirdparty directory? Scott M Stark wrote: > Its not working for me. I just threw away my thirdparty, updated it from > svn and then tried to run: > > [starksm@succubus build]$ ant -f build-maven.xml > > Buildfile: build-maven.xml > > check.inhibit.downloads: > > check.proxy: > > set.proxy.withoutauth: > > set.proxy.auth: > > set.proxy: > > createthirdparty: > [java] [INFO] Scanning for projects... > [java] [INFO] > ------------------------------------------------------------------------ > [java] [ERROR] FATAL ERROR > [java] [INFO] > ------------------------------------------------------------------------ > [java] [INFO] Error building POM (may not be this project's POM). > > > [java] Project ID: org.jboss.jbossas:jboss-as-thirdparty > [java] POM Location: /home/svn/JBossHead/jboss-head/thirdparty/pom.xml > [java] Validation Messages: > > [java] [0] 'dependencies.dependency.version' is missing for > jboss.jms-integration-tests:integration-mdb20-selector > [java] [1] 'dependencies.dependency.version' is missing for > jboss.web:jsp-api > [java] [2] 'dependencies.dependency.version' is missing for > jboss.web:jasper-jdt > [java] [3] 'dependencies.dependency.version' is missing for > sun-jaxws:jaxws-rt > [java] [4] 'dependencies.dependency.version' is missing for > apache-slide:jakarta-slide-webdavlib > [java] [5] 'dependencies.dependency.version' is missing for > org.jboss.cl:jboss-classloader > [java] [6] 'dependencies.dependency.version' is missing for > jboss.web:servlet-api > [java] [7] 'dependencies.dependency.version' is missing for > jboss.jms-integration-tests:integration-mdb20 > [java] [8] 'dependencies.dependency.version' is missing for > org.jboss.deployers:jboss-deployers-vfs > [java] [9] 'dependencies.dependency.version' is missing for > sun-jaxws:sjsxp > [java] [10] 'dependencies.dependency.version' is missing for > jboss.jms-integration-tests:integration-mdb20-userTransactionDups > [java] [11] 'dependencies.dependency.version' is missing for > jacorb:jacorb_g > [java] [12] 'dependencies.dependency.version' is missing for > sun-jaxws:saaj-api > [java] [13] 'dependencies.dependency.version' is missing for > org.jboss:jboss-mdr > [java] [14] 'dependencies.dependency.version' is missing for > apache-myfaces:myfaces-api > [java] [15] 'dependencies.dependency.version' is missing for > sun-jaxws:http > [java] [16] 'dependencies.dependency.version' is missing for > sun-jaxws:FastInfoset > [java] [17] 'dependencies.dependency.version' is missing for > sun-opends:OpenDS > [java] [18] 'dependencies.dependency.version' is missing for > sun-xacml:sunxacml-support > [java] [19] 'dependencies.dependency.version' is missing for > org.jboss.man:jboss-metatype > [java] [20] 'dependencies.dependency.version' is missing for > org.jboss.cl:jboss-classloading-vfs > [java] [21] 'dependencies.dependency.version' is missing for > org.jboss.deployers:jboss-deployers-client-spi > [java] [22] 'dependencies.dependency.version' is missing for > jboss.jms-integration-tests:integration-mdb20-userTransaction > [java] [23] 'dependencies.dependency.version' is missing for > org.jboss.cl:jboss-classloading > [java] [24] 'dependencies.dependency.version' is missing for > sun-jaxws:stax-ex > [java] [25] 'dependencies.dependency.version' is missing for > jboss.common:namespace > [java] [26] 'dependencies.dependency.version' is missing for > sun-jaxb:jaxb-api > [java] [27] 'dependencies.dependency.version' is missing for > javassist:javassist > [java] [28] 'dependencies.dependency.version' is missing for > sun-jaxws:saaj-impl > [java] [29] 'dependencies.dependency.version' is missing for > org.jboss.deployers:jboss-deployers-impl > [java] [30] 'dependencies.dependency.version' is missing for > org.jboss.deployers:jboss-deployers-spi > [java] [31] 'dependencies.dependency.version' is missing for > org.jboss.deployers:jboss-deployers-vfs-spi > [java] [32] 'dependencies.dependency.version' is missing for > jboss.common:jboss-common-client > [java] [33] 'dependencies.dependency.version' is missing for > jboss.aop:jboss-aop-jdk50 > [java] [34] 'dependencies.dependency.version' is missing for > org.jboss.deployers:jboss-deployers-core-spi > [java] [35] 'dependencies.dependency.version' is missing for > org.jboss.deployers:jboss-deployers-client > [java] [36] 'dependencies.dependency.version' is missing for > org.jboss.deployers:jboss-deployers-structure-spi > [java] [37] 'dependencies.dependency.version' is missing for > org.jboss:jboss-reflect > [java] [38] 'dependencies.dependency.version' is missing for > sun-jaxws:streambuffer > [java] [39] 'dependencies.dependency.version' is missing for > wutka-dtdparser:dtdparser > [java] [40] 'dependencies.dependency.version' is missing for > org.jboss:jboss-integration > [java] [41] 'dependencies.dependency.version' is missing for > jboss.aop:jboss-standalone-aspect-library-jdk50 > [java] [42] 'dependencies.dependency.version' is missing for > jacorb:idl_g > [java] [43] 'dependencies.dependency.version' is missing for > sun-jaxws:jaxws-tools > [java] [44] 'dependencies.dependency.version' is missing for > sun-fi:FastInfosetUtilities > [java] [45] 'dependencies.dependency.version' is missing for > jboss.jbossws:jboss-jaxws-ext > [java] [46] 'dependencies.dependency.version' is missing for > jboss.jms-integration-tests:integration-mdb20-durable > [java] [47] 'dependencies.dependency.version' is missing for > jboss.jbossws:jbossws-client > [java] [48] 'dependencies.dependency.version' is missing for > jboss.jbossws:jbossws-core > [java] [49] 'dependencies.dependency.version' is missing for > apache-myfaces:myfaces-impl > [java] [50] 'dependencies.dependency.version' is missing for > sun-jaxws:jsr173_api > [java] [51] 'dependencies.dependency.version' is missing for > sun-javamail:mail > [java] [52] 'dependencies.dependency.version' is missing for > org.jboss.man:jboss-managed > [java] [53] 'dependencies.dependency.version' is missing for > sun-jaxb:jaxb-xjc > [java] [54] 'dependencies.dependency.version' is missing for > jboss.jms-integration-tests:jms-integration-tests > [java] [55] 'dependencies.dependency.version' is missing for > jboss.jbossws-common:jbossws-common > [java] [56] 'dependencies.dependency.version' is missing for > jboss.remoting:jboss-remoting > [java] [57] 'dependencies.dependency.version' is missing for > sun-fi:FastInfoset > [java] [58] 'dependencies.dependency.version' is missing for > jboss.messaging:jboss-messaging-client > [java] [59] 'dependencies.dependency.version' is missing for > jboss.web:el-api > [java] [60] 'dependencies.dependency.version' is missing for > sun-jaxb:jaxb-impl > [java] [61] 'dependencies.dependency.version' is missing for > xdoclet:xjavadoc > [java] [62] 'dependencies.dependency.version' is missing for > sun-jaxws:jsr250-api > > > [java] Reason: Failed to validate POM for project > org.jboss.jbossas:jboss-as-thirdparty at > /home/svn/JBossHead/jboss-head/thirdparty/pom.xml > > > [java] [INFO] > ------------------------------------------------------------------------ > [java] [INFO] Trace > [java] org.apache.maven.reactor.MavenExecutionException: Failed to > validate POM for project org.jboss.jbossas:jboss-as-thirdparty at > /home/svn/JBossHead/jboss-head/thirdparty/pom.xml > [java] at > org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:376) > [java] at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:289) > [java] at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) [java] > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > [java] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > > [java] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > [java] at java.lang.reflect.Method.invoke(Method.java:585) > [java] at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > [java] at > org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > [java] at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > [java] at > org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [java] Caused by: > org.apache.maven.project.InvalidProjectModelException: Failed to > validate POM for project org.jboss.jbossas:jboss-as-thirdparty at > /home/svn/JBossHead/jboss-head/thirdparty/pom.xml > [java] at > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:996) > > [java] at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:799) > > [java] at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:476) > > [java] at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197) > > [java] at > org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:548) > [java] at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:458) > [java] at > org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:362) > [java] ... 11 more > [java] [INFO] > ------------------------------------------------------------------------ > [java] [INFO] Total time: < 1 second > [java] [INFO] Finished at: Wed Mar 26 20:55:30 PDT 2008 > [java] [INFO] Final Memory: 3M/74M > [java] [INFO] > ------------------------------------------------------------------------ > [java] Java Result: 1 > > _buildmagic:init: > Trying to override old definition of task property > > _buildmagic:init:local-properties: > > _buildmagic:init:buildlog: > > configure: > [echo] groups: default > [echo] modules: > main,bootstrap,j2se,mbeans,jmx,system,system-jmx,security,server,deployment,jbossas/remoting,jmx-remoting,jbossas/jmx-remoting,messaging,jbossmq,cluster,varia,iiop,aspects,profileservice,connector,management,ejb3,tomcat,webservices,hibernate-int,console,spring-int > > > init: > > _buildmagic:modules:most: > > ====================================================================== > == Executing 'most' in module 'main'... > == > /home/svn/JBossHead/jboss-head/thirdparty/libraries.ent could not be found > > BUILD FAILED > /home/svn/JBossHead/jboss-head/tools/etc/buildmagic/buildmagic.ent:1029: > java.io.FileNotFoundException: > /home/svn/JBossHead/jboss-head/thirdparty/libraries.ent (No such file or > directory) > > Total time: 2 seconds > [starksm@succubus build]$ type mvn > mvn is /home/starksm/java/maven-2.0.7/bin/mvn > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reply

Scott M Stark

2:30 p.m.

Even after removing both: /home/svn/repository.jboss.org/maven2/org/jboss/jbossas/ /home/svn/repository.jboss.org/maven2/org/jboss/jboss-parent/ from my svn repo, I'm not seeing the org.jboss.jbossas:jboss-as-component-matrix:5.0.0-SNAPSHOT being downloaded. org.jboss:jboss-parent:4-SNAPSHOT is updated, but its not even trying to download [starksm@succubus thirdparty]$ mvn -U package [INFO] Scanning for projects... [INFO] snapshot org.jboss:jboss-parent:4-SNAPSHOT: checking for updates from snapshots.jboss.org Downloading: http://snapshots.jboss.org/maven2/org/jboss/jboss-parent/4-SNAPSHOT/jboss... 11K downloaded [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). ... Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to validate POM for project org.jboss.jbossas:jboss-as-thirdparty at /home/svn/JBossHead/jboss-head/thirdparty/pom.xml Is there something wrong with my settings.xml? [starksm@succubus thirdparty]$ cat ~/.m2/settings.xml <settings>  <localRepository>/home/svn/repository.jboss.org/maven2</localReposit... <servers> <server> <id>snapshots.jboss.org</id> <username>scott.stark(a)jboss.org</username> <password>**secret**</password> </server> <server> <id>repository.jboss.org</id> <username>scott.stark(a)jboss.org</username> <password>**secret**</password> </server> </servers> <profiles> <profile> <id>local-properties</id> <properties>  <jboss.repository.root>/home/svn/repository.jboss.org</jboss.repository.root> <maven.repository.root>/home/svn/repository.jboss.org</maven.repository.root>  <maven.cvs.root>/home/svn/repository.jboss.org/maven2</maven.cvs.roo... </properties> </profile> <profile> <id>jboss.repository</id> <activation> <property> <name>!jboss.repository.off</name> </property> </activation> <repositories> <repository> <id>snapshots.jboss.org</id> <url>http://snapshots.jboss.org/maven2</url> <snapshots> <enabled>true</enabled> </snapshots> </repository> <repository> <id>repository.jboss.org</id> <url>http://repository.jboss.org/maven2</url> <snapshots> <enabled>false</enabled> </snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>repository.jboss.org</id> <url>http://repository.jboss.org/maven2</url> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> <pluginRepository> <id>snapshots.jboss.org</id> <url>http://snapshots.jboss.org/maven2</url> <snapshots> <enabled>true</enabled> </snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>local-properties</activeProfile> </activeProfiles> </settings> Scott M Stark wrote:

...

I see: [starksm@succubus thirdparty]$ mvn -U package [INFO] Scanning for projects... [INFO] snapshot org.jboss:jboss-parent:4-SNAPSHOT: checking for updates from snapshots.jboss.org [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: org.jboss.jbossas:jboss-as-thirdparty POM Location: /home/svn/JBossHead/jboss-head/thirdparty/pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:integration-mdb20-selector [1] 'dependencies.dependency.version' is missing for jboss.web:jsp-api [2] 'dependencies.dependency.version' is missing for jboss.web:jasper-jdt [3] 'dependencies.dependency.version' is missing for sun-jaxws:jaxws-rt [4] 'dependencies.dependency.version' is missing for apache-slide:jakarta-slide-webdavlib [5] 'dependencies.dependency.version' is missing for org.jboss.cl:jboss-classloader [6] 'dependencies.dependency.version' is missing for jboss.web:servlet-api [7] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:integration-mdb20 [8] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-vfs [9] 'dependencies.dependency.version' is missing for sun-jaxws:sjsxp [10] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:integration-mdb20-userTransactionDups [11] 'dependencies.dependency.version' is missing for jacorb:jacorb_g [12] 'dependencies.dependency.version' is missing for sun-jaxws:saaj-api [13] 'dependencies.dependency.version' is missing for org.jboss:jboss-mdr [14] 'dependencies.dependency.version' is missing for apache-myfaces:myfaces-api [15] 'dependencies.dependency.version' is missing for sun-jaxws:http [16] 'dependencies.dependency.version' is missing for sun-jaxws:FastInfoset [17] 'dependencies.dependency.version' is missing for sun-opends:OpenDS [18] 'dependencies.dependency.version' is missing for sun-xacml:sunxacml-support [19] 'dependencies.dependency.version' is missing for org.jboss.man:jboss-metatype [20] 'dependencies.dependency.version' is missing for org.jboss.cl:jboss-classloading-vfs [21] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-client-spi [22] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:integration-mdb20-userTransaction [23] 'dependencies.dependency.version' is missing for org.jboss.cl:jboss-classloading [24] 'dependencies.dependency.version' is missing for sun-jaxws:stax-ex [25] 'dependencies.dependency.version' is missing for jboss.common:namespace [26] 'dependencies.dependency.version' is missing for sun-jaxb:jaxb-api [27] 'dependencies.dependency.version' is missing for javassist:javassist [28] 'dependencies.dependency.version' is missing for sun-jaxws:saaj-impl [29] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-impl [30] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-spi [31] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-vfs-spi [32] 'dependencies.dependency.version' is missing for jboss.common:jboss-common-client [33] 'dependencies.dependency.version' is missing for jboss.aop:jboss-aop-jdk50 [34] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-core-spi [35] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-client [36] 'dependencies.dependency.version' is missing for org.jboss.deployers:jboss-deployers-structure-spi [37] 'dependencies.dependency.version' is missing for org.jboss:jboss-reflect [38] 'dependencies.dependency.version' is missing for sun-jaxws:streambuffer [39] 'dependencies.dependency.version' is missing for wutka-dtdparser:dtdparser [40] 'dependencies.dependency.version' is missing for org.jboss:jboss-integration [41] 'dependencies.dependency.version' is missing for jboss.aop:jboss-standalone-aspect-library-jdk50 [42] 'dependencies.dependency.version' is missing for jacorb:idl_g [43] 'dependencies.dependency.version' is missing for sun-jaxws:jaxws-tools [44] 'dependencies.dependency.version' is missing for sun-fi:FastInfosetUtilities [45] 'dependencies.dependency.version' is missing for jboss.jbossws:jboss-jaxws-ext [46] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:integration-mdb20-durable [47] 'dependencies.dependency.version' is missing for jboss.jbossws:jbossws-client [48] 'dependencies.dependency.version' is missing for jboss.jbossws:jbossws-core [49] 'dependencies.dependency.version' is missing for apache-myfaces:myfaces-impl [50] 'dependencies.dependency.version' is missing for sun-jaxws:jsr173_api [51] 'dependencies.dependency.version' is missing for sun-javamail:mail [52] 'dependencies.dependency.version' is missing for org.jboss.man:jboss-managed [53] 'dependencies.dependency.version' is missing for sun-jaxb:jaxb-xjc [54] 'dependencies.dependency.version' is missing for jboss.jms-integration-tests:jms-integration-tests [55] 'dependencies.dependency.version' is missing for jboss.jbossws-common:jbossws-common [56] 'dependencies.dependency.version' is missing for jboss.remoting:jboss-remoting [57] 'dependencies.dependency.version' is missing for sun-fi:FastInfoset [58] 'dependencies.dependency.version' is missing for jboss.messaging:jboss-messaging-client [59] 'dependencies.dependency.version' is missing for jboss.web:el-api [60] 'dependencies.dependency.version' is missing for sun-jaxb:jaxb-impl [61] 'dependencies.dependency.version' is missing for xdoclet:xjavadoc [62] 'dependencies.dependency.version' is missing for sun-jaxws:jsr250-api Reason: Failed to validate POM for project org.jboss.jbossas:jboss-as-thirdparty at /home/svn/JBossHead/jboss-head/thirdparty/pom.xml [INFO] ------------------------------------------------------------------------[INFO] Trace org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for project org.jboss.jbossas:jboss-as-thirdparty at /home/svn/JBossHead/jboss-head/thirdparty/pom.xml at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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:585) 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: org.apache.maven.project.InvalidProjectModelException: Failed to validate POM for project org.jboss.jbossas:jboss-as-thirdparty at /home/svn/JBossHead/jboss-head/thirdparty/pom.xml at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:998) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:801) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:553) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364) ... 11 more [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4 seconds [INFO] Finished at: Thu Mar 27 12:10:44 PDT 2008 [INFO] Final Memory: 3M/59M [INFO] ------------------------------------------------------------------------ [starksm@succubus thirdparty]$ Paul Gier wrote: > That looks like it's not finding an up to date component-matrix pom > for some reason. You can try installing that pom locally, and see if > these errors go away. I brought up possibly moving the > dependencyManagement stuff back into the app server poms on the build > forum (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=132452). > > Do you get the same thing if you run "mvn package" from the thirdparty > directory? _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Reply

Paul Gier

3:18 p.m.

Since there still seem to be a few issues with the maven thirdaprty build, I will wait until next week to make the final switch. Paul Gier wrote:

...

Hi Everyone, I'd like to make a second attempt at replacing build-thirdparty.xml with maven. I'm going to add a new file called build-maven.xml to the build directory. This will allow anyone who is interested to try it out before the actual switch. I'm planning to do some additional testing and dependency checking this afternoon (I still need to make some updates to jbossws dependencies), and then make the change to build.xml at the end of the day today. I will leave the build-thirdparty.xml file in the build directory for testing this week, and then if everything is working fine, it can be removed next week. If this conflicts with any changes you had planned, or you have concerns about this please let me know. Thanks!

Reply

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006