Re: Binaries distributable for Archiva 2.2.4

[Martin Stockhammer]

Hi,

will be published in the next days.
But it's only a bugfix release. No new features.

Regards

Martin

Am 29. April 2019 21:25:33 MESZ schrieb "Mirabito, Massimo (Max) 
(CDC/DDID/NCHHSTP/OD) (CTR)" :
>Dear All,
>
>We are running Archiva V2.2.3  on Windows. I just noticed that there is
>a 2.2.4 branch on github does anyone know when binaries will be
>available?
>
>Thanks in advance
>max

-- 
This message was sent from mobile phone.

Re: Interested in a Docker Image & Kubernetes Chart?

[Martin Stockhammer]

Hi Terence,

great! Start with small contributions to get an understanding how the process 
works. For getting bigger changes into the project the dev mailing list is the 
best place to start discussing about the details.

Regards

Martin

Am 22. Oktober 2018 21:34:24 MESZ schrieb Terence Kent :
>Martin,
>
>Sounds good! I've got to pickup another project, but as soon as I have
>some
>time I'll pickup the Archiva source and take a look at where the docker
>image would fit. To be honest, I probably should have just done that to
>begin with. There are a few minor things I've been wanting to
>change/fix in
>there for years, I've just been avoiding the effort of getting familiar
>with the project source :-). If I just bite the bullet get familiar
>with
>the source, I can send over a few different pull requests.
>
>Best,
>Terence
>
>
>
>
>
>On Sat, Oct 20, 2018 at 12:13 AM Martin  wrote:
>
>> Hi Terence,
>>
>> thank you for help.
>> As you already know, resources are very limited in this project. So,
>I
>> have to focus on the things that are manageable.
>> Code contribution is very appreciated, so if you have any changes you
>like
>> to get into the project, feel free to create pull
>> requests. If you like, you can even add the complete
>docker/kubernetes
>> part as pull request.
>> If you have any questions, don't hesitate to ask.
>>
>> Regards
>>
>> Martin
>>
>>
>> Am Samstag, 20. Oktober 2018, 01:30:41 CEST schrieb Terence Kent:
>> > Hey Martin,
>> >
>> > Feel free to add a link to our image and chart on the Archiva
>webpage.
>> > Also, I threw together a v2-snapshot
>> > 
>> branch/tag
>> > of the image that is built using the most recent 2.2.4 snapshot.
>All of
>> our
>> > image tests pass using the current 2.2.4-SNAPSHOT build, as you
>would
>> > expect.
>> >
>> > Looking ahead, whenever you dust off this project to finish out
>2.2.4 or
>> > jump to version 3, I'd really like to see a docker image brought
>into the
>> > project directly. Maintaining the image code separately from the
>project
>> > isn't the greatest idea and since you already have a docker image
>for
>> > testing, I'm sure it's something you've considered. If we're
>available
>> the
>> > next time there's some focus on this project, we'll see if we can
>help
>> out
>> > with that part. We've learned several lessons about running Archiva
>in a
>> > container over the past few years and we'd love to make some small
>> changes
>> > in the source project to make life easier :-).
>> >
>> > Oh, and it'd sure be nice to have an official Kubernetes helm chart
>once
>> > there is an offical docker image. I'm confident that a lot more
>people
>> > would use Archiva if was available there.
>> >
>> > Best,
>> > Terence
>> >
>> > On Fri, Oct 19, 2018 at 12:31 PM Martin 
>wrote:
>> >
>> > > Hi Terence,
>> > >
>> > > thank you for the information. Great work and great to hear, that
>you
>> > > decided to keep archiva, despite the
>> > > slow development.
>> > > I would like to add the link to our archiva web page if you don't
>mind.
>> > > We are using docker images for our integration tests on the
>jenkins
>> > > server, but without kubernetes, maybe I
>> > > can find some configuration on your project that may be useful
>for
>> these.
>> > >
>> > > Our current snapshot version for the stable 2.2 release branch
>> > > (2.2.4-SNAPSHOT) contains some fixes and
>> > > there are not very much changes compared to the 2.2.3 version, so
>I
>> would
>> > > consider it as stable.
>> > > If you like, you can use a current snapshot version in your
>docker
>> image
>> > > or provide an option for using it.
>> > > The zip files can be found at:
>> > >
>> > >
>>
>https://archiva-repository.apache.org/archiva/repository/snapshots/org/apache/archiva/archiva-jetty/2.2.4-SNAPSHOT/
>> > > But it's still a snapshot version so, if there is development
>going
>> on, it
>> > > may be broken every now and then, so it may be not a
>> > > good idea, if the file is downloaded dynamically during container
>> > > start/build.
>> > >
>> > > Regards
>> > >
>> > > Martin
>> > >
>> > > Am Freitag, 19. Oktober 2018, 02:08:52 CEST schrieb Terence Kent:
>> > > > Hello,
>> > > >
>> > > > In early 2015, we made our Archiva docker image public. It's
>had a
>> small
>> > > > following on github/dockerhub and we field questions on it from
>time
>> to
>> > > > time. As best we can tell, it's the de-facto docker image for
>> Archiva.
>> > > >
>> > > > We recently moved to Kubernetes and were faced with the
>decision of
>> > > > dropping the archiva image and moving to another repository
>manager,
>> or
>> > > > re-upping and modernizing the image. We chose to re-up and
>modernize
>> the
>> > > > image and we now have a "version 2" image with an companion
>helm
>> chart to
>> > > > make it easy to run in Kubernetes.
>> > > >
>> > > > I wanted to reach out to see if you had any interest in making
>our
>> image
>> > > > your official 

