Re: WO Deployment [was:A WebObjects article on Appleinsider]
Re: WO Deployment [was:A WebObjects article on Appleinsider]
- Subject: Re: WO Deployment [was:A WebObjects article on Appleinsider]
- From: Mike Schrag <email@hidden>
- Date: Thu, 9 Jul 2009 11:43:12 -0400
do you run into this problem or am i just making that out to be
more difficult than it is?
At that point, I would say industry have solved it. how do normal
j2ee developer do when they are in a developement cycle ?
- jfv
note that I know nothing of all this, I find it interesting though.
well, there are obvious fixes for it -- but it's not particularly end-
user friendly ... you can obviously put it in your project build path
but not put it in a folder that will deploy (i.e. put it somewhere
other than in Libraries), but that means that everyone that uses wo
has to remember to do this, which sort of sucks. i'm guessing maven
probably just has an answer to this -- build dependency jars that
aren't deployment dependency jars, so they probably don't have to
worry about it?
ms
_______________________________________________
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