+1 on this, my mental model of a parent POM is to handle the commonality, if there are a hundred projects that require the same settings in a POM that should be moved up to a parent, much like I would do if I were developing.
-- Jason On Tue, Feb 27, 2018, at 10:58 AM, Robert Munteanu wrote: > > Well, let's try and avoid that :-) > > Could we either: > > 1) Create a profile in the parent pom, activated for bundle projects, > which adds the OSGi dependencies? > > 2) Create a 'non-OSGi' parent POM (A) and an 'OSGi' parent POM (B), > where A is the parent of B. This way we could use the parent POM in > different projects without getting any clashes. > > Robert
