pivot-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sandro Martini <sandro.mart...@gmail.com>
Subject Re: Maven build and javadoc
Date Wed, 20 Jan 2016 13:28:18 GMT
Hi Tom,
note that Pivot build was setup years ago, when Ant was mainstream,
and it's not a project requiring a complex build (so Maven or Gradle
or other aren't strictly required).

Anyway if there is enough interest in the community I'm available to
discuss/implement a new version of our build system for example with
Gradle, but only for some common tasks (and if needed keep others with
Ant, could be a good compromise for now) because there are others not
so simple to migrate but only for the code in trunk 2.1.x (or better
for next major release, 2.5.x).

Anyway, currently if you have ant available and in the CLASSPATH the
ant-maven bridge jar, you have to:

$ ant maven-install

that generates Pivot jars in a format compatible with binary jars,
source jars, javadoc jars, and install them in a local maven

Note that pom.xml files in our sources are not usable directly because
our build system does a replace of varibles inside (like the @VERSION@
you wrote before).

Last (just for info), some year ago I wrote a Maven archetype (a
near-empty template project) for Pivot, you can find its sources here:


but it has never been published in maven main repository because we
didn't have a valid vote to release it.
Even for this, is there is enough community interest we can update and
try a vote ...

As always, be free to ask for more info.


2016-01-20 13:55 GMT+01:00 Tom <tom@soaringclub.org>:
> Actually, you may be closer to a complete maven build than you think.
> (And I was able to build the docs with 'ant doc'. I was just trying to avoid
> having to set up the ant classpath.)
> And the reason I posted here was to try to avoid having to read through the
> documentation for the maven javadoc plugin.
> Personally, I find Maven a complete pain (and you can see how much I know
> about it from my @VERSION@ question), but then there's something to be said
> for the simplicity of 'mvn clean install'.
> Right now I am wading through the Pivot docs trying to get a handle on them.
> When the smoke clears I will have a look at the maven build.
> You know what they say about projects: "If they can build it they will
> come."
> Thanks,
> Tom
> Sandro Martini <sandro.martini@gmail.com> wrote:
> Hi all and sorry for the delay,
> as Roger said Pivot maven files was mainly done to be able to generate and
> publish jar files in main Maven repository  (central).
> But all is driven by our Ant build; there is a dedicated task to let Ant
> maven task (related jar is needed in CLASSPATH in this case) to generate and
> install maven compatible jars in a local repository.
> I know that we should update our build system to maven or gradle, but time
> is needed to do it because there are other tasks not so simple to
> migrate/rewrite.
> Any  help is welcome :-) .
> Tell me if you need more info on this.
> Bye,
> Sandro
> Il 20/Gen/2016 01:39, "Roger Whitcomb" <Roger.Whitcomb@actian.com> ha
> scritto:
>> Actually, I think the biggest problem is that our project directory
>> structures don't conform to the standard Maven conventions (see
>> https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html)
>> and I don't see any project descriptor settings that would change that.
>> ~Roger
>> -----Original Message-----
>> From: Tom Coleman [mailto:tom@soaringclub.org]
>> Sent: Tuesday, January 19, 2016 9:12 AM
>> To: user@pivot.apache.org
>> Subject: Maven build and javadoc
>> Hi
>> I'm trying to build the project using Maven.   2 dumb questions.  Sorry.
>> How can I generate javadoc from the maven root directory?
>> mvn javadoc:javadoc just creates an xml file:
>> javadoc-options-javadoc-resources.xml.  Google didn't really help.
>> And how can I get a version number into the jars?  Here's what I get now:
>> ./core/target/pivot-core-@VERSION@.jar
>> Thanks.

View raw message