Error parsing command line: While parsing option --input F:\newRush\rush\bin\m\deps\MyLibrary-1.0.4.jar: F:\newRush\rush\bin\m\deps\MyLibrary-1.0.4.jar is not a valid path: it does not exist.
Please be a bit more specific and paste the complete build log here.
Build failed because of soo many source files?
│ info Picked 980 source files
└ failed
• Build failed [108ms] []
Just out of curiosity, how did you end up with so many source files for an extension?!
Copying out soo many files because jars don’t work 
Wdym? JARs should work!
No, I mean I could not find the jar files corrctly and most of them throw error, well there is no fault of rush here for Jars. 
Edit: so, why is the compile error
No one can help you if you’re not gonna explain why you couldn’t find the dependencies and why most of them throw errors. Your language is also a little not so understandable because of the “well there is no fault of rush here for Jars.” Be more clear and concise, and you can probably fix the issue. But @Shreyash needs to know what you did up until the point of building your extension.
He already gave me a solution in the PM.
Waiting to try it, but there are some problems.
What do you mean by “explain why you couldn’t find the dependencies”?
I am having some problems compiling them, I have already said ‘most of them throw error’ Did not you read it?
Almost everyone except you knows what I mean (most of them), I also just don’t want to reveal what is not working.
You just keep writing long sentences. Which could be explained in a few words.
No-fault of rush means, while adding the Jars, it was not a problem of Rush, you understand now?
I am talking about that compile error (unrelated to the functionality of adding Jars).
@Shreyash it seems that you must also enable desugaring even when using Kotlin (if you use things like…
return if(true){/** do things **/ "Hello world!"} else {/** do things **/ ""}
… In a PM you told me it only had to be enabled with Java?
No, I don’t think so.
Hmm? I don’t remember I ever had a PM w/ you where I said this. Anyways, just to make this clear, desuagring is only needed if your extension and/or one or more of its dependencies use Java 8 language features mentioned here. It doesn’t matter which language you’re using.
? language
Java
Kotlin
Im sorry, how to choose kotlin language how to do it ?
It literally tells you to use the up and down arrows on your keyboard…
1 Like
ok thanks 
1 Like
Rush v1.2.2
This minor release fixes some crucial bugs and introduces a couple of improvements.
Improvements 
-
Development dependencies are now centralized for all Rush projects. This makes Rush more disk efficient by not copying the
dev-depsfolder for every extension project. -
Creating a new extension will now fail if a directory with the same name already exists in the current working directory.
Bug fixes 
-
Fixed the issue that caused Rush to crash because of stack overflow while parsing
@SimplePropertyannotations. [ref] -
Fixed the issue where Rush won’t be able to compile too many source files. [ref]
-
Fixed the issue where the compilation would fail if the extension source file didn’t define any block annotations.
Internal changes 
- Migrated the annotations, processor, and migrator modules in the Rush annotation processor repo to Kotlin.
Installation 
To upgrade to v1.2.2 from v1.2.1, simply run rush upgrade. If you are on any other version, you will need to reinstall Rush.
To install Rush, follow the installation instructions in the first post:
Cheers,
Shreyash
7 Likes
Thats the unique one 
Thanks for the update
3 Likes
Some of the imported library issue remains in IDE for old rush project even after changing project structure
Oh, I missed it. Will release a hotfix soon.
1 Like
Np,
Waiting 