wocommunity/WOJenkins — comment on commit e7208b7ed8aa295575230938d608a9e7752fb1e9
File:  line 0
By avendasora:

This change (along with the one in 551e1e) breaks the logic of the build script.

This script was only intended to parse the .classpath file of the project identified by the user in the ```PROJECT_NAME``` parameter of the job.

Unless you somehow change the logic to step through all the sub-directories ("Projects") in the ```Projects``` directory **in dependency order** this change will cause the build to fail if a depended-upon framework hasn't been and installed in the ```${JENKINS_HOME}/WOFramworksRepository```

For example: Application named "ABC" depends upon Framework named "XYZ" both of which are "Projects" in the ```Projects``` directory.

As the script steps through all the sub-directories in ```Projects``` if the first sub-directory is "ABC" then the script will fail because it can't find XYZ.framework in either the WebObjects frameworks or WOnder frameworks or in the dist directory of a Jenkins job named XYZ.

If you want it to parse the .classpath of _all_ the "Projects" in the ```Projects``` directory, you'll have to change the script to process the Projects in dependency order, or you'll have to change how it determines success or failure.

If it works for you right now, it's by coincidence, not design.