1 Reply Latest reply on Nov 9, 2009 7:15 PM by Oisin Hurley

    Updating dependent versions

    biggiesmallz Newbie

      Hail,

       

      I discovered the need to apply a specific patch to one of my dependencies. As I am new to some of the techniques used for project build and management with these technologies, I pose my question for you guys.

       

      What is the best practice way to apply a patch?

       

      I see many pom.xml files and feature.xml files which specify specific versions of dependencies. I would prefer not to have to modify these files.

       

      Should I apply the patch to my dependency and rebuild having a different version number and then modify each and every pom/feature to make use of this patched version?

       

      Should I apply the patch and leave the version numbers as is? But this means if I distribute my own project's source that my fix would not apply on other people's machines because they would be using the unpatched version maven pulled off a repository.

       

      Ideally I would like to include the patch as part of my projects build cycle, either by including the 1 patched .java file in my src path and have it built along with my project. Or as an already built patched library included with my project that will be used instead of the unpatched version needed by FUSE.

       

      Basically, I want my patched .java to be loaded by FUSE and used by FUSE and my project, not the unpatched version.

       

      How best to accomplish this?

       

      Toodles,

      -bs

       

      -


      "Never get high on your own supply."

        • 1. Re: Updating dependent versions
          Oisin Hurley Novice

           

          What is the best practice way to apply a patch?

           

           

          Submit the patch to the target project's bug tracker - the best way to get patches out there is to contribute them to the project.

           

          If that won't work for you, the practical option is to do as you suggest here:

           

           

          Should I apply the patch to my dependency and rebuild having a different version number and then modify each and every pom/feature to make use of this patched version?

           

           

          You don't mention if the patch is a runtime or a build-time dependency. The approach you take will vary depending on which it is.

           

          I know my reply isn't very specific, but the question of managing the versions and projects is fairly general, and people do it differently, depending on what they want to get out of it.