npanday Issue Tracker Rss Feed

Closed Issue: Document Workaround: GAC install fails with access denied when UAC is turned on [13179]

apadilla — Thu, 16 May 2013 06:33:52 GMT

I'm running on Windows 7 (UAC).

mvn install fails with 'access denied' because it can't register the NPanday.Model.Pom assembly to the gac.

Resources that helped:
* http://completedevelopment.blogspot.com/2009/12/adding-permissions-to-add-items-to-gac.html
* http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=472139&SiteID=1

On my machine I had to turn off UAC or run the shell as Administrator.

Running it as Administrator installs it to the Administrator-Repo, though.

Closed Issue: compile-plugin has two deploy phases for ArtifactType.NETPLUGIN [13198]

jocaba — Thu, 16 May 2013 06:33:51 GMT

Maybe package was intended for goal 'npanday.plugin:maven-mojo-generator-plugin:generate-bindings'?

forType( ArtifactType.NETPLUGIN ) {
LifecycleMappingBuilder b->
b.validate (default_validate)
b.generate_sources (default_generate_sources)
b.process_sources (default_process_sources)
b.process_resources (default_process_resources)
b.compile (np_compile)
b.test_compile (np_test_compile)
b.deploy ('npanday.plugin:maven-mojo-generator-plugin:generate-bindings')
b.test (np_test)
b.install (default_install)
b.deploy (np_convert, mv_deploy)
}

Closed Issue: npe building gac artifact [13461]

jocaba — Thu, 16 May 2013 06:33:50 GMT

Sorry, I can't remember what I was building at the time, except that it was part of the npanday trunk source tree, but I do know that it was building an artifact of type ArtifactType.GAC, and an NPE was thrown. Patch attached.

Closed Issue: add missing dependencies to dotnet poms [13462]

jocaba — Thu, 16 May 2013 06:33:50 GMT

Fixes for issue #13018 made it that transitive dependencies are no longer passed to csc. This patch makes explicit additional dependencies for several of the dotnet projects.

Closed Issue: support jar style custom manifest entries in assemblies [13477]

jocaba — Thu, 16 May 2013 06:33:50 GMT

In our jar, war, and ear builds we add custom build time information into the MANIFEST.MF file. For example, we add build time stamps, and svn information. This patch attempts to do the same for assemblies, using a custom assembly level attribute.

e.g., in your pom, put something like this:

<plugin>
<groupId>npanday.plugin</groupId>
<artfiactId>maven-compile-plugin</artifactId>
<configuration>
<assemblyInfo>
<svn.version>${my.svn.version}</svn.version>
<asdf>${any.normal.maven.property}</asdf>
</assemblyInfo>
</configuration>
</plugin>

Closed Issue: Update/Create all three "types" of assembly version during compile when it is not there (AssemblyInfo.cs) initially [13590]

artemfedorenko — Thu, 16 May 2013 06:33:48 GMT

Assembly version was not updated during compile. Related discussion: http://npanday.codeplex.com/Thread/View.aspx?ThreadId=215098
Apart from the issue mentioned in the discussion in the patch functionality for injecting build number (through BUILD_NUMBER environment variable) has been implemented. Although this is not related to the main issue but in this way AssemblyVersion, AssemblyFileVersion and AssemblyInformationlVersion updating during compile will be complete. If BUILD_NUMBER is not set there won't be any error.

I created a patch for it (see attachement)

Closed Issue: Resync references may cause timeouts after successive snapshot metadata retrievals [13758]

brettporter — Thu, 16 May 2013 06:33:47 GMT

If you attempt to download a snapshot which has an invalid maven-metadata.xml, the connection is not properly closed, and so subsequent attempts to download from the same host will timeout waiting for the prior connection.

Closed Issue: Resync Reference doesn't update SNAPSHOT artifact from local repository that already exist in .references folder [14093]

jocaba — Thu, 16 May 2013 06:33:46 GMT

Steps:
1. Install Library1 into local maven repo
2. Add Library1 as dependency using Resync Reference to ProjectA (it will be copied into .references folder)
3. Update and reinstall Library1 into local maven repo
4. Invoke Resync Reference for ProjectA
5. Error: Library1 won't be updated in .references folder

Expected: newer version (in terms of file timestamp) of Library1 (if any) should be copied into .references folder from local maven repo during Resync Reference

