Sounds fair, whenever e.g. Jenkins needs to deploy it may be good to use settings maintained by Apache. I did not change the POM, but saw the version number we use for all "1.0.0" releases was missing a 0 in the README text, so I adjusted that.
I generated a fingerprint with the Apache email address and it's published to "gnupg.org". If this gets mirrored automatically, it should show up in the list soon, too. On Wed, Jul 16, 2014 at 9:36 PM, Reza <[email protected]> wrote: > So regarding the Apache parent pom... generally I like to keep my code > minimal and dependencies minimal, it reduces the surface area for problems, > bugs, and all sort of other issues associated with software development. > Just a practice I picked up along the way... That aside, I noticed that the > Apache parent pom has includes for lots and lots of plugins and other > configurations which I wasn't using, so I had cut it out. Thats really it, > if you want to include it, I can turn it on next build. No biggie :) > > Remember, I had made the release before some of these changes were checked > in, so they will be included in the next release. > > > ________________________________ > From: Werner Keil <[email protected]> > To: "[email protected]" < > [email protected]> > Sent: Wednesday, July 16, 2014 3:19 PM > Subject: Re: Please setup your PGP key if preparing releases > > > > I installed the Windows version (except for virtual boxes there's no Linux > here) of GnuPG, as soon as it generates a fingerprint, I'll add it, too. > > Note, the data tags contain entries for both device-data and test-data. > Should you wish to not include the test-data part, then using the separate > "releases" folder would allow to add only one of them or both. > > It never caused any build problem, but the classifier "lost" its parent > POM again It ain't so important if one right above was used, but unlike > isolated settings of e.g. > --- maven-compiler-plugin:3.0:compile > > all other POMs derived from either "apache-parent" or its children (like > "devicemap-java") get the more recent version > --- maven-compiler-plugin:3.1:compile > > > It won't break the build but make different Java artifacts inconsistent > from common Apache settings. Using at least an appropriate version of the > Apache parent would be highly advisable, not just for other plugins like > RAT that are configured there, too. > > If you don't use it you need to maintain up to 400(!) lines of that Apache > master POM in your own project, does anybody really want that burden, not > to mention the Maven deploy settings for the right servers, etc. > > Werner > > > > > On Wed, Jul 16, 2014 at 10:53 AM, Bertrand Delacretaz < > [email protected]> wrote: > > On Wed, Jul 16, 2014 at 10:13 AM, eberhard speer jr. <[email protected]> > wrote: > >> ...Did it again, this time manually added it to pgp.mit.edu.. > > > >ok I see it now at > >http://pgp.mit.edu/pks/lookup?op=vindex&search=0xF831E019FFBAC523 so > >it should appear at https://people.apache.org/keys/group/devicemap.asc > >soon. > > > >-Bertrand > > >
