When first launching IntelliJ IDEA Community Edition 14.0.2 on Windows 7 x64 I received the following error when trying to import the sample libGDX gradle config:
Intellij 14 the supplied javaHome seems to be invalid
The IDE is looking in C:\Program Files (x86)\JetBrains\IntelliJ IDEA Community Edition 14.0.2\jre for the java runtime, but the files exist in a sub directory off this one: C:\Program Files (x86)\JetBrains\IntelliJ IDEA Community Edition 14.0.2\jre\jre.
My solution was to copy the contents of jre\jre up one level to jre, which solved the problem - but doesn't feel like the right thing to do.
Is this an acceptable solution, or is there a 'better way' to solve this?
It feels strange to me that the default install is not in the correct location; but there might be something environmental that I'm not quite understanding.
This was recorded as a duplicate, but it is not - it is a different product. Android Studio is a different product to IntelliJ-Idea.
Since you have a 64-bit Java as your JAVA_HOME, run the 64-bit version on IntelliJ instead, idea64.exe in the bin directory of your IntelliJ installation; for example:
C:\Program Files (x86)\JetBrains\IntelliJ IDEA Community Edition 14.0.2\bin\idea64.exe
Related
I have a problem with Intershop Studio 4.9.0 not showing java and pipelets from gradle system cartridges. I upgraded Studio by extracting new zip file and just copy workspace from Studio 4.7. In old Studio I don't have this problem.
System cartridges opened in server folder shows java and pipelets without problem, but pipeline editor looks for pipelets in gradle cartridges and because of that all system pipelets can't be resolved.
Is this issue with latest Studio or something is wrong?
Thank you for your help!
This is a known problem and already fixed in the master branch. An updated version of Intershop-Studio will be available very soon.
I am installing a build agent on a virtual machine (using GoCD) and my goal is trying to keep it as light as possible, i.e., installing only MSBuild and avoid installing visual studio.
One of my projects uses OfficeTools and when compiling the build I get the following error:
C:\GoAgent1\pipelines\ProjectRepo\Office\MyProject.Office.Excel2007.UnderwritingNotes\MyProject.Office.Excel2007.UnderwritingNotes.csproj(365,3):
error MSB4019: The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v14.0\OfficeTools\Microsoft.VisualStudio.Tools.Office.targets"
was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
OfficeTools\Microsoft.VisualStudio.Tools.Office.targets doesn't exist!
For that I will need to install "Office Tools for Visual Studio" which depends on Visual Studio (in this case VS2015 or 14.0).
One solution is copying this folder from my development machine but is sounds a bit messy!
So I was wondering if there are standalone versions that I can plug into MSBuild without installing Visual Studio. Any suggestion?
I was trying to build the monodevelop source from https://github.com/mono/monodevelop using MSBuild
While building however the process stops with the error
MSBUILD : error MSB1001: Unknown switch.
Switch: /bl:MonoDevelop.binlog
Here is the line from the winbuild.bat file which is causing the problem
"%MSBUILD_EXE%" Main.sln /bl:MonoDevelop.binlog /m "/p:Configuration=%CONFIG%" "/p:Platform=%PLATFORM%" %* || goto :error
I am using Visual Studio 2017 Community Edition 15.2 (26430.14) running on Windows 10 Home
I can't seem to figure what's causing this issue. Google hasn't helped either. I hope someone over here can help me figure this out.
Update your Visual Studio to a recent version.
Binary logs have been introduced in MSBuild 15.3, with a few bugfixes in later versions.
The current VS and MSBuild versions are 15.6.*, make sure you update to the latest versions of the tools.
Check what is the switch ('/bl:MonoDevelop.binlog') is ? Are you using this switch for any reason ? If you don't have the answer comment/remove the switch and run the MS Build.
Maybe MS Build don't know why this switch is!
I have Windows 7 installation with 32 bit JDK.
When I try to run MuleStudio.exe I get the following error:
You need to download the 32 bit edition, which is rather hard to find on the first page.
Deprecation notice: The link is valid just for Mule Studio and not for the new Anypoint Studio. Basically think link is just for historical purposes here and there is a 99% chance this is the wrong link for you.
Check the All Mule Studio Downloads page. and select the 32 bit version.
another solution:
open your AnypointStudio.ini with notepad
add or edit the vm
-vm
C:\Program Files\Java\jdk1.8.0_151\bin // edit this with the path of your installed jdk
I have installed TFS 2010 including Build Service on a Win Srv 2008 R2 machine, and it works - almost.
What I can't seem to get going is the build using tools like resgen.exe from the Windows SDK - I get an error:
c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets
(1835):
Task could not find "Resgen.exe" using the SdkToolsPath
"C:\Program Files (x86)\Microsoft
SDKs\Windows\v7.0A\Bin\" or the
registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SDKs\Windows\v7.0A". Make sure the
SdkToolsPath is set and the tool
exists in the correct processor
specific location under the
SdkToolsPath and that the Microsoft
Windows SDK is installed
OK, so I went and downloaded and installed the most recent Windows SDK - v7.1. Everything went fine, I now have a copy of resgen.exe present and all - but I am still getting the same error.
OK, so I went and inspected the MSBuild targets file (c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets) mentioned in the error message - and I see it's using lots of references to FrameworkSDKDir and _TargetFrameworkSDKDirectoryItem - but where are those values initially set (to an obviously wrong directory, in my case) ?? I can't seem to find the "core" targets file and tell it to use my \SDKs\Windows\v7.1\Bin directory (instead of the \SDKs\Windows\v7.0A\Bin it wants to find - there's nothing in there...)
I think that the real problem is integration of the SDK v7.1 with VS2010.