[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cf-dev] Problem for building californium following pom.xml changes
|
Okay, I threw the signing profiles in the same pot without looking... I assume eclipse_jar_signing was added for Hudson, so we can generate the sandbox JAR.
Furthermore, I will pick create_gpg_signature and release_to_maven. I will put them into the parent together with Javadoc.
Please just double-check if these are the right profiles.
> -----Original Message-----
> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Kovatsch Matthias
> Sent: Donnerstag, 1. Oktober 2015 18:37
> To: Californium (Cf) developer discussions <cf-dev@xxxxxxxxxxx>
> Subject: Re: [cf-dev] Problem for building californium following pom.xml
> changes
>
> While working on the POMs, I noticed that the profiles are still distributed,
> sometimes duplicated, and slightly inconsistent:
>
> javadoc (all but parent)
>
> eclipse_jar_signing (element-connector, scandium-parent, californium-
> parent, tools)
> create_gpg_signature (scandium)
>
> release_to_maven (scandium)
> release (parent, actinium)
> maven_central (element-connector)
>
> I will move the profiles also to the overall parent POM.
> Which is the latest or proper profile for signing? Or are they for different
> purposes?
> Which is the proper release profile?
>
> Ciao
> Matthias
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit https://dev.eclipse.org/mailman/listinfo/cf-dev
