ws-savan-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <>
Subject Re: Plan for updating axis(yes it is axis 1 not 2)
Date Fri, 08 Oct 2010 09:29:33 GMT
If I remember correctly, the conclusion of the discussion about the
fate of Axis 1.x was that the Attic [1] focuses on top level projects
that no longer have a community. For subprojects that are no longer
maintained, it's up to the respective TLP to decide what to do with
them. With respect to Axis 1.x, I think that the implicit decision was
to keep the status quo (i.e. to simply leave the code in Subversion
[2] and to have at least download links reachable from the Axis TLP
home page) until somebody volunteers to do some maintenance work on
the code.

If Dilly wants to contribute to this, then I would propose the
following procedure:
* Create and/or update the relevant JIRA issues [1] and attach patches
with the changes.
* Periodically send to a list of JIRA issues
with patches to be reviewed and applied by Tom (or somebody else).


[2] (Note that the
tags are still under

On Thu, Oct 7, 2010 at 23:38, Tom Jordahl <> wrote:
> Hi dilly,
> If you are interested in taking on a caretaker role for Axis 1.x, I can give you a hand.
> If you have changes (and tests!) that you want to check in to the trunk, I could do that
for you, then we can get you committer status so you could then do that on your own.
> Note that the tentative plan is to move Axis to the Attic, which means it is a 'functional
but retired' codebase.  But you could stop this if you have the time and energy to put in
to moving Axis to a (final?) 1.4.1 or 1.5 release.
> Anyone else (Glen?) have any thoughts on how we can leverage dilly's energy here?
> Tom Jordahl
> Axis 1.x oldtimer
> -----Original Message-----
> From: dilly []
> Sent: Thursday, October 07, 2010 2:14 AM
> To:
> Subject: Plan for updating axis(yes it is axis 1 not 2)
>  Hi, I am a newcomer to this mailing list.
> I have used axis 1 in servial projects as an experienced user, it is a
> good choice for the web server with jdk 1.4 or lower.
> But it is a pity for long-time-no-updating situation. There are many
> outdated links which are not valid and misleading. Also, some tiny
> mistakes lie in the document. Besides, serival bugs live in the JIRA for
> a long time.
> So as a man who wants to do something for axis 1, I have a plan for
> updating axis 1.
> 1.Update the document and the axis 1 site web pages to correct the
> outdated links which are not valid anymore, e.g., the mailing list
> address(lol:).
> 2.Update the document with axis 1 package, remove tiny mistakes.
> 3.If possible, resolve some of the old bugs.
> The Ultimate purpose is to announce axis 1.5. It is beyond my
> capabilities, at least now. But I can make a small step towards it,
> let's say 1.4.1?
> So there are the questions: Who will take my ouputs to the svn
> repository? And there is still an active axis 1 sponsor ready for
> checking my work?
> Any response will be grateful, thank you in advance.
> dilly(Ma Yu)
> Shanghai, China
> 2010-10-07
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message