Skip to contentSkip to conversation

java-library: make easy to override jar package name

PATCH In review Nicola Lunghi 2 participants 2 messages Nov 23, 2018

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 java-library: make easy to override jar package name

define JARFILENAME and ALTJARFILENAMES with ?= to make simple to override them

---
 classes/java-library.bbclass | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
classes/java-library.bbclass +2 -2
index ce1cd28..c69cf6b 100644
@@ -42,10 +42,10 @@ PACKAGES += "${JPN}"
 FILES_${JPN} = "${datadir_java}"
 
 # File name of the libraries' main Jar file
-JARFILENAME = "${BP}.jar"
+JARFILENAME ?= "${BP}.jar"
 
 # Space-separated list of alternative file names.
-ALTJARFILENAMES = "${BPN}.jar"
+ALTJARFILENAMES ?= "${BPN}.jar"
 
 # Java "source" distributions often contain precompiled things
 # we want to delete first.
Signature · 1 line
2.19.1
#1 lore raw

✗ patchtest: failure for java-library: make easy to override jar package name

== Series Details ==

Series: java-library: make easy to override jar package name
Revision: 1
URL : https://patchwork.openembedded.org/series/15066/
State : failure

== Summary ==

Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:

* Patch            [meta-java] java-library: make easy to override jar package name
 Issue             Series sent to the wrong mailing list [test_target_mailing_list] 
  Suggested fix    Check the project's README (meta-java) and send the patch to the indicated list

* Issue Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at c80972be1f)

If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).

---

Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe