[kepler-dev] Add depency in build.xml?

[David Buttler]

Hi Jing,
I looked at the CVS diff of the build.xml file you just updated and I 
have a question:
it looks like you have modified the general compile target so that it 
requires your package, but in the build file you also added a CVS target 
that would check it out from the repository under your username, 
requesting the password from the builder at compile time.
Does this mean that I need your password in order to compile kepler now?
There has to be a better way to manage this; at the very least ask for 
username and password, rather than hard coding your username into the 
build file.  Does anyone else have other suggestions?

Dave

Jing Tao wrote:

>Hi, everyone:
>
>My kepler code will need the some jar files (about 6) in lib when it 
>communicates to ecogrid service. Those jar files come from ecogrid client 
>library in seek/ecogrid project.
>
>Now I have a question: do I need add those jar file direclty to kepler cvs 
>or add adependency on seek/ecogrid project in build.xml(add a target in 
>kepler build.xml and this target will create those jar files then copy 
>them to kepler/lib/jar)? 
>
>The first one is easiest one but duplicate code. The second one doesn't 
>duplicate the codes, but make user to run kepler should checkout seek 
>module first(it is pain too).
>
>Any idea or suggestions?
>
>Thanks!
>
>Jing
>
>
>
>  
>