Nabble - archiva-users

snapshots purge doesn't work

2009-11-24T00:19:36Z

Hello,

We have upgraded archiva 3 months ago to archiva 1.2.2
We have configured the snapshot repository like this :

Archiva Managed Snapshot Repository :
Identifier : snapshots
Name : Archiva Managed Snapshot Repository
Directory : /home/share/archiva_data/repositories/snapshots
Type : Maven 2.x Repository
Releases Included : N
Snapshots Included :Y
Delete Released Snapshots : Y
Repository Purge By Days Older Than :10
Repository Purge By Retention Count : 3
Scanned : Y
Scanning Cron : 0 1 * * * ?

But since the upgrade no snapshot has been purged.
Is the purge working ? Have we forget a configuration somewhere ?

Regards,

Elise.

Re: Archiva repository scan issue

2009-11-24T00:11:17Z

The repository scanner only processes artifacts whose last modified date
newer than the last run of the repo scan. I think in your case, since the
artifacts were added directly in the file system, they weren't processed
because of this. To work around this, you need to update the last
modification date of the artifacts that you added by executing the following
command for each artifact directory you added:

*find [DIRECTORY_NAME] | xargs touch*

In the next Archiva release, there will be an option from the web UI to scan
the entire repository so all artifacts get processed regardless of its last
modified date (http://jira.codehaus.org/browse/MRM-1056) :)

Thanks,
Deng

On Sat, Nov 21, 2009 at 3:06 AM, Menattamai, Rajasekaran <
Rajasekaran.Menattamai@...> wrote:

>
> Iam not sure if the operation I am doing is incorrect or the repository
> scanning feature in archiva 1.2.2 does not work as expected.
>
> I created a repository. Added some files directly to the repository's
> directory location ( in exactly like the maven2 format ) . Ran the
> "repository scan" for this repository. After the scan the result
> reported that it found 6 new files. These files appear in the "total
> file count" ,but other columns were not updated at all. There are some
> jars and poms in the set of the files I added. When I search for the
> file I added, "search" did not return any results, which means the
> database was not updated. If the operation I am doing is correct, then I
> will open a defect ticket for this.
>
>
>
> Statistics for Repository 'approved_3p'
>
>
> Date of Scan Total File Count Total Size Artifact Count
> Group Count Project Count Plugins Archetypes Jars
> Wars Deployments Downloads
> Fri Nov 20 13:12:43 EST 2009 6 1035114 0 0
> 0 0 0 0 0 0 0
> Fri Nov 20 13:10:59 EST 2009 0 0 0 0 0
> 0 0 0 0 0 0
>
>
>
>
> -- Thanks
>
> Raj
>
> Raj Menattamai
> Software Factory CM
> 240 386 6238 ( O )
> 804 852 4001 ( Cell )
>
>
>
>
>
> Confidentiality Notice: This email, including attachments, may include
> non-public, proprietary, confidential or legally privileged information. If
> you are not an intended recipient or an authorized agent of an intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of the information contained in or transmitted with this e-mail is
> unauthorized and strictly prohibited. If you have received this email in
> error, please notify the sender by replying to this message and permanently
> delete this e-mail, its attachments, and any copies of it immediately. You
> should not retain, copy or use this e-mail or any attachment for any
> purpose, nor disclose all or any part of the contents to any other person.
> Thank you
>
>

Re: Archiva Central repository Vs other remote repositories.

2009-11-20T15:02:10Z

No, there isn't a distinction.

Have you set up a proxy connector to connect the source repository to the new remote one?

On 21/11/2009, at 3:48 AM, Rob Bercik wrote:

> Is there a distinction between the Central repository and other 'remote'
> repositories that you define in Archiva? No matter how I specify other
> repositories from within Archiva, no other repositories seemed to get
> searched other than 'central'. Could someone shed some more light on how I
> define more than one repository to be searched?
>
> Thanks,
> Rob

Archiva repository scan issue

2009-11-20T11:06:39Z

Iam not sure if the operation I am doing is incorrect or the repository
scanning feature in archiva 1.2.2 does not work as expected.

I created a repository. Added some files directly to the repository's
directory location ( in exactly like the maven2 format ) . Ran the
"repository scan" for this repository. After the scan the result
reported that it found 6 new files. These files appear in the "total
file count" ,but other columns were not updated at all. There are some
jars and poms in the set of the files I added. When I search for the
file I added, "search" did not return any results, which means the
database was not updated. If the operation I am doing is correct, then I
will open a defect ticket for this.

Statistics for Repository 'approved_3p'

Date of Scan Total File Count Total Size Artifact Count
Group Count Project Count Plugins Archetypes Jars
Wars Deployments Downloads
Fri Nov 20 13:12:43 EST 2009 6 1035114 0 0
0 0 0 0 0 0 0
Fri Nov 20 13:10:59 EST 2009 0 0 0 0 0
0 0 0 0 0 0

-- Thanks

Raj

Raj Menattamai
Software Factory CM
240 386 6238 ( O )
804 852 4001 ( Cell )

Confidentiality Notice: This email, including attachments, may include non-public, proprietary, confidential or legally privileged information. If you are not an intended recipient or an authorized agent of an intended recipient, you are hereby notified that any dissemination, distribution or copying of the information contained in or transmitted with this e-mail is unauthorized and strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and permanently delete this e-mail, its attachments, and any copies of it immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you

Archiva Central repository Vs other remote repositories.

2009-11-20T08:48:24Z

Is there a distinction between the Central repository and other 'remote'
repositories that you define in Archiva? No matter how I specify other
repositories from within Archiva, no other repositories seemed to get
searched other than 'central'. Could someone shed some more light on how I
define more than one repository to be searched?

Thanks,
Rob

Re: Artifact Upload

2009-11-04T01:05:06Z

Hi Florian,

Have you tried uploading the artifact using 'mvn deploy:deploy-file ...'
instead of the web upload form?

Thanks,
Deng

On Wed, Nov 4, 2009 at 4:38 PM, Florian Probst <florian.probst@...>wrote:

> Hi,
>
> we just installed Archiva 1.2.2 as Repository Manager. It look like,
> artifact
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-scm-plugin</artifactId>
> <version>1.2</version>
> </plugin>
>
> has the following dependency:
>
> <dependency>
> <groupId>ch.ethz.ganymed</groupId>
> <artifactId>ganymed-ssh2</artifactId>
> <version>build210</version>
> </dependency>
>
> I tried to upload the file, but archiva sais "build210" is no valid
> version.
> How can this be resolved?
> Is it possible to copy the file manually and let Archiva find this file?
>
> Thanks,
> Florian
>

Artifact Upload

2009-11-04T00:38:59Z

Hi,

we just installed Archiva 1.2.2 as Repository Manager. It look like,
artifact

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-scm-plugin</artifactId>
<version>1.2</version>
</plugin>

has the following dependency:

<dependency>
<groupId>ch.ethz.ganymed</groupId>
<artifactId>ganymed-ssh2</artifactId>
<version>build210</version>
</dependency>

I tried to upload the file, but archiva sais "build210" is no valid version.
How can this be resolved?
Is it possible to copy the file manually and let Archiva find this file?

Thanks,
Florian

Re: disable policy.allowed.login.attempt

2009-11-03T19:10:13Z

You can override this feature by setting the following property in the
security.properties config file:

security.policy.password.expiration.enabled=false

For more details about Redback configuration:
http://redback.codehaus.org/configuration.html

HTH,
Deng

On Wed, Nov 4, 2009 at 2:25 AM, alexander.elsholz <
alexander.elsholz@...> wrote:

>
> Hi,
>
> is it possible to disable the passwort reset?
>
> thanks alex
> --
> View this message in context:
> http://old.nabble.com/disable-policy.allowed.login.attempt-tp26160678p26160678.html
> Sent from the archiva-users mailing list archive at Nabble.com.
>
>

disable policy.allowed.login.attempt

2009-11-03T10:25:30Z

Hi,

is it possible to disable the passwort reset?

thanks alex

Re: Archiva 1.2.2 and JBoss 5.1

2009-10-28T19:46:56Z

Cool :) Thanks Steve!

