September 2006 - jboss-development

jboss-4.0-testsuite-sun-1.5 Build Timed Out

by qa＠jboss.com

19 years, 6 months

1
0
0 / 0

jboss-portal-2.6-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

19 years, 6 months

1
0
0 / 0

jbossws-4.0-testsuite-1.5 Build Completed With Testsuite Errors

by qa＠jboss.com

19 years, 6 months

1
0
0 / 0

Re: [JBoss-dev] Re: JBossMQ in JBoss5

by Andrig T Miller

JBossMQ will be an optional module in AS 5 for those customers that have specific issues with converting over to JBoss Messaging, but JBoss Messaging will be the default. We need to stay on top of any and all feature development in JBossMQ that may happen from the community. Of course, we need to do our best to direct that effort at JBoss Messaging instead. We have to make sure that JBossMQ doesn't contain features that JBoss Messaging doesn't have. Andrig (Andy) Miller VP, Engineering JBoss, a division of Red Hat

19 years, 6 months

2
2
0 / 0

jboss-4.0-testsuite-1.5 Build Completed With Testsuite Errors

by qa＠jboss.com

19 years, 6 months

1
0
0 / 0

RE: [JBoss-dev] Re: Library dependencies/updates for jboss-4.0.5.GA

by Dimitris Andreadis

I think we should take the jarjar approach. Later, we could change to use the jaxp APIs. In the (unlikely) event we break somebody, he could change to the other CTOR: public XMBean(Object resource, org.w3c.dom.Element element, String version) > -----Original Message----- > From: jboss-development-bounces(a)lists.jboss.org > [mailto:jboss-development-bounces@lists.jboss.org] On Behalf > Of Scott M Stark > Sent: Tuesday, September 19, 2006 5:49 PM > To: Adrian Brock > Cc: JBoss.org development list > Subject: Re: [JBoss-dev] Re: Library dependencies/updates for > jboss-4.0.5.GA > > Ok, but there are zero uses of that ctor in the codebase. Its > going to be broken one way or another if you jarjar or revert > to the jaxp apis. > > Adrian Brock wrote: > > org.dom4j.Element element = ... > > XMBean mbean = new XMBean(object, element, version); > > server.registerMBean(mbean); > > > > Won't work if it is org.jboss.dom4j.Element > > > > > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development >

19 years, 6 months

1
0
0 / 0

RE: [JBoss-dev] Re: Library dependencies/updates for jboss-4.0.5.GA

by Dimitris Andreadis

