Cynosphere/bcv-vf
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
bcv-vf/libs
History
Konloch fe57e4f099 Darcula Swapped With DarkLAF 
Now that the swing interaction is working lag free, DarkLaf runs without any performance issues. DarkLAF is an updated version of Darcula so it makes sense to only support one, but if anyone wants it added back we could look at implementing dynamic/custom LAFs down the road using reflection
2021-06-28 17:27:17 -07:00
..
com Darcula Swapped With DarkLAF 2021-06-28 17:27:17 -07:00
eu/bibl/banalysis/byteanalysis Properly handle local dependencies 2021-06-22 21:08:44 +02:00
org/apktool/apktool Reducing jar size by removing unneeded stuff 2021-06-22 22:18:40 +02:00
enjarify-3.zip Re-added Enjarify and Krakatau & license cleanup 2021-06-20 23:48:11 -07:00
Krakatau-11.zip Re-added Enjarify and Krakatau & license cleanup 2021-06-20 23:48:11 -07:00
README.md Reducing jar size by removing unneeded stuff 2021-06-22 22:18:40 +02:00

README.md

Welcome! You have reached the libs folder!

Adding new dependencies

Run the following command (replacing the placeholders first of course!):

mvn deploy:deploy-file -DgroupId=[GROUP-ID] -DartifactId=[ARTIFACT-ID] -Dversion=[VERSION] -Durl=file:./libs -DrepositoryId=local-maven-repo -DupdateReleaseInfo=true -Dfile=[THE-JAR-FILE]

Updating dependencies

Just do the same procedure as in "Adding new dependencies", but with a new version number!

You can also safely delete the old version of the dependency, as nothing will depend on it anymore.

Why the suffix bcv?

Some dependencies may have been modified or could be released by their author in the future. To avoid confusion and dependency clashes in the local repository, the suffix is a nice way to ensure, the right dependency is used in every project (bcv = ByteCode Viewer btw).

Modifications

  • JD-GUI: Removed ASM and RSyntaxTextArea
  • APKTool: Recompiled with the newest dependency versions, removed prebuilt folder