ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Trump <>
Subject Re: Publishing non-jar artifacts
Date Sun, 15 Aug 2010 21:28:36 GMT
Hi Carl,

Not to nit-pick, but this is probably better a question for the users
mailing list than the dev mailing list.

I haven't tried this myself, but here's an idea:

1) You can configure IvyDE to retrieve your dependencies into the workspace
on resolve.   It might be useful to create a special Ivy configuration like
'ide' for these extra dependencies so that they go into 'lib/ide/**'.
2) You could then add an Ant Builder to your project, which executes a
specified ant target whenever the 'lib/ide' folder changes.  The Ant Builder
can also be configured to refresh the target directories in your eclipse
workspace where the resources have been unpacked.

here's some aging-but-still-relevant eclipse docs on setting up Ant Builder:


On Fri, Aug 13, 2010 at 5:23 PM, Carl Myers <> wrote:

> Hey all,
> We use ivy for dependency management but now we need to depend on things
> that are not jars (as an example, a java keystore, a text file containing a
> license, a .sql file describing a db schema).
> Currently we have a custom build system in ant which leverages ivy ant
> tasks, but we also have developers using IvyDE in Eclipse.  I want to be
> able to publish, and consume, non-jar dependencies in both places.  This
> means Ivy would need to be able to "unbundle" the contents of a
> jar/zip/whatever to a specific location on resolve.
> I know that ant hooks exist to do things like this, but will they work in
> IvyDE?  Is that the way to go?  If this does require dev work, how would you
> expect it to be done to be most likely to be accepted as a patch?
> Thanks!
> --
> Carl Myers
> Palantir Technologies | Internal Tools Software Engineer
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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