Create an aspx-compiler-mojo for precompilation of ASP .NET pages

First issue I've found is that the destination of the files can't be inside the folder you are compiling

ie. aspx files are in $

/target

maybe compile to a temporary place and then move the files?

Also seems that aspnet_compiler compiles source code too

In the attached example I've run
aspnet_compiler.exe -v /NMaven.It.It0021 -p .\ -u -f %TMP%\NMaven.It.It0021

and I've got in %TMP%\NMaven.It.It0021

./assembly.xml
./bin
./bin/App_Code.compiled
./bin/App_Code.dll
./bin/App_Web_oerzama_.dll
./Default.aspx
./NMaven.WebApplication.sln
./pom.xml
./PrecompiledApp.config
./web.config

Initial IT test

Initial implementation.
Will add the built aspx pages as attached artifacts so they are used by the compiler plugin (they may be needed by a source file)
Patch needed to use attached artifacts as references during compilation

Complex example of a webservice application with webapp

can you please supply the posible tags for this plugin

attached initial draft for the aspx compiler mojo.

Plugin code after merging Jan's work with mine

I decided to use maven-aspx-plugin name so we can add more mojos related to aspx if needed and not limit the plugin just for compilation

The problem is that with a simple test I'm getting an error that wasn't able to figure out what's the problem yet, seems to be extensions related

[INFO] Internal error in the plugin manager executing goal 'org.apache.maven.dotnet.plugins:maven-resolver-plugin:0.14-incubating-SNAPSHOT:resolve': Unable to find the mojo 'org.apache.maven.dotnet.plugins:maven-resolver-plugin:0.14-incubating-SNAPSHOT:resolve' in the plugin 'org.apache.maven.dotnet.plugins:maven-resolver-plugin'
Component descriptor cannot be found in the component repository: org.apache.maven.artifact.handler.ArtifactHandlerasp.

Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Component descriptor cannot be found in the component repository: org.apache.maven.artifact.handler.ArtifactHandlerasp.

Attached updated simple IT test

attached updated patch(nmaven-199-2.zip) after merging with carlos' changes yesterday.
changes
-commented unneeded entries / failing entries in components.xml (i'll dig deeper about the exception)
-added AspxCompiler.java and override "execute" to handle asp executable
-rearranged the parameters in the AspxCompilerMojo.java so that it won't be improperly quoted.

MavenITmng-0021-AspxCompilation should compile now.

i'd like to add the mojos:
-zipping the compiled asp project in the temp folder(because i'm not sure if we can still use maven-assembly-plugin)
-copying the zipped compiled asp project to local repo.

comments are welcome.

My mistake I had the wrong plugin name in the IT pom, attached the fixed IT. The compilation succeeds
After the aspnet compilation the files should be copied to the target folder from the temp folder

updated patch :
1. fix the ComponentLookupException ( was caused by missing artifact handler for asp in dotnet-artifact. )
2. reuse existing dotnet plugins applicable to aspx
3. copy the dependencies transitively to sourceDirectory/Bin folder
4. install the aspx artifact to local repository after compilation

(we can use the updated patch in NMAVEN-200 for zipping of artifact)

Updated aspx plugin that does the packaging too

Attached more complex example of a WebService app

Currently if fails for me with

java.lang.NullPointerException
at org.apache.maven.dotnet.vendor.impl.StateMachineProcessorImpl.process(StateMachineProcessorImpl.java:122)
at org.apache.maven.dotnet.executable.impl.NetExecutableFactoryImpl.getCompilerExecutableFor(NetExecutableFactoryImpl.java:100)
at org.apache.maven.dotnet.plugin.aspx.AspxCompilerMojo.execute(AspxCompilerMojo.java:208)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)

caused because in org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase:12
if ( object instanceof Initializable ) returns false

maybe a classpath issue?

Fixed the previous problem and add 2 integration tests