NPanday
  1. NPanday
  2. NPANDAY-315

Error when building with a dependency on unmanaged code

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: None
    • Labels:
      None
    • Codeplex ID:
      13796

      Description

      I have a .Net "winexe" build project that needs to have a runtime dependency on a DLL containing un-managed (VC++) code. The pom dependency looks like this:

      <dependency>
      <groupId>some.group.id</groupId>
      <artifactId>someArtifactId</artifactId>
      <version>2.1.0-SNAPSHOT</version>
      <type>dll</type>
      <scope>runtime</scope>
      </dependency>

      When I go to compile, I get a NullPointerException in the plugin:

      [INFO] [compile:compile

      {execution: default-compile}

      ]
      [INFO] No Assembly Info File found
      [INFO] NPANDAY-066-013: Found Vendor = Vendor = MICROSOFT, Vendor Version = 3.5, Framework Version = 3.5, Executable Paths =
      [INFO] ------------------------------------------------------------------------
      [ERROR] FATAL ERROR
      [INFO] ------------------------------------------------------------------------
      [INFO] null
      [INFO] ------------------------------------------------------------------------
      [INFO] Trace
      java.lang.NullPointerException
      at npanday.executable.impl.CompilerContextImpl.init(CompilerContextImpl.java:393)
      at npanday.executable.impl.NetExecutableFactoryImpl.getCompilerExecutableFor(NetExecutableFactoryImpl.java:141)
      at npanday.plugin.compile.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:986)
      at npanday.plugin.compile.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:673)
      at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)

      If I remove the dependency, everything compiles fine, but I have to then manually copy the dependant DLL to the target directory to run / test. It would be great if this can be fixed so I can use maven-dependency-plugin to copy the runtime dependency to my build output directory and eliminate that manual step.

        Activity

        There are no comments yet on this issue.

          People

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

            Dates

            • Created:
              Updated:

              Development