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 (Created) (JIRA)" <ji...@apache.org> on 2011/11/07 14:32:51 UTC

[jira] [Created] (NPANDAY-478) Visual Studio should not require 'profile'-tag in 'settings.xml'

Visual Studio should not require 'profile'-tag in 'settings.xml'
----------------------------------------------------------------

                 Key: NPANDAY-478
                 URL: https://issues.apache.org/jira/browse/NPANDAY-478
             Project: NPanday
          Issue Type: Improvement
    Affects Versions: 1.4-incubating
         Environment: VS 2010
            Reporter: Lars Corneliussen
            Assignee: Lars Corneliussen
             Fix For: 1.4.1-incubating


Currently, when resyncing references, the NPanday-Addin will complain, if the settings has no profiles-element declared.

{code}
Cannot add reference of <artifact id>, no valid Remote Repository was found that contained the Artifact to be Resolved. Please add a Remote Repository that contains the Unresolved Artifact." 
{code}

IMHO that is unessessary, as it should be up do the user how he wants to specify repositories.

It could be a hint, though...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Work started] (NPANDAY-478) Visual Studio should not require 'profile'-tag in 'settings.xml'

Posted by "Lars Corneliussen (Work started) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/NPANDAY-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on NPANDAY-478 started by Lars Corneliussen.

> Visual Studio should not require 'profile'-tag in 'settings.xml'
> ----------------------------------------------------------------
>
>                 Key: NPANDAY-478
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-478
>             Project: NPanday
>          Issue Type: Improvement
>    Affects Versions: 1.4-incubating
>         Environment: VS 2010
>            Reporter: Lars Corneliussen
>            Assignee: Lars Corneliussen
>             Fix For: 1.4.1-incubating
>
>
> Currently, when resyncing references, the NPanday-Addin will complain, if the settings has no profiles-element declared.
> {code}
> Cannot add reference of <artifact id>, no valid Remote Repository was found that contained the Artifact to be Resolved. Please add a Remote Repository that contains the Unresolved Artifact." 
> {code}
> IMHO that is unessessary, as it should be up do the user how he wants to specify repositories.
> It could be a hint, though...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (NPANDAY-478) Visual Studio should not require 'profile'-tag in 'settings.xml'

Posted by "Lars Corneliussen (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/NPANDAY-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Corneliussen resolved NPANDAY-478.
---------------------------------------

    Resolution: Fixed

Just review everything I set to fixed before we release :-)
                
> Visual Studio should not require 'profile'-tag in 'settings.xml'
> ----------------------------------------------------------------
>
>                 Key: NPANDAY-478
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-478
>             Project: NPanday
>          Issue Type: Improvement
>    Affects Versions: 1.4-incubating
>         Environment: VS 2010
>            Reporter: Lars Corneliussen
>            Assignee: Brett Porter
>             Fix For: 1.4.1-incubating
>
>
> Currently, when resyncing references, the NPanday-Addin will complain, if the settings has no profiles-element declared.
> {code}
> Cannot add reference of <artifact id>, no valid Remote Repository was found that contained the Artifact to be Resolved. Please add a Remote Repository that contains the Unresolved Artifact." 
> {code}
> IMHO that is unessessary, as it should be up do the user how he wants to specify repositories.
> It could be a hint, though...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (NPANDAY-478) Visual Studio should not require 'profile'-tag in 'settings.xml'

Posted by "Lars Corneliussen (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/NPANDAY-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Corneliussen reassigned NPANDAY-478:
-----------------------------------------

    Assignee: Brett Porter  (was: Lars Corneliussen)

Fixed in trunk r1198919, waiting for review.
                
> Visual Studio should not require 'profile'-tag in 'settings.xml'
> ----------------------------------------------------------------
>
>                 Key: NPANDAY-478
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-478
>             Project: NPanday
>          Issue Type: Improvement
>    Affects Versions: 1.4-incubating
>         Environment: VS 2010
>            Reporter: Lars Corneliussen
>            Assignee: Brett Porter
>             Fix For: 1.4.1-incubating
>
>
> Currently, when resyncing references, the NPanday-Addin will complain, if the settings has no profiles-element declared.
> {code}
> Cannot add reference of <artifact id>, no valid Remote Repository was found that contained the Artifact to be Resolved. Please add a Remote Repository that contains the Unresolved Artifact." 
> {code}
> IMHO that is unessessary, as it should be up do the user how he wants to specify repositories.
> It could be a hint, though...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira