ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Marks <topher1...@gmail.com>
Subject Re: Ivy housekeeping, repository cleaning
Date Mon, 06 Sep 2010 19:06:54 GMT
Not sure what Maven repository you're using, but Artifactory provides the
ability to remove jars after a certain time of not being requested.  We keep
all of our internal builds, but we use this for third party binaries.
Hope this helps

Thanks

On Sep 6, 2010 8:18 AM, "Steve Miller" <steven@millerland.com> wrote:

Hi Gerke,
 So far I've just manually deleted things and then just run the build
again. But if your using a continuous integration tool to publish the
artifacts, I see how it would be nice to have it automated somehow. I
wrote a quick ant target to do this for one project (see below).  It
just get's the latest version, and then deletes all folders but that
version. If you had several modules, I guess you'd need to call a
parent build that called subant for this task on each module. I'm
still not sure when this would get run. I guess manually when you feel
the repository has gotten to large. Any thoughts?

<target name="clean-int" depends="load-ivy"
       description="--> cleans the integration repository for the current
module">
       <ivy:info file="${ivy.file}" />
       <ivy:info property="lastbuild" organisation="${ivy.organisation}"
module="${ivy.module}" revision="latest.integration"/>
       <echo>Deleteing all but revision ${lastbuild.revision}</echo>

       <delete includeemptydirs="true">
               <fileset
dir="${ivy.local.default.root}/${lastbuild.organisation}/${lastbuild.module}">
                       <exclude name="${lastbuild.revision}/**" />
               </fileset>
       </delete>
</target>


On Mon, Sep 6, 2010 at 8:10 AM, Gerke Ephorus <gerke.ephorus@gmail.com>
wrote:
>  Hi list readers,
...

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message