• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Eclipse builds - force custom framework selections to be packaged
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Eclipse builds - force custom framework selections to be packaged


  • Subject: Re: Eclipse builds - force custom framework selections to be packaged
  • From: Lachlan Deck <email@hidden>
  • Date: Fri, 16 Mar 2012 09:30:01 +1100

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@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: Eclipse builds - force custom framework selections to be packaged (From: Daniel Roy <email@hidden>)
 >Re: Eclipse builds - force custom framework selections to be packaged (From: Pascal Robert <email@hidden>)
 >Re: Eclipse builds - force custom framework selections to be packaged (From: Daniel Roy <email@hidden>)
 >Re: Eclipse builds - force custom framework selections to be packaged (From: David Avendasora <email@hidden>)

  • Prev by Date: Re: Community Roadmap for 2012
  • Next by Date: Re: ERXRestFetchSpecification defaultSortOrderings ordered by id (PK)
  • Previous by thread: Re: Eclipse builds - force custom framework selections to be packaged
  • Next by thread: Couldn't locate action class
  • Index(es):
    • Date
    • Thread