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 "Lars Corneliussen (JIRA)" <ji...@apache.org> on 2011/03/21 11:27:05 UTC

[jira] [Updated] (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:all-tabpanel ]

Lars Corneliussen updated NPANDAY-123:
--------------------------------------

    Summary: PATH should not have to be set for both Visual Studio AddIn or mvn command-line to function  (was: PATH should not have to be set for Visual Studio AddIn to function)

> 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
>            Reporter: Brett Porter
>            Priority: Minor
>             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.

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