Jesse McConnell wrote:
>
> that should bypass certificates as well, there is something janky with
> it right now as well so you _may_ need to hit that url, then with the
> s in the https with the same url and then again the url above. there
> is a jira ticket on that strangeness
>
I was not a
Would one approach be to support the Maven "scm:" style URLs which seem to
delegate to the underlying SCM implementation to ensure authentication (and
certificate acceptance) have been performed?
Not that I'm volunteering... (yet).
Thanks for the response,
Tim
--
View this message in context:
last I looked (6-8 months ago) it will take come changes not just in
continuum but in the scm code and down into plexus-formica as well...
some api changing/adding mostly. it will get sorted out
anyone interested in tackling it I can point you in what I think is
the right direction
jesse
On 8
I have the same problem. However I figured out my issue for now (see below).
Meanwhile might I suggest you take a look in
apps/continuum/logs/continuum.log and check for the specific nature of the
error and post it here. It might reveal the core problem.
I had the same problem when omitting th
There is still a question hanging around in my head related to this issue.
If I try to add a project with the following url I get a message that the
url is not valid
https://username:[EMAIL PROTECTED]/svn/name/pom.xml
"You must provide a valid url (...)"
I cannot seem to get this to work, if I
you should just need to setup the settings.xml file for the user that
is running the continuum instance.
general rule of thumb is that if you can run it from the commandline
it ought to run in continuum.
There is a url format that you can use when pointing at the top lvl
pom.xml when adding the
