[jira] [Commented] (NPANDAY-623) Support reactor reference to other modules at compile phase
[ https://issues.apache.org/jira/browse/NPANDAY-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028953#comment-14028953 ] Lars Corneliussen commented on NPANDAY-623: --- Hi, you are right! Doesn*t like, that compile doesn't use final name - i think it should. But in the .NET-area there are some expectations to dll-names when automatically resolving assemblies - so no easy choice. Just changing final-name in the pom-model if it isn't yet custom-changed could be another option. Support reactor reference to other modules at compile phase Key: NPANDAY-623 URL: https://issues.apache.org/jira/browse/NPANDAY-623 Project: NPanday Issue Type: Bug Components: Maven Plugins Affects Versions: 1.4-incubating, 1.5.0-incubating Environment: Maven 2.2.1 Reporter: Greg Domjan Attachments: example.zip When building multiple artifacts with dependencies in the reactor it appears to be currently required that you build to the install phase. This can actually be a bug - see http://developer-blog.cloudbees.com/2012/12/maven-and-hack.html Even if not a bug, this goes against some common practices such as used in the release-plugin which attempts to test the build by running all projects to compile stage only. In comparison the maven reactor allows for dependency resolution in Java JAR dependencies as soon as the compile phase is run. It does this by pointing the artifact file to the local class folder. NPanday could take similar action and point the file to the local target file as soon as compile. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (NPANDAY-624) NPE in ilMerge
[ https://issues.apache.org/jira/browse/NPANDAY-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028964#comment-14028964 ] Lars Corneliussen commented on NPANDAY-624: --- Have you yet looked at the code? It's no magic :-) Also, could it be the same problem as the other issue - that the artifact isn't resolved...? NPE in ilMerge -- Key: NPANDAY-624 URL: https://issues.apache.org/jira/browse/NPANDAY-624 Project: NPanday Issue Type: Bug Components: Maven Plugins Affects Versions: 1.5.0-incubating Environment: Windows, VS2005, VS2012, Platform SDK 6,7,7.1,8.0,8.1 Using npanday.settings to select mininmal framework version 3.0 Maven 2.2.1 Reporter: Greg Domjan ilMerge appears to be looking for the compiler details to select the appropriate ilMerge app. The compiler list is returning multiple options, but then ilMerge gets NPE on following call to ```File assemblyPath = compilerExecutable.getAssemblyPath();``` [DEBUG] NPANDAY-102-003: Apply rule:npanday.vendor.impl.VendorInfoTransitionRuleFactory$8@38c9aa93 [DEBUG] NPANDAY-103-017: Entering State = FFF [DEBUG] NPANDAY-103-052: Set defaults: 3.0 [DEBUG] NPANDAY-102-004: Vendor info requirement after rule:[VendorRequirement for vendor MICROSOFT version 3.0, Framework Version = 3.0] [DEBUG] NPANDAY-065-008: Found vendor [Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0] for requirement [VendorRequirement for vendor MICROSOFT version 3.0, Framework Version = 3.0] [DEBUG] NPANDAY-065-001: Found matching capability: CompilerCapability [vendorInfo=[Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0], operatingSystem='Windows', language='C_SHARP'] [DEBUG] NPANDAY-065-009: Failed to match policy: ExecutableMatchPolicy[profile: 'FULL'] [DEBUG] NPANDAY-065-005: Capability doesn't match: CompilerCapability [vendorInfo=[Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0], operatingSystem='Windows', language='C_SHARP'] [DEBUG] NPANDAY-065-001: Found matching capability: CompilerCapability [vendorInfo=[Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0], operatingSystem='Windows', language='C_SHARP'] [DEBUG] NPANDAY-065-001: Found matching capability: CompilerCapability [vendorInfo=[Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0], operatingSystem='Windows', language='C_SHARP'] [DEBUG] NPANDAY-065-001: Found matching capability: CompilerCapability [vendorInfo=[Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0], operatingSystem='Windows', language='C_SHARP'] [DEBUG] NPANDAY-065-009: Failed to match policy: ExecutableMatchPolicy[language: 'C_SHARP'] [DEBUG] NPANDAY-065-005: Capability doesn't match: CompilerCapability [vendorInfo=[Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0], operatingSystem='Windows', language='VB'] [DEBUG] NPANDAY-065-009: Failed to match policy: ExecutableMatchPolicy[language: 'C_SHARP'] [DEBUG] NPANDAY-065-005: Capability doesn't match: CompilerCapability [vendorInfo=[Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0], operatingSystem='Windows', language='ASP'] [WARNING] NPANDAY-065-010: Found multiple matching capabilities; will choose the first one: [CompilerCapability [vendorInfo=[Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0], operatingSystem='Windows', language='C_SHARP'], CompilerCapability [vendorInfo=[Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0], operatingSystem='Windows', language='C_SHARP'], CompilerCapability [vendorInfo=[Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0], operatingSystem='Windows', language='C_SHARP'], CompilerCapability [vendorInfo=[Configured Vendor Info for MICROSOFT 3.0, Framework Version = 3.0], operatingSystem='Windows', language='C_SHARP']] [DEBUG] NPANDAY-061-006: Artifact Type:gac_msil [DEBUG] NPANDAY-061-007: Artifact Type:false [DEBUG] NPANDAY-061-006: Artifact Type:dotnet-library [DEBUG] NPANDAY-061-007: Artifact Type:false [DEBUG] NPANDAY-061-006: Artifact Type:dotnet-library [DEBUG] NPANDAY-061-007: Artifact Type:false [DEBUG] NPANDAY-061-006: Artifact Type:gac_msil [DEBUG] NPANDAY-061-007: Artifact Type:false [DEBUG] NPANDAY-061-006: Artifact Type:gac_msil [DEBUG] NPANDAY-061-007: Artifact Type:false [WARNING] NPANDAY-231: previously netDependencyId was used to resolve some private bin path... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [DEBUG] Trace java.lang.NullPointerException
Re: NPanday incubator report
On Tue, Jun 10, 2014 at 1:18 AM, David Akehurst d...@akehurst.net wrote: I hope the project has not gone dormant. I still actively use it, and hoping for its continued development and eventual (soon) promotion from incubating. At the very minimum the project would require some active mentors. Hang in there -- we'll try to resolve this at IPMC level. Thanks, Roman.
Re: NPanday incubator report
Hi Roman, My apologies, I didn't see your email immediately. Unfortunately, I am no longer an active mentor for NPanday. I've already stepped down as mentor for the project over a year ago so I am not quite up to date with what's happening on the project. I took a quick look now at the Jira and commit notifications, and the last commit was on April 4. There were also a number of tickets reported in the recent weeks, but there doesn't seem to be anyone actively working on them. Hope this somewhat helps! Thanks, Deng On Fri, Jun 13, 2014 at 11:22 AM, Roman Shaposhnik r...@apache.org wrote: On Tue, Jun 10, 2014 at 1:18 AM, David Akehurst d...@akehurst.net wrote: I hope the project has not gone dormant. I still actively use it, and hoping for its continued development and eventual (soon) promotion from incubating. At the very minimum the project would require some active mentors. Hang in there -- we'll try to resolve this at IPMC level. Thanks, Roman.
Re: NPanday incubator report
On Thu, Jun 12, 2014 at 8:46 PM, Deng Ching-Mallete och...@apache.org wrote: Hi Roman, My apologies, I didn't see your email immediately. Unfortunately, I am no longer an active mentor for NPanday. I've already stepped down as mentor for the project over a year ago so I am not quite up to date with what's happening on the project. I took a quick look now at the Jira and commit notifications, and the last commit was on April 4. There were also a number of tickets reported in the recent weeks, but there doesn't seem to be anyone actively working on them. Hope this somewhat helps! No worries. I totally understand. I would appreciate if you could reply to the general@incubator thread with the same information so that IPMC can suggest an appropriate course-correction for the project. Thanks, Roman.
Re: NPanday incubator report
Sure, will do :) Thanks, Deng On Fri, Jun 13, 2014 at 12:24 PM, Roman Shaposhnik r...@apache.org wrote: On Thu, Jun 12, 2014 at 8:46 PM, Deng Ching-Mallete och...@apache.org wrote: Hi Roman, My apologies, I didn't see your email immediately. Unfortunately, I am no longer an active mentor for NPanday. I've already stepped down as mentor for the project over a year ago so I am not quite up to date with what's happening on the project. I took a quick look now at the Jira and commit notifications, and the last commit was on April 4. There were also a number of tickets reported in the recent weeks, but there doesn't seem to be anyone actively working on them. Hope this somewhat helps! No worries. I totally understand. I would appreciate if you could reply to the general@incubator thread with the same information so that IPMC can suggest an appropriate course-correction for the project. Thanks, Roman. -- Maria Odea Deng Ching-Mallete | och...@apache.org | http://www.linkedin.com/in/oching
