Re: Keeping Plexus component states persisted accross plugin executions

I finally able to get my p4maven-provider sharing its singletons with other mojos ( scm, release, buildnumber, etc). Basically the example provided by Hervé Boutemy works, it had to tune extension file https://swarm.workshop.perforce.com

Re: Keeping Plexus component states persisted accross plugin executions

I am going back and forth on this topic and its reference, and still not able to get my singleton belonging to a jar to be shared across plugins. Dirk how are you doing at your side? Thanks -Dan On Fri, Aug 1, 2014 at 9:21 AM, Dan Tran wrote: > So far it looks to me it is as simple as settin

Re: Keeping Plexus component states persisted accross plugin executions

So far it looks to me it is as simple as setting true to my project's build-->plugins-->plugin ( in this case maven-scm-plugin ). It not working. Perhaps I need to do some MANIFEST setup at my component? -D here the Herve' s response at mojo-dev you use either build/extensions/extension[1] or

Re: Keeping Plexus component states persisted accross plugin executions

I replied on mojo (didn't see the cross-post) any help appreciated to improve the documentation :) Regards, Hervé Le vendredi 1 août 2014 11:05:43 dirk.mah...@buschmais.com a écrit : > +1 from my side (see my questi. > > I tried using an extension for the question I asked some days ago > (http

Re: Keeping Plexus component states persisted accross plugin executions

+1 from my side (see my questi. I tried using an extension for the question I asked some days ago (http://mail-archives.apache.org/mod_mbox/maven-dev/201407.mbox/%3Ca2133e028cf3c18c539eac4d6cf42ed9.squirrel%40webmail.buschmais.com%3E) but it seems not trivial - I ran into several classloading issu

Re: Keeping Plexus component states persisted accross plugin executions

Ping On Thursday, July 31, 2014, Dan Tran wrote: > > Hi > > my P4Maven - a Maven SCM providers - has plexus component singleton with > states, and I would like to have the states to persist across multiple > plugins executions ( maven-scm-plugin, maven-release-plugin, > buildnumber-maven-plugin,

Keeping Plexus component states persisted accross plugin executions

Hi my P4Maven - a Maven SCM providers - has plexus component singleton with states, and I would like to have the states to persist across multiple plugins executions ( maven-scm-plugin, maven-release-plugin, buildnumber-maven-plugin, etc) I think using maven extension is way to go, but not sure h