Hi guys i have raised a bug for this issue
http://jira.codehaus.org/browse/MRM-1024 since the NPE on the user side is not
being handled properly.
however after some digging by adding "struts.multipart.maxSize=20971520" to
webapps/archiva/ROOT/WEB-INF/classes/struts.properties I am now allowed
Aah, this is what happens when you (meaning me) are on too many
[EMAIL PROTECTED] ;-) I read the message and assumed it was on Commons
User, since it
was about Commons FileUpload, not looking to see that it was actually on
Archiva Users. Doh! Sorry about that.
I'm not seeing anywhere that Archiva
Thankyou for the reply Martin,
So this is not a simple configuration change for tomcat or the archiva.war file
then ?
Chris
-Original Message-
From: [EMAIL PROTECTED] on behalf of Martin Cooper
Sent: Thu 11/27/2008 12:08 PM
To: users@archiva.apache.org
Subject: Re: fileupload.FileUplo
I highly recommend reading the user guide and the API docs. That's why we
took the time to write them. ;-) Specifically:
http://commons.apache.org/fileupload/apidocs/org/apache/commons/fileupload/FileUploadBase.html#setSizeMax(long)
http://commons.apache.org/fileupload/apidocs/org/apache/commons/f
hi guys,
i am hitting this problem when users try to upload jars larger then the default
file size of 2097152
SEVERE:
org.apache.commons.fileupload.FileUploadBase$SizeLimitExceededException: the
request was rejected because its size (2346075) exceeds the configured maximum
(2097152)
how c
Are you concerned about people building their projects? You're not
touching the repository content, just the index and database, which
will be re-created.
If the scheduled scanning isn't doing the job, then this is the
easiest way to work around the problem.
--
Wendy
On Wed, Nov 26, 2008 at 10
When I go in the Repository Scanning section I have the following in the
-Consumers for Invalid Content- section:
Repository Scanning - Consumers of Invalid Content
There are no consumers of invalid content available.
How do I add consumers of invalid contents?
Could this be the reason why
Seems quite drastic
I have lots of people depending on the repository and somehow don't feel
very secure doing that
No other solution???
Sonia
Maria Odea Ching-5 wrote:
>
> Hi Sonia,
>
> You could do the following steps to re-create the database:
> 1. stop Archiva
> 2. delete the arc
Just an update in case anyone cares,
I verified that archiva 1.2-M1 doesn't exhibit this behavior.
Brent
>>> "Brent Atkinson" <[EMAIL PROTECTED]> 11/25/2008 6:40 PM >>>
Hi,
I recently upgraded from archiva 1.0.x to 1.1.3 and found that ldap
authentication is broken. Archiva 1.1.3 currently d
The virtual repository will check both if they are both included, and
only use the one where it is found. If you are concerned about
outbound checks by proxied repos, you can configure snapshots and
white/blacklists on those.
Cheers,
Brett
On 26/11/2008, at 4:39 PM, Carlos Sanchez wrote:
You can use the reset password link to have it emailed to you, if that
was set up correctly. Otherwise you need to alter the database, or
drop it entirely.
You can do that by simply removing the data/databases/users directory
if you are using the standalone derby installation and restarting
11 matches
Mail list logo
