maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gainty <mgai...@hotmail.com>
Subject RE: disabling default plugin from phase?
Date Thu, 03 Dec 2015 14:23:33 GMT
attempting to implement tycho compile but discovered my ClassRealm changed ?it appears new
ClassRealm "instrumented" a new lifecycle 
Consequently i have new plugin bindings for all phases for this new lifecycle
In particular the new process-test-resources phase plugin binding is not the plugin I want
to execute(Which is why I am attempting to disable the default plugin for process-test-resources
phase)
Thanks Adrian!
Martin 
______________________________________________ 
                                                                                         
      


> Date: Thu, 3 Dec 2015 09:54:04 +0100
> Subject: Re: disabling default plugin from phase?
> From: adrien.rivard@gmail.com
> To: users@maven.apache.org
> 
> Some goals/plugins also have a skip property.
> 
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-deploy-plugin</artifactId>
> <configuration>
> <!-- do not deploy that rtifact -->
> <skip>true</skip>
> </configuration>
> </plugin>
> 
> 
> On Thu, Dec 3, 2015 at 1:35 AM, Martin Gainty <mgainty@hotmail.com> wrote:
> 
> > I'll give this a tryThanks Mirko!
> > Martin-
> >
> > > From: mfriedenhagen@gmail.com
> > > Date: Wed, 2 Dec 2015 22:58:49 +0100
> > > Subject: Re: disabling default plugin from phase?
> > > To: users@maven.apache.org
> > >
> > > Hello Martin,
> > >
> > > as a hack you may override this in your pluginManagement by specifying
> > > an invalid phase.
> > >                 <plugin>
> > >                     <groupId>org.apache.maven.plugins</groupId>
> > >                     <artifactId>maven-source-plugin</artifactId>
> > >                     <version>${maven-source-plugin.version}</version>
> > >                     <inherited>true</inherited>
> > >                     <executions>
> > >                         <!-- suppress seperate generation of sources-jar
> > during
> > >                              run of release:stage, see
> > >
> > >
> > http://blog.peterlynch.ca/2010/05/maven-how-to-prevent-generate-sources.html
> > >                         -->
> > >                         <execution>
> > >                             <id>attach-sources</id>
> > >
> >  <phase>DISABLE_FORKED_LIFECYCLE_MSOURCES-13</phase>
> > >                         </execution>
> > >                         <execution>
> > >                             <id>default-jar-no-fork</id>
> > >                             <goals>
> > >                                 <goal>jar-no-fork</goal>
> > >                             </goals>
> > >                         </execution>
> > >                     </executions>
> > >                 </plugin>
> > > Regards Mirko
> > > --
> > > http://illegalstateexception.blogspot.com/
> > > https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
> > > https://bitbucket.org/mfriedenhagen/
> > >
> > >
> > > On Wed, Dec 2, 2015 at 9:57 PM, Martin Gainty <mgainty@hotmail.com>
> > wrote:
> > > > Folks-
> > > > is there any way to disable a particular plugin (which is somehow
> > declared as a default plugin for that phase )from executing in that phase?
> > > >
> > > > Thanks!
> > > > Martin
> > > > ______________________________________________
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> >
> >
> 
> 
> 
> -- 
> Adrien Rivard
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message