-Deng

On Thu, Oct 29, 2009 at 7:36 AM, Stephen Coy <steve.coy@...> wrote:

> Hi there,
>
> I managed to get this working, and have updated the wiki at <
> http://cwiki.apache.org/confluence/display/ARCHIVA/Archiva+on+JBoss>.
>
> Cheers
>
> Steve C.
>
>
> On 25/09/2009, at 1:03 AM, Robert Morse wrote:
>
> Hello Deng,
>> Thanks for the reply. I've tried it with prior versions, but not 1.2.2.
>> Just tried to get the source from a variety of mirrors, and it appears the
>> source zip file may be corrupt since I can't get it to decompress.
>>
>> Once I manage to get it, I'll try working through it, and if successful,
>> post the steps.
>>
>> Thanks.
>>
>> On Sep 22, 2009, at 8:21 PM, Deng Ching wrote:
>>
>> Did you try the steps specified in
>>> http://cwiki.apache.org/confluence/display/ARCHIVA/Archiva+on+JBoss ?
>>> It's
>>> for JBoss 4.2.x but it might be worth a try for 5.1.0 as well..
>>>
>>> Thanks,
>>> Deng
>>>
>>> On Tue, Sep 22, 2009 at 7:47 PM, Robert Morse <rmorse@...>
>>> wrote:
>>>
>>> Has anyone successfully deployed Archiva 1.2.2 (or any version for that
>>>> matter) on JBoss 5.1.0.GA?
>>>> If so, I'd appreciate learning how it's done. Thanks.
>>>>
>>>> The human mind is an iterative processor, it never does anything right
>>>> the
>>>> first time. What it does well is to make improvements on every
>>>> iteration
>>>> (deMarco)
>>>>
>>>>
>>>>
>>>>
>>>>
>> The human mind is an iterative processor, it never does anything right the
>> first time. What it does well is to make improvements on every iteration
>> (deMarco)
>>
>>
>>
>>
>

Re: Archiva 1.2.2 and JBoss 5.1

2009-10-28T16:36:13Z

Hi there,

I managed to get this working, and have updated the wiki at <http://cwiki.apache.org/confluence/display/ARCHIVA/Archiva+on+JBoss
>.

Cheers

Steve C.

On 25/09/2009, at 1:03 AM, Robert Morse wrote:

> Hello Deng,
> Thanks for the reply. I've tried it with prior versions, but not
> 1.2.2. Just tried to get the source from a variety of mirrors, and
> it appears the source zip file may be corrupt since I can't get it
> to decompress.
>
> Once I manage to get it, I'll try working through it, and if
> successful, post the steps.
>
> Thanks.
>
> On Sep 22, 2009, at 8:21 PM, Deng Ching wrote:
>
>> Did you try the steps specified in
>> http://cwiki.apache.org/confluence/display/ARCHIVA/Archiva+on
>> +JBoss ? It's
>> for JBoss 4.2.x but it might be worth a try for 5.1.0 as well..
>>
>> Thanks,
>> Deng
>>
>> On Tue, Sep 22, 2009 at 7:47 PM, Robert Morse <rmorse@...>
>> wrote:
>>
>>> Has anyone successfully deployed Archiva 1.2.2 (or any version for
>>> that
>>> matter) on JBoss 5.1.0.GA?
>>> If so, I'd appreciate learning how it's done. Thanks.
>>>
>>> The human mind is an iterative processor, it never does anything
>>> right the
>>> first time. What it does well is to make improvements on every
>>> iteration
>>> (deMarco)
>>>
>>>
>>>
>>>
>
> The human mind is an iterative processor, it never does anything
> right the first time. What it does well is to make improvements on
> every iteration (deMarco)
>
>
>

Re: archiva/maven 2 compatibility

2009-10-18T19:21:39Z

Hi EJ,

