List Info

Thread: jbossxb at 2.0.0-SNAPSHOT or 2.0.0.CR5
jbossxb at 2.0.0-SNAPSHOT or 2.0.0.CR5
user name
 2008-03-13 12:37:07 
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/serv
er/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(Server
Impl.java
:98)
         at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerI
mpl.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-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
Re: jbossxb at 2.0.0-SNAPSHOT or 2.0.0.CR5
user name
 2008-03-13 12:28:24 
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/serv
er/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(Server
Impl.java
> :98)
>          at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerI
mpl.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-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
Re: jbossxb at 2.0.0-SNAPSHOT or 2.0.0.CR5
user name
 2008-03-13 12:50:05 
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/serv
er/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(Server
Impl.java
>> :98)
>>          at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerI
mpl.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-developmentlists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
Re: jbossxb at 2.0.0-SNAPSHOT or 2.0.0.CR5
user name
 2008-03-13 12:51:47 
Good luck 

Judging by what I'm seeing (downloading it for the first
time),
there's all sorts of rubbish in the dependencies.

I've already seen xerces 2.2.0 and 2.4.1 being downloaded
jboss-test 1.0.3 and 1.0.5
and a couple of different versions of the jaxb apis.

I think I need to buy a new disk 

What's ironic is that the only way I've managed to make
Maven usable/stable is to blow away my whole maven
repository
on a regular basis (especially before doing releases!)

If I don't do that, it starts doing weird things
that aren't reproducable by anybody else or even
myself once I've deleted the repository.

At this rate its going to take me "hours" to
repopulate it
for the appserver build when I do that. :-(

Time to investigate how to use different local repositories
for different builds.

On Thu, 2008-03-13 at 19:50 +0200, 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/serv
er/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(Server
Impl.java
> >> :98)
> >>          at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerI
mpl.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-developmentlists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
> _______________________________________________
> jboss-development mailing list
> jboss-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
Re: jbossxb at 2.0.0-SNAPSHOT or 2.0.0.CR5
user name
 2008-03-13 13:20:33 
On Thu, 2008-03-13 at 19:50 +0200, 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.

There's no tag from just before this change.

So if anybody needs to reget build-thirdparty.xml use

svn co https
://svn.jboss.org/repos/jbossas/trunk/build70793

70793 == 70794-1 where 70794 is the version that changed to
maven.

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

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
Re: jbossxb at 2.0.0-SNAPSHOT or 2.0.0.CR5
user name
 2008-03-13 13:47:40 
I see a different issue (this is what I like about maven
it always produces the same results for everybody 

It is caused by it using an early access runtime
of JAXB 2.0

 javax.xml:jaxb-impl:jar:2.0EA3:compile

The old build used sun-jaxb:2.1.4

This is specified in the root pom.xml
where did these versions come from, was it guesswork? 

19:38:13,275 ERROR [AbstractKernelController] Error
installing to
Create: name=ManagedConnectionFactoryParserDeployer
state=Configured
java.lang.NoClassDefFoundError:
javax/xml/bind/annotation/AccessorOrder
        at
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createCla
ssInfo(RuntimeModelBuilder.java:59)
        at
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createCla
ssInfo(RuntimeModelBuilder.java:41)
        at
com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(Mod
elBuilder.java:123)
        at
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassI
nfo(RuntimeModelBuilder.java:49)
        at
com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassI
nfo(RuntimeModelBuilder.java:41)
        at
com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(Mode
lBuilder.java:189)
        at
com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(Mode
lBuilder.java:204)
        at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(J
AXBContextImpl.java:327)
        at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAX
BContextImpl.java:198)
        at
com.sun.xml.bind.v2.ContextFactory.createContext(ContextFact
ory.java:76)
        at
com.sun.xml.bind.v2.ContextFactory.createContext(ContextFact
ory.java:55)
        at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:
211)
        at
javax.xml.bind.ContextFinder.find(ContextFinder.java:372)
        at
javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)

        at
javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)

        at
org.jboss.resource.deployers.ManagedConnectionFactoryParserD
eployer.create(ManagedConnectionFactoryParserDeployer.java:1
21)


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/serv
er/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(Server
Impl.java
> :98)
>          at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerI
mpl.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-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
differences between pom.xml / build-thirdparty.xml
user name
 2008-03-13 15:45:12 
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</artifactI
d>
         <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/serv
er/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(Server
Impl.java
>>> :98)
>>>          at 
>>>
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerI
mpl.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-developmentlists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
> _______________________________________________
> jboss-development mailing list
> jboss-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
Re: jbossxb at 2.0.0-SNAPSHOT or 2.0.0.CR5
country flaguser name
United States		 2008-03-13 16:18:57 
Adrian Brock wrote:
 > What's ironic is that the only way I've managed to
make
 > Maven usable/stable is to blow away my whole maven
repository
 > on a regular basis (especially before doing
releases!)

Have you tried using the dependency plugin to clear only the

dependencies for the project you're releasing?  Sometimes
this helps me 
quite a bit:

mvn dependency:purge-local-repository

S,
ALR
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
Re: differences between pom.xml / build-thirdparty.xml
user name
 2008-03-13 16:26:35 
On Thu, 2008-03-13 at 22:45 +0200, Dimitris Andreadis
wrote:
> The components versions in the two files are very much
out-of-sync:

You didn't mention jaxb or the jboss-managed problem?

I say we invoke "Bill's rule" and revert back to
the previous
build until this is working properly. 

This should never have been committed in this state.

The server doesn't even boot, how can people work?

I have a working build by 

1) reverting
build/build.xml
build/build-thirdparty.xml
testsuite/build-thirdparty.xml

2) rm -rf thirdparty/*

3) build clean most
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
Re: differences between pom.xml / build-thirdparty.xml
user name
 2008-03-13 16:53:21 

  


  

    
Yes, let's do that. Create a tmp branch to work this out Paul.




Adrian Brock wrote:

warjort" type="cite">
  
On Thu, 2008-03-13 at 22:45 +0200, Dimitris Andreadis wrote:
  

  

    
The components versions in the two files are very much out-of-sync:
    

  

  

You didn't mention jaxb or the jboss-managed problem?

I say we invoke "Bill's rule" and revert back to the previous
build until this is working properly. 

This should never have been committed in this state.

The server doesn't even boot, how can people work?

I have a working build by 

1) reverting

build/build.xml
build/build-thirdparty.xml
testsuite/build-thirdparty.xml


2) rm -rf thirdparty/*

3) build clean most
  






  

  
  
   
     
    






 [1-10] [11-20] [21-30] [31-33]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )