[jira] [Updated] (NPANDAY-372) Integrate with NuGet and NuGet Gallery (nuget.org)

["Lars Corneliussen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NPANDAY-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Corneliussen updated NPANDAY-372:
--------------------------------------

    Description: 
Dependency Management has come to .NET - and Microsoft has taken care of it. That means, to be successful we have to integrate.

NuGet is for dependency management, and the nuget gallery has a couple of hundred OS packages online already.
-I think it should be fairly easy to create a repository layout for those and integrated it with maven.-

*Nothing is easy. :-)*

h4. Prioritized Requirements

For a first release, we should at least support following scenarios:

 # *Resolve library dependencies from nuget repositories / nuget.org* (this will be a huge benefit!, right away.)
   (!) How should we do this? Wagon, repository layout? I do not know enough about maven yet.
   (!) Also, which portions of a *.npkg should we support? It has some conventions, but supports very much any content you can put in a zip. It also has visual-studio-specific things in it. Have to investigate more here.
   (!) How do we talk to nuget.org? Via Nuget.Core?

 # *Generate nuspec-file from pom, or if it exsits, patch it*
   This will make it easier to pack and push nuget packages, even if this is not automated yet.

 # *Create a '\*.npkg' on 'package' and attach as 'nuget-package'*
   We need to add a new type != dotnet-*. Should this be part of npanday?

 # *Install \*.npgkg to local nuget repository on 'install'*
   (?) Is there any standard for this? (!) If not, will we invent one?

 # *Push \*.npkg to nuget.org on 'deploy'* 
   That shouldn't be to hard.
   

h4. Unique Selling Proposition

 * Nuget-Packages for VS 2005 and 2008
 * Nuget outside of Visual Studio (currently the cmd-line tool does not do more than download and unzip)

h4. Nice to have

 * Minimod support
 * further ideas?

  was:
Dependency Management has come to .NET - and Microsoft has taken care of it. That means, to be successful we have to integrate :-)

NuGet is for dependency management, and the nuget gallery has a couple of hundred OS packages online already.

I think it should be fairly easy to create a repository layout for those and integrated it with maven.

       Assignee: Lars Corneliussen

I have been playing with nuget in the context of Minimods. Would be great to have somebody in here to discuss further details.

> Integrate with NuGet and NuGet Gallery (nuget.org)
> --------------------------------------------------
>
>                 Key: NPANDAY-372
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-372
>             Project: NPanday
>          Issue Type: New Feature
>          Components: Maven Plugins
>            Reporter: Lars Corneliussen
>            Assignee: Lars Corneliussen
>             Fix For: 2.0
>
>
> Dependency Management has come to .NET - and Microsoft has taken care of it. That means, to be successful we have to integrate.
> NuGet is for dependency management, and the nuget gallery has a couple of hundred OS packages online already.
> -I think it should be fairly easy to create a repository layout for those and integrated it with maven.-
> *Nothing is easy. :-)*
> h4. Prioritized Requirements
> For a first release, we should at least support following scenarios:
>  # *Resolve library dependencies from nuget repositories / nuget.org* (this will be a huge benefit!, right away.)
>    (!) How should we do this? Wagon, repository layout? I do not know enough about maven yet.
>    (!) Also, which portions of a *.npkg should we support? It has some conventions, but supports very much any content you can put in a zip. It also has visual-studio-specific things in it. Have to investigate more here.
>    (!) How do we talk to nuget.org? Via Nuget.Core?
>  # *Generate nuspec-file from pom, or if it exsits, patch it*
>    This will make it easier to pack and push nuget packages, even if this is not automated yet.
>  # *Create a '\*.npkg' on 'package' and attach as 'nuget-package'*
>    We need to add a new type != dotnet-*. Should this be part of npanday?
>  # *Install \*.npgkg to local nuget repository on 'install'*
>    (?) Is there any standard for this? (!) If not, will we invent one?
>  # *Push \*.npkg to nuget.org on 'deploy'* 
>    That shouldn't be to hard.
>    
> h4. Unique Selling Proposition
>  * Nuget-Packages for VS 2005 and 2008
>  * Nuget outside of Visual Studio (currently the cmd-line tool does not do more than download and unzip)
> h4. Nice to have
>  * Minimod support
>  * further ideas?

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