Issue exist in trunk r59731

Closed Issue: Documentation links broken. [15360]

LarsCorneliussen — Thu, 16 May 2013 06:33:45 GMT

Just letting you know in case you're not aware of it, the documentation links appear to be broken.

Created Issue: How to Build Entity Framework Project using Npanday [18698]

ketanbembi — Tue, 25 Sep 2012 06:50:05 GMT

I am using Npnday 1.5. I have tried to build my project using Npanday. But DLL generated using Npanday has some issue. Because When I replace that DLL with other DLL which is generated by Visual Studio 2010, then my web application runs perfectly.

Have any one buid Entity Framework Project using Napanday??

Please tell me What are the steps required to build an entity framework project using Npanday.
Mainly what changes are required to do in POM.xml file???

Closed Issue: Build failed in Npanday [14966]

LarsCorneliussen — Tue, 05 Apr 2011 14:47:00 GMT

[INFO]
[INFO] --- NPanday.Plugin.Settings.JavaBinding:1.2.1:generate-settings (default-
generate-settings) @ MavenBuildTesting ---
[INFO] The input line is too long.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.922s
[INFO] Finished at: Mon Dec 27 15:54:09 IST 2010
[INFO] Final Memory: 4M/8M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal npanday.plugin:NPanday.Plugin.Settings.JavaBindin
g:1.2.1:generate-settings (default-generate-settings) on project MavenBuildTesti
ng: NPANDAY-xxx-000: NPANDAY-063-000: Execution Path = C:\pab\gac_msil\NPanday.P
lugin.Runner\1.2.1__npanday.plugin, Command = [parameterFile=C:\DOCUME~1\A466152
\LOCALS~1\Temp\Plugin11258.xml, assemblyFile=C:\pab\gac_msil\NPanday.Plugin.Sett
ings\1.2.1__npanday.plugin\NPanday.Plugin.Settings.dll, mojoName=NPanday.Plugin.
Settings.SettingsGeneratorMojo, startProcessAssembly=C:\pab\gac_msil\NPanday.Plu
gin.Loader\1.2.1__npanday.plugin\NPanday.Plugin.Loader.exe]: NPANDAY-040-001: Co
uld not execute: Command = cmd.exe /X /C ""NPanday.Plugin.Runner.exe parameterFi
le=C:\DOCUME~1\A466152\LOCALS~1\Temp\Plugin11258.xml assemblyFile=C:\pab\gac_msi
l\NPanday.Plugin.Settings\1.2.1__npanday.plugin\NPanday.Plugin.Settings.dll mojo
Name=NPanday.Plugin.Settings.SettingsGeneratorMojo startProcessAssembly=C:\pab\g
ac_msil\NPanday.Plugin.Loader\1.2.1__npanday.plugin\NPanday.Plugin.Loader.exe"",
Result = 1 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal n
panday.plugin:NPanday.Plugin.Settings.JavaBinding:1.2.1:generate-settings (defau
lt-generate-settings) on project MavenBuildTesting: NPANDAY-xxx-000
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:203)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:148)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:140)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu
ild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
eStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:134)
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:585)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
cher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
a:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
uncher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
352)
Caused by: org.apache.maven.plugin.MojoExecutionException: NPANDAY-xxx-000
at npanday.plugin.AbstractMojo.execute(AbstractMojo.java:169)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:107)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:195)
... 19 more
Caused by: npanday.executable.ExecutionException: NPANDAY-063-000: Execution Pat
h = C:\pab\gac_msil\NPanday.Plugin.Runner\1.2.1__npanday.plugin, Command = [para
meterFile=C:\DOCUME~1\A466152\LOCALS~1\Temp\Plugin11258.xml, assemblyFile=C:\pab
\gac_msil\NPanday.Plugin.Settings\1.2.1__npanday.plugin\NPanday.Plugin.Settings.
dll, mojoName=NPanday.Plugin.Settings.SettingsGeneratorMojo, startProcessAssembl
y=C:\pab\gac_msil\NPanday.Plugin.Loader\1.2.1__npanday.plugin\NPanday.Plugin.Loa
der.exe]
at npanday.executable.impl.DefaultRepositoryNetExecutable.execute(Defaul
tRepositoryNetExecutable.java:97)
at npanday.plugin.AbstractMojo.execute(AbstractMojo.java:159)
... 21 more
Caused by: npanday.executable.ExecutionException: NPANDAY-040-001: Could not exe
cute: Command = cmd.exe /X /C ""NPanday.Plugin.Runner.exe parameterFile=C:\DOCUM
E~1\A466152\LOCALS~1\Temp\Plugin11258.xml assemblyFile=C:\pab\gac_msil\NPanday.P
lugin.Settings\1.2.1__npanday.plugin\NPanday.Plugin.Settings.dll mojoName=NPanda
y.Plugin.Settings.SettingsGeneratorMojo startProcessAssembly=C:\pab\gac_msil\NPa
nday.Plugin.Loader\1.2.1__npanday.plugin\NPanday.Plugin.Loader.exe"", Result = 1

