-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[nuget_model] Add support for Nuget (NuSpec) dependency groups #85
Comments
Ah, looks like the clean_slate branch isn't ready for this yet. If I do this I'll send the PR to master |
In what sense is not |
@haf It looked like none of the other task implementations were there, so I |
Ah, no, there won't be any more task implementations; most of the things in old master is wrapping a command, and that we should rather provide good facilities to do -- instead of re-wrapping the parameters in ruby. Also, by taking a larger view of the process of building a project, the task types that ARE there are now more capable. clean_slate is rc2, so it's done. I'm waiting for bug reports; at new year we're publishing 2.0. |
@haf so the new version of Albacore won't provide built-in tasks for NuGet, NUnit, MSBuild, etc... ? |
yes, it does everything the previous version did with nugets, with less code with |
I'm considering contributing this myself, but I may not have the time to do it.
I would like to add NuGet 2.0's new dependency syntax to Albacore, which includes support for dependency groups.
The new syntax for specifying dependencies looks like this:
The really powerful difference between this spec type and what the current implementation does is the ability to specify dependencies for specific .NET framework versions.
If I need to use the System.Threading NuGet package targeting .NET 3.5 but not for any other supported NuGet target, this will allow me to do it.
Looking at the code under the
clean_slate
branch, it looks likenuget_model.rb
and its associated tests will need to be updated.I believe we can also accomplish these changes without breaking compatibility with existing Albacore instances that use the nuspec feature.
Here's my suggestion - currently the calls to adding a new nuspec dependency look like this:
I'm going to propose that we add a third optional attribute, for Target Framework at the end:
If no Target Framework is specified, the nuspec dependency will simply be put under the default group.
The text was updated successfully, but these errors were encountered: