[jira] [Created] (MNG-6138) Remove obsolete message_*.properties form maven-core
Michael Osipov created MNG-6138:
---
Summary: Remove obsolete message_*.properties form maven-core
Key: MNG-6138
URL: https://issues.apache.org/jira/browse/MNG-6138
Project: Maven
Issue Type: Task
Components: core
Affects Versions: 3.3.9
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.4.0
The folowing files are not used in the entire project tree:
{noformat}
$ find . -name '*.properties'
./src/main/resources/org/apache/maven/messages/messages.properties
./src/main/resources/org/apache/maven/messages/messages_de.properties
./src/main/resources/org/apache/maven/messages/messages_el.properties
./src/main/resources/org/apache/maven/messages/messages_en.properties
./src/main/resources/org/apache/maven/messages/messages_es.properties
./src/main/resources/org/apache/maven/messages/messages_fr.properties
./src/main/resources/org/apache/maven/messages/messages_ja.properties
./src/main/resources/org/apache/maven/messages/messages_ko.properties
./src/main/resources/org/apache/maven/messages/messages_nl.properties
./src/main/resources/org/apache/maven/messages/messages_no.properties
./src/main/resources/org/apache/maven/messages/messages_pl.properties
./src/main/resources/org/apache/maven/messages/messages_zh_CN.properties
{noformat}
The have been added years ago, but never used. Since we do not strive for any
i18n, they are safe to be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MPLUGIN-320) JavaJavadocMojoDescriptorExtractor fails with Java 8 lambdas.
Antony Riley created MPLUGIN-320:
Summary: JavaJavadocMojoDescriptorExtractor fails with Java 8
lambdas.
Key: MPLUGIN-320
URL: https://issues.apache.org/jira/browse/MPLUGIN-320
Project: Maven Plugin Tools
Issue Type: Bug
Components: maven-plugin-tools-java
Affects Versions: 3.5
Reporter: Antony Riley
Priority: Minor
JavaJavadocMojoDescriptorExtractor fails to parse the following source:
{code:java}
package com.example.plugin;
import com.amazonaws.AmazonWebServiceClient;
import com.amazonaws.services.ecr.AmazonECRClient;
import com.amazonaws.services.ecs.AmazonECSClient;
import java.util.function.Supplier;
public enum AmazonClients {
ECS(AmazonECSClient::new),
ECR(AmazonECRClient::new);
private final Supplier supplier;
AmazonClients(Supplier supplier) {
this.supplier = new SingletonSupplier(supplier);
}
public T get() {
return (T) supplier.get();
}
private static class SingletonSupplier implements Supplier {
private final Supplier realSupplier;
private T instance;
private SingletonSupplier(Supplier realSupplier) {
this.realSupplier = realSupplier;
}
@Override
public synchronized T get() {
return instance == null ? instance = realSupplier.get() : instance;
}
}
}
{code}
It fails on the lamdas in the constructors, this causes
maven-plugin-plugin:helpmojo to fail with the following exception:
{noformat}
Caused by: com.thoughtworks.qdox.parser.ParseException: syntax error @[10,24]
in
file:/home/antony/work/meter-download-site-v2/ecs-deploy-maven-plugin/src/main/java/com/vertoanalytics/meterdownloadsite/maven/AmazonClients.java
at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:1739)
at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:1861)
at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:1720)
at
com.thoughtworks.qdox.library.SourceLibrary.parse(SourceLibrary.java:232)
at
com.thoughtworks.qdox.library.SourceLibrary.parse(SourceLibrary.java:209)
at
com.thoughtworks.qdox.library.SourceLibrary.addSource(SourceLibrary.java:157)
at
com.thoughtworks.qdox.library.SortedClassLibraryBuilder.addSource(SortedClassLibraryBuilder.java:173)
at
com.thoughtworks.qdox.JavaProjectBuilder.addSource(JavaProjectBuilder.java:151)
at
com.thoughtworks.qdox.JavaProjectBuilder$2.visitFile(JavaProjectBuilder.java:223)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:103)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:81)
at
com.thoughtworks.qdox.JavaProjectBuilder.addSourceTree(JavaProjectBuilder.java:217)
at
com.thoughtworks.qdox.JavaProjectBuilder.addSourceTree(JavaProjectBuilder.java:204)
at
org.apache.maven.tools.plugin.extractor.javadoc.JavaJavadocMojoDescriptorExtractor.discoverClasses(JavaJavadocMojoDescriptorExtractor.java:625)
at
org.apache.maven.tools.plugin.extractor.javadoc.JavaJavadocMojoDescriptorExtractor.execute(JavaJavadocMojoDescriptorExtractor.java:573)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:96)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:283)
at
org.apache.maven.plugin.plugin.HelpGeneratorMojo.execute(HelpGeneratorMojo.java:92)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MPLUGIN-320) JavaJavadocMojoDescriptorExtractor fails with Java 8 lambdas.
[
https://issues.apache.org/jira/browse/MPLUGIN-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antony Riley updated MPLUGIN-320:
-
Description:
JavaJavadocMojoDescriptorExtractor fails to parse the following source:
{code:java}
package com.example.plugin;
import com.amazonaws.AmazonWebServiceClient;
import com.amazonaws.services.ecr.AmazonECRClient;
import com.amazonaws.services.ecs.AmazonECSClient;
import java.util.function.Supplier;
public enum AmazonClients {
ECS(AmazonECSClient::new),
ECR(AmazonECRClient::new);
private final Supplier supplier;
AmazonClients(Supplier supplier) {
this.supplier = new SingletonSupplier(supplier);
}
public T get() {
return (T) supplier.get();
}
private static class SingletonSupplier implements Supplier {
private final Supplier realSupplier;
private T instance;
private SingletonSupplier(Supplier realSupplier) {
this.realSupplier = realSupplier;
}
@Override
public synchronized T get() {
return instance == null ? instance = realSupplier.get() : instance;
}
}
}
{code}
It fails on the lamdas in the constructors, this causes
maven-plugin-plugin:helpmojo to fail with the following exception:
{noformat}
Caused by: com.thoughtworks.qdox.parser.ParseException: syntax error @[10,24]
in
file:/home/antony/work/example/src/main/java/com/example/plugin/AmazonClients.java
at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:1739)
at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:1861)
at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:1720)
at
com.thoughtworks.qdox.library.SourceLibrary.parse(SourceLibrary.java:232)
at
com.thoughtworks.qdox.library.SourceLibrary.parse(SourceLibrary.java:209)
at
com.thoughtworks.qdox.library.SourceLibrary.addSource(SourceLibrary.java:157)
at
com.thoughtworks.qdox.library.SortedClassLibraryBuilder.addSource(SortedClassLibraryBuilder.java:173)
at
com.thoughtworks.qdox.JavaProjectBuilder.addSource(JavaProjectBuilder.java:151)
at
com.thoughtworks.qdox.JavaProjectBuilder$2.visitFile(JavaProjectBuilder.java:223)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:103)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:81)
at
com.thoughtworks.qdox.JavaProjectBuilder.addSourceTree(JavaProjectBuilder.java:217)
at
com.thoughtworks.qdox.JavaProjectBuilder.addSourceTree(JavaProjectBuilder.java:204)
at
org.apache.maven.tools.plugin.extractor.javadoc.JavaJavadocMojoDescriptorExtractor.discoverClasses(JavaJavadocMojoDescriptorExtractor.java:625)
at
org.apache.maven.tools.plugin.extractor.javadoc.JavaJavadocMojoDescriptorExtractor.execute(JavaJavadocMojoDescriptorExtractor.java:573)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:96)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:283)
at
org.apache.maven.plugin.plugin.HelpGeneratorMojo.execute(HelpGeneratorMojo.java:92)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
{noformat}
was:
JavaJavadocMojoDescriptorExtractor fails to parse the following source:
{code:java}
package com.example.plugin;
import com.amazonaws.AmazonWebServiceClient;
import com.amazonaws.services.ecr.AmazonECRClient;
import com.amazonaws.services.ecs.AmazonECSClient;
import java.util.function.Supplier;
public enum AmazonClients {
ECS(AmazonECSClient::new),
ECR(AmazonECRClient::new);
private final Supplier supplier;
AmazonClients(Supplier supplier) {
this.supplier = new SingletonSupplier(supplier);
}
public T get() {
return (T) supplier.get();
}
private static class SingletonSupplier implements Supplier {
private final Supplier realSupplier;
private T instance;
private SingletonSupplier(Supplier realSupplier) {
this.realSupplier = realSupplier;
}
@Override
public synchronized T get() {
return instance == null ? instance = realSupplier.get() : instance;
}
}
}
{code}
It fail
[jira] [Created] (SCM-839) scm:diff with GIT doesn't work
Jacek Gebal created SCM-839: --- Summary: scm:diff with GIT doesn't work Key: SCM-839 URL: https://issues.apache.org/jira/browse/SCM-839 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-gitexe Affects Versions: 1.9.5 Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00) Maven home: C:\Users\a565281\apache-maven-3.3.9\bin\.. Java version: 1.8.0_92, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.8.0_92\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" Reporter: Jacek Gebal When executing the maven command as below, I get an exception. mvn scm:diff -DstartScmVersion=master -DstartScmVersionType=branch -DendScmVersion=HEAD -DendScmVersionType=branch Also the examples in documentation for mvn:diff do not seem to be OK: https://maven.apache.org/components/scm/maven-scm-plugin/examples/scm-advance-features.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SCM-839) scm:diff with GIT doesn't work
[ https://issues.apache.org/jira/browse/SCM-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766729#comment-15766729 ] Jacek Gebal commented on SCM-839: - Here is the debug log from executing the command: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00) Maven home: C:\Users\a565281\apache-maven-3.3.9\bin\.. Java version: 1.8.0_92, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.8.0_92\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" [DEBUG] Created new class realm maven.api [DEBUG] Importing foreign packages into class realm maven.api [DEBUG] Imported: javax.enterprise.inject.* < plexus.core [DEBUG] Imported: javax.enterprise.util.* < plexus.core [DEBUG] Imported: javax.inject.* < plexus.core [DEBUG] Imported: org.apache.maven.* < plexus.core [DEBUG] Imported: org.apache.maven.artifact < plexus.core [DEBUG] Imported: org.apache.maven.classrealm < plexus.core [DEBUG] Imported: org.apache.maven.cli < plexus.core [DEBUG] Imported: org.apache.maven.configuration < plexus.core [DEBUG] Imported: org.apache.maven.exception < plexus.core [DEBUG] Imported: org.apache.maven.execution < plexus.core [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core [DEBUG] Imported: org.apache.maven.model < plexus.core [DEBUG] Imported: org.apache.maven.monitor < plexus.core [DEBUG] Imported: org.apache.maven.plugin < plexus.core [DEBUG] Imported: org.apache.maven.profiles < plexus.core [DEBUG] Imported: org.apache.maven.project < plexus.core [DEBUG] Imported: org.apache.maven.reporting < plexus.core [DEBUG] Imported: org.apache.maven.repository < plexus.core [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core [DEBUG] Imported: org.apache.maven.settings < plexus.core [DEBUG] Imported: org.apache.maven.toolchain < plexus.core [DEBUG] Imported: org.apache.maven.usability < plexus.core [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core [DEBUG] Imported: org.codehaus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.* < plexus.core [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.component < plexus.core [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core [DEBUG] Imported: org.codehaus.plexus.container < plexus.core [DEBUG] Imported: org.codehaus.plexus.context < plexus.core [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core [DEBUG] Imported: org.eclipse.aether.* < plexus.core [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core [DEBUG] Imported: org.eclipse.aether.collection < plexus.core [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core [DEBUG] Imported: org.eclipse.aether.graph < plexus.core [DEBUG] Imported: org.eclipse.aether.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.installation < plexus.core [DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.metadata < plexus.core [DEBUG] Imported: org.eclipse.aether.repository < plexus.core [DEBUG] Imported: org.eclipse.aether.resolution < plexus.core [DEBUG] Imported: org.eclipse.aether.spi < plexus.core [DEBUG] Imported: org.eclipse.aether.transfer < plexus.core [DEBUG] Imported: org.eclipse.aether.version < plexus.core [DEBUG] Imported: org.slf4j.* < plexus.core [DEBUG] Imported: org.slf4j.helpers.* < plexus.core [DEBUG] Imported: org.slf4j.spi.* < plexus.core [DEBUG] Populating class realm maven.api [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from C:\Users\a565281\apache-maven-3.3.9\bin\..\conf\settings.xml [DEBUG] Reading user settings from C:\Users\a565281\.m2\settings.xml [DEBUG] Reading global toolchains from C:\Users\a565281\apache-maven-3.3.9\bin\..\conf\toolchains.xml [DEBUG] Reading us
[jira] [Issue Comment Deleted] (SCM-839) scm:diff with GIT doesn't work
[ https://issues.apache.org/jira/browse/SCM-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacek Gebal updated SCM-839: Comment: was deleted (was: Here is the debug log from executing the command: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00) Maven home: C:\Users\a565281\apache-maven-3.3.9\bin\.. Java version: 1.8.0_92, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.8.0_92\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" [DEBUG] Created new class realm maven.api [DEBUG] Importing foreign packages into class realm maven.api [DEBUG] Imported: javax.enterprise.inject.* < plexus.core [DEBUG] Imported: javax.enterprise.util.* < plexus.core [DEBUG] Imported: javax.inject.* < plexus.core [DEBUG] Imported: org.apache.maven.* < plexus.core [DEBUG] Imported: org.apache.maven.artifact < plexus.core [DEBUG] Imported: org.apache.maven.classrealm < plexus.core [DEBUG] Imported: org.apache.maven.cli < plexus.core [DEBUG] Imported: org.apache.maven.configuration < plexus.core [DEBUG] Imported: org.apache.maven.exception < plexus.core [DEBUG] Imported: org.apache.maven.execution < plexus.core [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core [DEBUG] Imported: org.apache.maven.model < plexus.core [DEBUG] Imported: org.apache.maven.monitor < plexus.core [DEBUG] Imported: org.apache.maven.plugin < plexus.core [DEBUG] Imported: org.apache.maven.profiles < plexus.core [DEBUG] Imported: org.apache.maven.project < plexus.core [DEBUG] Imported: org.apache.maven.reporting < plexus.core [DEBUG] Imported: org.apache.maven.repository < plexus.core [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core [DEBUG] Imported: org.apache.maven.settings < plexus.core [DEBUG] Imported: org.apache.maven.toolchain < plexus.core [DEBUG] Imported: org.apache.maven.usability < plexus.core [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core [DEBUG] Imported: org.codehaus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.* < plexus.core [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.component < plexus.core [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core [DEBUG] Imported: org.codehaus.plexus.container < plexus.core [DEBUG] Imported: org.codehaus.plexus.context < plexus.core [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core [DEBUG] Imported: org.eclipse.aether.* < plexus.core [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core [DEBUG] Imported: org.eclipse.aether.collection < plexus.core [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core [DEBUG] Imported: org.eclipse.aether.graph < plexus.core [DEBUG] Imported: org.eclipse.aether.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.installation < plexus.core [DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.metadata < plexus.core [DEBUG] Imported: org.eclipse.aether.repository < plexus.core [DEBUG] Imported: org.eclipse.aether.resolution < plexus.core [DEBUG] Imported: org.eclipse.aether.spi < plexus.core [DEBUG] Imported: org.eclipse.aether.transfer < plexus.core [DEBUG] Imported: org.eclipse.aether.version < plexus.core [DEBUG] Imported: org.slf4j.* < plexus.core [DEBUG] Imported: org.slf4j.helpers.* < plexus.core [DEBUG] Imported: org.slf4j.spi.* < plexus.core [DEBUG] Populating class realm maven.api [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from C:\Users\a565281\apache-maven-3.3.9\bin\..\conf\settings.xml [DEBUG] Reading user settings from C:\Users\a565281\.m2\settings.xml [DEBUG] Reading global toolchains from C:\Users\a565281\apache-maven-3.3.9\bin\..\conf\toolchains.xml [DEBUG] Reading user toolchains from C:\User
[jira] [Commented] (SCM-839) scm:diff with GIT doesn't work
[ https://issues.apache.org/jira/browse/SCM-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766750#comment-15766750 ] Jacek Gebal commented on SCM-839: - Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00) Maven home: C:\Users\a565281\apache-maven-3.3.9\bin\.. Java version: 1.8.0_92, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.8.0_92\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" [DEBUG] Created new class realm maven.api [DEBUG] Importing foreign packages into class realm maven.api [DEBUG] Imported: javax.enterprise.inject.* < plexus.core [DEBUG] Imported: javax.enterprise.util.* < plexus.core [DEBUG] Imported: javax.inject.* < plexus.core [DEBUG] Imported: org.apache.maven.* < plexus.core [DEBUG] Imported: org.apache.maven.artifact < plexus.core [DEBUG] Imported: org.apache.maven.classrealm < plexus.core [DEBUG] Imported: org.apache.maven.cli < plexus.core [DEBUG] Imported: org.apache.maven.configuration < plexus.core [DEBUG] Imported: org.apache.maven.exception < plexus.core [DEBUG] Imported: org.apache.maven.execution < plexus.core [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core [DEBUG] Imported: org.apache.maven.model < plexus.core [DEBUG] Imported: org.apache.maven.monitor < plexus.core [DEBUG] Imported: org.apache.maven.plugin < plexus.core [DEBUG] Imported: org.apache.maven.profiles < plexus.core [DEBUG] Imported: org.apache.maven.project < plexus.core [DEBUG] Imported: org.apache.maven.reporting < plexus.core [DEBUG] Imported: org.apache.maven.repository < plexus.core [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core [DEBUG] Imported: org.apache.maven.settings < plexus.core [DEBUG] Imported: org.apache.maven.toolchain < plexus.core [DEBUG] Imported: org.apache.maven.usability < plexus.core [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core [DEBUG] Imported: org.codehaus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.* < plexus.core [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.component < plexus.core [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core [DEBUG] Imported: org.codehaus.plexus.container < plexus.core [DEBUG] Imported: org.codehaus.plexus.context < plexus.core [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core [DEBUG] Imported: org.eclipse.aether.* < plexus.core [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core [DEBUG] Imported: org.eclipse.aether.collection < plexus.core [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core [DEBUG] Imported: org.eclipse.aether.graph < plexus.core [DEBUG] Imported: org.eclipse.aether.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.installation < plexus.core [DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.metadata < plexus.core [DEBUG] Imported: org.eclipse.aether.repository < plexus.core [DEBUG] Imported: org.eclipse.aether.resolution < plexus.core [DEBUG] Imported: org.eclipse.aether.spi < plexus.core [DEBUG] Imported: org.eclipse.aether.transfer < plexus.core [DEBUG] Imported: org.eclipse.aether.version < plexus.core [DEBUG] Imported: org.slf4j.* < plexus.core [DEBUG] Imported: org.slf4j.helpers.* < plexus.core [DEBUG] Imported: org.slf4j.spi.* < plexus.core [DEBUG] Populating class realm maven.api [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from C:\Users\a565281\apache-maven-3.3.9\bin\..\conf\settings.xml [DEBUG] Reading user settings from C:\Users\a565281\.m2\settings.xml [DEBUG] Reading global toolchains from C:\Users\a565281\apache-maven-3.3.9\bin\..\conf\toolchains.xml [DEBUG] Reading user toolchains from C:\Users\a565281\.m2\toolchains
[jira] [Commented] (SCM-839) scm:diff with GIT doesn't work
[ https://issues.apache.org/jira/browse/SCM-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766754#comment-15766754 ] Jacek Gebal commented on SCM-839: - What I've figured so far, is that the command `git diff --cache ` accepts only one branch/version paramete. The plugin however is passing both start and end version to that command. This makes the command fail. > scm:diff with GIT doesn't work > -- > > Key: SCM-839 > URL: https://issues.apache.org/jira/browse/SCM-839 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-gitexe >Affects Versions: 1.9.5 > Environment: Apache Maven 3.3.9 > (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00) > Maven home: C:\Users\a565281\apache-maven-3.3.9\bin\.. > Java version: 1.8.0_92, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.8.0_92\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" >Reporter: Jacek Gebal > > When executing the maven command as below, I get an exception. > mvn scm:diff -DstartScmVersion=master -DstartScmVersionType=branch > -DendScmVersion=HEAD -DendScmVersionType=branch > Also the examples in documentation for mvn:diff do not seem to be OK: > https://maven.apache.org/components/scm/maven-scm-plugin/examples/scm-advance-features.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRESOURCES-210) copy-resources erases file permissions
[ https://issues.apache.org/jira/browse/MRESOURCES-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766989#comment-15766989 ] Tommy Becker commented on MRESOURCES-210: - Not always, no. In particular where we are executing scripts that run during the build, e.g. to help with integration tests. I would hope that in almost-2017 Java 7 is not an onerous requirement. > copy-resources erases file permissions > -- > > Key: MRESOURCES-210 > URL: https://issues.apache.org/jira/browse/MRESOURCES-210 > Project: Maven Resources Plugin > Issue Type: Bug >Reporter: Volodymyr Kyrychenko > Fix For: waiting-for-feedback > > > rwx posix permission should be kept. There is possibility to do that now: > java.nio.file.Files.setPosixFilePermissions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-6023) Upgrade of slf4j-simple to a version later than 1.7.16 blocked by upstream issue.
[
https://issues.apache.org/jira/browse/MNG-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MNG-6023:
---
Fix Version/s: (was: 3.4.0)
> Upgrade of slf4j-simple to a version later than 1.7.16 blocked by upstream
> issue.
> -
>
> Key: MNG-6023
> URL: https://issues.apache.org/jira/browse/MNG-6023
> Project: Maven
> Issue Type: Bug
> Components: Command Line, Logging
>Reporter: Michael Osipov
>Assignee: Christian Schulte
>Priority: Blocker
>
> In
> [ce580ea2fafd7638ee56e1d0574de95a37164322|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=ce580ea2fafd7638ee56e1d0574de95a37164322]
> SLF4J was updated from 1.7.16 to 1.7.21. Use a snapshot of that commit and
> run {{mvn -X}} and see that no debug output is printed. Something is either
> broken in our code now or in SLF4J Simple.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-6023) Upgrade of slf4j-simple to a version later than 1.7.16 blocked by upstream issue.
[
https://issues.apache.org/jira/browse/MNG-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MNG-6023:
---
Affects Version/s: (was: 3.4.0)
> Upgrade of slf4j-simple to a version later than 1.7.16 blocked by upstream
> issue.
> -
>
> Key: MNG-6023
> URL: https://issues.apache.org/jira/browse/MNG-6023
> Project: Maven
> Issue Type: Bug
> Components: Command Line, Logging
>Reporter: Michael Osipov
>Assignee: Christian Schulte
>Priority: Blocker
>
> In
> [ce580ea2fafd7638ee56e1d0574de95a37164322|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=ce580ea2fafd7638ee56e1d0574de95a37164322]
> SLF4J was updated from 1.7.16 to 1.7.21. Use a snapshot of that commit and
> run {{mvn -X}} and see that no debug output is printed. Something is either
> broken in our code now or in SLF4J Simple.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (MNG-6023) Upgrade of slf4j-simple to a version later than 1.7.16 blocked by upstream issue.
[
https://issues.apache.org/jira/browse/MNG-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte reopened MNG-6023:
> Upgrade of slf4j-simple to a version later than 1.7.16 blocked by upstream
> issue.
> -
>
> Key: MNG-6023
> URL: https://issues.apache.org/jira/browse/MNG-6023
> Project: Maven
> Issue Type: Bug
> Components: Command Line, Logging
>Reporter: Michael Osipov
>Assignee: Christian Schulte
>Priority: Blocker
>
> In
> [ce580ea2fafd7638ee56e1d0574de95a37164322|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=ce580ea2fafd7638ee56e1d0574de95a37164322]
> SLF4J was updated from 1.7.16 to 1.7.21. Use a snapshot of that commit and
> run {{mvn -X}} and see that no debug output is printed. Something is either
> broken in our code now or in SLF4J Simple.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MNG-6023) Upgrade of slf4j-simple to a version later than 1.7.16 blocked by upstream issue.
[
https://issues.apache.org/jira/browse/MNG-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte closed MNG-6023.
--
Resolution: Done
Closing this "Done" and removing the versions. We do not need this issue to
appear in any release notes. It got created and fixed during development of the
release. Issue will never appear to users.
> Upgrade of slf4j-simple to a version later than 1.7.16 blocked by upstream
> issue.
> -
>
> Key: MNG-6023
> URL: https://issues.apache.org/jira/browse/MNG-6023
> Project: Maven
> Issue Type: Bug
> Components: Command Line, Logging
>Reporter: Michael Osipov
>Assignee: Christian Schulte
>Priority: Blocker
>
> In
> [ce580ea2fafd7638ee56e1d0574de95a37164322|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=ce580ea2fafd7638ee56e1d0574de95a37164322]
> SLF4J was updated from 1.7.16 to 1.7.21. Use a snapshot of that commit and
> run {{mvn -X}} and see that no debug output is printed. Something is either
> broken in our code now or in SLF4J Simple.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6041) Option -l does not disable colorized output
[ https://issues.apache.org/jira/browse/MNG-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767255#comment-15767255 ] Christian Schulte commented on MNG-6041: Do we really want this issue to appear in the release notes? It got created and fixed during development of the release. It will never appear to users. > Option -l does not disable colorized output > --- > > Key: MNG-6041 > URL: https://issues.apache.org/jira/browse/MNG-6041 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.4.0 >Reporter: Karl Heinz Marbaise >Assignee: Robert Scholte >Priority: Minor > Fix For: 3.4.0 > > > Therefore the generated log file also contains escape sequences. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6043) Colorization is disabled too late in batch mode
[ https://issues.apache.org/jira/browse/MNG-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767257#comment-15767257 ] Christian Schulte commented on MNG-6043: Do we really want this issue to appear in the release notes? It got created and fixed during development of the release. It will never appear to users. > Colorization is disabled too late in batch mode > --- > > Key: MNG-6043 > URL: https://issues.apache.org/jira/browse/MNG-6043 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.4.0 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.4.0 > > > See > [discussion|https://mail-archives.apache.org/mod_mbox/maven-dev/201606.mbox/%3Cc3b896b1-db25-9861-6fc0-a1e25afad710%40apache.org%3E]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-6139) Addition of command line option 'legacy-dependency-management'.
[ https://issues.apache.org/jira/browse/MNG-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MNG-6139. -- Resolution: Fixed Fix Version/s: 3.4.0 > Addition of command line option 'legacy-dependency-management'. > --- > > Key: MNG-6139 > URL: https://issues.apache.org/jira/browse/MNG-6139 > Project: Maven > Issue Type: New Feature >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > See the issues this issue is linked to. The command line option will simply > allow users to disable the bugfixes and get the former incorrect behaviour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNG-6139) Addition of command line option 'legacy-dependency-management'.
Christian Schulte created MNG-6139: -- Summary: Addition of command line option 'legacy-dependency-management'. Key: MNG-6139 URL: https://issues.apache.org/jira/browse/MNG-6139 Project: Maven Issue Type: New Feature Reporter: Christian Schulte Assignee: Christian Schulte Priority: Critical See the issues this issue is linked to. The command line option will simply allow users to disable the bugfixes and get the former incorrect behaviour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRESOLVER-9) DefaultDependencyCollector does not correctly handle dependency management.
[ https://issues.apache.org/jira/browse/MRESOLVER-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767544#comment-15767544 ] Hudson commented on MRESOLVER-9: SUCCESS: Integrated in Jenkins build maven-resolver #31 (See [https://builds.apache.org/job/maven-resolver/31/]) [MRESOLVER-9] DefaultDependencyCollector does not correctly handle (schulte: rev 763cac233d37e2240e43dfaf72023ba1f8ffd139) * (edit) maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/DefaultDependencyCollector.java > DefaultDependencyCollector does not correctly handle dependency management. > --- > > Key: MRESOLVER-9 > URL: https://issues.apache.org/jira/browse/MRESOLVER-9 > Project: Maven Resolver > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: Maven Artifact Resolver 1.2.0 > > > During dependency processing the 'DependencySelector' is called to decide if > a dependency is to be selected. The call to > 'DependencySelector.selectDependency( dependency )' is performed with the > unmanagement dependency but needs to be performed with the managed > dependency. With the fix applied, the result no longer contains dependencies > whose scope or optionality has been managed to not be part of the result > (correct behaviour). Without the fix applied, the result contains > dependencies with a managed scope or optionality not filtered out by the > 'DependencySelector' in use (incorrect behaviour). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6139) Addition of command line option 'legacy-dependency-management'.
[ https://issues.apache.org/jira/browse/MNG-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767556#comment-15767556 ] Hudson commented on MNG-6139: - SUCCESS: Integrated in Jenkins build maven-3.x #1470 (See [https://builds.apache.org/job/maven-3.x/1470/]) [MNG-6139] Addition of command line option (schulte: rev 7e70c59e43f112c12282de49d937e870c9545fc9) * (edit) maven-core/src/main/java/org/apache/maven/execution/MavenExecutionRequest.java * (edit) maven-model-builder/src/main/java/org/apache/maven/model/building/DefaultModelBuildingRequest.java * (edit) maven-core/src/main/java/org/apache/maven/DefaultMaven.java * (edit) maven-core/src/main/java/org/apache/maven/execution/DefaultMavenExecutionRequest.java * (edit) maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java * (edit) maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java * (edit) maven-model-builder/src/main/java/org/apache/maven/model/management/DefaultDependencyManagementInjector.java * (edit) maven-core/src/main/java/org/apache/maven/RepositoryUtils.java * (edit) maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java * (edit) maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuildingRequest.java * (edit) maven-model-builder/src/main/java/org/apache/maven/model/building/ModelBuildingRequest.java * (edit) maven-model-builder/src/main/java/org/apache/maven/model/building/FilterModelBuildingRequest.java * (edit) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/ArtifactDescriptorReaderDelegate.java * (edit) maven-core/src/main/java/org/apache/maven/project/ProjectBuildingRequest.java * (edit) maven-embedder/src/main/java/org/apache/maven/cli/CLIManager.java > Addition of command line option 'legacy-dependency-management'. > --- > > Key: MNG-6139 > URL: https://issues.apache.org/jira/browse/MNG-6139 > Project: Maven > Issue Type: New Feature >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > See the issues this issue is linked to. The command line option will simply > allow users to disable the bugfixes and get the former incorrect behaviour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6139) Addition of command line option 'legacy-dependency-management'.
[ https://issues.apache.org/jira/browse/MNG-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767601#comment-15767601 ] Hudson commented on MNG-6139: - SUCCESS: Integrated in Jenkins build maven-3.x #1472 (See [https://builds.apache.org/job/maven-3.x/1472/]) [MNG-6139] Addition of command line option (schulte: rev bb8a797c5bef4629c4c9127b1a6d94724b6cc430) * (edit) maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java > Addition of command line option 'legacy-dependency-management'. > --- > > Key: MNG-6139 > URL: https://issues.apache.org/jira/browse/MNG-6139 > Project: Maven > Issue Type: New Feature >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > See the issues this issue is linked to. The command line option will simply > allow users to disable the bugfixes and get the former incorrect behaviour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6049) Add behavior to filter resolved version ranges of an artifact
[
https://issues.apache.org/jira/browse/MNG-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767629#comment-15767629
]
Michael Osipov commented on MNG-6049:
-
I think, I had a chat once with [~hboutemy] about this and the upshot is that
SNAPSHOT is in constant flux.
> Add behavior to filter resolved version ranges of an artifact
> -
>
> Key: MNG-6049
> URL: https://issues.apache.org/jira/browse/MNG-6049
> Project: Maven
> Issue Type: Improvement
> Components: core, Dependencies
>Reporter: Uwe Barthel
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: 3.4.0
>
>
> The discussion on issue MNG-3092 shows the seriously needs of different kinds
> of version range resolving in Maven.
> This solution provides a hook for Maven extensions/plugins to change the list
> of resolved version range results as required.
> The {{DefaultVersionRangeResolver}} will be extended with a filter for
> version range results. A new interface {{VersionRangeResultFilter}} is added
> and a non-filtering {{DefaultVersionRangeResultFilter}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6043) Colorization is disabled too late in batch mode
[ https://issues.apache.org/jira/browse/MNG-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767646#comment-15767646 ] Michael Osipov commented on MNG-6043: - This is hard to argue, you will already find pros and cons. Basically, unreleased versions should not appear in "Affected Version/s". Take it as in-version regression. I do really prefer to work ticket-based, this is a comfortable and transparent process for everyone. > Colorization is disabled too late in batch mode > --- > > Key: MNG-6043 > URL: https://issues.apache.org/jira/browse/MNG-6043 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.4.0 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.4.0 > > > See > [discussion|https://mail-archives.apache.org/mod_mbox/maven-dev/201606.mbox/%3Cc3b896b1-db25-9861-6fc0-a1e25afad710%40apache.org%3E]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MNG-6043) Colorization is disabled too late in batch mode
[ https://issues.apache.org/jira/browse/MNG-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767646#comment-15767646 ] Michael Osipov edited comment on MNG-6043 at 12/21/16 6:23 PM: --- This is hard to argue, you will always find pros and cons. Basically, unreleased versions should not appear in "Affected Version/s". Take it as in-version regression. I do really prefer to work ticket-based, this is a comfortable and transparent process for everyone. was (Author: michael-o): This is hard to argue, you will already find pros and cons. Basically, unreleased versions should not appear in "Affected Version/s". Take it as in-version regression. I do really prefer to work ticket-based, this is a comfortable and transparent process for everyone. > Colorization is disabled too late in batch mode > --- > > Key: MNG-6043 > URL: https://issues.apache.org/jira/browse/MNG-6043 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.4.0 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.4.0 > > > See > [discussion|https://mail-archives.apache.org/mod_mbox/maven-dev/201606.mbox/%3Cc3b896b1-db25-9861-6fc0-a1e25afad710%40apache.org%3E]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6043) Colorization is disabled too late in batch mode
[ https://issues.apache.org/jira/browse/MNG-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767772#comment-15767772 ] Christian Schulte commented on MNG-6043: I just asked to not having to change the release notes. The list of issues for 3.4 is likely to change soon. I don't know. So be it. > Colorization is disabled too late in batch mode > --- > > Key: MNG-6043 > URL: https://issues.apache.org/jira/browse/MNG-6043 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.4.0 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.4.0 > > > See > [discussion|https://mail-archives.apache.org/mod_mbox/maven-dev/201606.mbox/%3Cc3b896b1-db25-9861-6fc0-a1e25afad710%40apache.org%3E]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6084) Support JSR250 annotations
[ https://issues.apache.org/jira/browse/MNG-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767958#comment-15767958 ] ASF GitHub Bot commented on MNG-6084: - Github user michael-o commented on the issue: https://github.com/apache/maven-integration-testing/pull/15 @dantran Can you squash? I will have a look and will merge soon. > Support JSR250 annotations > -- > > Key: MNG-6084 > URL: https://issues.apache.org/jira/browse/MNG-6084 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.3.9 >Reporter: Dan Tran >Assignee: Dan Tran > Fix For: 3.4.0 > > > JSR330 ( @Named, @Singeton, etc) currently supported for plugin development. > Would like to see JSR250 as well(@PostConstruct, etc) > Detail discussion is at > http://maven.40175.n5.nabble.com/Maven-Plugin-and-JSR330-td5879508.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPLUGIN-320) JavaJavadocMojoDescriptorExtractor fails with Java 8 lambdas.
[
https://issues.apache.org/jira/browse/MPLUGIN-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767988#comment-15767988
]
Guillaume Boué commented on MPLUGIN-320:
This is an issue with the downstream qdox library that the plugin is using. I
created an issue https://github.com/paul-hammant/qdox/issues/15 to track this.
> JavaJavadocMojoDescriptorExtractor fails with Java 8 lambdas.
> -
>
> Key: MPLUGIN-320
> URL: https://issues.apache.org/jira/browse/MPLUGIN-320
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: maven-plugin-tools-java
>Affects Versions: 3.5
>Reporter: Antony Riley
>Priority: Minor
>
> JavaJavadocMojoDescriptorExtractor fails to parse the following source:
> {code:java}
> package com.example.plugin;
> import com.amazonaws.AmazonWebServiceClient;
> import com.amazonaws.services.ecr.AmazonECRClient;
> import com.amazonaws.services.ecs.AmazonECSClient;
> import java.util.function.Supplier;
> public enum AmazonClients {
> ECS(AmazonECSClient::new),
> ECR(AmazonECRClient::new);
> private final Supplier supplier;
> AmazonClients(Supplier supplier) {
> this.supplier = new SingletonSupplier(supplier);
> }
> public T get() {
> return (T) supplier.get();
> }
> private static class SingletonSupplier implements Supplier {
> private final Supplier realSupplier;
> private T instance;
> private SingletonSupplier(Supplier realSupplier) {
> this.realSupplier = realSupplier;
> }
> @Override
> public synchronized T get() {
> return instance == null ? instance = realSupplier.get() :
> instance;
> }
> }
> }
> {code}
> It fails on the lamdas in the constructors, this causes
> maven-plugin-plugin:helpmojo to fail with the following exception:
> {noformat}
> Caused by: com.thoughtworks.qdox.parser.ParseException: syntax error @[10,24]
> in
> file:/home/antony/work/example/src/main/java/com/example/plugin/AmazonClients.java
> at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:1739)
> at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:1861)
> at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:1720)
> at
> com.thoughtworks.qdox.library.SourceLibrary.parse(SourceLibrary.java:232)
> at
> com.thoughtworks.qdox.library.SourceLibrary.parse(SourceLibrary.java:209)
> at
> com.thoughtworks.qdox.library.SourceLibrary.addSource(SourceLibrary.java:157)
> at
> com.thoughtworks.qdox.library.SortedClassLibraryBuilder.addSource(SortedClassLibraryBuilder.java:173)
> at
> com.thoughtworks.qdox.JavaProjectBuilder.addSource(JavaProjectBuilder.java:151)
> at
> com.thoughtworks.qdox.JavaProjectBuilder$2.visitFile(JavaProjectBuilder.java:223)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:103)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:91)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:81)
> at
> com.thoughtworks.qdox.JavaProjectBuilder.addSourceTree(JavaProjectBuilder.java:217)
> at
> com.thoughtworks.qdox.JavaProjectBuilder.addSourceTree(JavaProjectBuilder.java:204)
> at
> org.apache.maven.tools.plugin.extractor.javadoc.JavaJavadocMojoDescriptorExtractor.discoverClasses(JavaJavadocMojoDescriptorExtractor.java:625)
> at
> org.apache.maven.tools.plugin.extractor.javadoc.JavaJavadocMojoDescriptorExtractor.execute(JavaJavadocMojoDescriptorExtractor.java:573)
> at
> org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:96)
> at
> org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:283)
> at
> org.apache.maven.plugin.plugin.HelpGeneratorMojo.execute(HelpGeneratorMojo.java:92)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6084) Support JSR250 annotations
[ https://issues.apache.org/jira/browse/MNG-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768073#comment-15768073 ] ASF GitHub Bot commented on MNG-6084: - Github user dantran closed the pull request at: https://github.com/apache/maven-integration-testing/pull/15 > Support JSR250 annotations > -- > > Key: MNG-6084 > URL: https://issues.apache.org/jira/browse/MNG-6084 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.3.9 >Reporter: Dan Tran >Assignee: Dan Tran > Fix For: 3.4.0 > > > JSR330 ( @Named, @Singeton, etc) currently supported for plugin development. > Would like to see JSR250 as well(@PostConstruct, etc) > Detail discussion is at > http://maven.40175.n5.nabble.com/Maven-Plugin-and-JSR330-td5879508.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6084) Support JSR250 annotations
[ https://issues.apache.org/jira/browse/MNG-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768072#comment-15768072 ] ASF GitHub Bot commented on MNG-6084: - Github user dantran commented on the issue: https://github.com/apache/maven-integration-testing/pull/15 already merged > Support JSR250 annotations > -- > > Key: MNG-6084 > URL: https://issues.apache.org/jira/browse/MNG-6084 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.3.9 >Reporter: Dan Tran >Assignee: Dan Tran > Fix For: 3.4.0 > > > JSR330 ( @Named, @Singeton, etc) currently supported for plugin development. > Would like to see JSR250 as well(@PostConstruct, etc) > Detail discussion is at > http://maven.40175.n5.nabble.com/Maven-Plugin-and-JSR330-td5879508.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
