Alexey, Have not seen this. jbossas/trunk CI builds have been successful too: http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x/ Shelly McGowan JBoss, by Red Hat ----- Original Message ----- From: "Alexey Loubyansky&quot;&lt;alexey.loubyansky(a)redhat.com&gt; To: "JBoss.org development list&quot;&lt;jboss-development(a)lists.jboss.org&gt; Sent: Tuesday, September 21, 2010 9:59:26 AM GMT -05:00 US/Canada Eastern Subject: [jboss-dev] as trunk build and dependencies I had to add the following dependencies to be able to build it. Has anybody else seen these issues? --- tomcat/pom.xml (revision 108213) +++ tomcat/pom.xml (working copy) @@ -166,6 +166,11 @@ <dependencies> <!-- Compile (global dependencies) --> +<dependency> +<groupId>jfree</groupId> +<artifactId>jcommon</artifactId> +<version>1.0.2</version> +</dependency> --- depchain/pom.xml (revision 108213) +++ depchain/pom.xml (working copy) @@ -1045,6 +1045,10 @@ <groupId>org.jboss.ws.native</groupId> <artifactId>jbossws-native-services</artifactId> </dependency> +<dependency> +<groupId>org.jboss.ws.native</groupId> +<artifactId>jbossws-native-core</artifactId> +</dependency> --- weld-int/ejb/pom.xml (revision 108213) +++ weld-int/ejb/pom.xml (working copy) @@ -304,6 +304,11 @@ <artifactId>jboss-interceptors-api_1.1_spec</artifactId> </dependency> +<dependency> +<groupId>org.jboss.spec.javax.servlet</groupId> +<artifactId>jboss-servlet-api_3.0_spec</artifactId> +</dependency> Thanks, Alexey _______________________________________________ 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

I had to add the following dependencies to be able to build it. Has anybody else seen these issues? --- tomcat/pom.xml (revision 108213) +++ tomcat/pom.xml (working copy) @@ -166,6 +166,11 @@ <dependencies> <!-- Compile (global dependencies) --> +<dependency> +<groupId>jfree</groupId> +<artifactId>jcommon</artifactId> +<version>1.0.2</version> +</dependency> --- depchain/pom.xml (revision 108213) +++ depchain/pom.xml (working copy) @@ -1045,6 +1045,10 @@ <groupId>org.jboss.ws.native</groupId> <artifactId>jbossws-native-services</artifactId> </dependency> +<dependency> +<groupId>org.jboss.ws.native</groupId> +<artifactId>jbossws-native-core</artifactId> +</dependency> --- weld-int/ejb/pom.xml (revision 108213) +++ weld-int/ejb/pom.xml (working copy) @@ -304,6 +304,11 @@ <artifactId>jboss-interceptors-api_1.1_spec</artifactId> </dependency> +<dependency> +<groupId>org.jboss.spec.javax.servlet</groupId> +<artifactId>jboss-servlet-api_3.0_spec</artifactId> +</dependency> Thanks, Alexey _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

The jbossjts-integration pom is using the "import" scope to include versions for several dependencies. This is known to not work correctly using Maven 2. Are you using Maven 3 on both Linux and Windows when generating the dependency tree? [1]https://repository.jboss.org/nexus/content/repositories/releases/org/jb... On 09/27/2010 11:06 AM, Alexey Loubyansky wrote: > What's happening in my case, is that the build module depends only on > depchain module and needs org.jboss.ws.native:jbossws-native-core:jar > which is missing from depchain. > > If I execute dependency:tree from the build module on the (linux) > machine that can build the AS, I see (among other things): > > [INFO] | +- org.jboss.jbossts:jbossjts-integration:jar:4.11.0.Final:compile > [INFO] | | \- > org.jboss.ws.native:jbossws-native-core:jar:3.3.0.GA:compile (version > managed from 3.3.0.CR1.SP2) > [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.2:compile > > If I execute the same on my (windows) laptop, I get > > [WARNING] Invalid POM for > org.jboss.jbossts:jbossjts-integration:jar:4.11.0.Final, transitive > dependencies (if any) will not be available, enable debug logging for > more details: 2 problems were encountered while building the effective > model for org.jboss.jbossts:jbossjts-integration:4.11.0.Final > [ERROR] 'dependencies.dependency.version' for sun-jaxb:jaxb-api:jar is > missing. @ > [ERROR] 'dependencies.dependency.version' for javax.xml.ws:jaxws-api:jar > is missing. @ > for project org.jboss.jbossts:jbossjts-integration:4.11.0.Final > ... > [INFO] | +- org.jboss.jbossts:jbossjts-integration:jar:4.11.0.Final:compile > > So, I guess, the reason it is not building here (not pulling it > transitively) is because it doesn't like the pom of jbossjts-integration? > > Alexey > > On 9/21/2010 3:59 PM, Alexey Loubyansky wrote: >> I had to add the following dependencies to be able to build it. Has >> anybody else seen these issues? >> >> --- tomcat/pom.xml (revision 108213) >> +++ tomcat/pom.xml (working copy) >> @@ -166,6 +166,11 @@ >> >> <dependencies> >> <!-- Compile (global dependencies) --> >> +<dependency> >> +<groupId>jfree</groupId> >> +<artifactId>jcommon</artifactId> >> +<version>1.0.2</version> >> +</dependency> >> >> --- depchain/pom.xml (revision 108213) >> +++ depchain/pom.xml (working copy) >> @@ -1045,6 +1045,10 @@ >> <groupId>org.jboss.ws.native</groupId> >> <artifactId>jbossws-native-services</artifactId> >> </dependency> >> +<dependency> >> +<groupId>org.jboss.ws.native</groupId> >> +<artifactId>jbossws-native-core</artifactId> >> +</dependency> >> >> --- weld-int/ejb/pom.xml (revision 108213) >> +++ weld-int/ejb/pom.xml (working copy) >> @@ -304,6 +304,11 @@ >> <artifactId>jboss-interceptors-api_1.1_spec</artifactId> >> </dependency> >> >> +<dependency> >> +<groupId>org.jboss.spec.javax.servlet</groupId> >> +<artifactId>jboss-servlet-api_3.0_spec</artifactId> >> +</dependency> >> >> Thanks, >> Alexey >> _______________________________________________ >> 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

