Sebastian Krysmanski wrote:
Hi all,
thanks for all the answers. To just summarize for me what has been said
(correct me, if I'm wrong):
* This big(gest) (and only?) disadvantage of storing the dependencies in a
VCS is the time needed to checkout a project.
This will be a serious problem if y
If a module depends on itself (module name matches), an exception is
thrown in Ivy, and resolve fails. (the message is 'a module is not
authorized to depend on itself'). This is problematic, since there are
reasons why a module might depend on itself. e.g.
* depends on older version (e.g. to gene
Maarten Coene wrote:
Stefan,
it's not clear from your answer, but did you try to omit the port when
declaring the credentials?
If that doesn't work as well, could you post the log you get on your console
when running in verbose mode?
I suspect he didn't see my suggestion - my inline
Burkhardt Stefan (CI/TMP) wrote:
Hi,
I try to upload an artefact to archiva. I always get an exception
(Unauthorized) when I have to use Basic Authentication. (The
http-client.jar is in the classpath)
Before I try to publish the artefact I set the Authentication parameters
within Ivy:
Build fil
I'm trying to install Axis2 and all its dependencies into my company IVY
repo from public maven repos. I'm now down to just a few errors, all
relating to the packaging element in the POM not matching the file
extension of the main artifact. For example:
maven-plugin
and
bundle
is actually a .
