Hi Alexander, I was already aware of this method. However I am talking about a corporate repository to service 20+ developers.
Thanks for your input though, Steve C > On 29 Jul 2021, at 12:06 am, Alexander Kriegisch <alexan...@kriegisch.name> > wrote: > > An alternative to hosting your own Nexus, if you have a limited shared > hosting package (which is the case for my OSS projects or if I quickly > want to deploy a non-snapshot of a bugfix of any OSS package while > waiting for the upstream artifact to be released): > > It is quite easy to deploy directly to a WebDAV share (looks like a > local directory or mapped drive to Maven), if your web hosting provider > happens to offer WebDAV write access to your web storage space. Then you > can simply use any directory of your HTTP server as a makeshift Maven > repository. Maven deploys to there like it would to any Nexus, i.e. > complete with checksums. Of course that might be inappropriate for a > corporate setting, but for me it works. > > -- > Alexander Kriegisch > https://scrum-master.de > > > Mantas Gridinas schrieb am 28.07.2021 13:59 (GMT +07:00): > >> I'll second alexander. You also need to add credentials per repository >> that would host the package as well as that repository declaration >> into your pom declaration. In addition Dependabot cannot scan github >> packages hosts unless you give it the credentials as well. >> >> All in all, github packages would only work if you're working with >> monorepo, but at that point why even have a nexus other than to reduce >> build times. Even in that case I would still host my own nexus since >> it's less hair splitting and much simpler to setup and maintain. >> >> On Wed, Jul 28, 2021 at 9:51 AM Alexander Kriegisch >> <alexan...@kriegisch.name> wrote: >>> >>> It is possible to use GH Packages repos locally, if you configure Maven >>> correctly. But I found working with it a no-go, espacially for OSS >>> projects, because you do not only need credentials in order to deploy >>> artifacts, but also in order to *consume* them!!! This is a no-go, IMO. >>> Even if the repository is public, you need to provide all people trying >>> to access artifacts from GH Packages with credentials (access token). >>> This is why I stopped using it, for the most part. It is tedious, but OK >>> for artifacts only used from within a project or organisation, but there >>> is no public read-only access to GH Packages. Many users have been >>> complaining about it for a long time, but to no avail so far. >>> >>> -- >>> Alexander Kriegisch >>> https://scrum-master.de >>> >>> >>> Tommy Svensson schrieb am 27.07.2021 21:02 (GMT +07:00): >>> >>>> I played with GitHub packages thinking I could use it as a general binary >>> repo, >>>> but NO! It turned out that what is published on GitHub packages are only >>>> available from within GitHub! Anything built with GitHub CI can use GitHub >>>> packages. If you want to build locally you cannot access Github packages. >>>> At >>>> least I found no way to do so. >>>> >>>> I assume that GitHub packages are intended for GitHubs CI when there are >>>> dependencies between different GitHub repos, and I continue that assumption >>>> with that GH repos are only available within same account / organisation. >>>> >>>> I would be very happy to be wrong here! >>>> >>>> /Tommy >>>> >>>> >>>> Från: Stephen Coy <st...@resolvesw.com.au> >>>> Svara: Maven Users List <users@maven.apache.org> >>>> Datum: 27 juli 2021 at 15:22:52 >>>> Till: users@maven.apache.org <users@maven.apache.org> >>>> Ämne: OSS Nexus vs GitHub Packages >>>> >>>> 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 >>> >> >> >> -- >> // Mantas >> >> --------------------------------------------------------------------- >> 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
