juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Viens" <st...@viens.net>
Subject [juddi-Developers] jUDDI's build.xml includes a new "deploy" target.
Date Fri, 19 Sep 2003 15:22:25 GMT
I didn't mention the fact that I added a 'deploy' target to the build
last weekend.  This target requires an instance of Tomcat to be running
on localhost.  It basically performs these steps:

 1. Removes log files from the build directory
    from the last time 'deploy' was run (more 
    on this in a minute).

 2. Tests to make sure that a Tomcat instance
    is running (creates verify.log in the build 
    directory).

 3. Stops the jUDDI webapp if one is currently
    deployed and running (creates stop.log in 
    the build directory). 

 4. Deletes the 'juddi' directory from Tomcat's
    webapp directory.

 5. Copies the newly created 'juddi' webapp 
    directory (built in the 'war' target) to
    the Tomcat webapps directory.

 6. Starts the jUDDI webapp (creates start.log
    in the build directory.

This target uses the values specified in the 
build.properties file to perform it's duties.
 
  tomcat.dir            Tomcat's home directory
  tomcat.url            The URL to Tomcat's home page
  tomcat.mngr.username  Username to Tomcat's Manager webapp
  tomcat.mngr.password  Password to Tomcat's Manager webapp

If you'd like to use this deploy target be sure to set these values to
the one's your Tomcat instance Uses.

Steve

-----Original Message-----
From: juddi-developers-admin@lists.sourceforge.net
[mailto:juddi-developers-admin@lists.sourceforge.net] On Behalf Of Andy
Cutright
Sent: Friday, September 19, 2003 4:37 PM
To: juddi-developers@lists.sourceforge.net
Subject: RE: [juddi-Developers] doing some work on uddi4j test suite


minor correction. i've discovered a couple of bugs in my suite
introduced by my changes this morning. i've hacked those out
temporarily. i've just committed the changes, so you may want to update
the uddi4j test subdir to get the latest. 

cheers,
andy 

> -----Original Message-----
> From: Andy Cutright
> Sent: Friday, September 19, 2003 11:12 AM
> To: juddi-developers@lists.sourceforge.net
> Subject: [juddi-Developers] doing some work on uddi4j test suite
> 
> 
> hi all,
> 
> i've modified build.xml to pick up some additional jars for the uddi4j

> test suite. i've also started using the client save_publisher 
> interface to dynamically configure the registry, reducing 
> pre-configuration dependencies. it currently has one 'publisher' 
> dependency now, 'juddi'.
> i can change this if y'all like to some other name. we ship with a
> default 'juddi' publisher alleviating end-user bootstrap pain :) 
> 
> all the tests but one are known to accurately test uddi4j
> functionality.
> the one problem test just doesn't do anything yet. it should be
> functional shortly. running the test suite simply requires a running
> instance at port 8080 with the standard /juddi/... contexts available.
> 
> i'd like to make sure we start running all the test suites prior to 
> committing changes. thoughts?
> 
> cheers,
> andy
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf 
> _______________________________________________
> juddi-developers mailing list juddi-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/juddi-developers
> 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
juddi-developers mailing list
juddi-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/juddi-developers






Mime
View raw message