NPanday 1.2-RC3 now ready for testing

Developer
Jun 6, 2010 at 4:34 PM
Edited Jun 7, 2010 at 11:54 AM

Hi All,

 

NPanday 1.2-RC3 is now ready for testing.

 

tag - >https://npanday.svn.codeplex.com/svn/releases/npanday-project-1.2-RC3/

npanday-repository-builder -> http://repo.npanday.org/archiva/repository/npanday-releases/npanday/npanday-repository-builder/1.2-RC3/npanday-repository-builder-1.2-RC3-bin.tar.gz

npanday installer -> http://repo.npanday.org/archiva/repository/npanday-releases/npanday/npanday-installer/1.2-RC3/npanday-installer-1.2-RC3.msi

 

To be able to use the installer successfully, manually change the location of the local repository during installation.

 

Thanks!

Jun 7, 2010 at 2:10 AM

Thanks Liit! :) I'll try out the new RC today.

Coordinator
Jun 7, 2010 at 2:15 AM

Thanks Liit,

I'll post my results after trying 1.2-RC3

Coordinator
Jun 7, 2010 at 11:40 AM

Hi,

This is testing was done by building from the source of the 1.2-RC3

Most of the project types work fine for me except for the regression in wpf project types, I get a null pointer exception when building the project.

 

Still need to test using the installer and the repository builder.

 

Developer
Jun 7, 2010 at 12:25 PM

Hi All,

 

I was able to verify some of the issues included for the 1.2 release and they all passed.

 

I only got build error when building wpf and mvc projects.

 

I was able to use NPanday successfully through the souce code in the 1.2-RC3 tag and using the installer.  Although in the installer, I have to manually add the uac\gac_msil folder in the local repository.

 

Thanks!

Developer
Jun 7, 2010 at 12:27 PM

I was not able to successfully install NPanday using the npanday-repository-builder coz when I run this command mvn npanday.plugin:maven-vsinstaller-plugin:install, I got this error - > http://pastie.org/994802

 

I'll investigate the mapping of the artifacts.

 

Thanks!

Developer
Jun 8, 2010 at 6:11 AM
Edited Jun 8, 2010 at 6:12 AM

Why do I have to edit the repo-location manually? Shouldn't it be detected? Or at least default to my user home?

Developer
Jun 8, 2010 at 6:54 AM
I have a number of failing tests in its. But I had some problems with svn - couldn't update and had little time. So I ran an old version (r51768) of its against the RC-3. Tests in error: testMVCProject(npanday.its.NPandayIT11480MVCProjectTest) testWpfProject(npanday.its.NPandayIT12549WpfProjectTest) testMsBuildCopyReferences(npanday.its.NPandayIT11695MsBuildCopyReferencesTest) testMsBuildErrorsHandled(npanday.its.NPandayIT11637MsBuildErrorHandlingTest) testResGenWithErrorInFileName(npanday.its.NPandayIT9903ResGenWithErrorInFileNameTest) testWebAppInstall(npanday.its.NPandayITWebAppInstallTest) testWebAppInstall(npanday.its.NPandayITVBWebAppTest) testCompileExclusions(npanday.its.NPandayIT0032VerifyInstallationTest) There are some rights-problems I had before with the webapp... Just see if you can get anything out of it... I can have a look in about 10 hours. No time now. I dropped the results here: http://drop.io/1kxkvrt
Jun 8, 2010 at 8:47 AM

I'm also getting an error when installing 1.2-RC3 using the VSInstaller plugin. But the error I got is different from Liit's:

