On Tue, May 17, 2011 at 13:53, Martin Gainty <[email protected]> wrote: > main concern are the majority of sample projects and client folders still > use ant.
Since the samples are not released as Maven artifacts, they don't need to be mavenized. They could continue using Ant. > we should think about refactoring wsdl2java to creating a pom.xml along with > build.xml I don't like the word "refactoring" in the context of a maintenance release... > to solve persistent "wrong version" errors that seem to plague axis even to > this day. > > yes we *should* continue to support Axis1 as the installed base of RPC > services have a larger installed base than current implementations of Axis2. As usual, in the absence of hard statistical data, one can make any claim one wants to make ;-) > Martin > ______________________________________________ > Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht > dient lediglich dem Austausch von Informationen und entfaltet keine > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le > destinataire prévu, nous te demandons avec bonté que pour satisfaire > informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie > de ceci est interdite. Ce message sert à l'information seulement et n'aura > pas n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > aucune responsabilité pour le contenu fourni. > > > > >> Date: Tue, 17 May 2011 11:04:34 +0200 >> From: [email protected] >> To: [email protected] >> Subject: Re: Is Axis (not Axis2) still being developed? >> >> Hi Andreas, >> >> first of all, thank you for your answer. >> >> Am 16.05.2011 21:40, schrieb Andreas Veithen: >> >> I'm wondering whether Axis (not Axis2) is still being developed. >> > >> > No. Since a picture says more than a thousand words: >> > >> > >> > http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fwebservices%2Faxis%2Ftrunk%2Fjava >> >> Thats no surprise, I was just wondering because of the lack of some >> official statement on e.g. http://ws.apache.org/axis/ >> >> > There are no official plans to do a bug fix release of Axis. We even >> > had discussions to "attic" Axis 1 completely. >> > >> > That being said, I'm facing a similar issue than you. At work, we have >> > a couple of applications that still use Axis 1 and they are all >> > affected by the class loader leak described in AXIS-2674. I think >> > nobody would object to doing a maintenance release, as long as there a >> > volunteers to handle it. The problem is that it is non trivial to do >> > that: >> > >> > 1. The build and release system is antiquated and probably no longer >> > conforms to the ASF guidelines. I guess that one would have to migrate >> > it to Maven 2, which is probably not that difficult (and almost >> > certainly easier than upgrading some obscure Ant scripts) but would >> > require some reshuffling of the directory structure. >> >> So I understand it correctly: To do a maintenance release of an ASF >> project it needs to be updated to the current version of the ASF >> guidelines. Thus, it's not sufficient to simply correct the specific >> parts in the code and run the existing Ant build script to create the >> binaries. >> >> > 3. I think that the 1.4 release was not properly tagged in SVN. One >> > would first have to locate the branch and revision from which the >> > release was created in order to have a well defined base line for a >> > maintenance release. >> >> That sure is a problem. Also see another comment regarding subversion >> below. >> >> > Probably the most realistic option is to create a branch from the 1.4 >> > release (after locating the correct revision), mavenize that branch >> > and abandon the current trunk (after recovering some selected >> > changes), i.e. all "development" would happen on that branch, knowing >> > that there will never be an Axis 1.5 release from the trunk. >> >> Thats IMHO to much work for a) a some small number of bugs and b) in the >> meanwhile outdated project. >> >> > Are you willing to help with this? >> >> For the time being I am not able to make a statement to this. >> >> >> Sourcecode access as proposed in http://axis.apache.org/axis/cvs.html >> >> does >> >> not work anymore. I cannot upgrade to Axis2, because I am restricted to >> >> JDK >> >> 1.4. >> > >> > The source code was moved when we graduated to an Apache top level >> > project, and is now here: >> > >> > http://svn.apache.org/repos/asf/axis/axis1/java/trunk/ >> >> And if I see this correctly all SVN history was dropped which in fact >> makes it harder to retrieve version 1.4. >> >> Regards, >> Simon >> >> -- >> Simon Frettlöh >> Consultant >> >> EXXETA AG >> Albert-Nestler-Str. 11 >> D-76131 Karlsruhe >> >> fax +49(0) 721/6105 1599 >> mobil +49(0) 162/260 36 99 >> >> mail [email protected] >> web www.EXXETA.de >> >> Sitz der Gesellschaft: >> >> EXXETA AG >> Albert-Nestler-Str. 9, D-76131 Karlsruhe >> >> Vorstände: >> Achim Kirchgässner, Andreas Ritter >> >> Aufsichtsratvorsitzender: >> Klaus Wybranietz >> USt-IdNr. DE813026499 >> Eingetragen beim Amtsgericht Mannheim HRB 702566 >> >> Dieses E-Mail enthaelt vertrauliche oder rechtlich geschuetzte >> Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, >> informieren Sie bitte sofort den Absender und loeschen Sie diese E-Mail. >> Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der >> enthaltenen Informationen ist nicht gestattet. >> >> The information contained in this message is confidential or protected >> by law. If you are not the intended recipient, please contact the sender >> and delete this message. Any unauthorised copying of this message or >> unauthorised distribution of the information contained herein is >> prohibited. >> >> --------------------------------------------------------------------- >> 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]
