Am 02.06.2015 8:28 nachm. schrieb Anton Tanasenko <[email protected]>: > > That's the point. You don't have to specify an execution phase if a default > one is set. > But you do have to express your intent to execute the mojo during build by > specifying an execution itself.
Okay, I see! Thanks for your support! > > In case of dependency:unpack, its > <plugin> > ... > <executions> > <execution> > <id>..</id> > <goals><goal>unpack</goal></goals> > <configuration>...</configuration> > </execution> > </executions> > </plugin> > > See, no phase. > > 2015-06-02 20:16 GMT+03:00 Thomas Meyer <[email protected]>: > > > > > Am 02.06.2015 6:58 nachm. schrieb Anton Tanasenko <[email protected] > > >: > > > > > > Hi, you probably missed the previous section: > > > > > > > Oops :-) > > > > Okay, I understand now. > > > > But one more question: what use has the assigned default life cycle of the > > resp Mojo class when you need to explicitly specify the execution phase in > > the pom? > > > > > If you intend to configure this mojo for execution on the command line > > > using: > > > mvn dependency:copy > > > > > > you must not put the configuration inside the executions tag. Your > > > configuration should look like this: > > > ... > > > > > > 2015-06-02 19:36 GMT+03:00 Thomas Meyer <[email protected]>: > > > > > > > Hi, > > > > > > > > I've a question regarding the maven dependency plugin: > > > > > > > > In the usage description ( > > > > https://maven.apache.org/plugins/maven-dependency-plugin/usage.html ) > > in > > > > section "The dependency:unpack mojo" it's written that: > > > > > > > > "you must not put the configuration inside the executions tag. Your > > > > configuration should look like this:" > > > > > > > > But this doesn't seem to be true as the plugin seems not get executed > > at > > > > all, at least for a project with package type "war". > > > > > > > > So what am I missing here? > > > > Any ideas? > > > > > > > > My expectation was that the plugin gets executed in the generated > > sources > > > > phase. > > > > > > > > Here an excerpt of my pom file: > > > > > > > > <build> > > > > [...] > > > > <plugins> > > > > <plugin> > > > > <artifactId>maven-dependency-plugin</artifactId> > > > > <version>2.10</version> > > > > <configuration> > > > > <artifactItems> > > > > <artifactItem> > > > > [...] > > > > </artifactItem> > > > > </artifactItems> > > > > </configuration> > > > > </plugin> > > > > <plugin> > > > > <groupId>org.bsc.maven</groupId> > > > > <artifactId>maven-processor-plugin</artifactId> > > > > <version>2.2.4</version> > > > > <executions> > > > > <execution> > > > > <id>process</id> > > > > <phase>generate-sources</phase> > > > > <goals> > > > > <goal>process</goal> > > > > </goals> > > > > </execution> > > > > </executions> > > > > <configuration> > > > > <defaultOutputDirectory> > > > > ${project.build.directory}/generated-sources > > > > </defaultOutputDirectory> > > > > <processors> > > > > <processor>org.mapstruct.ap.MappingProcessor</ > > > > processor> > > > > </processors> > > > > </configuration> > > > > <dependencies> > > > > <dependency> > > > > <groupId>org.mapstruct</groupId> > > > > <artifactId>mapstruct-processor</artifactId> > > > > <version>${version.mapstruct}</version> > > > > </dependency> > > > > </dependencies> > > > > </plugin> > > > > > > > > I'm using maven 3.3.1. > > > > > > > > With kind regards > > > > Thomas > > > > > > > > > > > > > > > -- > > > Regards, > > > Anton. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > -- > Regards, > Anton.
