ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <xavier.ha...@gmail.com>
Subject Re: My first build of Ivy
Date Sat, 12 May 2007 00:21:21 GMT
n 5/11/07, Jan.Materne@rzf.fin-nrw.de <Jan.Materne@rzf.fin-nrw.de> wrote:
>
> I just did my first build of Ivy.


Welcome in Ivy world :-)

So here my first thoughts on the
> output:
>
> Revision: 537162
> Proxy not configured
> Build command: ant
>
> init:             ...
> prepare:          ...
> compile-core:   ...
> compile-ant:    ...
> init-ivy:
> [ivy:configure] Loading ... ivy.properties
> [ivy:configure] :: Ivy non official version ::
> http://incubator.apache.org/ivy/ ::
> [ivy:configure] impossible to define new type: class not found:
> org.apache.ivy.plugins.resolver.VsftpResolver in [] nor Ivy classloader
> [ivy:configure] impossible to define new type: class not found:
> ...SshResolver in [] ...
> [ivy:configure] impossible to define new type: class not found:
> ....VfsResolver in [] ...
> [ivy:configure] impossible to define new type: class not found:
> ....SFTPResolver in [] ...
> [ivy:configure] :: loading settings :: file = ... ivysettings.xml
> [ivy:configure] DEPRECATED: 'ivyconf' element is deprecated, use
> 'ivysettings' instead (... ivysettings.xml )
> [ivy:configure] DEPRECATED: 'conf' is deprecated, use 'settings' instead
> (... ivysettings.xml)
>
> resolve:
> [ivy:retrieve] :: resolving dependencies :: [ apache | ivy |
> working@nb011696 ]
> [ivy:retrieve]  confs: [default, test]
> [ivy:retrieve] You probably access the destination server through a
> proxy server that is not well configured.
> [ivy:retrieve] You probably access the destination server through a
> proxy server that is not well configured.
> ...
>
> [ivy:retrieve] :: resolution report ::
>
> ---------------------------------------------------------------------
>         |                  |            modules            ||
> artifacts   |
>         |       conf       | number| search|dwnlded|evicted||
> number|dwnlded|
>
> ---------------------------------------------------------------------
>         |      default     |   6   |   0   |   0   |   0   ||   0   |
> 0   |
>         |       test       |   1   |   0   |   0   |   0   ||   0   |
> 0   |
>
> ---------------------------------------------------------------------
>
> BUILD FAILED
> C:\ant\svn-repository\ivy\core\build.xml:150: impossible to resolve
> dependencies: java.lang.NullPointerException
>
>
>
> 1. target "init-ivy":
>    - why do you use deprecated elements in your own configuration?
> (ivyconf-->ivysettings, conf-->settings)


Maarten has very recentely reviewed the build to use a self build ivy core
for resolving Ivy own dependencies, and it seems he forgot to update the
settings file.
Maarten, do you have time to update the settings file, or should I do so.

2. target "resolve":
>    - I got 22 messages "You probably access ..." - so many? One would be
> enough ...


We wanna make sure you don't miss it, sometimes users complain because there
are only 18 messages :-)
Indeed, we could improve that, you can open a JIRA issue.

   - How to set proxy?
> 3. build result "build.xml:150: impossible to resolve dependencies:
> java.lang.NullPointerException"
>    build.xml:150:   <ivy:retrieve conf="default,test" />
>    - You should catch a NPE and provide a useful message.


Of course, this is a bad bug, I really don't like NPE. Could you please open
a JIRA issue for this too?

I cant provide a patch or deeper ideas because of not knowing the
> sources yet ;-)


I'm pretty sure this won't last very long :-) Anyway, thanks for your
feedback!

Xavier

Jan
>



-- 
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/

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