Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.0
    • Component/s: Maven Plugins
    • Labels:
      None
    • Codeplex ID:
      9603

      Description

      if you use a dep like the following:
      <dependency>
      <groupId>it.bz.prov.Schools.Popcorn</groupId>
      <artifactId>Services.Common</artifactId>
      <version>$

      {project.version}</version>
      <type>library</type>
      </dependency>

      npanday fails:
      NFO: NPANDAY-180-014: Problem in resolving artifact: Assembly Artifact Id = Services.Common, Type = library, Message = Unable to download the artifact from any repository
      25-mar-2009 11.52.56 npanday.dao.impl.ProjectDaoImpl storeProjectAndResolveDependencies
      INFO: NPANDAY-180-018: Retrieving artifact: Artifact ID = Services.Common
      java.io.IOException: NPANDAY-180-020: Problem in resolving artifact: Assembly Artifact Id = Services.Common, Type = library, Local Path Check = C:\Documents and Settings\Administrator\.m2\uac\gac_msil\Services.Common\${project.version}

      __it.bz.prov.Schools.Popcorn\Services.Common.dll, Message = Unable to download the artifact from any repository
      at npanday.dao.impl.ProjectDaoImpl.storeProjectAndResolveDependencies(ProjectDaoImpl.java:733)
      at npanday.dao.impl.ProjectDaoImpl.storeModelAndResolveDependencies(ProjectDaoImpl.java:799)
      at npanday.artifact.impl.ArtifactInstallerImpl.installArtifactWithPom(ArtifactInstallerImpl.java:417)
      at npanday.plugin.install.InstallerMojo.execute(InstallerMojo.java:179)
      at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
      at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
      at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
      at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
      at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
      at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
      at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
      [INFO] ------------------------------------------------------------------------

        Issue Links

          Activity

          Hide
          Brett Porter added a comment -

          we have to fix this in 2.0 with the removal of the RDF store

          Show
          Brett Porter added a comment - we have to fix this in 2.0 with the removal of the RDF store
          Hide
          ingeo added a comment -

          Using a variable within the version node in the pom.xml does not work correctly.

          eg: <version>$

          {buildVersion}</version>

          Setting the custom variable using the following syntax works fine in a Java maven project but does not work with nPanday.

          > mvn clean install -DbuildVersion=0.0.0.5

          The build will complete "successfully" and the DLL will deploy to the local repo as MyLibrary\0.0.0.5\MyLibrary-0.0.0.5.dll but the following is not handled correctly:

          * The assembly is not updated correctly. The DLL is still identified with the previous version
          * The pom file for the library still has <version>${buildVersion}

          </version> instead of <version>0.0.0.5</version>

          The following error is thrown in the AbstractCompilerMojo.

          View the error log here (http://paste-bin.com/view/36555ecb)

          Show
          ingeo added a comment - Using a variable within the version node in the pom.xml does not work correctly. eg: <version>$ {buildVersion}</version> Setting the custom variable using the following syntax works fine in a Java maven project but does not work with nPanday. > mvn clean install -DbuildVersion=0.0.0.5 The build will complete "successfully" and the DLL will deploy to the local repo as MyLibrary\0.0.0.5\MyLibrary-0.0.0.5.dll but the following is not handled correctly: * The assembly is not updated correctly. The DLL is still identified with the previous version * The pom file for the library still has <version>${buildVersion} </version> instead of <version>0.0.0.5</version> The following error is thrown in the AbstractCompilerMojo. View the error log here ( http://paste-bin.com/view/36555ecb )

            People

            • Assignee:
              Unassigned
              Reporter:
              jedioetzi
            • Votes:
              4 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development