Hi Daniel, Thanks for getting in touch :) I'm not able to reproduce your problem, but, it kind of looks like the url that is being built for when ivy checks the file isnt building correctly.. Have you tried just running the war (java -jar hudson.war) directly to verify if this happens in that case as well? I would also suggest going to the manage hudson link, and going to system configuration, and setting up the full path to hudson to see if that fixes things.. might be a bug in the Ivy plugin.. might not be, i'm fairly junior at hudson internals.
Just to reiterate, hudson 1.226 + ivy 0.1 is working in standalone (java -jar hudson.war) for me. And it seems like it may be a tomcat setup or hudson setup error you are bumping into.
But, also, that error you are seing is just the configuration's test for the presence of the file.. if you go ahead and save the correct value, the plugin should operate just fine.
On Wed, Jun 18, 2008 at 6:38 PM, Daniel Schwager <[hidden email]> wrote:
so, the plugin actually fills in the 'build other projects' part of the configuration each time the build is run.. so, it scans the configred ivy.xml, determines what the dependencies are, and gathers up the projects that equate to that dependency. So, you need to setup the path to the ivy.xml file on each project that is ivy managed, and then run the builds for those projects.
The plugin doesn't output anything to the console after the build.
Hope that is helpful.. You might be able to see some console output where you started hudson in standalone mode... note sure though.
On Thu, Jun 19, 2008 at 8:18 AM, Daniel Schwager <[hidden email]> wrote:
thx for the quick response. Your are right – with "java -jar hudson.war"
the error does not occurs.
It must be a topic relatated to tomcat's configuration (I think,
tomcat does not know about the directory containing
But one more
-can I debug your plugin
o is it possible to see, which
projects depends on the first project ?
oWhich ivy-file does the
plugin use/search-for ?
-I created two Hudson jobs
(ivy-enabled), each with an ivy.xml in the top to the project directory (beside
of my build.xml). The first one depends
on the second one – but I can's see any action/gui-changes related to
- Requirement: Place project specific
pieces of information (org-name, module-name, Branch, CVS-module-name, ….)
only in ONE-file (e.g. build.configuration), not in ivy.xml,
build.configuration, bla.java, …. Therefore, I use the variables.
Ivy-Plugin optionally read a project dependent property file before parsing
ivy.xml (using the vars read before..)
description="1. global variable" />
-Or only a normal, plain
-Or an using a plain
propertyfile generated after calling ant with a defined target:
Target calling ant for generating propertyfile: generate_propertyfile