As a work-around, you can add the modify the TestSourceProcessorMojo
(maven-compile-plugin) by adding the pattern to the exclude list.
excludeList.add( "*.suo" );
excludeList.add( "*.csproj" );
excludeList.add( "*.sln" );
excludeList.add( "obj/**" );
On 6/28/07, Evan Worley <[EMAIL PROTECTED]> wrote:
Hi Brian,
There is a JIRA, http://jira.codehaus.org/browse/NMAVEN-78 which is
related. Essentially the test-plugin grabs everything as a build test
source instead of looking for only "test sources"
-Evan
On 6/28/07, Deacon, Brian <[EMAIL PROTECTED]> wrote:
>
> > So I've got this in build/plugins:
> > <plugin>
> > <groupId>org.apache.maven.dotnet.plugins</groupId>
> > <artifactId>maven-test-plugin</artifactId>
> > <version>0.14-SNAPSHOT</version>
> > <extensions>true</extensions>
> > <configuration>
> >
> > <reportsDirectory>${basedir}/target/nunit-log</reportsDirectory>
> > <compilerArgument>/debug:full</compilerArgument>
> > </configuration>
> > </plugin>
> >
> > But the csc call that gets made as a result when trying to generate
> > the test assembly has:
> > /recurse:c:\blah\blah\target\build-test-sources\**
> >
> > So it's spitting out all kinds of syntax errors because the test
> > assembly contains .resx and other things that it is trying to compile
> > as c# content, which of course it isn't.
> >
> > Oh, and my only other settings in the <build> element are:
> >
> > <finalName>${artifactId}</finalName>
> > <sourceDirectory>../src/dotnet</sourceDirectory>
> > <testSourceDirectory>../test/dotnet</testSourceDirectory>
> >
> > So, firstly, I need it to stop treating the resources like source
> > code, then secondly, I need it to actually compile those resources
> > into the assembly. Anybody have the answer in their back pocket?
> >
> > Brian
>
