Hi Bilen,

VS 2010 and Net 4.0 is not yet supported in NPanday 1.2.1.


However, we already have incorporated our fix for the ff support in our source 
code repository --> 
http://svn.apache.org/repos/asf/incubator/npanday/branches/npanday-vs2010-support/


You can try checking it out and the "how to" in building the source code can be 
found here -> http://www.npanday.org/docs/1.2/


Hope that helps.


Keep us posted.


Thanks! 


----- "Bilen Öğretmen" <ogretm...@gmail.com> wrote:

> Hi,
> I am using VS2010 and framework 4.0 in my project
> I downloaded NPanday 1.2.1 MSI installer and run the setup.
> Then I created a maven-archetype-dotnet-simple Hello world project.
> When I
> run "mvn install" I get the error below
> 
> [INFO] [NPanday.Plugin.Settings.JavaBinding:generate-settings
> {execution:
> defaul
> t-generate-settings}]
> [DEBUG] NPANDAY-102-012: Initialized rule factory
> repositoryRegistry:npanday.reg
> istry.impl.repositoryregistryi...@2153fe
> [DEBUG] NPANDAY-103-036.0: Respository registry:
> npanday.registry.impl.Repositor
> yregistryi...@2153fe
> [DEBUG] NPANDAY-102-001: Unable to initialize rule factory.
> npanday.InitializationException: NPANDAY-103-002: Unknown Default
> Vendor:
> Name =
> null
> at
> npanday.vendor.impl.VendorInfoTransitionRuleFactory.init(VendorInfoTr
> ansitionRuleFactory.java:111)
> at
> npanday.vendor.impl.StateMachineProcessorImpl.initialize(StateMachine
> ProcessorImpl.java:87)
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhas
> e.execute(InitializePhase.java:16)
> at
> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(Abstract
> LifecycleHandler.java:101)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startC
> omponentLifecycle(AbstractComponentManager.java:105)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.create
> ComponentInstance(AbstractComponentManager.java:95)
> at
> org.codehaus.plexus.component.manager.ClassicSingletonComponentManage
> r.getComponent(ClassicSingletonComponentManager.java:92)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
> ner.java:331)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assi
> gnRequirementToField(FieldComponentComposer.java:129)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.asse
> mbleComponent(FieldComponentComposer.java:73)
> at
> org.codehaus.plexus.component.composition.DefaultComponentComposerMan
> ager.assembleComponent(DefaultComponentComposerManager.java:68)
> at
> org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPl
> exusContainer.java:1486)
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPha
> se.execute(CompositionPhase.java:29)
> at
> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(Abstract
> LifecycleHandler.java:101)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startC
> omponentLifecycle(AbstractComponentManager.java:105)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.create
> ComponentInstance(AbstractComponentManager.java:95)
> at
> org.codehaus.plexus.component.manager.PerLookupComponentManager.getCo
> mponent(PerLookupComponentManager.java:48)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
> ner.java:331)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
> ner.java:440)
> at
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul
> tPluginManager.java:652)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:468)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.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:6
> 0)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.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)
> [DEBUG] Configuring mojo
> 'npanday.plugin:maven-compile-plugin:1.2.2-incubating-S
> NAPSHOT:generate-assembly-info' -->
> [DEBUG] (f) language = C_SHARP
> [DEBUG] (f) project = MavenProject: DENEME:EX:1.0-SNAPSHOT @
> C:\Documents
> and
> Settings\bilen.ogretmen\EX\pom.xml
> [DEBUG] (f) sourceDirectory = C:\Documents and
> Settings\bilen.ogretmen\EX\src\
> main\csharp
> [DEBUG] -- end configuration --
> [INFO] [compile:generate-assembly-info {execution:
> default-generate-assembly-inf
> o}]
> [INFO] NPANDAY-902-000: Generating Assembly Info: Language = C_SHARP
> [DEBUG] NPANDAY-102-002: Apply
> rule:npanday.vendor.impl.VendorInfoTransitionRule
> factory...@1159e0c
> [DEBUG] NPANDAY-103-016: Entering State = FFF
> [DEBUG] NPANDAY-102-003: Vendor info after rule:Vendor = null, Vendor
> Version =
> null, Framework Version = null, Executable Paths =
> [DEBUG] NPANDAY-102-002: Apply
> rule:npanday.vendor.impl.VendorInfoTransitionRule
> factor...@3b5699
> [DEBUG] NPANDAY-103-034: Entering State = Post Process
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> java.lang.NullPointerException
> at
> npanday.vendor.impl.VendorInfoRepositoryImpl.getSdkInstallRootFor(Ven
> dorInfoRepositoryImpl.java:98)
> at
> npanday.vendor.impl.VendorInfoTransitionRuleFactory$1.process(VendorI
> nfoTransitionRuleFactory.java:132)
> at
> npanday.vendor.impl.StateMachineProcessorImpl.process(StateMachinePro
> cessorImpl.java:131)
> at
> npanday.plugin.compile.AssemblyInfoGeneratorMojo.execute(AssemblyInfo
> GeneratorMojo.java:185)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.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:6
> 0)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.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]
> ------------------------------------------------------------------------
> [INFO] Total time: 12 seconds
> [INFO] Finished at: Wed Dec 01 15:09:00 EET 2010
> [INFO] Final Memory: 16M/35M
> [INFO]
> ------------------------------------------------------------------------
> 
> 
> 
> Than, I tried building Npanday from svn (npanday-vs2010-support
> branch)
> It failed at "mvn clean install" step with the following error
> 
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building NPanday :: .NET Model :: POM
> [INFO] task-segment: [install]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [compile:initialize {execution: default-initialize}]
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [jar:file:/C:/Documents and
> Settings/bilen.ogretmen/.m2/
> repository/org/sonatype/gossip/gossip/1.0/gossip-1.0.jar!/org/slf4j/impl/StaticL
> oggerBinder.class]
> SLF4J: Found binding in [jar:file:/C:/Documents and
> Settings/bilen.ogretmen/.m2/
> repository/org/slf4j/slf4j-jdk14/1.5.11/slf4j-jdk14-1.5.11.jar!/org/slf4j/impl/S
> taticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> 
> 01.Ara.2010 14:40:49 npanday.registry.ConnectionsRepository lazyLoad
> INFO: NPANDAY-080-001: Adding data access object: Class Name =
> npanday.dao.impl.
> ProjectDaoImpl
> 01.Ara.2010 14:40:49 npanday.registry.ConnectionsRepository lazyLoad
> INFO: NPANDAY-080-004: Connection Start Up: Time = 63
> 01.Ara.2010 14:40:49 npanday.dao.impl.ProjectDaoImpl
> storeProjectAndResolveDepen
> dencies
> INFO: Detected jar dependency - skipping: Artifact Dependency ID =
> junit
> 01.Ara.2010 14:40:49 npanday.dao.impl.ProjectDaoImpl
> storeProjectAndResolveDepen
> dencies
> INFO: Detected jar dependency - skipping: Artifact Dependency ID =
> easymock
> [INFO] Mojo Execution Time = 156
> [INFO] [resolver:resolve {execution: default-resolve}]
> [INFO] [NPanday.Plugin.Settings.JavaBinding:generate-settings
> {execution:
> defaul
> t-generate-settings}]
> [INFO] [compile:generate-assembly-info {execution:
> default-generate-assembly-inf
> o}]
> [INFO] NPANDAY-902-000: Generating Assembly Info: Language = C_SHARP
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at
> npanday.plugin.compile.AssemblyInfoGeneratorMojo.execute(AssemblyInfo
> GeneratorMojo.java:185)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.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:6
> 0)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.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]
> ------------------------------------------------------------------------
> [INFO] Total time: 2 minutes 8 seconds
> [INFO] Finished at: Wed Dec 01 14:41:03 EET 2010
> [INFO] Final Memory: 58M/63M
> [INFO]
> ------------------------------------------------------------------------
> 
> what is wrong in Npanday with framework 4.0, could someone explain the
> steps
> of running Npanday with Framework 4.0?
> Bilen Öğretmen

Reply via email to