[jboss-dev-forums] [Design of JBoss Transaction Services] - Re: bundling JTS into AS 5.0

[adrian@jboss.org]

"jhalliday" wrote : Umm, JBossTS is already integrated. The AS build system handles the .jar versioning just fine, thanks. 
  | 

Only because you do all the integration in your project which is the wrong way around.

anonymous wrote : 
  | All I need to do is add a couple of text files to the AS.
  | 

Configuration is also integration.

anonymous wrote : 
  | You seem to be telling me that requires messing around with maven artefacts, poms and such. No wonder this thing is behind schedule if it's that hard to get anything done. varia needs to stay, it's far more suitable for my needs :-)

It's even more delayed/broken when to do a simple fix to the integration
(not the implementation) needs a whole new release cycle of a dependent project
and makes integration with other versions impossible.

Implementation -> your project
policy == integration -> jbossas

I've had this argument with the aop, jboss messaging, remoting and webservices projects,
so far I'm winning, but only just. 
I'm only winning when I find out somebody is doing it wrong. ;-)

By way of an example, I'm going to need a jbosstm integration project in jbossas
to fix the "port" problem we were discussing, i.e. replace the GUID mechanism.

Now if my mechanism is generic, I can contribute it back to JBossTM.
If it is a JBossAS specific mechanism then it belongs in that source tree.

The real test is whether you created a circular dependency in your build:

jbossas -> jbossts -> jbossas

In your case, it's even worse (you have the same problem jbossws used to have).
You're not even compiling over a version controlled version of jboss


  |         <condition property="jboss.home" value="${env.JBOSS_HOME}">
  |             <isset property="env.JBOSS_HOME"/>
  |         </condition>
  | 
  |         <path id="build.classpath">
  |             <fileset dir="${com.arjuna.mwlabs.installation.lib.directory}">
  | 				<include name="**/*.jar"/>
  | 				<include name="**/*.zip"/>
  | 			</fileset>
  | 			<filelist dir="${jboss.lib.dir}" files="${jboss.libs}"/>
  | 			<filelist dir="${jboss.client.lib.dir}" files="${jboss.client.libs}"/>
  |             <filelist dir="${jboss.server.lib.dir}" files="${jboss.server.libs}"/>
  |         </path>
  | 

Who knows how to reproduce you're binaries?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174581#4174581

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174581