Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-3948

Experiment with placing poms outside of src



    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0-ALPHA
    • Component/s: general/build
    • Labels:
    • Lucene Fields:
      New, Patch Available


      Recent work in LUCENE-3944 has changed how our generated pom.xml files are handled during release preparation, placing them in build/ instead. However get-maven-poms still places the poms inside src/ so you can use them to drive a build. What I think would be ideal is if we could unify the release handling of the poms and the normal building handling, so that the poms can sit outside of src and serve both purposes.

      Some time ago I investigated how the ANT project handles its own Maven integration and it has its poms sitting in their own directory. They then reference the actual src locations inside the poms. This works for ANT but with a warning since some of their tests don't work due to how the Maven surefire plugin works, so they skip their tests.

      I have done some quick testing of my own and this process does seem to work for our poms and tests. I now want to take this to a full scale POC and see if it works fully.


        1. LUCENE-3948.patch
          66 kB
          Steven Rowe
        2. LUCENE-3948.patch
          59 kB
          Steven Rowe
        3. LUCENE-3948.patch
          61 kB
          Chris Male
        4. LUCENE-3948.patch
          56 kB
          Steven Rowe
        5. LUCENE-3948.patch
          56 kB
          Chris Male



            • Assignee:
              sarowe Steven Rowe
              cmale Chris Male
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: