I've got version 1.1.0 of a feature installed that I've deployed a version 1.1.1 of, as visible in the 'Install new software' view: .
However, 'Check for software updates' is saying there are no updates available. Why is this?
'Check for updates' will only check for updates on the installation seeds. These are the features and the product that is listed on the 'Installed Software' tab in the installation details.
'Check for updates' will not check the dependencies of the installation seeds for new versions. So in your case, it seems that the "Smart Constraint" feature is not installed as seed but only as dependency of one of the other seeds.
To get the new version installed, you can simply install it via the 'Install new software' dialog. This will install the new version (possibly requiring other updates to mitigate conflicting dependencies), and make the feature a seed so that it will be updated by a 'Check for updates' in the future.
Related
I have successfully set up continuous integration process using TeamCity for non-SalesForce projects, but need help with automating SalesFoce manage packages installation.
To migrate metadata from source to target org, I used ant migration tool, but how to do in case of managed packages?
Questions:
How will TeamCity know that the new package has been created? I may watch the changes in source code tool, but not in the cloud where the created package is stored.
How to get the latest version of the package from the cloud? I need to compare the versions of the packages: the installed one and the new one
How to install the package?
Please help.
I checked SF documentation and found that SF API provides ability to install, upgrade and uninstall Managed Packages. Also it provides ability to run some Apex code after these actions. I think, you need to move in this way. Here is related documentation.
According to "pub --help" the "upgrade" command is used to:
Upgrade the current package's dependencies to latest versions.
However, I just had to run "pub upgrade" several times to reach the current latest versions of packages that my pubspec.yaml depends on. It seemed like each run upgraded only incrementally. What am I missing?
Specific example I observed was mustache: ">=0.1.5", which was first upgraded to 0.1.6 and on a second run to 0.1.7.
pub version: Pub 1.1.0-dev.5.11
It should upgrade all dependencies to the latest version available, or the latest version allowed in pubspec.yaml (see the Pub Package Manager docs).
But if it jumps only over one new version per upgrade, try to fill in the bug
I have never seen that behavior. It should go straight to the highest available (not-dev) release that fulfills your dependency constraints.
You can see this behaviour if a new version of your dependency lands between your 2 runs.
Looking at the versions of mustache (click on the Versions tab) you can see if a new version has landed during your test. It may explain what you observed.
I've created a Yeoman generator and want my team to use it.
What happens if I update my generator on Github? They installed the generator locally in an older version. Do they always have to install again to get the latest version?
Team members don't know when updates happen and I don't want them to care too much about it. I just would like for them to use the latest version of the generator.
What is the suggested way of updating generators?
Thanks
Glad you asked!
Starting with Yeoman RC1, which will be announced later today, there's a brand new way to manage your generators: Just enter yo and enjoy the new wizard:
If you select "Update Generators" from the menu, yo yo will take care of bringing them all to the latest version.
If you are a generator author and want to go one step further to make sure your users are always up-to-date, you can use update-notifier from the Yeoman project to greet users with a notification if they run an obsolete version.
If you want to update a specific generator you can run
npm update generator-mygenerator -g
Nice if you have many generators installed.
In linux I had trouble of upgrading using the yoeman cli because of some permission issues
So instead I did the following
In my case it was
sudo npm install -g generator-your-generator-name
This automatically reinstalled the latests version
You could try
npm install -g generator-your-generator-name
Im using Visual Wb Developer 2012 Express. I'm trying to update NuGet. Inside the error log i find this:
Install Error : VSIXInstaller.SignatureMismatchException: The signature on the update version of 'NuGet Package Manager' does not match the signature on the installed version. Therefore, Extension Manager cannot install the update.
at VSIXInstaller.Common.VerifyMatchingExtensionSignatures(IInstalledExtension installedExtension, IInstallableExtension updateExtension)
at VSIXInstaller.InstallProgressPage.BeginInstallVSIX(SupportedVSSKU targetAppID)
How can i get the signature of the update version of NuGet to match he installed version?
Nuget's had some issues with upgrades requiring the user first uninstall the old addin, and then installing the new version fresh. Give that a shot. Upgrades after that should be ok.
I am attempting set up Netbeans 7.1 as my RoR editor. When trying to install plugins I get the following error:
Some plugins require plugin HTML Editor Library to be installed. The
plugin HTML Editor Library is requested in version >= 1.21 (release
version 1) but only 2.0.1 (of release version different from 1) was
found. The following plugin is affected:
Embedded Ruby (RHTML)
I looked for this HTML plugin so I could install it but I can't seem to find it anywhere.
It seems that the Ruby on Rails plugin has some problem (i.e. does not support) Netbeans 7.1 and 7.2. But it works with version 6.9 and 7.
Reference: http://plugins.netbeans.org/plugin/38549/ruby-and-rails
If I'm not wrong this is the lovely 207075 from the bugtracker: https://netbeans.org/bugzilla/show_bug.cgi?id=207075
In fact there's a workaround for this issue:
http://blog.enebo.com/2012/01/workaround-for-ruby-support-on-netbeans.html
good luck.
If you want to install it on a newly downloaded Netbeans (7.1 in my case), you should first go to Tools > Plugins, select Updates Tab and install the updates. Then, after restart, you'll go to the mentioned above Plugins, and now you will able to install all the required updates (HTML Editor will be among them.)
Lastl thing, as #skripted already mentioned, just install the plugin by following the instructions on this page.