Dan, Joel,
I could write a script (using ANT) that will pull down the example axis2 war from a URL specified by the user and modify it and install it into the appropriate place in the muse distribution. This could be wrapped up into a script that lives in muse/bin call update_install.{sh,bat} will pull down the appropriate WAR. Now the neat thing we could do is have a file on our side that meta-refreshes to where the axis2 war is, so that the user doesn't actually have to provide the URL, they just have to run the script. Think of this as the poor man's update site. For now we can point to the nightly WAR and that's what will get pulled down, but when Axis2 goes happy we can just update the link on the site and existing users can just rerun the update and new users will just run the update.
Thoughts?
Thanks,
Andrew
Andrew Eberbach
Autonomic Computing
(919) 254-2645
T/L: 444-2645
[EMAIL PROTECTED]
| Daniel Jemiolo/Durham/[EMAIL PROTECTED]
09/26/2006 11:50 AM
|
|
The Axis2 1.1 release has been postponed indefinitely, so we will have to
leave the Axis2 WAR out of our release build. I will update the
documentation to point to the latest Axis2 builds and add instructions for
putting it in muse-2.0.0-bin/lib.
Andrew - please leave the build as it is, I will remove the Axis2 WAR
manually before signing it.
Andrew/Joel - please do whatever is necessary to make it easy for people
to bundle-ize the Axis2 WAR.
Let's try and get this done by EOD and start the vote.
Thanks,
Dan
----- Forwarded by Daniel Jemiolo/Durham/IBM on 09/26/2006 11:43 AM -----
"Thilina Gunarathne" <[EMAIL PROTECTED]> wrote on 09/26/2006 11:25:43 AM:
> Hi all,
> I figured out that we still have some blockers to be fixed [1]..
> Even though the earlier schedule was to do the code freeze today, I
> would like to postpone it a bit.. Revised plan is to do the code
> freeze and the cutting of RC when this [1] list goes down to zero.
> I'm sure all the devs will agree with me..
>
> The code freeze will effect only theAxis2 1.1 releasing modules. Namely
> * ADB
> * Addressing
> * jibx
> * Saaj
> * spring
> * Webapp
> * adb-codegen
> * codegen
> * java2wsdl
> * kernel
> * samples
> * soap monitor
> * tool
> *xmlbeans
>
> Rampart, security, secpolicy modules will be released later.. Please
> take utmost care *not to break* the build at this critical point of
> time...
>
> We still have the neethi and woden releases to be finalised... I would
> like to see them finalise soon.
>
> In the mean time please test the nightly builds to their extremes+ try
> to figure out ways to improve our documents.
>
> Lets do our best to make the Axis2 1.1 release Rock Solid...
>
> Thanks,
> Thilina
>
> [1] http://issues.apache.org/jira/secure/IssueNavigator.jspa?
> mode=hide&requestId=12311157
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