The fix for the bug mentioned was backported to the 1.1.x series and is
available in 1.1.4 (http://archiva.apache.org/docs/1.1.4/release-notes.html).
You would need to upgrade to this version to make it compatible with Maven
2.1.x. The release contains only this fix so there shouldn't be any problems
with the upgrade.

Thanks,
Deng

On Sat, Oct 17, 2009 at 5:36 AM, EJ Ciramella <eciramella@...>wrote:

> Hi all - I just saw this article:
>
>
>
> http://www.sonatype.com/people/2009/07/from-apache-archiva-to-sonatype-n
> exus/<http://www.sonatype.com/people/2009/07/from-apache-archiva-to-sonatype-n%0Aexus/>
>
>
>
> Where there's this:
>
>
>
> <snip>
>
> Apart from the incompatibility with Maven 2.1.0, nothing suggested that
> the new version fixed any of our problems and there were few
> improvements/new features at that time, due to lack of time by the
> maintainers.
>
> </snip>
>
>
>
> Is this still the case? We're evaluating maven 2.2.1 right now. In
> fact, I'm using it locally and have used it to deploy artifacts to our
> archiva (1.1.3) server.
>
>
>
> I don't see any mention of this in release notes for archiva - where can
> I get more detail?
>
>

archiva/maven 2 compatibility

2009-10-16T14:36:12Z

Hi all - I just saw this article:

http://www.sonatype.com/people/2009/07/from-apache-archiva-to-sonatype-n
exus/

Where there's this:

<snip>

Apart from the incompatibility with Maven 2.1.0, nothing suggested that
the new version fixed any of our problems and there were few
improvements/new features at that time, due to lack of time by the
maintainers.

</snip>

Is this still the case? We're evaluating maven 2.2.1 right now. In
fact, I'm using it locally and have used it to deploy artifacts to our
archiva (1.1.3) server.

I don't see any mention of this in release notes for archiva - where can
I get more detail?

Re: Using http for deploy

2009-10-09T03:54:20Z

On Fri, 2009-10-09 at 18:42 +0800, Deng Ching wrote:

> On Fri, Oct 9, 2009 at 6:38 PM, Thorsten Scherler <
> thorsten.scherler.ext@...> wrote:
>
> > Hi all,
> >
> > I am looking for information about using http protocol to deploy our
> > artifacts.
> >
> > In our use case Archiva is a proxy for the external repos (like the
> > official apache one) but we want to deploy our own artifacts on it.
> >
> > We found some information about doing it with scp:// but we would like
> > to use http:// instead.
> >
> > Is this possible and if so can somebody point me to some documentation
> > bout it?
> >
>
> Yes it's possible, here's the documentation for that..
>
> http://archiva.apache.org/docs/1.2.2/userguide/deploy.html
>
> You would also need to grant the user the Repository Manager role for the
> repo in order to be able to deploy to it.
>
>

Thank you very much for your very quick answer. I will give it a go.

salu2

> >
> > TIA
> >
> > salu2
> >
> > P.S. It took me a while to find
> > http://archiva.apache.org/mail-lists.html since I did not found a direct
> > link to page. In the end I need to use a search engine to find it.
> >
>
> Noted, thanks! :)
>
> -Deng
>
> --
> > Thorsten Scherler <thorsten.at.apache.org>
> > Open Source Java <consulting, training and solutions>
> >
> > Sociedad Andaluza para el Desarrollo de la Sociedad
> > de la Información, S.A.U. (SADESI)
> >
> >
> >
> >
> >

--
Thorsten Scherler <thorsten.at.apache.org>
Open Source Java <consulting, training and solutions>

Sociedad Andaluza para el Desarrollo de la Sociedad
de la Información, S.A.U. (SADESI)

Re: Using http for deploy

2009-10-09T03:42:28Z

On Fri, Oct 9, 2009 at 6:38 PM, Thorsten Scherler <
thorsten.scherler.ext@...> wrote:

> Hi all,
>
> I am looking for information about using http protocol to deploy our
> artifacts.
>
> In our use case Archiva is a proxy for the external repos (like the
> official apache one) but we want to deploy our own artifacts on it.
>
> We found some information about doing it with scp:// but we would like
> to use http:// instead.
>
> Is this possible and if so can somebody point me to some documentation
> bout it?
>

Yes it's possible, here's the documentation for that..

http://archiva.apache.org/docs/1.2.2/userguide/deploy.html

You would also need to grant the user the Repository Manager role for the
repo in order to be able to deploy to it.

>
> TIA
>
> salu2
>
> P.S. It took me a while to find
> http://archiva.apache.org/mail-lists.html since I did not found a direct
> link to page. In the end I need to use a search engine to find it.
>

Noted, thanks! :)

-Deng

--

> Thorsten Scherler <thorsten.at.apache.org>
> Open Source Java <consulting, training and solutions>
>
> Sociedad Andaluza para el Desarrollo de la Sociedad
> de la Información, S.A.U. (SADESI)
>
>
>
>
>

Using http for deploy

2009-10-09T03:34:20Z

Hi all,

I am looking for information about using http protocol to deploy our
artifacts.

In our use case Archiva is a proxy for the external repos (like the
official apache one) but we want to deploy our own artifacts on it.

We found some information about doing it with scp:// but we would like
to use http:// instead.

Is this possible and if so can somebody point me to some documentation
bout it?

TIA

salu2

P.S. It took me a while to find
http://archiva.apache.org/mail-lists.html since I did not found a direct
link to page. In the end I need to use a search engine to find it.
--
Thorsten Scherler <thorsten.at.apache.org>
Open Source Java <consulting, training and solutions>

Sociedad Andaluza para el Desarrollo de la Sociedad
de la Información, S.A.U. (SADESI)

Re: Archiva not working on 64 bit Linux

2009-10-07T09:51:12Z

On a follow up, I managed to make it work:

I simply deleted the /lib/libwrapper-linux-x86-32.so and /bin/wrapper-linux-x86-32 files.

Perhaps brett and the rest of the team can figure out why this is needed and, if confirmed, add this to the wiki instructions.

Thanks to Babak Shafian and his post at http://www.mail-archive.com/users@continuum.apache.org/msg01688.html

wild_oscar wrote:

Hi,

I tried running archiva on an Ubuntu 9.04 64 bits:

1) Downloaded version 1.2.2
2) Untared it
3) ran ./bin/archiva console

But I get:

eval: 1: /home/mike/Software/archiva/apache-archiva-1.2.2/bin/./wrapper-linux-x86-32: not found

I do have some wrapper-linux files on archiva's root directory; including 32 and 64 ones. I've chmod them to 777, but no luck: I can't seem to be able to run it!

Has anyone successfully run archiva in these conditions, or is otherwise able to help me out?
Thank you!

