Closed GoogleCodeExporter closed 8 years ago
Hi Jeff, I wonder if it would be possible to specify the project name in the
build.properties file instead? I deliberately avoid making project-specific
changes in build.xml so I can easily drop in newer versions, but if it were
externalised that might work.
Original comment by will.abson
on 24 May 2011 at 2:24
[deleted comment]
Having tried this out on another project, it is possible to override the
project name if a second build script which simply includes build.xml is added
to the project. That allows the stock build.xml to be used without
customisation (and updated when new versions are available), whilst providing a
custom project name in the Ant view using the second build script.
In my project I named the second build script 'project.xml', but any name will
do
<project basedir="." default="dist-jar" name="My XXXX Share Customisations">
<!-- Import properties and targets from stock build script -->
<import file="build.xml" />
</project>
You could also override any of the build targets by redeclaring them in this
file with the customisations you require, rather the modifying the original
build.xml.
Feel free to re-open the ticket, Jeff, if this doesn't work for you.
Original comment by will.abson
on 7 Nov 2011 at 3:10
Original issue reported on code.google.com by
jeffpotts01
on 9 May 2011 at 11:03Attachments: