Re: Local repository accessed by multiple Maven instances - how is it solved ?
Yes, these are good news! Am 04.10.21 um 15:10 schrieb Thomas Broyer: From JIRA links, this is apparently fixed by https://issues.apache.org/jira/browse/MRESOLVER-131, which means you need to deploy a Redis server. There apparently also is an Hazelcast-based version: https://maven.apache.org/resolver/maven-resolver-named-locks/index.html On Mon, Oct 4, 2021 at 2:32 PM Francois Marot wrote: Hello all, I would like clarifications on MNG-2802[*] that seems to be solved. If I understand correctly it solves the problem where multiple simultaneous Maven executions shared the same local repository. I have been keeping for years a bit of code in my Jenkinsfiles ensuring the local repos were accessed only by a single jenkins executor at the same time, so it seems like I can get rid of this doesn't it ? I'd like your input on this because reproducing the bug is difficult so I'd like to be sure before simplifying my Jenkinsfile. Moreover, does anyone know how this problem is solved technically ? Using files lock ? Can anybody explain ? Thanks you and thanks the Maven team for keeping up the good work at such pace ! François MAROT * https://issues.apache.org/jira/browse/MNG-2802 -- N Oliver B. Fischer A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany P +49 30 44793251 M +49 178 7903538 E o.b.fisc...@swe-blog.net S oliver.b.fischer J oliver.b.fisc...@jabber.org X http://xing.to/obf - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: OSS Nexus vs GitHub Packages
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
Re: Maven Enforcer Rule for Having annotation
If you are going to write such tests, you should also have a look at refelctions (http://code.google.com/p/reflections). It is pretty forward and very easy to use if you are looking for specific classes or annotations... Am 17.10.2011 13:34, schrieb Ansgar Konermann: You might want to consider PMD and Checkstyle. Another, simpler option is to write an integration test which iterates over your target directory and does some class filtering based on package name, then loads the desired classes using path name transform (directory + file name -> package + class name) and class.forName(). Apache commons io has some directory filtering classes IIRC. Am 17.10.2011 13:04 schrieb "Cem Koc": - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to write a working Custom Lifecycle?
Hi all, I try to define my own custom lifecycle, which I would like to use in some of my projects. As far as I understood, I should be enough to create a module with packaging type jar, to create a components.xml and to place this file below META-INF/plexus. To use this packaging type it should be engough to add it to the project as plugin with extensions set to true: customGroup packaingType42 1.0 true Maven knows the packaging type if I declare my packaging type like this, but the life cycle it self seems not to be found. What do I miss? My components.xml looks like this: org.apache.maven.lifecycle.mapping.LifecycleMapping packaging42 org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping default org.apache.maven.plugins:maven-resources-plugin:2.4:resources org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile I put the code for the packaging type on Github: https://github.com/plexusnexus/custompackagingtype Also an example project which uses this packaging type: https://github.com/plexusnexus/custompackagingusage Bye, Oliver https://github.com/plexusnexus/custompackagingusage - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
