-----Original Message-----
From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On
Behalf Of Simon Bernard
Sent: Tuesday, September 15, 2015 3:51 PM
To: Californium (Cf) developer discussions
Subject: Re: [cf-dev] Parent POM for "static" information (e.g.,
committers)
+1 for renaming "californium" to "californium.core" and use the actual
parent "californium" for the parent POM.
I feel this less confusing too, but this will require more works, so I
could understand that the vote of people will do the job, could have
further weight than mine.
Simon
Le 07/09/2015 16:44, Kovatsch Matthias a écrit :
Hi all
Kai proposed to extract the redundant information in the sub-project
POMs into an Eclipse-project-wide parent POM and applied the changes.
Now, however, we have a funny structure and build order, where a sub-
directory in "californium" needs to be build first and then the usual
process with element-connector, scandium, actual californium again,
tools, and actinium.
It would be better to move the parent POM into its own repo. Here, we
have two options:
- create a new repo "californium.parent" (+1 Kai)
- rename "californium" to "californium.core" and use the actual
parent "californium" for the parent POM (+1 Matthias)
I personally prefer the second option because it will be less
confusing. However, it will come with some overhead to reconfigure
Hudson and for people to clone the renamed repository...
Thoughts, comments?
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
_______________________________________________
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
