[MPH-192] need <skip> option for evaluate goal

Open
#164 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

Start at the Maven Help Plugin implementation for the evaluate goal and inspect how its parameters are declared and tested. Compare skip options in the referenced Maven plugins, then verify that a POM-configured skip prevents evaluation while existing evaluation and file-output behavior remains unchanged.

Written by the indexing model from the issue text.

Description

enhancement priority:major

Garret Wilson opened MPH-192 and commented

It is typical and even expected for Maven plugins to have a <skip> option, so that we can provide (via properties, profiles, etc.) a way to skip the plugin execution. See for example the Antrun Plugin <skip> option and the Maven Assembly Plugin <skipAssembly> option. (I could provide a long list of similar plugins.)

Please provide a Maven configuration option to skip execution for the evaluate goal.

This is particularly important because the Maven Help Plugin provides the only means to generate output to a file which is recognized across many development environments. (For example, Antrun <echo> can generate a file, but it is not supported by Eclipse.)

It is important to be able to able to configure in the POM to evaluate an expression and output to a file only under certain conditions. Currently the lack of this functionality is blocking my use of the Maven Help Plugin evaluate goal and I am forced to look for other options, or limp along with Antrun not working in Eclipse.

Thank you.

Affects: 3.3.0

Dominant language
Java
Stars
29
Forks
42
Avg merge
23h 15m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/maven-help-plugin

All issues in apache/maven-help-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.