When Using site goal on NetBeans Parent module it fails - Unable to resolve nbm-file artifact

the nbm-file type (and nbm for that matter) will only correctly be identified when the nbm-plugin is defined for the project and has the <extensions>true</extensions>. beware that while the "nbm" type gets resolved, it gets resolved wrongly as correctly it shall be a jar file without the transitive dependencies, but without extensions set, it resolves to the nbm file, rather than the jar file.

Here is a snipet of my POM file in the top level parent project NB App Parent.

<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>nbm-maven-plugin</artifactId>
<version>3.4</version>
<extensions>true</extensions>
<configuration>
<brandingToken>$

</cluster>
</configuration>
</plugin>
<plugin>
<!-- NetBeans 6.9+ requires JDK 6 -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.3.1</version>
<configuration>
<useDefaultManifestFile>true</useDefaultManifestFile>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>3.0-beta-2</version>
</plugin>
</plugins>
</pluginManagement>
</build>

I am reproducing this with 3.6 final, site 3.0, and mvn 3.0.3. Once caveat is that the NB pom is a sub of a larger aggregate project. For instance I have the layout:

parent
-NB
--application
--branding
--main module
--other module
-Some other
--Another sub
--Another sub2

I can run site:site from the NB folder, but I can not from the parent folder or I get this exact message. Jesse, are you able to reproduce like that? I will attempt to create a very simple use case for this using NB 7.0.1. If you have the ability to reopen issues here, then maybe you can. I can not as I don't have permissions.

Thanks

I am not able to reproduce it. If you can, please create a self-contained minimal test case (presumably a ZIP of a clean reactor tree plus instructions on which goal/phase to run with a specific Maven version) and attach it here.