You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by "SlinnHawkins, Jon (ELS-CAM)" <J....@elsevier.com> on 2008/02/04 12:15:08 UTC
Achiva and Proximity
Hi All,
Is it possible to migrate an existing Proximity repository to use
Archiva ?
Many thanks
Jon
This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084,
whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom.
Re: Achiva and Proximity
Posted by Brett Porter <br...@gmail.com>.
This seems like a bug - can you file this in JIRA?
Thanks,
Brett
On 05/02/2008, SlinnHawkins, Jon (ELS-CAM) <J....@elsevier.com> wrote:
> OK - Thanks got my repositories into Archiva now
>
> However, it does not seem to be indexing my
> <name>-<version>-test-sources.jar artifacts...
>
> I am getting the following in my logs :
>
> 218109 [pool-2-thread-1] ERROR
> org.apache.maven.archiva.repository.scanner.RepositoryScanner:default -
> Consumer [metadata-updater] had an error when processing file
> [C:\apps\Tomcat
> 6.0\data\repositories\snapshots\com\elsevier\elslon\common\components\ec
> om\eCommerce\0.0.1-SNAPSHOT\eCommerce-0.0.1-20070219.171202-34-test-sour
> ces.jar]: Unable to convert to artifact reference:
> com\elsevier\elslon\common\components\ecom\eCommerce\0.0.1-SNAPSHOT\eCom
> merce-0.0.1-20070219.171202-34-test-sources.jar
> org.apache.maven.archiva.consumers.ConsumerException: Unable to convert
> to artifact reference:
> com\elsevier\elslon\common\components\ecom\eCommerce\0.0.1-SNAPSHOT\eCom
> merce-0.0.1-20070219.171202-34-test-sources.jar
> at
> org.apache.maven.archiva.consumers.core.MetadataUpdaterConsumer.processF
> ile(MetadataUpdaterConsumer.java:167)
> at
> org.apache.maven.archiva.repository.scanner.functors.ConsumerProcessFile
> Closure.execute(ConsumerProcessFileClosure.java:57)
> at
> org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java
> :117)
> at
> org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.
> java:388)
> at
> org.apache.maven.archiva.repository.scanner.RepositoryScannerInstance.di
> rectoryWalkStep(RepositoryScannerInstance.java:138)
> at
> org.codehaus.plexus.util.DirectoryWalker.fireStep(DirectoryWalker.java:1
> 73)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:39
> 1)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
> 5)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
> 5)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
> 5)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
> 5)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
> 5)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
> 5)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
> 5)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
> 5)
> at
> org.codehaus.plexus.util.DirectoryWalker.scan(DirectoryWalker.java:344)
> at
> org.apache.maven.archiva.repository.scanner.DefaultRepositoryScanner.sca
> n(DefaultRepositoryScanner.java:120)
> at
> org.apache.maven.archiva.repository.scanner.DefaultRepositoryScanner.sca
> n(DefaultRepositoryScanner.java:64)
> at
> org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTa
> skExecutor.executeTask(ArchivaRepositoryScanningTaskExecutor.java:106)
> at
> org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut
> orRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
> at
> edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter
> .call(Executors.java:442)
> at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask
> .java:176)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWor
> ker(ThreadPoolExecutor.java:987)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
> .run(ThreadPoolExecutor.java:528)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.maven.archiva.repository.layout.LayoutException:
> Invalid path to Artifact: filename format is invalid,expected timestamp
> format in filename.
> at
> org.apache.maven.archiva.repository.content.DefaultPathParser.toArtifact
> Reference(DefaultPathParser.java:134)
> at
> org.apache.maven.archiva.repository.content.AbstractDefaultRepositoryCon
> tent.toArtifactReference(AbstractDefaultRepositoryContent.java:49)
> at
> org.apache.maven.archiva.repository.content.ManagedDefaultRepositoryCont
> ent.toArtifactReference(ManagedDefaultRepositoryContent.java:330)
> at
> org.apache.maven.archiva.consumers.core.MetadataUpdaterConsumer.processF
> ile(MetadataUpdaterConsumer.java:161)
> ... 24 more
>
> Any help appreciated
>
> Thanks
>
> Jon
>
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
> Sent: 05 February 2008 02:14
> To: archiva-users@maven.apache.org
> Subject: Re: Achiva and Proximity
>
> This should later be resolved by running through both the repository
> scan and the database scan processes though?
>
> On 05/02/2008, Heck, Joe <Jo...@dig.com> wrote:
> > That process (dropping in new directories to an archiva instance) is
> > exactly what I'm doing - works very nicely. One tidbit that I noticed
> > in version 1.0 is that if you have established an internal repository
> > and then add *to it* after the fact, the artifacts don't always get
> > indexed properly.
> >
> > I found that getting the directory in place prior to launching archiva
>
> > for the first time (I was shoving all my artifacts into the default
> > "internal" repository) worked to resolve that issue.
> >
> > -joe
> >
> > -----Original Message-----
> > Sent: Monday, February 04, 2008 9:15 AM
> > To: archiva-users@maven.apache.org
> > Subject: Re: Achiva and Proximity
> >
> > Sure - since both use repositories stored in the file system you can
> > configure Archiva to point at the disk location of the repositories
> > when you add managed repositories. They'll be scanned and indexed
> > after they are added.
> >
> > Archiva doesn't however have an option for importing configuration
> > from Proximity.
> >
> > Cheers,
> > Brett
> >
> > On 04/02/2008, SlinnHawkins, Jon (ELS-CAM)
> > <J....@elsevier.com>
> > wrote:
> > > Hi All,
> > >
> > > Is it possible to migrate an existing Proximity repository to use
> > > Archiva ?
> > >
> > > Many thanks
> > >
> > > Jon
> > >
> > >
> > >
> > > This email is from Elsevier Limited, a company registered in England
> > and Wales with company number 1982084,
> > > whose registered office is The Boulevard, Langford Lane, Kidlington,
> > Oxford, OX5 1GB, United Kingdom.
> > >
> > >
> >
> >
> > --
> > Brett Porter
> > Blog: http://www.devzuz.org/blogs/bporter/
> >
>
>
> --
> Brett Porter
> Blog: http://www.devzuz.org/blogs/bporter/
>
>
> This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084,
> whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom.
>
>
--
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/
RE: Achiva and Proximity
Posted by "SlinnHawkins, Jon (ELS-CAM)" <J....@elsevier.com>.
OK - Thanks got my repositories into Archiva now
However, it does not seem to be indexing my
<name>-<version>-test-sources.jar artifacts...
I am getting the following in my logs :
218109 [pool-2-thread-1] ERROR
org.apache.maven.archiva.repository.scanner.RepositoryScanner:default -
Consumer [metadata-updater] had an error when processing file
[C:\apps\Tomcat
6.0\data\repositories\snapshots\com\elsevier\elslon\common\components\ec
om\eCommerce\0.0.1-SNAPSHOT\eCommerce-0.0.1-20070219.171202-34-test-sour
ces.jar]: Unable to convert to artifact reference:
com\elsevier\elslon\common\components\ecom\eCommerce\0.0.1-SNAPSHOT\eCom
merce-0.0.1-20070219.171202-34-test-sources.jar
org.apache.maven.archiva.consumers.ConsumerException: Unable to convert
to artifact reference:
com\elsevier\elslon\common\components\ecom\eCommerce\0.0.1-SNAPSHOT\eCom
merce-0.0.1-20070219.171202-34-test-sources.jar
at
org.apache.maven.archiva.consumers.core.MetadataUpdaterConsumer.processF
ile(MetadataUpdaterConsumer.java:167)
at
org.apache.maven.archiva.repository.scanner.functors.ConsumerProcessFile
Closure.execute(ConsumerProcessFileClosure.java:57)
at
org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java
:117)
at
org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.
java:388)
at
org.apache.maven.archiva.repository.scanner.RepositoryScannerInstance.di
rectoryWalkStep(RepositoryScannerInstance.java:138)
at
org.codehaus.plexus.util.DirectoryWalker.fireStep(DirectoryWalker.java:1
73)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:39
1)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
5)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
5)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
5)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
5)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
5)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
5)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
5)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:38
5)
at
org.codehaus.plexus.util.DirectoryWalker.scan(DirectoryWalker.java:344)
at
org.apache.maven.archiva.repository.scanner.DefaultRepositoryScanner.sca
n(DefaultRepositoryScanner.java:120)
at
org.apache.maven.archiva.repository.scanner.DefaultRepositoryScanner.sca
n(DefaultRepositoryScanner.java:64)
at
org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTa
skExecutor.executeTask(ArchivaRepositoryScanningTaskExecutor.java:106)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut
orRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
at
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter
.call(Executors.java:442)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask
.java:176)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWor
ker(ThreadPoolExecutor.java:987)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
.run(ThreadPoolExecutor.java:528)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.maven.archiva.repository.layout.LayoutException:
Invalid path to Artifact: filename format is invalid,expected timestamp
format in filename.
at
org.apache.maven.archiva.repository.content.DefaultPathParser.toArtifact
Reference(DefaultPathParser.java:134)
at
org.apache.maven.archiva.repository.content.AbstractDefaultRepositoryCon
tent.toArtifactReference(AbstractDefaultRepositoryContent.java:49)
at
org.apache.maven.archiva.repository.content.ManagedDefaultRepositoryCont
ent.toArtifactReference(ManagedDefaultRepositoryContent.java:330)
at
org.apache.maven.archiva.consumers.core.MetadataUpdaterConsumer.processF
ile(MetadataUpdaterConsumer.java:161)
... 24 more
Any help appreciated
Thanks
Jon
-----Original Message-----
From: Brett Porter [mailto:brett.porter@gmail.com]
Sent: 05 February 2008 02:14
To: archiva-users@maven.apache.org
Subject: Re: Achiva and Proximity
This should later be resolved by running through both the repository
scan and the database scan processes though?
On 05/02/2008, Heck, Joe <Jo...@dig.com> wrote:
> That process (dropping in new directories to an archiva instance) is
> exactly what I'm doing - works very nicely. One tidbit that I noticed
> in version 1.0 is that if you have established an internal repository
> and then add *to it* after the fact, the artifacts don't always get
> indexed properly.
>
> I found that getting the directory in place prior to launching archiva
> for the first time (I was shoving all my artifacts into the default
> "internal" repository) worked to resolve that issue.
>
> -joe
>
> -----Original Message-----
> Sent: Monday, February 04, 2008 9:15 AM
> To: archiva-users@maven.apache.org
> Subject: Re: Achiva and Proximity
>
> Sure - since both use repositories stored in the file system you can
> configure Archiva to point at the disk location of the repositories
> when you add managed repositories. They'll be scanned and indexed
> after they are added.
>
> Archiva doesn't however have an option for importing configuration
> from Proximity.
>
> Cheers,
> Brett
>
> On 04/02/2008, SlinnHawkins, Jon (ELS-CAM)
> <J....@elsevier.com>
> wrote:
> > Hi All,
> >
> > Is it possible to migrate an existing Proximity repository to use
> > Archiva ?
> >
> > Many thanks
> >
> > Jon
> >
> >
> >
> > This email is from Elsevier Limited, a company registered in England
> and Wales with company number 1982084,
> > whose registered office is The Boulevard, Langford Lane, Kidlington,
> Oxford, OX5 1GB, United Kingdom.
> >
> >
>
>
> --
> Brett Porter
> Blog: http://www.devzuz.org/blogs/bporter/
>
--
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/
This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084,
whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom.
Re: Achiva and Proximity
Posted by Brett Porter <br...@gmail.com>.
This should later be resolved by running through both the repository
scan and the database scan processes though?
On 05/02/2008, Heck, Joe <Jo...@dig.com> wrote:
> That process (dropping in new directories to an archiva instance) is
> exactly what I'm doing - works very nicely. One tidbit that I noticed in
> version 1.0 is that if you have established an internal repository and
> then add *to it* after the fact, the artifacts don't always get indexed
> properly.
>
> I found that getting the directory in place prior to launching archiva
> for the first time (I was shoving all my artifacts into the default
> "internal" repository) worked to resolve that issue.
>
> -joe
>
> -----Original Message-----
> Sent: Monday, February 04, 2008 9:15 AM
> To: archiva-users@maven.apache.org
> Subject: Re: Achiva and Proximity
>
> Sure - since both use repositories stored in the file system you can
> configure Archiva to point at the disk location of the repositories
> when you add managed repositories. They'll be scanned and indexed
> after they are added.
>
> Archiva doesn't however have an option for importing configuration
> from Proximity.
>
> Cheers,
> Brett
>
> On 04/02/2008, SlinnHawkins, Jon (ELS-CAM) <J....@elsevier.com>
> wrote:
> > Hi All,
> >
> > Is it possible to migrate an existing Proximity repository to use
> > Archiva ?
> >
> > Many thanks
> >
> > Jon
> >
> >
> >
> > This email is from Elsevier Limited, a company registered in England
> and Wales with company number 1982084,
> > whose registered office is The Boulevard, Langford Lane, Kidlington,
> Oxford, OX5 1GB, United Kingdom.
> >
> >
>
>
> --
> Brett Porter
> Blog: http://www.devzuz.org/blogs/bporter/
>
--
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/
RE: Achiva and Proximity
Posted by "Heck, Joe" <Jo...@dig.com>.
That process (dropping in new directories to an archiva instance) is
exactly what I'm doing - works very nicely. One tidbit that I noticed in
version 1.0 is that if you have established an internal repository and
then add *to it* after the fact, the artifacts don't always get indexed
properly.
I found that getting the directory in place prior to launching archiva
for the first time (I was shoving all my artifacts into the default
"internal" repository) worked to resolve that issue.
-joe
-----Original Message-----
Sent: Monday, February 04, 2008 9:15 AM
To: archiva-users@maven.apache.org
Subject: Re: Achiva and Proximity
Sure - since both use repositories stored in the file system you can
configure Archiva to point at the disk location of the repositories
when you add managed repositories. They'll be scanned and indexed
after they are added.
Archiva doesn't however have an option for importing configuration
from Proximity.
Cheers,
Brett
On 04/02/2008, SlinnHawkins, Jon (ELS-CAM) <J....@elsevier.com>
wrote:
> Hi All,
>
> Is it possible to migrate an existing Proximity repository to use
> Archiva ?
>
> Many thanks
>
> Jon
>
>
>
> This email is from Elsevier Limited, a company registered in England
and Wales with company number 1982084,
> whose registered office is The Boulevard, Langford Lane, Kidlington,
Oxford, OX5 1GB, United Kingdom.
>
>
--
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/
Re: Achiva and Proximity
Posted by Brett Porter <br...@gmail.com>.
Sure - since both use repositories stored in the file system you can
configure Archiva to point at the disk location of the repositories
when you add managed repositories. They'll be scanned and indexed
after they are added.
Archiva doesn't however have an option for importing configuration
from Proximity.
Cheers,
Brett
On 04/02/2008, SlinnHawkins, Jon (ELS-CAM) <J....@elsevier.com> wrote:
> Hi All,
>
> Is it possible to migrate an existing Proximity repository to use
> Archiva ?
>
> Many thanks
>
> Jon
>
>
>
> This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084,
> whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom.
>
>
--
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/