[jira] Commented: (NPANDAY-327) dependency management not working

[Brett Porter (JIRA)]

[ 
https://issues.apache.org/jira/browse/NPANDAY-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919746#action_12919746
 ] 

Brett Porter commented on NPANDAY-327:
--

unfortunately we've inherited a subsystem that duplicates a lot of Maven 
functionality without completely replicating it. We're looking to remove it - 
see the related issue.


 dependency management not working
 -

 Key: NPANDAY-327
 URL: https://issues.apache.org/jira/browse/NPANDAY-327
 Project: NPanday
  Issue Type: Bug
Affects Versions: 1.2, 1.2.1
 Environment: windows 7 32 bits. maven 2.0.9, java 6 sdk eng.
Reporter: sergio rupena

 I have a parent pom that declares a config section like this:
 dependencyManagement
 dependencies
 dependency
 groupIdLogging/groupId
 artifactIdlog4net/artifactId
 version1.2.10.0/version
 typedotnet-library/type
 /dependency
 /dependencies
 /dependencyManagement
 When I refer to my parent pom and use the following section (without 
 explicitly denoting the version)
 dependency
 groupIdLogging/groupId
 artifactIdlog4net/artifactId 
 typedotnet-library/type
 /dependency
 I can successfully do a maven test. (mvn test)
 However, when I do a maven install I get the following error:
 [INFO] Trace
 java.lang.NullPointerException
 at npanday.dao.Project.hashCode(Project.java:329)
 at java.util.HashMap.put(HashMap.java:372)
 at java.util.HashSet.add(HashSet.java:200)
 at npanday.dao.Project.addProjectDependency(Project.java:204)
 at npanday.dao.ProjectFactory.createProjectFrom(ProjectFactory.java:148)
 at 
 npanday.dao.impl.ProjectDaoImpl.storeModelAndResolveDependencies(ProjectDaoImpl.java:837)
 at 
 npanday.artifact.impl.ArtifactInstallerImpl.installArtifactWithPom(ArtifactInstallerImpl.java:399)
 at npanday.plugin.install.InstallerMojo.execute(InstallerMojo.java:177)
 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)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
 at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
 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)
 I think that dependency management is one of the great features from maven, 
 but it doesn't seem to be working in npanday.
 /joe

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (NPANDAY-231) Remove RDF repository and model

[Brett Porter (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NPANDAY-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brett Porter updated NPANDAY-231:
-

Fix Version/s: (was: Backlog)
   2.0

 Remove RDF repository and model
 ---

 Key: NPANDAY-231
 URL: https://issues.apache.org/jira/browse/NPANDAY-231
 Project: NPanday
  Issue Type: Bug
  Components: Maven Plugins
Reporter: Brett Porter
Priority: Critical
 Fix For: 2.0


 This will be a significant change to the way NPanday works internally, but 
 should have no external effect. We desire to have it more closely work with 
 Maven's dependency resolution, as the RDF adds no value and produces a number 
 of confusing results and error messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (NPANDAY-288) Support for VS 2010 and .NET Framework 4.0

[Adelita L. Padilla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NPANDAY-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adelita L. Padilla resolved NPANDAY-288.


Resolution: Fixed

 Support for VS 2010 and .NET Framework 4.0
 --

 Key: NPANDAY-288
 URL: https://issues.apache.org/jira/browse/NPANDAY-288
 Project: NPanday
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Lars Corneliussen
Assignee: Adelita L. Padilla
 Fix For: 2.0


 VS 2010 and .NET Framework 4.0 has shipped a while ago.
 We also have a patch in the queue that does some of the work:
  * 6036 by crimmc, 
 http://npanday.codeplex.com/Project/Download/FileDownload.aspx?DownloadId=124562
 blockquote
 Here are the changes, this release holds:
 1. Allow to work with .NET Framework 4.0 gac files. Added (gac_msil4) archive 
 type;
 2. Allow to use embeded resources when building DLLs (added for NHibernate);
 3. Allow to compile ASP.NET projects with dependencies from 4.0 gac files;
 4. Alow to run NUnit tests developed with .NET Framework 4.0;
 5. Allow to run NPanday on Windows 7 systems;
 /blockquote

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.