Unmanaged dependency failed to be resolved about heroku-buildpack-java HOT 10 CLOSED

hi @fgarsombke , check your .gitignore file, maybe you should remove the *.jar in it
I met the same problem. I finally find the .gitignore ignore all *.jarso you're not able to submit your jar to heroku.

from heroku-buildpack-java.

Arggh...markdown. Here are the correct POM elements.

<repository>
  <id>project.local</id>
  <name>project</name>
  <url>file:${project.basedir}/repo</url>
</repository>

<dependency>
    <groupId>pubnub</groupId>
    <artifactId>pubnub-java</artifactId>
     <version>3.4</version>
 </dependency>

from heroku-buildpack-java.

Locally, can you try first deleting it from your $HOME/.m2/repository directory and then trying the build? If you already have the dependency in your $HOME/.m2/repository directory, Maven will find it from there and ignore the repo you added to your POM. It's probably easier to just manually delete the dependency from $HOME/.m2/repository, but the dependency:purge-local-repository might be helpful if you have a lot of them.

from heroku-buildpack-java.

I did already do that and it 'downloads' the file successfully into my local repository on my local instance. :)

from heroku-buildpack-java.

Hmm, there should be nothing special about Maven on Heroku that would cause a difference. Just to make sure, have you have added and committed the files into the Git repo? Can you paste in the snippet of your POM and what your file structure of repo looks like?

from heroku-buildpack-java.

Yes the repo has been committed to github. I double checked :)

It seems really straight forward doing this...but for some reason doesn't work.

Here are the repo files:

repo/pubnub/pubnub-java/3.4/pubnub-java-3.4.jar.md5
repo/pubnub/pubnub-java/3.4/pubnub-java-3.4.jar.sha1
repo/pubnub/pubnub-java/3.4/pubnub-java-3.4.pom
repo/pubnub/pubnub-java/3.4/pubnub-java-3.4.pom.md5
repo/pubnub/pubnub-java/3.4/pubnub-java-3.4.pom.sha1
repo/pubnub/pubnub-java/maven-metadata.xml
repo/pubnub/pubnub-java/maven-metadata.xml.md5
repo/pubnub/pubnub-java/maven-metadata.xml.sha1

Here is the POM:

......

I do have a workaround and I ended up adding these files to my project which is definitely not a best practice, but allowed me to move forward for now.

Thank you for taking the time to try and diagnose this issue. I have been using Maven for quite some time so hopefully I haven't made any rookie mistakes :)

Franz

from heroku-buildpack-java.

thanks @jcouyang! I actually had the same problem and been banging my head against the wall, never realised that the jar hasn't been sent, and that fixed it for me.

from heroku-buildpack-java.

Thank @jcouyang ! ,,,, finally found this ..... 👍

from heroku-buildpack-java.

hi, @jcouyang thanks for you help.

from heroku-buildpack-java.

Thanks @jcouyang for saving the day.

from heroku-buildpack-java.