[jira] [Commented] (MRESOURCES-237) Resource plugin's handling of symbolic links changed in 3.0.x, broke existing behavior
[
https://issues.apache.org/jira/browse/MRESOURCES-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17299977#comment-17299977
]
Andrew Shcheglov commented on MRESOURCES-237:
-
I support [~mirabilos]'s idea with a configuration option. But my case is the
opposite. I have a project with the implementation of a couple of NIO2
filesystems and my "test/resources" directory is full of different kinds of
links: absolute, relative, broken, circular and they should be preserved as-is.
> Resource plugin's handling of symbolic links changed in 3.0.x, broke existing
> behavior
> --
>
> Key: MRESOURCES-237
> URL: https://issues.apache.org/jira/browse/MRESOURCES-237
> Project: Maven Resources Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.1.0, 3.2.0
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T11:41:47-05:00)
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-200.fc25.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Brian D. Johnson
>Assignee: Olivier Lamy
>Priority: Minor
> Fix For: 3.3.0
>
> Attachments: a.tgz
>
>
> It looks like the handling of symbolic links in the
> {{maven-resources-plugin}} has changed in version 3.0.x. I'm submitting a
> JIRA because it breaks the previous behavior and I have not been able to find
> this documented anywhere as an intended change.
> *Use case:* Multi-module maven project. We have a custom log4j2
> configuration file we use during testing. Instead of maintaining this file
> in multiple {{src/test/resources}} directories, we instead maintain a single
> copy of the file at the project's root level and create symbolic links from
> each module's {{src/test/resources}} directory to the file using relative
> paths.
> *2.7 Behavior:* the symlink was evaluated and the target file was copied to
> {{target/test-classes/}}.
> *3.0.x Behavior:* the symlink is copied to {{target/test-classes/}} verbatim.
> The symlink's relative path results in the symlink pointing to the wrong
> file location. The log4j2 configuration is not found.
> *Requested Change:* Either revert to the original 2.7 behavior, or document
> the change and provide a configuration parameter to allow the legacy behavior.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-enforcer] elharo opened a new pull request #95: [MENFORCER-381] include classifiers in error messages
elharo opened a new pull request #95: URL: https://github.com/apache/maven-enforcer/pull/95 @khmarbaise This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (SUREFIRE-1893) New maven-surefire JUnit5 extension by Fabricio Yamamoto
[ https://issues.apache.org/jira/browse/SUREFIRE-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1893. -- Resolution: Fixed https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=c00ffe702abc5498f4963f89948c609b475dd9e5 > New maven-surefire JUnit5 extension by Fabricio Yamamoto > > > Key: SUREFIRE-1893 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1893 > Project: Maven Surefire > Issue Type: New Feature > Components: documentation, JUnit 5.x support, Maven Failsafe Plugin, > Maven Surefire Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Fix For: 3.0.0-M6 > > Attachments: junit5extension.png > > > https://github.com/fabriciorby/maven-surefire-junit5-tree-reporter -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SUREFIRE-1893) New maven-surefire JUnit5 extension by Fabricio Yamamoto
[ https://issues.apache.org/jira/browse/SUREFIRE-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1893: --- Summary: New maven-surefire JUnit5 extension by Fabricio Yamamoto (was: New maven-surefire JUnit5 extension API by Fabricio Yamamoto) > New maven-surefire JUnit5 extension by Fabricio Yamamoto > > > Key: SUREFIRE-1893 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1893 > Project: Maven Surefire > Issue Type: New Feature > Components: documentation, JUnit 5.x support, Maven Failsafe Plugin, > Maven Surefire Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Fix For: 3.0.0-M6 > > Attachments: junit5extension.png > > > https://github.com/fabriciorby/maven-surefire-junit5-tree-reporter -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SUREFIRE-1894) Surefire report XML schema is incomplete (attribute version not allowed in testsuite)
[ https://issues.apache.org/jira/browse/SUREFIRE-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1894. -- Resolution: Fixed https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=14e8e1acd97e9e92ef9b36f31e9d21f11c8cbac7 > Surefire report XML schema is incomplete (attribute version not allowed in > testsuite) > - > > Key: SUREFIRE-1894 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1894 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin, Maven Surefire Report Plugin >Affects Versions: 3.0.0-M5 >Reporter: Martin Morgenstern >Assignee: Tibor Digana >Priority: Minor > Fix For: 3.0.0-M6 > > > When using the schema > _maven-surefire-plugin/src/site/resources/xsd/surefire-test-report-3.0.xsd_ > to validate an XML report (TEST-*.xml) created with maven-surefire 3.0.0-M5, > validators complain that the attribute _version_ is not allowed to appear in > the element _testsuite_. However, this attribute was added to the XML report > as part of commit > [edb3b71b9|https://github.com/apache/maven-surefire/commit/edb3b71b95db98eef6a8e4fa98d376fd3512b05a#diff-c634b539151b4b76bde50d93d5a6cd2b0f51aa411281398cc295cc721bdfa1d5] > for SUREFIRE-1590. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-surefire] Tibor17 merged pull request #341: [SUREFIRE-1894] Add missing "version" attribute to report XSD
Tibor17 merged pull request #341: URL: https://github.com/apache/maven-surefire/pull/341 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] Tibor17 commented on pull request #341: [SUREFIRE-1894] Add missing "version" attribute to report XSD
Tibor17 commented on pull request #341: URL: https://github.com/apache/maven-surefire/pull/341#issuecomment-797026379 @martinmo The test verifies XML against the schema which is very suitable in this case. If the test fails without your fix and passed with it, then it is acceptable. Thx. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (SUREFIRE-1894) Surefire report XML schema is incomplete (attribute version not allowed in testsuite)
[ https://issues.apache.org/jira/browse/SUREFIRE-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1894: --- Fix Version/s: 3.0.0-M6 > Surefire report XML schema is incomplete (attribute version not allowed in > testsuite) > - > > Key: SUREFIRE-1894 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1894 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin, Maven Surefire Report Plugin >Affects Versions: 3.0.0-M5 >Reporter: Martin Morgenstern >Assignee: Tibor Digana >Priority: Minor > Fix For: 3.0.0-M6 > > > When using the schema > _maven-surefire-plugin/src/site/resources/xsd/surefire-test-report-3.0.xsd_ > to validate an XML report (TEST-*.xml) created with maven-surefire 3.0.0-M5, > validators complain that the attribute _version_ is not allowed to appear in > the element _testsuite_. However, this attribute was added to the XML report > as part of commit > [edb3b71b9|https://github.com/apache/maven-surefire/commit/edb3b71b95db98eef6a8e4fa98d376fd3512b05a#diff-c634b539151b4b76bde50d93d5a6cd2b0f51aa411281398cc295cc721bdfa1d5] > for SUREFIRE-1590. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SUREFIRE-1894) Surefire report XML schema is incomplete (attribute version not allowed in testsuite)
[ https://issues.apache.org/jira/browse/SUREFIRE-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1894: -- Assignee: Tibor Digana > Surefire report XML schema is incomplete (attribute version not allowed in > testsuite) > - > > Key: SUREFIRE-1894 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1894 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin, Maven Surefire Report Plugin >Affects Versions: 3.0.0-M5 >Reporter: Martin Morgenstern >Assignee: Tibor Digana >Priority: Minor > > When using the schema > _maven-surefire-plugin/src/site/resources/xsd/surefire-test-report-3.0.xsd_ > to validate an XML report (TEST-*.xml) created with maven-surefire 3.0.0-M5, > validators complain that the attribute _version_ is not allowed to appear in > the element _testsuite_. However, this attribute was added to the XML report > as part of commit > [edb3b71b9|https://github.com/apache/maven-surefire/commit/edb3b71b95db98eef6a8e4fa98d376fd3512b05a#diff-c634b539151b4b76bde50d93d5a6cd2b0f51aa411281398cc295cc721bdfa1d5] > for SUREFIRE-1590. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-surefire] rmannibucau commented on a change in pull request #340: [SUREFIRE-1892] ensure systemPropertyVariables values are stringified
rmannibucau commented on a change in pull request #340:
URL: https://github.com/apache/maven-surefire/pull/340#discussion_r59255
##
File path:
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
##
@@ -3623,9 +3623,20 @@ public void setSystemProperties( Properties
systemProperties )
}
@SuppressWarnings( "UnusedDeclaration" )
-public void setSystemPropertyVariables( Map
systemPropertyVariables )
+public void setSystemPropertyVariables( Map
systemPropertyVariables )
{
-this.systemPropertyVariables = systemPropertyVariables;
+if (systemPropertyVariables != null)
+{
+this.systemPropertyVariables = new HashMap<>();
+for ( final Map.Entry entry :
systemPropertyVariables.entrySet() )
+{
+this.systemPropertyVariables.put( entry.getKey(),
String.valueOf( entry.getValue() ) );
Review comment:
Right, but once again it is not the main reason to not fix it there as
explained.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-surefire] Tibor17 commented on a change in pull request #340: [SUREFIRE-1892] ensure systemPropertyVariables values are stringified
Tibor17 commented on a change in pull request #340:
URL: https://github.com/apache/maven-surefire/pull/340#discussion_r592486479
##
File path:
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
##
@@ -3623,9 +3623,20 @@ public void setSystemProperties( Properties
systemProperties )
}
@SuppressWarnings( "UnusedDeclaration" )
-public void setSystemPropertyVariables( Map
systemPropertyVariables )
+public void setSystemPropertyVariables( Map
systemPropertyVariables )
{
-this.systemPropertyVariables = systemPropertyVariables;
+if (systemPropertyVariables != null)
+{
+this.systemPropertyVariables = new HashMap<>();
+for ( final Map.Entry entry :
systemPropertyVariables.entrySet() )
+{
+this.systemPropertyVariables.put( entry.getKey(),
String.valueOf( entry.getValue() ) );
Review comment:
Even if the utility class is public, still the method
`calculateEffectiveProperties` is package private, and `copyProperties` is
private.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Closed] (MEAR-299) KungfuQQ Situs Agen IDN Poker Online Deposit Via Pulsa Tanpa Potongan
[ https://issues.apache.org/jira/browse/MEAR-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders closed MEAR-299. Resolution: Invalid > KungfuQQ Situs Agen IDN Poker Online Deposit Via Pulsa Tanpa Potongan > - > > Key: MEAR-299 > URL: https://issues.apache.org/jira/browse/MEAR-299 > Project: Maven EAR Plugin > Issue Type: New Feature >Reporter: KungfuQQ Situs Agen IDN Poker Online Deposit Via Pulsa > Tanpa Potongan >Priority: Trivial > Labels: newbie > Attachments: bisa gila la.jpg > > Original Estimate: 2,148h > Remaining Estimate: 2,148h > > KungfuQQ Situs IDN Poker Online Terpercaya di Tahun 2021 Deposit Pulsa Tanpa > Potongan. > KungfuQQ merupakan salah satu Situs IDN Poker Online yang hadir sejak tahun > 2015 hingga saat ini masih berkembang dan memberikan layanan terbaik serta > memberikan keuntungan yang sangat besar. Di KungfuQQ juga memiliki Lisensi > Resmi, ini membuktikan bahwa situs IDN Poker KungfuQQ ini menjadi salah satu > Situs IDN Poker Online Terpercaya saat ini. > Untuk bermain di KungfuQQ anda di wajibkan untuk melakukan deposit yang > besar, sehingga akan membebani biaya anda nantinya. Cukup dengan 10ribu saja > anda sudah bisa bermain poker dan mendapatkan kemenangan yang besar di > KungfuQQ ini. Dengan bermodalkan 10ribu saja tentu saja itu tidak akan > membuat anda merasakan rugi bukan? > Nah, untuk deposit di KungfuQQ anda bisa melalui Bank yang ada. Karena > KungfuQQ sudah bekerja sama dengan Bank-Bank lokal Ternama di Indonesia ini. > Dengan adanya kerjasama dengan bank lokal, ini akan mempermudah anda di saat > ingin melakukan deposit dan penarikan dana. Sebab bank yang tersedia di > kungfuQQ semua Online 24 jam setiap harinya. > Tidak hanya itu saja, jika anda merasa males pergi ke bank atau mesin ATM > yang dikarenakan jauh dari rumah, anda tidak perlu khawatir. Sebab di > kungfuQQ sudah menyediakan Deposit Via Pulsa yang akan membantu anda dalam > melakukan deposit di kala ingin melakukan permainan tersebut. Untuk melakukan > deposit Via Pulsa di KungfuQQ, anda tidak perlu khawatir dengan ada nya > potongan. > Karena jika anda melakukan deposit Via Pulsa Di KungfuQQ anda tidak akan di > kenakan potongan apapun, jadi berapa saja yang anda kirim maka akan lagsung > di proseskan ke dalam akun anda. Untuk proses deposit dan juga witdhraw di > kungfuQQ, sangatlah cepat sekali di lakukan. Hanya dalam kurang dari 1 menit > saja semua sudah di proseskan untuk anda. > Kemudian untuk pendaftaran di kungfuQQ juga tidak di kenakan biaya apapun, > Pendaftaran 100% GRATIS dan mudah untuk di lakukan. Anda hanya perlu > menyediakan nama rekening, nomor rekening, email dan nomor HP atau WA anda. > Silahkan kunjungkin situs kungfuQQ dengan klik link berikut ini kungfuqq.net. > Jika anda merasakan bingung di saat melakukan pendaftaran di kungfuqq, anda > tidak perlu khawatir. Sebab di kungfuqq memiliki Layanan Customer Service > yang akan membantu anda dalam melakukan pendaftaran Akun tersebut. Customer > Service di kungfuQQ selalu siap melayanin anda kapan saja. Karena Layanan ini > selalu Aktif atau online 24 jam setiap hari nya. > Serta untuk pelayanan yang akan diberikan untuk anda juga sangat ramah dan > juga sudah profesional. Jadi jika anda memiliki pertanyaan yang tidak di > menggerti seputar permainan, deposit atau withdraw. Anda bisa lagsung chat ke > layanan Customer Service tersebut. Dan kungfuQQ juga memiliki Nomor WA yang > bisa anda hubungin, jadi anda tidak perlu selalu datang ke livechat jika > ingin menayakan sesuatu. > Kemudian, jika anda sudah berhasil bergabung dengan kungfuQQ, anda jugak bisa > mendapatkan bonus besar di saat anda melakukan deposit pertama kalinya. Tidak > hanya memberikan deposit member baru saja, di kungfuQQ juga akan memberikan > bonus setiap harinya untuk para membernya dan masih banyak bonus lainnya > lagi. Penasaran dengan bonus tersebut, berikut ini : > - Bonus Member Baru 20% > - Bonus Deposit Harian 10% > - Bonus Turnover 0.5% Setiap Hari Kamis > - Bonus Referral 20% Seumur Hidup > Itu semua bonus besar yang bisa anda dapatkan di Situs IDN POker KungfuQQ > Deposit Via Pulsa Tanpa Potongan ini, Jadi lagsung saja daftarkan diri anda > sekrang juga dan rasakan semua keuntungan anda bermain poker menggunakan > pulsa tanpa potongan ini. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MEAR-300) KungfuQQ Web IDN Poker Online Dengan Bonus Terbesar Di Indonesia
[ https://issues.apache.org/jira/browse/MEAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders closed MEAR-300. Resolution: Invalid > KungfuQQ Web IDN Poker Online Dengan Bonus Terbesar Di Indonesia > > > Key: MEAR-300 > URL: https://issues.apache.org/jira/browse/MEAR-300 > Project: Maven EAR Plugin > Issue Type: Task >Affects Versions: 2.10.1, 3.2.0 >Reporter: KungfuQQ Situs Agen IDN Poker Online Deposit Via Pulsa > Tanpa Potongan >Priority: Minor > Labels: newbie > Attachments: backkungfu1.jpg > > Original Estimate: 2,268h > Remaining Estimate: 2,268h > > KUNGFUQQ ialah Catatan Web Agen Judi IDN Poker Online 88 Terpercaya sangat > terkenal dengan bermacam tipe game kartu terlengkap di indonesia. Disini kami > web judi poker online sediakan banyak sekali tipe game di mulai dari: Poker, > bandar ceme keliling, ceme online, capsa susun, dominoqq, omaha, super10, > superbull serta blackjack. Seluruhnya lumayan dengan satu akun idn poker saja > yang bisa kalian mainkan lewat hp android ataupun ios. > Coba hoki Kamu di salah satu dari 10 web poker online terpercaya duit asli > KUNGFUQQ serta miliki bonus free. Salurkan masing- masing hari demi chip > lebih banyak lagi. Untuk Kalian yang lagi mencari game judi online terpercaya > indonesia, hingga tidak salah lagi bila memilah kami KUNGFUQQ. Selaku layanan > agen poker terbaik, web judi online terpopuler indonesia. KUNGFUQQ bisa di > mainkan secara gampang lewat apk IDN Poker android maupun iphone serta pasti > nya dengan deposit terkecil di mulai dari 25. 000 kamu telah dapat > berkesempatan bermain serta menang sampai jutaan rupiah. > POKER ONLINE TERBARU > Web catatan poker online terkini KUNGFUQQ dapat buat akun melalui hp > android ios terkini dengan tampilan modern. Itu yang banyak digemari > bermacam golongan dari pemain poker dikala ini. Poker IDNPLAY bisa dimainkan > lumayan dengan memakai smartphone kesayangan kamu. Kamu tidak butuh takut > buat menanggulangi kesusahan dalam memainkan permainan poker maupun > keterbatasan tempat serta waktu buat bermain. Lekas bergabung saat ini pula > buat menikmati seluruh tipe poker online yang sudah disediakan cuma dengan 1 > ID saja. > BONUS NEW MEMBER Web POKER ONLINE TERBAIK Terbanyak SE INDONESIA > KUNGFUQQ membagikan kemudahan dalam melaksanakan registrasi kepada tiap > pemain yang mau bergabung bersama web poker online. Banyaknya bonus dan > keuntungan paling banyak yang diberikan secara cuma- cuma disini. Kami pula > membagikan dorongan kepada para pemain yang berkesulitan dalam melaksanakan > registrasi ID Poker Online. Ada pula ada persoalan seputar pendaftaran yang > kurang dipahami silahkan menghubungi lewat livechat yang sudah kami sajikan > dibawah kanan tampilan kamu. > PROMO BONUS NEW MEMBER 20% > PROMO BONUS DEPOSIT Setiap hari 10% > PROMO BONUS TURNOVER TO UP TO 054% > PROMO BONUS REFERRAL UP TO 100% > Kenyamanan serta Kelebihan Bersama Web IDN Poker Online Terkini KUNGFUQQ > Tidak hanya Lengkap nya Game kartu, di KUNGFUQQ seluruh golongan pemain di > mulai dari kecil sampai pemain besar merupakan sama di mata kami sehingga > seluruh pelayanan merupakan adil serta pasti nya Game merupakan FAIRPLAY > tanpa terdapat kecurangan apapun di dukung dengan Teknologi yang Terkini > sehingga game begitu mudah, serta semacam yang di tahu banyak peminat judi qq > online server IDN Poker ini serta teruji memilah KUNGFUQQ selaku web judi > poker qq online terpercaya ini > Pelayanan Terbaik Agen Poker Online IDNPLAY serta Judi Domino QQ online > KUNGFUQQ > Pihak KUNGFUQQ mengosongkan Sarana Aplikasi Idnplay yg telah populer dapat di > akses dari APK IDN Poker ANDROID serta IOS. Jadi kapanpun serta di manapun > member bisa bermain dengan Mudah serta nyaman. Tidak hanya tersebut KUNGFUQQ > menyerahkan pelayanan web judi poker qq IDN terbaik dalam mengawal tiap > kenyamanan member yang lagi bermain judi IDN Poker domino qq ini. Web IDN > Poker KUNGFUQQ menggunakan transaksi Deposit dana ataupun tarik dana online > 24 jam setiap harinya dengan sokongan bank paling lengkap dan ternama yang > menerima segala jenis transaksi dari segala bank yang ada di indonesia > Salah satu web dari lapisan poker online terpercaya yakni dari web gemparqq. > Yang mana web judi on line yang satu ini diketahui selaku agen poker online > terpercaya yang sangat tidak sedikit sediakan promo serta bonus. Sehingga, > ini bakal sangat cocok sekali buat kalian yang membidik web judi qq online > terpercaya yang berlimpah promo serta bonusnya. > Tetapi, yang sangat utama dari web judi poker online terpercaya ini yakni > kamu dapat memainkan 9 game, baik domino ataupun poker melulu dalam 1 user > ID. Serta tidak perlu ragu karena web gemparqq ini
[jira] [Created] (MNG-7114) Publish XSDs as artifact to Central
Andreas Sewe created MNG-7114:
-
Summary: Publish XSDs as artifact to Central
Key: MNG-7114
URL: https://issues.apache.org/jira/browse/MNG-7114
Project: Maven
Issue Type: Improvement
Reporter: Andreas Sewe
At the moment, a number of XML Schema files for descriptor-like file formats
like archetype or assembly descriptors are only available at
[https://maven.apache.org/xsd/].
This makes them hard to consume, for example, by the {{xml:validate}} goal,
which is IMHO quite well suited for sanity-checking your descriptor files
before packaging and subsequently releasing them.
Would it be possible to release the XSDs under {{org.apache.maven:maven-xsd}}
or a similar coordinate?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MEAR-300) KungfuQQ Web IDN Poker Online Dengan Bonus Terbesar Di Indonesia
KungfuQQ Situs Agen IDN Poker Online Deposit Via Pulsa Tanpa Potongan created MEAR-300: -- Summary: KungfuQQ Web IDN Poker Online Dengan Bonus Terbesar Di Indonesia Key: MEAR-300 URL: https://issues.apache.org/jira/browse/MEAR-300 Project: Maven EAR Plugin Issue Type: Task Affects Versions: 3.2.0, 2.10.1 Reporter: KungfuQQ Situs Agen IDN Poker Online Deposit Via Pulsa Tanpa Potongan Attachments: backkungfu1.jpg KUNGFUQQ ialah Catatan Web Agen Judi IDN Poker Online 88 Terpercaya sangat terkenal dengan bermacam tipe game kartu terlengkap di indonesia. Disini kami web judi poker online sediakan banyak sekali tipe game di mulai dari: Poker, bandar ceme keliling, ceme online, capsa susun, dominoqq, omaha, super10, superbull serta blackjack. Seluruhnya lumayan dengan satu akun idn poker saja yang bisa kalian mainkan lewat hp android ataupun ios. Coba hoki Kamu di salah satu dari 10 web poker online terpercaya duit asli KUNGFUQQ serta miliki bonus free. Salurkan masing- masing hari demi chip lebih banyak lagi. Untuk Kalian yang lagi mencari game judi online terpercaya indonesia, hingga tidak salah lagi bila memilah kami KUNGFUQQ. Selaku layanan agen poker terbaik, web judi online terpopuler indonesia. KUNGFUQQ bisa di mainkan secara gampang lewat apk IDN Poker android maupun iphone serta pasti nya dengan deposit terkecil di mulai dari 25. 000 kamu telah dapat berkesempatan bermain serta menang sampai jutaan rupiah. POKER ONLINE TERBARU Web catatan poker online terkini KUNGFUQQ dapat buat akun melalui hp android ios terkini dengan tampilan modern. Itu yang banyak digemari bermacam golongan dari pemain poker dikala ini. Poker IDNPLAY bisa dimainkan lumayan dengan memakai smartphone kesayangan kamu. Kamu tidak butuh takut buat menanggulangi kesusahan dalam memainkan permainan poker maupun keterbatasan tempat serta waktu buat bermain. Lekas bergabung saat ini pula buat menikmati seluruh tipe poker online yang sudah disediakan cuma dengan 1 ID saja. BONUS NEW MEMBER Web POKER ONLINE TERBAIK Terbanyak SE INDONESIA KUNGFUQQ membagikan kemudahan dalam melaksanakan registrasi kepada tiap pemain yang mau bergabung bersama web poker online. Banyaknya bonus dan keuntungan paling banyak yang diberikan secara cuma- cuma disini. Kami pula membagikan dorongan kepada para pemain yang berkesulitan dalam melaksanakan registrasi ID Poker Online. Ada pula ada persoalan seputar pendaftaran yang kurang dipahami silahkan menghubungi lewat livechat yang sudah kami sajikan dibawah kanan tampilan kamu. PROMO BONUS NEW MEMBER 20% PROMO BONUS DEPOSIT Setiap hari 10% PROMO BONUS TURNOVER TO UP TO 054% PROMO BONUS REFERRAL UP TO 100% Kenyamanan serta Kelebihan Bersama Web IDN Poker Online Terkini KUNGFUQQ Tidak hanya Lengkap nya Game kartu, di KUNGFUQQ seluruh golongan pemain di mulai dari kecil sampai pemain besar merupakan sama di mata kami sehingga seluruh pelayanan merupakan adil serta pasti nya Game merupakan FAIRPLAY tanpa terdapat kecurangan apapun di dukung dengan Teknologi yang Terkini sehingga game begitu mudah, serta semacam yang di tahu banyak peminat judi qq online server IDN Poker ini serta teruji memilah KUNGFUQQ selaku web judi poker qq online terpercaya ini Pelayanan Terbaik Agen Poker Online IDNPLAY serta Judi Domino QQ online KUNGFUQQ Pihak KUNGFUQQ mengosongkan Sarana Aplikasi Idnplay yg telah populer dapat di akses dari APK IDN Poker ANDROID serta IOS. Jadi kapanpun serta di manapun member bisa bermain dengan Mudah serta nyaman. Tidak hanya tersebut KUNGFUQQ menyerahkan pelayanan web judi poker qq IDN terbaik dalam mengawal tiap kenyamanan member yang lagi bermain judi IDN Poker domino qq ini. Web IDN Poker KUNGFUQQ menggunakan transaksi Deposit dana ataupun tarik dana online 24 jam setiap harinya dengan sokongan bank paling lengkap dan ternama yang menerima segala jenis transaksi dari segala bank yang ada di indonesia Salah satu web dari lapisan poker online terpercaya yakni dari web gemparqq. Yang mana web judi on line yang satu ini diketahui selaku agen poker online terpercaya yang sangat tidak sedikit sediakan promo serta bonus. Sehingga, ini bakal sangat cocok sekali buat kalian yang membidik web judi qq online terpercaya yang berlimpah promo serta bonusnya. Tetapi, yang sangat utama dari web judi poker online terpercaya ini yakni kamu dapat memainkan 9 game, baik domino ataupun poker melulu dalam 1 user ID. Serta tidak perlu ragu karena web gemparqq ini yakni web judi formal. Serta web ini juga merupakan web IDN Poker terbaik yang dapat diandalkan selaku posisi bermain judi kartu online uang asli. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MEAR-299) KungfuQQ Situs Agen IDN Poker Online Deposit Via Pulsa Tanpa Potongan
KungfuQQ Situs Agen IDN Poker Online Deposit Via Pulsa Tanpa Potongan created MEAR-299: -- Summary: KungfuQQ Situs Agen IDN Poker Online Deposit Via Pulsa Tanpa Potongan Key: MEAR-299 URL: https://issues.apache.org/jira/browse/MEAR-299 Project: Maven EAR Plugin Issue Type: New Feature Reporter: KungfuQQ Situs Agen IDN Poker Online Deposit Via Pulsa Tanpa Potongan Attachments: bisa gila la.jpg KungfuQQ Situs IDN Poker Online Terpercaya di Tahun 2021 Deposit Pulsa Tanpa Potongan. KungfuQQ merupakan salah satu Situs IDN Poker Online yang hadir sejak tahun 2015 hingga saat ini masih berkembang dan memberikan layanan terbaik serta memberikan keuntungan yang sangat besar. Di KungfuQQ juga memiliki Lisensi Resmi, ini membuktikan bahwa situs IDN Poker KungfuQQ ini menjadi salah satu Situs IDN Poker Online Terpercaya saat ini. Untuk bermain di KungfuQQ anda di wajibkan untuk melakukan deposit yang besar, sehingga akan membebani biaya anda nantinya. Cukup dengan 10ribu saja anda sudah bisa bermain poker dan mendapatkan kemenangan yang besar di KungfuQQ ini. Dengan bermodalkan 10ribu saja tentu saja itu tidak akan membuat anda merasakan rugi bukan? Nah, untuk deposit di KungfuQQ anda bisa melalui Bank yang ada. Karena KungfuQQ sudah bekerja sama dengan Bank-Bank lokal Ternama di Indonesia ini. Dengan adanya kerjasama dengan bank lokal, ini akan mempermudah anda di saat ingin melakukan deposit dan penarikan dana. Sebab bank yang tersedia di kungfuQQ semua Online 24 jam setiap harinya. Tidak hanya itu saja, jika anda merasa males pergi ke bank atau mesin ATM yang dikarenakan jauh dari rumah, anda tidak perlu khawatir. Sebab di kungfuQQ sudah menyediakan Deposit Via Pulsa yang akan membantu anda dalam melakukan deposit di kala ingin melakukan permainan tersebut. Untuk melakukan deposit Via Pulsa di KungfuQQ, anda tidak perlu khawatir dengan ada nya potongan. Karena jika anda melakukan deposit Via Pulsa Di KungfuQQ anda tidak akan di kenakan potongan apapun, jadi berapa saja yang anda kirim maka akan lagsung di proseskan ke dalam akun anda. Untuk proses deposit dan juga witdhraw di kungfuQQ, sangatlah cepat sekali di lakukan. Hanya dalam kurang dari 1 menit saja semua sudah di proseskan untuk anda. Kemudian untuk pendaftaran di kungfuQQ juga tidak di kenakan biaya apapun, Pendaftaran 100% GRATIS dan mudah untuk di lakukan. Anda hanya perlu menyediakan nama rekening, nomor rekening, email dan nomor HP atau WA anda. Silahkan kunjungkin situs kungfuQQ dengan klik link berikut ini kungfuqq.net. Jika anda merasakan bingung di saat melakukan pendaftaran di kungfuqq, anda tidak perlu khawatir. Sebab di kungfuqq memiliki Layanan Customer Service yang akan membantu anda dalam melakukan pendaftaran Akun tersebut. Customer Service di kungfuQQ selalu siap melayanin anda kapan saja. Karena Layanan ini selalu Aktif atau online 24 jam setiap hari nya. Serta untuk pelayanan yang akan diberikan untuk anda juga sangat ramah dan juga sudah profesional. Jadi jika anda memiliki pertanyaan yang tidak di menggerti seputar permainan, deposit atau withdraw. Anda bisa lagsung chat ke layanan Customer Service tersebut. Dan kungfuQQ juga memiliki Nomor WA yang bisa anda hubungin, jadi anda tidak perlu selalu datang ke livechat jika ingin menayakan sesuatu. Kemudian, jika anda sudah berhasil bergabung dengan kungfuQQ, anda jugak bisa mendapatkan bonus besar di saat anda melakukan deposit pertama kalinya. Tidak hanya memberikan deposit member baru saja, di kungfuQQ juga akan memberikan bonus setiap harinya untuk para membernya dan masih banyak bonus lainnya lagi. Penasaran dengan bonus tersebut, berikut ini : - Bonus Member Baru 20% - Bonus Deposit Harian 10% - Bonus Turnover 0.5% Setiap Hari Kamis - Bonus Referral 20% Seumur Hidup Itu semua bonus besar yang bisa anda dapatkan di Situs IDN POker KungfuQQ Deposit Via Pulsa Tanpa Potongan ini, Jadi lagsung saja daftarkan diri anda sekrang juga dan rasakan semua keuntungan anda bermain poker menggunakan pulsa tanpa potongan ini. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MNGSITE-445) Document "inlined collections" approach for plugin configuration
Andreas Sewe created MNGSITE-445: Summary: Document "inlined collections" approach for plugin configuration Key: MNGSITE-445 URL: https://issues.apache.org/jira/browse/MNGSITE-445 Project: Maven Project Web Site Issue Type: Improvement Environment: Maven website "Last Published: 2021-03-07" Reporter: Andreas Sewe I have searched in various places ([Guide To Configuring Plug-ins|https://maven.apache.org/guides/mini/guide-configuring-plugins.html], the [Your First Mojo tutorial|https://maven.apache.org/guides/plugin/guide-java-plugin-development.html#parameters], the [Mojo API documentation|https://maven.apache.org/developers/mojo-api-specification.html]) but couldn't find any mention of a feature introduced way back with Maven 3.0.3 and (AFAICT) only described in this blog post from 2011, [Configuring Plugin Goals in Maven 3|https://blog.sonatype.com/2011/03/configuring-plugin-goals-in-maven-3/]: Inlined collections. IMHO, this feature and also the other improvements mentioned in said blog post are currently missing from Maven's documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-enforcer] elharo opened a new pull request #94: fix assorted warnings and deprecations
elharo opened a new pull request #94: URL: https://github.com/apache/maven-enforcer/pull/94 @slachiewicz This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-enforcer] elharo merged pull request #81: simplify code
elharo merged pull request #81: URL: https://github.com/apache/maven-enforcer/pull/81 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-enforcer] elharo commented on pull request #81: simplify code
elharo commented on pull request #81: URL: https://github.com/apache/maven-enforcer/pull/81#issuecomment-796702572 Jenkins passed, waiting for github This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MENFORCER-381) classifier not included in output of failed RequireUpperBoundDeps test
[ https://issues.apache.org/jira/browse/MENFORCER-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17299523#comment-17299523 ] Elliotte Rusty Harold commented on MENFORCER-381: - Fix belongs in `RequireUpperBoundsDep`, possibly in `getFullArtifactName()` > classifier not included in output of failed RequireUpperBoundDeps test > -- > > Key: MENFORCER-381 > URL: https://issues.apache.org/jira/browse/MENFORCER-381 > Project: Maven Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Reporter: Elliotte Rusty Harold >Priority: Major > > This true positive confused m for a while: > > Failed while enforcing RequireUpperBoundDeps. The error(s) are [ > Require upper bound dependencies error for > com.google.cloud:google-cloud-core:1.94.3 paths to dependency are: > +-com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT > +-com.google.cloud:google-cloud-core:1.94.3 > and > +-com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT > +-com.google.cloud:google-cloud-core:1.94.4 > Notice that com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT seems to > depend on both com.google.cloud:google-cloud-core:1.94.3 and > com.google.cloud:google-cloud-core:1.94.4. WTF? That shouldn't happen. > > What's going on here is that these are two different artifacts, > com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT:jar and > com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT:jar:testlib > > However the classifier isn't printed in the failure message so this is far > from obvious. > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MENFORCER-381) classifier not included in output of failed RequireUpperBoundDeps test
[ https://issues.apache.org/jira/browse/MENFORCER-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold reassigned MENFORCER-381: --- Assignee: Elliotte Rusty Harold > classifier not included in output of failed RequireUpperBoundDeps test > -- > > Key: MENFORCER-381 > URL: https://issues.apache.org/jira/browse/MENFORCER-381 > Project: Maven Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > > This true positive confused m for a while: > > Failed while enforcing RequireUpperBoundDeps. The error(s) are [ > Require upper bound dependencies error for > com.google.cloud:google-cloud-core:1.94.3 paths to dependency are: > +-com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT > +-com.google.cloud:google-cloud-core:1.94.3 > and > +-com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT > +-com.google.cloud:google-cloud-core:1.94.4 > Notice that com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT seems to > depend on both com.google.cloud:google-cloud-core:1.94.3 and > com.google.cloud:google-cloud-core:1.94.4. WTF? That shouldn't happen. > > What's going on here is that these are two different artifacts, > com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT:jar and > com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT:jar:testlib > > However the classifier isn't printed in the failure message so this is far > from obvious. > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-enforcer] elharo opened a new pull request #93: remove unused field
elharo opened a new pull request #93: URL: https://github.com/apache/maven-enforcer/pull/93 @michael-o small code cleanup This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-enforcer] elharo commented on pull request #81: simplify code
elharo commented on pull request #81: URL: https://github.com/apache/maven-enforcer/pull/81#issuecomment-796685307 running through jenkins: https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/simple/ This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MENFORCER-381) classifier not included in output of failed RequireUpperBoundDeps test
[ https://issues.apache.org/jira/browse/MENFORCER-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MENFORCER-381: Component/s: Standard Rules > classifier not included in output of failed RequireUpperBoundDeps test > -- > > Key: MENFORCER-381 > URL: https://issues.apache.org/jira/browse/MENFORCER-381 > Project: Maven Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Reporter: Elliotte Rusty Harold >Priority: Major > > This true positive confused m for a while: > > Failed while enforcing RequireUpperBoundDeps. The error(s) are [ > Require upper bound dependencies error for > com.google.cloud:google-cloud-core:1.94.3 paths to dependency are: > +-com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT > +-com.google.cloud:google-cloud-core:1.94.3 > and > +-com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT > +-com.google.cloud:google-cloud-core:1.94.4 > Notice that com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT seems to > depend on both com.google.cloud:google-cloud-core:1.94.3 and > com.google.cloud:google-cloud-core:1.94.4. WTF? That shouldn't happen. > > What's going on here is that these are two different artifacts, > com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT:jar and > com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT:jar:testlib > > However the classifier isn't printed in the failure message so this is far > from obvious. > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MENFORCER-381) classifier not included in output of failed RequireUpperBoundDeps test
Elliotte Rusty Harold created MENFORCER-381: --- Summary: classifier not included in output of failed RequireUpperBoundDeps test Key: MENFORCER-381 URL: https://issues.apache.org/jira/browse/MENFORCER-381 Project: Maven Enforcer Plugin Issue Type: Bug Reporter: Elliotte Rusty Harold This true positive confused m for a while: Failed while enforcing RequireUpperBoundDeps. The error(s) are [ Require upper bound dependencies error for com.google.cloud:google-cloud-core:1.94.3 paths to dependency are: +-com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT +-com.google.cloud:google-cloud-core:1.94.3 and +-com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT +-com.google.cloud:google-cloud-core:1.94.4 Notice that com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT seems to depend on both com.google.cloud:google-cloud-core:1.94.3 and com.google.cloud:google-cloud-core:1.94.4. WTF? That shouldn't happen. What's going on here is that these are two different artifacts, com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT:jar and com.google.cloud:google-cloud-nio:0.122.11-SNAPSHOT:jar:testlib However the classifier isn't printed in the failure message so this is far from obvious. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-7113) config maven to mark “running test” as ERROR when some tests are skipped
[
https://issues.apache.org/jira/browse/MNG-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17299475#comment-17299475
]
Michael Osipov commented on MNG-7113:
-
Have you looked that Surefire Plugin offers? Most of them are already available.
> config maven to mark “running test” as ERROR when some tests are skipped
>
>
> Key: MNG-7113
> URL: https://issues.apache.org/jira/browse/MNG-7113
> Project: Maven
> Issue Type: New Feature
>Reporter: Jan
>Priority: Minor
>
> As a tester/developer I would like to have a flag in maven to set final
> verdict of running tests to ERROR when some tests has been skipped.
> Flag name proposal:
> markBuildAsErrorWhenAnyTestSkipped
> Example using:
> mvn test -DmarkBuildAsErrorWhenAnyTestSkipped=false
>
> {noformat}
> [WARNING] Tests run: 1423, Failures: 0, Errors: 0, **Skipped: 3,** Time
> elapsed: 149.449 s - in TestSuite
> [INFO]
> [INFO] Results:
> [INFO]
> [WARNING] Tests run: 1423, Failures: 0, Errors: 0, Skipped: 3
> [INFO]
> [INFO]
>
> [INFO] **BUILD SUCCESS**
> [INFO]
>
> [INFO] Total time: 02:55 min
> [INFO] Finished at: 2021-03-10T13:12:35+01:00
> [INFO]
> {noformat}
> mvn test -DmarkBuildAsErrorWhenAnyTestSkipped=true
>
> {noformat}
> [WARNING] Tests run: 1423, Failures: 0, Errors: 0, **Skipped: 3,** Time
> elapsed: 149.449 s - in TestSuite
> [INFO]
> [INFO] Results:
> [INFO]
> [WARNING] Tests run: 1423, Failures: 0, Errors: 0, Skipped: 3
> [INFO]
> [INFO]
>
> [INFO] **BUILD ERROR**
> [INFO]
>
> [INFO] Total time: 02:55 min
> [INFO] Finished at: 2021-03-10T13:12:35+01:00
> [INFO]
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MNG-7113) config maven to mark “running test” as ERROR when some tests are skipped
Jan created MNG-7113:
Summary: config maven to mark “running test” as ERROR when some
tests are skipped
Key: MNG-7113
URL: https://issues.apache.org/jira/browse/MNG-7113
Project: Maven
Issue Type: New Feature
Reporter: Jan
As a tester/developer I would like to have a flag in maven to set final verdict
of running tests to ERROR when some tests has been skipped.
Flag name proposal:
markBuildAsErrorWhenAnyTestSkipped
Example using:
mvn test -DmarkBuildAsErrorWhenAnyTestSkipped=false
{noformat}
[WARNING] Tests run: 1423, Failures: 0, Errors: 0, **Skipped: 3,** Time
elapsed: 149.449 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[WARNING] Tests run: 1423, Failures: 0, Errors: 0, Skipped: 3
[INFO]
[INFO]
[INFO] **BUILD SUCCESS**
[INFO]
[INFO] Total time: 02:55 min
[INFO] Finished at: 2021-03-10T13:12:35+01:00
[INFO]
{noformat}
mvn test -DmarkBuildAsErrorWhenAnyTestSkipped=true
{noformat}
[WARNING] Tests run: 1423, Failures: 0, Errors: 0, **Skipped: 3,** Time
elapsed: 149.449 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[WARNING] Tests run: 1423, Failures: 0, Errors: 0, Skipped: 3
[INFO]
[INFO]
[INFO] **BUILD ERROR**
[INFO]
[INFO] Total time: 02:55 min
[INFO] Finished at: 2021-03-10T13:12:35+01:00
[INFO]
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-surefire] martinmo commented on pull request #341: [SUREFIRE-1894] Add missing "version" attribute to report XSD
martinmo commented on pull request #341: URL: https://github.com/apache/maven-surefire/pull/341#issuecomment-796577899 Hi, thanks for looking at this! Can you please elaborate why this is not enough? The new XML file is automatically used in `SurefireSchemaValidationTest`, which picks up all `TEST-*.xml` files in the test resources. For example, if I revert the fix to the schema file, the test fails and thus reproduces the issue: ``` [ERROR] Tests run: 13, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.19 s <<< FAILURE! - in org.apache.maven.plugins.surefire.report.JUnit4SuiteTest [ERROR] org.apache.maven.plugins.surefire.report.SurefireSchemaValidationTest.testValidate_XMLs_against_schema Time elapsed: 0.221 s <<< ERROR! java.lang.AssertionError: surefire-1894/TEST-surefire.MyTest.xml has violations: - ERROR at row:2 col:104 cvc-complex-type.3.2.2: Attribute 'version' is not allowed to appear in element 'testsuite'. at org.junit.Assert.fail(Assert.java:89) at org.junit.Assert.assertTrue(Assert.java:42) at org.apache.maven.plugins.surefire.report.SurefireSchemaValidationTest.testValidate_XMLs_against_schema(SurefireSchemaValidationTest.java:83) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at junit.framework.TestCase.runTest(TestCase.java:177) at junit.framework.TestCase.runBare(TestCase.java:142) at junit.framework.TestResult$1.protect(TestResult.java:122) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.framework.TestResult.run(TestResult.java:125) at junit.framework.TestCase.run(TestCase.java:130) at junit.framework.TestSuite.runTest(TestSuite.java:241) at junit.framework.TestSuite.run(TestSuite.java:236) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90) at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:50) at junit.framework.TestSuite.runTest(TestSuite.java:241) at junit.framework.TestSuite.run(TestSuite.java:236) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.maven.shadefire.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:99) at org.apache.maven.shadefire.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:141) at org.apache.maven.shadefire.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:114) at org.apache.maven.shadefire.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377) at org.apache.maven.shadefire.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138) at org.apache.maven.shadefire.surefire.booter.ForkedBooter.run(ForkedBooter.java:465) at org.apache.maven.shadefire.surefire.booter.ForkedBooter.main(ForkedBooter.java:451) ``` Or do you want to test something else? I've looked at `Surefire597Test`, but it tests the generation of an HTML report from the XML report and this seems unrelated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] rmannibucau commented on a change in pull request #340: [SUREFIRE-1892] ensure systemPropertyVariables values are stringified
rmannibucau commented on a change in pull request #340:
URL: https://github.com/apache/maven-surefire/pull/340#discussion_r592172934
##
File path:
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
##
@@ -3623,9 +3623,20 @@ public void setSystemProperties( Properties
systemProperties )
}
@SuppressWarnings( "UnusedDeclaration" )
-public void setSystemPropertyVariables( Map
systemPropertyVariables )
+public void setSystemPropertyVariables( Map
systemPropertyVariables )
{
-this.systemPropertyVariables = systemPropertyVariables;
+if (systemPropertyVariables != null)
+{
+this.systemPropertyVariables = new HashMap<>();
+for ( final Map.Entry entry :
systemPropertyVariables.entrySet() )
+{
+this.systemPropertyVariables.put( entry.getKey(),
String.valueOf( entry.getValue() ) );
Review comment:
Understood but it does not fix the issue that the mojo exposed view is
wrong for some time in between until the utility is public which is worse than
these 2 lines IMHO so not a bad compromise probably.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-surefire] Tibor17 commented on a change in pull request #340: [SUREFIRE-1892] ensure systemPropertyVariables values are stringified
Tibor17 commented on a change in pull request #340:
URL: https://github.com/apache/maven-surefire/pull/340#discussion_r592161135
##
File path:
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
##
@@ -3623,9 +3623,20 @@ public void setSystemProperties( Properties
systemProperties )
}
@SuppressWarnings( "UnusedDeclaration" )
-public void setSystemPropertyVariables( Map
systemPropertyVariables )
+public void setSystemPropertyVariables( Map
systemPropertyVariables )
{
-this.systemPropertyVariables = systemPropertyVariables;
+if (systemPropertyVariables != null)
+{
+this.systemPropertyVariables = new HashMap<>();
+for ( final Map.Entry entry :
systemPropertyVariables.entrySet() )
+{
+this.systemPropertyVariables.put( entry.getKey(),
String.valueOf( entry.getValue() ) );
Review comment:
Both methods will be private and they have a commpon purpose - moving
properties from one Map to second Map. Of course j8 may turn loops to streams
but that's a big hammer for this little refactoring.
I would be glad when Maven aligns all default Maven plugins to j8 after
Maven 4.0, and then all the stack would be on the same j8. IMO j9 would be even
a bigger benefit for the Maven but not for users yet ;-).
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
