On Sat, 19 Jan 2013 04:34:10 PM Michael Vehrs wrote: > Right, I am now working only with the git repo. Assuming that my commit > earlier today was done according to best practices, I am ready to go.
Looks good to me.
> By the way, I noticed that the svnproperties and gitproperties tasks do
> not work (for me, at least),
Ah. My mistake, I had forgotten about that nasty hack. What is happening
there is that we need to find a value to set Package-Version to in the
MANIFEST.MF. We all used to use svnproperties, which uses {svn, <svn-repo>}
to set a bunch of properties in build/svn.properties, including svn.Revision
which is what we use.
When I started using git, I introduced the gitproperties task to do the same
with {git, <svn-repo>}. In hindsight I should have called it
gitsvnproperties.
Now that we have {git, <git-repo>}, neither tasks work. I will sort this out
shortly.
> and that several unit tests failed due to missing files.
I am not seeing any test suite failures. I suspect you are right and that is
a local problem.
Cheers,
Mike Pope
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_123012
_______________________________________________ Freecol-developers mailing list Freecol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freecol-developers
