Maven Repository plugin fails when artifactId contains a dot about bnd HOT 4 CLOSED

The problem is that maven group/artifact id cannot be unambiguously be used from a bundle symbolic name. Therefore, there is a plugin you can set:

-plugin = aQute.bnd.maven.MavenGroup; groupId=org.apache.felix, ...

This will use a group Id and then assume the bsn is the artifact id. So in the previous setting, the bsn for file install is org.apache.felix.fileinstall because Felix repeats the groupId in the artifact id.

I could make this more user friendly, I am actually trying this. However, this was never written as a widely used feature, I made it for Richard Hall. However, more and more people seem to be interested.

from bnd.

Good to know (I saw the reference but was unsure about the usage).
What if the bundles referenced that are in my Maven repository belong to more than one groupId?

from bnd.

I made a new release: http://www.aQute.biz/Bnd/Download that should have a maven plugin that is more clever than it was before about bsn -> groupid/artifactId mapping. Let me know your experiences.

from bnd.

Please provide feedback

from bnd.