Also, do you have M2_HOME set? Some of the build scripts in AS trunk refer to MAVEN_HOME instead of M2_HOME, and this could cause you to use a different version of Maven than you think is being used. On 09/27/2010 12:18 PM, Paul Gier wrote: > The jbossjts-integration pom is using the "import" scope to include > versions for several dependencies. This is known to not work correctly > using Maven 2. Are you using Maven 3 on both Linux and Windows when > generating the dependency tree? > > [1]https://repository.jboss.org/nexus/content/repositories/releases/org/jb... > > On 09/27/2010 11:06 AM, Alexey Loubyansky wrote: >> What's happening in my case, is that the build module depends only on >> depchain module and needs org.jboss.ws.native:jbossws-native-core:jar >> which is missing from depchain. >> >> If I execute dependency:tree from the build module on the (linux) >> machine that can build the AS, I see (among other things): >> >> [INFO] | +- org.jboss.jbossts:jbossjts-integration:jar:4.11.0.Final:compile >> [INFO] | | \- >> org.jboss.ws.native:jbossws-native-core:jar:3.3.0.GA:compile (version >> managed from 3.3.0.CR1.SP2) >> [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.2:compile >> >> If I execute the same on my (windows) laptop, I get >> >> [WARNING] Invalid POM for >> org.jboss.jbossts:jbossjts-integration:jar:4.11.0.Final, transitive >> dependencies (if any) will not be available, enable debug logging for >> more details: 2 problems were encountered while building the effective >> model for org.jboss.jbossts:jbossjts-integration:4.11.0.Final >> [ERROR] 'dependencies.dependency.version' for sun-jaxb:jaxb-api:jar is >> missing. @ >> [ERROR] 'dependencies.dependency.version' for javax.xml.ws:jaxws-api:jar >> is missing. @ >> for project org.jboss.jbossts:jbossjts-integration:4.11.0.Final >> ... >> [INFO] | +- org.jboss.jbossts:jbossjts-integration:jar:4.11.0.Final:compile >> >> So, I guess, the reason it is not building here (not pulling it >> transitively) is because it doesn't like the pom of jbossjts-integration? >> >> Alexey >> >> On 9/21/2010 3:59 PM, Alexey Loubyansky wrote: >>> I had to add the following dependencies to be able to build it. Has >>> anybody else seen these issues? >>> >>> --- tomcat/pom.xml (revision 108213) >>> +++ tomcat/pom.xml (working copy) >>> @@ -166,6 +166,11 @@ >>> >>> <dependencies> >>> <!-- Compile (global dependencies) --> >>> +<dependency> >>> +<groupId>jfree</groupId> >>> +<artifactId>jcommon</artifactId> >>> +<version>1.0.2</version> >>> +</dependency> >>> >>> --- depchain/pom.xml (revision 108213) >>> +++ depchain/pom.xml (working copy) >>> @@ -1045,6 +1045,10 @@ >>> <groupId>org.jboss.ws.native</groupId> >>> <artifactId>jbossws-native-services</artifactId> >>> </dependency> >>> +<dependency> >>> +<groupId>org.jboss.ws.native</groupId> >>> +<artifactId>jbossws-native-core</artifactId> >>> +</dependency> >>> >>> --- weld-int/ejb/pom.xml (revision 108213) >>> +++ weld-int/ejb/pom.xml (working copy) >>> @@ -304,6 +304,11 @@ >>> <artifactId>jboss-interceptors-api_1.1_spec</artifactId> >>> </dependency> >>> >>> +<dependency> >>> +<groupId>org.jboss.spec.javax.servlet</groupId> >>> +<artifactId>jboss-servlet-api_3.0_spec</artifactId> >>> +</dependency> >>> >>> Thanks, >>> Alexey >>> _______________________________________________ >>> 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 >