gmalartre
commented
10 years ago It would be nice to see this issue go, but anyway there are workarounds:
Reparenting the folder worked fine for me.
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
<phase>generate-sources</phase>
<configuration>
<tasks>
<copy todir="${project.build.directory}${file.separator}javascriptFramework${file.separator}output${file.separator}externDependencies" flatten="true">
<fileset dir="${project.build.directory}${file.separator}javascriptFramework${file.separator}output${file.separator}externDependencies${file.separator}externDependencies">
<exclude name="junit*" />
<include name="**/*.js"/>
</fileset>
</copy>
<delete>
<fileset dir="${project.build.directory}${file.separator}javascriptFramework${file.separator}output${file.separator}externDependencies${file.separator}externDependencies">
<include name="**/*"/>
</fileset>
</delete>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>
When adding other JSAR maven projects, if you have an externDependencies folder, it will create a never-ending nesting of this folder unto itself. Not sure where this is in the code, but no one is currently doing much with externDependencies, thankfully. Please let me know if anyone is using them and I'll look into it sooner.