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 Changes Path
> 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