In one of my projects, we started with Github packages. After a while
and having a lot of projects and various organisations, it turned out to
be very complicated to manage all these different repositories in the
setting.xml files of the developers. So, it was hard to stay on the top
of the things.
Now we are using Artifactory. For a larger, feel free to define the term
large, it is the better approach. But as always, it depends on your
project, the number of people working with you and your own approach. It
is easy to start with it, but... ;-)
Oliver
Am 27.07.21 um 15:21 schrieb Stephen Coy:
Hi all,
Just wondering if anyone has any thoughts on using GitHub Packages as a company
repo vs Nexus.
Right now we (about 30-40 devs) are using an ageing version of Sonatype Nexus
for onsite builds and S3 for “cloud” based builds (a process inherited from
using Spring Boot).
Now there is a push for us to migrate everything to GitHub Packages.
Personally, I would just run up a Nexus OSS instance in an EC2 instance and use
that.
There does not seem to be much discussion about this around.
What is everyone else doing right now?
Cheers,
Steve C
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
