You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Dan Tran <da...@gmail.com> on 2014/08/01 10:33:01 UTC
Re: Keeping Plexus component states persisted accross plugin executions
Ping
On Thursday, July 31, 2014, Dan Tran <da...@gmail.com> 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, etc)
>
> I think using maven extension is way to go, but not sure how to get this
> to work. Do you have a code sample somewhere?
>
> Huge thanks ahead
>
> -Dan
>
Re: Keeping Plexus component states persisted accross plugin executions
Posted by Dan Tran <da...@gmail.com>.
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
<https://plus.google.com/u/0/107251243568189719606?prsrc=4> works, it had
to tune extension file
https://swarm.workshop.perforce.com/files/guest/dantran/p4maven/p4maven-mojo/src/main/resources/META-INF/maven/extension.xml
the sample test is at
https://swarm.workshop.perforce.com/files/guest/dantran/p4maven/p4maven-mojo/src/it/shelve
-Dan
On Wed, Sep 10, 2014 at 12:11 PM, Dan Tran <da...@gmail.com> wrote:
> 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 <da...@gmail.com> wrote:
>
>> So far it looks to me it is as simple as setting
>> <extensions>true</extensions> 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 plugin/extensions[2]
>>
>> build/extensions is used in multiple mojo projects (just grep to find
>> them) to
>> add an extension to site plugin (which IMHO should not be done with such
>> extension but just as m-site-p dependency)
>>
>> I couldn't find any exemple of plugin/extension, and the doc isn't clear.
>> But since there is a Maven Core IT [3] for MNG-4381 [4] that explains
>> exactly
>> what you are trying to do ("Test that extension plugins can contribute
>> non-
>> core components that can be accessed by other plugins in the same project
>> and
>> in projects with the same extension"), this should contain a working
>> example
>>
>> Regards,
>>
>> Hervé
>>
>> [1] http://maven.apache.org/ref/3.2.2/maven-model/maven.html#class_build
>>
>> [2] http://maven.apache.org/ref/3.2.2/maven-model/maven.html#class_plugin
>>
>> [3] http://jira.codehaus.org/browse/MNG-4381
>>
>> [4]
>> http://maven.apache.org/core-its/core-it-suite/xref-test/org/apache/maven/it/MavenITmng4381ExtensionSingletonComponentTest.html
>>
>> Le vendredi 1 août 2014 01:55:59 vous avez écrit :
>>
>>
>> On Fri, Aug 1, 2014 at 2:24 AM, Hervé BOUTEMY <he...@free.fr>
>> wrote:
>>
>>> 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.mahler@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://mail-archives.apache.org/mod_mbox/maven-dev/201407.mbox/%3Ca2133e028
>>> > cf3c18c539eac4d6cf42ed9.squirrel%40webmail.buschmais.com%3E) but it
>>> seems
>>> > not trivial - I ran into several classloading issues. Thus an example
>>> would
>>> > be very helpful.
>>> >
>>> > Best regards and thanks in advance
>>> >
>>> > Dirk
>>> >
>>> > > Ping
>>> > >
>>> > > On Thursday, July 31, 2014, Dan Tran <da...@gmail.com> 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, etc)
>>> > >>
>>> > >> I think using maven extension is way to go, but not sure how to get
>>> this
>>> > >> to work. Do you have a code sample somewhere?
>>> > >>
>>> > >> Huge thanks ahead
>>> > >>
>>> > >> -Dan
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> > For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>
Re: Keeping Plexus component states persisted accross plugin executions
Posted by Dan Tran <da...@gmail.com>.
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 <da...@gmail.com> wrote:
> So far it looks to me it is as simple as setting
> <extensions>true</extensions> 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 plugin/extensions[2]
>
> build/extensions is used in multiple mojo projects (just grep to find
> them) to
> add an extension to site plugin (which IMHO should not be done with such
> extension but just as m-site-p dependency)
>
> I couldn't find any exemple of plugin/extension, and the doc isn't clear.
> But since there is a Maven Core IT [3] for MNG-4381 [4] that explains
> exactly
> what you are trying to do ("Test that extension plugins can contribute non-
> core components that can be accessed by other plugins in the same project
> and
> in projects with the same extension"), this should contain a working
> example
>
> Regards,
>
> Hervé
>
> [1] http://maven.apache.org/ref/3.2.2/maven-model/maven.html#class_build
>
> [2] http://maven.apache.org/ref/3.2.2/maven-model/maven.html#class_plugin
>
> [3] http://jira.codehaus.org/browse/MNG-4381
>
> [4]
> http://maven.apache.org/core-its/core-it-suite/xref-test/org/apache/maven/it/MavenITmng4381ExtensionSingletonComponentTest.html
>
> Le vendredi 1 août 2014 01:55:59 vous avez écrit :
>
>
> On Fri, Aug 1, 2014 at 2:24 AM, Hervé BOUTEMY <he...@free.fr>
> wrote:
>
>> 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.mahler@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://mail-archives.apache.org/mod_mbox/maven-dev/201407.mbox/%3Ca2133e028
>> > cf3c18c539eac4d6cf42ed9.squirrel%40webmail.buschmais.com%3E) but it
>> seems
>> > not trivial - I ran into several classloading issues. Thus an example
>> would
>> > be very helpful.
>> >
>> > Best regards and thanks in advance
>> >
>> > Dirk
>> >
>> > > Ping
>> > >
>> > > On Thursday, July 31, 2014, Dan Tran <da...@gmail.com> 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, etc)
>> > >>
>> > >> I think using maven extension is way to go, but not sure how to get
>> this
>> > >> to work. Do you have a code sample somewhere?
>> > >>
>> > >> Huge thanks ahead
>> > >>
>> > >> -Dan
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
Re: Keeping Plexus component states persisted accross plugin executions
Posted by Dan Tran <da...@gmail.com>.
So far it looks to me it is as simple as setting
<extensions>true</extensions> 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 plugin/extensions[2]
build/extensions is used in multiple mojo projects (just grep to find them)
to
add an extension to site plugin (which IMHO should not be done with such
extension but just as m-site-p dependency)
I couldn't find any exemple of plugin/extension, and the doc isn't clear.
But since there is a Maven Core IT [3] for MNG-4381 [4] that explains
exactly
what you are trying to do ("Test that extension plugins can contribute non-
core components that can be accessed by other plugins in the same project
and
in projects with the same extension"), this should contain a working example
Regards,
Hervé
[1] http://maven.apache.org/ref/3.2.2/maven-model/maven.html#class_build
[2] http://maven.apache.org/ref/3.2.2/maven-model/maven.html#class_plugin
[3] http://jira.codehaus.org/browse/MNG-4381
[4]
http://maven.apache.org/core-its/core-it-suite/xref-test/org/apache/maven/it/MavenITmng4381ExtensionSingletonComponentTest.html
Le vendredi 1 août 2014 01:55:59 vous avez écrit :
On Fri, Aug 1, 2014 at 2:24 AM, Hervé BOUTEMY <he...@free.fr> wrote:
> 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.mahler@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://mail-archives.apache.org/mod_mbox/maven-dev/201407.mbox/%3Ca2133e028
> > cf3c18c539eac4d6cf42ed9.squirrel%40webmail.buschmais.com%3E) but it
> seems
> > not trivial - I ran into several classloading issues. Thus an example
> would
> > be very helpful.
> >
> > Best regards and thanks in advance
> >
> > Dirk
> >
> > > Ping
> > >
> > > On Thursday, July 31, 2014, Dan Tran <da...@gmail.com> 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, etc)
> > >>
> > >> I think using maven extension is way to go, but not sure how to get
> this
> > >> to work. Do you have a code sample somewhere?
> > >>
> > >> Huge thanks ahead
> > >>
> > >> -Dan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Keeping Plexus component states persisted accross plugin executions
Posted by Hervé BOUTEMY <he...@free.fr>.
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.mahler@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://mail-archives.apache.org/mod_mbox/maven-dev/201407.mbox/%3Ca2133e028
> cf3c18c539eac4d6cf42ed9.squirrel%40webmail.buschmais.com%3E) but it seems
> not trivial - I ran into several classloading issues. Thus an example would
> be very helpful.
>
> Best regards and thanks in advance
>
> Dirk
>
> > Ping
> >
> > On Thursday, July 31, 2014, Dan Tran <da...@gmail.com> 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, etc)
> >>
> >> I think using maven extension is way to go, but not sure how to get this
> >> to work. Do you have a code sample somewhere?
> >>
> >> Huge thanks ahead
> >>
> >> -Dan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Keeping Plexus component states persisted accross plugin
executions
Posted by di...@buschmais.com.
+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 issues. Thus an
example would be very helpful.
Best regards and thanks in advance
Dirk
> Ping
>
> On Thursday, July 31, 2014, Dan Tran <da...@gmail.com> 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, etc)
>>
>> I think using maven extension is way to go, but not sure how to get this
>> to work. Do you have a code sample somewhere?
>>
>> Huge thanks ahead
>>
>> -Dan
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org