Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
Gump2-2.4
-
None
Description
You want the ability to verify a project state is consistent with what gump expects it to be after a build, but only gump can verify that.
Maybe we could have an ant task that talks to the gump repository to keep (nay, improve on) that functionality.
<project default="test">
<target name="verify-gump" depends="build">
<gump-check project="cocoon"/>
</target>
<target name="test" depends="build,verify-gump">
</target>
</project>
the gump-check task would get a list of requirements from the gump server (ie, what jars should exist, what directories, licenses, ...)
and compare that info to the filesystem. It would warn the user of any errors.
Mailing list thread @ http://nagoya.apache.org/eyebrowse/BrowseList?listName=general@gump.apache.org&by=thread&from=682505