Archiva not working on 64 bit Linux

2009-10-07T09:26:24Z

Hi,

I tried running archiva on an Ubuntu 9.04 64 bits:

1) Downloaded version 1.2.2
2) Untared it
3) ran ./bin/archiva console

But I get:

eval: 1: /home/mike/Software/archiva/apache-archiva-1.2.2/bin/./wrapper-linux-x86-32: not found

I do have some wrapper-linux files on archiva's root directory; including 32 and 64 ones. I've chmod them to 777, but no luck: I can't seem to be able to run it!

Has anyone successfully run archiva in these conditions, or is otherwise able to help me out?
Thank you!

ApacheCon US (Oakland) is in < 5 weeks: Nov 2-6

2009-09-29T21:06:40Z

I posted this to the Maven Users list, but am re-posting here for
anyone that isn't subscribed there.

ApacheCon US is coming up in just a few weeks in Oakland. You can
register from the web site: http://us.apachecon.com/c/acus2009/

I'll be hosting a Maven training session on November 2 (http://www.us.apachecon.com/c/acus2009/sessions/379
). In it, I use Archiva and Continuum to illustrate one way of
applying repository management and continuous builds in a Maven-based
infrastructure. Rich Bowen from Feathercast has just released an
interview we did discussing it last week for more info: http://feathercast.org/?p=84

Last year we also had a "Maven and artifact repositories" meetup on
one of the nights. I'm hoping we can organise another similar session
- is there anyone attending that would be interested?

For the main program, this year it is in tracks:

* HTTPd
* Tomcat
* Business & Community
* Lucene
* Felix & OSGi
* Tuscany & Synapse
* Content Technologies (Jackrabbit, and various web frameworks)
* Web Services
* Geronimo & Directory
* Hadoop

Of course there's also the BarCamp and Hackathon for opportunities to
meet up and talk about anything else.

Cheers,
Brett

Re: Corrupt Source Zip?

2009-09-29T19:57:05Z

Yes, it seems there was a problem. We are currently reapproving the
sources for distribution (please refer to dev@...).

- Brett

On 26/09/2009, at 8:36 PM, Robert Morse wrote:

> I've tried to unzip the 1.2.2 source from several sites, and
> consistently get:
>
> Archive: apache-archiva-1.2.2-src.zip
> End-of-central-directory signature not found. Either this file is
> not
> a zipfile, or it constitutes one disk of a multi-part archive. In
> the
> latter case the central directory and zipfile comment will be found
> on
> the last disk(s) of this archive.
> unzip: cannot find zipfile directory in one of apache-archiva-1.2.2-
> src.zip or
> apache-archiva-1.2.2-src.zip.zip, and cannot find apache-
> archiva-1.2.2-src.zip.ZIP, period.
>
> Just thought I'd pass this along.
>
> Mac OSX 10.6
>
> The human mind is an iterative processor, it never does anything
> right the first time. What it does well is to make improvements on
> every iteration (deMarco)
>
>
>

Corrupt Source Zip?

2009-09-26T03:36:17Z

I've tried to unzip the 1.2.2 source from several sites, and
consistently get:

Archive: apache-archiva-1.2.2-src.zip
End-of-central-directory signature not found. Either this file is
not
a zipfile, or it constitutes one disk of a multi-part archive. In
the
latter case the central directory and zipfile comment will be found
on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of apache-archiva-1.2.2-
src.zip or
apache-archiva-1.2.2-src.zip.zip, and cannot find apache-
archiva-1.2.2-src.zip.ZIP, period.

Just thought I'd pass this along.

Mac OSX 10.6

The human mind is an iterative processor, it never does anything right
the first time. What it does well is to make improvements on every
iteration (deMarco)

Re: Archiva 1.2.2 and JBoss 5.1

2009-09-24T08:03:49Z

Hello Deng,
Thanks for the reply. I've tried it with prior versions, but not
1.2.2. Just tried to get the source from a variety of mirrors, and
it appears the source zip file may be corrupt since I can't get it to
decompress.

Once I manage to get it, I'll try working through it, and if
successful, post the steps.

Thanks.

On Sep 22, 2009, at 8:21 PM, Deng Ching wrote:

> Did you try the steps specified in
> http://cwiki.apache.org/confluence/display/ARCHIVA/Archiva+on
> +JBoss ? It's
> for JBoss 4.2.x but it might be worth a try for 5.1.0 as well..
>
> Thanks,
> Deng
>
> On Tue, Sep 22, 2009 at 7:47 PM, Robert Morse <rmorse@...>
> wrote:
>
>> Has anyone successfully deployed Archiva 1.2.2 (or any version for
>> that
>> matter) on JBoss 5.1.0.GA?
>> If so, I'd appreciate learning how it's done. Thanks.
>>
>> The human mind is an iterative processor, it never does anything
>> right the
>> first time. What it does well is to make improvements on every
>> iteration
>> (deMarco)
>>
>>
>>
>>

The human mind is an iterative processor, it never does anything right
the first time. What it does well is to make improvements on every
iteration (deMarco)

Re: Archiva 1.2.2 and JBoss 5.1

2009-09-22T19:21:22Z

Did you try the steps specified in
http://cwiki.apache.org/confluence/display/ARCHIVA/Archiva+on+JBoss ? It's
for JBoss 4.2.x but it might be worth a try for 5.1.0 as well..

Thanks,
Deng

On Tue, Sep 22, 2009 at 7:47 PM, Robert Morse <rmorse@...> wrote:

> Has anyone successfully deployed Archiva 1.2.2 (or any version for that
> matter) on JBoss 5.1.0.GA?
> If so, I'd appreciate learning how it's done. Thanks.
>
> The human mind is an iterative processor, it never does anything right the
> first time. What it does well is to make improvements on every iteration
> (deMarco)
>
>
>
>

[ANN] New book - Apache Maven 2: Effective Implementation

2009-09-22T05:52:49Z

The final release of "Apache Maven 2: Effective Implementation" is now
available online! It is available in both eBook and printed + eBook
versions, and is written by Deng Ching and myself with help from our
reviewers Wendy Smoak, Emmanuel Venisse, and Carsten Ziegler.

http://www.packtpub.com/apache-maven-2-effective-implementations/book
http://www.amazon.com/Apache-Maven-2-Effective-Implementation/dp/1847194540/

