Thanks for the suggestion, Stephen! so you mean that rather than attaching the new pom to the original project, I should use the deployer to deploy a separated artifact, right?
TIA, all the best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Thu, May 2, 2013 at 2:21 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Deploy at a different GAV. > > Used do this at a former employers. Internally we'd use one GA and the > publish externally at a different GA (same V) > > On Thursday, 2 May 2013, Simone Tripodi wrote: > > > Hi all, > > > > I am in the scenario where a POM is generated and attached in the main > > project, then will be deployed on the repo; that POM contains all > required > > dependencies my users need when developing custom applications. > > > > The issue comes when I would like to resolve the generated prom in an > > external project, becauee IIUC there is no way to: > > > > * inherit from a parent pom with a classifier; > > > > * declare its dependency in `dependencyManagement` with scope `import`. > > > > Does that mean that POM cannot have classifiers? Do you have any > > alternative solution? > > TIA! > > -Simo > > > > http://people.apache.org/~simonetripodi/ > > http://simonetripodi.livejournal.com/ > > http://twitter.com/simonetripodi > > http://www.99soft.org/ > > > > > -- > Sent from my phone >
