I installed the latest version of Eclipse Neon in Ubuntu 16.04.1 LTS. When I attempted to create a PHP project I got this error:
Failed to load JavaHL Library.
These are the errors that were encountered:
no libsvnjavahl-1 in java.library.path
no svnjavahl-1 in java.library.path
no svnjavahl in java.library.path
java.library.path = /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib
So I attempted to install JavaHL follow the instructions at:
http://subclipse.tigris.org/wiki/JavaHL
In Eclipse: Help => Installation Details I see I have Subclipse version 1.10.13. According that web page I need to install SVN/JavaHL version 1.8.x. When I follow the directions farther down that page and execute the command:
sudo apt-get install libsvn-java
what is installed is version 1.9.3-2ubuntu1. How can I install version 1.8.x?
I attempted to install Subclipse version 1.12.x by pasting the URL: http://subclipse.tigris.org/update_1.12.x
In Eclipse: Help => Install New Software => Work with field, after removing both Subclipse and SVNKit. But the versions it was going to install was still Subclipse 1.10.13 and SVNKit Library 1.8.12
You are doing the right thing. The Subclipse version is the same because it is not possible to host both the 1.8.x and 1.9.x version of the JavaHL plugin on the same site and there is otherwise no difference in the versions.
That said, since you have 1.9.x available you should just move on to the new location and version of Subclipse that only supports 1.9.x. The project has moved here:
https://github.com/subclipse/subclipse
Information on installation and JavaHL is in the wiki.
Note that other than a few small bug fixes that have been released, it is not much different than the version that was on tigris. That said, that version is dead and will not receive any more updates so it makes sense to move to this version now.
I just updated the sdk to 4.1.4 and trying to install clay from command line I get the following message:
This projected is outdated (try 'pebble convert-project' or'pebble sdk install 2.9')
Now, I am not going to install the 2.9 sdk, of course, and I know that convert is just going to change appinfo.json into pakage.json, which I don't need to do because I am already on sdk 4.1.4.
Has anybody here had the same issue, how did you solve it?
Pebble-Clay is a JS package that can also be installed by running
npm install pebble-clay
This fixes the issue.
Alternatively downloading and installing the SDK 2.9 will fix it. (This will not overwrite the latest version of the SDK.)
I can't seem to install the Windows Azure Storage NuGet Package because the version clashes with another package that probably depends on it. I can't seem to install anything related Azure because the same error pops up every time.
Install failed. Rolling back... Updating 'Microsoft.Data.OData 5.6.2'
to 'Microsoft.Data.OData 5.6.4' failed. Unable to find versions of
'WindowsAzure.MobileServices.Backend.Tables,
WindowsAzure.MobileServices.Backend.Entity' that are compatible with
'Microsoft.Data.OData 5.6.4'.
Why do I get this and how can I get around to having all compatible versions?
I am making a multi-platform app in VS 2013 (iOS, WinPhone and Android). I want to add into the iOS reference folder a Nuget Packages named Microsoft Http Clients Libraries and I cannot do it because I get the following error:
Could not install package 'Microsoft.Bcl.Build 1.0.14'. You are trying
to install this package into a project that targets
'Xamarin.iOS,Version=v1.0', but the package does not contain any
assembly references or content files that are compatible with that
framework. For more information, contact the package author.
Can anybody help me with that?
I faced the same problem and apparently the Bcl.Build 1.0.14 can not be installed, but you probably you don't need that old version.
I faced this issue when I tried adding WindowsAzure.MobileService to the iOS Xamarin project. And it failed, because the minimal supported Bcl.Build is required to be 1.0.14, but if you have a newer version, which installs quite fine, you will be able to add other packages that depend on it.
So
1. Install Microsoft.Bcl.Build package separately (the latest)
2. Install your package that depends on it.
Go to -> Solution -> Manage Packages For Solution -> In the tab "Browse" -> Select the two options follow below:
First:
Install package "Microsoft.Bcl.Build" your version more latest 1.0.21
Second:
After this step, now install package "Microsoft.Net.Http" your version mor latest 2.2.29
Result:
For me was solved!
Microsoft.Bcl.Build 1.0.14 can be installed into Xamarin.iOS projects.
It may fail if:
Your NuGet Package manager is not up to date.
You do not have the Xamarin Portable Class Library profiles for Xamarin.iOS installed.
If you have the latest Xamarin version installed it is probably the NuGet Package Manager not being up to date. You can update it from Tools - Extensions and Updates - Updates - Visual Studio Gallery.
In Visual Studio 2017 I encountered above error, and I solved the issue by installing Microsoft.Bcl.Build first on the Xamarin.Android, then installed Microsoft.Net.Http and System.Net.Http, but Xamarin.IOS and Xamarin.UWP there were no issues.
I found the solution and put it here in case some one may face the same problem.
Install "Microsoft.Bcl.Build.1.0.21" first for all your projects.
Now you can install "PortableRest", all dependency that depends on Microsoft.Bcl.Build will be installed correctly.
I was trying to install Microsoft.Net.Http in my Xamarin.Forms project when i faced this issue. Here is what you must try to get rid of this error:
1- Update Xamarin.Forms to latest version in each project of solution.
2- As my primary intention was to install Microsoft.Net.Http, and this package had dependencies on Microsoft.BCL and Microsoft.BCL.Build. I tried installing these packages (Microsoft.Bcl and Microsoft.Bcl.Build) individually and it worked for me. First install latest version of Microsoft.Bcl.Build 1.0.21 (If 1.0.14 did not install, try latest version). Then, install Microsoft.Bcl which should be installed successfully and this solution worked for me and I hope would work for you too. After installing these packages indivisually, I was able to install Microsoft.Net.Http successfully.
NOTE: While installing Packages (Microsoft.Bcl and Microsoft.Bcl.Build) into your projects, check which version you are installing. Try installing another version, if one does not work and let me know If problem does not solve.
Have a great day :)
In the VS solution, I have as dependencies (in the packages.config file)
a package A, version 2.0.0 which has dependency on package B version >= 5.0.0.0. The latest version of A is 2.1.0 and has the same dependencies as in 2.0.0
a package B, version 10.0.0.0. The latest version is 10.0.5.2
I want to update the package A to 2.1.0 so I tried the command
update-package A
in 'package manager console'. But strangely, Nuget updates also the package B to 10.0.5.2.
Someone told me that by default, Nuget will update to the 'bug fix' version, but I haven't found the link about that.
Does anyone know how to tell Nuget to not update other packages automatically ?
For info, I'm using Nuget 2.5, so according to http://docs.nuget.org/docs/reference/versioning, the dependencies are no longer updated during package installation
Thanks.
As far as I'm aware, this cannot be done, and is the main reason we created the ProGet Client Tools.
You might be able to get away with specifying the explicit version by surrounding it in brackets (e.g. [10.0.0.0]) in the packages.config file but that still seemed to grab the bug fix version when I tried it - though I haven't tested it on the latest version yet.
For reference, the NuGet dependency version selection algorithm is described in detail here: http://blog.davidebbo.com/2011/01/nuget-versioning-part-2-core-algorithm.html