With a quick search I've found org.dom4j usage in the A) jmx module (DescriptorSupport, JBossXMBean10, XMLMetadata, XMBean) B) deployment module (DeploymentMetadata, DeploymentManagerImpl) C) console module (XMLToHTMLTreeBuilder) D) build (VersionRelease) - not realy an issue Should I switch all to use org.jboss.dom4j and bundle with jboss-jmx.jar? Or Switch the jmx module, bundle with jboss-jmx.jar and, include the original dom4j.jar in server/lib for the others (including end-user code that depends on dom4j). But then, our jarjar'ed version would have to be in a different place in the repository (can't have 2 versions of the same thing), like repository.jboss.com/jboss/dom4j/1.6.1.jarjar > -----Original Message----- > From: jboss-development-bounces(a)lists.jboss.org > [mailto:jboss-development-bounces@lists.jboss.org] On Behalf > Of Dimitris Andreadis > Sent: Tuesday, September 19, 2006 3:00 PM > To: Steve Ebersole; Emmanuel Bernard; Scott M Stark > Cc: JBoss.org development list > Subject: RE: [JBoss-dev] Re: Library dependencies/updates for > jboss-4.0.5.GA > > What about Hibernate usage of dom4j? > > If I make the jmx/system code use the jarjard version, > hibernate will need to include it seperately. > > > -----Original Message----- > > From: jboss-development-bounces(a)lists.jboss.org > > [mailto:jboss-development-bounces@lists.jboss.org] On > Behalf Of Scott > > M Stark > > Sent: Monday, September 18, 2006 8:02 PM > > To: JBoss.org development list > > Subject: Re: [JBoss-dev] Re: Library dependencies/updates for > > jboss-4.0.5.GA > > > > I have put the jarjard dom4j jar into the repository here: > > http://repository.jboss.com/dom4j/1.6.1.jarjar > > > > It contains the dom4j-jarjar.jar (which uses an > org.jboss.dom4j root > > package namespace), and the jarjar build script: > > <project name="Jarjar dom4j" default="patchdom4j"> > >  > > <target name="patchdom4j"> > > <taskdef name="jarjar" > > classname="com.tonicsystems.jarjar.JarJarTask" > > classpath="dist/jarjar-0.7.jar"/> > > <mkdir dir="output" /> > > <jarjar jarfile="output/dom4j-jarjar.jar"> > > <manifest> > > <attribute name="Created-by" > > value="${java.vm.version} ${java.vm.vendor}"/> > > <attribute name="Specification-Title" > > value="Dom4j > > JarJar(org.jboss.dom4j)"/> > > <attribute name="Specification-Version" > > value="1.6.1"/> > > <attribute name="Specification-Vendor" > > value="http://dom4j.org/"/> > > <attribute name="Implementation-Title" > > value="JarJar > > Dom4j"/> > > <attribute name="Implementation-URL" > > value="http://repository.jboss.com/dom4j/1.6.1.jarjar"/> > > <attribute name="Implementation-Version" > > value="1.6.1.jarjar"/> > > <attribute name="Implementation-Vendor" > > value="JBoss, > > a division of Red Hat"/> > > <attribute name="Implementation-Vendor-Id" > > value="http://www.jboss.org"/> > > </manifest> > > <zipfileset src="dom4j.jar"/> > > <rule pattern="org.dom4j.**" > result="org.jboss.dom4j.@1"/> > > <zap pattern="org.dom4j.jaxb.**"/> > > <zap pattern="org.dom4j.swing.**"/> > > <zap pattern="org.dom4j.xpath.**"/> > > </jarjar> > > </target> > > </project> > > > > All that is left is to update all the bootstrap modules which use > > dom4j > > (jmx/j2se/system/system-jmx) to use the new namespace. The > dom4j jars > > could be embedded into one of these module output jars as an > > implementation detail to reduce the number of bootstrap jars if > > desired. > > > > Scott M Stark wrote: > > > It would be kept in the server/default/lib for app > > compatibility. It > > > would just be embedded in the core jmx/system layer as an > > impl detail > > > and removed from the server bootstrap classpath. > > > > > > Emmanuel Bernard wrote: > > >> Keep Steve in the loop since Hibernate use dom4j > > >> > > > > > > > _______________________________________________ > > 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 >

19 years, 6 months

3
6
0 / 0

RE: [JBoss-dev] Re: JBossMQ in JBoss5

by Dimitris Andreadis

> OK, but I suspect we will keep having a dumb "zip" version, no? We haven't really discussed this, but my guess is yes. > > Adrian Brock wrote: > > On Tue, 2006-09-19 at 10:54 +0100, Tim Fox wrote: > > > >> For customers who really don't want to / can't move to JBoss > >> Messaging when they move to JB5 , then we can provide a > download and > >> a script they can run, as Sacha has suggested. I think > this makes more sense. > >> > > > > The installer is the script. > > > > If it doesn't already, it is certainly planned that this should be > > runnable in "headless" mode. > > > > Eventually, this is really just going to create profiles anyway. > > > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development >

19 years, 6 months

5
8
0 / 0

jboss-4.0-testsuite-sun-1.4 Build Completed With Testsuite Errors

by qa＠jboss.com

19 years, 6 months

1
0
0 / 0

RE: [JBoss-dev] Re: JBossMQ in JBoss5

by Dimitris Andreadis

The size argument will be less of an issue though, as the jems installer bundle gets bigger (includes portal, seam, etc.), unless we come up with a *jboss* only installer. Then, we have the redhat rpm'ised distro to consider, too :) > On Tue, 2006-09-19 at 08:54 -0400, Tom Elrod wrote: > > Or > > > > 1) Download jboss-5.0.0.zip > > 2) unzip jboss-5.0.0.zip > > > > Notice how few '-' there were. ;) > > And also notice: > > 1) how much longer it took to download > 2) you've got no clue what you need to do to make a minimal > JMS server or WebServer or add an Oracle datasource, etc. > > If anybody actually used the default configurations in > production (with hypersonic, badly configured CMP, all the > debug options enabled, etc.) I'd be more impressed with your > arguments. > > Adrian Brock

19 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-development September 2006