Hi, > Am 22.05.2017 um 09:19 schrieb sebb <[email protected]>: > > On 22 May 2017 at 13:14, Rob Tompkins <[email protected] > <mailto:[email protected]>> wrote: >> >>> On May 22, 2017, at 8:10 AM, Stephen Colebourne <[email protected]> >>> wrote: >>> >>> On 22 May 2017 at 12:51, Rob Tompkins <[email protected]> wrote: >>>> You could, in the parent, declare in the properties section beside the >>>> declaration of “commons.osgi.symbolicName”, another property pointing to >>>> that as >>>> >>>> <commons.automatic-module-name>${commons.osgi.symbolicName}</commons.automatic-module-name> >>>> >>>> and then allow people to override that in their local poms. That way you >>>> wouldn’t get the blank lines. >>> >>> True, but I want to ensure that we only add it to components where it >>> is valid (and we have manually checked it is valid). Which I think >>> requires us to do it in each subproject. >> >> We might be able to contrive something using antrun after compile that >> predicates on the property being populated, but that feels extra hacky. > > It's possible to have a profile depend on the presence of a file. > > So just create an empty file when the property is available for use.
Please no more profile activation based on files being present. This is just confusing and a dirty hack IMHO. > >>> Stephen >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> <mailto:[email protected]> >>> For additional commands, e-mail: [email protected] >>> <mailto:[email protected]> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> <mailto:[email protected]> >> For additional commands, e-mail: [email protected] >> <mailto:[email protected]> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > <mailto:[email protected]> > For additional commands, e-mail: [email protected] > <mailto:[email protected]>
