Maven 1

• Type: Wish
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: None
• Fix Version/s: 1.0-rc1
• Component/s: None
• Labels:

  None

I'm suggesting to create a component in jira for every plugin maven is bundled. This will make it easier to find releated issues and also to get a bether overview of the issues.

This is the current list of 'jira components' thats plugin related:
maven-reactor-plugin
plugin-cactus
plugin-changes
plugin-clean
plugin-clover
plugin-dist
plugin-java
plugin-latex
plugin-other
plugin-pmd
plugin-pom
plugin-test
plugin-war
plugin-xdoc

It might be a bit of a overkill to include all plugins but I think there are a bunch that should be a jira component.

This is the list of all plugins thats not a component:
ant
antlr
appserver
artifact
ashkelon
aspectj
castor
changelog
checkstyle
codeswitcher
console
deploy
developer-activity
docbook
ear
eclipse
ejb
examples
faq
file-activity
genapp
gump
hibernate
html2xdoc
idea
j2ee
jalopy
jar
javadoc
jboss
jbuilder
jdee
jdepend
jdeveloper
jdiff
jellydoc
jnlp
junit-report
junitdoclet
jxr
latka
license
linkcheck
multiproject
native
pdf
perforce
plexus
plugin
release
repository
runner
sea
shell
simian
site
statcvs
struts
summit
tasklist
tjdo
torque
touchstone
touchstone-partner
uberjar
vdoclet
was40
webserver
wizard
word2html

Also, the 'maven-reactor-plugin' component should be renamed to 'plugin-reactor'

• Assignee:

  Unassigned

  Reporter:

  Trygve Laugstol

• Created:

  15/Aug/03 10:25 AM

  Updated:

  08/Mar/06 10:47 PM

  Resolved:

  17/Aug/03 8:14 PM