[MNG-5384] Declarative artifacts

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.4
• Fix Version/s: Issues to be reviewed for 4.x
• Component/s: Artifacts and Repositories, POM, Reactor and Workspace
• Assignee: Unassigned
• Reporter: Tuomas Kiviaho
• Created: 22/Nov/12 02:36
• Updated: 24/Oct/21 21:26

Description

Currently there's no way to know which attachments a project is going to have beforehand. Lack of this feature is currently patched inside Aether where test-jar for instance has a special treatment prior packaging phase so that we can get a file pointer to ${project.target.testOutputDirectory}.

Maven 2 had this hack embedded inside of it, but with Maven 3 the project attachments list doesn't contain test-jar until it is actually added to the project. I had to patch MBUILDHELPER-41 to be able attach this artifact prior packaging phase and remove it at prepare-package so that the actual attachment could be added to the project.

I propose that POM could have a section similar to build.finalName where you'd list the attacments that the project is going to introduce. For backwards compatibility this of course would not be required. Plugins such as jar, sources and javadoc could kick in automatically when pom contains the respective declarations (race conditions would arise between maven-bundle-plugin and jar for instance).

Issue Links

• is related to: MNG-7316 REGRESSION: MavenProject.getAttachedArtifacts() is read-only
• relates to: MNG-5868 Adding several times the same artifact via MavenProjectHelper (attachArtifact) keep adding to the List duplicate artifacts
• relates to: MNG-2596 Allow support for multiple classifier for a given artifact
• relates to: MNG-2649 Allow support for property list based artifact qualifying (enhanced classifiers)
• mentioned in: Page Loading...