<div dir="ltr"><div><div><div>Mark,<br><br></div>These maven pom files have all been updated and tested on sonatype using my own groupId. A small number of changes were required and it turns out that in a multi-module project the parent module can't produce a jar. This re-iterates the requirement for the main/pom.xml file. I attempted to do without the main/pom.xml file but it wouldn't produce the an abcl package that way.The release was made with the code on a 1.3.2-maven git branch located at <a href="https://github.com/rritoch/abcl/tree/1.3.2-maven" target="_blank">https://github.com/rritoch/abcl/tree/1.3.2-maven</a> . I have updated the pom.xml files on my master branch to reflect the required changes to be fully compatible with sonatype's deployment process. <br><br>The deployment process with these pom files is as follows.<br><br></div><div>1. Change all version numbers in abcl/pom.xml , abcl/contrib/pom.xml, and abcl/main/pom.xml to an absolute version number without the -SNAPSHOT extension.<br><br></div><div>2. Execute mvn deploy -Dbuild=full<br></div><div><br></div><div>3. Login to oss sonatype, locate the staging repository in Build Promotion > Staging Repositories (in the left menu), close the repository, and finally release the repository.<br><br></div><div>This is MUCH easier, and more efficient than the current process. Deployment to localrepo is as simple as just typing mvn install and I believe it no longer requires the gpg signing process. These will continue to work without maintenance as long as the ant build targets aren't renamed or significantly changed.<br><br></div><div>The artifacts I deployed are accessible with the following dependencies. I left in the original group-id commented out since this isn't an official release.<br><br> <dependency><br> <!-- <groupId>org.armedbear.lisp</groupId> --><br> <groupId>com.vnetpublishing.abcl</groupId><br> <artifactId>abcl</artifactId><br> <version>1.3.2</version><br> </dependency><br><br> <dependency><br> <!-- <groupId>org.armedbear.lisp</groupId> --><br> <groupId>com.vnetpublishing.abcl</groupId><br> <artifactId>abcl-contrib</artifactId><br> <version>1.3.2</version><br> </dependency><br></div><div><br></div>Best Regards,<br></div> Ralph Ritoch<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 3, 2015 at 12:58 PM, Ralph Ritoch <span dir="ltr"><<a href="mailto:rritoch@gmail.com" target="_blank">rritoch@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Mark,<br><br></div> I have added a separate build profile for deployment to maven central. When the "default" profile is used the source release and javadoc aren't generated, and the gpg signing isn't executed. To use this new full profile, such as for deploying to maven central, you must append -Dbuild=full to your command line. For example, mvn install -Dbuild=full , if you don't include this extra argument the javadocs and source releases aren't generated and the gpg signing isn't applied. These new pom's are on git.<br><br><a href="https://github.com/rritoch/abcl/blob/master/abcl/pom.xml" target="_blank">https://github.com/rritoch/abcl/blob/master/abcl/pom.xml</a><br><a href="https://github.com/rritoch/abcl/blob/master/abcl/main/pom.xml" target="_blank">https://github.com/rritoch/abcl/blob/master/abcl/main/pom.xml</a><br><a href="https://github.com/rritoch/abcl/blob/master/abcl/contrib/pom.xml" target="_blank">https://github.com/rritoch/abcl/blob/master/abcl/contrib/pom.xml</a><br><br></div>My next project will be to attempt to release version 1.3.2 to a maven central repository which will likely require some additional changes to these pom files.<br><br></div>Best Regards,<br></div> Ralph Ritoch<br><div><div><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Fri, Jul 24, 2015 at 2:44 PM, Mark Evenson <span dir="ltr"><<a href="mailto:evenson@panix.com" target="_blank">evenson@panix.com</a>></span> wrote:<br></span><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
<br>
On 2015/7/21 19:27, Ralph Ritoch wrote:<br>
> Hi,<br>
><br>
> I have created some maven POM files which can be used to build and deploy<br>
> ABCL with maven. There have been a few modifications to these over the past<br>
> few days and there is probably room for improvement but these make it<br>
> possible to build and depoy ABCL with the normal maven lifecycle.<br>
<br>
</span>Thanks!<br>
<br>
A couple questions:<br>
<br>
1) Is it possible to merge the new main/pom.xml into top-level POM?<br>
Creating a new directory just to separate the main ABCL build<br>
instructions seems a little wrong to me.<br>
<br>
2) Why not use the Ant instructions for building the actual abcl.jar<br>
artifact? It would be better for future maintenance not to have two<br>
sets of instructions for constructing deployment artifacts.<br>
<br>
3) Can we make the GPG signing optional for the 'install' target?<br>
<span><font color="#888888"><br>
<br>
<br>
--<br>
"A screaming comes across the sky. It has happened before, but there<br>
is nothing to compare to it now."<br>
</font></span></blockquote></div></div></div><br></div>
</blockquote></div><br></div>