Jun 8, 2010 3:44:26 PM npanday.dao.impl.ProjectDaoImpl storeProjectAndResolveDependencies
INFO: NPANDAY-180-018: Retrieving artifact: Artifact ID  = NPanday.Model.Pom
Downloading: http://repo.npanday.org/archiva/repository/npanday-releases/npanday/model/NPanday.Model.Pom/1.2-RC3/NPanday.Model.Pom-1.2-RC3-4b435f4d76e2f0e6.library
[INFO] Unable to find resource 'npanday.model:NPanday.Model.Pom:library:4b435f4d76e2f0e6:1.2-RC3' in repository npanday-releases (http://repo.npanday.org/archiva/repository/npanday-releases)

Downloading: http://pip.manila.exist.com/archiva/repository/maestro-releases/npanday/model/NPanday.Model.Pom/1.2-RC3/NPanday.Model.Pom-1.2-RC3-4b435f4d76e2f0e6.library
[INFO] Unable to find resource 'npanday.model:NPanday.Model.Pom:library:4b435f4d76e2f0e6:1.2-RC3' in repository maestro-releases (http://pip.manila.exist.com/archiva/repository/maestro-relea
ses)
Downloading: http://pip.manila.exist.com/archiva/repository/3rdparty//npanday/model/NPanday.Model.Pom/1.2-RC3/NPanday.Model.Pom-1.2-RC3-4b435f4d76e2f0e6.library
[INFO] Unable to find resource 'npanday.model:NPanday.Model.Pom:library:4b435f4d76e2f0e6:1.2-RC3' in repository 3rdparty (http://pip.manila.exist.com/archiva/repository/3rdparty/)
Downloading: http://pip.manila.exist.com/archiva/repository/maestro//npanday/model/NPanday.Model.Pom/1.2-RC3/NPanday.Model.Pom-1.2-RC3-4b435f4d76e2f0e6.library
[INFO] Unable to find resource 'npanday.model:NPanday.Model.Pom:library:4b435f4d76e2f0e6:1.2-RC3' in repository central (http://repo1.maven.org/maven2)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] NPANDAY-180-020: Problem in resolving artifact: Assembly Artifact Id = NPanday.Model.Pom, Type = library, Local Path Check = D:\Documents and Settings\maestro\.m2\uac\gac_msil\NPanday
.Model.Pom\1.2-RC3__npanday.model\NPanday.Model.Pom.dll, Message = Unable to download the artifact from any repository
The assembly resolvers used by the plugin seems to be using the wrong packaging. Notice that it's trying to download the NPanday.Model.Pom with .library packaging instead of .dll.

Jun 8, 2010 at 8:54 AM

BTW, the default installation dir of the NPanday AddIn in the installer still points to Liit's environment (C:\Documents and Settings\liit\.m2\repository).

Coordinator
Jun 8, 2010 at 10:17 AM

I propose we branch off from REV 51223 since the regression problems was not yet present at this point and in the changes for the release

REVs51838,52045,52048,52251,52675, 52771, 52772, 52787, 52788 and use this for 1.2-RC4.

 

What do you guys think?

Jun 8, 2010 at 11:27 AM

Hi Joe,

Can't the changes that broke trunk just be reverted instead of branching off?

Thanks,

Deng

Developer
Jun 8, 2010 at 11:55 AM
Edited Jun 8, 2010 at 11:57 AM
Hi All, I'd go for reverting the trunk too. I tried locally reverting the changes from r51359 to r51758, and all ITs passed and NPanday was able to start successfully in VS. The issues that were fixed in the above revisions were as follows: 1) http://npanday.codeplex.com/workitem/13296 2) http://npanday.codeplex.com/workitem/13203 But they're not originally included in the list of issues fixed for NPanday 1.2 so we could probably do a 1.2.1 release for those issues after we've pushed out 1.2. Thanks, Liit
Coordinator
Jun 8, 2010 at 12:26 PM
Well we could do that too, I was just thinking that we could continue working on the trunk for the fix and release on the branch, do both work simultaneously . Which ever is more comfortable with everyone is fine with me :D
Developer
Jun 8, 2010 at 1:45 PM

The bug with library/dll is something I must have introduced!! I'm now reviewing all my changes.

The packaging "library" ist totally ok, but it should resolve to the extension "dll".

http://github.com/lcorneliussen/npanday/compare/6341b843bf047ac4c9cb...80580e48e4e2cf9f95c6

I'm sure we can find this and take steps forward instead of backward :-)

But if we revert I'd prefer a branch for the release of 1.2 and bump the trunk to 1.2.1-SNAPSHOT

 

Developer
Jun 8, 2010 at 1:58 PM
deng_c wrote:

I'm also getting an error when installing 1.2-RC3 using the VSInstaller plugin. But the error I got is different from Liit's:

 

Jun 8, 2010 3:44:26 PM npanday.dao.impl.ProjectDaoImpl storeProjectAndResolveDependencies
INFO: NPANDAY-180-018: Retrieving artifact: Artifact ID  = NPanday.Model.Pom
Downloading: http://repo.npanday.org/archiva/repository/npanday-releases/npanday/model/NPanday.Model.Pom/1.2-RC3/NPanday.Model.Pom-1.2-RC3-4b435f4d76e2f0e6.library
[INFO] Unable to find resource 'npanday.model:NPanday.Model.Pom:library:4b435f4d76e2f0e6:1.2-RC3' in repository npanday-releases (http://repo.npanday.org/archiva/repository/npanday-releases)

Downloading: http://pip.manila.exist.com/archiva/repository/maestro-releases/npanday/model/NPanday.Model.Pom/1.2-RC3/NPanday.Model.Pom-1.2-RC3-4b435f4d76e2f0e6.library
[INFO] Unable to find resource 'npanday.model:NPanday.Model.Pom:library:4b435f4d76e2f0e6:1.2-RC3' in repository maestro-releases (http://pip.manila.exist.com/archiva/repository/maestro-relea
ses)
Downloading: http://pip.manila.exist.com/archiva/repository/3rdparty//npanday/model/NPanday.Model.Pom/1.2-RC3/NPanday.Model.Pom-1.2-RC3-4b435f4d76e2f0e6.library
[INFO] Unable to find resource 'npanday.model:NPanday.Model.Pom:library:4b435f4d76e2f0e6:1.2-RC3' in repository 3rdparty (http://pip.manila.exist.com/archiva/repository/3rdparty/)
Downloading: http://pip.manila.exist.com/archiva/repository/maestro//npanday/model/NPanday.Model.Pom/1.2-RC3/NPanday.Model.Pom-1.2-RC3-4b435f4d76e2f0e6.library
[INFO] Unable to find resource 'npanday.model:NPanday.Model.Pom:library:4b435f4d76e2f0e6:1.2-RC3' in repository central (http://repo1.maven.org/maven2)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] NPANDAY-180-020: Problem in resolving artifact: Assembly Artifact Id = NPanday.Model.Pom, Type = library, Local Path Check = D:\Documents and Settings\maestro\.m2\uac\gac_msil\NPanday
.Model.Pom\1.2-RC3__npanday.model\NPanday.Model.Pom.dll, Message = Unable to download the artifact from any repository
The assembly resolvers used by the plugin seems to be using the wrong packaging. Notice that it's trying to download the NPanday.Model.Pom with .library packaging instead of .dll.

 

Somehow in the context of this the ArtifactHandler for 'library' is not in scope. Then it defaults to use the dependency type as file extension.

 

Developer
Jun 9, 2010 at 1:34 AM

hey Lars,

this is probably unrelated, but I thought you might like to know...

I couldn't get the  maven-compile-plugin to build properly using maven 2.0.9. It was completely skipping the generate-plexus-config execution and thus producing a broken plexus jar. When I changed to maven 2.1 it worked fine.

cheers,

Craig

Developer
Jun 9, 2010 at 11:20 AM
supkichen wrote:

hey Lars,

this is probably unrelated, but I thought you might like to know...

I couldn't get the  maven-compile-plugin to build properly using maven 2.0.9. It was completely skipping the generate-plexus-config execution and thus producing a broken plexus jar. When I changed to maven 2.1 it worked fine.

cheers,

Craig

You're right. Unrelated, but still relevant :-)

In 1.2 we generate the plexus conf from a groovy script. It uses gmaven. Maybe there are incompatibilities with gmaven and maven 2.0.9 - could you file a bug in the issue tracker?

Developer
Jun 9, 2010 at 1:25 PM
Edited Jun 10, 2010 at 3:59 AM

 

Hi All,

 

I'm just finalizing the changes larscorneliussen and supkichen submitted and testing it locally.  If everything passes, I'll be pushing with the 1.2-RC4 release tomorrow morning.

 

Thanks again for all your help and patience.

 

- -

 

liit