I have had this same problem, but not with the admin user, rather with other
new users I have created. I think I have found the problem. If a user only
has the role of "Repository Manager", then all that user can do is
browse/serarch. I have to assign the user to the "System Administrator" role
t
I was using (just setting up) Archiva 1.0.2. I decided to upgrade to 1.1
before going live. I had email working correctly w/ Plexus settings, but
cannot get archiva/jetty to correctly send email.
I have made the following changes to the jetty.xml
mail/Session
> a Repository Manager role for each repo, as well as a global one. Are
> you not seeing those when you edit a user?
On Wed, Jul 16, 2008 at 4:36 PM, Mark Johnson <[EMAIL PROTECTED]>
wrote:
> I have had this same problem, but not with the admin user, rather with
other
> new users
ging the contents of the repo, but not the
> configuration.)
>
> --
> Wendy
>
> On Thu, Jul 24, 2008 at 8:45 AM, Mark Johnson <[EMAIL PROTECTED]>
> wrote:
> > I have the same problem on 1.1. I have grated all combinations of roles,
> > (Repo Manager to specifi
opened for 1.1, see
> http://jira.codehaus.org/browse/MRM-584 for more details..
>
>
> Thanks,
> Deng
> On Thu, Jul 24, 2008 at 5:15 AM, Mark Johnson <[EMAIL PROTECTED]>
wrote:
> I was using (just setting up) Archiva 1.0.2. I decided to upgrade to 1.1
> before go
Regarding this problem "network proxy fails after upgrading to archiva 1.1"
(http://jira.codehaus.org/browse/MRM-884); I am new to Archiva, and just
finished getting 1.0.2 running. I decided to convert to 1.1 before going
live, but have hit this problem. My Archiva repositories are currently
empt
4/wagon-provider-api-1.0-beta-4.jar
> >
> > Cheers,
> > Brett
> >
> > 2008/7/28 Dan Dare <[EMAIL PROTECTED]>:
> >>
> >> If the problem has been fixed (indicated in JIRA) how do I get hold
> of
> > the
> >> changes that were necessary fo
,
Mark
On Mon, Jul 28, 2008 at 8:07 PM, Brett Porter <[EMAIL PROTECTED]>wrote:
> 2008/7/29 Mark Johnson <[EMAIL PROTECTED]>:
> > I downloaded the snapshot referenced below, extracted it on my linux
> system,
> > updated the wrapper.conf (the only conf file which appear
d in some
> additional logging for proxying failures.
>
> The tarball above will be updated within an hour or so otherwise.
>
> Cheers,
> Brett
>
> 2008/7/30 Mark Johnson <[EMAIL PROTECTED]>:
> > When the app starts, it identifies itself as Archiva 1.2-SNAPSHOT
>
Can you also check that you have removed all the old wagon-* JARs from
> WEB-INF/lib?
>
> Thanks,
> Brett
>
> >
> > Cheers,
> > Brett
> >
> > 2008/7/30 Mark Johnson <[EMAIL PROTECTED]>:
> >> I did not build, but downloaded the new tarball
.apache.maven.archiva.proxy" with
> a level of "debug" you should start to see the proxy details used on
> every request.
>
> - Brett
>
> 2008/7/31 Mark Johnson <[EMAIL PROTECTED]>:
> > No, there are not an earlier "Could not connect to" warning.
&
I cannot seem to resolve the proxy download error. I'm wondering if I have
something configured incorrectly in archiva. Does anyone have any further
suggestions?
I have started over clean with archiva using 1.1.1. I then pasted the "test
url" in the instructions (modified for my install), as sh
original
1.2 snapshot that solved the proxy problem, I have been struggling with my
internet access, and the errors are quite similar.
Thanks Brett for your help.
Mark
On Mon, Aug 11, 2008 at 3:23 PM, Mark Johnson <[EMAIL PROTECTED]>wrote:
> I cannot seem to resolve the proxy download er
13 matches
Mail list logo
