I get the below error message when I try to run the command in VSCode.
Command "maven.archetype.generate" fails. Cannot read property 'length' of undefined
As far as I can see, I have all plugins/extensions but cannot work out why it won't work. I found this but still cannot get it to work, however I can run apps for files created before I updated VSCode to version 1.32.1. I just cannot create new ones.
It's look like a bug.
Are you running the commands without any workspace or folder open?
Open a folder first, see if the issue still exists. If it's gone, I
suppose it's because of a potential NPE which is fixed by PR #276 but
not released yet. Please let me know the result.
It worked for me!
See more: https://github.com/Microsoft/vscode-maven/issues/277#issuecomment-473166245
From command line, type in:
mvn --version
to see if Maven is installed properly.
You need maven and jdk installed for maven to work.
Check out the “Before you begin” here:
https://code.visualstudio.com/docs/java/java-tutorial#_create-the-program
What is probably happening is that you do not have Maven or JDK installed, or you have not set the system variables properly. These installations are not the same as the plugins/extensions found in Visual Studio Code. These are in addition to that.
Related
When i try to execute "solana-test-validator" command in my terminal, i get error and it says:
"libcrypto1_1-x64.dll not found"
"libssl-1_1-x64.dll not found"
I searched everywhere and i looked every solana-test-validator related error things but i never be able to solve my problem.
Here is how I solved it. The solution is in the problem. It needs those two DLL files. Therefore, find a correct version of the both the DLL over the internet and paste in the solana active-release path or if you have zoom installed, you can copy the DLLs from there.
Zoom Location - C:\Users\Asus\AppData\Roaming\Zoom\bin
Solana Active release - C:\Users\Asus\.local\share\solana\install\active_release\bin
Once you copy paste the DLLs, just start the CMD as an admin and run
solana-test-validator
I solved my problem by reinstalling the Ubuntu terminal.
I need sbt version 0.13.x for a course in Scala and I am having difficulties installing it. I tried with the brew install sbt#0.13 command, but when I then check with sbt about it gives a message No such file or directory.
However, if I again try and do brew install sbt#0.13, it gives Warning: sbt#0.13 0.13.16 is already installed, although sbt about does not find anything.
In addition to that, I tried installing the latest version of sbt with brew install sbt and then manually changing the version each of my projects is using by entering sbt.version=0.13.12 in a given build.properties file. This seemed to work initially, when I check with the terminal the version of sbt inside the project. However, I am still not able to import already existing projects.
Finally, I downloaded the version from http://www.scala-sbt.org/download.html but then I need to do some corrections to my PATH from what I've read online and I am not sure what that means.
So, I would be grateful if someone could help me with the installation of an older version.
The way sbt works is that it will look in project/build.properties for the sbt version to use to build your project. So the way you described - installing the latest sbt and set the version you want to use for the build in project/build.properties - should work just fine.
Regarding
not able to import already existing projects
these existing projects also should have project/build.properties indicating the sbt version.
Note that even with installing 0.13.12 locally, when building your project sbt will still use the version specified in project/build.properties, it will just download it as necessary.
If you absolutely want to run a specific version from the command line, as you already discovered, you can download it. Regarding updating your PATH - PATH is an environment variable that tells your command line where to look for executable files. It's a list of directories, so if you unpacked the downloaded file in say "$HOME/tools", you have so say something like export PATH=$HOME/tools/sbt/bin:$PATH. See https://www.cyberciti.biz/faq/appleosx-bash-unix-change-set-path-environment-variable/ for a more detailed description.
As you can see near the screenshot Logs infos pic, the .sh Script can run normal inside terminal, but failed to run via Xcode custom behavior, Is there missing some configuration? I've Googled a lot of infos. still can't solve it. I really need someone's help. Thanks
XCode version: Version 8.3.2 (8E2002)
Add a New Run Script Phase in your projects Build Phases to run a Shell script. You do not need to open -a Terminal:
Update:
How I understand your comment, your actual question is how to get the Xcode project directory. Xcode provides a enviromental variable for this, ${PROJECT_DIR}:
prints:
You can find a list of Xcodes enviromental variables in this repo and helpful information in Apples documentation.
I'm trying to setup a project and I get the following error in the output OmniSharpLog
[ERROR:OmniSharp.Dnx.DesignTimeHostManager] Failed to launch DesignTimeHost in a timely fashion.
I can't seem to find any documentation about this error elsewhere and I have absolutely no clue as to how to circumvent it.
My dnu restore command completed successfully.
I found this link and thought it could help me. Luckily, the steps worked! I fixed my issue by first installing/downgrading to dnvm 1.0.0-beta4, I was at 6.
dnvm install 1.0.0-beta4
then explicitly pointing to that version like so,
dnvm use 1.0.0-beta4
Everything ran perfectly fine after that.
When I run svnversion from the command line, I see version "3978" which is correct.
However, when I run this in a build script in Xcode 4.6.3 from the same directory I see "exported".
Why is this and how can I resolve this?
(My client and server are on SVN 1.7. According to the redbook, this can happen when svnversion is invoked on a directory that is not a working copy but this perhaps doesn't seem to be the case here.)
Digging into Xcode 4.6.3's package contents, in Contents/Developer/usr/bin the version of svn bundled with Xcode is 1.6.18, while the system version is 1.7.10. This seems to explain the mismatch.
Symlinking to /opt/local/bin/svn* in Contents/Developer/usr/bin resolved this for me.