Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Content to include in the POM: 
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-50
       
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-3726
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-4506
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-4921
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-2216
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-3608
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-3879
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-5926
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-2916
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-5563
       (perhaps it is a legitimate concern for plugins to require parameters that have defined values from somewhere... unclear if this affects the POM though) 
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-5900
       Open question do we want properties? and if we do, what interpolation rules would apply... how would parent, mix-in, platform, profiles etc take effect...
    supports / provides type concepts: 
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-1775657
       WONT FIX I do not see the value in splitting content out of the pom... that way leads to profiles.xml which was madness
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-5652
      Jira
      5659
       WONT FIX I do not see the value in splitting content out of the pom... that way leads to profiles.xml which was madness
  • supports / provides type concepts: 
    • Jira
      serverASF JIRA
      serverId
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-1977177
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-23165652
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-23161977
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-58672316
       
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-
    624Lifecycle related changes
    • 2316
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-1935867
       (since the symmetry will feed into the lifecycle definition syntax perhaps)
  • Versioning
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-683624
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-3522
       (effectively superseded as you can augment the lifecycle from within the POM and thus provide any additional phases you require in order to ensure the sequencing required)
      4173
       (should just do this for 5.0.0. No more plugin version "magic")
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-5517
       WONT FIX I do not see the value in moving from the range syntax to a less mathematically complete syntax
  • Lifecycle related changes
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-5384193
       (since the symmetry will feed into the lifecycle definition syntax perhaps)
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-683
       (this one is really important as we want to be able to enable light-weight multi-module builds that just don't fail where "clean install" would succeed - solving this will mean that the reactor can proceed across all modules as required in order to deliver the requirements of the "driving" module(s))
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-56653522
       (need to ensure that we address this need in the lifecycle declaration syntax)
    Scope related changes
    • effectively superseded as you can augment the lifecycle from within the POM and thus provide any additional phases you require in order to ensure the sequencing required)
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-18675384
       (effectively addressed above as we remove all "special" scopes replacing them with convention)this one is really important as we want to be able to enable light-weight multi-module builds that just don't fail where "clean install" would succeed - solving this will mean that the reactor can proceed across all modules as required in order to deliver the requirements of the "driving" module(s))
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-61075665
       (need to ensure that we address this need in the lifecycle declaration syntax)
  • Scope related changesBetter profile activation
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-33261867
       (effectively addressed above as we remove all "special" scopes replacing them with convention)
    • Jirajira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-38266107
  • Better profile activation
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-5650
    How to format the POM
    • 3326
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-3397
       /
      3826
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-5653
       (effectively addressed in the current proposal)
      5650
  • How to format the POM
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-6061
       switching to a DSL should be considered... though I suspect a new compact XML would be less of an issue while retaining some ability to allow earlier maven versions to at least print semi-sensible errors if attempt is made to build new pom with old maven
    Mix-ins
    • 3397
       /
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-5102
       / 
      Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-5588
       (should be addressed with the current proposal, but need to review what the ask in this issue was to see if any gaps exist
      5653
       (effectively addressed in the current proposal)
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-6061
       switching to a DSL should be considered... though I suspect a new compact XML would be less of an issue while retaining some ability to allow earlier maven versions to at least print semi-sensible errors if attempt is made to build new pom with old maven
  • Mix-ins4173 (should just do this for 5.0.0. No more plugin version "magic")
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-
    5517
    • 5102
     WONT FIX I do not see the value in moving from the range syntax to a less mathematically complete syntax
    •  / 
      Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-
    5654
    • 5588
       (
    effectively addressed above)
    Jira
    serverASF JIRA
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b
    keyMNG-5657
     / 
    • should be addressed with the current proposal, but need to review what the ask in this issue was to see if any gaps exist)
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyMNG-
    5659
    • 5654
       (effectively addressed above)
     WONT FIX I do not see the value in splitting content out of the pom... that way leads to profiles.xml which was madness