On 16/03/2012, at 2:26 AM, David Avendasora wrote:

> You seem to be working really hard to find a complex solution to a simple 
> problem.
> 
> 1) Why not just include _all_ the depended-upon frameworks in your app's 
> .classpath? In other words, The App's class path has all of the WOFramework 
> entries for the frameworks it depends upon, even if they are 2- or 3- or 
> n-times removed from the App itself? They are just lines of text in 1 file. 
> Other than duplication, which you are doing anyway by creating a secondary 
> classpath file what is it you are trying to avoid? By including them all in 
> the .classpath, both WOJenkins and WOLips would know what to do when you 
> build.
> 
> 2) If you are using Jenkins, why do you still use WOLips to build your App? 
> WOLips does not _ever_ build your dependencies for you. You will always have 
> to build them one at a time,

Not if you use maven.

> in dependency order and you run the risk of forgetting a dependency and 
> having WOLips build with an old version.

Ants are funny little critters aren't they; easily confused. Put a leaf in 
their path and they go into a frenzy figuring out where they should go next ;-)

> If you've got Jenkins working, by hook or by crook, then _stop_ using WOLips 
> to trigger Ant builds. It's like still keeping a MySQL version of your 
> database synchronized with your production FrontBase database.

I would have thought the driver for having builds from your dev environment 
mirror that of your UAT env is so that you can make a change and try it out 
immediately. What you are describing with your use of jenkins is called a 
work-a-round . It might be a useful work-a-round but it's a bandaid. Bandaids 
need to come off at some point ;-).

Lachlan Deck
[email protected]


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to