I'll say this again: I think that Heroku is making a mistake by mixing the build and the deploy steps in java applications. A lot of applications are not built using maven, that don't have easily resolvable dependencies, or that might rely on system-specific resources. Additionally, a lot of java shops aren't as comfortable shipping source code out to third parties as the scripting language communities are.
I feel we should be able to deploy wars/jars locally and deploy them directly. It is admittedly different than the rails approach, but it fits the java development process much more naturally. Cheers, Carson On Sep 21, 7:00 pm, TomXH <thomasho...@clear.net> wrote: > I am trying to port a java application to Heroku. The application has > dependencies on many jars. Several of these were available in the > Maven repository so no problem. However, I have a couple that are > not available on public repositories. I added these jars to my local > maven repository using "mvn install:install....". With that, I am > able to build and run my project locally. However, when I push to > Heroku, I get an error indicating "artifacts cannot be resolved". > > What is the best way to make these jar files available to my > application on Heroku? I have to think this is a common problem and > there must be a simple answer. > > Thanks -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