In this book, we wanted to focus on “best practices” and tying
everything together in a way that shows how Maven was meant to be
used. It works through a reasonably useful example application from
scratch, up to an assembly, building it in CI, deploying it to the
repository, and releasing it.

The book includes:
Chapter 1: Maven in a Nutshell
Chapter 2: Staying in Control with Archiva
Chapter 3: Building an Application Using Maven
Chapter 4: Application Testing with Maven
Chapter 5: Reporting and Checks
Chapter 6: Useful Maven Plugins
Chapter 7: Maven Best Practices
Chapter 8: Continuum: Ensuring the Health of your Source Code
Chapter 9: Continuum in Depth
Chapter 10: Archiva in a Team
Chapter 11: Archetypes
Chapter 12: Maven, Archiva, and Continuum in the Enterprise
Appendix A: Troubleshooting Maven
Appendix B: Recent Maven Features
Appendix C: Migrating Archiva and Continuum Data

Full contents: http://www.packtpub.com/article/apache-maven-2-effective-implementations-table-of-contents

"Chapter 6: Useful Maven Plugins" is available now as a sample from
the book site.

Cheers,
Brett

Archiva 1.2.2 and JBoss 5.1

2009-09-22T04:47:30Z

Has anyone successfully deployed Archiva 1.2.2 (or any version for
that matter) on JBoss 5.1.0.GA?
If so, I'd appreciate learning how it's done. Thanks.

The human mind is an iterative processor, it never does anything right
the first time. What it does well is to make improvements on every
iteration (deMarco)

Re: Archiva 1.2.1 - repos won't get index

2009-09-17T19:28:31Z

Perhaps you could use Luke to inspect the Lucene index and see whether
that helps identify the issue by looking at what data has been
successfully recorded?

On 17/09/2009, at 1:19 AM, Marc Lustig wrote:

>
> Hi,
> I gave this another try by doing the following steps.
>
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
>
> When we search now for e.g. xmlbeans, we do get a few jar-artifacts
> that
> contain a package-name "xmlbeans". But we do not get the artifact
> whose name
> is xmlbeans.
>
> I have no idea what else to try to make the search-function to work
> again.
> User's here are pretty annoyed about it.
>
> Any suggestion what to do except filing a jira issue?
>
>
>
>
>
> Deng Ching-2 wrote:
>>
>> On Thu, Jun 25, 2009 at 7:26 PM, Marc Lustig <ml@...>
>> wrote:
>>
>>>
>>> On our side, the story is continuing like this.
>>> In the afternoon, I touch the whole repo and let the scan running
>>> and
>>> re-create the database.
>>> After that, it seems like all (physically) existing artifacts can be
>>> found
>>> on the Web-UI. Fine.
>>> The next morning again hundreds of artifacts are disappeared from
>>> the
>>> Web-UI
>>> (but still existing physically). It's so annoying...
>>> I checked the last couple of scans in the log and cannot find
>>> exceptions
>>> for
>>> that Repo concerned.
>>> (However I didn't check all the scans since yesterday afternoon.)
>>
>>
>>>
>>> Anyway, for some reason, some consumer is removing certain
>>> artifacts (or
>>> whole groupId's) from the index. I have no clue why.
>>>
>>> Any suggestion what to do to prevent the removal of artifacts from
>>> the
>>> index-database?
>>>
>>> If we disable the "update-db-artifact" consumer, what undesired
>>> side-effects
>>> may this have?
>>>
>>>
>> Your artifacts won't show up in the webapp browse as this consumer
>> adds
>> the
>> basic artifact info in the db and that's where the artifacts shown
>> in the
>> Browse page is gathered..
>>
>> You can try disabling these consumers in Database page as they are
>> the
>> ones
>> doing the cleanup work, but afaik they only clean up the db and
>> index for
>> artifacts that are no longer in the filesystem:
>> not-present-remove-db-artifact
>> not-present-remove-db-project
>> not-present-remove-indexed
>>
>> If the problem still persists, do you mind filing an issue for this
>> in
>> jira?
>> :)
>>
>> Thanks,
>> Deng
>>
>>
>>>
>>> Marc Lustig wrote:
>>>>
>>>> Indeed,
>>>> find [REPOSITORY_DIRECTORY_NAME] | xargs touch
>>>> is tremendously faster than
>>>> find [REPOSITORY_DIRECTORY_NAME] -exec touch {} \;
>>>>
>>>>
>>>>
>>>>
>>>> Deng Ching-2 wrote:
>>>>>
>>>>> Hi Marc,
>>>>>
>>>>> Did you touch the contents of the repository? The last modified
>>>>> date
>>> of
>>>>> the
>>>>> artifacts need to be more recent than the last run of the
>>>>> repository
>>>>> scan.
>>>>> You can execute *find [REPOSITORY_DIRECTORY_NAME] | xargs touch
>>>>> *at
>>> the
>>>>> base
>>>>> dir where your repo is located.
>>>>>
>>>>> Thanks,
>>>>> Deng
>>>>>
>>>>> On Wed, Jun 3, 2009 at 11:54 PM, Marc Lustig <ml@...>
>>> wrote:
>>>>>
>>>>>>
>>>>>> I forgot to add an excerpt from the log:
>>>>>>
>>>>>> 2009-06-03 17:42:11,554 [pool-2-thread-1] INFO
>>>>>>
>>>>>>
>>> org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor
>>>>>> - Finished repository task:
>>>>>> .\ Scan of internal \.__________________________________________
>>>>>> Repository Dir : /opt/managed_repos/internal
>>>>>> Repository Name : ....
>>>>>> Repository Layout : default
>>>>>> Known Consumers : (7 configured)
>>>>>> auto-rename
>>>>>> metadata-updater
>>>>>> repository-purge
>>>>>> auto-remove
>>>>>> update-db-artifact
>>>>>> create-missing-checksums
>>>>>> index-content
>>>>>> Invalid Consumers : <none>
>>>>>> Duration : 1 Minute 13 Seconds 689 Milliseconds
>>>>>> When Gathered : 6/3/09 5:42 PM
>>>>>> Total File Count : 107263
>>>>>> Avg Time Per File :
>>>>>> ______________________________________________________________
>>>>>> 2009-06-03 17:42:55,317 [pool-1-thread-1] INFO
>>>>>>
>>>>>>
>>> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor
>>>>>> - Executing task from queue with job name:
>>> database-job:user-requested
>>>>>> 2009-06-03 17:42:55,319 [pool-1-thread-1] INFO
>>>>>>
>>>>>>
>>> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor
>>>>>> - Task: Updating unprocessed artifacts
>>>>>> 2009-06-03 17:42:55,318 [http-8080-6] INFO
>>>>>> org.apache.maven.archiva.web.action.admin.SchedulerAction -
>>>>>> [ActionMessage]
>>>>>> Your request to update the database has been queued.
>>>>>> 2009-06-03 17:42:55,591 [pool-1-thread-1] INFO
>>>>>>
>>>>>>
>>> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor
>>>>>> - Task: Updating processed artifacts
>>>>>> 2009-06-03 17:44:20,355 [pool-1-thread-1] INFO
>>>>>>
>>>>>>
>>> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor
>>>>>> - Finished database task in 85035ms.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Marc Lustig wrote:
>>>>>>>
>>>>>>> We upgraded our test-server to release 1.2.1, removed .index and
>>>>>> .indexer
>>>>>>> from all the repos, ran the Scan for the repos and then the
>>>>>>> Update
>>>>>>> Database.
>>>>>>>
>>>>>>> As a result, before the upgrade we had 500 MB inside in all of
>>>>>>> the
>>>>>> .index
>>>>>>> directories.
>>>>>>> After the upgrade and the repo-scan, the total size is less
>>>>>>> than 1
>>>>>> MB.
>>>>>>> Apparently the repo indexing-process does not work anymore. The
>>>>>>> Search-function does not give any results.
>>>>>>>
>>>>>>> Any idea how to make the repos to get indexed again?
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>>
>>> http://www.nabble.com/Archiva-1.2.1---repos-won%27t-get-index-tp23854158p23854203.html
>>>>>> Sent from the archiva-users mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Archiva-1.2.1---repos-won%27t-get-index-tp23854158p24201482.html
>>> Sent from the archiva-users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Archiva-1.2.1---repos-won%27t-get-index-tp23854158p25474649.html
> Sent from the archiva-users mailing list archive at Nabble.com.
>

Re: browse to artifact directory doesn't work

2009-09-17T03:18:56Z

Hi Julian,

Looks like a similar problem to:

http://jira.codehaus.org/browse/MRM-1176

You would need to re-create the database as indicated in
http://jira.codehaus.org/browse/MRM-1157 (related issue) to workaround this.

You need to follow these steps to re-create it:
1. Stop Archiva
2. Delete the index directory of the repository (don't forget to delete the
.index dir at the root of the repository directory)
3. Execute *find [REPOSITORY_DIRECTORY_NAME] | xargs touch* at the base
directory where the repository resides
4. Start Archiva

The repositories will be scanned during startup.

Thanks,
Deng

On Thu, Sep 17, 2009 at 2:21 AM, Julian Dunn <Julian.Dunn@...> wrote:

> We're using Archiva 1.2 and can't browse to any artifacts. When I try
> this, I get the following (example URL:
> http://archiva.nm.cbc.ca/archiva/browse/asm/asm-tree/2.2.1)
>
> HTTP Status 500 -
>
> type Exception report
>
> message
>
> description The server encountered an internal error () that prevented
> it from fulfilling this request.
>
> exception
>
> javax.servlet.ServletException: Error in JDO during get of Database
> object id [asm:asm-tree:2.2.1] of type
> org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-group
>
> org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:515)
>
> org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:419)
>
> com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
>
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
>
> org.apache.struts2.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:99)
>
>
> The Archiva database is on PostgreSQL.
>
> Can someone help?
>
> - Julian
>