Re: deleting old snapshots

[Martin Stockhammer]

Hi Mathew,

sorry resources are very limited. 
To help sort this out, please use version 2.2.3. 
There are some tickets in jira about purging. Have you checked, if the 
snapshots are still in the filesystem? There is an issue about the index not 
updated for purged files.
Can you provide some logs?

Regards

Martin




Am 19. Oktober 2018 15:39:54 MESZ schrieb Matthew Broadhead 
:
>yes i have activated the "repository-purge" consumer under Repository 
>scanning -> Consumers.  maybe i also need to activate the 
>"validate-checksums" consumer as that is the only one not enabled
>
>in my snapshot repository i have the following values:
>Cron Expression  0 0,30 * * * ?
>Days Older  30
>Retention Count  2
>Delete Released Snapshots is checked
>
>i was going to upgrade to 2.2.3 but if yours is not working either then
>
>there is not much point
>
>i wonder if there is any way to trigger it from the command line?
>
>On 19/10/2018 13:52, Stefaan Dutry wrote:
>> According to my understanding it should be through the
>> repository-purge consumer. (This is located under Administration >
>> repository scanning > Consumers)
>>
>> Then on the repository configuration itself there are settings like
>> "Delete Released Snapshots" and "retention count" and "days older"
>>
>> Unfortunately the automatic purge isn't happening on our systems
>either.
>> (our version is 2.2.3)
>>
>> see:
>> http://archiva.apache.org/docs/2.2.0/adminguide/repositories.html
>> * delete released snapshots
>> * repository purge by days older
>> * repository purge by retention count
>> http://archiva.apache.org/docs/2.2.0/adminguide/consumers.html
>> * repository-purge
>>
>> But this is what's specified in the link you provided
>>
>> Regards,
>> Stefaan Dutry
>> Op vr 19 okt. 2018 om 13:37 schreef Jay Vyas :
>>> Hey Matt: some of us are definetly here.  Archiva saved me when I
>couldn’t pay for nexus so, I’d definetly say there are a few others in
>that boat.  Ufortubately nobody has responded yet.  Next step if
>necessary would be filing a JIrA issue on the Apache organization for
>archiva if nobody is able to help on the thread.
>>>
 On Oct 19, 2018, at 4:51 AM, Matthew Broadhead
> wrote:

 sorry to chase but is anyone still monitoring this list?  are we
>supposed to move to sonatype nexus oss?  i thought apache created
>maven?

> On 08/10/2018 20:00, Matthew Broadhead wrote:
> i am using 2.2.0 and i have looked through all the settings but i
>don't understand how to automatically delete old snapshots.
>
> i followed this
>https://stackoverflow.com/questions/12315461/how-to-configure-maven-or-apache-archiva-that-it-keeps-only-n-builds-of-an-snaps
>but it didn't work

-- 
This message was sent from mobile phone.

Re: help with upgrade -- CSRF / Redback / proxy

[Martin Stockhammer]

Hi,

it is mentioned in the release notes. But not clear enough, I think. I will 
improve the docs.

Greetings

Martin

