You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Eric Fetzer <er...@gmail.com> on 2022/03/01 20:49:52 UTC
Archiva Upgrade
Hi all! I'm upgrading archiva 2.2.4 to 2.2.7 for the log4j vulnerability.
I'm going from the document at:
https://archiva.apache.org/docs/2.2.7/adminguide/upgrade.html
This doc says that I should copy forward the data/repositories folder, but
I don't have that folder. My repositories folder is at the same level as
data. Data only has databases, jcr, and remotes in it.
Should I copy forward the repositories folder where it is now to the 2.7
version or put it under data there?
Thanks,
Eric
Re: Archiva Upgrade
Posted by Thad Humphries <th...@gmail.com>.
Eric,
I also have data and repositories on the same level. My install--and it's
been a while--is Stanalone following the instructions for "Separating the
base from the installation" (
https://archiva.apache.org/docs/2.2.7/adminguide/standalone.html). So
Archiva is installed at /opt/apache-archiva and the rest--what the link
above calls 'data'--is at /u3/archiva, containing:
$ ls -F /u3/archiva
conf/ data/ groups/ logs/ nohup.out repositories/ temp/
Does your setup look similar? So I think you can just update
/opt/apache-archiva. That's similar to how I install Tomcat--binaries one
place, config and apps in another.
On Tue, Mar 1, 2022 at 3:50 PM Eric Fetzer <er...@gmail.com> wrote:
> Hi all! I'm upgrading archiva 2.2.4 to 2.2.7 for the log4j vulnerability.
> I'm going from the document at:
>
> https://archiva.apache.org/docs/2.2.7/adminguide/upgrade.html
>
> This doc says that I should copy forward the data/repositories folder, but
> I don't have that folder. My repositories folder is at the same level as
> data. Data only has databases, jcr, and remotes in it.
>
> Should I copy forward the repositories folder where it is now to the 2.7
> version or put it under data there?
>
> Thanks,
> Eric
>
--
"Hell hath no limits, nor is circumscrib'd In one self-place; but where we
are is hell, And where hell is, there must we ever be" --Christopher
Marlowe, *Doctor Faustus* (v. 111-13)
RE: Archiva Upgrade
Posted by Jason Grammenos <ja...@agilitypr.com.INVALID>.
No the group still exists, but there is basically no activity. You may have to wait awhile for your question to get answered. I think you question is the first activity on the list in many months.
Jason Grammenos | Operations and Infrastructure Analyst
Pronouns: he/him
P: 613.232.7797 x1131
Toll-free: 866.545.3745 x1131
jason.grammenos@agilitypr.com
agilitypr.com
Learn new PR tips from our free resources.
-----Original Message-----
From: Eric Fetzer <er...@gmail.com>
Sent: March 3, 2022 12:53 PM
To: users@archiva.apache.org
Subject: Re: Archiva Upgrade
Is this user group no longer maintained?
On Tue, Mar 1, 2022 at 1:49 PM Eric Fetzer <er...@gmail.com> wrote:
> Hi all! I'm upgrading archiva 2.2.4 to 2.2.7 for the log4j
> vulnerability. I'm going from the document at:
>
> https://archiva.apache.org/docs/2.2.7/adminguide/upgrade.html
>
> This doc says that I should copy forward the data/repositories folder,
> but I don't have that folder. My repositories folder is at the same
> level as data. Data only has databases, jcr, and remotes in it.
>
> Should I copy forward the repositories folder where it is now to the
> 2.7 version or put it under data there?
>
> Thanks,
> Eric
>
Re: Archiva Upgrade
Posted by Eric Fetzer <er...@gmail.com>.
Is this user group no longer maintained?
On Tue, Mar 1, 2022 at 1:49 PM Eric Fetzer <er...@gmail.com> wrote:
> Hi all! I'm upgrading archiva 2.2.4 to 2.2.7 for the log4j
> vulnerability. I'm going from the document at:
>
> https://archiva.apache.org/docs/2.2.7/adminguide/upgrade.html
>
> This doc says that I should copy forward the data/repositories folder, but
> I don't have that folder. My repositories folder is at the same level as
> data. Data only has databases, jcr, and remotes in it.
>
> Should I copy forward the repositories folder where it is now to the 2.7
> version or put it under data there?
>
> Thanks,
> Eric
>