Cynosphere/bcv-vf
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
bcv-vf/libs
History
Nico Mexis 98e1719f10
Document dependency release process
2021-06-22 21:21:10 +02:00
..
com Properly handle local dependencies 2021-06-22 21:08:44 +02:00
eu/bibl/banalysis/byteanalysis Properly handle local dependencies 2021-06-22 21:08:44 +02:00
org/apktool/apktool Properly handle local dependencies 2021-06-22 21:08:44 +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 Document dependency release process 2021-06-22 21:21:10 +02:00

README.md

Welcome! You have reached the libs folder!

Adding new dependencies

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

mvn deploy:deploy-file -DgroupId=[GROUP-ID] -DartifactId=[ARTIFACT-ID] -Dversion=[VERSION] -Durl=file:. -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).