[GitHub] [maven-surefire] rmannibucau commented on pull request #398: [SUREFIRE-1962] Unit test for ProviderInfo#isApplicable
rmannibucau commented on pull request #398: URL: https://github.com/apache/maven-surefire/pull/398#issuecomment-997662609 Not obvious to me what the goal is and if it is only isApplicable maybe it needs a true/false case for all providers when possible? But likely misses the most important part: not mock but use mojo harnessing instead -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MWRAPPER-42) maven-wrapper fails to self-update maven-wrapper.jar
[ https://issues.apache.org/jira/browse/MWRAPPER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MWRAPPER-42: -- Fix Version/s: 3.1.1 > maven-wrapper fails to self-update maven-wrapper.jar > > > Key: MWRAPPER-42 > URL: https://issues.apache.org/jira/browse/MWRAPPER-42 > Project: Maven Wrapper > Issue Type: Bug > Components: Maven Wrapper Scripts >Affects Versions: 3.1.0 >Reporter: Jeremy Norris >Priority: Major > Fix For: 3.1.1 > > > In cases where users do not check-in the maven-wrapper.jar into their > repositories, after executing `mvn wrapper:wrapper -Dtype=script` to update, > the newly updated `mvnw` script will continue to use an older version of > `.mvn/wrapper/maven-wrapper.jar` that was previously downloaded. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MWRAPPER-42) maven-wrapper fails to self-update maven-wrapper.jar
[ https://issues.apache.org/jira/browse/MWRAPPER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462411#comment-17462411 ] Herve Boutemy commented on MWRAPPER-42: --- nice finding, nice report I suppose that we can compare date of mvnw[.com] with maven-wrapper.jar: if script is strictly newer, maven-wrapper.jar has to be deleted, to be downloaded again coding that in *nix is easy (the hardest part is making sure it is portable) I don't know about .cmd: any hint better what I found in SO than https://stackoverflow.com/questions/1687014/how-do-i-compare-timestamps-of-files-in-a-batch-script ? > maven-wrapper fails to self-update maven-wrapper.jar > > > Key: MWRAPPER-42 > URL: https://issues.apache.org/jira/browse/MWRAPPER-42 > Project: Maven Wrapper > Issue Type: Bug > Components: Maven Wrapper Scripts >Affects Versions: 3.1.0 >Reporter: Jeremy Norris >Priority: Major > > In cases where users do not check-in the maven-wrapper.jar into their > repositories, after executing `mvn wrapper:wrapper -Dtype=script` to update, > the newly updated `mvnw` script will continue to use an older version of > `.mvn/wrapper/maven-wrapper.jar` that was previously downloaded. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MWRAPPER-16) update mvnw scripts to launch target Maven mvn scripts, to enforce consistency
[ https://issues.apache.org/jira/browse/MWRAPPER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MWRAPPER-16: -- Fix Version/s: (was: 3.1.1) 3.2.0 > update mvnw scripts to launch target Maven mvn scripts, to enforce consistency > -- > > Key: MWRAPPER-16 > URL: https://issues.apache.org/jira/browse/MWRAPPER-16 > Project: Maven Wrapper > Issue Type: Improvement > Components: Maven Wrapper Scripts >Affects Versions: 0.5.6, 3.1.0 >Reporter: Herve Boutemy >Priority: Major > Fix For: 3.2.0 > > > currently, wrapper scripts copied to user project mimic Maven scripts (search > .mvn, and so on), then launch wrapper.jar: at the end, wrapper.jar calls > installed Maven distribution Classworlds bootstrap to run Maven Java code > this may cause a discrepency between features supported by mvnw script vs > what would have been done by installed Maven mvn scripts > for example, when/if [https://github.com/apache/maven/pull/602] is done > To enforce consistency, mvnw should launch installed Maven mvn script at the > end, and let it do its full work as if it had been launched -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-checkstyle-plugin] dependabot[bot] opened a new pull request #59: Bump extra-enforcer-rules from 1.4 to 1.5.1
dependabot[bot] opened a new pull request #59: URL: https://github.com/apache/maven-checkstyle-plugin/pull/59 Bumps [extra-enforcer-rules](https://github.com/mojohaus/extra-enforcer-rules) from 1.4 to 1.5.1. Release notes Sourced from https://github.com/mojohaus/extra-enforcer-rules/releases;>extra-enforcer-rules's releases. 1.5.1 No changes Last release has issues with oss.sonatype.org so trying again 1.5.0 Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/enforce-bytecode-version-multirelease (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/154;>#154) https://github.com/dependabot;>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-fail-when-not-identical (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/155;>#155) https://github.com/dependabot;>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-ignore-when-identical (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/156;>#156) https://github.com/dependabot;>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-jdk9 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/157;>#157) https://github.com/dependabot;>@dependabot Bump mockito-core from 3.12.4 to 4.1.0 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/151;>#151) https://github.com/dependabot;>@dependabot Bump actions/setup-java from 2.3.1 to 2.4.0 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/153;>#153) https://github.com/dependabot;>@dependabot Bump mojo-parent from 63 to 65 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/152;>#152) https://github.com/dependabot;>@dependabot Bump actions/setup-java from 2.3.0 to 2.3.1 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/145;>#145) https://github.com/dependabot;>@dependabot Bug Fixes Bytecode version of multirelease metadata should be lower or equal to specified version (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/158;>#158) https://github.com/Vlatombe;>@Vlatombe Commits https://github.com/mojohaus/extra-enforcer-rules/commit/da069393305d91ff1bf24fecd1725d145cf3a121;>da06939 [maven-release-plugin] prepare release extra-enforcer-rules-1.5.1 https://github.com/mojohaus/extra-enforcer-rules/commit/24c1b61b670f4ad6495762e6f86377ef783c733a;>24c1b61 [maven-release-plugin] prepare for next development iteration https://github.com/mojohaus/extra-enforcer-rules/commit/4e4e2db3df60fc8af22c877e38f27b391c6be1f8;>4e4e2db [maven-release-plugin] prepare release extra-enforcer-rules-1.5 https://github.com/mojohaus/extra-enforcer-rules/commit/5553dfc45a7cc4090b270b9bcd5d429804f8e7f4;>5553dfc fix IT test https://github.com/mojohaus/extra-enforcer-rules/commit/ecff4d7c5eae7d9e9e1f61a7cb9f43ffb06ea17c;>ecff4d7 Bump log4j-api in /src/it/enforce-bytecode-version-multirelease https://github.com/mojohaus/extra-enforcer-rules/commit/4db8e82362ebf79fd2ca373d38511c8ad0cf1cd1;>4db8e82 Merge pull request https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/155;>#155 from mojohaus/dependabot/maven/src/it/banduplicate-cl... https://github.com/mojohaus/extra-enforcer-rules/commit/b21d419d09def4665e0cc1209967e4d986ebfb13;>b21d419 Merge pull request https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/156;>#156 from mojohaus/dependabot/maven/src/it/banduplicate-cl... https://github.com/mojohaus/extra-enforcer-rules/commit/9aded1a52b48a1ca3b720e41a7a7251b2784f3ef;>9aded1a Merge pull request https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/157;>#157 from mojohaus/dependabot/maven/src/it/banduplicate-cl... https://github.com/mojohaus/extra-enforcer-rules/commit/90ac027afa09353989f9ba1173f49fe2dcd41404;>90ac027 Bytecode version of multirelease metadata should be lower or equal to specifi... https://github.com/mojohaus/extra-enforcer-rules/commit/0cdcfacfbfaa29c5c22ad5bfb669983748f1d36d;>0cdcfac Bump log4j-api in /src/it/banduplicate-classes-jdk9 Additional commits viewable in https://github.com/mojohaus/extra-enforcer-rules/compare/extra-enforcer-rules-1.4...extra-enforcer-rules-1.5.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[GitHub] [maven-resources-plugin] dependabot[bot] opened a new pull request #14: Bump plexus-utils from 3.3.0 to 3.4.1
dependabot[bot] opened a new pull request #14: URL: https://github.com/apache/maven-resources-plugin/pull/14 Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from 3.3.0 to 3.4.1. Release notes Sourced from https://github.com/codehaus-plexus/plexus-utils/releases;>plexus-utils's releases. 3.4.1 Bug Fixes Fixes https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/163;>#163: Regression: encoding error when parsing a ISO-8859-1 xml (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/164;>#164) https://github.com/belingueres;>@belingueres Dependency updates Bump actions/setup-java from 2.2.0 to 2.3.0 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/168;>#168) https://github.com/dependabot;>@dependabot Bump jmh-generator-annprocess from 1.32 to 1.33 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/166;>#166) https://github.com/dependabot;>@dependabot Bump jmh-core from 1.32 to 1.33 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/165;>#165) https://github.com/dependabot;>@dependabot Bump actions/setup-java from 2.1.0 to 2.2.0 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/167;>#167) https://github.com/dependabot;>@dependabot Bump junit from 4.13.1 to 4.13.2 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/162;>#162) https://github.com/dependabot;>@dependabot Bump actions/setup-java from 1 to 2.1.0 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/157;>#157) https://github.com/dependabot;>@dependabot Bump jmh-generator-annprocess from 1.29 to 1.32 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/159;>#159) https://github.com/dependabot;>@dependabot Bump jmh-core from 1.29 to 1.32 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/160;>#160) https://github.com/dependabot;>@dependabot Bump actions/cache from 2.1.5 to 2.1.6 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/161;>#161) https://github.com/dependabot;>@dependabot Bump actions/checkout from 2 to 2.3.4 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/154;>#154) https://github.com/dependabot;>@dependabot 3.4.0 Enforcing JDK 11 on release (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/148;>#148) https://github.com/mkarg;>@mkarg Using JDK 16 GA instead of JDK 16 EA (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/147;>#147) https://github.com/mkarg;>@mkarg Fixed infinite loop in MXParser and reactivate tests in MXParserTest (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/119;>#119,https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/118;>#118) https://github.com/belingueres;>@belingueres Added support for PPC64LE (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/97;>#97) https://github.com/ezeeyahoo;>@ezeeyahoo Avoid build issues with symlink (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/90;>#90) https://github.com/olamy;>@olamy New feature FileUtils.linkFile(source, destination) (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/82;>#82) https://github.com/mkarg;>@mkarg Fix Javadoc build with Java 11 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/88;>#88) https://github.com/olamy;>@olamy Support combine.keys (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/76;>#76) https://github.com/rfscholte;>@rfscholte Support combine.self=remove (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/75;>#75,https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/74;>#74) https://github.com/belingueres;>@belingueres Input location (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/62;>#62,https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/61;>#61) https://github.com/hboutemy;>@hboutemy UT improvement : Check that symlinks resources are preserved during git clone (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/56;>#56) https://github.com/rfscholte;>@rfscholte Junit4 annotations (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/55;>#55) https://github.com/rfscholte;>@rfscholte Test failure in CommandlineTest#testExecuteBinaryOnPath with Maven 3.5.4 or later (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/50;>#50) https://github.com/belingueres;>@belingueres PrettyPrintXMLWriter fails with a java.util.NoSuchElementException (Java 1.7 only)
[GitHub] [maven-invoker] dependabot[bot] opened a new pull request #31: Bump extra-enforcer-rules from 1.4 to 1.5.1
dependabot[bot] opened a new pull request #31: URL: https://github.com/apache/maven-invoker/pull/31 Bumps [extra-enforcer-rules](https://github.com/mojohaus/extra-enforcer-rules) from 1.4 to 1.5.1. Release notes Sourced from https://github.com/mojohaus/extra-enforcer-rules/releases;>extra-enforcer-rules's releases. 1.5.1 No changes Last release has issues with oss.sonatype.org so trying again 1.5.0 Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/enforce-bytecode-version-multirelease (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/154;>#154) https://github.com/dependabot;>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-fail-when-not-identical (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/155;>#155) https://github.com/dependabot;>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-ignore-when-identical (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/156;>#156) https://github.com/dependabot;>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-jdk9 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/157;>#157) https://github.com/dependabot;>@dependabot Bump mockito-core from 3.12.4 to 4.1.0 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/151;>#151) https://github.com/dependabot;>@dependabot Bump actions/setup-java from 2.3.1 to 2.4.0 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/153;>#153) https://github.com/dependabot;>@dependabot Bump mojo-parent from 63 to 65 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/152;>#152) https://github.com/dependabot;>@dependabot Bump actions/setup-java from 2.3.0 to 2.3.1 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/145;>#145) https://github.com/dependabot;>@dependabot Bug Fixes Bytecode version of multirelease metadata should be lower or equal to specified version (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/158;>#158) https://github.com/Vlatombe;>@Vlatombe Commits https://github.com/mojohaus/extra-enforcer-rules/commit/da069393305d91ff1bf24fecd1725d145cf3a121;>da06939 [maven-release-plugin] prepare release extra-enforcer-rules-1.5.1 https://github.com/mojohaus/extra-enforcer-rules/commit/24c1b61b670f4ad6495762e6f86377ef783c733a;>24c1b61 [maven-release-plugin] prepare for next development iteration https://github.com/mojohaus/extra-enforcer-rules/commit/4e4e2db3df60fc8af22c877e38f27b391c6be1f8;>4e4e2db [maven-release-plugin] prepare release extra-enforcer-rules-1.5 https://github.com/mojohaus/extra-enforcer-rules/commit/5553dfc45a7cc4090b270b9bcd5d429804f8e7f4;>5553dfc fix IT test https://github.com/mojohaus/extra-enforcer-rules/commit/ecff4d7c5eae7d9e9e1f61a7cb9f43ffb06ea17c;>ecff4d7 Bump log4j-api in /src/it/enforce-bytecode-version-multirelease https://github.com/mojohaus/extra-enforcer-rules/commit/4db8e82362ebf79fd2ca373d38511c8ad0cf1cd1;>4db8e82 Merge pull request https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/155;>#155 from mojohaus/dependabot/maven/src/it/banduplicate-cl... https://github.com/mojohaus/extra-enforcer-rules/commit/b21d419d09def4665e0cc1209967e4d986ebfb13;>b21d419 Merge pull request https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/156;>#156 from mojohaus/dependabot/maven/src/it/banduplicate-cl... https://github.com/mojohaus/extra-enforcer-rules/commit/9aded1a52b48a1ca3b720e41a7a7251b2784f3ef;>9aded1a Merge pull request https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/157;>#157 from mojohaus/dependabot/maven/src/it/banduplicate-cl... https://github.com/mojohaus/extra-enforcer-rules/commit/90ac027afa09353989f9ba1173f49fe2dcd41404;>90ac027 Bytecode version of multirelease metadata should be lower or equal to specifi... https://github.com/mojohaus/extra-enforcer-rules/commit/0cdcfacfbfaa29c5c22ad5bfb669983748f1d36d;>0cdcfac Bump log4j-api in /src/it/banduplicate-classes-jdk9 Additional commits viewable in https://github.com/mojohaus/extra-enforcer-rules/compare/extra-enforcer-rules-1.4...extra-enforcer-rules-1.5.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: #
[GitHub] [maven-indexer] dependabot[bot] opened a new pull request #148: Bump version.spring from 5.3.13 to 5.3.14
dependabot[bot] opened a new pull request #148: URL: https://github.com/apache/maven-indexer/pull/148 Bumps `version.spring` from 5.3.13 to 5.3.14. Updates `spring-beans` from 5.3.13 to 5.3.14 Release notes Sourced from https://github.com/spring-projects/spring-framework/releases;>spring-beans's releases. v5.3.14 :star: New Features Add default methods to CachingConfigurer https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27811;>#27811 Provide a variant of ListableBeanFactory.findAnnotationOnBean(String, Class) that does not initialize factory beans https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27796;>#27796 Convert single null argument to Optional.empty() in SpEL varargs expression https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27795;>#27795 Declare serialVersionUID on DefaultAopProxyFactory https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27784;>#27784 The ReactorClientHttpConnector must apply mapper before tcpConfiguration() https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27749;>#27749 Add getter for RequestMappingInfo builder config https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/27723;>#27723 Give warning when using capturing patterns with the AntPathMatcher https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27688;>#27688 Support for customization of 404 response when RouterFunctionWebHandler finds no routes https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/25358;>#25358 ModelAndView.status does not work with RedirectView https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/25092;>#25092 ThreadPoolExecutorFactoryBean add ability to prestart threads https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/1246;>#1246 Support empty attributes in TagWriter https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/910;>#910 :lady_beetle: Bug Fixes AsyncConfigurer implementations are loaded too early https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27808;>#27808 Possible NPE in Spring MVC LogFormatUtils https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27782;>#27782 Extending CachingConfigurerSupport results in at least one log message about not being eligible for full post-processing https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27751;>#27751 WebFlux ServerResponse does not overwrite already present response headers https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27741;>#27741 Passing single null value in varargs SpEL expression results in NullPointerException https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27719;>#27719 UriUtils::extractFileExtension does not properly handle empty file names https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27639;>#27639 References of CountingBeforeAdvice target its previous location https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/22246;>#22246 ProxyFactoryBean getObject called before setInterceptorNames, silently creating an invalid proxy [SPR-7582] https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/12238;>#12238 :notebook_with_decorative_cover: Documentation Remove references to AsyncConfigurerSupport as AsyncConfigurer should be used instead https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27812;>#27812 Fix javadoc reference to ThrowsAdvice https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/27804;>#27804 Suggested WebSocket config causes circular bean reference https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27746;>#27746 Document the difference in generics resolution between @Autowired and beanFactory.getBeanProvider https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27727;>#27727 Clarify that interface-level cache annotations work for target-class proxies as well https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/27726;>#27726 SchedulerFactoryBean no longer sets the job store's DataSource when the job store class has been customized https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/27709;>#27709 Fix typo https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/27699;>#27699 Fix incorrect example of error handling in WebClient Javadoc https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/27645;>#27645 Missing reference documentation for WebSocketScope
[GitHub] [maven-archetype] dependabot[bot] opened a new pull request #96: Bump extra-enforcer-rules from 1.3 to 1.5.1
dependabot[bot] opened a new pull request #96: URL: https://github.com/apache/maven-archetype/pull/96 Bumps [extra-enforcer-rules](https://github.com/mojohaus/extra-enforcer-rules) from 1.3 to 1.5.1. Release notes Sourced from https://github.com/mojohaus/extra-enforcer-rules/releases;>extra-enforcer-rules's releases. 1.5.1 No changes Last release has issues with oss.sonatype.org so trying again 1.5.0 Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/enforce-bytecode-version-multirelease (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/154;>#154) https://github.com/dependabot;>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-fail-when-not-identical (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/155;>#155) https://github.com/dependabot;>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-ignore-when-identical (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/156;>#156) https://github.com/dependabot;>@dependabot Bump log4j-api from 2.15.0 to 2.16.0 in /src/it/banduplicate-classes-jdk9 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/157;>#157) https://github.com/dependabot;>@dependabot Bump mockito-core from 3.12.4 to 4.1.0 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/151;>#151) https://github.com/dependabot;>@dependabot Bump actions/setup-java from 2.3.1 to 2.4.0 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/153;>#153) https://github.com/dependabot;>@dependabot Bump mojo-parent from 63 to 65 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/152;>#152) https://github.com/dependabot;>@dependabot Bump actions/setup-java from 2.3.0 to 2.3.1 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/145;>#145) https://github.com/dependabot;>@dependabot Bug Fixes Bytecode version of multirelease metadata should be lower or equal to specified version (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/158;>#158) https://github.com/Vlatombe;>@Vlatombe 1.4 Bump mockito-core from 3.11.2 to 3.12.4 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/139;>#139) https://github.com/dependabot;>@dependabot Bump mojo-parent from 60 to 63 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/142;>#142) https://github.com/dependabot;>@dependabot Master update dependencies (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/136;>#136) https://github.com/slachiewicz;>@slachiewicz Refactor AbstractRequireRoles.getRolesFromString (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/133;>#133) https://github.com/pzygielo;>@pzygielo Require Java 8 (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/134;>#134) https://github.com/slachiewicz;>@slachiewicz [jdk17] Apply jdk 17 to allowed jdk versions (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/129;>#129) https://github.com/hazendaz;>@hazendaz New features and improvements add dependabot and release drafter configurations (https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/138;>#138) https://github.com/olamy;>@olamy Commits https://github.com/mojohaus/extra-enforcer-rules/commit/da069393305d91ff1bf24fecd1725d145cf3a121;>da06939 [maven-release-plugin] prepare release extra-enforcer-rules-1.5.1 https://github.com/mojohaus/extra-enforcer-rules/commit/24c1b61b670f4ad6495762e6f86377ef783c733a;>24c1b61 [maven-release-plugin] prepare for next development iteration https://github.com/mojohaus/extra-enforcer-rules/commit/4e4e2db3df60fc8af22c877e38f27b391c6be1f8;>4e4e2db [maven-release-plugin] prepare release extra-enforcer-rules-1.5 https://github.com/mojohaus/extra-enforcer-rules/commit/5553dfc45a7cc4090b270b9bcd5d429804f8e7f4;>5553dfc fix IT test https://github.com/mojohaus/extra-enforcer-rules/commit/ecff4d7c5eae7d9e9e1f61a7cb9f43ffb06ea17c;>ecff4d7 Bump log4j-api in /src/it/enforce-bytecode-version-multirelease https://github.com/mojohaus/extra-enforcer-rules/commit/4db8e82362ebf79fd2ca373d38511c8ad0cf1cd1;>4db8e82 Merge pull request https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/155;>#155 from mojohaus/dependabot/maven/src/it/banduplicate-cl... https://github.com/mojohaus/extra-enforcer-rules/commit/b21d419d09def4665e0cc1209967e4d986ebfb13;>b21d419 Merge pull request https://github-redirect.dependabot.com/mojohaus/extra-enforcer-rules/issues/156;>#156 from mojohaus/dependabot/maven/src/it/banduplicate-cl...
[GitHub] [maven-surefire] dependabot[bot] opened a new pull request #411: Bump animal-sniffer-maven-plugin from 1.17 to 1.20
dependabot[bot] opened a new pull request #411: URL: https://github.com/apache/maven-surefire/pull/411 Bumps [animal-sniffer-maven-plugin](https://github.com/mojohaus/animal-sniffer) from 1.17 to 1.20. Release notes Sourced from https://github.com/mojohaus/animal-sniffer/releases;>animal-sniffer-maven-plugin's releases. 1.20 This release is now Java 8 minimum New features and improvements add some java8 sugar syntax usage (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/148;>#148) https://github.com/olamy;>@olamy mojo paremt 61 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/147;>#147) https://github.com/olamy;>@olamy Bug Fixes checking test code is disabled by default (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/143;>#143) https://github.com/jtnord;>@jtnord Typo fix in error message (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/137;>#137) https://github.com/gunnarmorling;>@gunnarmorling Fix NestMember requires ASM7 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/135;>#135) https://github.com/bradcupit;>@bradcupit Add LICENSE file (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/88;>#88) https://github.com/steven-sheehy;>@steven-sheehy Fix https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/5;>#5: fix false negatives when checking test classes (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/81;>#81) https://github.com/famod;>@famod Dependency updates Bump maven-common-artifact-filters from 3.1.0 to 3.1.1 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/140;>#140) https://github.com/dependabot;>@dependabot Bump maven-checkstyle-plugin from 3.1.1 to 3.1.2 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/141;>#141) https://github.com/dependabot;>@dependabot Bump ant from 1.9.15 to 1.10.9 in /animal-sniffer-ant-tasks (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/144;>#144) https://github.com/dependabot;>@dependabot Bump asm from 9.0 to 9.1 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/146;>#146) https://github.com/dependabot;>@dependabot Bump actions/cache from v2.1.3 to v2.1.4 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/145;>#145) https://github.com/dependabot;>@dependabot Bump release-drafter/release-drafter from v5.12.1 to v5.13.0 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/138;>#138) https://github.com/dependabot;>@dependabot upgrade mojo-parent 60 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/136;>#136) https://github.com/olamy;>@olamy Bump actions/cache from v2.1.2 to v2.1.3 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/133;>#133) https://github.com/dependabot;>@dependabot Bump ant from 1.9.4 to 1.9.15 in /animal-sniffer-ant-tasks (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/109;>#109) https://github.com/dependabot;>@dependabot Bump ant from 1.9.4 to 1.9.15 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/113;>#113) https://github.com/dependabot;>@dependabot Bump maven-surefire-plugin from 2.22.0 to 2.22.2 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/126;>#126) https://github.com/dependabot;>@dependabot Bump maven-compiler-plugin from 3.8.0 to 3.8.1 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/127;>#127) https://github.com/dependabot;>@dependabot Bump maven-project-info-reports-plugin from 3.0.0 to 3.1.1 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/128;>#128) https://github.com/dependabot;>@dependabot Bump maven-site-plugin from 3.9.0 to 3.9.1 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/129;>#129) https://github.com/dependabot;>@dependabot Bump junit from 3.8.1 to 4.13.1 in /animal-sniffer-maven-plugin/src/it/version-resolution (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/121;>#121) https://github.com/dependabot;>@dependabot Bump plexus-container-default from 1.0-alpha-9 to 2.1.0 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/94;>#94) https://github.com/dependabot;>@dependabot Bump junit from 4.13 to 4.13.1 in /animal-sniffer-enforcer-rule (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/116;>#116) https://github.com/dependabot;>@dependabot Bump plexus-utils from 1.5.6 to 3.3.0 (https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/117;>#117) https://github.com/dependabot;>@dependabot Bump enforcer-api from 1.0 to 1.4.1
[GitHub] [maven-archetype] dependabot[bot] opened a new pull request #95: Bump xmlunit-matchers from 2.6.4 to 2.8.4
dependabot[bot] opened a new pull request #95: URL: https://github.com/apache/maven-archetype/pull/95 Bumps [xmlunit-matchers](https://github.com/xmlunit/xmlunit) from 2.6.4 to 2.8.4. Release notes Sourced from https://github.com/xmlunit/xmlunit/releases;>xmlunit-matchers's releases. XMLUnit for Java 2.8.4 improves performance when comparing documents with many sibling elements. Changelog: improved comparison performance for documents with many siblings based on a suggestion by https://github.com/gerpres;>@gerpres made in https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/236;>#236 XMLUnit for Java 2.8.3 added a new fullDescription method to Diff that provides a string-representation of all differences - not just the first one like toString does. PR https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/235;>#235 fixing https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/232;>#232 by https://github.com/Boiarshinov;>@Boiarshinov made sure AssertJ's methods to override the assertion message like withFailMessage are honored. https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/225;>#225 adjusted unit tests so they pass when AssertJ 3.19.0 is used. PR https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/212;>#212 by https://github.com/mmathesius;>mmathesius XMLUnit for Java 2.8.2 This release fixes a bug in the new AssertJ 3.x module. CompareAssert inside the AssertJ3 module swapped the expected and actual parameters when creating the assertion error. https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/210;>#210 by https://github.com/f-lopes;>@f-lopes XMLUnit for Java 2.8.1 The only real change when compared to XMLUnit for Java 2.8.0 is the introduction of a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later in order to address a problem with running AssertJ tests in an OSGi environment. The original xmlunit-assertj module will still be supported. The full changelog of XMLUnit for Java 2.8.1 added a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later. This module no longer uses AssertJ internal classes that are not exported to OSGi environments and thus fixes issue https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/203;>#203. The module (like AssertJ 3.x itself) requires Java 8 at runtime and is similar to xmlunit-assertj but is no drop-in replacement. It uses a different Java package from xmlunit-assertj and CompareAssert will no longer throw a JUnit 4.x ComparisonException but an opentest4j AssertionFailedError instead. The existing xmlunit-assertj module will still be supported in future releases but expect AssertJ 3.x specific changes to only get applied to xmlunit-assertj3. Many thanks to https://github.com/Zegveld;>@Zegveld, https://github.com/scordio;>@scordio and https://github.com/joel-costigliola;>@joel-costigliola. XMLUnit for Java 2.8.0 This release now requires Java 7 for all modules and updates some dependencies - the changed JAXB dependency is a breaking change. It also fixes a few bugs. Details of changes: ... (truncated) Changelog Sourced from https://github.com/xmlunit/xmlunit/blob/main/RELEASE_NOTES.md;>xmlunit-matchers's changelog. XMLUnit for Java 2.8.4 - /Released 2021-12-16/ improved comparison performance for documents with many siblings based on a suggestion by https://github.com/gerpres;>@gerpres made in https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/236;>#236 XMLUnit for Java 2.8.3 - /Released 2021-10-17/ added a new fullDescription method to Diff that provides a string-representation of all differences - not just the first one like toString does. PR https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/235;>#235 fixing https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/232;>#232 by https://github.com/Boiarshinov;>@Boiarshinov made sure AssertJ's methods to override the assertion message like withFailMessage are honored. https://github-redirect.dependabot.com/xmlunit/xmlunit/issues/225;>#225 adjusted unit tests so they pass when AssertJ 3.19.0 is used. PR https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/212;>#212 by https://github.com/mmathesius;>mmathesius XMLUnit for Java 2.8.2 - /Released 2020-12-21/ CompareAssert inside the AssertJ3 module swapped the expected and actual parameters when creating the assertion error. https://github-redirect.dependabot.com/xmlunit/xmlunit/pull/210;>#210 by https://github.com/f-lopes;>@f-lopes XMLUnit for Java 2.8.1 - /Released 2020-11-15/ added a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later. This module no longer uses
[GitHub] [maven-javadoc-plugin] dependabot[bot] opened a new pull request #113: Bump httpcore from 4.4.14 to 4.4.15
dependabot[bot] opened a new pull request #113: URL: https://github.com/apache/maven-javadoc-plugin/pull/113 Bumps httpcore from 4.4.14 to 4.4.15. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MWRAPPER-40) Wrapper Properties File License system dependant line separator
[ https://issues.apache.org/jira/browse/MWRAPPER-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MWRAPPER-40. - Fix Version/s: 3.2.0 Assignee: Herve Boutemy Resolution: Fixed PR merged in https://github.com/apache/maven-wrapper/commit/0cc43ce3aeeea11a89db0eb2f830264efebba391 thank you > Wrapper Properties File License system dependant line separator > --- > > Key: MWRAPPER-40 > URL: https://issues.apache.org/jira/browse/MWRAPPER-40 > Project: Maven Wrapper > Issue Type: Bug > Components: Maven Wrapper Plugin >Affects Versions: 3.1.0 >Reporter: Jorge Solórzano >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.2.0 > > > The license added to the wrapper properties file uses a template with a > hardcoded "\n" line separator, and later the properties are written with > System.lineSeparator(), this can create a file with mixed line separator. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MWRAPPER-40) Wrapper Properties File License system dependant line separator
[ https://issues.apache.org/jira/browse/MWRAPPER-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462306#comment-17462306 ] ASF GitHub Bot commented on MWRAPPER-40: hboutemy merged pull request #11: URL: https://github.com/apache/maven-wrapper/pull/11 -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Wrapper Properties File License system dependant line separator > --- > > Key: MWRAPPER-40 > URL: https://issues.apache.org/jira/browse/MWRAPPER-40 > Project: Maven Wrapper > Issue Type: Bug > Components: Maven Wrapper Plugin >Affects Versions: 3.1.0 >Reporter: Jorge Solórzano >Priority: Major > > The license added to the wrapper properties file uses a template with a > hardcoded "\n" line separator, and later the properties are written with > System.lineSeparator(), this can create a file with mixed line separator. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-wrapper] hboutemy merged pull request #11: [MWRAPPER-40] Fix line separators in wrapper properties file
hboutemy merged pull request #11: URL: https://github.com/apache/maven-wrapper/pull/11 -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (SUREFIRE-1959) Switch to Maven 3.1+
[ https://issues.apache.org/jira/browse/SUREFIRE-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski reassigned SUREFIRE-1959: - Assignee: Slawomir Jaranowski (was: Tibor Digana) > Switch to Maven 3.1+ > > > Key: SUREFIRE-1959 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1959 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.0.0-M6 > > > We will can use JSR-330. > Refactoring will be easier by separate responsibility to dedicated service. > Smaller service can be easily tested by unit tests, which are lighter than > integration tests. > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=155749857 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-7369) Maven BOM doesn't need to package as a JAR
[
https://issues.apache.org/jira/browse/MNG-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MNG-7369:
Labels: must-be-in-4.0.0-alpha-1 up-for-grabs (was: good-first-issue
must-be-in-4.0.0-alpha-1)
> Maven BOM doesn't need to package as a JAR
> --
>
> Key: MNG-7369
> URL: https://issues.apache.org/jira/browse/MNG-7369
> Project: Maven
> Issue Type: Task
> Components: General
>Reporter: Maarten Mulders
>Priority: Minor
> Labels: must-be-in-4.0.0-alpha-1, up-for-grabs
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The new Maven BOM module packages as a JAR file, which is almost empty:
> {code}
> $ unzip -l maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Archive: maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Length DateTimeName
> - -- -
> 358 01-26-2020 09:04 META-INF/MANIFEST.MF
> 0 01-26-2020 09:04 META-INF/
> 0 01-26-2020 09:04 META-INF/maven/
> 0 01-26-2020 09:04 META-INF/maven/org.apache.maven/
> 0 01-26-2020 09:04 META-INF/maven/org.apache.maven/maven-bom/
> 272 01-26-2020 09:04 META-INF/DEPENDENCIES
> 11358 01-26-2020 09:04 META-INF/LICENSE
> 179 01-26-2020 09:04 META-INF/NOTICE
> 6260 01-26-2020 09:04
> META-INF/maven/org.apache.maven/maven-bom/pom.xml
>77 01-26-2020 09:04
> META-INF/maven/org.apache.maven/maven-bom/pom.properties
> - ---
> 18504 10 files
> {code}
> The Maven BOM module should package as "pom" to avoid this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MWRAPPER-40) Wrapper Properties File License system dependant line separator
[ https://issues.apache.org/jira/browse/MWRAPPER-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462300#comment-17462300 ] ASF GitHub Bot commented on MWRAPPER-40: jorsol commented on pull request #11: URL: https://github.com/apache/maven-wrapper/pull/11#issuecomment-997462575 > Please don't mix writing of the license with the actual properties Done. -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Wrapper Properties File License system dependant line separator > --- > > Key: MWRAPPER-40 > URL: https://issues.apache.org/jira/browse/MWRAPPER-40 > Project: Maven Wrapper > Issue Type: Bug > Components: Maven Wrapper Plugin >Affects Versions: 3.1.0 >Reporter: Jorge Solórzano >Priority: Major > > The license added to the wrapper properties file uses a template with a > hardcoded "\n" line separator, and later the properties are written with > System.lineSeparator(), this can create a file with mixed line separator. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-wrapper] jorsol commented on pull request #11: [MWRAPPER-40] Fix line separators in wrapper properties file
jorsol commented on pull request #11: URL: https://github.com/apache/maven-wrapper/pull/11#issuecomment-997462575 > Please don't mix writing of the license with the actual properties Done. -- 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. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-7369) Maven BOM doesn't need to package as a JAR
[
https://issues.apache.org/jira/browse/MNG-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-7369:
---
Labels: good-first-issue must-be-in-4.0.0-alpha-1 (was:
must-be-in-4.0.0-alpha-1)
> Maven BOM doesn't need to package as a JAR
> --
>
> Key: MNG-7369
> URL: https://issues.apache.org/jira/browse/MNG-7369
> Project: Maven
> Issue Type: Task
> Components: General
>Reporter: Maarten Mulders
>Priority: Minor
> Labels: good-first-issue, must-be-in-4.0.0-alpha-1
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The new Maven BOM module packages as a JAR file, which is almost empty:
> {code}
> $ unzip -l maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Archive: maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Length DateTimeName
> - -- -
> 358 01-26-2020 09:04 META-INF/MANIFEST.MF
> 0 01-26-2020 09:04 META-INF/
> 0 01-26-2020 09:04 META-INF/maven/
> 0 01-26-2020 09:04 META-INF/maven/org.apache.maven/
> 0 01-26-2020 09:04 META-INF/maven/org.apache.maven/maven-bom/
> 272 01-26-2020 09:04 META-INF/DEPENDENCIES
> 11358 01-26-2020 09:04 META-INF/LICENSE
> 179 01-26-2020 09:04 META-INF/NOTICE
> 6260 01-26-2020 09:04
> META-INF/maven/org.apache.maven/maven-bom/pom.xml
>77 01-26-2020 09:04
> META-INF/maven/org.apache.maven/maven-bom/pom.properties
> - ---
> 18504 10 files
> {code}
> The Maven BOM module should package as "pom" to avoid this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7358) Can't debug with mvnDebug with version 4
[
https://issues.apache.org/jira/browse/MNG-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462294#comment-17462294
]
Michael Osipov commented on MNG-7358:
-
[~odne...@gmail.com], please add the following to the Arch ticket:
We don't object people to build from source, we encourage too, but as history
has proven many Linux distro alter Maven beyond recognition, especially
Debian/Ubuntu. Therefore, we have no choice, but to reject any distro build
because we cannot and will not check 100 different Linux distro buils for
customizations.
All of our builds are reproducible. If you can prove that your binary package
is bit by bit identical to what we produce, I will accept that in a ticket as
well. I don't like the Debian way and I won't support it. Please be as close as
possible to upstream. Good luck.
BTW: I fully appreciate and acknowledge this comment:
https://bugs.archlinux.org/task/73085#comment204468
> Can't debug with mvnDebug with version 4
>
>
> Key: MNG-7358
> URL: https://issues.apache.org/jira/browse/MNG-7358
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 4.0.x-candidate
> Environment: Linux
> 3.8.3
> $ mvn --version
> Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 3.8.3 (NON_CANONICAL)
> Maven home: /opt/maven
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
> 4.0.0
> Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 4.0.0-alpha-1-SNAPSHOT (3a06530dbce82e2054afa3cc4c81631910474bd0)
> Maven home: /opt/maven-git
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
>Reporter: Odne Hellebø
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: image-2021-12-11-21-55-46-230.png, intellijDebug.png,
> mvnDebugGit.zip, screenshot-1.png
>
>
> When using mvnDebug at version 4, it just skips all the breakpoints in
> intellij.
> These are the settings in intellij
> !intellijDebug.png!
> To reproduce just set some breakpoints in test, and then run
> {code:bash}mvnDebug test{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7369) Maven BOM doesn't need to package as a JAR
[
https://issues.apache.org/jira/browse/MNG-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-7369:
---
Labels: must-be-in-4.0.0-alpha-1 (was: )
> Maven BOM doesn't need to package as a JAR
> --
>
> Key: MNG-7369
> URL: https://issues.apache.org/jira/browse/MNG-7369
> Project: Maven
> Issue Type: Task
> Components: General
>Reporter: Maarten Mulders
>Priority: Minor
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The new Maven BOM module packages as a JAR file, which is almost empty:
> {code}
> $ unzip -l maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Archive: maven-bom/target/maven-bom-4.0.0-alpha-1-SNAPSHOT.jar
> Length DateTimeName
> - -- -
> 358 01-26-2020 09:04 META-INF/MANIFEST.MF
> 0 01-26-2020 09:04 META-INF/
> 0 01-26-2020 09:04 META-INF/maven/
> 0 01-26-2020 09:04 META-INF/maven/org.apache.maven/
> 0 01-26-2020 09:04 META-INF/maven/org.apache.maven/maven-bom/
> 272 01-26-2020 09:04 META-INF/DEPENDENCIES
> 11358 01-26-2020 09:04 META-INF/LICENSE
> 179 01-26-2020 09:04 META-INF/NOTICE
> 6260 01-26-2020 09:04
> META-INF/maven/org.apache.maven/maven-bom/pom.xml
>77 01-26-2020 09:04
> META-INF/maven/org.apache.maven/maven-bom/pom.properties
> - ---
> 18504 10 files
> {code}
> The Maven BOM module should package as "pom" to avoid this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7370) Upgrade Maven Wagon to 3.5.0
[ https://issues.apache.org/jira/browse/MNG-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7370: --- Labels: must-be-in-4.0.0-alpha-1 (was: ) > Upgrade Maven Wagon to 3.5.0 > > > Key: MNG-7370 > URL: https://issues.apache.org/jira/browse/MNG-7370 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-7286) Maven code style improvements
[ https://issues.apache.org/jira/browse/MNG-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7286: --- Labels: must-be-in-4.0.0-alpha-1 (was: ) > Maven code style improvements > - > > Key: MNG-7286 > URL: https://issues.apache.org/jira/browse/MNG-7286 > Project: Maven > Issue Type: Improvement >Reporter: Arturo Bernal >Priority: Minor > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.0, 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-7347) SessionScoped beans should be singletons for a given session
[ https://issues.apache.org/jira/browse/MNG-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7347: --- Labels: must-be-in-4.0.0-alpha-1 (was: ) > SessionScoped beans should be singletons for a given session > > > Key: MNG-7347 > URL: https://issues.apache.org/jira/browse/MNG-7347 > Project: Maven > Issue Type: Bug >Affects Versions: 3.8.4 >Reporter: Guillaume Nodet >Priority: Major > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-7345) Missing exported packages
[ https://issues.apache.org/jira/browse/MNG-7345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7345: --- Labels: must-be-in-4.0.0-alpha-1 (was: ) > Missing exported packages > - > > Key: MNG-7345 > URL: https://issues.apache.org/jira/browse/MNG-7345 > Project: Maven > Issue Type: Bug >Reporter: Guillaume Nodet >Priority: Major > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-7330) Upgrade parent and revert MNG-7329
[ https://issues.apache.org/jira/browse/MNG-7330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7330: --- Labels: must-be-in-4.0.0-alpha-1 (was: ) > Upgrade parent and revert MNG-7329 > -- > > Key: MNG-7330 > URL: https://issues.apache.org/jira/browse/MNG-7330 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Priority: Major > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-7267) Documentation updates for pages based on Maven Core Plexus XML
[ https://issues.apache.org/jira/browse/MNG-7267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7267: --- Labels: must-be-in-4.0.0-alpha-1 (was: ) > Documentation updates for pages based on Maven Core Plexus XML > -- > > Key: MNG-7267 > URL: https://issues.apache.org/jira/browse/MNG-7267 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Tamás Cservenák >Priority: Major > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.0, 4.0.0-alpha-1 > > > Now that maven-core/src/main/resources/META-INF/plexus/ directory has all 3 > Plexus XMLs removed, we need to update documentation pages that were > referring them: > [https://maven.apache.org/ref/3.8.2/maven-core/lifecycles.html] > [https://maven.apache.org/ref/3.8.2/maven-core/default-bindings.html] > [https://maven.apache.org/ref/3.8.2/maven-core/artifact-handlers.html] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-7260) Remove old deprecated code
[
https://issues.apache.org/jira/browse/MNG-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-7260:
---
Labels: must-be-in-4.0.0-alpha-1 (was: )
> Remove old deprecated code
> --
>
> Key: MNG-7260
> URL: https://issues.apache.org/jira/browse/MNG-7260
> Project: Maven
> Issue Type: Task
>Reporter: Guillaume Nodet
>Priority: Major
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Things like {{maven-compat}} for example, but we should review everything
> that has been deprecated since quite some time and possibly remove those.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7319) Maven 4 (SNAPSHOT) can't build itself
[
https://issues.apache.org/jira/browse/MNG-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-7319:
---
Labels: must-be-in-4.0.0-alpha-1 (was: )
> Maven 4 (SNAPSHOT) can't build itself
> -
>
> Key: MNG-7319
> URL: https://issues.apache.org/jira/browse/MNG-7319
> Project: Maven
> Issue Type: Bug
> Components: Core
> Environment: Apache Maven 4.0.0-alpha-1-SNAPSHOT
> (a5f1bca9efdb19b6a04db9e31101c55d40a34559)
> Maven home: /home/maarten/Junk/apache-maven-4.0.0-alpha-1-SNAPSHOT
> Java version: 16.0.1, vendor: AdoptOpenJDK, runtime:
> /usr/lib/jvm/adoptopenjdk-16-hotspot-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.11.0-34-generic", arch: "amd64", family: "unix"
>Reporter: Maarten Mulders
>Priority: Blocker
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.0-alpha-1
>
>
> Apache Maven 4.0.0-alpha-1-SNAPSHOT
> (a5f1bca9efdb19b6a04db9e31101c55d40a34559) can't build itself.
> The build fails at the very first plugin on the very first module:
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce
> (enforce-maven-version) on project maven-bom: Execution enforce-maven-version
> of goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce failed:
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce:
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.plugin.PluginParameterExpressionEvaluator.(org.apache.maven.execution.MavenSession,
> org.apache.maven.plugin.MojoExecution,
> org.apache.maven.project.path.PathTranslator,
> org.codehaus.plexus.logging.Logger, org.apache.maven.project.MavenProject,
> java.util.Properties)'{quote}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-6992) Allow access to org.eclipse.aether.transform
[
https://issues.apache.org/jira/browse/MNG-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462289#comment-17462289
]
Michael Osipov commented on MNG-6992:
-
Then let's leave this in 4.x.
> Allow access to org.eclipse.aether.transform
>
>
> Key: MNG-6992
> URL: https://issues.apache.org/jira/browse/MNG-6992
> Project: Maven
> Issue Type: Improvement
> Components: Class Loading
>Affects Versions: 3.6.3
>Reporter: Slawomir Jaranowski
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
>
> Maven core doesn't export org.eclipse.aether.transform package in
> {{maven-core/src/main/resources/META-INF/maven/extension.xml}}
> So when we want, in plugin code, call:
> {code:java}
> org.eclipse.aether.RepositorySystemSession repositorySystemSession;
> ...
> repositorySystemSession.getFileTransformerManager()
> {code}
> we have:
> {code:java}
> [ERROR] Failed to execute goal ... failed: A required class was missing
> while executing ... org/eclipse/aether/transform/FileTransformerManager
> Caused by: java.lang.NoClassDefFoundError:
> org/eclipse/aether/transform/FileTransformerManager
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-6992) Allow access to org.eclipse.aether.transform
[
https://issues.apache.org/jira/browse/MNG-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6992:
Fix Version/s: (was: 3.9.0-candidate)
> Allow access to org.eclipse.aether.transform
>
>
> Key: MNG-6992
> URL: https://issues.apache.org/jira/browse/MNG-6992
> Project: Maven
> Issue Type: Improvement
> Components: Class Loading
>Affects Versions: 3.6.3
>Reporter: Slawomir Jaranowski
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Maven core doesn't export org.eclipse.aether.transform package in
> {{maven-core/src/main/resources/META-INF/maven/extension.xml}}
> So when we want, in plugin code, call:
> {code:java}
> org.eclipse.aether.RepositorySystemSession repositorySystemSession;
> ...
> repositorySystemSession.getFileTransformerManager()
> {code}
> we have:
> {code:java}
> [ERROR] Failed to execute goal ... failed: A required class was missing
> while executing ... org/eclipse/aether/transform/FileTransformerManager
> Caused by: java.lang.NoClassDefFoundError:
> org/eclipse/aether/transform/FileTransformerManager
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7244) Change from deprecated WARNING to FAIL the build for usage of pom.X placeholders
[
https://issues.apache.org/jira/browse/MNG-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7244:
Labels: must-be-in-4.0.0-alpha-1 (was: )
> Change from deprecated WARNING to FAIL the build for usage of pom.X
> placeholders
>
>
> Key: MNG-7244
> URL: https://issues.apache.org/jira/browse/MNG-7244
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 4.0.0-alpha-1
>Reporter: Karl Heinz Marbaise
>Assignee: Maarten Mulders
>Priority: Minor
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.x-candidate
>
>
> Currently we produce a {{WARNING}} in case of using {{pom.version}} or alike.
> I would suggest to change {{WARNING}} into a failing build in such use cases.
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for 'com.soebes.examples.j2ee:appasm:pom:1.0-SNAPSHOT'
> [WARNING] The expression ${pom.version} is deprecated. Please use
> ${project.version} instead.
> {code}
> WDYT?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-5982) The POM for ... is invalid, transitive dependencies ... while property was overriden
[
https://issues.apache.org/jira/browse/MNG-5982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5982:
Labels: must-be-in-4.0.0-alpha-1 needs-attention (was: needs-attention)
> The POM for ... is invalid, transitive dependencies ... while property was
> overriden
>
>
> Key: MNG-5982
> URL: https://issues.apache.org/jira/browse/MNG-5982
> Project: Maven
> Issue Type: Bug
> Components: Dependencies, Inheritance and Interpolation, POM
>Affects Versions: 3.0, 3.3.9
> Environment: Linux and Mac
>Reporter: Fabrice Pipart
>Priority: Minor
> Labels: must-be-in-4.0.0-alpha-1, needs-attention
> Fix For: 4.0.x-candidate
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I experienced issues with a maven build that does not behave the same way if
> done on Windows (like they were done in the past) or Linux (like I want to do
> them now).
> I want to build a project that has a dependency on another project that pom
> that itself imports a pom that contains a Windows path.
> {code:xml}
>my project | other project
> |
> mybuild ---|--> pom > pom with systemPath
> dependencyimport
> |
> {code}
> But in a nutshell, here is my pom:
> {code:xml}
> test.properties
> buildme
> 1.0-SNAPSHOT
> ...
>
>
> test.properties.installme
> module
> 1.0-SNAPSHOT
> pom
>
>
> {code}
> And I depend on a pom that looks like this (not under my control)
> {code:xml}
> test.properties.installme
> module
> 1.0-SNAPSHOT
> ...
>
>
>
> test.properties.installme
> dependency
> 1.0-SNAPSHOT
> import
> pom
>
>
>
>
>
> log4j
> log4j
> 1.2.17
>
>
> {code}
> and the problem lies in this last pom (not under my control again):
> {code:xml}
> 4.0.0
> test.properties.installme
> dependency
> 1.0-SNAPSHOT
> ...
>
> D:/java/jdk1.8.0_65/lib/tools.jar
>
>
>
>
> com.sun
> tools
> 1.8
> system
> ${com.sun.tools.path}
>
>
>
> {code}
> I have no control on the other project in question. I totally agree that a
> refactoring to use environment variable in place of the hard coded paths
> would solve my problem. But instead the Windows path is defined in a
> property. *One would think that overriding the value of the property
> depending on my platform would be enough.* But it is not.
> Unfortunately in this precise case case maven seems to behave to behave
> poorly.
> Before applying any property override in any form (in settings.xml,
> -Dproperty=, redefinition in root pom), maven starts building the effective
> pom. And during that step, if it finds the pattern I mentioned above (a
> dependency on another pom that itself imports a pom that contains a Windows
> path), then it says:
> {code:xml}
> The POM for ::jar: is invalid, transitive
> dependencies (if any) will not be available
> {code}
> As a consequence, my project needs to explicitly define all the dependencies
> of the second project. And I cannot rely on transitive dependencies which
> gives me a lot of trouble.
> In order to illustrate the issue, I created a minimal example showing the
> problem. It can be found here:
> [https://github.com/fabricepipart/test-properties]
> Can you confirm this is a bug from maven?
> I tested with several versions of maven. 3.0 up to a 3.3.9 I think.
> The issue remains the same. It is all a matter of redefining the value of the
> property based on the environment. If I *launch maven with
> -Dcom.sun.tools.path=/correct/linux/path*, globally my build is fine. Because
> when the classes are compiled, it is the *overriden Linux path that is
> taken*, not the Windows one.
> But during the *initial evaluation of the pom*(before any maven phase is
> started), the error I mentioned above is thrown because the *value of the
> property is still the Windows one* (and the path is considered invalid).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7046) Revert MNG-5639 and make repo config static only
[ https://issues.apache.org/jira/browse/MNG-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7046: Labels: must-be-in-4.0.0-alpha-1 (was: ) > Revert MNG-5639 and make repo config static only > > > Key: MNG-7046 > URL: https://issues.apache.org/jira/browse/MNG-7046 > Project: Maven > Issue Type: Task > Components: Artifacts and Repositories, Dependencies >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.0, 4.0.0-alpha-1 > > > As discussed in MNG-5639 repositories should always be known upfront, they > have to be static to avoid chicken and egg situations, a project should not > influence settings. It should be the way around. > In subsequent ticket it will be verified that repo configuration does not > contain any expression: > https://github.com/apache/maven/commit/d411c3fa98832e7d86d901fe86ff63ba907cf868#commitcomment-44782281. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-6992) Allow access to org.eclipse.aether.transform
[
https://issues.apache.org/jira/browse/MNG-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462288#comment-17462288
]
Slawomir Jaranowski commented on MNG-6992:
--
but for consequence if {{RepositorySystemSession}} is exported so evrything it
is used by {{RepositorySystemSession}} also should be exported
> Allow access to org.eclipse.aether.transform
>
>
> Key: MNG-6992
> URL: https://issues.apache.org/jira/browse/MNG-6992
> Project: Maven
> Issue Type: Improvement
> Components: Class Loading
>Affects Versions: 3.6.3
>Reporter: Slawomir Jaranowski
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
>
> Maven core doesn't export org.eclipse.aether.transform package in
> {{maven-core/src/main/resources/META-INF/maven/extension.xml}}
> So when we want, in plugin code, call:
> {code:java}
> org.eclipse.aether.RepositorySystemSession repositorySystemSession;
> ...
> repositorySystemSession.getFileTransformerManager()
> {code}
> we have:
> {code:java}
> [ERROR] Failed to execute goal ... failed: A required class was missing
> while executing ... org/eclipse/aether/transform/FileTransformerManager
> Caused by: java.lang.NoClassDefFoundError:
> org/eclipse/aether/transform/FileTransformerManager
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7059) Add profile-free repository support in Maven Settings model
[ https://issues.apache.org/jira/browse/MNG-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7059: Labels: must-be-in-4.0.0-alpha-1 (was: ) > Add profile-free repository support in Maven Settings model > --- > > Key: MNG-7059 > URL: https://issues.apache.org/jira/browse/MNG-7059 > Project: Maven > Issue Type: New Feature > Components: Settings >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Assignee: Robert Scholte >Priority: Major > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.x-candidate > > > With MNG-4645 = the move of Maven Central repository definition out of [Super > POM|https://maven.apache.org/ref/3.6.3/maven-model-builder/super-pom.html] > into global settings, [current settings > model|https://maven.apache.org/ref/3.6.3/maven-settings/settings.html] forces > to use a profile, although central repository should be always there w/o a > profile. > Settings Model version 1.2.0 shall have native support for repositories w/o > the need to use profiles. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-7206) Properly prioritize JVM options from MAVEN_OPTS and jvm.config
[
https://issues.apache.org/jira/browse/MNG-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7206:
Labels: must-be-in-4.0.0-alpha-1 (was: )
> Properly prioritize JVM options from MAVEN_OPTS and jvm.config
> --
>
> Key: MNG-7206
> URL: https://issues.apache.org/jira/browse/MNG-7206
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.x-candidate
>
>
> We currently have two ways of settings options with the JVM:
> 1. {{MAVEN_OPTS}}
> 2. {{.mvn/jvm.config}}
> We should correctly implement and document priority of those two.
> If we go from general to specific, a generic option shall be overridable (if
> possible) with a specific one. Thus, first {{MAVEN_OPTS}} is evaluated then
> {{jvm.config}} since the former applies to all executions while the latter
> applies to a specific project.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7217) Completely update CLI handling according to Commons CLI 1.5 documentation
[
https://issues.apache.org/jira/browse/MNG-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7217:
Labels: must-be-in-4.0.0-alpha-1 (was: )
> Completely update CLI handling according to Commons CLI 1.5 documentation
> -
>
> Key: MNG-7217
> URL: https://issues.apache.org/jira/browse/MNG-7217
> Project: Maven
> Issue Type: Task
> Components: Command Line
>Reporter: Michael Osipov
>Assignee: Maarten Mulders
>Priority: Major
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.x-candidate
>
>
> We currently don't have code which complies with the documentation of Commons
> CLI 1.5. As soon as we move we can address a few issues, e.g., support of
> {{--}} to separate options from real args.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7193) Introduce MAVEN_ARGS environment variable
[
https://issues.apache.org/jira/browse/MNG-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7193:
Labels: must-be-in-4.0.0-alpha-1 (was: )
> Introduce MAVEN_ARGS environment variable
> -
>
> Key: MNG-7193
> URL: https://issues.apache.org/jira/browse/MNG-7193
> Project: Maven
> Issue Type: New Feature
> Components: Command Line
>Affects Versions: 3.8.1
>Reporter: Michael Osipov
>Priority: Major
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.x-candidate
>
>
> Over the last couple of years people demanded to always pass arguments down
> to Maven without supplying it specifically or repeat for every project over
> and over again in {{maven.config}}. Arguments like {{-B}} or {{-V}}.
> A new environment variable {{MAVEN_ARGS}} can be passed *before* the actual
> CLI arguments.
> Ideal precedence:
> {{MAVEN_ARGS}} is overwritten by {{maven.config}} is overwritten by CLI
> arguments. General to specific. Unfortunately, since {{MAVEN_ARGS}} will be
> passed just like CLI arguments there is no way to detect that these arguments
> came either via CLI or {{MAVEN_ARGS}}
> One option would be to add separator token which would be dropped internally
> thus makes it possible to differentiate between both, e.g,,
> {{MAVEN_ARGS_START [ARGS...] MAVEN_ARGS_STOP}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7094) Assure in an IT that reactor repository definitions are not used when Model Builder downloads dependencies with scope import
[ https://issues.apache.org/jira/browse/MNG-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7094: Labels: must-be-in-4.0.0-alpha-1 (was: ) > Assure in an IT that reactor repository definitions are not used when Model > Builder downloads dependencies with scope import > > > Key: MNG-7094 > URL: https://issues.apache.org/jira/browse/MNG-7094 > Project: Maven > Issue Type: Task > Components: Artifacts and Repositories, Dependencies, Design, > Patterns Best Practices, Integration Tests >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Priority: Major > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.x-candidate > > > Based on several discussions (MNG-6772, MNG-6397) the topic of repo scoping > causes a lot of confusion. > Create an IT which shows that repositories defined in a reactor are never > available (inject) to download imported dependency BOMs. Thus all repos are > properly scoped. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-6772) Super POM overwrites remapped central repository in nested dependencyManagement import POMs
[
https://issues.apache.org/jira/browse/MNG-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6772:
Labels: must-be-in-4.0.0-alpha-1 (was: )
> Super POM overwrites remapped central repository in nested
> dependencyManagement import POMs
> ---
>
> Key: MNG-6772
> URL: https://issues.apache.org/jira/browse/MNG-6772
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, POM
>Affects Versions: 3.6.2
>Reporter: Eddie Wiegers
>Priority: Major
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.x-candidate
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> My projects define a repository with {{central,}} which is meant to
> specifically override the entry in the Super POM. This is specifically what
> [JFrog Artifactory
> recommends|https://www.jfrog.com/confluence/display/RTF/Maven+Repository#MavenRepository-ManuallyOverridingtheBuilt-inRepositories]
> doing, and seems valid in situations where the _real_ Maven Central may be
> unreachable.
>
> The override takes precedence almost all of the time. However, there is at
> least one scenario where this is not the case, and that is when importing a
> POM that in turn imports another POM.
>
> Digging into the code, it appears the reason this happens is because the
> {{DefaultModelBuilder}} overwrites repositories after interpolation is
> complete:
> [https://github.com/apache/maven/blob/53f04f03e3e58c75dcc791d557758357a6ec7983/maven-model-builder/src/main/java/org/apache/maven/model/building/DefaultModelBuilder.java#L411]
>
> From what I can tell, this is done with the intention of overwriting
> repositories that were added to the local resolver prior to interpolation
> with the interpolated version. Due to the way the {{DefaultModelResolver}}
> works, an unintended side effect is that the {{central}} repository from the
> Super POM is added once after each interpolation. The first time the
> repository is added, it is added to the {{repositoryIds}} but doesn't
> actually remove the original repository. The second time it is added is when
> the original repository will be replaced. Currently, the repositoryIds are
> preserved in the {{ModelResolver}} when resolving import POMs, leading to the
> behavior I am seeing where the second nested import POM ends up being where
> the failure occurs.
>
> I am planning on submitting a PR to clone the {{ModelResolver}} in a way that
> resets the repositoryIds prior to import POMs being resolved, since they are
> separate artifact builds. That seems like the most consistent fix to me that
> covers cases outside of the the Super POM's {{central}} definition.
>
> *Workarounds*:
> The current workaround is to use a repository ID other than {{central}} for
> my Artifactory repository, which isn't ideal since it leaves the potential
> for long timeouts to occur on the real {{central}} when an artifact can't be
> resolved from my Artifactory repository.
>
> Mirrors are not an ideal workaround since getting them in place on all
> possible build environments isn't trivial.
>
> When looking at the code I noticed
> {{RepositorySystemSession#isIgnoreArtifactDescriptorRepositories()}} being
> checked in various places, which seems like it would also act as a potential
> workaround, but I don't see a way to enable this value via MavenCLI or
> properties of any kind. It seems like this value aligns well with what
> Artifactory is already trying to enforce, so it would make sense to enable
> this in projects that intend to exclusively use Artifactory. Is there a
> supported way to set this value outside of constructing a Maven build in code?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7020) Remove Maven 2 WagonExcluder backward compat code
[ https://issues.apache.org/jira/browse/MNG-7020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7020: Labels: must-be-in-4.0.0-alpha-1 (was: ) > Remove Maven 2 WagonExcluder backward compat code > - > > Key: MNG-7020 > URL: https://issues.apache.org/jira/browse/MNG-7020 > Project: Maven > Issue Type: Task > Components: Class Loading, Dependencies >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.x-candidate > > Attachments: mng5669-log_post-mng7020.txt, mng5669-log_pre-mng7020.txt > > > Maven includes a Wagon Excluder when Maven 2 artifacts are used with Wagon > 1.0.x: > https://maven.apache.org/ref/3.8.4/maven-core/xref/org/apache/maven/plugin/internal/WagonExcluder.html > This is ancient Maven 2 backward compat. > Let's remove it and hope everyone has moved on to Maven 3.x artifacts and > Wagon 3.x. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-6112) Central repository in the 4.0.0 super POM should declare update policy 'never'.
[ https://issues.apache.org/jira/browse/MNG-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6112: Labels: must-be-in-4.0.0-alpha-1 (was: ) > Central repository in the 4.0.0 super POM should declare update policy > 'never'. > --- > > Key: MNG-6112 > URL: https://issues.apache.org/jira/browse/MNG-6112 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0-beta-1 >Reporter: Christian Schulte >Assignee: Robert Scholte >Priority: Major > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.x-candidate > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-5781) resolution of nested import scoped dependencies causes maven to reach out to external central repo
[
https://issues.apache.org/jira/browse/MNG-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5781:
Labels: must-be-in-4.0.0-alpha-1 (was: )
> resolution of nested import scoped dependencies causes maven to reach out to
> external central repo
> --
>
> Key: MNG-5781
> URL: https://issues.apache.org/jira/browse/MNG-5781
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap Build, Dependencies
>Affects Versions: 3.2.5
> Environment: Apache Maven 3.2.5
> (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T09:29:23-08:00)
> Maven home: /usr/local/maven-3.2.5
> Java version: 1.7.0_76, vendor: Oracle Corporation
> Java home: /usr/local/jdk1.7.0_76-server-jre/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-504.3.3.el6.centos.plus.x86_64", arch:
> "amd64", family: "unix"
>Reporter: Ravi Sanwal
>Priority: Major
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.x-candidate
>
> Attachments: MNG-5781-Maven360.txt, first.pom.xml,
> global_settings.xml, last.pom.xml, second.pom.xml
>
>
> When a project uses a dependency that has as import scoped dependency, which
> in turn also has another import scoped dependency (nested imported scoped
> dependencies), resolution of the last level of dependency makes maven to
> reach our to the external central repository
> ([https://repo.maven.apache.org/maven2/])
> Steps to reproduce:
> Use the attached global settings file.
> It has an internal repository declared as a replacement to 'central', you can
> point to one of your own internal repo.(not the local)
> Build the attached file first.pom.xml:
> {code:java}
> mvn -gs global_settings.xml install -f first.pom.xml{code}
> Build the attached file second.pom.xml:
> {code:java}
> mvn install -f second.pom.xml{code}
> Then, delete _org.aspectj:aspectjtools from local repo (rm
> ~/.m2/repository/org/aspectj_/aspectjtools), we want to download this from
> our internal central repository alias repository.
> Build the attached file last.pom.xml:
> {code:java}
> mvn -gs global_settings.xml dependency:copy-dependencies -f last.pom.xml{code}
> (copy dependencies because this is a pom project, alternatively change
> last.pom.xml to a jar project and do mvn -gs global_settings.xml install -
> same thing)
> You'll see that org.aspectj:aspectjtools is being downloaded from central
> ([https://repo.maven.apache.org/maven2/]) effectively rendering hosting our
> own repositories useless.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-6561) New RepositorySystem implementation as replacement of deprecated from maven-compat
[
https://issues.apache.org/jira/browse/MNG-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6561:
Labels: must-be-in-4.0.0-alpha-1 (was: )
> New RepositorySystem implementation as replacement of deprecated from
> maven-compat
> --
>
> Key: MNG-6561
> URL: https://issues.apache.org/jira/browse/MNG-6561
> Project: Maven
> Issue Type: Improvement
>Reporter: Sylwester Lachiewicz
>Priority: Major
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.x-candidate
>
>
> Create a component that will replace
> org.apache.maven.repository.RepositorySystem implementation from maven-compat
> module to keep backward compatibility with Maven 2.x plugins.
> While testing MNG-5995 and with deleted maven-compat.jar - a compilation of
> basic project failed with error:
>
> {code:java}
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ my-app ---
> [WARNING] Error injecting: org.apache.maven.plugin.compiler.CompilerMojo
> com.google.inject.ProvisionException: Unable to provision, see the following
> errors:
> 1) No implementation for org.apache.maven.repository.RepositorySystem was
> bound.
> while locating org.apache.maven.plugin.compiler.CompilerMojo
> 1 error
> at com.google.inject.internal.InternalProvisionException.toProvisionException
> (InternalProvisionException.java:226)
> at com.google.inject.internal.InjectorImpl$1.get (InjectorImpl.java:1053)
> at com.google.inject.internal.InjectorImpl.getInstance
> (InjectorImpl.java:1086)
> at org.eclipse.sisu.space.AbstractDeferredClass.get
> (AbstractDeferredClass.java:48)
> at com.google.inject.internal.ProviderInternalFactory.provision
> (ProviderInternalFactory.java:85)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision
> (InternalFactoryToInitializableAdapter.java:57)
> at com.google.inject.internal.ProviderInternalFactory$1.call
> (ProviderInternalFactory.java:66)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision
> (ProvisionListenerStackCallback.java:112)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision
> (ProvisionListenerStackCallback.java:127)
> at com.google.inject.internal.ProvisionListenerStackCallback.provision
> (ProvisionListenerStackCallback.java:66)
> at com.google.inject.internal.ProviderInternalFactory.circularGet
> (ProviderInternalFactory.java:61)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.get
> (InternalFactoryToInitializableAdapter.java:47)
> at com.google.inject.internal.InjectorImpl$1.get (InjectorImpl.java:1050)
> at org.eclipse.sisu.inject.Guice4$1.get (Guice4.java:162)
> at org.eclipse.sisu.inject.LazyBeanEntry.getValue (LazyBeanEntry.java:81)
> at org.eclipse.sisu.plexus.LazyPlexusBean.getValue (LazyPlexusBean.java:51)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup
> (DefaultPlexusContainer.java:263)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup
> (DefaultPlexusContainer.java:255)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
> (DefaultMavenPluginManager.java:520)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:124)
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project my-app: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed: Unable
> to load the mojo 'compile' (or one of its required components) from the
> plugin 'org.apache.maven.plugins:maven-compiler-plugin:3.8.0':
> com.google.inject.ProvisionException: Unable to provision, see the following
> errors:
> [ERROR]
> [ERROR] 1) No implementation for c was bound.
> [ERROR] while locating org.apache.maven.plugin.compiler.CompilerMojo
> [ERROR] at
> ClassRealm[plugin>org.apache.maven.plugins:maven-compiler-plugin:3.8.0,
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@6e5e91e4] (via
> modules: org.eclipse.sisu.wire.WireModule ->
> org.eclipse.sisu.plexus.PlexusBindingModule)
> [ERROR] while locating org.apache.maven.plugin.Mojo annotated with
> @com.google.inject.name.Named(value="org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile")
> [ERROR]
> [ERROR] 1 error
> [ERROR] role: org.apache.maven.plugin.Mojo
> [ERROR] roleHint:
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile{code}
> Sometimes we can change usages of
> _org.apache.maven.repository.RepositorySystem_ to
> _org.apache.maven.bridge.MavenRepositorySystem_
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-5180) Versioning's snapshot version list is not included in metadata merge
[ https://issues.apache.org/jira/browse/MNG-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-5180: Labels: must-be-in-4.0.0-alpha-1 (was: ) > Versioning's snapshot version list is not included in metadata merge > -- > > Key: MNG-5180 > URL: https://issues.apache.org/jira/browse/MNG-5180 > Project: Maven > Issue Type: Bug >Affects Versions: 3.0.3 >Reporter: Noam Y. Tenne >Assignee: Michael Osipov >Priority: Major > Labels: must-be-in-4.0.0-alpha-1 > Fix For: 4.0.x-candidate > > Attachments: MavenMetadataSnapshotVersionsMergeTest.java > > > Versioning#snapshotVersions is not being merged when using Metadata#merge. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-6956) Ensure all Apache Maven repositories can handle build/consumer
[
https://issues.apache.org/jira/browse/MNG-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6956:
Labels: must-be-in-4.0.0-alpha-1 (was: )
> Ensure all Apache Maven repositories can handle build/consumer
> --
>
> Key: MNG-6956
> URL: https://issues.apache.org/jira/browse/MNG-6956
> Project: Maven
> Issue Type: Task
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Critical
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.x-candidate
>
>
> First run based on https://github.com/apache/maven-sources/tree/submodules
> {noformat}
> [INFO] Maven Core ITs suite 2.1-SNAPSHOT .. FAILURE [36:34
> min]
> [INFO] Maven Artifact Resolver Ant Tasks 1.2.2-SNAPSHOT ... FAILURE [ 34.579
> s]
> [INFO] Maven Plugin Testing Mechanism 3.4.0-SNAPSHOT .. FAILURE [ 0.972
> s]
> [INFO] Maven :: Indexer Core 6.1.0-SNAPSHOT ... FAILURE [ 2.874
> s]
> [INFO] Maven Surefire Common 3.0.0-M6-SNAPSHOT FAILURE [ 0.544
> s]
> [INFO] Maven Surefire Integration Tests 3.0.0-M6-SNAPSHOT . FAILURE [ 1.499
> s]
> [INFO] Apache Maven AntRun Plugin 3.1.0-SNAPSHOT .. FAILURE [01:54
> min]
> [INFO] Apache Maven Enforcer API 3.0.0-M4-SNAPSHOT FAILURE [ 0.096
> s]
> [INFO] Apache Maven PDF Plugin 1.5.0-SNAPSHOT . FAILURE [01:49
> min]
> [INFO] Maven Plugin Metadata Model 3.6.1-SNAPSHOT . FAILURE [ 0.083
> s]
> [INFO] Maven Ant Mojo Support 3.6.1-SNAPSHOT .. FAILURE [ 0.440
> s]
> [INFO] Maven Beanshell Mojo Support 3.6.1-SNAPSHOT FAILURE [ 0.171
> s]
> [INFO] Maven Release APIs 3.0.0-SNAPSHOT .. FAILURE [ 0.243
> s]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-6992) Allow access to org.eclipse.aether.transform
[
https://issues.apache.org/jira/browse/MNG-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462287#comment-17462287
]
Slawomir Jaranowski commented on MNG-6992:
--
can be ...
It is need it for pom-transformers I assume the can be used from 4.x so in 3.x
I don't use this.
For 3.x simply get the same pom without transformation as I remember ...
> Allow access to org.eclipse.aether.transform
>
>
> Key: MNG-6992
> URL: https://issues.apache.org/jira/browse/MNG-6992
> Project: Maven
> Issue Type: Improvement
> Components: Class Loading
>Affects Versions: 3.6.3
>Reporter: Slawomir Jaranowski
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
>
> Maven core doesn't export org.eclipse.aether.transform package in
> {{maven-core/src/main/resources/META-INF/maven/extension.xml}}
> So when we want, in plugin code, call:
> {code:java}
> org.eclipse.aether.RepositorySystemSession repositorySystemSession;
> ...
> repositorySystemSession.getFileTransformerManager()
> {code}
> we have:
> {code:java}
> [ERROR] Failed to execute goal ... failed: A required class was missing
> while executing ... org/eclipse/aether/transform/FileTransformerManager
> Caused by: java.lang.NoClassDefFoundError:
> org/eclipse/aether/transform/FileTransformerManager
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7228) MavenProject.getOriginalSource returns interpolated parts
[
https://issues.apache.org/jira/browse/MNG-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7228:
Labels: must-be-in-4.0.0-alpha-1 (was: )
> MavenProject.getOriginalSource returns interpolated parts
> -
>
> Key: MNG-7228
> URL: https://issues.apache.org/jira/browse/MNG-7228
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-1
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> I have tested the maven-enforcer-plugin 3.0.0 running in a project where I
> use the following configuration:
> {code:xml}
>
> The rules for repo1.maven.org are that pom.xml
> files should not include repository definitions. If
> repository definitions are included, they must be limited
> to SNAPSHOT only repositories.
> true
> true
> true
>
>
> {code}
> The project works correct with Maven 3.X but fails with Maven 4.X (current
> state of master 92d2c2e3b43ca214989f0f517aa90f1525f0ff2e).
> After some investigation it looks like that the
> {{mavenProject.getOriginalModel()}} returns already interpolated model and
> **NOT** the original model.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7228) MavenProject.getOriginalSource returns interpolated parts
[
https://issues.apache.org/jira/browse/MNG-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7228:
Fix Version/s: 4.0.0-alpha-1
> MavenProject.getOriginalSource returns interpolated parts
> -
>
> Key: MNG-7228
> URL: https://issues.apache.org/jira/browse/MNG-7228
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-1
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> I have tested the maven-enforcer-plugin 3.0.0 running in a project where I
> use the following configuration:
> {code:xml}
>
> The rules for repo1.maven.org are that pom.xml
> files should not include repository definitions. If
> repository definitions are included, they must be limited
> to SNAPSHOT only repositories.
> true
> true
> true
>
>
> {code}
> The project works correct with Maven 3.X but fails with Maven 4.X (current
> state of master 92d2c2e3b43ca214989f0f517aa90f1525f0ff2e).
> After some investigation it looks like that the
> {{mavenProject.getOriginalModel()}} returns already interpolated model and
> **NOT** the original model.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[
https://issues.apache.org/jira/browse/MNG-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-2478:
Fix Version/s: (was: 3.9.0-candidate)
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[
https://issues.apache.org/jira/browse/MNG-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462286#comment-17462286
]
Michael Osipov commented on MNG-2478:
-
Agreed.
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-6972) Allow access to org.apache.maven.graph
[
https://issues.apache.org/jira/browse/MNG-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462285#comment-17462285
]
Michael Osipov commented on MNG-6972:
-
[~gnodet], [~rfscholte], worthwhile for 3.9.0?
> Allow access to org.apache.maven.graph
> --
>
> Key: MNG-6972
> URL: https://issues.apache.org/jira/browse/MNG-6972
> Project: Maven
> Issue Type: Improvement
> Components: Class Loading, Plugin API
>Affects Versions: 3.6.3
>Reporter: Michael Kroll
>Assignee: Michael Osipov
>Priority: Major
> Labels: easyfix, pull-request-available
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Hi
> maven doesn't export org.apache.maven.graph package in
> maven-core/src/main/resources/META-INF/maven/extension.xml so the
> GraphBuilder is not usable in extensions.
> {code:java}
> // leads to java.lang.NoClassDefFoundError:
> Lorg/apache/maven/graph/GraphBuilder;
> @Requirement( hint = GraphBuilder.HINT )
> private GraphBuilder graphBuilder;
> {code}
> Background: if one build extension adds dependencies and another build
> extension uses {{session.getProjectDependencyGraph()}}, then the dependency
> graph is out of date. This is because the graph is only rebuilt after
> executing _all_ extensions. One solution to this would be to update the
> {{MavenSession}} and setting the new dependency graph in the first extension,
> but for this we need access to the {{GraphBuilder}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-6972) Allow access to org.apache.maven.graph
[
https://issues.apache.org/jira/browse/MNG-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6972:
Fix Version/s: 3.9.0-candidate
> Allow access to org.apache.maven.graph
> --
>
> Key: MNG-6972
> URL: https://issues.apache.org/jira/browse/MNG-6972
> Project: Maven
> Issue Type: Improvement
> Components: Class Loading, Plugin API
>Affects Versions: 3.6.3
>Reporter: Michael Kroll
>Assignee: Michael Osipov
>Priority: Major
> Labels: easyfix, pull-request-available
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
>
> Hi
> maven doesn't export org.apache.maven.graph package in
> maven-core/src/main/resources/META-INF/maven/extension.xml so the
> GraphBuilder is not usable in extensions.
> {code:java}
> // leads to java.lang.NoClassDefFoundError:
> Lorg/apache/maven/graph/GraphBuilder;
> @Requirement( hint = GraphBuilder.HINT )
> private GraphBuilder graphBuilder;
> {code}
> Background: if one build extension adds dependencies and another build
> extension uses {{session.getProjectDependencyGraph()}}, then the dependency
> graph is out of date. This is because the graph is only rebuilt after
> executing _all_ extensions. One solution to this would be to update the
> {{MavenSession}} and setting the new dependency graph in the first extension,
> but for this we need access to the {{GraphBuilder}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-6965) Extensions suddenly have org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
[
https://issues.apache.org/jira/browse/MNG-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462284#comment-17462284
]
Michael Osipov commented on MNG-6965:
-
[~rfscholte], worthwhile for 3.9.0?
> Extensions suddenly have org.codehaus.plexus:plexus-utils:jar:1.1 on their
> classpath
>
>
> Key: MNG-6965
> URL: https://issues.apache.org/jira/browse/MNG-6965
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.6.0, 3.6.3
> Environment: Win7, Win10, at least one variant of Linux (not sure
> which)
>Reporter: Mark Nolan
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Labels: archetype
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
> Attachments: pom.xml
>
>
> A simple minimal archetype pom following the manual pages downloads
> plexus-utils 1.1, even though it is not (apparently) declared anywhere. This
> version is banned at my organization (edited to add: due to vulnerabilities),
> meaning such a pom always fails.
>
> {code:xml}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> test
> test
> 0.0.1-SNAPSHOT
> maven-archetype
> test
>
>
>
> org.apache.maven.archetype
> archetype-packaging
> 3.1.2
>
>
>
>
>
> org.apache.maven.plugins
> maven-archetype-plugin
> 3.1.2
>
>
>
>
>
> {code}
> Running any goal, such as mvn -X clean, produces the following before the
> goal is executed:
> {code}
> [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=952800,
> ConflictMarker.markTime=586900, ConflictMarker.nodeCount=1,
> ConflictIdSorter.graphTime=549200, ConflictIdSorter.topsortTime=586700,
> ConflictIdSorter.conflictIdCount=1, ConflictIdSorter.conflictIdCycleCount=0,
> ConflictResolver.totalTime=3313100, ConflictResolver.conflictItemCount=1,
> DefaultDependencyCollector.collectTime=66890900,
> DefaultDependencyCollector.transformTime=8523500}
> [DEBUG] org.apache.maven.archetype:archetype-packaging:jar:3.1.2:
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> {code}
>
> As far as I can see, there is no declared dependency on plexus-utils:1.1.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-6965) Extensions suddenly have org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
[
https://issues.apache.org/jira/browse/MNG-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6965:
Fix Version/s: 3.9.0-candidate
> Extensions suddenly have org.codehaus.plexus:plexus-utils:jar:1.1 on their
> classpath
>
>
> Key: MNG-6965
> URL: https://issues.apache.org/jira/browse/MNG-6965
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.6.0, 3.6.3
> Environment: Win7, Win10, at least one variant of Linux (not sure
> which)
>Reporter: Mark Nolan
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Labels: archetype
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
> Attachments: pom.xml
>
>
> A simple minimal archetype pom following the manual pages downloads
> plexus-utils 1.1, even though it is not (apparently) declared anywhere. This
> version is banned at my organization (edited to add: due to vulnerabilities),
> meaning such a pom always fails.
>
> {code:xml}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> test
> test
> 0.0.1-SNAPSHOT
> maven-archetype
> test
>
>
>
> org.apache.maven.archetype
> archetype-packaging
> 3.1.2
>
>
>
>
>
> org.apache.maven.plugins
> maven-archetype-plugin
> 3.1.2
>
>
>
>
>
> {code}
> Running any goal, such as mvn -X clean, produces the following before the
> goal is executed:
> {code}
> [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=952800,
> ConflictMarker.markTime=586900, ConflictMarker.nodeCount=1,
> ConflictIdSorter.graphTime=549200, ConflictIdSorter.topsortTime=586700,
> ConflictIdSorter.conflictIdCount=1, ConflictIdSorter.conflictIdCycleCount=0,
> ConflictResolver.totalTime=3313100, ConflictResolver.conflictItemCount=1,
> DefaultDependencyCollector.collectTime=66890900,
> DefaultDependencyCollector.transformTime=8523500}
> [DEBUG] org.apache.maven.archetype:archetype-packaging:jar:3.1.2:
> [DEBUG]org.codehaus.plexus:plexus-utils:jar:1.1:runtime
> {code}
>
> As far as I can see, there is no declared dependency on plexus-utils:1.1.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-6949) As a developer on Maven Core I would like to verify my build before merge
[ https://issues.apache.org/jira/browse/MNG-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462283#comment-17462283 ] Michael Osipov commented on MNG-6949: - No version required, this goes online directly. > As a developer on Maven Core I would like to verify my build before merge > - > > Key: MNG-6949 > URL: https://issues.apache.org/jira/browse/MNG-6949 > Project: Maven > Issue Type: Improvement >Reporter: Martin Kanters >Assignee: Sylwester Lachiewicz >Priority: Major > > One of the requirements before providing a pull request to Maven is that you > have to run `mvn verify` and the integration tests. This is to ensure that > the PR that is delivered is of good quality. I do not disagree with this > approach, but it can be easy to forget to run this, especially in the case of > processing (small) review comments. > For me it already happened a couple of times that a failing test was found at > the time when the pull request was getting merged in master. By utilizing > GitHub Actions we can ensure that the PR's requirements are fulfilled. This > is meant as an addition on top of local tests and the CI job on Jenkins tests > that commiters execute during merger, not a replacement. > > I have implemented this last weekend and would like to propose this. It is > based on another Maven project's GitHub Action workflow, but has been > extended. It features the following: > # mvn verify on Ubuntu, Windows and MacOS machines, with Java 8, 11, 14. > # integration tests against the new Maven build (from step 1). > By default it will run against the latest master version of > apache/maven-integration-testing. > However, if the developer has a branch with the same name as the maven PR on > a forked maven-integration-testing project, it will check that out instead. > Link to the pull request: [https://github.com/apache/maven/pull/365]. > Currently the action is not running on the PR itself, I guess that is due to > settings in the apache/maven project. > It is running on the branch of our fork, though: > [https://github.com/infosupport/maven/actions/runs/150771674]. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-6949) As a developer on Maven Core I would like to verify my build before merge
[ https://issues.apache.org/jira/browse/MNG-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6949: Fix Version/s: (was: 4.0.0) (was: 4.0.0-alpha-1) > As a developer on Maven Core I would like to verify my build before merge > - > > Key: MNG-6949 > URL: https://issues.apache.org/jira/browse/MNG-6949 > Project: Maven > Issue Type: Improvement >Reporter: Martin Kanters >Assignee: Sylwester Lachiewicz >Priority: Major > > One of the requirements before providing a pull request to Maven is that you > have to run `mvn verify` and the integration tests. This is to ensure that > the PR that is delivered is of good quality. I do not disagree with this > approach, but it can be easy to forget to run this, especially in the case of > processing (small) review comments. > For me it already happened a couple of times that a failing test was found at > the time when the pull request was getting merged in master. By utilizing > GitHub Actions we can ensure that the PR's requirements are fulfilled. This > is meant as an addition on top of local tests and the CI job on Jenkins tests > that commiters execute during merger, not a replacement. > > I have implemented this last weekend and would like to propose this. It is > based on another Maven project's GitHub Action workflow, but has been > extended. It features the following: > # mvn verify on Ubuntu, Windows and MacOS machines, with Java 8, 11, 14. > # integration tests against the new Maven build (from step 1). > By default it will run against the latest master version of > apache/maven-integration-testing. > However, if the developer has a branch with the same name as the maven PR on > a forked maven-integration-testing project, it will check that out instead. > Link to the pull request: [https://github.com/apache/maven/pull/365]. > Currently the action is not running on the PR itself, I guess that is due to > settings in the apache/maven project. > It is running on the branch of our fork, though: > [https://github.com/infosupport/maven/actions/runs/150771674]. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-6815) Upgrade Guice to 4.2.2
[ https://issues.apache.org/jira/browse/MNG-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6815: Summary: Upgrade Guice to 4.2.2 (was: Upgrade Guice 4.2.2) > Upgrade Guice to 4.2.2 > -- > > Key: MNG-6815 > URL: https://issues.apache.org/jira/browse/MNG-6815 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap Build >Affects Versions: 3.6.3 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-6815) Upgrade Guice 4.2.2
[ https://issues.apache.org/jira/browse/MNG-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6815: Fix Version/s: 3.9.0-candidate > Upgrade Guice 4.2.2 > --- > > Key: MNG-6815 > URL: https://issues.apache.org/jira/browse/MNG-6815 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap Build >Affects Versions: 3.6.3 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-7068) Active dependency management for Google Guice/Guava
[ https://issues.apache.org/jira/browse/MNG-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7068: Fix Version/s: 3.9.0-candidate > Active dependency management for Google Guice/Guava > --- > > Key: MNG-7068 > URL: https://issues.apache.org/jira/browse/MNG-7068 > Project: Maven > Issue Type: Improvement > Components: Dependencies >Affects Versions: 3.6.3 >Reporter: Boris Unckel >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate > > > The current pom includes com.google.inject:guice with the default transitive > dependency of com.google.guava:guava. Guava has declared several > dependencies, which are not needed at runtime. Only > com.google.guava:failureaccess is needed. > The proposal is first to add com.google.guava:guava to the excludes of guice. > Second guava and failureaccess shall be added as direct dependencies. > This has two advantages: Downstream projects only get the needed dependencies > and the version of guava can be independently set. > The runtime dependencies for Guava are explained in the last section of the > [README|https://github.com/google/guava/tree/v30.1] "Important Warnings" #3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-6815) Upgrade Guice 4.2.2
[ https://issues.apache.org/jira/browse/MNG-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6815: Summary: Upgrade Guice 4.2.2 (was: Upgrade guice 4.2.2) > Upgrade Guice 4.2.2 > --- > > Key: MNG-6815 > URL: https://issues.apache.org/jira/browse/MNG-6815 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap Build >Affects Versions: 3.6.3 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 4.0.0, 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[
https://issues.apache.org/jira/browse/MNG-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462282#comment-17462282
]
Robert Scholte commented on MNG-2478:
-
Think about scope! Maven 3.8.2+ learned the scope was too big and as you know:
I'm only having a focus on Maven 4.
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-6878) Upgrade Guice to 4.2.3
[
https://issues.apache.org/jira/browse/MNG-6878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6878:
Fix Version/s: 3.9.0-candidate
> Upgrade Guice to 4.2.3
> --
>
> Key: MNG-6878
> URL: https://issues.apache.org/jira/browse/MNG-6878
> Project: Maven
> Issue Type: Dependency upgrade
>Reporter: Sylwester Lachiewicz
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
>
> h4. Changes since Guice 4.2.2 [https://github.com/google/guice/wiki/Guice423]
> [http://google.github.io/guice/api-docs/4.2.3/api-diffs/changes.html]
> * Java14 support (updated asm).
> * Added {{Injector.getElements}} API, to expose all Element SPI types from
> the Injector.
> * Added {{Injector.getAllMembersInjectorInjectionPoints}} API, to expose
> injection points created by arbitrary members injection.
> * Added {{getAlternateKeys}} to Multibinder SPI types
> ({{MultibinderBinding}}, {{MapBinderBinding}}, {{OptionalBinderBinding}}), to
> explicitly list the other keys these bindings are available as.
> * Scan for (and bind) @Provides-like methods in a consistent ordering,
> rather than relying on the non-deterministic Class.getDeclaredMembers
> ordering.
> * Update {{DaggerAdapter}} to work with newer dagger code.
> * Fixed a [subtle
> bug|https://github.com/google/guice/commit/f8cc1718a33a868e9951f7d3d6b4f74d8b1a1548]
> with eager singleton evaluation.
> * Updated {{@RequestScope}}'s scope annotation to the JSR330 {{@Scope}}, so
> it can be reused by non-Guice DI systems.
> * Clarified the error message when an injectable constructor is missing.
> * Add deprecated overloads to various {{Modules}} methods, to make it
> clearer when calling them is unnecessary.
> * Added factory methods to {{Modules}} for common Binder configuration
> methods, to make it easier to configure them.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[
https://issues.apache.org/jira/browse/MNG-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462281#comment-17462281
]
Michael Osipov commented on MNG-2478:
-
[~rfscholte], worthwhile for 3.9.0?
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[
https://issues.apache.org/jira/browse/MNG-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-2478:
Fix Version/s: 3.9.0-candidate
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build succeeded in Jenkins: Maven TLP » maven » MNG-6878 #8
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6878/8/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6828 #15
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6828/15/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6656 #56
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6656/56/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build succeeded in Jenkins: Maven TLP » maven » master #434
See https://builds.apache.org/job/maven-box/job/maven/job/master/434/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MPOM-215 #32
See https://builds.apache.org/job/maven-box/job/maven/job/MPOM-215/32/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » REMOVE_DEPRECATED #15
See https://builds.apache.org/job/maven-box/job/maven/job/REMOVE_DEPRECATED/15/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » slf4j-1.8-modules #33
See https://builds.apache.org/job/maven-box/job/maven/job/slf4j-1.8-modules/33/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6012-Missing-Profile-At-End
#56
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6012-Missing-Profile-At-End/56/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » mng-5668-poc #23
See https://builds.apache.org/job/maven-box/job/maven/job/mng-5668-poc/23/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-5222 #13
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5222/13/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #43
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/43/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6889 #2
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6889/2/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6555 #44
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6555/44/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6555 #14
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6555/14/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6551 #14
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/14/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6556 #14
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/14/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6656 #57
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6656/57/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6553 #14
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6553/14/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build failed in Jenkins: Maven TLP » maven » MNG-6828 #13
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6828/13/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6829 #23
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6829/23/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build succeeded in Jenkins: Maven TLP » maven-studies » maven-metrics #18
See
https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/18/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-5567 #54
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5567/54/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-5868 #54
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5868/54/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6548 #21
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6548/21/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MRESOLVER-94 #2
See https://builds.apache.org/job/maven-box/job/maven/job/MRESOLVER-94/2/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6888 #2
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6888/2/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6550 #40
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/40/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6552 #37
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6552/37/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6554 #36
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6554/36/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6878 #6
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6878/6/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6553 #37
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6553/37/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556 #42
See
https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/42/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-2478) add "resources-filtered" filtered resource directories to super POM
[ https://issues.apache.org/jira/browse/MNG-2478 ]
Michael Osipov deleted comment on MNG-2478:
-
was (Author: hudson):
Build unstable in Jenkins: Maven TLP » maven » MNG-6512-build-11 #14
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6512-build-11/14/
> add "resources-filtered" filtered resource directories to super POM
> ---
>
> Key: MNG-2478
> URL: https://issues.apache.org/jira/browse/MNG-2478
> Project: Maven
> Issue Type: New Feature
> Components: POM
>Affects Versions: 2.0.4
> Environment: any
>Reporter: Jörg Hohwiller
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> The super POM contains default folders for resources that are NOT filtered
> (src/main/resources and src/test/resources). If one (additionally) needs a
> filtered resources folder, it needs to override the default and therefore has
> to add all default folders if he does NOT want to "loose" the defaults.
> To make this easier my suggestion is to add filtered resource folders to the
> super POM. This should also fit to the philosophy of maven that aims to have
> defaults and only declare as little custom configuration as needed.
> My personal favorite for the foldernames would be "templates" but to make
> things more obvious to the user maybe "resources-filtered" would be better.
> Actually I do not care to much about the name...
> So the resources in the super POM should look like this:
> {code:xml}
>
> src/main/resources
>
>
>
> src/main/resources-filtered
> true
>
>
>
>
>
> src/test/resources
>
>
>
> src/test/resources-filtered
> true
>
>
> {code}
> Update: The folder name has been changed to "resources-filtered".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