at npanday.executable.CommandExecutor$Factory$1.executeCommand(CommandEx
ecutor.java:371)
at npanday.executable.impl.DefaultRepositoryNetExecutable.execute(Defaul
tRepositoryNetExecutable.java:93)
... 22 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
Comments:

I added some comments on the corresponding Jira-issue:

https://issues.apache.org/jira/browse/NPANDAY-366

Commented Issue: Build failed in Npanday [14966]

brettporter — Mon, 04 Apr 2011 12:16:00 GMT

This is fixed in trunk, but the project has moved to http://incbuator.apache.org/npanday/. We are working on release candidates at the moment.

Commented Issue: Build failed in Npanday [14966]

cdossantos — Mon, 04 Apr 2011 08:02:46 GMT

Hello,

We are just evaluating NPanday for C# projects and got the the same error. Is there a workaround?

Thanks in advance,

Santos

Commented Issue: Build failed in Npanday [14966]

KenFromNN — Wed, 09 Mar 2011 14:24:33 GMT

I have the same error when trying to build sample .NET project.

I just installed the nPanday and created sample project with the following command:
mvn archetype:generate -DarchetypeArtifactId=maven-archetype-dotnet-simple -DarchetypeGroupId=npanday -DarchetypeVersion=1.2.1

After that I executed the mvn compile command and got the error.

It seems that calling cmd.exe /X /C "ARG" with ARG length > 260 symbols cause this error.
I did not get this error when try to execute ARG itself in console.

Console output is attached.

