Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-users@maven.apache.org
Received-SPF: pass (asf.osuosl.org: domain of james.shute@lehman.com
 designates 192.147.57.144 as permitted sender)
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: Project specific build.properties for Maven1 build
Date: Thu, 6 Apr 2006 09:24:42 +0100
Message-ID: 
 <8DEDAF68EB79CA4BB2FCB204C9FCCCA7045DCC32@logisexm007.leh.lbcorp.lehman.com>
Thread-Topic: Project specific build.properties for Maven1 build
Thread-Index: AcZZU4zYaeZO5hEsTem4AajwhicwqA==
From: "Shute, James" <james.shute@lehman.com>
To: "Continuum Users" <continuum-users@maven.apache.org>
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi,

Just started using Continuum and am really liking it, but have just 1
small issue I can't seem to find an answer to.

One of our projects, which is built using Maven 1, needs a machine
specific property set (it's an absolute path to a specific file), so
that goes in build.properties in the project dir and each developer sets
it to the correct value for their box.  It's potentially different on
each box, hence it can't go in project.properties.

Now I tried fixing our build under Continuum by adding the
build.properties file with the value set into the working area, but next
time a CVS update happens during the build that file gets wiped out and
the build fails again.

=46or now I've got it working by putting the setting in the system wide
build.properties file, but that's not an ideal solution as this property
is only really relevant to this 1 project.

Is there some way round this, or shall I file a JIRA=3F

thanks

James

---------------------------------------------------------------------------=
---
This message is intended only for the personal and confidential use of the =
designated recipient(s) named above.  If you are not the intended recipient=
 =
of this message you are hereby notified that any review, dissemination, =
distribution or copying of this message is strictly prohibited.  This =
communication is for information purposes only and should not be regarded a=
s=
 an offer to sell or as a solicitation of an offer to buy any financial =
product, an official confirmation of any transaction, or as an official =
statement of Lehman Brothers.  Email transmission cannot be guaranteed to b=
e=
 secure or error-free.  Therefore, we do not represent that this informatio=
n=
 is complete or accurate and it should not be relied upon as such.  All =
information is subject to change without notice.