Item5806: build.pl -release
cancels with error on new contribs
Priority: Normal
Current State: No Action Required
Released In: 1.0.5
Target Release: n/a
Related to
TWiki:Support.BuildContribOnSVNInstall and on
TWiki:Main.SvenDowideit's recommendation, following a sum-up of what seems to be a bug:
When trying to develop a new Contrib (in this case on a SVN environment) using the
TWiki:Plugins.BuildContrib, creating the new extension with
create_new_plugin.pl
works just fine. But when getting to the point that a
-release
shall be prepared (using the
build.pl
which is inside the directories of the new Contrib) an
error occurs, indicating that some SVN info cannot be found. Obviously, because the Contrib has not been commited to SVN before. Same happens when running
build.pl
with the
-test
parameter.
- build.log: Output of running
perl build.pl release
; the file is located within the Contrib directory and was generated by BuildContrib
--
TWiki:Main/SebastianKlus - 23 Jul 2008
Sorry, my first comment was totally wrong, and
WillNorris made me figure out what we discussed with
CrawfordCurrie when I implemented support for git.
BuildContrib parses Subversion (or git now) history to figure out what version it's currently using, so it can automagically replace it.
The idea is that, if neither is found, the version number is set to the current time. This is in fact very useful for Crawford's automagic porting of extensions from Foswiki to TWiki, because it copies and replaces things on the fly, but the resulting files aren't stored in Subversion.
So for me, this is fixed in the latest trunk, and has been fixed since
distro:a4cd7a79516d (I broke it a bit earlier :))
Therefore, I'm closing this bug. Please re-open if you still find some issues with
BuildContrib (the one in trunk).
--
OlivierRaginel - 06 Jun 2009