[jboss-dev] differences between pom.xml / build-thirdparty.xml
Dimitris Andreadis
dandread at redhat.com
Thu Mar 13 16:45:12 EDT 2008
The components versions in the two files are very much out-of-sync:
pom.xml build-thirdparty.xml
junit 3.8.1 3.8.2-brew
aop 2.0.0-SNAPSHOT 2.0.0.CR7
microcontainer 2.0.0.Beta10 2.0.0.Beta10.1
security 2.0.2.Beta5 2.0.2.Beta5 but jbosssx at 2.0.2-SNAPSHOT
oswego 1.3.4-jboss 1.3.4-jboss-update1
antlr 2.7.7 2.7.6-brew
apache-discovery 0.2 0.4-brew
apache-logging 1.0.4-jboss 1.1.0.jboss
apache-myfaces 1.1.0 1.1.3
apache-slide 2.0 2.1-brew
apache-velocity 1.4 1.4jboss
apache-xalan j_2.7.0 2.7.0.patch01-brew
apache-xerces 2.9.1 ` 2.9.0
apache-xmlsec ` 1.2.97 1.3.0
cglib 2.1_3 2.1.3
dom4j 1.6.1-jboss 1.6.1
gnu-getopt 1.0.13 1.0.12-brew
hibernate 3.2.4.SP1 3.2.4.SP1_CP01-brew
hibernate-annotations 3.3.0.ga 3.3.1.Beta1
hibernate-commons-annotations
3.0.0.ga 3.0.0.GA
hibernate-entitymanager 3.3.2.Beta1 3.3.2.Beta3
hsqldb 1.8.0.7 1.8.0.8-brew
jacorb 2.3.0jboss.patch4-brew 2.3.0jboss.patch5-brew
jacorb-idl 2.2.2.jboss.patch3
javassist 3.6.0.GA 3.7.1.GA
jaxen 1.1-beta-11 1.1-brew
common-logging-jdk 2.0.4.GA 2.0.2.GA
common-logging-log4j 2.0.4.GA 2.0.2.GA
common-logging-spi 2.0.4.GA 2.0.2.GA
jboss-ejb3-cache 0.13.0-SNAPSHOT 0.11.1
jboss-ha-client 1.0.0.BETA1 1.0.0.GA
jboss-jaspi-api 1.0.0-SNAPSHOT 1.0-BETA1
jboss-managed 2.0.0-SNAPSHOT 2.0.0.snapshot
jboss-vfs 2.0.0.Beta7 2.0.0.snapshot
jbossws-context 2.1.0.snapshot
jbossws-framework 3.0.0.GA
jbossws-framework-scripts3.0.0.GA
jbossws-spi 1.0.1.GA
jbossws snapshot
jbossxb 2.0.0-SNAPSHOT 2.0.0.CR5
metadata 1.0.0-SNAPSHOT 1.0.0.Beta6
microcontainer 2.0.0.Beta10 2.0.0.Beta10.1
remoting 2.2.1.GA 2.4.0.Beta2
joesnmp 0.3.3 0.3.4
junit 3.8.1 3.8.2-brew
qdox 1.6 1.6.1
sun-opends 1.0.0-BUILD04 0.1.0.build016
trove 2.1.1 1.0.2
osgi 4.0
osgi_R4_compendium 1.0
osgi_R4_core 1.0
objectweb-joramtests ??? 1.5
jms-integration-tests ??? 1.0.1.GA
jboss/integration ??? 5.0.0.Beta4
javamail ??? 1.4
sun-javac 4.0 3.2
javaee There are multiple jars at different -SNAPSHOT level, that ok?
recorded as:
org.beanshell beanshell
bcel apache-bcel
commons-beanutils apache-beanutils
commons-codec apache-codec
commons-collections apache-collections
commons-digester apache-digester
commons-fileupload apache-fileupload
Snapshot plugins - shouldn't those be tagged???
<groupId>org.codehaus.mojo</groupId>
<artifactId>jboss-packaging-maven-plugin</artifactId>
<version>2.0-SNAPSHOT</version>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-1-jboss-1-SNAPSHOT</version>
<groupId>org.codehaus.mojo</groupId>
<artifactId>rmic-maven-plugin</artifactId>
<version>1.0-alpha-1-SNAPSHOT</version>
Dimitris Andreadis wrote:
> I'll go through root pom.xml to see what are the differences with
> build/build-thirdparty.xml when it was removed.
>
> Adrian Brock wrote:
>> JBossXB is currently at 2.0.0.CR7, why use a snapshot?
>>
>> The error message indicates some other problem anyway
>> since that class has been in JBossXB "forever".
>>
>> e.g. did you see Alex's comment about Xerces 2.6.1 getting
>> downloaded by maven instead of 2.9.1?
>>
>> Looks like a spurious transient dependency to me.
>>
>> I've fixed a lot of this kind of thing in the MC build
>> use
>> mvn dependency:list
>>
>> and fix them
>>
>> e.g. Don't let jboss-test choose an older version
>> of jboss-common-core, etc....
>>
>> <dependency>
>> <groupId>org.jboss</groupId>
>> <artifactId>jboss-test</artifactId>
>> <exclusions>
>> <exclusion>
>> <groupId>jboss</groupId>
>> <artifactId>jboss-common-core</artifactId>
>> </exclusion>
>> <exclusion>
>> <groupId>jboss</groupId>
>> <artifactId>jboss-common-logging-spi</artifactId>
>> </exclusion>
>> </exclusions>
>> </dependency>
>>
>>
>> On Thu, 2008-03-13 at 19:37 +0200, Dimitris Andreadis wrote:
>>> The root AS5 pom.xml refers to jbossxb 2.0.0-SNAPSHOT. The removed
>>> build/build-thirdparty.xml was referencing 2.0.0.CR5 instead.
>>>
>>> Do we need to revert? The server fails to start with the snapshot:
>>>
>>> 18:52:41,578 INFO [ServerImpl] Starting Microcontainer,
>>> bootstrapURL=file:/X:/c
>>> vs/jboss-public/jboss-head/build/output/jboss-5.0.0.CR1/server/all/conf/bootstra
>>>
>>> p-beans.xml
>>> Exception in thread "main" java.lang.NoClassDefFoundError:
>>> org/jboss/xb/binding/
>>> UnmarshallerFactory
>>> at
>>> org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.<clinit>(Bas
>>> icXMLDeployer.java:52)
>>> at
>>> org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java
>>> :98)
>>> at
>>> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
>>> 398)
>>> at org.jboss.Main.boot(Main.java:209)
>>> at org.jboss.Main$1.run(Main.java:544)
>>> at java.lang.Thread.run(Thread.java:595)
>>> 18:52:41,593 INFO [ServerImpl] Runtime shutdown hook called,
>>> forceHalt: true
>>> 18:52:41,593 INFO [ServerImpl] Shutdown complete
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
More information about the jboss-development
mailing list