Hi @Shreyash I made an installer for Rush
Now we dont have to add all the paths manually…
3 Likes
Hi,
Please make sure that you are editing the correct Java file, which in your case should be src/io/sample/sample.java.
Thanks for building it, Pratyush. If you’d like to, please consider creating a PR on GitHub for the same.
1 Like
Ok Thanks
Btw can I know when is the Dependency management system comming? 
Unfortunately, not anytime soon. I underestimated the work it would take to implement it. But yes, it’s definitely coming, just a bit late.
1 Like
Ok I am very excited abt it
Btw you will download the jars from the given package name in the input ?
Wdym? 
He wants to maybe say that the rush will download the dependency (JAR as he saying) from the name…?
1 Like
Oh, ok. I haven’t yet finalized anything yet, but you’d be able to define the required dependencies in deps field in a format similar to Gradle. Something like this:
deps:
- androidx.appcompat:appcompat:1.2.0
Rush will then fetch and cache all the required dependencies locally and you’ll be able to use them in your extensions.
1 Like
Oh yes thats what I was asking
btw can u delete my PR in github…
I will make a new one
And I will also try and work on the Dependency management system (in github)
1 Like
Rush 1.1.0
What’s new 
-
Building extensions is now almost 1.5x faster with Rush! Yes, you heard that right, 1.5x faster than previous versions! Don’t believe me, give it a shot yourself and feel the speed.
-
Want to port your old extension(s) to Rush but fear rewriting those huge manifest annotations? No worries, I got your back. Introducing the
migratecommand!
Simply run rush migratein your extension template’s root directory and let Rush do the rest of the work. Learn more here. -
You can now install Rush using the Rush installer –
rush-init. It’s not a full-blown installer and yeah, there’s still a lot of room for improvement, but hey, it’s better than nothing.
Bug fixes 
-
The notorious “no extension in the
outdirectory” bug is finally fixed (hopefully).
-
Some Android manifest tags weren’t being added to the application’s
AndroidManifest.xmlwhen using Kodular. This issue is now fixed and you should be able to use all the supported manifest elements without any headache. -
Previously, aliasing the
rushcommand and then trying to create/build an extension would throw some weird errors. This is no longer the case and you’d be just fine aliasingrushcommand to whatever you want. -
The
-s(--support-lib) flag used to generate the support library version of your extension even if it didn’t depend on any of the AndroidX packages. Now, Rush will warn you when you unnecessary pass-sflag. -
There was this little bug that would create a directory named
.rushif you runrush buildin a non Rush project directory. It is now fixed.
Internal changes 
-
Rush now no longer depend on Apache Ant to build your extensions. All the compilation, optimization, and packaging are now done by Rush itself.
-
Tweaked quite a few other things that are either too small to notice or too tough to explain. All you need to know is that Rush is now much more stable and faster than it was before.
Installation 
To install, as well as to update, follow the new installation instructions:
I hope this update will make extension development a bit more easier and faster. If you face any issues, as always, create an issue here on GitHub or just leave a reply on this topic. I’ll try to respond ASAP.
Cheers,
Shreyash
6 Likes
Great 
PS:
1 Like
Looks like I am a bit late in the installer part 
1 Like
A new update i’m so excited for it 
2 Likes
Did you let the installer download all the necessary files?
Please re-run the installer. Looks like it was unable to download some files.
1 Like
Deleted the rush folder and now i’m trying to select directory but after selecting dir
cmd closes
Please try running the installer from a terminal. You can do it by opening the terminal in the directory where you’ve downloaded the installer and running ./rush-init-win64.exe.