Maven 1.x Plugin Plugin

Prevent using the plugin plugin goals for non plugin projects

Details

  • Type: Improvement Improvement
  • Status: Reopened Reopened
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Running plugin:install on a non-plugin project generates files in the plugin directory. There should be a check (for example veriyfing that plugin.jelly exists) and it should display an error for non-plugin projects.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Emmanuel Venisse added a comment -

Done. Check if project.xml and plugin.jelly exist in basedir.

Show
Emmanuel Venisse added a comment - Done. Check if project.xml and plugin.jelly exist in basedir.
Hide
Permalink
dion gillard added a comment -

Why do plugins need a plugin.jelly file?

Couldn't they simply be adding jars to a classpath?

Show
dion gillard added a comment - Why do plugins need a plugin.jelly file? Couldn't they simply be adding jars to a classpath?
Hide
Permalink
Emmanuel Venisse added a comment -

How to know if a project is a plugin?

Show
Emmanuel Venisse added a comment - How to know if a project is a plugin?

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.