[ http://issues.apache.org/jira/browse/GUMP-39?page=all ]
Leo Simons closed GUMP-39:
--------------------------
Resolution: Won't Fix
Fix Version: Gump3-alpha-4
(was: Gump3-alpha-5)
Eyebrowse references are broken (find thread @
http://www.mail-archive.com/general@gump.apache.org/msg01030.html). Basically
this idea is a little dated; gump isn't nearly as ant-focussed anymore as it
used to be, nor does the idea of ant depending on gump again sound like such a
good idea in retrospect. Rather than add these kinds of checks, we should aim
to make gump predictable.
> gump-check ant task
> -------------------
>
> Key: GUMP-39
> URL: http://issues.apache.org/jira/browse/GUMP-39
> Project: Gump
> Type: New Feature
> Components: Python-based Gump
> Versions: Gump2
> Reporter: Leo Simons
> Fix For: Gump3-alpha-4
>
> 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/[EMAIL
> PROTECTED]&by=thread&from=682505
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