browse to artifact directory doesn't work

2009-09-16T11:21:18Z

We're using Archiva 1.2 and can't browse to any artifacts. When I try
this, I get the following (example URL:
http://archiva.nm.cbc.ca/archiva/browse/asm/asm-tree/2.2.1)

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented
it from fulfilling this request.

exception

javax.servlet.ServletException: Error in JDO during get of Database
object id [asm:asm-tree:2.2.1] of type
org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-group
org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:515)
org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:419)
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
org.apache.struts2.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:99)

The Archiva database is on PostgreSQL.

Can someone help?

- Julian

Re: Archiva 1.2.1 - repos won't get index

2009-09-16T08:19:17Z

Hi,
I gave this another try by doing the following steps.

1. deleting repo/.index and repo/.indexer
2. touching all files and dirs in repo recursively
3. running the repo scan

When we search now for e.g. xmlbeans, we do get a few jar-artifacts that contain a package-name "xmlbeans". But we do not get the artifact whose name is xmlbeans.

I have no idea what else to try to make the search-function to work again.
User's here are pretty annoyed about it.

Any suggestion what to do except filing a jira issue?

Deng Ching-2 wrote:

On Thu, Jun 25, 2009 at 7:26 PM, Marc Lustig <ml@marclustig.com> wrote:

