I'm encountering an issue with Byldan (.NET version of Maven) and since this
is a general problem, I thought I'd raise it here on the list. I need to
extend the pom model to include information like the key token id of the
.NET assembly. Using the modelVersion element of the pom isn't appropriate
to indicate these platform type extensions.

The key here is to provide enough information in the pom to allow the build
tool to choose the implementation of the ModelTransformer it needs. For
example, if Maven sees Maven:4.0.0, then it chooses PomClassicTransformer to
read the information into the canonical data format. If Maven sees
dotnet:1.0.0, then Maven could use DotnetModelTransformer, and so on.

Some ideas:
1) qualify modelVersion with platform: dotnet:1.0.0, maven:4.0.0
2) new platform tag
3) use of namespaces
4) Some unique id that maps to transformer

I'm leaning toward (4) as it is more future proof to changes. Thoughts?

Thanks,
Shane

Reply via email to