In addtion,
 
I already previously removed build.xml for this reason from head/master, as it inteferred with the CI stuff that we are already running.
 
Paul


 
On Fri, Jul 29, 2011 at 4:13 PM, John Reese <john@noswap.com> wrote:
On 07/29/2011 10:38 AM, noreply@github.com wrote:
>    Branch: refs/heads/master-1.2.x
>    Home:   https://github.com/mantisbt/mantisbt
>
>    Commit: 3b3400f1b4a6f5d13d22c09f1d56bc5a5f2b7672
>        https://github.com/mantisbt/mantisbt/commit/3b3400f1b4a6f5d13d22c09f1d56bc5a5f2b7672
>    Author: Robert Munteanu<robert.munteanu@gmail.com>
>    Date:   2011-07-29 (Fri, 29 Jul 2011)
>
>    Changed paths:
>      M build.xml
>
>    Log Message:
>    -----------
>    First version of building a installable archive and calculating checksums
>
>...

As I mentioned in issue #11339, we already have a set of scripts [1]
that will build a set of release tarballs, including documentation, and
it can do that from a fresh git clone to ensure that it represents
exactly what's in the upstream repositories.  Why are we duplicating
this effort into a build system that requires the repository already be
checked out to the ref we want to build?

https://github.com/mantisbt/mantisbt-tools

--
John Reese
noswap.com

------------------------------------------------------------------------------
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
mantisbt-dev mailing list
mantisbt-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev