#133 checkstyle.basedir not OS agnostic

release_3.2
closed
1
2012-10-10
2003-01-06
Daniel Cox
No

It would be nice if the checking of the basedir property
converted OS file separators in the property value to "/".

Discussion

  • Lars Kühne

    Lars Kühne - 2003-01-11

    Logged In: YES
    user_id=401384

    This is a feature request, not a bug - moving to RFE tracker.

    Daniel, could you please elaborate why this would be a
    useful feature for you? I never had any problems with the
    basedir property, just use ant's ${basedir} and things just
    work. Why do you need the feature you requested?

     
  • Daniel Cox

    Daniel Cox - 2003-01-11

    Logged In: YES
    user_id=662432

    First, sorry about putting this in as a bug - don't know what I
    was thinking.

    The basedir property can obviously be specified without using
    ${basedir} from ant. In my particular case I was using
    ${basedir} + a hard coded path fragment. Generally ant tasks
    tend to be file separator agnostic. You can mix them up
    however you like. This isn't the case with checkstyle as the
    comparison of the path fragment with the full filename doesn't
    do any file separator conversion.

    This is very low priority - its just that us M$-centric people we
    are used to having case-insensitivy and using "\" and want to
    force the world to submit to the one true way ;). (Actually I
    don't really care - I just wish it were all the same)

     
  • Daniel Cox

    Daniel Cox - 2003-01-11

    Logged In: YES
    user_id=662432

    Whoa - browser messed something up there. move the "we"
    on a separate line to the end of the following line.

     
  • Oleg Sukhodolsky

    Logged In: YES
    user_id=746148

    Implemenation committed in CVS for 3.2

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks