aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (Commented) (JIRA)" <>
Subject [jira] [Commented] (ARIES-757) Contribute semantic versioning check tool
Date Wed, 25 Jan 2012 18:04:41 GMT


David Jencks commented on ARIES-757:


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 

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

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:
>             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:!default.jspa
For more information on JIRA, see:


View raw message