[jira] [Commented] (MCHANGES-357) Cannot include Unresolved issues
[ https://issues.apache.org/jira/browse/MCHANGES-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14614910#comment-14614910 ] Michael Osipov commented on MCHANGES-357: - Without looking at the bug itself, why do you want that? Releases include complete issue only. Cannot include Unresolved issues Key: MCHANGES-357 URL: https://issues.apache.org/jira/browse/MCHANGES-357 Project: Maven Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.11 Environment: Jira 5.2.11 Reporter: Franck Malartic Using the jira-report goal, it is impossible to get Unresolved issues. Unresolved is not managed by Jira server like other resolution statuses. The REST API does not return the Unresolved status thus the plugin throws the following exception: org.apache.maven.plugin.MojoFailureException: Could not find resolution Unresolved. at org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:265) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:246) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:212) at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:131) at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:372) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:210) at org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:207) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) at org.codehaus.classworlds.Launcher.main(Launcher.java:46) Note that you won't have the same error with the https://issues.apache.org/jira/ server, because the Unresolved status is redefined (id 9) https://issues.apache.org/jira/rest/api/2/resolution/ This is explicitly not recommended in Jira documentation: https://confluence.atlassian.com/display/JIRA/Defining+Resolution+Field+Values The redefinition of Unresolved shall lead to incorrect Jira status report. JQL with id=Unresolved is correct: https://issues.apache.org/jira/browse/MCHANGES-240?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC but with id=9 it is not (result is empty): https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%209%20ORDER%20BY%20priority%20DESC And in that case, setting configuration resolutionIds to Unresolved will lead to the second sample query. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPIR-251) Artifact ###### has no file error regression.
[ https://issues.apache.org/jira/browse/MPIR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14614962#comment-14614962 ] Jędrzej Dąbrowa commented on MPIR-251: -- Just got the same error: [INFO] Generating Dependencies report --- maven-project-info-reports-plugin:2.7:dependencies [ERROR] Artifact: com.rsa:kmsclient:jar:2.1.3.2 has no file. [ERROR] Artifact: // bunch of artifacts from our company's Nexus repository [ERROR] Artifact: com.tibco:tibjms:jar:4.4.3 has no file. [ERROR] Artifact: commons-codec:commons-codec:jar:1.6 has no file. [ERROR] Artifact: commons-io:commons-io:jar:2.4 has no file. [ERROR] Artifact: commons-logging:commons-logging:jar:1.1 has no file. [ERROR] Artifact: concurrent:concurrent:jar:1.3.2 has no file. [ERROR] Artifact: dom4j:dom4j:jar:1.6.1 has no file. [ERROR] Artifact: javax.jms:jms:jar:1.1 has no file. [ERROR] Artifact: javax.resource:connector:jar:1.0 has no file. [ERROR] Artifact: javax.transaction:jta:jar:1.1 has no file. [ERROR] Artifact: junit:junit:jar:4.12 has no file. [ERROR] Artifact: log4j:log4j:jar:1.2.17 has no file. [ERROR] Artifact: logkit:logkit:jar:1.2 has no file. [ERROR] Artifact: org.antlr:antlr-runtime:jar:3.3 has no file. [ERROR] Artifact: org.antlr:stringtemplate:jar:4.0 has no file. [ERROR] Artifact: org.apache.commons:commons-lang3:jar:3.3.2 has no file. [ERROR] Artifact: org.apache.jcs:jcs:jar:1.3 has no file. [ERROR] Artifact: org.hamcrest:hamcrest-core:jar:1.3 has no file. [ERROR] Artifact: org.jacorb:jacorb:jar:P6:2.3.0 has no file. [ERROR] Artifact: org.javassist:javassist:jar:3.19.0-GA has no file. [ERROR] Artifact: org.mockito:mockito-all:jar:1.10.19 has no file. [ERROR] Artifact: org.objenesis:objenesis:jar:2.1 has no file. [ERROR] Artifact: org.osgi:osgi_R4_core:jar:1.0 has no file. [ERROR] Artifact: org.powermock:powermock-api-mockito:jar:1.6.2 has no file. [ERROR] Artifact: org.powermock:powermock-api-support:jar:1.6.2 has no file. [ERROR] Artifact: org.powermock:powermock-core:jar:1.6.2 has no file. [ERROR] Artifact: org.powermock:powermock-module-junit4:jar:1.6.2 has no file. [ERROR] Artifact: org.powermock:powermock-module-junit4-common:jar:1.6.2 has no file. [ERROR] Artifact: org.powermock:powermock-reflect:jar:1.6.2 has no file. [ERROR] Artifact: org.projectlombok:lombok:jar:1.16.2 has no file. [ERROR] Artifact: xerces:xercesImpl:jar:2.11.0 has no file. [ERROR] Artifact: xml-apis:xml-apis:jar:1.4.01 has no file. We use dedicated build machine for release activities. Yesterday I got above errors when I chcked out new version from SVN and executed mvn clean package deploy site. I tried adding -U to the command, with no effect. When I executed with -X switch, I got: [DEBUG] Using mirror mirrorId (http://maven.company.com/content/repositories/central) for central (https://repo.maven.apache.org/maven2). // repeated couple times [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 01:40 min [INFO] Finished at: 2015-07-06T04:49:29-05:00 [INFO] Final Memory: 72M/675M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project project: Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site failed. NullPointerException - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project project: Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site failed. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
[jira] [Closed] (MSHADE-148) Shade Plugin gets stuck in infinite loop building dependency reduced POM
[ https://issues.apache.org/jira/browse/MSHADE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-148. -- Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1689490|http://svn.apache.org/r1689490] Shade Plugin gets stuck in infinite loop building dependency reduced POM Key: MSHADE-148 URL: https://issues.apache.org/jira/browse/MSHADE-148 Project: Maven Shade Plugin Issue Type: Bug Affects Versions: 2.1 Environment: OS X 10.7.5 Reporter: Rob Vesse Assignee: Karl Heinz Marbaise Fix For: 2.5 Attachments: MSHADE-148.patch, dependency-reduced-pom.xml, pom.xml, shade-bug.txt I have encountered a bug whereby the shade plugin gets stuck in an infinite loop in the step of creating a dependency reduced POM. I have attached a minimal POM that reproduces the issue and done some debugging on this. The problem seems to be caused by using both the jar and test-jar version of a dependency (jena-fuseki in my example) while also including a jar dependency that is a transitive dependency of the other dependencies (jena-arq in my example). Removing either the jar/test-jar resolves the problem and so does removing the other jar dependency. The problem appears to be that the plugin is getting stuck endlessly trying to produce the dependency-reduced-pom.xml If I watch the file over time it is repeatedly deleted and rewritten, each time it is written it gets larger. When I manage to kill the process at a point where the file is non-empty I can see that the plugin is endlessly adding the same set of exclusions to one of the jena-fuseki dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHADE-195) createSourcesJar with source:jar-no-fork causes sources.jar to be deployed twice, causing the build to fail
[
https://issues.apache.org/jira/browse/MSHADE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615577#comment-14615577
]
Karl Heinz Marbaise commented on MSHADE-195:
Do you have an example project which shows the wrong behaviour ?
createSourcesJar with source:jar-no-fork causes sources.jar to be deployed
twice, causing the build to fail
---
Key: MSHADE-195
URL: https://issues.apache.org/jira/browse/MSHADE-195
Project: Maven Shade Plugin
Issue Type: Bug
Affects Versions: 2.3, 2.4
Reporter: Esko Luontola
The workaround described in https://issues.apache.org/jira/browse/MSHADE-120
(i.e. running maven-source-plugin's jar-no-fork goal before shading) causes
the problem that Maven will install and deploy the same sources.jar file
twice:
{noformat}
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @
pricing-client ---
[INFO] Installing xxx/pricing-client/target/pricing-client-0-SNAPSHOT.jar to
xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT.jar
[INFO] Installing xxx/pricing-client/target/dependency-reduced-pom.xml to
xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT.pom
[INFO] Installing
xxx/pricing-client/target/pricing-client-0-SNAPSHOT-sources.jar to
xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT-sources.jar
[INFO] Installing
xxx/pricing-client/target/pricing-client-0-SNAPSHOT-sources.jar to
xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT-sources.jar
{noformat}
With maven-install-plugin this doesn't matter that much, but with
maven-deploy-plugin it *fails the build*, because it tries to upload the
sources.jar twice to the Maven repository and _Nexus doesn't allow that_:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on
project project: Failed to deploy artifacts: Could not transfer artifact
xxx.availability:availability-client:jar:sources:1.0.24 from/to xxx-releases
(http://xxx/nexus/content/repositories/releases): Failed to transfer file:
http://xxx/nexus/content/repositories/releases//availability/availability-client/1.0.24/availability-client-1.0.24-sources.jar.
Return code is: 400, ReasonPhrase: Bad Request.
{noformat}
I'm suspecting this to be something like the maven-source-plugin and
maven-shade-plugin both attaching the same sources.jar to the build, when
only one of them should do it. This problem only happens with the sources jar
and not the main artifact, so a trick similar to replacing the main artifact
is needed also for the sources jar.
h4. Workaround
Configure maven-source-plugin with {{attachfalse/attach}}. Then the shade
plugin will find the sources and include them in the shaded sources jar, but
the sources jar won't be attached to the build twice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNGSITE-246) Documentation of mavenrc_pre / .mavenrc
[ https://issues.apache.org/jira/browse/MNGSITE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615151#comment-14615151 ] Manfred Moser commented on MNGSITE-246: --- This should be added with a little info to the new configure page and then with more details on a separate page linked off it imho. http://maven.apache.org/configure.html Documentation of mavenrc_pre / .mavenrc --- Key: MNGSITE-246 URL: https://issues.apache.org/jira/browse/MNGSITE-246 Project: Maven Project Web Site Issue Type: Improvement Reporter: Karl Heinz Marbaise Priority: Minor The usage and the intention of mavenrc_pre and .maverc should be documented somehow. cause at the moment it does not exist any documenation about this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MSHADE-148) Shade Plugin gets stuck in infinite loop building dependency reduced POM
[ https://issues.apache.org/jira/browse/MSHADE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHADE-148: --- Fix Version/s: 2.5 Shade Plugin gets stuck in infinite loop building dependency reduced POM Key: MSHADE-148 URL: https://issues.apache.org/jira/browse/MSHADE-148 Project: Maven Shade Plugin Issue Type: Bug Affects Versions: 2.1 Environment: OS X 10.7.5 Reporter: Rob Vesse Fix For: 2.5 Attachments: MSHADE-148.patch, dependency-reduced-pom.xml, pom.xml, shade-bug.txt I have encountered a bug whereby the shade plugin gets stuck in an infinite loop in the step of creating a dependency reduced POM. I have attached a minimal POM that reproduces the issue and done some debugging on this. The problem seems to be caused by using both the jar and test-jar version of a dependency (jena-fuseki in my example) while also including a jar dependency that is a transitive dependency of the other dependencies (jena-arq in my example). Removing either the jar/test-jar resolves the problem and so does removing the other jar dependency. The problem appears to be that the plugin is getting stuck endlessly trying to produce the dependency-reduced-pom.xml If I watch the file over time it is repeatedly deleted and rewritten, each time it is written it gets larger. When I manage to kill the process at a point where the file is non-empty I can see that the plugin is endlessly adding the same set of exclusions to one of the jena-fuseki dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MSHADE-195) createSourcesJar with source:jar-no-fork causes sources.jar to be deployed twice, causing the build to fail
[
https://issues.apache.org/jira/browse/MSHADE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MSHADE-195:
---
Fix Version/s: waiting-for-feedback
createSourcesJar with source:jar-no-fork causes sources.jar to be deployed
twice, causing the build to fail
---
Key: MSHADE-195
URL: https://issues.apache.org/jira/browse/MSHADE-195
Project: Maven Shade Plugin
Issue Type: Bug
Affects Versions: 2.3, 2.4
Reporter: Esko Luontola
Fix For: waiting-for-feedback
The workaround described in https://issues.apache.org/jira/browse/MSHADE-120
(i.e. running maven-source-plugin's jar-no-fork goal before shading) causes
the problem that Maven will install and deploy the same sources.jar file
twice:
{noformat}
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @
pricing-client ---
[INFO] Installing xxx/pricing-client/target/pricing-client-0-SNAPSHOT.jar to
xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT.jar
[INFO] Installing xxx/pricing-client/target/dependency-reduced-pom.xml to
xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT.pom
[INFO] Installing
xxx/pricing-client/target/pricing-client-0-SNAPSHOT-sources.jar to
xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT-sources.jar
[INFO] Installing
xxx/pricing-client/target/pricing-client-0-SNAPSHOT-sources.jar to
xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT-sources.jar
{noformat}
With maven-install-plugin this doesn't matter that much, but with
maven-deploy-plugin it *fails the build*, because it tries to upload the
sources.jar twice to the Maven repository and _Nexus doesn't allow that_:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on
project project: Failed to deploy artifacts: Could not transfer artifact
xxx.availability:availability-client:jar:sources:1.0.24 from/to xxx-releases
(http://xxx/nexus/content/repositories/releases): Failed to transfer file:
http://xxx/nexus/content/repositories/releases//availability/availability-client/1.0.24/availability-client-1.0.24-sources.jar.
Return code is: 400, ReasonPhrase: Bad Request.
{noformat}
I'm suspecting this to be something like the maven-source-plugin and
maven-shade-plugin both attaching the same sources.jar to the build, when
only one of them should do it. This problem only happens with the sources jar
and not the main artifact, so a trick similar to replacing the main artifact
is needed also for the sources jar.
h4. Workaround
Configure maven-source-plugin with {{attachfalse/attach}}. Then the shade
plugin will find the sources and include them in the shaded sources jar, but
the sources jar won't be attached to the build twice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1166) Include/Exclude regex pattern for a path is incorrectly replaced on Windows
[
https://issues.apache.org/jira/browse/SUREFIRE-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615255#comment-14615255
]
Matthias Gradl commented on SUREFIRE-1166:
--
I have a patch, that should demonstrate the issue:
{noformat}
diff --git
a/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/FailsafeIncludesRegexPath.java
b/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/FailsafeIncludesRegexPath.java
new file mode 100644
index 000..463a639
--- /dev/null
+++
b/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/FailsafeIncludesRegexPath.java
@@ -0,0 +1,32 @@
+package org.apache.maven.surefire.its.jiras;
+
+import org.apache.maven.surefire.its.fixture.SurefireJUnit4IntegrationTestCase;
+import org.junit.Test;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+
+public class FailsafeIncludesRegexPath extends
SurefireJUnit4IntegrationTestCase {
+
+ @Test
+ public void testFailsafeIncludesRegexPath() throws Exception {
+ unpack(failsafe-includesRegexPath).executeVerify();
+ }
+}
diff --git
a/surefire-integration-tests/src/test/resources/failsafe-includesRegexPath/pom.xml
b/surefire-integration-tests/src/test/resources/failsafe-includesRegexPath/pom.xml
new file mode 100644
index 000..c84eea3
--- /dev/null
+++
b/surefire-integration-tests/src/test/resources/failsafe-includesRegexPath/pom.xml
@@ -0,0 +1,62 @@
+?xml version=1.0 encoding=UTF-8?
+!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one
+ ~ or more contributor license agreements. See the NOTICE file
+ ~ distributed with this work for additional information
+ ~ regarding copyright ownership. The ASF licenses this file
+ ~ to you under the Apache License, Version 2.0 (the
+ ~ License); you may not use this file except in compliance
+ ~ with the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing,
+ ~ software distributed under the License is distributed on an
+ ~ AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ~ KIND, either express or implied. See the License for the
+ ~ specific language governing permissions and limitations
+ ~ under the License.
+ --
+
+project xmlns=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;
+ modelVersion4.0.0/modelVersion
+ groupIdlocalhost/groupId
+ artifactIdfailsafe-includesRegexPath/artifactId
+ version1.0/version
+ namefailsafe-includesRegexPath/name
+ dependencies
+dependency
+ groupIdjunit/groupId
+ artifactIdjunit/artifactId
+ version3.8.2/version
+ scopetest/scope
+/dependency
+ /dependencies
+ build
+plugins
+ plugin
+groupIdorg.apache.maven.plugins/groupId
+artifactIdmaven-failsafe-plugin/artifactId
+version${surefire.version}/version
+ executions
+ execution
+ configuration
+ excludes
+ exclude%regex[.*/exclude/.*]/exclude
+ /excludes
+ includes
+ include%regex[.*/include/.*]/include
+ /includes
+ /configuration
+goals
+ goalintegration-test/goal
+ goalverify/goal
+/goals
+ /execution
+ /executions
+ /plugin
+/plugins
+ /build
+
+/project
diff --git
a/surefire-integration-tests/src/test/resources/failsafe-includesRegexPath/src/test/java/exclude/ExcludeMe.java
b/surefire-integration-tests/src/test/resources/failsafe-includesRegexPath/src/test/java/exclude/ExcludeMe.java
new file mode 100644
index 000..f876f13
--- /dev/null
+++
b/surefire-integration-tests/src/test/resources/failsafe-includesRegexPath/src/test/java/exclude/ExcludeMe.java
@@
[jira] [Commented] (MNG-5816) Empy maven.config cause Maven to exit with failure
[
https://issues.apache.org/jira/browse/MNG-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615464#comment-14615464
]
Hudson commented on MNG-5816:
-
SUCCESS: Integrated in maven-3.x #1089 (See
[https://builds.apache.org/job/maven-3.x/1089/])
[MNG-5816] Empy maven.config cause Maven to exit with failure (khmarbaise: rev
193778ec0e780ebf89138f5104ead881c0e3899f)
* maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java
Empy maven.config cause Maven to exit with failure
--
Key: MNG-5816
URL: https://issues.apache.org/jira/browse/MNG-5816
Project: Maven
Issue Type: Bug
Components: Bootstrap Build, Command Line
Affects Versions: 3.3.1
Reporter: tssp
Assignee: Karl Heinz Marbaise
Priority: Minor
Fix For: 3.3.4
An empty maven.config cause Maven to exit with a failure. Imho an empty
configuration file should be treated equally to a non-existing maven.config.
{code:none}
Unable to parse maven.config: Unrecognized maven.config entries: []
usage: mvn [options] [goal(s)] [phase(s)]
Options:
-am,--also-makeIf project list is specified, also
build projects required by the
list
-amd,--also-make-dependentsIf project list is specified, also
build projects that depend on
projects on the list
-B,--batch-modeRun in non-interactive (batch)
mode
-b,--builder arg The id of the build strategy to
use.
-C,--strict-checksums Fail the build if checksums don't
match
-c,--lax-checksums Warn if checksums don't match
-cpu,--check-plugin-updatesIneffective, only kept for
backward compatibility
-D,--define arg Define a system property
-e,--errorsProduce execution error messages
-emp,--encrypt-master-password arg Encrypt master security password
-ep,--encrypt-password arg Encrypt server password
-f,--file argForce the use of an alternate POM
file (or directory with pom.xml).
-fae,--fail-at-end Only fail the build afterwards;
allow all non-impacted builds to
continue
-ff,--fail-fastStop at first failure in
reactorized builds
-fn,--fail-never NEVER fail the build, regardless
of project result
-gs,--global-settings argAlternate path for the global
settings file
-gt,--global-toolchains arg Alternate path for the global
toolchains file
-h,--help Display help information
-l,--log-file argLog file to where all build output
will go.
-llr,--legacy-local-repository Use Maven 2 Legacy Local
Repository behaviour, ie no use of
_remote.repositories. Can also be
activated by using
-Dmaven.legacyLocalRepo=true
-N,--non-recursive Do not recurse into sub-projects
-npr,--no-plugin-registry Ineffective, only kept for
backward compatibility
-npu,--no-plugin-updates Ineffective, only kept for
backward compatibility
-nsu,--no-snapshot-updates Suppress SNAPSHOT updates
-o,--offline Work offline
-P,--activate-profiles arg Comma-delimited list of profiles
to activate
-pl,--projects arg Comma-delimited list of specified
reactor projects to build instead
of all projects. A project can be
specified by [groupId]:artifactId
or by its relative path.
-q,--quiet Quiet output - only show errors
-rf,--resume-from argResume reactor from specified
[jira] [Commented] (MNG-5816) Empy maven.config cause Maven to exit with failure
[
https://issues.apache.org/jira/browse/MNG-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615434#comment-14615434
]
ASF GitHub Bot commented on MNG-5816:
-
Github user khmarbaise commented on the pull request:
https://github.com/apache/maven/pull/47#issuecomment-118945749
Integrated. Thanks for fix.
Empy maven.config cause Maven to exit with failure
--
Key: MNG-5816
URL: https://issues.apache.org/jira/browse/MNG-5816
Project: Maven
Issue Type: Bug
Components: Bootstrap Build, Command Line
Affects Versions: 3.3.1
Reporter: tssp
Assignee: Jason van Zyl
Priority: Minor
Fix For: 3.3.4
An empty maven.config cause Maven to exit with a failure. Imho an empty
configuration file should be treated equally to a non-existing maven.config.
{code:none}
Unable to parse maven.config: Unrecognized maven.config entries: []
usage: mvn [options] [goal(s)] [phase(s)]
Options:
-am,--also-makeIf project list is specified, also
build projects required by the
list
-amd,--also-make-dependentsIf project list is specified, also
build projects that depend on
projects on the list
-B,--batch-modeRun in non-interactive (batch)
mode
-b,--builder arg The id of the build strategy to
use.
-C,--strict-checksums Fail the build if checksums don't
match
-c,--lax-checksums Warn if checksums don't match
-cpu,--check-plugin-updatesIneffective, only kept for
backward compatibility
-D,--define arg Define a system property
-e,--errorsProduce execution error messages
-emp,--encrypt-master-password arg Encrypt master security password
-ep,--encrypt-password arg Encrypt server password
-f,--file argForce the use of an alternate POM
file (or directory with pom.xml).
-fae,--fail-at-end Only fail the build afterwards;
allow all non-impacted builds to
continue
-ff,--fail-fastStop at first failure in
reactorized builds
-fn,--fail-never NEVER fail the build, regardless
of project result
-gs,--global-settings argAlternate path for the global
settings file
-gt,--global-toolchains arg Alternate path for the global
toolchains file
-h,--help Display help information
-l,--log-file argLog file to where all build output
will go.
-llr,--legacy-local-repository Use Maven 2 Legacy Local
Repository behaviour, ie no use of
_remote.repositories. Can also be
activated by using
-Dmaven.legacyLocalRepo=true
-N,--non-recursive Do not recurse into sub-projects
-npr,--no-plugin-registry Ineffective, only kept for
backward compatibility
-npu,--no-plugin-updates Ineffective, only kept for
backward compatibility
-nsu,--no-snapshot-updates Suppress SNAPSHOT updates
-o,--offline Work offline
-P,--activate-profiles arg Comma-delimited list of profiles
to activate
-pl,--projects arg Comma-delimited list of specified
reactor projects to build instead
of all projects. A project can be
specified by [groupId]:artifactId
or by its relative path.
-q,--quiet Quiet output - only show errors
-rf,--resume-from argResume reactor from specified
project
-s,--settings argAlternate path for the user
[jira] [Closed] (MNG-5816) Empy maven.config cause Maven to exit with failure
[
https://issues.apache.org/jira/browse/MNG-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MNG-5816.
Resolution: Fixed
Assignee: Karl Heinz Marbaise (was: Jason van Zyl)
Fixed by
[193778ec0e780ebf89138f5104ead881c0e3899f|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=193778ec0e780ebf89138f5104ead881c0e3899f].
Empy maven.config cause Maven to exit with failure
--
Key: MNG-5816
URL: https://issues.apache.org/jira/browse/MNG-5816
Project: Maven
Issue Type: Bug
Components: Bootstrap Build, Command Line
Affects Versions: 3.3.1
Reporter: tssp
Assignee: Karl Heinz Marbaise
Priority: Minor
Fix For: 3.3.4
An empty maven.config cause Maven to exit with a failure. Imho an empty
configuration file should be treated equally to a non-existing maven.config.
{code:none}
Unable to parse maven.config: Unrecognized maven.config entries: []
usage: mvn [options] [goal(s)] [phase(s)]
Options:
-am,--also-makeIf project list is specified, also
build projects required by the
list
-amd,--also-make-dependentsIf project list is specified, also
build projects that depend on
projects on the list
-B,--batch-modeRun in non-interactive (batch)
mode
-b,--builder arg The id of the build strategy to
use.
-C,--strict-checksums Fail the build if checksums don't
match
-c,--lax-checksums Warn if checksums don't match
-cpu,--check-plugin-updatesIneffective, only kept for
backward compatibility
-D,--define arg Define a system property
-e,--errorsProduce execution error messages
-emp,--encrypt-master-password arg Encrypt master security password
-ep,--encrypt-password arg Encrypt server password
-f,--file argForce the use of an alternate POM
file (or directory with pom.xml).
-fae,--fail-at-end Only fail the build afterwards;
allow all non-impacted builds to
continue
-ff,--fail-fastStop at first failure in
reactorized builds
-fn,--fail-never NEVER fail the build, regardless
of project result
-gs,--global-settings argAlternate path for the global
settings file
-gt,--global-toolchains arg Alternate path for the global
toolchains file
-h,--help Display help information
-l,--log-file argLog file to where all build output
will go.
-llr,--legacy-local-repository Use Maven 2 Legacy Local
Repository behaviour, ie no use of
_remote.repositories. Can also be
activated by using
-Dmaven.legacyLocalRepo=true
-N,--non-recursive Do not recurse into sub-projects
-npr,--no-plugin-registry Ineffective, only kept for
backward compatibility
-npu,--no-plugin-updates Ineffective, only kept for
backward compatibility
-nsu,--no-snapshot-updates Suppress SNAPSHOT updates
-o,--offline Work offline
-P,--activate-profiles arg Comma-delimited list of profiles
to activate
-pl,--projects arg Comma-delimited list of specified
reactor projects to build instead
of all projects. A project can be
specified by [groupId]:artifactId
or by its relative path.
-q,--quiet Quiet output - only show errors
-rf,--resume-from argResume reactor from specified
project
-s,--settings arg
[jira] [Created] (MNG-5852) mvn script invokes /bin/sh but requires /bin/bash functions
Jeffrey Alexander created MNG-5852: -- Summary: mvn script invokes /bin/sh but requires /bin/bash functions Key: MNG-5852 URL: https://issues.apache.org/jira/browse/MNG-5852 Project: Maven Issue Type: Bug Components: Command Line Affects Versions: 3.3.3 Environment: Solaris 11 Reporter: Jeffrey Alexander The bin/mvn script uses the local command which is a shell builtin of bash and similar shells, but is not required for POSIX-compliance in sh. When I attempt to run mvn on my Solaris system, I see the following output: $ ./mvn ./mvn[200]: local: not found [No such file or directory] ./mvn[201]: local: not found [No such file or directory] ... Lines 200 and 201 invoke local to make local variables to the function. According to man bash, this is a shell builtin. However, bin/mvn is invoked as: #!/bin/sh On most flavors of linux, this resolves to bash or dash which probably runs in a restricted environment after checking to see that its $0 is sh. But on Solaris's /bin/sh is actually ksh93 for backwards compatibility. Since local is not part of a POSIX-compliant /bin/sh, depending on it in a script that is invoked with /bin/sh is a bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1166) Include/Exclude regex pattern for a path is incorrectly replaced on Windows
[ https://issues.apache.org/jira/browse/SUREFIRE-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615835#comment-14615835 ] Tibor Digana commented on SUREFIRE-1166: Can you open normal PR on GitHub? This is very hard to merge. Include/Exclude regex pattern for a path is incorrectly replaced on Windows --- Key: SUREFIRE-1166 URL: https://issues.apache.org/jira/browse/SUREFIRE-1166 Project: Maven Surefire Issue Type: Bug Components: Maven Failsafe Plugin Affects Versions: 2.18.1 Environment: Windows Reporter: Matthias Gradl On non-unix systems, the file scanner converts slashes (/) into the file-system appropriate separator (eg. \ on Windows) thus colliding with the standard escape character in regex Strings. For regex pattern matching a path (segment) to a test package (like: %regex[.*/smoketest/.*Test\.java] this leads to unusable patterns: %regex[.*\smoketest\.*Test\.java] There needs to be a more sophisticated replacement happening when the include string is actually a regex pattern. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1166) Include/Exclude regex pattern for a path is incorrectly replaced on Windows
[ https://issues.apache.org/jira/browse/SUREFIRE-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615867#comment-14615867 ] Tibor Digana commented on SUREFIRE-1166: Most probably you did not run your IT with 2.19-SNAPSHOT excluding the patch itself because the patch is used in @Deprecated class SpecificFileFilter. The class is used within a unit test only. Try to run you project with 2.19-SNAPSHOT and let me know if we still have the same issue. Include/Exclude regex pattern for a path is incorrectly replaced on Windows --- Key: SUREFIRE-1166 URL: https://issues.apache.org/jira/browse/SUREFIRE-1166 Project: Maven Surefire Issue Type: Bug Components: Maven Failsafe Plugin Affects Versions: 2.18.1 Environment: Windows Reporter: Matthias Gradl On non-unix systems, the file scanner converts slashes (/) into the file-system appropriate separator (eg. \ on Windows) thus colliding with the standard escape character in regex Strings. For regex pattern matching a path (segment) to a test package (like: %regex[.*/smoketest/.*Test\.java] this leads to unusable patterns: %regex[.*\smoketest\.*Test\.java] There needs to be a more sophisticated replacement happening when the include string is actually a regex pattern. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHADE-148) Shade Plugin gets stuck in infinite loop building dependency reduced POM
[ https://issues.apache.org/jira/browse/MSHADE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615820#comment-14615820 ] Andrew Or commented on MSHADE-148: -- Thanks for the fix. When will the next release be published? The Spark project is suffering from this issue (SPARK-8819) and currently needs to introduce a hacky workaround for it. Shade Plugin gets stuck in infinite loop building dependency reduced POM Key: MSHADE-148 URL: https://issues.apache.org/jira/browse/MSHADE-148 Project: Maven Shade Plugin Issue Type: Bug Affects Versions: 2.1 Environment: OS X 10.7.5 Reporter: Rob Vesse Assignee: Karl Heinz Marbaise Fix For: 2.5 Attachments: MSHADE-148.patch, dependency-reduced-pom.xml, pom.xml, shade-bug.txt I have encountered a bug whereby the shade plugin gets stuck in an infinite loop in the step of creating a dependency reduced POM. I have attached a minimal POM that reproduces the issue and done some debugging on this. The problem seems to be caused by using both the jar and test-jar version of a dependency (jena-fuseki in my example) while also including a jar dependency that is a transitive dependency of the other dependencies (jena-arq in my example). Removing either the jar/test-jar resolves the problem and so does removing the other jar dependency. The problem appears to be that the plugin is getting stuck endlessly trying to produce the dependency-reduced-pom.xml If I watch the file over time it is repeatedly deleted and rewritten, each time it is written it gets larger. When I manage to kill the process at a point where the file is non-empty I can see that the plugin is endlessly adding the same set of exclusions to one of the jena-fuseki dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1167) Upgrade DOXIA to Version 1.6
Tibor Digana created SUREFIRE-1167: -- Summary: Upgrade DOXIA to Version 1.6 Key: SUREFIRE-1167 URL: https://issues.apache.org/jira/browse/SUREFIRE-1167 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin Affects Versions: 2.18.1 Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.19 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1167) Upgrade DOXIA to Version 1.6
[ https://issues.apache.org/jira/browse/SUREFIRE-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1167. -- Resolution: Fixed commit 789252c9f3cd7922840d2ae027668a75455c9d8f Upgrade DOXIA to Version 1.6 Key: SUREFIRE-1167 URL: https://issues.apache.org/jira/browse/SUREFIRE-1167 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin Affects Versions: 2.18.1 Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.19 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-300) Upgrade to Checkstyle 6.8.x+
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616099#comment-14616099
]
Roman Ivanov commented on MCHECKSTYLE-300:
--
Hi [~denn...@apache.org] ,
{quote}The version of Checkstyle used in the upcoming 2.16 version of the
plugin requires Java 7, which has meant a bunch of changes to the POM (this is
the first Maven plugin that will require Java 7){quote}
Sorry for causing a problem by that, it was my decision that helped me to
attract more contributors to the project, there is no fun to contribute by Java
that is outdated. Even java7 already got EOL , do you know plans for upgrade
of pom's to java8 ?
{quote} I wanted to use the latest version of Checkstyle for the release, but
got stuck when upgrading, see MCHECKSTYLE-292{quote}
can you point me exact problem with that upgrade, I see reference to closed
issue and reference to changes in c-tor signature that will result in
additional catch in plugin as maximum, am I miss smth ?
{quote} it would be great if you could have a look at MCHECKSTYLE-292 and help
us get past the problems described in there.{quote}
see my answer above , please do not hesitate to contact our team at mail-list
(https://groups.google.com/forum/#!forum/checkstyle-devel) for any help or
problem you run into.
{quote} I will try to push for a release of the plugin now, in its current
state. Then when we get MCHECKSTYLE-292 solved I can push for another
release.{quote}
please do 2.16 , and 292 we will resolve as next step.
It would be really nice for plugin to catch up to almost same rollout schedule
(introducing checkstyle version bump as a hotfix release 2.16.1, 2.16.2
,..) if not braking compatibility is introduced by library. Please let me
know if I help somehow.
Upgrade to Checkstyle 6.8.x+
Key: MCHECKSTYLE-300
URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-300
Project: Maven Checkstyle Plugin
Issue Type: Improvement
Reporter: Juan Martín Sotuyo Dodero
We should upgrade to the latest and greatest checkstyle version. Notice since
6.8 there was a big breaking change:
Rename CheckStyleTask to CheckstyleAntTask, Rename and move
checkstyletask.properties. Author: Michal Kordas
[#1108|https://github.com/checkstyle/checkstyle/issues/1108]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MNG-5853) Can not set proxy port to 443
Chuyen Vo created MNG-5853: -- Summary: Can not set proxy port to 443 Key: MNG-5853 URL: https://issues.apache.org/jira/browse/MNG-5853 Project: Maven Issue Type: Bug Components: General, Settings Affects Versions: 3.2.3 Environment: mvn --version Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-12T03:58:10+07:00) Maven home: /opt/maven Java version: 1.7.0_67, vendor: Oracle Corporation Java home: /usr/java/jdk1.7.0_67/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: linux, version: 2.6.32-431.el6.x86_64, arch: amd64, family: unix settings proxies proxy activetrue/active protocolhttp/protocol hostx.x.x.x/host port443/port username/username password/password nonProxyHostswww.google.com|*.somewhere.com/nonProxyHosts /proxy /proxies /settings Reporter: Chuyen Vo org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute INFO: I/O exception (java.net.SocketException) caught when processing request: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPMD-213) The language parameter should not be read-only
Dennis Lundberg created MPMD-213:
Summary: The language parameter should not be read-only
Key: MPMD-213
URL: https://issues.apache.org/jira/browse/MPMD-213
Project: Maven PMD Plugin
Issue Type: Bug
Reporter: Dennis Lundberg
The language parameter in {{AbstractPmdViolationCheckMojo}} should not be
read-only. It should be possible to change it in case you have an artifact with
different types of sources, i.e. java and javascript.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MPMD-213) The language parameter should not be read-only
[
https://issues.apache.org/jira/browse/MPMD-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MPMD-213:
-
Description: The language parameter in {{AbstractPmdViolationCheckMojo}}
should not be read-only. It should be possible to change it in case you have an
artifact with a type of sources for which there is no artifact handler, i.e.
jsp. (was: The language parameter in {{AbstractPmdViolationCheckMojo}} should
not be read-only. It should be possible to change it in case you have an
artifact with different types of sources, i.e. java and javascript.)
The language parameter should not be read-only
--
Key: MPMD-213
URL: https://issues.apache.org/jira/browse/MPMD-213
Project: Maven PMD Plugin
Issue Type: Bug
Reporter: Dennis Lundberg
The language parameter in {{AbstractPmdViolationCheckMojo}} should not be
read-only. It should be possible to change it in case you have an artifact
with a type of sources for which there is no artifact handler, i.e. jsp.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MPMD-213) The language parameter should not be read-only
[
https://issues.apache.org/jira/browse/MPMD-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MPMD-213:
-
Description:
The language parameter in {{AbstractPmdViolationCheckMojo}} should not be
read-only. It should be possible to change it in case you have an artifact with
a type of sources for which there is no artifact handler, i.e. javascript.
The IT PMD-205-pmd-js-check shows this. It currently fails under Maven 2.2.1,
but works under Maven 3 due to MNG-5001.
was:The language parameter in {{AbstractPmdViolationCheckMojo}} should not be
read-only. It should be possible to change it in case you have an artifact with
a type of sources for which there is no artifact handler, i.e. jsp.
The language parameter should not be read-only
--
Key: MPMD-213
URL: https://issues.apache.org/jira/browse/MPMD-213
Project: Maven PMD Plugin
Issue Type: Bug
Reporter: Dennis Lundberg
The language parameter in {{AbstractPmdViolationCheckMojo}} should not be
read-only. It should be possible to change it in case you have an artifact
with a type of sources for which there is no artifact handler, i.e.
javascript.
The IT PMD-205-pmd-js-check shows this. It currently fails under Maven 2.2.1,
but works under Maven 3 due to MNG-5001.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MCHECKSTYLE-285) Remove config/maven_checks.xml by removing the dependency on maven-shared-resources:2
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHECKSTYLE-285. --- Resolution: Fixed Assignee: Dennis Lundberg Fixed in [r1689315|http://svn.apache.org/viewvc?view=revisionrevision=1689315]. Remove config/maven_checks.xml by removing the dependency on maven-shared-resources:2 - Key: MCHECKSTYLE-285 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-285 Project: Maven Checkstyle Plugin Issue Type: Task Reporter: Dennis Lundberg Assignee: Dennis Lundberg Fix For: 2.16 The plugin should not include configurations for specific projects, by default. Let the users pick their own configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-294) NPE on missing license artifact, not fixed previously
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14614592#comment-14614592 ] Dennis Lundberg commented on MCHECKSTYLE-294: - Hi Bob, What does your configuration look like? I'd like to add an integration test for this issue, to make sure it is properly fixed and doesn't reappear later on. NPE on missing license artifact, not fixed previously - Key: MCHECKSTYLE-294 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-294 Project: Maven Checkstyle Plugin Issue Type: Bug Components: checkstyle:checkstyle Affects Versions: 2.15, 2.16 Environment: Windows7 x64 JDK8 Checkstyle 6.2 maven-checkstyle-plugin 2.15 and 2.16-SNAPSHOT as of 5/20/2015. Reporter: Bob Fields Labels: easyfix, patch Fix For: 2.16 Attachments: MCHECKSTYLE-294.java.patch MCHECKSTYLE-250 fix does not check for null values, only for invalid URL. This patch checks for null values and fixes the original problem, and emits a warning if the license file is missing (but does not kill the checkstyle process or site build). Interestingly - this error only occurs on 'mvn site', not on 'mvn checkstyle:checkstyle'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-300) Upgrade to Checkstyle 6.8.x+
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14614607#comment-14614607 ] Dennis Lundberg commented on MCHECKSTYLE-300: - Hi all, There are a couple of reasons why there hasn't been a release of the plugin in a while: * There has been some breaking (for the Maven project itself) changes made in the upcoming 2.16 version of the plugin, which has required discussions to get them right * The version of Checkstyle used in the upcoming 2.16 version of the plugin requires Java 7, which has meant a bunch of changes to the POM (this is the first Maven plugin that will require Java 7) * I wanted to use the latest version of Checkstyle for the release, but got stuck when upgrading, see MCHECKSTYLE-292 * I haven't had much time for OSS-work lately [~romani], it would be great if you could have a look at MCHECKSTYLE-292 and help us get past the problems described in there. I will try to push for a release of the plugin now, in its current state. Then when we get MCHECKSTYLE-292 solved I can push for another release. Upgrade to Checkstyle 6.8.x+ Key: MCHECKSTYLE-300 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-300 Project: Maven Checkstyle Plugin Issue Type: Improvement Reporter: Juan Martín Sotuyo Dodero We should upgrade to the latest and greatest checkstyle version. Notice since 6.8 there was a big breaking change: Rename CheckStyleTask to CheckstyleAntTask, Rename and move checkstyletask.properties. Author: Michal Kordas [#1108|https://github.com/checkstyle/checkstyle/issues/1108] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1166) Include/Exclude regex pattern for a path is incorrectly replaced on Windows
Matthias Gradl created SUREFIRE-1166: Summary: Include/Exclude regex pattern for a path is incorrectly replaced on Windows Key: SUREFIRE-1166 URL: https://issues.apache.org/jira/browse/SUREFIRE-1166 Project: Maven Surefire Issue Type: Bug Components: Maven Failsafe Plugin Affects Versions: 2.18.1 Environment: Windows Reporter: Matthias Gradl On non-unix systems, the file scanner converts slashes (/) into the file-system appropriate separator (eg. \ on Windows) thus colliding with the standard escape character in regex Strings. For regex pattern matching a path (segment) to a test package (like: %regex[.*/smoketest/.*Test\.java] this leads to unusable patterns: %regex[.*\smoketest\.*Test\.java] There needs to be a more sophisticated replacement happening when the include string is actually a regex pattern. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHANGES-357) Cannot include Unresolved issues
[ https://issues.apache.org/jira/browse/MCHANGES-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615182#comment-14615182 ] Franck Malartic commented on MCHANGES-357: -- Hi Michael, The ECSS software standard (ECSS stands for European Cooperation for Space Standards) states that the release document shall list known problems and on-going changes (in addition to what have been fixed in the release). Since the information is available in Jira (opened issues), i would like to generate a report with Unresolved issues (as well as a report with Closed issues in this version). Best regards, Franck Cannot include Unresolved issues Key: MCHANGES-357 URL: https://issues.apache.org/jira/browse/MCHANGES-357 Project: Maven Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.11 Environment: Jira 5.2.11 Reporter: Franck Malartic Using the jira-report goal, it is impossible to get Unresolved issues. Unresolved is not managed by Jira server like other resolution statuses. The REST API does not return the Unresolved status thus the plugin throws the following exception: org.apache.maven.plugin.MojoFailureException: Could not find resolution Unresolved. at org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:265) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:246) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:212) at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:131) at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:372) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:210) at org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:207) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) at org.codehaus.classworlds.Launcher.main(Launcher.java:46) Note that you won't have the same error with the https://issues.apache.org/jira/ server, because the Unresolved status is redefined (id 9) https://issues.apache.org/jira/rest/api/2/resolution/ This is explicitly not recommended in Jira documentation: https://confluence.atlassian.com/display/JIRA/Defining+Resolution+Field+Values The redefinition of Unresolved shall lead to incorrect Jira status report. JQL with id=Unresolved is correct: https://issues.apache.org/jira/browse/MCHANGES-240?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC but with id=9 it is not (result is empty): https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%209%20ORDER%20BY%20priority%20DESC And in that case,
