I've deployed an artifact that does not have the same name as its parent
module (long story) and I can't retrieve it, getting this exception:
org.apache.maven.archiva.repository.layout.LayoutException: Invalid path
to Artifact: filename format is invalid, should start with artifactId as
stated in
I have a strange problem where an Archiva instance absolutely refuses to
retrieve one particular artifact from central under any circumstances...
it is /org/apache/maven/maven/2.0.6/maven-2.0.6.pom . I've verified
that the instance can retrieve other artifacts, in fact maven-2.0.5.pom
retrieves
in
the proxying related to that artifact.
Do you have any content for that version in the managed repository?
- Brett
On 29/02/2008, Brown, Carlton [EMAIL PROTECTED] wrote:
I have a strange problem where an Archiva instance absolutely refuses
to retrieve one particular artifact from central
In my latest Archiva installation, I noticed that Archiva resolves the
path to the derby database relative to whatever was the current working
directory at the time Tomcat was started.
For example, if I'm in $CATALINA_HOME/bin and I run ./catalina.sh start,
then the derby database gets created
-Original Message-
From: Eric Miles [mailto:[EMAIL PROTECTED]
Sent: Friday, February 22, 2008 4:07 PM
To: archiva-users@maven.apache.org
Subject: RE: Archiva crashes after a couple of days
I too had this same issue. Make sure your cron syntax is correct as
it
is not standard unix
Hi all,
This question may in fact be generalized to Maven, but I'm wondering if
there is any reverse lookup mechanism for jar artifacts. For example,
I have this mystery dependency called foo.jar. Is there a way to
query a Maven-compliant repository to search on the checksum to
determine the
Hi,
I've got a problem where an artifact downloaded to the filesystem cannot
be browsed. There's some problem with either the database scanning or
repository indexing. The maven metadata files are not being generated.
The pom file appears to be good.
How can I troubleshoot this problem and
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Friday, February 15, 2008 1:17 PM
To: archiva-users@maven.apache.org
Subject: Re: Artifacts not being indexed
On Fri, Feb 15, 2008 at 11:06 AM, Brown, Carlton
[EMAIL PROTECTED] wrote:
I've got a problem
I'm getting this error unable to find project model when I browse down
to a particular module, even though the POM and metadata are there, and
I've force the database to rescan. What's going on and and how do I
need to fix it?
TIA,
Carlton
-
Hi all,
Is there a simple way to test whether Archiva can retrieve a certain
artifact from the central maven repository without going through all the
Maven client-side configuration?
I was thinking just to point my browser at the Archiva repository with
the URL of a non-existent
10 matches
Mail list logo
