[MNG-7369] Maven BOM doesn't need to package as a JAR

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-2, 4.0.0
• Component/s: General
• Labels: up-for-grabs
• Assignee: Michael Osipov
• Reporter: Maarten Mulders
• Created: 19/Dec/21 15:49
• Updated: 20/Oct/22 08:11
• Resolved: 02/Jan/22 15:25

Description

The new Maven BOM module packages as a JAR file, which is almost empty:

$ unzip -l maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar 
Archive:  maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
  Length      Date    Time    Name
---------  ---------- -----   ----
      358  01-26-2020 09:04   META-INF/MANIFEST.MF
        0  01-26-2020 09:04   META-INF/
        0  01-26-2020 09:04   META-INF/maven/
        0  01-26-2020 09:04   META-INF/maven/org.apache.maven/
        0  01-26-2020 09:04   META-INF/maven/org.apache.maven/maven-bom/
      272  01-26-2020 09:04   META-INF/DEPENDENCIES
    11358  01-26-2020 09:04   META-INF/LICENSE
      179  01-26-2020 09:04   META-INF/NOTICE
     6260  01-26-2020 09:04   META-INF/maven/org.apache.maven/maven-bom/pom.xml
       77  01-26-2020 09:04   META-INF/maven/org.apache.maven/maven-bom/pom.properties
---------                     -------
    18504                     10 files

The Maven BOM module should package as "pom" to avoid this.

Issue Links

• Discovered while testing: MNG-7357 All Maven Core JARs have unusual entry order
• links to: GitHub Pull Request #647