[ https://issues.apache.org/jira/browse/ARIES-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193156#comment-13193156 ] 

David Jencks commented on ARIES-757:
------------------------------------

I've:

made it so packageinfo files are added for "wrong" package versions (this can be turned off by the property writePackageInfos=false)

supplied a plugin prefix of "asv" for command line usage.  To use this you need to put the groupId in your settings.xml pluginGroups element like 
{code}
    <pluginGroups>
        <pluginGroup>org.apache.aries.versioning</pluginGroup>
    </pluginGroups>
{code}

supplied a separate command line mojo that can be run like this:
{code}
 mvn clean asv:check -DoldArtifact=org.apache.aries.blueprint:org.apache.aries.blueprint.api:0.2.1
{code}

made the mojo only try to execute if the oldArtifact is supplied.  So you can configure the execution for the plugin in a parent pom and only supply oldArtifact in the modules you want to compare with something.




                
> Contribute semantic versioning check tool 
> ------------------------------------------
>
>                 Key: ARIES-757
>                 URL: https://issues.apache.org/jira/browse/ARIES-757
>             Project: Aries
>          Issue Type: New Feature
>    Affects Versions: 0.4
>            Reporter: Emily Jiang
>            Assignee: Emily Jiang
>            Priority: Minor
>
> Based on the discussion on the dev mailing list, it seems that all of us like to have a semantic versioning check tool.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira