RE: [JBoss-dev] Re: Library dependencies/updates for jboss-4.0.5.GA
by Dimitris Andreadis
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">
> <!--
> A jarjar ant build script to create the jarjard dom4j jar.
> -->
> <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
>
19 years, 6 months
Re: JBossMQ in JBoss5
by Adrian Brock
Encouragement is fine.
But telling a contributor that his work is useless is not.
Especially when that reason is based on irrelevant
JBoss.com development policy that doesn't affect them.
I already promised him that the work could go in JBoss4
once he had it working and tested in JBoss5.
Converting JBossMQ deployments to JBoss Messaging
deployments is not an option for everybody.
Forcing such a conversion would just leave certain
users/customers stuck with JBoss4.
Supporting JBossMQ within JBoss5 is no different
to supporting JBossMQ within JBoss4 since it is
the same codebase.
I expect the market to decide that JBoss Messaging
is better than JBossMQ (it already is, even before
the upcoming clustering features)
and the number of JBossMQ users will gradually diminish to zero.
On Fri, 2006-09-15 at 17:58 +0000, Andrig T Miller wrote:
> Adrian,
>
> Every new feature that is developed for JBossMQ has to also be
> put into JBoss Messaging. It doesn't matter who does the work, in my
> mind. New features of any kind should NOT be put into JBossMQ. If
> the community wants to contribute something, they need to be
> encouraged to contribute to JBoss Messaging.
>
> On the topic of JBossMQ still being in AS 5, I was not aware that
> that was an official decision. If that is the case, that decision
> needs to be revisted, in my opinion. I see no reason to have both
> code bases in AS 5, considering that customers application code is not
> affected by the change, only server configuration. I would rather see
> us take a little time to develop a conversion utility for the
> migration of the configuration between the two, as part of our
> productizing AS 5 and JBoss Messaging, then see us support the old
> code base.
>
> Andy
>
> On Fri, 2006-09-15 at 14:45 +0200, Adrian Brock wrote:
> > http://jira.jboss.com/jira/browse/JBAS-2156
> > plus some others.
> >
> > JBossMQ will be a part of JBoss5.
> > I've already had to correct this statement on the WIKI before.
> >
> > JBoss Messaging will be the default, JBossMQ will be optional
> > for those that need to keep using their JBossMQ configuration
> > within JBoss5.
> >
> > We will remove support for JBossMQ once people have had time
> > to migrate, i.e. probably JBoss6 or maybe 7 depending upon
> > when JBoss6 is released.
> >
> > Development of major new features for JBossMQ by JBoss
> > has already stopped except for those requested by paying customers,
> > e.g. XARecovery integration with JBossTM is the latest example.
> >
> > That does not preclude development by the community.
> >
> > The example above is a feature provided by the community.
> > JBoss.com policy towards JBossMQ should not affect this work!
> Andrig (Andy) Miller
> VP, Engineering
> JBoss, a division of Red Hat
--
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx
19 years, 6 months
RE: [JBoss-dev] Updating jboss-common jars
by Dimitris Andreadis
Thanks, I corrected the page because it was pointing to the old
locations (common/trunk/common-x rather than common/common-x/trunk)
I've noticed also you need to build the modules in a certain order, is
that expected?
Finally, any idea how to change the location of the local repository
(defaults to $HOME/.m2/repository)
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org
> [mailto:jboss-development-bounces@lists.jboss.org] On Behalf
> Of Alexey Loubyansky
> Sent: Monday, September 18, 2006 10:37 AM
> To: JBoss.org development list
> Subject: Re: [JBoss-dev] Updating jboss-common jars
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCommonProject
>
> Dimitris Andreadis wrote:
> > Is there any wiki how the common modules are build?
> >
> >> -----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 9:09 AM
> >> To: JBoss.org development list
> >> Subject: Re: [JBoss-dev] Updating jboss-common jars
> >>
> >> The MC_VDF_WORK branch build files and eclipse project files have
> >> been updated to refer to the jars built from the 2.0.0 tags:
> >>
> >> https://svn.jboss.org/repos/common/common-core/tags/2.0.0/
> >> https://svn.jboss.org/repos/common/common-logging-spi/tags/2.0.0/
> >> https://svn.jboss.org/repos/common/common-logging-log4j/tags/2.0.0/
> >> https://svn.jboss.org/repos/common/common-logging-jdk/tags/2.0.0/
> >>
> >> The trunk will be updated when the MC_VDF_WORK branch is
> merged this
> >> week.
> >>
> >> Scott M Stark wrote:
> >>> I don't know where the current jboss-common.jar in trunk and the
> >>> MC_VDF_WORK branch is coming from, so I'm going to update
> these two
> >>> branches to use a 2.0 build of the refactored projects:
> >>> https://svn.jboss.org/repos/common/{common-core,
> >> common-logging-jdk,
> >>> common-logging-log4j, common-logging-spi}.
> >>>
> >>> This will end up replacing the lib/jboss-common.jar with
> >>>
> >>
> lib/{jboss-common-core-2.0.jar,jboss-logging-spi-2.0.jar,jboss-loggin
> >> g
> >>> -log4j-2.0.jar,
> >>>
> >>> jboss-logging-jdk-2.0.jar}.
> >> _______________________________________________
> >> 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
> >
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
19 years, 6 months
