You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Stadelmann Josef <jo...@axa-winterthur.ch> on 2010/08/24 15:31:37 UTC
maven-1.1 build-bootstrap fails with OpenVMS
I have successfully built maven-1.1 from .\maven\maven-1\trunks\core on
my Vista PC / Java 1.5 from DOS and from NetBeans 5.5.1
Using maven-1.1 I have successfully built axis2-1.2; and thats why I
need maven also on a OpenVMS Integrity Server from HP;
There - Axis2-1.2 - is up and running there; but I need to compile/debug
axis2-1.2 to figure/detect out undocumented behaviour.
i.e. - why my destroy() method is no longer called in
scope="soapsession"
So I like to complement our development environment on OpenVMS with
maven-1.1 first and then subseqeuntl upgrade tomaven 2 and
Maven 3 when done with maven 1.1
However
IA64> ant -f build-bootstrap.xml
Fails on OpenVMS but runs on the Vista PC
IA64>ant "-f" "build-bootstrap.xml"
Buildfile: build-bootstrap.xml
check-maven-home:
check-maven-home-local-default:
check-maven-home-local:
check-maven-repo-local:
check-properties:
check-env:
[echo] maven.home = /dkb3/apache-maven-1.1
env:
[echo] maven.home = /dkb3/apache-maven-1.1
[echo] maven.home.local = /dkb3/stadelma/.maven
[echo] maven.repo.local = /dkb3/stadelma/.maven/repository
[echo]
[echo]
[echo] +----------------------------------------------------------
[echo]
[echo] | WARNING WARNING WARNING WARNING WARNING WARNING WARNING
[echo]
[echo] |
[echo]
. . . .
[echo] |
[echo]
[echo] | WARNING WARNING WARNING WARNING WARNING WARNING WARNING
[echo]
[echo] +----------------------------------------------------------
clean-maven-home:
[delete] Deleting directory /dkb3/apache-maven-1.1/bin
[mkdir] Created dir: /dkb3/apache-maven-1.1/bin
[delete] Deleting directory /dkb3/apache-maven-1.1/lib
[mkdir] Created dir: /dkb3/apache-maven-1.1/lib
[delete] Deleting directory /dkb3/apache-maven-1.1/plugins
[mkdir] Created dir: /dkb3/apache-maven-1.1/plugins
maven-phase-1:
[delete] Deleting directory
/dkb3/sw-projekte/asf/maven/maven-1/trunks/core/bootstrap
[mkdir] Created dir:
/dkb3/sw-projekte/asf/maven/maven-1/trunks/core/bootstrap/bootstrap-clas
ses
[javac] Compiling 6 source files to
/dkb3/sw-projekte/asf/maven/maven-1/trunks/core/bootstrap/bootstrap-clas
ses
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[echo]
[echo]
[echo] |
[echo]
[echo] | LOADING BOOTSTRAP TASKDEF...
[echo]
[echo] |
[echo]
[echo]
[echo] |
[echo]
[echo] | RUNNING BOOTSTRAP TASK...
[echo]
[echo] |
[mkdir] Created dir:
/dkb3/sw-projekte/asf/maven/maven-1/trunks/core/bootstrap/bin
[bootstrap] Using the following for your maven.repo.local:
/dkb3/stadelma/.maven/repository
[bootstrap] Using the following for your local repository:
/dkb3/stadelma/.maven/repository
[bootstrap] Using the following for your remote repositories:
[http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.m
aven.org/maven/]
[bootstrap] Downloading
http://people.apache.org/repo/m1-snapshot-repository/maven/jars/dom4j-1.
7-20060614.jar
[bootstrap] Error retrieving artifact from
[http://people.apache.org/repo/m1-snapshot-repository/maven/jars/dom4j-1
.7-20060614.jar]:
java.io.IOException: Not authorized by proxy.
[bootstrap] Downloading
http://repo1.maven.org/maven/maven/jars/dom4j-1.7-20060614.jar
[bootstrap] Error retrieving artifact from
[http://repo1.maven.org/maven/maven/jars/dom4j-1.7-20060614.jar]:
java.io.IOException: No
t authorized by proxy.
BUILD FAILED
/dkb3/sw-projekte/asf/maven/maven-1/trunks/core/build-bootstrap.xml:180:
Failed to download dependency
Total time: 11 seconds
IA64>
IA64>ty sys$login:build.properties
# ----- Proxy setup -----
user.home=/dkb3/stadelma
#
# ----- Default Base Path for Dependent Packages -----
# Replace this path with the directory path where
# dependencies binaries should be downloaded.
#base.path=C:\\Users\\C770817\\.maven\\base.path
base.path=/dkb3/stadelma/.maven/base.path
#
#--- maven specific
#
maven.proxy.host=bcproxyserver.ch.winterthur.com
maven.proxy.port=8080
maven.proxy.username=C770817
maven.proxy.password=Sep10orbx
maven.proxy.ntlm.host=C007368
maven.proxy.ntlm.domain=CH.WINTERTHUR.COM
maven.proxy.use=on
maven.repo.local=${user.home}/.maven/repository
maven.home=/dkb3/apache-maven-1.1
env.MAVEN_HOME=${maven.home}
IA64>
Note: our proxy server as identified accepts both NTLM and then BASIC
authentication
I have successfully pass this infomation and checked using some logging
via the build.properties file as shown.
The thing is that all items are accepted except
maven.proxy.ntlm.domain=CH.WINTERTHUR.COM
When I look at Ethereal, a network protocol analyzer I observer the
following:
ON VISTA
The build-bootstrap uses NTLM authentication because NTLM is presented
first by the proxy-server.
It does not use basic authntication for downloading artefacts as shown.
ON INTEG1 (OVMS)
The build-bootstrap uses NTLM authentication because NTLM is presented
first by the proxy-server.
It does not use basic authntication for downloading artefacts as shown.
**** HOW CAN I FORCE THAT BASIC ATHENTICATION IS USED but NEVER NTLM
**** This would solve my problem
OR
**** WHAT CAN I DO THAT MY ntlm.domain=CH.WINTERTHUR.COM is returned in
Ethereal but not the dummy value "domain"
Involved in the game is
org.apache.maven.HttpUtils.java
called by
org.apache.maven.ArtifactDownloader.java
How can I add the NTLM required credentials used by NTLM to the default
Authenticator created at
Package org.apache.maven.HttpUtils
public static void useProxyUser( final String proxyHost, final
String proxyPort, final String proxyUserName,
final String proxyPassword )
{
if ( ( proxyHost != null ) && ( proxyPort != null ) )
{
System.getProperties().put( "proxySet", "true" );
System.getProperties().put( "proxyHost", proxyHost );
System.getProperties().put( "proxyPort", proxyPort );
if ( proxyUserName != null )
{
Authenticator.setDefault( new Authenticator()
{
protected PasswordAuthentication
getPasswordAuthentication()
{
return new PasswordAuthentication(
proxyUserName, proxyPassword == null ? new char[0]
: proxyPassword
.toCharArray() );
}
} );
}
}
}
Josef.Stadelmann
@axa-winterthur.ch
AW: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Wayne
Or keep it more simple, maybe you understand me then.
What would you say if subversion, would not work just because it is unable to authenticate properly with your proxy server? Would that tool be useful for you? Not saying what artifacts you need or intend to download with it in the future.
Maven is in this sense like subversion. It hast to download missing artifacts whenever it detects at unforeseen times that an artifact has to be downloaded. This automatic dependency management AND download capability makes maven what it is:
MAVEN - I love it.
Josef
-----Ursprüngliche Nachricht-----
Von: Wayne Fay [mailto:waynefay@gmail.com]
Gesendet: Dienstag, 24. August 2010 16:11
An: Maven Users List
Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
> **** HOW CAN I FORCE THAT BASIC ATHENTICATION IS USED but NEVER NTLM
> **** This would solve my problem
Why are you wasting your time with this? Just download the artifacts
(jar files etc) yourself and copy it to the proper Maven1 local repo
cache structure. I haven't used M1 in a long time so I will admit that
I forget how all that works, but it is not required that Maven itself
download all artifacts, simply that they are available to be used
during the build.
And/or use a Maven Repo Manager that is M1-compatible.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Stephen Connolly <st...@gmail.com>.
_Use a Maven Repository Manager as a proxy to your proxy_
That way you can control how it proxies. AFAIK Nexus can provide you with
the control you need and can server up as Maven 1.x format repos as well
-Stephen
On 30 August 2010 13:34, Stadelmann Josef <
josef.stadelmann@axa-winterthur.ch> wrote:
> Stephen
>
> I agree with some of your points,
>
> But please tell me how authentication with a proxy server is handled in
> maven-2 or maven-3?
>
> If authentication toward a proxy server is handled the same way as in
> maven-1
> then there is at least one pile left in maven-2 or maven-3 :-),
>
> But given there are no such piles left; how then is authentication handled
> in maven-2 or maven-3?
>
> Most important for me:
> Can I force maven-2 or maven-3 to use only BASIC authentication (user name
> AND password) but not
> NTLM or DIGEST toward a proxy server to reach out for artifact downloading,
> this because I run
> from OpenVMS, which might be not as good as Linux or Windows is in dealing
> with NTLM Authentication.
>
> Josef
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Gesendet: Montag, 30. August 2010 12:45
> An: Maven Users List
> Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
>
> 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 <
> josef.stadelmann@axa-winterthur.ch> 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:kathryn@kathrynhuxtable.org]
> > 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: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Wayne Fay <wa...@gmail.com>.
> Please note that currently NTLM proxies are not supported as they have not been tested.
> You may be able to use the relevant system properties on JDK 1.4+ to make this work.
>
> ++> would be nice to know how?
>
> So what java system properties do I have to set to make JDK work and force to use only BASIC authentication?
Googling for "java proxy system property ntlm" takes me to:
http://download.oracle.com/javase/1.4.2/docs/guide/net/properties.html
That page seems to cover what you're looking for.
And here's a page with additional information for JDK6 (same search, a
few links down in the list):
http://download-llnw.oracle.com/javase/6/docs/technotes/guides/net/http-auth.html
As for "forcing" basic auth, that seems to be the default unless you
specify the http.auth.ntlm.domain or another property. But I am far
from an expert in this area. You probably need to be setting
http.proxyHost and http.proxyPort.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Benson Margulies <bi...@gmail.com>.
You could run in Apache Harmony to debug this.
On Mon, Aug 30, 2010 at 1:12 PM, Stadelmann Josef
<jo...@axa-winterthur.ch> wrote:
> It would be very fine if BASIC Authentication would be enforced by default when one opens an URLConnection in OpenVMS and other platforms. But that is not the case. Instead it goes into some kind of NTLM conversation and fails in OpenVMS on JDK 5.0 (that can be seen when I run Ethereal)
>
> I have found the sources below on the web: And I like to see now how it is going for BASIC Authentication on my OpenVMS machine. So far when I try to debug I can see the code called in rt.jar from sun. I can see code because src.zip is in the source class path. But as the rt.jar was not complied with the -g option I can't see any argument values but bunches of asynchronity when doing single steping; Hence I cannot see the argument values passed so deep in code from the java system properties into critical rt.jar routines used to open an connection with the proper authorization and proxy data, called.
>
> How would you go from there to see argument values passed if arguments belong to sun rt.jar code not complied with the -g option; I can only see argument values in my own short code. Do I get somewhere an rt.jar which was compiled with the -g option or do I have to make that myself a project?
>
>
> /*
> * TestJDKNTLM.java
> *
> * Created on 30. August 2010, 15:19
> *
> */
>
> package axawl.spezpla.jdkntlmauth;
>
> import java.io.BufferedReader;
> import java.io.IOException;
> import java.io.InputStreamReader;
> import java.net.URL;
> import java.net.URLConnection;
>
>
> /**
> *
> * @author C770817
> */
> public class TestJDKNTLM {
>
> private void execute() throws IOException {
> #1 System.setProperty("proxySet", "true");
> #2 System.setProperty("http.proxyHost", "bcproxy.ch.winterthur.com");
> #3 System.setProperty("http.proxyPort", "8080");
> #4 System.setProperty("http.proxyUser", "C770817");
> #5 System.setProperty("http.proxyPassword", "mydomainpassword");
> #6 System.setProperty("http.auth.ntlm.domain", "ourdomain");
>
> URL url = new URL("http://www.ks-net.ch");
> URLConnection conn = url.openConnection();
>
> conn.setAllowUserInteraction(true);
> BufferedReader reader = new BufferedReader(new InputStreamReader(conn.getInputStream()));
> int read = 0;
> String body = null;
>
> do {
> body = reader.readLine();
> System.out.println(body);
> } while (body != null);
>
> }
>
> /**
> * @param args the command line arguments
> */
> public static void main(String[] args) throws IOException {
> new TestJDKNTLM().execute();
> }
>
> }
>
> Commenting #1 above out shows no effect on Vista and on OpenVMS
> Commenting #4, #5, #6 out has no effect on Vista and on OpenVMS
> Commenting #2 and/or #3 out shows an effect on OpenVMS and VISTA
>
> I have removed all properties from files like build.properties;
> So ANT and JAVA does not know this properties unless code makes em known.
>
> Effe4ct: on VISTA NTLM takes place and all works due to NTLM works, on OpenVMS I get 407 errors and al fails!
>
> That is to say: NTLM authentication still works because the magic stuff is at the sun corner for VISTA and fails short for the OpenVMS part, but is done in the JDK itself with little to no effect doing such things here in code.
>
> But what is going on there, that remains the big question?
>
> To make it worse - stepping through remote code at OpenVMS shows asynchronity at the rt.jar level; some lines are hit as they should and some are not. That means the sources and or JDK versions used on VISTA and Open VMS are the same but not really! JDK's and/or sources of JDK 1.5 may vary in minor ways, making it hard to debug using a modern IDE like NetBeans and remote debugging. Guess I have to use stone time jdb on OpenVMS to not be enforced to remote debugging and asynchronity when doing single stepping.
>
> So far the nice properties;
>
> On OpenVMS I can conclude: That BASIC authentication does not work if the proxy server asks for NTLM and BASIC because the client side code at OpenVMS does not know how to handle it. And this magic belongs to rt.jar (so far quality and portability among platforms and testing).
>
>
> Josef
>
>
>
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] Im Auftrag von Anders Hammar
> Gesendet: Montag, 30. August 2010 15:30
> An: Maven Users List
> Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
>
> AFAIK, basic auth is what is used out-of-the-box. If you want something
> else, then you need some configuration. So you should be fine.
>
> /Anders
>
> On Mon, Aug 30, 2010 at 15:15, Stadelmann Josef <
> josef.stadelmann@axa-winterthur.ch> wrote:
>
>> Anders
>>
>> Thanks for the info, I went through that already, A DN it is formaven2 and
>> maven3
>>
>> However as you can read as well .. just below the box on tghe mentioned
>> page/like
>> http://maven.apache.org/guides/mini/guide-proxies.html
>>
>> Please note that currently NTLM proxies are not supported as they have not
>> been tested.
>> You may be able to use the relevant system properties on JDK 1.4+ to make
>> this work.
>>
>> ++> would be nice to know how?
>>
>> So what java system properties do I have to set to make JDK work and force
>> to use only BASIC authentication?
>>
>> Josef
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] Im
>> Auftrag von Anders Hammar
>> Gesendet: Montag, 30. August 2010 14:46
>> An: Maven Users List
>> Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
>>
>> http://maven.apache.org/guides/mini/guide-proxies.html
>>
>> /Anders
>>
>> On Mon, Aug 30, 2010 at 14:34, Stadelmann Josef <
>> josef.stadelmann@axa-winterthur.ch> wrote:
>>
>> > Stephen
>> >
>> > I agree with some of your points,
>> >
>> > But please tell me how authentication with a proxy server is handled in
>> > maven-2 or maven-3?
>> >
>> > If authentication toward a proxy server is handled the same way as in
>> > maven-1
>> > then there is at least one pile left in maven-2 or maven-3 :-),
>> >
>> > But given there are no such piles left; how then is authentication
>> handled
>> > in maven-2 or maven-3?
>> >
>> > Most important for me:
>> > Can I force maven-2 or maven-3 to use only BASIC authentication (user
>> name
>> > AND password) but not
>> > NTLM or DIGEST toward a proxy server to reach out for artifact
>> downloading,
>> > this because I run
>> > from OpenVMS, which might be not as good as Linux or Windows is in
>> dealing
>> > with NTLM Authentication.
>> >
>> > Josef
>> >
>> >
>> >
>> >
>> > -----Ursprüngliche Nachricht-----
>> > Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
>> > Gesendet: Montag, 30. August 2010 12:45
>> > An: Maven Users List
>> > Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
>> >
>> > 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 <
>> > josef.stadelmann@axa-winterthur.ch> 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:kathryn@kathrynhuxtable.org]
>> > > 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: users-unsubscribe@maven.apache.org
>> > > > For additional commands, e-mail: users-help@maven.apache.org
>> > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: users-help@maven.apache.org
>> > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: users-help@maven.apache.org
>> > >
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
It would be very fine if BASIC Authentication would be enforced by default when one opens an URLConnection in OpenVMS and other platforms. But that is not the case. Instead it goes into some kind of NTLM conversation and fails in OpenVMS on JDK 5.0 (that can be seen when I run Ethereal)
I have found the sources below on the web: And I like to see now how it is going for BASIC Authentication on my OpenVMS machine. So far when I try to debug I can see the code called in rt.jar from sun. I can see code because src.zip is in the source class path. But as the rt.jar was not complied with the -g option I can't see any argument values but bunches of asynchronity when doing single steping; Hence I cannot see the argument values passed so deep in code from the java system properties into critical rt.jar routines used to open an connection with the proper authorization and proxy data, called.
How would you go from there to see argument values passed if arguments belong to sun rt.jar code not complied with the -g option; I can only see argument values in my own short code. Do I get somewhere an rt.jar which was compiled with the -g option or do I have to make that myself a project?
/*
* TestJDKNTLM.java
*
* Created on 30. August 2010, 15:19
*
*/
package axawl.spezpla.jdkntlmauth;
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import java.net.URL;
import java.net.URLConnection;
/**
*
* @author C770817
*/
public class TestJDKNTLM {
private void execute() throws IOException {
#1 System.setProperty("proxySet", "true");
#2 System.setProperty("http.proxyHost", "bcproxy.ch.winterthur.com");
#3 System.setProperty("http.proxyPort", "8080");
#4 System.setProperty("http.proxyUser", "C770817");
#5 System.setProperty("http.proxyPassword", "mydomainpassword");
#6 System.setProperty("http.auth.ntlm.domain", "ourdomain");
URL url = new URL("http://www.ks-net.ch");
URLConnection conn = url.openConnection();
conn.setAllowUserInteraction(true);
BufferedReader reader = new BufferedReader(new InputStreamReader(conn.getInputStream()));
int read = 0;
String body = null;
do {
body = reader.readLine();
System.out.println(body);
} while (body != null);
}
/**
* @param args the command line arguments
*/
public static void main(String[] args) throws IOException {
new TestJDKNTLM().execute();
}
}
Commenting #1 above out shows no effect on Vista and on OpenVMS
Commenting #4, #5, #6 out has no effect on Vista and on OpenVMS
Commenting #2 and/or #3 out shows an effect on OpenVMS and VISTA
I have removed all properties from files like build.properties;
So ANT and JAVA does not know this properties unless code makes em known.
Effe4ct: on VISTA NTLM takes place and all works due to NTLM works, on OpenVMS I get 407 errors and al fails!
That is to say: NTLM authentication still works because the magic stuff is at the sun corner for VISTA and fails short for the OpenVMS part, but is done in the JDK itself with little to no effect doing such things here in code.
But what is going on there, that remains the big question?
To make it worse - stepping through remote code at OpenVMS shows asynchronity at the rt.jar level; some lines are hit as they should and some are not. That means the sources and or JDK versions used on VISTA and Open VMS are the same but not really! JDK's and/or sources of JDK 1.5 may vary in minor ways, making it hard to debug using a modern IDE like NetBeans and remote debugging. Guess I have to use stone time jdb on OpenVMS to not be enforced to remote debugging and asynchronity when doing single stepping.
So far the nice properties;
On OpenVMS I can conclude: That BASIC authentication does not work if the proxy server asks for NTLM and BASIC because the client side code at OpenVMS does not know how to handle it. And this magic belongs to rt.jar (so far quality and portability among platforms and testing).
Josef
-----Ursprüngliche Nachricht-----
Von: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] Im Auftrag von Anders Hammar
Gesendet: Montag, 30. August 2010 15:30
An: Maven Users List
Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
AFAIK, basic auth is what is used out-of-the-box. If you want something
else, then you need some configuration. So you should be fine.
/Anders
On Mon, Aug 30, 2010 at 15:15, Stadelmann Josef <
josef.stadelmann@axa-winterthur.ch> wrote:
> Anders
>
> Thanks for the info, I went through that already, A DN it is formaven2 and
> maven3
>
> However as you can read as well .. just below the box on tghe mentioned
> page/like
> http://maven.apache.org/guides/mini/guide-proxies.html
>
> Please note that currently NTLM proxies are not supported as they have not
> been tested.
> You may be able to use the relevant system properties on JDK 1.4+ to make
> this work.
>
> ++> would be nice to know how?
>
> So what java system properties do I have to set to make JDK work and force
> to use only BASIC authentication?
>
> Josef
>
>
> -----Ursprüngliche Nachricht-----
> Von: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] Im
> Auftrag von Anders Hammar
> Gesendet: Montag, 30. August 2010 14:46
> An: Maven Users List
> Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
>
> http://maven.apache.org/guides/mini/guide-proxies.html
>
> /Anders
>
> On Mon, Aug 30, 2010 at 14:34, Stadelmann Josef <
> josef.stadelmann@axa-winterthur.ch> wrote:
>
> > Stephen
> >
> > I agree with some of your points,
> >
> > But please tell me how authentication with a proxy server is handled in
> > maven-2 or maven-3?
> >
> > If authentication toward a proxy server is handled the same way as in
> > maven-1
> > then there is at least one pile left in maven-2 or maven-3 :-),
> >
> > But given there are no such piles left; how then is authentication
> handled
> > in maven-2 or maven-3?
> >
> > Most important for me:
> > Can I force maven-2 or maven-3 to use only BASIC authentication (user
> name
> > AND password) but not
> > NTLM or DIGEST toward a proxy server to reach out for artifact
> downloading,
> > this because I run
> > from OpenVMS, which might be not as good as Linux or Windows is in
> dealing
> > with NTLM Authentication.
> >
> > Josef
> >
> >
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> > Gesendet: Montag, 30. August 2010 12:45
> > An: Maven Users List
> > Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
> >
> > 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 <
> > josef.stadelmann@axa-winterthur.ch> 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:kathryn@kathrynhuxtable.org]
> > > 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: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Anders Hammar <an...@hammar.net>.
AFAIK, basic auth is what is used out-of-the-box. If you want something
else, then you need some configuration. So you should be fine.
/Anders
On Mon, Aug 30, 2010 at 15:15, Stadelmann Josef <
josef.stadelmann@axa-winterthur.ch> wrote:
> Anders
>
> Thanks for the info, I went through that already, A DN it is formaven2 and
> maven3
>
> However as you can read as well .. just below the box on tghe mentioned
> page/like
> http://maven.apache.org/guides/mini/guide-proxies.html
>
> Please note that currently NTLM proxies are not supported as they have not
> been tested.
> You may be able to use the relevant system properties on JDK 1.4+ to make
> this work.
>
> ++> would be nice to know how?
>
> So what java system properties do I have to set to make JDK work and force
> to use only BASIC authentication?
>
> Josef
>
>
> -----Ursprüngliche Nachricht-----
> Von: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] Im
> Auftrag von Anders Hammar
> Gesendet: Montag, 30. August 2010 14:46
> An: Maven Users List
> Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
>
> http://maven.apache.org/guides/mini/guide-proxies.html
>
> /Anders
>
> On Mon, Aug 30, 2010 at 14:34, Stadelmann Josef <
> josef.stadelmann@axa-winterthur.ch> wrote:
>
> > Stephen
> >
> > I agree with some of your points,
> >
> > But please tell me how authentication with a proxy server is handled in
> > maven-2 or maven-3?
> >
> > If authentication toward a proxy server is handled the same way as in
> > maven-1
> > then there is at least one pile left in maven-2 or maven-3 :-),
> >
> > But given there are no such piles left; how then is authentication
> handled
> > in maven-2 or maven-3?
> >
> > Most important for me:
> > Can I force maven-2 or maven-3 to use only BASIC authentication (user
> name
> > AND password) but not
> > NTLM or DIGEST toward a proxy server to reach out for artifact
> downloading,
> > this because I run
> > from OpenVMS, which might be not as good as Linux or Windows is in
> dealing
> > with NTLM Authentication.
> >
> > Josef
> >
> >
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> > Gesendet: Montag, 30. August 2010 12:45
> > An: Maven Users List
> > Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
> >
> > 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 <
> > josef.stadelmann@axa-winterthur.ch> 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:kathryn@kathrynhuxtable.org]
> > > 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: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
AW: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Anders
Thanks for the info, I went through that already, A DN it is formaven2 and maven3
However as you can read as well .. just below the box on tghe mentioned page/like
http://maven.apache.org/guides/mini/guide-proxies.html
Please note that currently NTLM proxies are not supported as they have not been tested.
You may be able to use the relevant system properties on JDK 1.4+ to make this work.
++> would be nice to know how?
So what java system properties do I have to set to make JDK work and force to use only BASIC authentication?
Josef
-----Ursprüngliche Nachricht-----
Von: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] Im Auftrag von Anders Hammar
Gesendet: Montag, 30. August 2010 14:46
An: Maven Users List
Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
http://maven.apache.org/guides/mini/guide-proxies.html
/Anders
On Mon, Aug 30, 2010 at 14:34, Stadelmann Josef <
josef.stadelmann@axa-winterthur.ch> wrote:
> Stephen
>
> I agree with some of your points,
>
> But please tell me how authentication with a proxy server is handled in
> maven-2 or maven-3?
>
> If authentication toward a proxy server is handled the same way as in
> maven-1
> then there is at least one pile left in maven-2 or maven-3 :-),
>
> But given there are no such piles left; how then is authentication handled
> in maven-2 or maven-3?
>
> Most important for me:
> Can I force maven-2 or maven-3 to use only BASIC authentication (user name
> AND password) but not
> NTLM or DIGEST toward a proxy server to reach out for artifact downloading,
> this because I run
> from OpenVMS, which might be not as good as Linux or Windows is in dealing
> with NTLM Authentication.
>
> Josef
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Gesendet: Montag, 30. August 2010 12:45
> An: Maven Users List
> Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
>
> 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 <
> josef.stadelmann@axa-winterthur.ch> 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:kathryn@kathrynhuxtable.org]
> > 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: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Anders Hammar <an...@hammar.net>.
http://maven.apache.org/guides/mini/guide-proxies.html
/Anders
On Mon, Aug 30, 2010 at 14:34, Stadelmann Josef <
josef.stadelmann@axa-winterthur.ch> wrote:
> Stephen
>
> I agree with some of your points,
>
> But please tell me how authentication with a proxy server is handled in
> maven-2 or maven-3?
>
> If authentication toward a proxy server is handled the same way as in
> maven-1
> then there is at least one pile left in maven-2 or maven-3 :-),
>
> But given there are no such piles left; how then is authentication handled
> in maven-2 or maven-3?
>
> Most important for me:
> Can I force maven-2 or maven-3 to use only BASIC authentication (user name
> AND password) but not
> NTLM or DIGEST toward a proxy server to reach out for artifact downloading,
> this because I run
> from OpenVMS, which might be not as good as Linux or Windows is in dealing
> with NTLM Authentication.
>
> Josef
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Gesendet: Montag, 30. August 2010 12:45
> An: Maven Users List
> Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
>
> 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 <
> josef.stadelmann@axa-winterthur.ch> 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:kathryn@kathrynhuxtable.org]
> > 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: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
AW: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Stephen
I agree with some of your points,
But please tell me how authentication with a proxy server is handled in maven-2 or maven-3?
If authentication toward a proxy server is handled the same way as in maven-1
then there is at least one pile left in maven-2 or maven-3 :-),
But given there are no such piles left; how then is authentication handled in maven-2 or maven-3?
Most important for me:
Can I force maven-2 or maven-3 to use only BASIC authentication (user name AND password) but not
NTLM or DIGEST toward a proxy server to reach out for artifact downloading, this because I run
from OpenVMS, which might be not as good as Linux or Windows is in dealing with NTLM Authentication.
Josef
-----Ursprüngliche Nachricht-----
Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
Gesendet: Montag, 30. August 2010 12:45
An: Maven Users List
Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
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 <
josef.stadelmann@axa-winterthur.ch> 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:kathryn@kathrynhuxtable.org]
> 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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Stephen Connolly <st...@gmail.com>.
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 <
josef.stadelmann@axa-winterthur.ch> 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:kathryn@kathrynhuxtable.org]
> 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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
AW: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
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:kathryn@kathrynhuxtable.org]
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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Kathryn Huxtable <ka...@kathrynhuxtable.org>.
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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Wayne Fay <wa...@gmail.com>.
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Wayne,
Wasting time?
It seems to me that I am not the only one having problems with Authentication. In particular with NTLM Authentication, or forcing an Authentication Schema.
Therefore again;:
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 system property.
"java is full of it" but I am not the expert on Authentication else I would dive down in Java JDK code to see what missing bits and bytes I can feed via a system property just tell the Authenticator or the like that we want to go with BASIC authentication.
I am not the only one which has problems to force an Authentication schema.
Forcing one or the other Authentication is a long lasting burner in the web.
While I can certainly download artifacts for the maven build-bootstrap, how do I do it best to not get? But then maven-1.1 uses further downloads for plugins and just all what is still not mavenized for maven-2 etc. i.e. axis2-1.2 etc. etc. shall I download all this artifacts as well by hand?
If our companies maven repository would not just keep artifacts for maven 2 and 3 but for maven 1 as well, then I would not be here asking silly questions and waste others time.
Josef
-----Ursprüngliche Nachricht-----
Von: Wayne Fay [mailto:waynefay@gmail.com]
Gesendet: Dienstag, 24. August 2010 16:11
An: Maven Users List
Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
> **** HOW CAN I FORCE THAT BASIC ATHENTICATION IS USED but NEVER NTLM
> **** This would solve my problem
Why are you wasting your time with this? Just download the artifacts
(jar files etc) yourself and copy it to the proper Maven1 local repo
cache structure. I haven't used M1 in a long time so I will admit that
I forget how all that works, but it is not required that Maven itself
download all artifacts, simply that they are available to be used
during the build.
And/or use a Maven Repo Manager that is M1-compatible.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-1.1 build-bootstrap fails with OpenVMS
Posted by Wayne Fay <wa...@gmail.com>.
> **** HOW CAN I FORCE THAT BASIC ATHENTICATION IS USED but NEVER NTLM
> **** This would solve my problem
Why are you wasting your time with this? Just download the artifacts
(jar files etc) yourself and copy it to the proper Maven1 local repo
cache structure. I haven't used M1 in a long time so I will admit that
I forget how all that works, but it is not required that Maven itself
download all artifacts, simply that they are available to be used
during the build.
And/or use a Maven Repo Manager that is M1-compatible.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org