Looks like the right thing to do would be to swap out JSR 275 use with
that? I'll take a look if noone else has yet. I came across it while
looking into the packaging side of things, so keen to use the "right"
thing for the long term.
I agree. Oh, reminds me - any thoughts on long term use of the org.custardsource
namespace? Would "io.pcp.parfait" make sense? I don't mind either way
just want to do any namespace switching upfront, before we start making
any heavier use of it here. (RPM supports namespace aliases, so we can
support both too if that's preferable).
I also agree and think we should switch to a more consistent PCP based namespace. That will of course BreakEverything, so best done as a managed major version increment with a migration guide (if possible, providing an example migration bash script that automatically replaces Java import statements with the new namespace. Hey my Mum said I can always ask, they can say no! :-P )
One other implication is to change the oss.sonatype.com link for Parfait for deployment out to the Java Maven repos, see things like this:
I believe that a top level namespace mapping is needed perhaps for the deployment for this artefactId or groupId.
RPM isn't going to help you here.
Paul
|