You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-commits@incubator.apache.org by "Brett Porter (JIRA)" <ji...@apache.org> on 2011/04/11 15:34:05 UTC

[jira] [Commented] (NPANDAY-123) PATH should not have to be set for both Visual Studio AddIn or mvn command-line to function

    [ https://issues.apache.org/jira/browse/NPANDAY-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018392#comment-13018392 ] 

Brett Porter commented on NPANDAY-123:
--------------------------------------

what commands do you run to test this?

I have VS 2008, NUnit and mvn 2.2.1 on the path, but no csc, xsd, etc. I cleared my local repository/pab/uac/npanday-settings.xml.

Using the bootstrap, then mvn install, it fails in the same place whether I use npanday 1.2.1 as the bootstrap version, or ${project.version}. No npanday-settings.xml was created.

(Interestingly on 1.3.1-incubating-SNAPSHOT, I needed to set MAVEN_OPTS higher - might need to check if usage has gone up or if I did something differently).


> PATH should not have to be set for both Visual Studio AddIn or mvn command-line to function
> -------------------------------------------------------------------------------------------
>
>                 Key: NPANDAY-123
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-123
>             Project: NPanday
>          Issue Type: Bug
>          Components: Maven Plugins
>    Affects Versions: 1.2, 1.2.1
>            Reporter: Brett Porter
>            Assignee: Brett Porter
>             Fix For: 1.3.1-incubating
>
>
> some utilities are called from within the assemblies - such as gacutil (see item #9904) - assuming that they are on the path. However, the default configuration for the Visual Studio application does not establish that. To minimise configuration for new users, the application should be able to locate the framework paths and construct full paths to such executables.
> Things to be tested
> * Does NPanday build pass without .NET on the PATH (just NUnit) *worksforme (lars)*
> * Do the integration tests pass without .NET on the PATH *yes and no. see NPANDAY-393*
> * Are the NPanday-DLLs targeted to CLR 2.0 (use Reflector) *worksforme (lars)*
> Combinations to be tested
> * -Windows 7 64bit, .NET 2.0, .NET 3.0, .NET 3.5, .NET 4.0, VS 2010, MVN 2, trunk->trunk-
> * XP, VS 2005 (brett)
> * XP, VS 2008 (brett)
> Further Todos
> * -Remove all the documentation about setting up the path-
> * -Remove warnings about 64bit (http://incubator.apache.org/npanday/docs/1.3-incubating/developers/building-on-64bit.html)-
> * -Document the very first bootstrapping build (Developer Guide)-

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira