There was a ____MAJOR____ refactoring between Maven 1.x and Maven 2.x If a project is built using Maven 1.x you have no hope to build it with Maven 2.x unless you convert the build process yourself (or unless somebody else has converted it for you)
Maven 1.x development pretty much ceased at least 4-5 years ago I think you are out of luck unless you can use a Maven Repository Manager (e.g. Nexus) to proxy the requests for you -Stephen P.S. Stephen has never done any development work with Maven 1.x. Stephen thinks Maven 1.x is a stinking pile of excrement... which makes an excellent fertiliser from which the roses that are Maven 2.x and Maven 3.x have grown ;-) On 30 August 2010 09:56, Stadelmann Josef < [email protected]> wrote: > We are using a feature with Axis2-1.2 which is called scope="soapsession" > That is to say, we have a state-full web service realized and interfaced > with Microsoft WCF 3.5 Clients. > State-full web services with long lasting user sessions is a thing which > makes every bode I've meet so far cry. > > Hence I never got real help on that issues when I need it, hence I have > built axis2-1.2 in the past from scratch myself just to be able to single > step through the engine code to master this features; sorry but we use long > lasting session because our legacy server code some 120'000 line of OpenVMS > Pascal code is as it is. And yes: all is running fine. But since some few > weeks my destroy() method is no longer called when the user session breaks. > > Axis2-1.2 needs at a max maven-1.1 for building. > > I do it routinely at home not sitting behind a fire wall proxy demanding > username and password and domain name to reach out for artifacts; but here > in the AXA company I can't reach out for artifacts unless this NTLM > authentication is properly supported. > > > Also: WHO OF YOU MAVEN GUYS CAN TELL ME how to best approach? > > 1. Does Axis2-1.5 and greater support scope="soapsession" correctly; I've > read somewhere that this is not any longer the case; Unfortunately I lost my > pointer to this information, hence I can't ask the author. And again; this > feature seems to be so exotic but is there, that nobody helps me. > > > 2. WHO OF YOU MAVEN DEVELOPERS can tell me that maven-2.2.1 and above used > to build Axis2-1.5 and above can reach through proxies using username > password and domain name and is able to deal with NTLM authentication > correctly? > > If this does not run on maven-1.1 why should it run on maven-2 and maven-3? > > > I will certainly go any build maven-2.2.1 and port it to OpenVMS and hope > that it can reach through proxy protected networks to get artifacts > downloaded. > > Josef > > > > > > -----Ursprüngliche Nachricht----- > Von: Kathryn Huxtable [mailto:[email protected]] > Gesendet: Dienstag, 24. August 2010 19:14 > An: Maven Users List > Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS > > Egads, is anyone still using Maven 1? If so, why? -K > > On Aug 24, 2010, at 11:40 AM, Wayne Fay wrote: > > >> Wasting time? > >> > >> How do I force BASIC authentication using maven-1.1 either with > >> maven-1.1 or maybe I can do it outside maven-1.1-code through a > > > > Let me be more plain... you are WASTING YOUR TIME trying to fix > > Maven1. Perhaps you understand me better now? > > > > Find the simplest thing that could possibly work -- just download the > > artifacts into the proper spot in your local filesystem -- and get on > > with the more important things, which is apparently debugging your > > problems Axis. > > > > Wayne > > > > --------------------------------------------------------------------- > > 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] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
