-
-
Save jitpack-io/f928a858aa5da08ad9d9662f982da983 to your computer and use it in GitHub Desktop.
install: | |
- FILE="-Dfile=jars/my-library.jar" | |
- mvn install:install-file $FILE -DgroupId=com.github.user -DartifactId=repo -Dversion=1.0 -Dpackaging=jar -DgeneratePom=true |
@jitpack-io Do I need to repeat this for all the .jar
s? Should they all share the same artifactId
, or use a unique one for each jar?
But what about .aar
s? Do I just need to change all instances of jar
to aar
?
dont you need mvn deploy
to deploy things to a remote? mvn install
installs it locally.
this appears to be a file you add to the root of your repo that reconfigures the jitpack build process to use this artifact instead (or as well as? not sure) of building one itself
@jitpack-io how do we dynamically define the version?
Always getting this erro.
ERROR: Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.github.hemanthkaipaa:sapostore:1.1.1.
Show Details
Affected Modules: app
ERROR: Unable to resolve dependency for ':app@debugAndroidTest/compileClasspath': Could not resolve com.github.hemanthkaipaa:sapostore:1.1.1.
Show Details
Affected Modules: app
ERROR: Unable to resolve dependency for ':app@debugUnitTest/compileClasspath': Could not resolve com.github.hemanthkaipaa:sapostore:1.1.1.
Show Details
Affected Modules: app
I have a dependency of 3rd party aar. I'm not aware how to deal with it.
Isn't there any kind of authentication required?
Can everyone upload artifacts named with every github username?
This would be a huge security issue
@kekru the groupId and artifactId will be overwritten by JitPack at the time of build. If you put another username then the groupId will still be 'com.github.YourUsername'
@jitpack-io I published an aar by following that example. but after I used the dependency url and I can't reach the classes that exist on the aar file. it doesn't even available in library folder
For this to work the root directory also needs to have a pom.xml file: