Build ABCL with Maven using these updated POM files.
rritoch at gmail.com
Mon Aug 3 04:58:20 UTC 2015
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
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.
On Fri, Jul 24, 2015 at 2:44 PM, Mark Evenson <evenson at panix.com> wrote:
> On 2015/7/21 19:27, Ralph Ritoch wrote:
> > Hi,
> > I have created some maven POM files which can be used to build and deploy
> > ABCL with maven. There have been a few modifications to these over the
> > few days and there is probably room for improvement but these make it
> > possible to build and depoy ABCL with the normal maven lifecycle.
> A couple questions:
> 1) Is it possible to merge the new main/pom.xml into top-level POM?
> Creating a new directory just to separate the main ABCL build
> instructions seems a little wrong to me.
> 2) Why not use the Ant instructions for building the actual abcl.jar
> artifact? It would be better for future maintenance not to have two
> sets of instructions for constructing deployment artifacts.
> 3) Can we make the GPG signing optional for the 'install' target?
> "A screaming comes across the sky. It has happened before, but there
> is nothing to compare to it now."
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the armedbear-devel