Re: [jira] [Commented] (MNG-5987) Document the algorithm calculating the order of plugin executions.

ild POM, but that child's execution > order is different from the parent's. > > Overall, I think execution id is better, and the transition cost is worth it. > >> Document the algorithm calculating the order of plugin executions. >>

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

Re: Passing State Between Plugin Executions

Excellent, thanks all for the quick help! On Wed, Jan 30, 2013 at 3:09 PM, Robert Scholte wrote: > I would use http://maven.apache.org/ref/3.**0.4/maven-plugin-api/apidocs/* > *org/apache/maven/plugin/**AbstractMojo.html#**getPluginContext()

Re: Passing State Between Plugin Executions

I would use http://maven.apache.org/ref/3.0.4/maven-plugin-api/apidocs/org/apache/maven/plugin/AbstractMojo.html#getPluginContext() Robert Op Wed, 30 Jan 2013 20:36:47 +0100 schreef Stephen Connolly : You can stash it in the MavenSession IIRC On Wednesday, 30 January 2013, Brian Fox wrot

Re: Passing State Between Plugin Executions

You can stash it in the MavenSession IIRC On Wednesday, 30 January 2013, Brian Fox wrote: > The enforcer plugin uses a static array to hold data between executions. > > > On Wed, Jan 30, 2013 at 2:15 PM, Aaron Dixon > > wrote: > > > I am developing a plugin with "start" and "stop" goals to be exe

Re: Passing State Between Plugin Executions

The enforcer plugin uses a static array to hold data between executions. On Wed, Jan 30, 2013 at 2:15 PM, Aaron Dixon wrote: > I am developing a plugin with "start" and "stop" goals to be executed > typically in pre-integration-test and post-integration-test phases, > respectively. > > For exam

Passing State Between Plugin Executions

I am developing a plugin with "start" and "stop" goals to be executed typically in pre-integration-test and post-integration-test phases, respectively. For example, the "start" execution will discover a port that I'd like the "stop" execution to know. Of course, I could use a file or possibly sta

Re: Plugin executions

8:05 AM To: Maven Developers List Subject: Plugin executions Hi All, Is there any way of specifying which execution to use when inheriting plugin executions form a parent pom. I have a department wide pom, which configures various plugins and executions for use across all our maven projects (ju

RE: Plugin executions

Hi Take a look at profiles. Hermod -Original Message- From: SlinnHawkins, Jon (ELS) [mailto:[EMAIL PROTECTED] Sent: Thursday, August 17, 2006 8:05 AM To: Maven Developers List Subject: Plugin executions Hi All, Is there any way of specifying which execution to use when inheriting

Plugin executions

Hi All, Is there any way of specifying which execution to use when inheriting plugin executions form a parent pom. I have a department wide pom, which configures various plugins and executions for use across all our maven projects (just 1 at the moment, but will be about 15 soon). I need to

[jira] Closed: (MNG-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)

[ http://jira.codehaus.org/browse/MNG-2054?page=all ] John Casey closed MNG-2054: --- Assign To: John Casey Resolution: Fixed Fix Version: (was: 2.0.4) 2.0.3 > Multiple Inheritence causes plugin executions to run multi

[jira] Reopened: (MNG-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)

[ http://jira.codehaus.org/browse/MNG-2054?page=all ] John Casey reopened MNG-2054: - > Multiple Inheritence causes plugin executions to run multiple times (Test > Case At

[jira] Closed: (MNG-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)

[ http://jira.codehaus.org/browse/MNG-2054?page=all ] John Casey closed MNG-2054: --- Resolution: Fixed confirmed fixed by Brian Fox, I just added a variant of sample.zip as it0096. > Multiple Inheritence causes plugin executions to run multiple ti

[jira] Commented: (MNG-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)

reflects the correct information. I'd like to see this get created as an integration test to prevent future regresion, but I'm not 100% sure how to test for this condition. > Multiple Inheritence causes plugin executions to run multiple times (Test &g

[jira] Updated: (MNG-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)

[ http://jira.codehaus.org/browse/MNG-2054?page=all ] John Casey updated MNG-2054: Fix Version: (was: 2.0.3) 2.0.4 > Multiple Inheritence causes plugin executions to run multiple times (Test > Case At

[jira] Updated: (MNG-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)

[ http://jira.codehaus.org/browse/MNG-2054?page=all ] Carlos Sanchez updated MNG-2054: Priority: Critical (was: Major) Fix Version: 2.0.3 > Multiple Inheritence causes plugin executions to run multiple times (Test > Case At

[jira] Commented: (MNG-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)

the same name be merged with their parent? > Multiple Inheritence causes plugin executions to run multiple times (Test > Case Attached) > > > Key: MNG-2054 > URL: http://j

[jira] Created: (MNG-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)

Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached) Key: MNG-2054 URL: http://jira.codehaus.org/browse/MNG-2054 Project: Maven 2 Type: Bug