Nicolas - Thanks, this info is very helpful. I will investigate and be
sure to let you know if I have any feedback.
-Carl
On 08/24/2010 02:03 AM, Nicolas Lalevée wrote:
Le 24 août 2010 à 00:47, Carl Myers a écrit :
The "common and reusable" pattern is "I have a mess of files". Why does it
Le 24 août 2010 à 00:47, Carl Myers a écrit :
> The "common and reusable" pattern is "I have a mess of files". Why does it
> need to be more specific?
>
> Some examples:
>
> 1. Our custom build system consists of several xml and properties files. We
> would like to version our build system
The "common and reusable" pattern is "I have a mess of files". Why does
it need to be more specific?
Some examples:
1. Our custom build system consists of several xml and properties files.
We would like to version our build system itself so that just a small
ant script is used to pull the b
Le 19 août 2010 à 03:15, Carl Myers a écrit :
> Thanks Jason, that info is very helpful.
>
> The reason why this is appropriate for the dev list is, I think, I am asking
> "shouldn't Ivy/IvyDE do this natively?"
>
> I guess you could call this a feature request (which I would be willing to
>
Thanks Jason, that info is very helpful.
The reason why this is appropriate for the dev list is, I think, I am
asking "shouldn't Ivy/IvyDE do this natively?"
I guess you could call this a feature request (which I would be willing
to implement myself) to make Ivy better support non-jars. I do
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
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 als