>
> On our side, the story is continuing like this.
> In the afternoon, I touch the whole repo and let the scan running and
> re-create the database.
> After that, it seems like all (physically) existing artifacts can be found
> on the Web-UI. Fine.
> The next morning again hundreds of artifacts are disappeared from the
> Web-UI
> (but still existing physically). It's so annoying...
> I checked the last couple of scans in the log and cannot find exceptions
> for
> that Repo concerned.
> (However I didn't check all the scans since yesterday afternoon.)

>
> Anyway, for some reason, some consumer is removing certain artifacts (or
> whole groupId's) from the index. I have no clue why.
>
> Any suggestion what to do to prevent the removal of artifacts from the
> index-database?
>
> If we disable the "update-db-artifact" consumer, what undesired
> side-effects
> may this have?
>
>
Your artifacts won't show up in the webapp browse as this consumer adds the
basic artifact info in the db and that's where the artifacts shown in the
Browse page is gathered..

You can try disabling these consumers in Database page as they are the ones
doing the cleanup work, but afaik they only clean up the db and index for
artifacts that are no longer in the filesystem:
not-present-remove-db-artifact
not-present-remove-db-project
not-present-remove-indexed

If the problem still persists, do you mind filing an issue for this in jira?
:)

Thanks,
Deng

>
> Marc Lustig wrote:
> >
> > Indeed,
> > find [REPOSITORY_DIRECTORY_NAME] | xargs touch
> > is tremendously faster than
> > find [REPOSITORY_DIRECTORY_NAME] -exec touch {} \;
> >
> >
> >
> >
> > Deng Ching-2 wrote:
> >>
> >> Hi Marc,
> >>
> >> Did you touch the contents of the repository? The last modified date of
> >> the
> >> artifacts need to be more recent than the last run of the repository
> >> scan.
> >> You can execute *find [REPOSITORY_DIRECTORY_NAME] | xargs touch *at the
> >> base
> >> dir where your repo is located.
> >>
> >> Thanks,
> >> Deng
> >>
> >> On Wed, Jun 3, 2009 at 11:54 PM, Marc Lustig <ml@marclustig.com> wrote:
> >>
> >>>
> >>> I forgot to add an excerpt from the log:
> >>>
> >>> 2009-06-03 17:42:11,554 [pool-2-thread-1] INFO
> >>>
> >>>
> org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor
> >>> - Finished repository task:
> >>> .\ Scan of internal \.__________________________________________
> >>> Repository Dir : /opt/managed_repos/internal
> >>> Repository Name : ....
> >>> Repository Layout : default
> >>> Known Consumers : (7 configured)
> >>> auto-rename
> >>> metadata-updater
> >>> repository-purge
> >>> auto-remove
> >>> update-db-artifact
> >>> create-missing-checksums
> >>> index-content
> >>> Invalid Consumers : <none>
> >>> Duration : 1 Minute 13 Seconds 689 Milliseconds
> >>> When Gathered : 6/3/09 5:42 PM
> >>> Total File Count : 107263
> >>> Avg Time Per File :
> >>> ______________________________________________________________
> >>> 2009-06-03 17:42:55,317 [pool-1-thread-1] INFO
> >>>
> >>>
> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor
> >>> - Executing task from queue with job name: database-job:user-requested
> >>> 2009-06-03 17:42:55,319 [pool-1-thread-1] INFO
> >>>
> >>>
> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor
> >>> - Task: Updating unprocessed artifacts
> >>> 2009-06-03 17:42:55,318 [http-8080-6] INFO
> >>> org.apache.maven.archiva.web.action.admin.SchedulerAction -
> >>> [ActionMessage]
> >>> Your request to update the database has been queued.
> >>> 2009-06-03 17:42:55,591 [pool-1-thread-1] INFO
> >>>
> >>>
> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor
> >>> - Task: Updating processed artifacts
> >>> 2009-06-03 17:44:20,355 [pool-1-thread-1] INFO
> >>>
> >>>
> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor
> >>> - Finished database task in 85035ms.
> >>>
> >>>
> >>>
> >>> Marc Lustig wrote:
> >>> >
> >>> > We upgraded our test-server to release 1.2.1, removed .index and
> >>> .indexer
> >>> > from all the repos, ran the Scan for the repos and then the Update
> >>> > Database.
> >>> >
> >>> > As a result, before the upgrade we had 500 MB inside in all of the
> >>> .index
> >>> > directories.
> >>> > After the upgrade and the repo-scan, the total size is less than 1
> >>> MB.
> >>> > Apparently the repo indexing-process does not work anymore. The
> >>> > Search-function does not give any results.
> >>> >
> >>> > Any idea how to make the repos to get indexed again?
> >>> >
> >>>
> >>> --
> >>> View this message in context:
> >>>
> http://www.nabble.com/Archiva-1.2.1---repos-won%27t-get-index-tp23854158p23854203.html
> >>> Sent from the archiva-users mailing list archive at Nabble.com.
> >>>
> >>>
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Archiva-1.2.1---repos-won%27t-get-index-tp23854158p24201482.html
> Sent from the archiva-users mailing list archive at Nabble.com.
>
>

Re: How to Release Snapshot artifacts in 1.2.2

2009-09-15T14:31:41Z

On Tue, Sep 15, 2009 at 6:01 AM, Soumen Trivedi
<soumen.trivedi@...> wrote:
> Thanks for replying back Wendy. Yes I want to release application specific
> contents into Archiva as RELEASE and not as SNAPSHOT before it is actually
> sent to production env. Do you reckon using Maven for this purpose? I
> apologies for this question, I was thinking that we upload artifacts into
> Archiva as SNAPSHOT and then Archiva helps to move those into RELEASE stage.

This is probably best discussed on the Maven users list, but snapshots
are just a point in time. They may depend on other snapshots, they
have no associated tag in the scm repo, and generally are not
reproducible, so you wouldn't want to take one and promote it to
release status.

If you check JIRA you may find a feature request for staging and
promoting _releases_ but that implies that you have done an official
release first.

--
Wendy

Re: How to Release Snapshot artifacts in 1.2.2

2009-09-15T06:01:32Z

Thanks for replying back Wendy. Yes I want to release application specific
contents into Archiva as RELEASE and not as SNAPSHOT before it is actually
sent to production env. Do you reckon using Maven for this purpose? I
apologies for this question, I was thinking that we upload artifacts into
Archiva as SNAPSHOT and then Archiva helps to move those into RELEASE stage.

On Mon, Sep 14, 2009 at 7:55 PM, Wendy Smoak <wsmoak@...> wrote:

> On Mon, Sep 14, 2009 at 11:04 AM, Soumen Trivedi
> <soumen.trivedi@...> wrote:
>
> > 1. How to move SNAPSHOT artifacts to RELEASE stage in Archiva
>
> That you have SNAPSHOT artifacts in the repository implies that you're
> using Maven to build your project.
>
> If so, you can use the Maven Release plugin to automate the process of
> creating a tag and building a released version of your project.
>
> I'm not sure what you meant in (2) about project specific jars and the
> website, can you re-state the question?
>
> > 3. What steps should be followed to stage the release? I have a
> Application
> > Server on which Archiva runs and want to stage the releases in the same
> > server along with the /data/repositories directory? Can this be possible?
>
> It sounds like you want to deploy your released application. There's
> nothing in Archiva to help with that, but there are other ways to
> automate it. If you are using Maven there might be a plugin for your
> app server, or you might take a look at the Cargo project.
>
> --
> Wendy
>

--
Thanks & Regards,
Soumen Trivedi
+44 (0) 751 544 6779
Email: Soumen.Trivedi@...

Re: How to Release Snapshot artifacts in 1.2.2

2009-09-14T11:55:44Z

On Mon, Sep 14, 2009 at 11:04 AM, Soumen Trivedi
<soumen.trivedi@...> wrote:

> 1. How to move SNAPSHOT artifacts to RELEASE stage in Archiva

That you have SNAPSHOT artifacts in the repository implies that you're
using Maven to build your project.

If so, you can use the Maven Release plugin to automate the process of
creating a tag and building a released version of your project.

I'm not sure what you meant in (2) about project specific jars and the
website, can you re-state the question?

> 3. What steps should be followed to stage the release? I have a Application
> Server on which Archiva runs and want to stage the releases in the same
> server along with the /data/repositories directory? Can this be possible?

It sounds like you want to deploy your released application. There's
nothing in Archiva to help with that, but there are other ways to
automate it. If you are using Maven there might be a plugin for your
app server, or you might take a look at the Cargo project.

--
Wendy

How to Release Snapshot artifacts in 1.2.2

2009-09-14T11:04:44Z

Hi all,
I am using Archiva ver 1.2.2 & Maven for development and have the following
queries:

1. How to move SNAPSHOT artifacts to RELEASE stage in Archiva
2. The SNAPSHOT jars is project specific and not upon apache, should it
still be staged on the
http://people.apache.org/repo/m2-snapshot-repository/website?
3. What steps should be followed to stage the release? I have a Application
Server on which Archiva runs and want to stage the releases in the same
server along with the /data/repositories directory? Can this be possible?

Any answers or pointers to the above queries will be very helpful.

Please feel free to ask questions to me if you feel what I described above
does not make any sense to you? I am new to Archiva and trying to understand
& implement the process involved Archiva administration and release
activity.

--
Thanks & Regards,
Soumen Trivedi
Email: Soumen.Trivedi@...

UsedBy isn't accurate

2009-09-14T08:21:32Z

Hi,

Using Archiva 1.1.3 (Tomcat war/derby install)

Artifacts aren't reported in the UsedBy tab. It appears that the list isn't complete - there are artifacts that depend on others, but they aren't visible on the appropriate UsedBy pages. Strangely, once we've navigated to the page for an artifact known to depend on another, it then starts appearing.

Based on what little information I have, it appears that the Archiva database isn't being kept up-to-date with the artifacts residing in the repository.

Some additional information:
* I checked that the poms were not listed as problems in the repository report section.
* Artifacts are deployed directly to the filesystem via the CI server, we do not deploy through Archiva's DAV interface.

In a quick JIRA search, I am seeing things like:

http://jira.codehaus.org/browse/MRM-952
http://jira.codehaus.org/browse/MRM-1061

Has anyone encountered this problem? Is it fixed in a newer version of Archiva? I don't want to disrupt things with an upgrade if it isn't going to help.

Thanks,

Brent Atkinson
batkinson@...

RE: making sure archiva goes exactly where you want it to

2009-09-11T03:46:28Z

Thanks for the tips - I'll try to get that going soon.

Why do we have codehaus repositories? Is everything synced (sonar, glassfish, etc)?

I thought we used the snapshots as well, but i'm disconnected from the VPN atm so I can't check.

-----Original Message-----
From: Brett Porter on behalf of Brett Porter
Sent: Thu 9/10/2009 9:53 PM
To: users@...
Subject: Re: making sure archiva goes exactly where you want it to

I'm not sure why you have codehaus listed, since they are all synced
to central - or do you not proxy central? Or are you using the
snapshots repo?

Anyway, in this scenario I would white list org/codehaus/** (and any
other GIDs you ned from there) on Codehaus' proxy connector so it only
uses that flaky link when a new version of something from there. Make
sure you set releases to "once" and snapshots to "never" so that it
doesn't go out looking for metadata unnecessarily (or vice versa if
you are configuring the codehaus snapshots repository).

That will limit it to requests for codehaus artifacts - there's not
much more you can do if those connections are not good other use the
connector disable button when it is particularly bad.

- Brett

On 09/09/2009, at 11:42 PM, EJ Ciramella wrote:

> How many repositories do you have mapped?
>
> We have four internal ones:
>
> "bertha" - for our release and project branches
> "snapshot" - unused for now, but will house, you guessed it, snapshots
> "test" - for testing deployments
> "thirdparty" - (proxy) for storing all thirdparty artifacts we need to
> install
>
> And maybe 6 - 8 remote repositories that feed "thirdparty"
>
> Regularly, the codehaus ones get flaky and even tho we've set 2 second
> timeouts, each third party artifact has to time out. That's pretty
> horrendous when a few projects have 20 DIRECT dependencies let alone
> hundreds of transitive ones.
>
> Does this paint a better picture? I don't feel like the black/white
> lists are what we need, especially when we have 100% of the artifacts
> the build is looking for already in "thirdparty". Is there a better
> way
> to do this? What we've been doing is when a remote repository gets
> wonky, we'll remove it and let the artifacts get served from our local
> stash, but that stinks if someone is actively adding new features to a
> module and requires new/different dependnencies to be looked up and
> downloaded.
>
> How do people normally accomplish this kinda thing?
>
> -----Original Message-----
> From: Brett Porter [mailto:brett@...] On Behalf Of Brett
> Porter
> Sent: Tuesday, September 08, 2009 7:57 PM
> To: users@...
> Subject: Re: making sure archiva goes exactly where you want it to
>
>
> On 08/09/2009, at 10:33 PM, EJ Ciramella wrote:
>
>> So that's kind of a pain, no? Having to list things that should be
>> coming from the codehaus repository in all the blacklists of every
>> other repository?
>>
>> Is this truly the only way to do this?
>
> I see you're point and personally I'd rather all these rules were in a
> central location.
>
> The best approach to the current situation is to use whitelists on
> every
> repository (in which case blacklists for those not in that list are
> not
> necessary). Only on repositories such as central where you generally
> want everything except corporate artifacts do I use a blacklist
> typically.
>
> - Brett