I made new Package for Umbraco, then I publish it on http://our.umbraco.org/projects.
Now the package is online. It is available to community.
But I can't find it inside an Umbraco installation.
If I go in Umbraco backoffice, "Developer", "Packages", "Umbraco package repositories", I can't find it.
Why?
Maybe I will wait some days? The package is online since August 23, 2013.
Thanks
I wrote on Umbraco Forum as for suggestion of #ProNotion, then I received answer.
Hi Flavio
That's because packages needs to have 15 karma points before they're
available in the backoffice. It's that way to ensure that the packages
you can install directly from within Umbraco are high quality that
have been approved by the community.
Cheers, Jan
Topic url:
http://our.umbraco.org/forum/developers/extending-umbraco/44611-Umbraco-my-new-published-package-is-missing-on-Developer-section
I think the package has to have a certain number of votes before it makes it into the Umbraco package repository. I don't believe that the exact rules are officially published anywhere so can't direct you somewhere for official confirmation other than to suggest you ask on the forums or Twitter with the hash tag #umbraco.
Related
This morning, I tried to get a coop student up and running on an older version of the Google App Engine for Eclipse plugin.
The following website and all related links appear to have been wiped off the face of the earth:
https://developers.google.com/eclipse/
Is this just down at the moment?
Is it possible to get older versions of the plugin?
While it is correct that the Google Plugin for Eclipse has been removed from Google's documentation, it is still available.
To install it, in Eclipse Neon, click "Install new Software" and add in this URL.
http://dl.google.com/eclipse/plugin/4.6
Next, click through the dialogues to allow the installation, and restart Eclipse.
While Google has chosen to stop supporting this, I personally feel that the new Cloud Tools for Eclipse plugin is just not ready. Also, in the early days, JDO was what many people were using on top of the data layer, and since GAE has been around for 10+ years, many of us have a lot of infrastructure built on top of this that is costly to change. While it's still possible, in theory, to run the DataNucleus enhancer manually, it's a huge pain that requires in-depth knowledge of the inner workings of GAE and DataNucleus and knowledge of which dependencies go together. It may have been well-documented in the past, but today it is not.
But be warned, one of our engineers recently lost the ability to deploy the project to Google App Engine using the GPE and was forced to use the gcloud tool, which doesn't seem to have sensible defaults, like deploying to a non-default version and instead will deploy straight to default, well, by default. So we're writing a script around that command that will pass in --no-promote so it doesn't immediately start migrating traffic... Visit the gcloud reference for app deploy for more details. Good luck!
For more information on the install process, please see How to install Google Plugin for Eclipse on mkyong.com.
GPE is indeed gone. It was not up to date and many parts of it no longer functioned. Over the coming year, even more core functionality was going to break. We wouldn't be doing anyone any favors by letting them invest their time in a broken tool. This is doubly true for new users such as your students. There are some old GPE snapshots floating around here and there, but those don't really work with GCP in 2018.
That official documentation is most likely gone for good, the plugin was deprecated in favour of the Google Cloud Tools for Eclipse. From Migrating from the Google Plugin for Eclipse:
The Google Plugin for Eclipse is deprecated and will not be supported
beyond Eclipse 4.6 (Neon). It will be removed in early 2018.
This document describes how to migrate a project that uses the Google
Plugin for Eclipse to the supported tooling.
You can check the snapshots of the docs on the Wayback Machine, and maybe still find the matching code repositories, if they haven't been removed as well.
But it's probably a good idea to switch to the supported tools sooner than later, especially since they're just getting started.
Related: Migrating GAE project to Java 8 - get XML validation error after adding runtime property to appengine-web.xml
My team needs to bring immediately to customers a fix in Codename One that will only be available in next version.
(GitHub commit: ddc2356ee77eefb64425bcdd0d8ed5aab30505bf)
(GitHub issue: #2203)
Unfortunately we can't wait for the November 2017 planned release of the new plugin version.
So, we need to configure a new Plugin locally with this fix and use it to build a new Android Application for deployment. How do we go about that?
We already cloned the GitHub's Codenameone Project and read some documentation, but we couldn't find required information.
That commit will be included in the next server update next Friday. You don't need to wait until November.
I have an application that is using an ASP.NET MVC project and controllers that is an envelope to an Angular-based SPA hosted inside of that project. Previous developers implemented SASS port of Bootstrap 3.3.0 and I need to get it up to 3.3.7. Most documentation on the Official Port of Bootstrap 2/3 is catering to ruby/npm implementations. How does one keep up on updates effectively in a Visual Studio world or should I simply update it externally using rake, ruby, npm, etc? Any guides or assistance is welcome. Thanks in advance.
After more research it looks like rake and the instructions found on the twbs readme may be sufficient from a command line standpoint but if anyone has further thoughts feel free to add.
https://github.com/twbs/bootstrap-sass#upstream-converter
Also have found a Nuget package that may provide better support than the handrolled version in place in the project now. https://www.nuget.org/packages/Twitter.Bootstrap.Sass/
My sincerest apologies, if this has been asked before. I've searched the site but have not seen an answer for what I'm looking for yet.
For years, my company has referenced custom binaries in a local folder hierarchy within source control. We're in the process of changing our source control, and in the process are defining new strategies for many things. One of the things I've been working on is to setup a local NuGet feed for our custom packages to replace the old source control folder method. I've been able to successfully create custom packages and using the package restore feature, log into our build box to restore both NuGet packages from our local feed, as well as those from the official NuGet feed. Everything has worked well up to this point.
The time has come to begin testing our migration process from our old source control to the new source control, and convert all of the references over to NuGet packages. Where needed, we're creating packages and placing them on our local NuGet server. The issue I came across today involves a project that uses an old version of a vendor library. I searched the official NuGet feed and found the library as a package, but the particular version we used at the time is no longer available.
I know from the fact that package restoration was a highly requested feature, that other companies are already employing the strategy we're attempting now. My question is what strategy is your company implementing when operating under this criteria? Is there a best practice we should be considering?
Thanks for your time and assistance.
That's quite a big question to answer so I'll recommend you some resources to read up on this topic.
I wrote an MSDN article on some patterns and practices I'd recommend when using NuGet into the organization. Maybe you'll find something useful in there: http://msdn.microsoft.com/en-us/magazine/jj851071.aspx.
There's also the book Pro NuGet available at http://bit.ly/ProNuGet.
I noticed a few tweets this morning about a new version of Silverlight having been released - Silverlight 2 GDR 1 (2.0.40115.0). Details of what/why/should I target it/is it backward compatible/etc seem incredibly thin on the ground.
Hitting this Silverlight page on Microsoft.com tells me my version (RTW) is now out of date and I should upgrade to GDR 1. But hitting silverlight.net - there's no mention of it, the Silverlight elements on the page don't tell me my version is out of date and the Getting Started page still links to RTW tools.
This kinda leads me to presume that if you upgrade your dev tools to target the GDR release, then your users will need to upgrade their Silverlight install also?
A few details on what's in GDR can be found in the release notes - but it sure would be nice if Microsoft would clarify it's purpose and suggested adoption. Anyone got any more details?
Tim Heuer explains all: http://timheuer.com/blog/archive/2009/02/19/silverlight-2-gets-minor-update-gdr1.aspx
It seems to be only bug fixing.
So if your applications (so your users) are not concerned by those bugs, it is not mandatory to update your plugin for the moment.