maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (JIRA)" <j...@codehaus.org>
Subject [jira] (MPLUGIN-287) refactoring: consistent package name for extractor and javadoc
Date Thu, 01 Jan 2015 17:44:10 GMT
Herve Boutemy created MPLUGIN-287:
-------------------------------------

             Summary: refactoring: consistent package name for extractor and javadoc
                 Key: MPLUGIN-287
                 URL: https://jira.codehaus.org/browse/MPLUGIN-287
             Project: Maven Plugin Tools
          Issue Type: Task
          Components: maven-plugin-tools-annotations, maven-plugin-tools-java
    Affects Versions: 3.3
            Reporter: Herve Boutemy


after creating groups for aggregate javadoc in [r1648856|http://svn.apache.org/r1648856],
some inconsistencies become obvious that would help people understand code:
- for {{maven-plugin-tools-java}}, package {{org.apache.maven.tools.plugin.extractor.java}}
should be {{org.apache.maven.tools.plugin.extractor.javadoc}}
- for {{maven-plugin-tools-annotations}}, package {{org.apache.maven.tools.plugin.annotations}}
should be {{org.apache.maven.tools.plugin.extractor.annotations}}
Changing these internal java package won't change anything for end-users, it will only improve
Maven developers code understanding

notice that {{maven-plugin-tools-java}}, ie the artifact id for javadoc extractor, should
be renamed to {{{{maven-plugin-tools-javadoc}}, but this artifact id is already used for javadoc
doclets: this would require change for end-users using it, then we can't refactor this


while at it, extractors for Ant and Beanshell (and the model) can go to maven-script directory:
this will remove clutter from first-level directory (for features less used)



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message