jcabi / jcabi-heroku-maven-plugin

Maven Plugin for Deploying to Heroku

This project is just a parent POM for all other Java projects in "jcabi family".

See www.jcabi.com website for more details.

jcabi-heroku-maven-plugin's Issues

0.10

Please, publish a new release 0.10 (or higher). Don't forget to update us here regularly (at least once a week), as explained in this article.

Qulice configuration - no license specified.

1. Checkout master branch
2. run mvn qulice:check -Pqulice
3. There are multiple Line does not match expected header line of ' * BSD License'. (HeaderCheck) messages.

This is a known bug of qulice configuration in parent-0.31 (jcabi/jcabi-parent#19), accessed via jcabi-0.16. Suggested action is waiting until jcabi/jcabi#297 fix is released and upgrading jcabi version.

Estimate project size

There is no estimate in the project yet. We have to create one as explained here

JCABI heroku plugin documentation

jcabi heroku plugin documentation is very minimal. As a newbie to Heroku, the documentation is very small to appreciate its usefulness. Having used jcabi logging and jcabi cache I am sure this would also be great! Can documentation be extended with step by step procedure for a small app.

Indie tech review no.1

Review our existing source code and all other technical artifacts and report at least 8 bugs. More about such reviews you can read here. The task will be closed once we have that bugs reported and classified. Don't forget to add itr tag to each of them.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency org.apache.maven:maven-core to v3.8.1 [SECURITY]
• Update dependency com.jcabi:jcabi to v1.39.0
• Update maven.version to v3.9.6 (org.apache.maven:maven-model, org.apache.maven:maven-settings, org.apache.maven:maven-artifact, org.apache.maven:maven-plugin-api)
• Update actions/cache action to v4
• Update actions/checkout action to v4
• Update actions/setup-java action to v4
• Update codecov/codecov-action action to v4
• Update dependency ubuntu to v22
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/codecov.yml

• actions/checkout v3
• actions/setup-java v3
• actions/cache v3
• codecov/codecov-action v3
• ubuntu 20.04

.github/workflows/mvn.yml

• actions/checkout v3
• actions/setup-java v3
• actions/cache v3

.github/workflows/pdd.yml

• actions/checkout v3
• ubuntu 20.04

.github/workflows/xcop.yml

• actions/checkout v3
• ubuntu 20.04

maven

pom.xml

• com.jcabi:jcabi 1.18
• com.rexsl:rexsl-test 0.13.3
• org.jfrog.maven.annomojo:maven-plugin-anno 1.4.1
• org.apache.maven:maven-plugin-api 3.0.5
• org.apache.maven:maven-artifact 3.0.5
• org.apache.maven:maven-settings 3.0.5
• org.apache.maven:maven-model 3.0.5
• org.apache.maven:maven-core 3.0.5
• org.jfrog.maven.annomojo:maven-plugin-tools-anno 1.4.1

src/it/skipped-deployment/pom.xml

---

• Check this box to trigger a request for Renovate to run again on this repository

settings.xml missing private key

I recognize the issue with including the private key as part of the deploy up to Heroku
Cf.: this comment in the generated settings.xml:

<!--
  privateKey is not supported at the moment,
  since we're not transferring this file to Heroku.
  Maybe it's a good feature to implement in the future
-->

However, there seems to be a recent issue in the aws-maven plugin that requires it to be present: spring-attic/aws-maven#14

In any case, my app is now no longer able to deploy to Heroku using this plugin because it requires authentication with S3 to upload/download the artifacts and I'm getting 403 errors (per below). When I hardcode a privateKey element (referencing my private key on my local computer) in the generated settings.xml, this succeeds.

[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building 1390673614925 1.0
[INFO] ------------------------------------------------------------------------
[INFO] Downloading: s3://com.example.mvn/snapshot/com/example/fakename/console/fakename-jobs-console/1.13-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: s3://com.example.mvn/release/com/example/fakename/console/fakename-jobs-console/1.13-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: http://repo.maven.apache.org/maven2/com/example/fakename/console/fakename-jobs-console/1.13-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata com.example.fakename.console:fakename-jobs-console:1.13-SNAPSHOT/maven-metadata.xml from/to aws-release (s3://com.example.mvn/release): Access Denied
[WARNING] Could not transfer metadata com.example.fakename.console:fakename-jobs-console:1.13-SNAPSHOT/maven-metadata.xml from/to aws-snapshot (s3://com.example.mvn/snapshot): Access Denied
[WARNING] Failure to transfer com.example.fakename.console:fakename-jobs-console:1.13-SNAPSHOT/maven-metadata.xml from s3://com.example.mvn/release was cached in the local repository, resolution will not be reattempted until the update interval of aws-release has elapsed or updates are forced. Original error: Could not transfer metadata com.example.fakename.console:fakename-jobs-console:1.13-SNAPSHOT/maven-metadata.xml from/to aws-release (s3://com.example.mvn/release): Access Denied
[WARNING] Failure to transfer com.example.fakename.console:fakename-jobs-console:1.13-SNAPSHOT/maven-metadata.xml from s3://com.example.mvn/snapshot was cached in the local repository, resolution will not be reattempted until the update interval of aws-snapshot has elapsed or updates are forced. Original error: Could not transfer metadata com.example.fakename.console:fakename-jobs-console:1.13-SNAPSHOT/maven-metadata.xml from/to aws-snapshot (s3://com.example.mvn/snapshot): Access Denied
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ fakename-jobs-console-pom ---
[INFO] 
[INFO] --- maven-dependency-plugin:2.6:copy-dependencies (copy) @ fakename-jobs-console-pom ---
[INFO] Copying fakename-jobs-console-1.13-SNAPSHOT.war to /Users/.../target/heroku/fakename-jobs-console.war
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.352s
[INFO] Finished at: Sat Jan 25 13:32:59 EST 2014
[INFO] Final Memory: 11M/27M
[INFO] ------------------------------------------------------------------------

N.b.: real names obscured in the above logfile.

Build failed on windows with lots of EOL violations

@dmarkov Looks like we need to add .gitattributes to force EOL of the repo.

skin 1.4

system.properties for Heroku repo

Thanks for creating the tool I've been looking for :-)

What's the recommended way for a project to bundle up it's jar file and dependencies to work with this plugin?

• If I create an executable fat jar (i.e. all dependencies with main attribute in manifest), it doesn't get pushed up to heroku.
• If I add a main attribute to the manifest, then it's not finding the classes on the classpath.

Would you kindly provide a more sophisticated (i.e. non-web) example that involves multiple 3rd party jar files? (In my case I'm building a Spring Batch job). What should the procfile look like to be compatible?

Thanks!

Copyright section is outdated

Copyright sections still feature 2014 as a year.