Have tried both...they come back with the same message:

/svn: OPTIONS of 'https://svn.apache.org/repos/asf/opennlp/trunk': Could not create SSL connection through proxy server: Could not authenticate to proxy server: rejected Basic challenge (https://svn.apache.org)/

Of course i've stripped the asterisks before "**asf"...

Jim


On 25/02/12 00:11, [email protected] wrote:
Are you doing:

svn co https://svn.apache.org/repos/**asf/*incubator*/opennlp/trunk/

?

The new one is

svn co https://svn.apache.org/repos/**asf/opennlp/trunk/

It works for me.

On Fri, Feb 24, 2012 at 10:06 PM, Jim - FooBar();<[email protected]>wrote:

Hey William,

I am indeed using the URL from the link you sent...this is where i found
it in the first place. I am trying to checkout the latest version using
"svn co" but i cannot authenticate...

Can anyone checkout a copy? For some reason i can't...

Jim


On 24/02/12 23:58, [email protected] wrote:

Hi Jim,

OpenNLP was promoted to Apache top level project. Please use the SVN URL
described here: 
http://opennlp.apache.org/**source-code.html<http://opennlp.apache.org/source-code.html>

We are in the middle of the migration process, but the SVN already moved
to
its new location, as well as the mailing lists.



On Fri, Feb 24, 2012 at 9:46 PM, Jim - FooBar();<[email protected]**
wrote:
  Do i need a username for the svn repo?
or the command svn co 
https://svn.apache.org/repos/****<https://svn.apache.org/repos/**>
asf/incubator/opennlp/trunk/<h**ttps://svn.apache.org/repos/**
asf/incubator/opennlp/trunk/<https://svn.apache.org/repos/asf/incubator/opennlp/trunk/>
**will do?

For some reason it is not working for me...I realize this may have
nothing
to do with openNLP!
BTW i'm on ubuntu 11.10 and am not missing any subversion packages ...

Thanks,
Jim


On 24/02/12 21:16, James Kosin wrote:

  On 2/24/2012 11:21 AM, Jim - FooBar(); wrote:
  <dictionary case_sensitive="false">
  Just be sure your dictionary has the line like the following at the
top... and your are using the trunk code in SVN.  We have had a few
issues with case sensitivity flags and implementing.

James



Reply via email to