Am 1. Juni 2017 05:02:14 MESZ schrieb Adam Brin :
>Martin,
>Thank you, that really helped.  It might be nice to identify some of
>this
>in the upgrade notes for 2.2.3, I definitely missed all of this when I
>went
>to try and figure out what was broken.
>
>- adam
>
>On Wed, May 31, 2017 at 1:15 PM, Martin  wrote:
>
>> Yes, thats the right place to configure it.
>>
>> redback properties have been moved to  archiva.xml
>> Inside the
>> 
>> 
>> ...
>> 
>> 
>> Element.
>>
>> This section is also changed, when you change the Redback Runtime
>> properties
>> by the WebUI:
>> http://archiva.apache.org/docs/2.2.3/adminguide/redback-
>> runtime-configuration.html#Runtime_properties
>>
>> But in this case editing via WebUI only works, if you have a browser
>behind
>> the reverse proxy. So you may want to edit the archiva.xml manually
>>
>> In your case this should be:
>> 
>> ...
>> 
>> ...
>>   
>> 
>>   false
>>   false
>>   
>> true
>>   
>> 
>> http://dev.server.com:9
>>   
>> ...
>> 
>> ...
>> 
>>
>> Info about configuration files can be found at:
>>
>http://archiva.apache.org/docs/2.2.3/adminguide/configuration-files.html
>>
>>
>> Greetings
>>
>> Martin
>>
>>
>> Am Mittwoch, 31. Mai 2017, 21:41:02 CEST schrieb Niranjan Babu Bommu:
>> > I had same problem when I upgarded archiva, issue was fixed by
>adding
>> > rest.baseUrl in archiva.xml and restart archiva
>> >
>> > 
>> > rest.baseUrl=.https://dev.server.com/archiva
>> >
>> >
>> > On Wed, May 31, 2017 at 2:35 PM, Adam Brin
>
>> >
>> > wrote:
>> > > Hi,
>> > >
>> > >  We proxy our archiva install behind nginx such that
>> > >
>> > > https://dev.server.com/archiva/ —> http://localhost:9/ . I’ve
>been
>> > > trying to read the documentation on how to update, but I’m
>afraid, I’m
>> a
>> > > bit lost.  A few questions:
>> > >
>> > > Where is the redback config stored, is it in
>> apps/archiva/WEB-INF/classes/
>> > > org/apache/archiva/redback-security.properties ?   If so, can
>this be
>> > > added to the doc, and also, moved into the conf/ directory? If
>not,
>> where
>> > > is it?
>> > > when I start archiva and go to the URL, I get the following
>warning…
>> > > Referer Header does not match: refererUrl=https://dev.server.
>> com/archiva/,
>> > > targetUrl=http://dev.tdar.org. Matches: Host=true, Port=false .
>But, I
>> > > don’t see how to fix the port issue according to the doc (
>> > > http://archiva.apache.org/redback/configuration.html#
>> > > REST_security_settings).
>> > >
>> > > help?
>> > >
>> > > thanks
>>
>>
>>
>
>
>-- 
>_
>Adam Brin
>Director of Technology, Digital Antiquity
>480.965.1278

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Re: Rebuilding the repository

[Martin Stockhammer]

Hi Marco,

a rescan (directories scanning action) does not help?


For 2: would be great if you can create a issue in the Jira. 

Greetings

Martin

Am 22. September 2016 17:13:55 MESZ, schrieb m...@mherrn.de:
>Hello,
>
>I see lots of problems in the archiva.log that the process cannot find
>some bundles:
>
>2016-09-22 17:08:02,435 [pool-6-thread-1] ERROR
>org.apache.jackrabbit.core.persistence.bundle.BundleFsPersistenceManager
>[] - failed to read bundle: b9706fc7-846b-4dab-bac3-7a734136dbf8:
>java.io.EOFException
>2016-09-22 17:08:02,477 [pool-6-thread-1] ERROR
>org.apache.jackrabbit.core.persistence.bundle.BundleFsPersistenceManager
>[] - failed to read bundle: b9706fc7-846b-4dab-bac3-7a734136dbf8:
>java.io.EOFException
>2016-09-22 17:08:02,528 [pool-6-thread-1] ERROR
>org.apache.jackrabbit.core.persistence.bundle.BundleFsPersistenceManager
>[] - failed to read bundle: b9706fc7-846b-4dab-bac3-7a734136dbf8:
>java.io.EOFException
>2016-09-22 17:08:02,549 [pool-6-thread-1] ERROR
>org.apache.jackrabbit.core.persistence.bundle.BundleFsPersistenceManager
>[] - failed to read bundle: 27c8fb7c-b9ef-4b6c-9b59-565d71f51ce5:
>java.io.EOFException
>
>
>I expect this happened because some files were removed directly in the
>filesystem.
>
>
>This leads to two questions:
>
>1. How can I recreate the whole repository from scratch? I tried
>configuring a different location in archiva.xml, but that lead to the
>same
>problems.
>
>2. How can archiva be made a bit more robust? Files or directories
>being
>deleted directly in the filesystem shouldn't confuse archiva that much
>that it doesn't really revive.
>
>Best regards
>Marco

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Re: Archiva to Attic? Asking contribution

[Martin Stockhammer]

Hi Olivier,

I like archiva, because it's simple and lightweight comparing to nexus and 
artifactory.
It has some advantages to the other two main repository implementations:
- You can deploy it on any application server (e.g. we use it on WebSphere)
- it does not claim to be a "multipurpose all providing" repository, it's only
 a simple maven repository with a basic set of permission roles
- it's completely open source

There are some issues that could/should be solved but I think it's ok, when 
there are no major changes the next time.
I'm willing to help (I have already sent some pull requests via github) and 
looking forward to suggestions what could be improved.

I must say, it was very easy to setup the build environment. The maven build 
and tests are working very well. And the code where I had to investigate some
issues was clear and understandable (great work!).

So if I can help, feel free to contact me. I'm subscribed to the mailing lists 
already.

Greetings

Martin


> Hi everyone,
> I'm a bit sad to say I don't have anymore a lot of time to contribute to
> the project.
> We have a very limited number of contributor.
> So we ask if you are interested to help/contribute to the project.
> Otherwise we will have to move the project to the Attic land [1]
> Let us know if you are interested!
> 
> 
> Cheers
> --
> Olivier Lamy on behalf of Apache Archiva PMC
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> 
> [1] http://attic.apache.org/