Plugin dependency not always included to classpath

Plugins not always see their dependencies.

For example. I got project with parent project -

• if I run mvn install on child project mvn package runs correctly.
• if i run mvn install on parent project then child project is build with error, plugin doesn't see their dependency and fails with class not found

Example of child project
Short example

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>

<parent>
<groupId>oss</groupId>
<artifactId>oss</artifactId>
<version>1.0.0-SNAPSHOT</version>
<relativePath>../pom.xml</relativePath>
</parent>

<groupId>oss</groupId>
<artifactId>oss-ws</artifactId>
<packaging>war</packaging>
(...)
<dependencies>
<dependency>
<groupId>${groupId}</groupId>
<artifactId>oss-rpc</artifactId>
<version>${version}</version>
<scope>provided</scope> <!-- if dependecy is compile evething runs ok-->
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jaxws-maven-plugin</artifactId>
<executions>
<execution>
<id>wsdl_generate_service_classes</id>
<phase>process-classes</phase>
<goals>
<goal>wsgen</goal>
</goals>
<configuration>
<genWsdl>true</genWsdl>
<sei>oss.ossServiceImpl</sei>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>${groupId}</groupId>
<artifactId>oss-rpc</artifactId>
<version>${version}</version>
</dependency>
</dependencies>
</plugin>
(...)

Parent project

(..)
<modules>
<module>oss</module>
</modules>