commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gilles Sadowski <gil...@harfang.homelinux.org>
Subject Re: [jira] Commented: (MATH-389) New superclass for "AbstractScalarDifferentiableOptimizer"
Date Wed, 21 Jul 2010 07:50:13 GMT
> >>> I ran "mvn site" but could not find the report. What is the file name?
> >>
> >> clirr-report.html
> >>
> >> It should be in top directory. It is generated by clirr-maven-plugin.
> >> You can also try "mvn clirr:check" or "mvn clirr:clirr", see
> >> <http://mojo.codehaus.org/clirr-maven-plugin/usage.html>
> > 
> > Excerpt from the build output:
> > 
> > [INFO] Unable to find a previous version of the project in the repository
> 
> Perhaps you should make an "mvn install" of the previous version (i.e.
> 2.1) in your local repository.

Does that mean that I must check out the 2.1 tag?
If so, I did the following

 $ svn co http://svn.apache.org/viewvc/commons/proper/math/tags/MATH_2_1/

And got this error:

 svn: Repository moved permanently to '/viewvc/commons/proper/math/tags/MATH_2_1/'; please
relocate


Gilles

P.S. I found the following possible explanation on the Subversion FAQ page:
---CUT---
I can see my repository in a web browser, but 'svn checkout' gives me an
error about "301 Moved Permanently". What's wrong?

It means your httpd.conf is misconfigured. Usually this error happens when
you've defined the Subversion virtual "location" to exist within two
different scopes at the same time.

For example, if you've exported a repository as <Location /www/foo>, but
you've also set your DocumentRoot to be /www, then you're in trouble. When
the request comes in for /www/foo/bar, apache doesn't know whether to find a
real file named /foo/bar within your DocumentRoot, or whether to ask
mod_dav_svn to fetch a file /bar from the /www/foo repository. Usually the
former case wins, and hence the "Moved Permanently" error.

The solution is to make sure your repository <Location> does not overlap or
live within any areas already exported as normal web shares.

It's also possible that you have an object in the web root which has the
same name as your repository URL. For example, imagine your web server's
document root is /var/www and your Subversion repository is located at
/home/svn/repo. You then configure Apache to serve the repository at
http://localhost/myrepo. If you then create the directory /var/www/myrepo/
this will cause a 301 error to occur.
---CUT---

Mime
View raw message