[MNG-6230] Separate plugin dependencies and execution declarations

• Type: Wish
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: Issues to be reviewed for 4.x
• Fix Version/s: Issues to be reviewed for 4.x
• Component/s: POM
• Labels: dependencies executions plugins schema
• Assignee: Unassigned
• Reporter: Peter Cummuskey
• Created: 09/May/17 23:16
• Updated: 27/Nov/20 12:17

Description

Proposed example:

<dependencies>

    <dependency>...</dependency> <!-- maybe turn <type> into subtypes of this -->

    <plugin> <!-- subtype of dependency? -->
        <id>bongo</id> <!-- defaults to short name -->
        <groupId>com.bongo.morebongo</groupId>
        <artifactId>allthebongo</artifactId>
        <version>1.1.0-BONGO</version>
    </plugin>

</dependencies>

<build>
    <executions>

        <execution>
            <id>bongo-run</id>
            <pluginId>bongo</pluginId> <!-- can also use gavc -->
            <phase>generate-sources</phase>
            <goal>bongotime</goal> <!-- just flatten the goals list -->
            <configuration>
                <nomorebongo>false</nomorebongo>
            </configuration>
        </execution>

        <execution>
            <id>maven-compile</id> <!-- ref to make sure bongo fires first -->
        </execution>

    </executions>
</build>

Does any of that sound reasonable?

Issue Links

• is related to: MNG-3397 [RFC] change the POM to use attributes