[
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
|
Not all of the profiles make sense for all of the Maven sub-modules in all components, e.g. we do not want to deploy all artifacts in californium.core to maven central but want to make some of them only available from the eclipse download site (we discussed this shortly in some previous mails, Matthias). I have therefore placed (and sometimes duplicated) the profile definitions into particular POMs and I do not think that they should all be "pulled up" into the parent POM.
If we put all profile definitions into the parent POM we will need to have a way to "disable" the profiles in certain sub-modules. We could do that by adding another property for explicitly de-activating them in the corresponding sub-modules, very much like the way we use properties to actually activate them ...
I have spent some time in placing the eclipse_jar_signing and create_gpg_signature and javadoc profile definitions so that they are only executed for sub-modules for which they make sense. Could you please check, that this is still the case now that you have pulled them all up?
Mit freundlichen Grüßen / Best regards
Kai Hudalla
Chief Software Architect
Technology Strategy
Bosch Software Innovations GmbH
Schöneberger Ufer 89-91
10785 Berlin
GERMANY
www.bosch-si.com
Phone +49 (30) 726112-159
Mobile +49 (151) 54336335
kai.hudalla@xxxxxxxxxxxx
Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B;
Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn
________________________________________
Von: cf-dev-bounces@xxxxxxxxxxx [cf-dev-bounces@xxxxxxxxxxx]" im Auftrag von "Kovatsch Matthias [kovatsch@xxxxxxxxxxx]
Gesendet: Donnerstag, 1. Oktober 2015 18:37
An: Californium (Cf) developer discussions
Betreff: 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
