> > Maybe we can have a compromise and require a property in the pom, e.g. > > <properties> > <sling.bundle>true</sling.bundle> > </properties> > > That property will activate the OSGi-related profile from the parent > pom. > > Not ideal but still better than copy/pasting considerably more > dependency versions. >
This is not supported by Maven. Only properties given via command line can be used for profile activation (see https://issues.apache.org/jira/browse/MNG-5127 and a lot of related tickets). Therefore we would rather need to rely on existence of a dedicated marker file.
