What a trully bizzare diff... I don't understand how it comes up with
this... but whatever works.
--jason
Jason Dillon wrote:
> User: user57
> Date: 02/04/19 16:40:36
>
> Modified:jbossTag: Branch_3_0 build.xml
> Log:
> o include iiop & jboss.net in standard group
> o drop o
User: user57
Date: 02/04/19 16:40:36
Modified:jbossTag: Branch_3_0 build.xml
Log:
o include iiop & jboss.net in standard group
o drop optional-requires-config (becomes optional)
Revision ChangesPath
No revision
No rev
You beat me :-)))
Claudio
> -Original Message-
> From: Francisco Reverbel [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 19, 2002 3:25 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-dev] CVS update: build/jboss build.xml
>
> User: reverbel
>
User: reverbel
Date: 02/04/19 06:24:58
Modified:jbossTag: Branch_3_0 build.xml
Log:
Merged change from HEAD: copy iiop-service.xml to deploy dir.
Revision ChangesPath
No revision
No revision
1.117.2.2 +10 -1 bui
User: cgjung
Date: 02/04/19 00:47:58
Modified:jbossbuild.xml
Log:
axis.jar in jboss-net.jar.
Revision ChangesPath
1.121 +1 -37 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvs
User: cazzius
Date: 02/04/17 09:19:52
Modified:jbossbuild.xml
Log:
copy iiop-service.xml in deploy
Revision ChangesPath
1.120 +10 -1 build/jboss/build.xml
Index: build.xml
===
RCS file:
User: starksm
Date: 02/04/16 10:37:07
Modified:jbossbuild.xml
Log:
Main is now 3.1 development
Revision ChangesPath
1.119 +3 -3 build/jboss/build.xml
Index: build.xml
===
RCS file: /cv
User: user57
Date: 02/04/15 15:50:23
Modified:jbossbuild.xml
Log:
o optional members now part of standard
o optional-requires-config -> optional
* will deal with detecting config for optional later
Revision ChangesPath
1.118 +6 -9 build/jboss/build.
User: starksm
Date: 02/04/15 02:36:40
Modified:jbossTag: Branch_3_0 build.xml
Log:
Update the version info
Revision ChangesPath
No revision
No revision
1.117.2.1 +3 -3 build/jboss/build.xml
Index: build.x
User: d_jencks
Date: 02/04/13 21:31:56
Modified:jbossbuild.xml
Log:
A little config cleanup and possible solution to jdk1.4 hslqdb login problem
Revision ChangesPath
1.117 +14 -2 build/jboss/build.xml
Index: build.xml
==
User: chirino
Date: 02/04/12 16:30:07
Modified:jbossbuild.xml
Log:
Updated jbossmq config so that it is better organized.
Revision ChangesPath
1.116 +5 -18 build/jboss/build.xml
Index: build.xml
User: cgjung
Date: 02/04/09 03:01:35
Modified:jbossbuild.xml
Log:
techtrader reflection for WSDL generation needed.
Revision ChangesPath
1.115 +6 -1 build/jboss/build.xml
Index: build.xml
=
User: d_jencks
Date: 02/04/06 18:59:30
Modified:jbossbuild.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.114 +8 -1 build/jboss/build.xml
Index: build.xml
===
User: user57
Date: 02/04/03 14:29:35
Modified:jbossbuild.xml
Log:
o applied patch: [ 523396 ] AutoNumber not being built, plus it's broken...
Revision ChangesPath
1.113 +2 -1 build/jboss/build.xml
Index: build.xml
==
User: d_jencks
Date: 02/03/24 16:36:17
Modified:jbossbuild.xml
Log:
fix so there is only one hsql config copied. This copies the new one, obvious
change to go back to the old one
Revision ChangesPath
1.112 +3 -1 build/jboss/build.xml
Index: build.xml
User: ejort
Date: 02/03/23 13:10:59
Modified:jbossbuild.xml
Log:
JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more
complete ejblink test that currently fails
Revision ChangesPath
1.111 +14 -21build/jboss/build.xml
Index:
User: cgjung
Date: 02/03/12 02:55:21
Modified:jbossbuild.xml
Log:
Axis Beta RC1 is here. Needs some log4j extensions and wsdl4j
to be present at runtime.
Revision ChangesPath
1.110 +12 -3 build/jboss/build.xml
Index: build.xml
=
User: starksm
Date: 02/03/11 14:32:02
Modified:jbossbuild.xml
Log:
Remove the reference to the non-existent jsr77.jar
Revision ChangesPath
1.109 +1 -8 build/jboss/build.xml
Index: build.xml
User: patriot1burke
Date: 02/03/10 22:29:40
Modified:jbossbuild.xml
Log:
added cluster module back into build
Revision ChangesPath
1.108 +2 -2 build/jboss/build.xml
Index: build.xml
===
User: schaefera
Date: 02/03/10 20:31:31
Modified:jbossbuild.xml
Log:
Moved the JSR-77 code to the new "management" module. It contains the
specification implementation for MEJB and the JBoss implementation.
It does not contain references to JBoss server.
The only workar
User: user57
Date: 02/03/09 17:57:50
Modified:jbossbuild.xml
Log:
o added management module config (not hooked up to standard group yet)
o added example hook
Revision ChangesPath
1.106 +66 -1 build/jboss/build.xml
Index: build.xml
===
User: user57
Date: 02/03/08 18:48:02
Modified:jbossbuild.xml
Log:
o drop jboss- prefix
Revision ChangesPath
1.105 +2 -2 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/
User: user57
Date: 02/03/08 18:45:34
Modified:jbossbuild.xml
Log:
o re-enable jboss-pool.jar copy to lib
o minor hack to reuse jca-sar jboss-service.xml
Revision ChangesPath
1.104 +21 -2 build/jboss/build.xml
Index: build.xml
User: starksm
Date: 02/03/07 22:19:43
Modified:jbossbuild.xml
Log:
Restore the jetty module build
Revision ChangesPath
1.103 +3 -2 build/jboss/build.xml
Index: build.xml
===
RCS file:
User: mnf999
Date: 02/03/07 11:04:08
Modified:jbossbuild.xml
Log:
REMOVED JETTY UNTIL CLUSTER IS FIXED.
THE BAD NEWS IS JULES WILL BE AT THE LONDON TRAINING, SO SOMEONE FROM CLUSTER NEEDS
TO FIX THAT OR SOMEONE FROM JETTY. SACHA WILL BE AT THE TRAINING ALSO.
SO IT
User: mnf999
Date: 02/03/07 09:45:46
Modified:jbossbuild.xml
Log:
build for client interceptors
include the new client classes
TEMP: removal of the cluster stuff until bill adapts it
Revision ChangesPath
1.101 +2 -2 build/jboss/build.xml
Index: bu
User: neales
Date: 02/03/07 09:03:52
Modified:jbossbuild.xml
Log:
o Replace org.jboss.proxy.compiler with a BCEL implementation
o Add a test for this.
Revision ChangesPath
1.100 +8 -1 build/jboss/build.xml
Index: build.xml
User: user57
Date: 02/03/04 19:16:04
Modified:jbossbuild.xml
Log:
o Directories will be created if they do not exist (even for log/)
Revision ChangesPath
1.99 +1 -13 build/jboss/build.xml
Index: build.xml
===
User: kimptoc
Date: 02/02/28 00:43:05
Modified:jbossbuild.xml
Log:
added date to the test results email subject, for ease of threading on forums
Revision ChangesPath
1.98 +6 -3 build/jboss/build.xml
Index: build.xml
=
User: user57
Date: 02/02/27 17:28:37
Modified:jbossbuild.xml
Log:
o initial xdoclet todo integration
Revision ChangesPath
1.96 +10 -1 build/jboss/build.xml
Index: build.xml
===
RCS f
User: user57
Date: 02/02/27 01:24:24
Modified:jbossbuild.xml
Log:
o Release structure and server config changes
Revision ChangesPath
1.95 +125 -121 build/jboss/build.xml
Index: build.xml
User: user57
Date: 02/02/25 23:24:52
Modified:jbossbuild.xml
Log:
o removed install-dependencies, each module hook will copy the
required thiordparty bits it requires unless a dependent module
already copied it
Revision ChangesPath
1.94 +118 -86 b
User: user57
Date: 02/02/25 18:19:02
Modified:jbossbuild.xml
Log:
o build file clean up
Revision ChangesPath
1.93 +70 -98build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot
User: user57
Date: 02/02/24 17:23:30
Modified:jbossbuild.xml
Log:
o system has no static docs
Revision ChangesPath
1.92 +1 -9 build/jboss/build.xml
Index: build.xml
===
RCS file: /c
User: user57
Date: 02/02/24 02:41:34
Modified:jbossbuild.xml
Log:
o moved catalina to optional-requires-config group
o fixed optional group def (these are modules not groups)
o Added most group set, which includes everything that should
build with no extra config
User: user57
Date: 02/02/24 02:24:28
Modified:jbossbuild.xml
Log:
o moved core system from server to system (includes
all of org.jboss.system, some of org.jboss.deployment +
Main, Shutdown & Version)
o finished the integration of ServerLoader, Server and
Ser
There will not be another beta release for at least a couple weeks.
- Original Message -
From: "David Jencks" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, February 21, 2002 7:56 PM
Subject: R
Are you about to do another beta build? I've finished my changes for the
ear deployer problem, I think it fixes 1 bug in the testsuite, and I'm
finishing an explicit test case. If no one objects I'd like to check it in
before the next beta.
thanks
david jencks
On 2002.02.21 21:51:16 -0500 Sco
User: starksm
Date: 02/02/21 18:51:16
Modified:jbossbuild.xml
Log:
Beta Rel_3_0_0_3 is already history
Revision ChangesPath
1.89 +3 -3 build/jboss/build.xml
Index: build.xml
===
RCS f
User: chirino
Date: 02/02/21 15:33:19
Modified:jbossbuild.xml
Log:
Finished integrating the new Boot class into the build system.
Revision ChangesPath
1.88 +2 -1 build/jboss/build.xml
Index: build.xml
User: starksm
Date: 02/02/21 12:27:54
Modified:jbossbuild.xml
Log:
Create an empty log/server.log to make the dumb unarchiver tools
create the log directory
Revision ChangesPath
1.87 +3 -1 build/jboss/build.xml
Index: build.xml
===
On Tue, 19 Feb 2002, Scott M Stark wrote:
> We won't do releases of Jetty as Mortbay has their own Sourceforge
> project that handles that.
Understood, that's not what I mean to imply.
What I meant, was that if a thirdparty checkins in source, and when doing,
they use the same tagname as what w
quot;Jason Dillon" <[EMAIL PROTECTED]>
Cc: "Scott M Stark" <[EMAIL PROTECTED]>; "JBoss Development"
<[EMAIL PROTECTED]>
Sent: Tuesday, February 19, 2002 6:52 PM
Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml
> On Tue, 19 Feb 2002, Jason Dil
On Tue, 19 Feb 2002, Jason Dillon wrote:
> Like the JBossMQ and JBossMX stuff...
Or what about thirdparty projects that are maintained in jboss cvs(ie, jetty)?
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/l
.
- Original Message -
From: "Jason Dillon" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, February 19, 2002 6:14 PM
Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml
> Like the JBossMQ and JBossMX stu
TED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, February 19, 2002 5:59 PM
> Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml
>
>
> > Ok, so I am not as crazy as I though I was. Basically if we were to start
> > tagging other projects then we coul
What do you mean by other projects?
- Original Message -
From: "Jason Dillon" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, February 19, 2002 5:59 PM
Subject: Re: [JBoss-dev] CVS update: build/
tt M Stark wrote:
> We are still using those tag names, what do you call this?
>
>
> - Original Message -
> From: "Jason Dillon" <[EMAIL PROTECTED]>
> To: "Scott M Stark" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent:
We are still using those tag names, what do you call this?
- Original Message -
From: "Jason Dillon" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, February 19, 2002 5:37 PM
Subject: Re: [JBoss-
I thought we were still using R_* and Branch_* for tag names. As for the
rest, I was just getting lost in the esthetics. I agree that we should
include cvs tag information.
--jason
On Tue, 19 Feb 2002, Scott M Stark wrote:
>
> > Why does the server need to know anything about the source con
> Why does the server need to know anything about the source controlsystem
> which is being used to manage its sources?
>
> Pet names, as you say, are a time honored tradition amoung software
> developers. The are also used as a rememberance tool. Many folks will be
> more inclinded to remeber
Why does the server need to know anything about the source controlsystem
which is being used to manage its sources?
Pet names, as you say, are a time honored tradition amoung software
developers. The are also used as a rememberance tool. Many folks will be
more inclinded to remeber rabbit-hole
ssage -
From: "Jason Dillon" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, February 17, 2002 4:36 PM
Subject: Re: [JBoss-dev] CVS update: build/jboss build.xml
> version.name was never meant to have anyth
version.name was never meant to have anything to do with cvs. It is
there to hold the rather arbitrary name of a release (ie. rabbit-hole or
whistler or merlin). While understand your desire to include cvs tag
information, I do not think that this is the best place for it.
I suggest we add a ve
User: reverbel
Date: 02/02/17 13:50:26
Modified:jbossbuild.xml
Log:
Pointer to JacORB library has been deleted somehow. Added again.
Revision ChangesPath
1.86 +5 -1 build/jboss/build.xml
Index: build.xml
==
User: starksm
Date: 02/02/17 07:44:38
Modified:jbossbuild.xml
Log:
Document the use of version.name as the cvs tag for any release build
Revision ChangesPath
1.85 +2 -1 build/jboss/build.xml
Index: build.xml
=
User: starksm
Date: 02/02/17 07:07:14
Modified:jbossbuild.xml
Log:
Update the version info for the next beta release
Revision ChangesPath
1.84 +2 -2 build/jboss/build.xml
Index: build.xml
=
User: user57
Date: 02/02/17 01:52:54
Modified:jbossbuild.xml fix-workspace.xml
Log:
o revert to j2ee, connector & messaging
Revision ChangesPath
1.83 +27 -27build/jboss/build.xml
Index: build.xml
User: user57
Date: 02/02/16 22:13:28
Modified:jbossbuild.xml
Log:
o moved JMSRA to resource module
o repackaged under org.jboss.resource.jms
Revision ChangesPath
1.82 +3 -4 build/jboss/build.xml
Index: build.xml
User: user57
Date: 02/02/16 20:22:23
Modified:jbossbuild.xml
Log:
o Some re-org in preperation for a 3.0 release
o Added ejb & system modules
o Renamed messaging to mq, I don't know what I was thinking when I changed
it in the first place.
o Connector becomes re
User: user57
Date: 02/02/15 22:36:49
Modified:jbossbuild.xml
Log:
o building jboss-common-client.jar, cause clients won't care about alot
of what is in here (and should not have to care)
Revision ChangesPath
1.80 +2 -2 build/jboss/build.xml
Ind
User: user57
Date: 02/02/15 20:16:31
Modified:jbossbuild.xml
Log:
o CounterService moved from server to varia
o Repackaged under org.jboss.varia.counter
o Added counter-service.xml, which should go into an example
deployment directory, but now just gets dropped int
User: user57
Date: 02/02/15 17:33:25
Modified:jbossbuild.xml
Log:
o cleaned up server/src/etc a bit. Probably need to reconsider how
we paqkage configuration files, since our notion of a configuration file
has changed so much with the recent deployable xml stuff.
User: user57
Date: 02/02/15 15:34:26
Modified:jbossbuild.xml
Log:
o these don't exist anymore
Revision ChangesPath
1.76 +1 -4 build/jboss/build.xml
Index: build.xml
===
RCS file: /c
User: user57
Date: 02/02/15 00:28:38
Modified:jbossbuild.xml
Log:
o HypersonicDatabase will now create its directory under db/ when it is
no there.
o not creating db/hypersonic or db/jbossmq directories from build anymore
o scheme.ini take a hike, unless you can fi
User: user57
Date: 02/02/15 00:17:20
Modified:jbossbuild.xml
Log:
o hrm...
Revision ChangesPath
1.74 +2 -2 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/
User: user57
Date: 02/02/15 00:11:01
Modified:jbossbuild.xml
Log:
o Moved MailService to varia, made is use the xml snippent stuff
to get its properties (this is *ucking cool) and made it deployable
with mail-service.xml
Revision ChangesPath
1.73 +1
User: user57
Date: 02/02/14 22:22:54
Modified:jbossbuild.xml
Log:
o no conf files right now
Revision ChangesPath
1.72 +1 -9 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvs
User: user57
Date: 02/02/14 22:12:25
Modified:jbossbuild.xml
Log:
o plugins maddness removed
Revision ChangesPath
1.71 +74 -58build/jboss/build.xml
Index: build.xml
===
RCS file: /cv
User: user57
Date: 02/02/12 20:19:22
Modified:jbossbuild.xml
Log:
o cleaned up server most hook, re-use existing directory based
tasks to copy files... its faster!
o adding jbossmq-testsuite-service.xml (hack) really need to have
seperate configurations, one for
User: user57
Date: 02/02/11 19:22:01
Modified:jbossbuild.xml
Log:
o Adding SafeObjectFactory, which simply makes ObjectNames and
turns ant malformed exceptions into Errors. This is used to
create ObjectName OBJECT_NAME fields, so we don't have to keep
creating
User: patriot1burke
Date: 02/02/04 13:25:59
Modified:jbossbuild.xml
Log:
JavaGroups 2.0
Revision ChangesPath
1.68 +2 -2 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jb
User: ejort
Date: 02/02/01 18:58:14
Modified:jbossbuild.xml
Log:
Add jmx to the standard compile, required in the testsuite
Revision ChangesPath
1.67 +28 -2 build/jboss/build.xml
Index: build.xml
User: mnf999
Date: 02/01/28 14:41:21
Modified:jbossbuild.xml
Log:
cluster compiles
Revision ChangesPath
1.66 +3 -3 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss
User: mnf999
Date: 02/01/20 07:04:41
Modified:jbossbuild.xml
Log:
new deployers
Revision ChangesPath
1.65 +87 -22build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/bu
User: olegnitz
Date: 02/01/16 17:30:40
Modified:jbossbuild.xml
Log:
Jetty jar files are now built from sources
Revision ChangesPath
1.64 +7 -23 build/jboss/build.xml
Index: build.xml
===
User: user57
Date: 02/01/03 16:08:26
Modified:jbossbuild.xml
Log:
o Consolodate server module install tasks.
o Stop copying tmp.properties, db.properties, ...
Revision ChangesPath
1.63 +19 -109 build/jboss/build.xml
Index: build.xml
==
User: user57
Date: 02/01/02 20:00:51
Modified:jbossbuild.xml
Log:
o migrated all components to a new JMX domain name model. jboss.system
is now where to core/spine components live. moved all components that
were in JBOSS-SYSTEM that did not move into a jboss.* dom
User: ejort
Date: 02/01/01 09:54:27
Modified:jbossbuild.xml
Log:
Removed Logging Analysis Service
Revision ChangesPath
1.61 +1 -9 build/jboss/build.xml
Index: build.xml
===
RCS file
User: patriot1burke
Date: 01/12/31 12:51:19
Modified:jbossbuild.xml
Log:
added cluster back into standard
Revision ChangesPath
1.60 +2 -2 build/jboss/build.xml
Index: build.xml
===
RCS
User: ejort
Date: 01/12/23 10:51:34
Modified:jbossbuild.xml
Log:
Log Analysis Service for debugging logging calls.
Will probably want removing before 3.0 goes stable.
Revision ChangesPath
1.59 +11 -3 build/jboss/build.xml
Index: build.xml
===
User: mnf999
Date: 01/12/18 12:55:51
Modified:jbossbuild.xml
Log:
Removing cluster from the build TEMPORARY will put it back as soon as build is fixed
for cluster (next on my plate)
Revision ChangesPath
1.58 +2 -2 build/jboss/build.xml
Index: build.
User: user57
Date: 01/12/08 21:22:56
Modified:jbossbuild.xml
Log:
o include shutdown.jar
Revision ChangesPath
1.57 +2 -1 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroo
Diff is really odd sometimes... why did it decide that I added a new set of
end tags and then filled in the rest. I don't think I could do that if I
wanted too. I would get too confused.
--jason
>
>
> @@ -898,6 +898,14 @@
>
>
>
> +
> +
wow, sf mailing lists are really slow, this was done yesterday...
--jason
__
View: http://jboss.org/forums/thread.jsp?forum=66&thread=4930
___
Jboss-development mailing list
[EMAIL PRO
User: user57
Date: 01/12/06 22:55:28
Modified:jbossbuild.xml
Log:
o added cluster-service.xml to the release
Revision ChangesPath
1.56 +9 -1 build/jboss/build.xml
Index: build.xml
===
User: user57
Date: 01/12/06 17:04:36
Modified:jbossbuild.xml
Log:
o changed release to use the modules-most target (which does not generate/
install docs)
o added release-full, which get the previous behavior
Revision ChangesPath
1.55 +8 -2 build
User: user57
Date: 01/12/05 21:13:04
Modified:jbossbuild.xml
Log:
o added source-* targets to build a free and external (tools and thirdparty)
source release distribution.
Revision ChangesPath
1.54 +92 -1 build/jboss/build.xml
Index: build.xml
User: user57
Date: 01/12/05 19:09:20
Modified:jbossbuild.xml
Log:
o fixed run-jboss target
Revision ChangesPath
1.53 +3 -3 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsr
User: peter_f
Date: 01/11/26 16:15:28
Modified:jbossbuild.xml
Log:
Removed InstantDB references and files
Revision ChangesPath
1.51 +1 -5 build/jboss/build.xml
Index: build.xml
===
R
User: d_jencks
Date: 01/11/22 10:06:46
Modified:jbossbuild.xml
Log:
Cleaned up jbosscx packaging a little. Put jbosspool.jar in jbosscx.sar
Revision ChangesPath
1.50 +3 -10 build/jboss/build.xml
Index: build.xml
===
User: d_jencks
Date: 01/11/19 07:34:04
Modified:jbossbuild.xml
Log:
Repackaged jetty to use jar-in-sar
Revision ChangesPath
1.49 +10 -15build/jboss/build.xml
Index: build.xml
===
RCS fi
User: user57
Date: 01/11/16 20:13:58
Modified:jbossbuild.xml
Log:
o help should depend on init to get the correct module.Name
Revision ChangesPath
1.48 +3 -3 build/jboss/build.xml
Index: build.xml
==
User: user57
Date: 01/11/15 14:14:46
Modified:jbossbuild.xml
Log:
o removed modules-cluster & cluster-only targets
o removed cluster-only group
* use -Dmodules=cluster to only build the cluster module
Revision ChangesPath
1.47 +1 -32 build/jboss/bui
User: schaefera
Date: 01/11/11 20:24:18
Modified:jbossbuild.xml
Log:
Reworked Farm which is now part of clustering and uses JavaGroups. Right
now only the "farm-service.xml" must be deployed on each node of the
farm and then servies must be placed into "/jboss/deploy/farm" a
User: chirino
Date: 01/11/08 22:26:36
Modified:jbossbuild.xml
Log:
Created a new JBossMQ IL that uses the HA framework.
Revision ChangesPath
1.45 +3 -1 build/jboss/build.xml
Index: build.xml
==
thanks sorry for that
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Wednesday, October 31, 2001 2:58 PM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] CVS update: build/jboss build.xml
|
|
| User: starksm
| Date: 01/10
User: starksm
Date: 01/10/31 11:58:27
Modified:jbossbuild.xml
Log:
Remove the obsolete idb.jar
Revision ChangesPath
1.44 +1 -4 build/jboss/build.xml
Index: build.xml
===
RCS file: /cv
User: chirino
Date: 01/10/20 22:38:12
Modified:jbossbuild.xml
Log:
Feature add:
You can now setup a JBossMQ connection with out using JNDI.
The ConnectionTestCase has a test case in case your interested on how it
is done.
Revision ChangesPath
1.43 +4 -3
User: starksm
Date: 01/10/20 16:52:52
Modified:jbossbuild.xml
Log:
Add a run-basic-testsuite to the main build.xml file that invokes
the tests-unit target in the testsuite module. This test should be run
prior to any commits to ensure a minimum compatibility level with the
1 - 100 of 133 matches
Mail list logo