Re: [JBoss-dev] CVS update: build/jbossmq build.xml
This change will break the release-* targets, as well as the consistency
model where files are generated. Why do you need to work off of this
directory for project.release output?
--jason
On Wed, 22 Aug 2001, Hiram Chirino wrote:
User: chirino
Date: 01/08/22 08:15:47
Modified:jbossmq build.xml
Log:
These changes should allow jboss-mq to build ok again.
Revision ChangesPath
1.6 +2 -2 build/jbossmq/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/jbossmq/build.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- build.xml 2001/08/18 04:55:09 1.5
+++ build.xml 2001/08/22 15:15:47 1.6
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.5 2001/08/18 04:55:09 user57 Exp $ --
+!-- $Id: build.xml,v 1.6 2001/08/22 15:15:47 chirino Exp $ --
project default=main basedir=..
@@ -74,7 +74,7 @@
| thirdparty.root - Where to thirdparty libraries live
--
property name=project.output value=${project.config}/output/
- property name=project.release value=${project.output}/
+ property name=project.release value=${project.config}/build/
property name=tools.root value=${project.root}/tools/
property name=thirdparty.root value=${project.root}/thirdparty/
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jbossmq build.xml
Hi Jason,
I guess this is not the best way, but it was the quickest way I could get it
to build the standalone binary distribution right. What I need the build to
do is:
- go through all the modules and release thier normal jboss output.
- Filter out some of those file (JBossMQ standalone does not need all the
JBoss jars) to come up with a the MQ release.
So, the change I did has the modules place their release output into
${project.config}/build which then is copied/filtered/configured to
${project.output} (by the mqrelease target).
What do you think is a better solution???
Regards,
Hiram...
From: Jason Dillon [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] CVS update: build/jbossmq build.xml
Date: Wed, 22 Aug 2001 12:39:30 -0700 (PDT)
This change will break the release-* targets, as well as the consistency
model where files are generated. Why do you need to work off of this
directory for project.release output?
--jason
On Wed, 22 Aug 2001, Hiram Chirino wrote:
User: chirino
Date: 01/08/22 08:15:47
Modified:jbossmq build.xml
Log:
These changes should allow jboss-mq to build ok again.
Revision ChangesPath
1.6 +2 -2 build/jbossmq/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/jbossmq/build.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- build.xml 2001/08/18 04:55:09 1.5
+++ build.xml 2001/08/22 15:15:47 1.6
@@ -10,7 +10,7 @@
!--
--
!--
== --
-!-- $Id: build.xml,v 1.5 2001/08/18 04:55:09 user57 Exp $ --
+!-- $Id: build.xml,v 1.6 2001/08/22 15:15:47 chirino Exp $ --
project default=main basedir=..
@@ -74,7 +74,7 @@
| thirdparty.root - Where to thirdparty libraries live
--
property name=project.output value=${project.config}/output/
- property name=project.release value=${project.output}/
+ property name=project.release value=${project.config}/build/
property name=tools.root value=${project.root}/tools/
property name=thirdparty.root
value=${project.root}/thirdparty/
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jbossmq build.xml
On Wed, 22 Aug 2001, Hiram Chirino wrote:
I guess this is not the best way, but it was the quickest way I could get it
to build the standalone binary distribution right.
No worries. I know the current release stuff for shared modules has
problems.
What I need the build to do is:
- go through all the modules and release thier normal jboss output.
- Filter out some of those file (JBossMQ standalone does not need all the
JBoss jars) to come up with a the MQ release.
I need to figure out an elegant way to allow the project control module to
pull from source modules instead of having them push, as you mentioned
before. I am going to be switching over my corporate build systems from an
other version of BM, so I should probably beable to fix that too (and test
it and such), then update jboss.
So, the change I did has the modules place their release output into
${project.config}/build which then is copied/filtered/configured to
${project.output} (by the mqrelease target).
What do you think is a better solution???
It is fine for now, just note that the other release-* targets won't
function like this.
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
