Menu

External tools and tasks

Developers
2005-07-28
2013-04-25
  • Ivan Ivanov

    Ivan Ivanov - 2005-07-28

    Dear colleagues,

    I had just inspected sqlunit's build.xml and found that it contains several hardcoded paths to external tools like jalopy, checkstyle and xdoclet.
    I think that these paths should be isolated in external properties files. I already created these files on my local machine namely:
    build.properties - configures the default locations of the above locations; should be store in CVS;
    local.build.properties -  gives the user the ability to overrides the default tools locations; if used should not be stored in CVS repository.

    This will make sqlunit's build.xml more flexible, for example I use both Linux in home and Windows in my work so /usr/java/checkstyle is not an option for my Windows machine. Having local.build.properties will allow to override these settings.

    Is it appropriate to commit these changes?

    Regards
    Ivan

     
    • Sujit Pal

      Sujit Pal - 2005-07-30

      Hi Ivan,

      I think it is, although, you should probably check in an empty build.user.properties file with the keys that need to be updated (if possible with some inline comments) so people know what to replace in these files if they need to.

      -sujit

       
    • Ivan Ivanov

      Ivan Ivanov - 2005-08-03

      I just added build.properties and touched build.xml to read its properties from build.properties, which contains the instructions how to override the properties settings.

      Regards
      Ivan

       
    • Sujit Pal

      Sujit Pal - 2005-08-09

      Thank you, I will download it tonight.

      -sujit

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.