[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.example:Example.Project:library:1.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for npanday.plugin:maven-compile-plugin is missing. @ line 21, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Example.Project 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] — maven-compile-plugin:1.2.1:initialize (default-initialize) @ Example.Project —
[INFO] Mojo Execution Time = 266
[INFO]
[INFO] — maven-resolver-plugin:1.2.1:resolve (default-resolve) @ Example.Project —
[INFO] Mojo Execution Time = 0
[INFO]
[INFO] — NPanday.Plugin.Settings.JavaBinding:1.2.1:generate-settings (default-generate-settings) @ Example.Project —
[INFO] The input line is too long.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.234s
[INFO] Finished at: Wed Mar 09 12:11:30 GMT 2011
[INFO] Final Memory: 5M/15M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal npanday.plugin:NPanday.Plugin.Settings.JavaBinding:1.2.1:generate-settings (default-generate-settings) on project Example.Project: NPANDAY-xxx-000: NPANDAY-063-000: Execution Path = C:\DEV\Maven\pab\gac_msil\NPanday.Plugin.Runner\1.2.1__npanday.plugin, Command = [parameterFile=C:\DEV\Temp\WinTmp\Plugin1630420998735221868.xml, assemblyFile=C:\DEV\Maven\pab\gac_msil\NPanday.Plugin.Settings\1.2.1__npanday.plugin\NPanday.Plugin.Settings.dll, mojoName=NPanday.Plugin.Settings.SettingsGeneratorMojo, startProcessAssembly=C:\DEV\Maven\pab\gac_msil\NPanday.Plugin.Loader\1.2.1__npanday.plugin\NPanday.Plugin.Loader.exe]: NPANDAY-040-001: Could not execute: Command = cmd.exe /X /C ""NPanday.Plugin.Runner.exe parameterFile=C:\DEV\Temp\WinTmp\Plugin1630420998735221868.xml assemblyFile=C:\DEV\Maven\pab\gac_msil\NPanday.Plugin.Settings\1.2.1_npanday.plugin\NPanday.Plugin.Settings.dll mojoName=NPanday.Plugin.Settings.SettingsGeneratorMojo startProcessAssembly=C:\DEV\Maven\pab\gac_msil\NPanday.Plugin.Loader\1.2.1_npanday.plugin\NPanday.Plugin.Loader.exe"", Result = 1 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal npanday.plugin:NPanday.Plugin.Settings.JavaBinding:1.2.1:generate-settings (default-generate-settings) on project Example.Project: NPANDAY-xxx-000
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: NPANDAY-xxx-000
at npanday.plugin.AbstractMojo.execute(AbstractMojo.java:169)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: npanday.executable.ExecutionException: NPANDAY-063-000: Execution Path = C:\DEV\Maven\pab\gac_msil\NPanday.Plugin.Runner\1.2.1__npanday.plugin, Command = [parameterFile=C:\DEV\Temp\WinTmp\Plugin1630420998735221868.xml, assemblyFile=C:\DEV\Maven\pab\gac_msil\NPanday.Plugin.Settings\1.2.1__npanday.plugin\NPanday.Plugin.Settings.dll, mojoName=NPanday.Plugin.Settings.SettingsGeneratorMojo, startProcessAssembly=C:\DEV\Maven\pab\gac_msil\NPanday.Plugin.Loader\1.2.1__npanday.plugin\NPanday.Plugin.Loader.exe]
at npanday.executable.impl.DefaultRepositoryNetExecutable.execute(DefaultRepositoryNetExecutable.java:97)
at npanday.plugin.AbstractMojo.execute(AbstractMojo.java:159)
... 21 more
Caused by: npanday.executable.ExecutionException: NPANDAY-040-001: Could not execute: Command = cmd.exe /X /C ""NPanday.Plugin.Runner.exe parameterFile=C:\DEV\Temp\WinTmp\Plugin1630420998735221868.xml assemblyFile=C:\DEV\Maven\pab\gac_msil\NPanday.Plugin.Settings\1.2.1_npanday.plugin\NPanday.Plugin.Settings.dll mojoName=NPanday.Plugin.Settings.SettingsGeneratorMojo startProcessAssembly=C:\DEV\Maven\pab\gac_msil\NPanday.Plugin.Loader\1.2.1_npanday.plugin\NPanday.Plugin.Loader.exe"", Result = 1
at npanday.executable.CommandExecutor$Factory$1.executeCommand(CommandExecutor.java:371)
at npanday.executable.impl.DefaultRepositoryNetExecutable.execute(DefaultRepositoryNetExecutable.java:93)
... 22 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Commented Issue: Documentation links broken. [15360]

LarsCorneliussen — Mon, 28 Feb 2011 12:26:10 GMT

Just letting you know in case you're not aware of it, the documentation links appear to be broken.
Comments: ** Comment from web user: LarsCorneliussen **

Thank you for the hint. Should be fixed now.

Commented Issue: Documentation links broken. [15360]

brettporter — Mon, 21 Feb 2011 12:20:04 GMT

Just letting you know in case you're not aware of it, the documentation links appear to be broken.
Comments: ** Comment from web user: brettporter **

which links specifically? they are working for me...

Commented Issue: Documentation links broken. [15360]

smapjb — Mon, 21 Feb 2011 11:27:20 GMT

Just letting you know in case you're not aware of it, the documentation links appear to be broken.
Comments: ** Comment from web user: smapjb **

Yes the link on the site page at http://incubator.apache.org/npanday/ still point to old URL

So front page link to docs it still not working.

Commented Issue: Documentation links broken. [15360]

brettporter — Fri, 18 Feb 2011 02:52:48 GMT

Just letting you know in case you're not aware of it, the documentation links appear to be broken.
Comments: ** Comment from web user: brettporter **

Sorry about that. You can now find it here: http://incubator.apache.org/npanday/

Created Issue: Documentation links broken. [15360]

rob759 — Fri, 18 Feb 2011 01:45:39 GMT

Just letting you know in case you're not aware of it, the documentation links appear to be broken.

Created Issue: Build failed in Npanday [14966]

RajamohanR — Mon, 27 Dec 2010 10:52:17 GMT