You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter Cummuskey (JIRA)" <ji...@apache.org> on 2017/05/09 23:17:04 UTC
[jira] [Created] (MNG-6230) Separate plugin dependencies and
execution declarations
Peter Cummuskey created MNG-6230:
------------------------------------
Summary: Separate plugin dependencies and execution declarations
Key: MNG-6230
URL: https://issues.apache.org/jira/browse/MNG-6230
Project: Maven
Issue Type: Wish
Components: POM
Affects Versions: Issues to be reviewed for 3.x
Reporter: Peter Cummuskey
Priority: Minor
Fix For: Issues to be reviewed for 4.x
Proposed example:
{code}
<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>
{code}
Does any of that sound reasonable?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)