Regarding 2.0, the branches have been merged, resharper 6 is sadly a top priority.
A quick and easy way to use http as a remote repository (to publish to) for native OpenWrap functionality is to use the normal \\unc\ syntax on a webdav-enabled site, or to mount a webdav drive using net use x: http://blah.com/blah/. An alternative is to push to a unc and expose that folder over http using IIS. OpenWrap-server I'm not ready to release yet, the cost of finishing it off is too high with too low benefits on a The OpenWrap Publishing Protocol is published so if you want to add an openwrap endpoint and deal with the atrocities of making Orchard or nuget gallery support openWrap packages and publications, you can do that, that'd be a great OSS project. You could also simply implement that protocol in your own web server, using any of the great available web frameworks, it's really easy. As for reusing anything from them, there's a huge amounts of reasons, some competitive, some based on the potential of professional two-way relationship, some due to code architecture, some due to the attitude of certain people on that team, why there will be no nuget code in OpenWrap, now or in the near future. I'm not interested in being a nice nuget copycat that does what they do, just slightly better, OpenWrap takes care of more and works on different principles, that is exactly what makes it exist alongside nuget. Going down the avenue you suggest Henrik would just kill the project. Seb ________________________________________ From: [email protected] [[email protected]] on behalf of Henrik Feldt [[email protected]] Sent: 01 September 2011 22:29 To: [email protected] Subject: RE: Rake, NuGet and Openwrap So the frozen-rake stuff is at: https://github.com/codereflection/BuildWithRuby Right now my pipeline has filled up quite a lot, but I'm still trying to keep a steady stream of OSS flowing - anyway - someone should have a look at stabilizing the buildwithruby/albacore project on Windows and Ubuntu/*nix to make it work. I've been experimenting with Ubuntu and albacore to make this work properly there - since I needed to build Windsor for Ubuntu. Unfortunately I couldn't make it work right there and then, and Albacore probably needs some minor fixes applied - I have a work item to have another go, from the author of that project, so I'll see how that works out. Pull-requests are probably very welcome here as well - Logirel: My idea is that I add an option to logirel to pull the 'BuildWithRuby'-project from git into the scaffold when I run it on in a solution folder. Logirel is turning 0.2 in a while which will support selecting multiple framework targets for given projects (leaving SL-projects as they are and mono as an if-statement), but my time to hack on that is limited, too. Pull-requests are very welcome :) OpenWrap: I'm sure Sebastien is reading this list, so perhaps he'd like to comment. (Personally I wish he would just harvest some nuget code for the VS integration and create an acceptably stable release off of the 1.1_remotes branch and defer R#6-integration, then harvesting the same orchard code for the package-service, to get something we can push wraps to. As far as I understand, the licensing permits it [MS-PL]. If nothing is done, then, as always, MS tech will become good enough eventually) Nugets: As logirel builds both into the rakefile, both tasks for packaging and publishing nugets, we could just push packages built from master branch in CI-server (we could e.g. follow gitflow and it would be the natural order of things) My 2 cents. Henrik -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of G. Richard Bellamy Sent: den 31 augusti 2011 17:27 To: [email protected] Subject: Rake, NuGet and Openwrap So, I know that folks have pretty much settled on using a repository-frozen version of Rake with Albacore for the build process. Has anyone put together a quick set of notes about what the plan is? I've been reading some about OpenWrap, and wondering where that fits in, if at all... -rb -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
