Il 11/08/2014 14:29, Francesco Chicchiriccò ha scritto:
Hi all,
as the time for releasing (at least the first milestone of) 1.2.0 is
approaching, I have noticed that we currently have few Maven
sub-modules which effectively don't generate artifacts for usage with
Maven, i.e.
* standalone (1.1.X / 1.2.X)
* installer (1.2.X)
* deb (1.2.X)
Do you see any problem if we remove such modules from default build
profile, e.g. change the main pom.xml from
<modules>
<module>archetype</module>
<module>build-tools</module>
<module>common</module>
<module>client</module>
<module>core</module>
<module>console</module>
<module>standalone</module>
<module>installer</module>
<module>deb</module>
</modules>
to
<modules>
<module>archetype</module>
<module>build-tools</module>
<module>common</module>
<module>client</module>
<module>core</module>
<module>console</module>
</modules>
?
Naturally, we will also need to change the release procedure [1] to
take this fact into account - e.g. to manually (e.g. not via Maven
release plugin / Nexus) publish to the staging area the artifacts for
standalone, installer and deb.
We might create an "all" profile including the modules excluded above
and instruct Jenkins / Travis to use that profile, in order to check
that they still work fine.
This will dramatically speed-up the deploy time (not requiring to
upload to Maven repositories some artifacts that are not actually
meant to be used via Maven).
WDYT?
I noticed that insertion of deb module also raised, on some machines,
the need to change Maven/Java memory options to build project, so I
completely agree.
+1
[1] http://syncope.apache.org/release-process.html
--
Dott. Andrea Patricelli
Tel +393204524292
Junior Engineer @ Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +390859116307 / FAX +39 0859111173
http://www.tirasa.net
