NMaven (Retired)
  1. NMaven (Retired)
  2. NMAVEN-199

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

    Details

    • Type: New Feature New Feature
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.14 (Unreleased), 0.16
    • Fix Version/s: 0.14 (Unreleased)
    • Component/s: ASP support
    • Labels:
      None
    • Number of attachments :
      16

      Description

      http://docs.codehaus.org/display/MAVENUSER/NMaven+and+ASP+.NET

      It should run

      aspnet_compiler.exe -v /artifactId -p artifactId\ -u -f  target\artifactId
      
      1. maven-aspx-plugin.tgz
        5 kB
        Carlos Sanchez
      2. NMaven.WebService.tgz
        15 kB
        Carlos Sanchez
      3. nmaven-199.patch
        1 kB
        Carlos Sanchez
      4. NMAVEN-199-1.patch
        18 kB
        jan ancajas
      5. NMAVEN-199-3.zip
        7 kB
        jan ancajas

        Issue Links

          Activity

          Hide
          Carlos Sanchez added a comment -

          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

          Show
          Carlos Sanchez added a comment - 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
          Hide
          jan ancajas added a comment -

          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)

          Show
          jan ancajas added a comment - 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)
          Hide
          Carlos Sanchez added a comment -

          Updated aspx plugin that does the packaging too

          Show
          Carlos Sanchez added a comment - Updated aspx plugin that does the packaging too
          Hide
          Carlos Sanchez added a comment -

          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?

          Show
          Carlos Sanchez added a comment - 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?
          Hide
          Carlos Sanchez added a comment -

          Fixed the previous problem and add 2 integration tests

          Show
          Carlos Sanchez added a comment - Fixed the previous problem and add 2 integration tests

            People

            • Assignee:
              Unassigned
              Reporter:
              Carlos Sanchez
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: