Re: [mojo-dev] trouble with OSSHR and flatten-maven-plugin

[Jörg Hohwiller]

Am 01.05.2014 22:13, schrieb Robert Scholte:

Hi,

Hi Robert,

Now there are two solutions:
1. create a couple of predefined descriptors matching these requirements
2. have a way for developers to create their own descriptor.

the current result of a flattened pom contains only the information required other projects need to be ably to *use* this artifact, nothing more, nothing less. It's all Aether needs. So now it seems that some artifact repositories required extra info for quality purpose, so that's some other goal, though valid. the first one could be done programmatically, but if it is a separate (xml)-file, you can do both at once. I know there are some people/companies who want to hide the scm info, because it is not useful when giving/selling the artifacts to customers. So we probably need a dynamic solution in the end.

Thanks for your input. I was also thinking about a flexible way to configure this as one day we will end up there anyways.

So maybe for each of this POM elements we could have a configuration option.
For plain options there is just "keep" or "remove" available.
For others such as scm, also "inherit" could be an option.

I will add such feature to the Mojo and then we can have a look and chat about the defaults. However, after our current released behaviour it might be the safest way to keep all the new options off (set to "remove") by default to keep current behaviour and initial goal (flatten/minimize). For OSSHR projects I could add a example/hint on the site with the proper configuration to go.

thanks,
Robert

Regards
  Jörg

smime.p7s
Description: S/MIME Cryptographic Signature