[esb-issues] [JBoss JIRA] Closed: (JBESB-387) jUDDI-registry (juddi.war) is missing deploy/undeploy ant task

[Kurt Stam (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBESB-387?page=all ]

Kurt Stam closed JBESB-387.
---------------------------

    Resolution: Done

Thanks for the patch. I added the build.xml.

> jUDDI-registry (juddi.war) is missing deploy/undeploy ant task
> --------------------------------------------------------------
>
>                 Key: JBESB-387
>                 URL: http://jira.jboss.com/jira/browse/JBESB-387
>             Project: JBoss ESB
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Registry and Repository
>            Reporter: jarkko Lietolahti
>         Assigned To: Kurt Stam
>             Fix For: 4.2 Milestone Release 2
>
>         Attachments: build.xml, deployment.properties
>
>
> As I hate copying files I found out that jUDDI-registry in trunk/product/install/jUDDI-registry is missing proper ant build.xml.  Find it attacted here.
> The build.xml relies on a new global deployment.properties located at ../../../deployment.properties from trunk/product/install/jUDDI-registry that is in the root of the project. This new file should be there that one only has to configure org.jboss.esb.appserver.home and org.jboss.esb.appserver.config only ONCE to make deployment a lot easier for new checkouts and installations. I hate nothing more than copying files to some weird location (e.g. H:/dev/etc ) when running ant first time in a directory ;)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira