Thanks a lot for your suggestions Stephen, that's priceless help! :) Have a nice day, all the best! -Simo
http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, May 3, 2013 at 12:32 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Another solution is the maven-shade-plugin can publish the shaded pom to a > different GAV > > > On 3 May 2013 11:31, Stephen Connolly <stephen.alan.conno...@gmail.com > >wrote: > > > I'd either do it something like > > > > <plugin> > > <artifactId>maven-deploy-plugin</artifactId> > > <executions> > > <execution> > > <id>public-artifact</id> > > <phase>deploy</phase> > > <goals> > > <goal>deploy-file</goal> > > </goals> > > <configuration> > > <pomFile>${project.build.directory}/public-pom.xml</pomFile> > > <file>${project.build.directory}/some.jar</file> > > > > > <files>${project.build.directory}/some-javadoc.jar,${project.build.directory}/some-sources.jar</files> > > <types>jar,jar</types> > > <classifiers>javadoc,sources</classifiers> > > </configuration> > > </execution> > > </executions> > > </plugin> > > > > Or I would use the non-maven-jar maven plugin and the dependency:copy > > plugins keeping the public pom as part of the reactor (for the case where > > you need to use the public pom as a dependency within your reactor > > > > > > On 3 May 2013 11:25, Stephen Connolly <stephen.alan.conno...@gmail.com > >wrote: > > > >> yep > >> > >> > >> On 3 May 2013 11:18, Simone Tripodi <simonetrip...@apache.org> wrote: > >> > >>> 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 > >>> > > >>> > >> > >> > > >
