I have a project here which, currently, uses one pom.xml (link) to generate one \"artifact\".
What I\'d like to do is split the project, let\'s call it p, into:
Your life will be much easier if you simply break out p-format into a separate project that depends on p-core.
Although there are ways to publish multiple artifacts per project, Maven is designed around one artifact per pom/module (plus test artifacts). From experience, clever attempts to work around this design point will end up biting you eventually - usually in the form of an issue 6 months down the road where packaging won't work properly on someone's machine.
The scenario you describe fits well within the multi-project use case, and I'd suggest you go with the flow and make your future self happy.