On Wed, Oct 26, 2011 at 10:36 AM, Stefan Bodewig <bode...@apache.org> wrote:

> On 2011-10-26, Gary Gregory wrote:
>
> > On Wed, Oct 26, 2011 at 9:18 AM, Gary Gregory <garydgreg...@gmail.com
> >wrote:
>
> >> On Wed, Oct 26, 2011 at 8:55 AM, Simone Tripodi <
> simonetrip...@apache.org>wrote:
>
> >>> Hi Gary!
> >>> OK so it is expected because revision number neither SCM branch can be
> >>> determined since the source code is not under the version control!
>
>
> >> Yep, makes sense now.
>
> > Hm.. not so sure now. I am building from my trunk working copy and I get:
>
> > [INFO] --- buildnumber-maven-plugin:1.0:create (default) @
> commons-compress
> > ---
> > [INFO] Change the default 'svn' provider implementation to 'javasvn'.
> > [INFO] Checking for local modifications: skipped.
> > [INFO] Updating project files from SCM: skipped.
> > [WARNING] Cannot get the revision information from the scm repository,
> > proceeding with revision of ?????? :
> > Exception while executing SCM command.
> > [INFO] Storing buildNumber: ?????? at timestamp: 1319638816660
> > [WARNING] Cannot get the branch information from the scm repository,
> > proceeding with UNKNOWN_BRANCH :
> > Exception while executing SCM command.
> > [INFO] Storing buildScmBranch: UNKNOWN_BRANCH
> > [INFO]
>
> > I wonder if this is because I am using Svn 1.7.0 (64-bit) instead of
> > 1.6.x...
>
> I think so.  AFAIK svn 1.7 does away with per-directory .svn dirs and
> stores everything in a single directory at the root of your working
> copy.
>

Yep, that's what Svn 1.7 does.

Gary


>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Reply via email to