[jira] [Commented] (MNG-6216) ArrayIndexOutOfBoundsException when parsing POM
[ https://issues.apache.org/jira/browse/MNG-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189717#comment-17189717 ] Michael Osipov commented on MNG-6216: - I'd be happy to analyze if you could provide me the sample project. > ArrayIndexOutOfBoundsException when parsing POM > > > Key: MNG-6216 > URL: https://issues.apache.org/jira/browse/MNG-6216 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Marc Savy >Priority: Major > Fix For: 3.7.x-candidate > > Attachments: log > > > When building apiman https://github.com/apiman/apiman.git on Maven 3.5.0 the > XML parser seems to have some issues parsing the apiman-test-common module. > If you want to reproduce, you can simply use mvn clean install, no profiles > needed. > Log: https://gist.github.com/msavy/a1b4307fb238a543dfd6af426b42d446 > Also attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6216) ArrayIndexOutOfBoundsException when parsing POM
[ https://issues.apache.org/jira/browse/MNG-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189691#comment-17189691 ] Robert Scholte commented on MNG-6216: - It is indeed a race condition issue, but IIRC with a simple project I was able to hit it somewhere between 20% to 33% of the times. That might be often enough for an IT. > ArrayIndexOutOfBoundsException when parsing POM > > > Key: MNG-6216 > URL: https://issues.apache.org/jira/browse/MNG-6216 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Marc Savy >Priority: Major > Fix For: 3.7.x-candidate > > Attachments: log > > > When building apiman https://github.com/apiman/apiman.git on Maven 3.5.0 the > XML parser seems to have some issues parsing the apiman-test-common module. > If you want to reproduce, you can simply use mvn clean install, no profiles > needed. > Log: https://gist.github.com/msavy/a1b4307fb238a543dfd6af426b42d446 > Also attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6216) ArrayIndexOutOfBoundsException when parsing POM
[ https://issues.apache.org/jira/browse/MNG-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189638#comment-17189638 ] Michael Osipov commented on MNG-6216: - The only thing I can think of is concurrency (race conditions) issues in Resolver. Version 1.6.0 will provide two concurrency safe contexts to avoid such issues. > ArrayIndexOutOfBoundsException when parsing POM > > > Key: MNG-6216 > URL: https://issues.apache.org/jira/browse/MNG-6216 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Marc Savy >Priority: Major > Fix For: 3.7.x-candidate > > Attachments: log > > > When building apiman https://github.com/apiman/apiman.git on Maven 3.5.0 the > XML parser seems to have some issues parsing the apiman-test-common module. > If you want to reproduce, you can simply use mvn clean install, no profiles > needed. > Log: https://gist.github.com/msavy/a1b4307fb238a543dfd6af426b42d446 > Also attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARCHETYPE-610) Allow to enforce line ending for files generated from Velocity templates
Konrad Windszus created ARCHETYPE-610: - Summary: Allow to enforce line ending for files generated from Velocity templates Key: ARCHETYPE-610 URL: https://issues.apache.org/jira/browse/ARCHETYPE-610 Project: Maven Archetype Issue Type: Improvement Components: Archetypes Affects Versions: 3.2.0 Reporter: Konrad Windszus Sometimes files created from velocity templates should have a specific line ending. Currently it is always the platform default. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1798) trimStackTrace should be false by default
[
https://issues.apache.org/jira/browse/SUREFIRE-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189572#comment-17189572
]
Jesse Glick commented on SUREFIRE-1798:
---
bq. pushing this change right now would mean that the behavior of configuration
parameter would change. We have a big opportunity to use the version 3.0.0-M5
in Maven 3.7.0.
Misleading I think. From what I can tell, the current default version in Maven
is 2.12.4, which did trim stack traces by default but only above the test code:
in the above example, lines below {{BaseSlackIntegrationTest.setUp}}. (The
trimming actually seems to be broken in 2.12.4 at least on JUnit 4.13; fixed in
2.13.) Still potentially missing some critical diagnostic information, but far
less likely than the current (2.19+) behavior.
Therefore I would advise against such an upgrade until this issue is fixed, as
it would make everyday test-driven development less usable by default.
> trimStackTrace should be false by default
> -
>
> Key: SUREFIRE-1798
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1798
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Surefire Plugin
>Reporter: Romain Manni-Bucau
>Priority: Major
>
> True was intended to clean up the output but it always misses any useful data
> so let's set an useful default
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MCHANGES-396) Upgrade Eclipse EGit Github client to 5.3.0
[ https://issues.apache.org/jira/browse/MCHANGES-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGES-396: -- Summary: Upgrade Eclipse EGit Github client to 5.3.0 (was: Upgrade GitHub client to 5.3.0) > Upgrade Eclipse EGit Github client to 5.3.0 > --- > > Key: MCHANGES-396 > URL: https://issues.apache.org/jira/browse/MCHANGES-396 > Project: Maven Changes Plugin > Issue Type: Dependency upgrade > Components: github >Affects Versions: 2.12.1 >Reporter: Luc Maisonobe >Priority: Major > Labels: Java8 > Fix For: 3.0.0 > > > In order to solve issue MCHANGES-378, it would be necessary > to first update the GiHubClient to the lastest version as commit > https://github.com/eclipse/egit-github/commit/03f87a38a842acf0f2958ef41d5dc34936eff074 > allows to set up a proxy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MCHANGES-393) Default for teamlist is wrong
[ https://issues.apache.org/jira/browse/MCHANGES-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MCHANGES-393. - Resolution: Duplicate > Default for teamlist is wrong > - > > Key: MCHANGES-393 > URL: https://issues.apache.org/jira/browse/MCHANGES-393 > Project: Maven Changes Plugin > Issue Type: Bug > Components: changes.xml >Reporter: Joerg Schaible >Priority: Major > > It seems at some stage the PIR changed the name for the page generated for > the team list. At least with current PIR 3.0.0 generates a page _team.html_ > and the current changes report has broken links for the devs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1798) trimStackTrace should be false by default
[
https://issues.apache.org/jira/browse/SUREFIRE-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189376#comment-17189376
]
James Nord commented on SUREFIRE-1798:
--
just lost a lot of time due to the stacktrace trimming the really important
information :(
{noformat}
[ERROR]
com.cloudbees.jenkins.test.acceptance.SlackIntegrationAndBitbucketTest.test_sending_when_pr_is_built
Time elapsed: 145.47 s <<< ERROR!
org.openqa.selenium.WebDriverException:
TypeError: a is null
Build info: version: '3.141.59', revision: 'e82be7d358', time:
'2018-11-14T08:17:03'
System info: host: 'CB-JAMES2', ip: '192.168.147.112', os.name: 'Windows 10',
os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_265'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Capabilities {acceptInsecureCerts: true, browserName: firefox, browserVersion:
79.0, javascriptEnabled: true, moz:accessibilityChecks: false, moz:buildID:
20200720193547, moz:geckodriverVersion: 0.27.0, moz:headless: false,
moz:processID: 2521, moz:profile: /tmp/rust_mozprofileXamBcR,
moz:shutdownTimeout: 6, moz:useNonSpecCompliantPointerOrigin: false,
moz:webdriverClick: true, pageLoadStrategy: normal, platform: LINUX,
platformName: LINUX, platformVersion: 4.19.104-microsoft-standard, rotatable:
false, setWindowRect: true, strictFileInteractability: false, timeouts:
{implicit: 0, pageLoad: 30, script: 3}, unhandledPromptBehavior:
dismiss and notify, webdriver.remote.sessionid: de72d1c1-b2e0-45d8-a52f-164...}
Session ID: de72d1c1-b2e0-45d8-a52f-164548f12475
{noformat}
is useless to help me fix the test and work out what and where it has failed.
when disabling stack trimming I get
{noformat}
[ERROR]
com.cloudbees.jenkins.test.acceptance.SlackIntegrationAndBitbucketTest.test_sending_when_pr_is_built
Time elapsed: 223.846 s <<< ERROR!
org.openqa.selenium.WebDriverException:
TypeError: a is null
Build info: version: '3.141.59', revision: 'e82be7d358', time:
'2018-11-14T08:17:03'
System info: host: 'CB-JAMES2', ip: '192.168.147.112', os.name: 'Windows 10',
os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_265'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Capabilities {acceptInsecureCerts: true, browserName: firefox, browserVersion:
79.0, javascriptEnabled: true, moz:accessibilityChecks: false, moz:buildID:
20200720193547, moz:geckodriverVersion: 0.27.0, moz:headless: false,
moz:processID: 2853, moz:profile: /tmp/rust_mozprofilefjc8vM,
moz:shutdownTimeout: 6, moz:useNonSpecCompliantPointerOrigin: false,
moz:webdriverClick: true, pageLoadStrategy: normal, platform: LINUX,
platformName: LINUX, platformVersion: 4.19.104-microsoft-standard, rotatable:
false, setWindowRect: true, strictFileInteractability: false, timeouts:
{implicit: 0, pageLoad: 30, script: 3}, unhandledPromptBehavior:
dismiss and notify, webdriver.remote.sessionid: 8d0ea3c9-747e-4e7f-96f0-fc5...}
Session ID: 8d0ea3c9-747e-4e7f-96f0-fc54ef7de803
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:187)
at
org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:122)
at
org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:158)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
at
org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:285)
at
org.openqa.selenium.remote.RemoteWebElement.getText(RemoteWebElement.java:166)
at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringWebElement.lambda$new$0(EventFiringWebDriver.java:404)
at com.sun.proxy.$Proxy38.getText(Unknown Source)
at
org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringWebElement.getText(EventFiringWebDriver.java:463)
at
org.jenkinsci.test.acceptance.po.CapybaraPortingLayerImpl.getPageContent(CapybaraPortingLayerImpl.java:490)
at
org.jenkinsci.test.acceptance.Matchers$1.matchesSafely(Matchers.java:47)
at
org.jenkinsci.test.acceptance.Matchers$1.matchesSafely(Matchers.java:41)
at org.hamcrest.TypeSafeM
[jira] [Closed] (MCHANGES-383) Support XInclude in changes.xml
[ https://issues.apache.org/jira/browse/MCHANGES-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MCHANGES-383. - Resolution: Auto Closed Feel free to open PR with secure solution and reopen ticket. > Support XInclude in changes.xml > --- > > Key: MCHANGES-383 > URL: https://issues.apache.org/jira/browse/MCHANGES-383 > Project: Maven Changes Plugin > Issue Type: New Feature > Components: changes.xml >Reporter: ocean >Priority: Minor > > Maven Changes should support XInclude in the changes.xml. > Problem: When writing a changes.xml file the file itself can grow very large. > We need to be able to break out each 'release' into its own file and include > that back in the changes.xml file. > Proposed Solution: changes.xml should support XInclude, the standard XML > mechanism for including one XML document in another. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MCHANGES-365) Add Link to Action
[
https://issues.apache.org/jira/browse/MCHANGES-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MCHANGES-365.
-
Resolution: Auto Closed
> Add Link to Action
> --
>
> Key: MCHANGES-365
> URL: https://issues.apache.org/jira/browse/MCHANGES-365
> Project: Maven Changes Plugin
> Issue Type: New Feature
> Components: announcement
>Affects Versions: 2.11
>Reporter: dur
>Priority: Minor
> Labels: close-pending
>
> Add property link to class Action to support links in an announcment.
> Property should copied in
> {code}
> /**
> * Create an Action from an issue.
> *
> * @param issue The issue to extract the information from
> * @return An Action
> */
> public Action createAction( Issue issue )
> {
> Action action = new Action();
> // @todo We need to add something like
> issue.getPresentationIdentifier() to be able to support other IMSes
> // beside JIRA
> action.setIssue( issue.getKey() );
> // Try to map the IMS-specific issue type to one that is used in a
> changes.xml file
> IssueType type;
> if ( getIssueTypeMap().containsKey( issue.getType() ) )
> {
> type = getIssueTypeMap().get( issue.getType() );
> action.setType( type.modelRepresentation() );
> }
> else
> {
> action.setType( UNKNOWN_ISSUE_TYPE );
> }
> action.setDev( issue.getAssignee() );
> // Set dueTo to the empty String instead of null to make Velocity
> happy
> action.setDueTo( "" );
> // action.setDueTo( issue.getReporter() );
> action.setAction( issue.getSummary() );
> return action;
> }
> {code}
> For example with following line:
> {code}
> action.setLink(issue.getLink());
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MCHANGES-365) Add Link to Action
[
https://issues.apache.org/jira/browse/MCHANGES-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MCHANGES-365:
--
Labels: (was: close-pending)
> Add Link to Action
> --
>
> Key: MCHANGES-365
> URL: https://issues.apache.org/jira/browse/MCHANGES-365
> Project: Maven Changes Plugin
> Issue Type: New Feature
> Components: announcement
>Affects Versions: 2.11
>Reporter: dur
>Priority: Minor
>
> Add property link to class Action to support links in an announcment.
> Property should copied in
> {code}
> /**
> * Create an Action from an issue.
> *
> * @param issue The issue to extract the information from
> * @return An Action
> */
> public Action createAction( Issue issue )
> {
> Action action = new Action();
> // @todo We need to add something like
> issue.getPresentationIdentifier() to be able to support other IMSes
> // beside JIRA
> action.setIssue( issue.getKey() );
> // Try to map the IMS-specific issue type to one that is used in a
> changes.xml file
> IssueType type;
> if ( getIssueTypeMap().containsKey( issue.getType() ) )
> {
> type = getIssueTypeMap().get( issue.getType() );
> action.setType( type.modelRepresentation() );
> }
> else
> {
> action.setType( UNKNOWN_ISSUE_TYPE );
> }
> action.setDev( issue.getAssignee() );
> // Set dueTo to the empty String instead of null to make Velocity
> happy
> action.setDueTo( "" );
> // action.setDueTo( issue.getReporter() );
> action.setAction( issue.getSummary() );
> return action;
> }
> {code}
> For example with following line:
> {code}
> action.setLink(issue.getLink());
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MCHANGES-396) Upgrade GitHub client to 5.3.0
[ https://issues.apache.org/jira/browse/MCHANGES-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGES-396: -- Labels: Java8 (was: ) > Upgrade GitHub client to 5.3.0 > -- > > Key: MCHANGES-396 > URL: https://issues.apache.org/jira/browse/MCHANGES-396 > Project: Maven Changes Plugin > Issue Type: Dependency upgrade > Components: github >Affects Versions: 2.12.1 >Reporter: Luc Maisonobe >Priority: Major > Labels: Java8 > Fix For: 3.0.0 > > > In order to solve issue MCHANGES-378, it would be necessary > to first update the GiHubClient to the lastest version as commit > https://github.com/eclipse/egit-github/commit/03f87a38a842acf0f2958ef41d5dc34936eff074 > allows to set up a proxy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-assembly-plugin] elharo closed pull request #36: revert jaxen scope
elharo closed pull request #36: URL: https://github.com/apache/maven-assembly-plugin/pull/36 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-assembly-plugin] elharo commented on pull request #36: revert jaxen scope
elharo commented on pull request #36: URL: https://github.com/apache/maven-assembly-plugin/pull/36#issuecomment-685829017 failure this was supposed to fix appears to be a flaky node This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MCHANGES-340) Retrieve Jira user/password from settings.xml
[ https://issues.apache.org/jira/browse/MCHANGES-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189324#comment-17189324 ] Sylwester Lachiewicz commented on MCHANGES-340: --- ok CI good, merged to master. For later it would be good to add more tests related to this functionality. > Retrieve Jira user/password from settings.xml > - > > Key: MCHANGES-340 > URL: https://issues.apache.org/jira/browse/MCHANGES-340 > Project: Maven Changes Plugin > Issue Type: New Feature > Components: jira >Reporter: Guillaume Boucherie >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.0.0 > > Attachments: MCHANGES-340.patch > > > Add a mechanism to get jira credentials from settings.xml instead from pom > only. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MCHANGES-340) Retrieve Jira user/password from settings.xml
[ https://issues.apache.org/jira/browse/MCHANGES-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MCHANGES-340. - Resolution: Fixed > Retrieve Jira user/password from settings.xml > - > > Key: MCHANGES-340 > URL: https://issues.apache.org/jira/browse/MCHANGES-340 > Project: Maven Changes Plugin > Issue Type: New Feature > Components: jira >Reporter: Guillaume Boucherie >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.0.0 > > Attachments: MCHANGES-340.patch > > > Add a mechanism to get jira credentials from settings.xml instead from pom > only. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MCHANGES-340) Retrieve Jira user/password from settings.xml
[ https://issues.apache.org/jira/browse/MCHANGES-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGES-340: -- Fix Version/s: 3.0.0 > Retrieve Jira user/password from settings.xml > - > > Key: MCHANGES-340 > URL: https://issues.apache.org/jira/browse/MCHANGES-340 > Project: Maven Changes Plugin > Issue Type: New Feature > Components: jira >Reporter: Guillaume Boucherie >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.0.0 > > Attachments: MCHANGES-340.patch > > > Add a mechanism to get jira credentials from settings.xml instead from pom > only. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MCHANGES-340) Retrieve Jira user/password from settings.xml
[ https://issues.apache.org/jira/browse/MCHANGES-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189317#comment-17189317 ] Hudson commented on MCHANGES-340: - Build succeeded in Jenkins: Maven » Maven TLP » maven-changes-plugin » master #13 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-changes-plugin/job/master/13/ > Retrieve Jira user/password from settings.xml > - > > Key: MCHANGES-340 > URL: https://issues.apache.org/jira/browse/MCHANGES-340 > Project: Maven Changes Plugin > Issue Type: New Feature > Components: jira >Reporter: Guillaume Boucherie >Assignee: Sylwester Lachiewicz >Priority: Major > Attachments: MCHANGES-340.patch > > > Add a mechanism to get jira credentials from settings.xml instead from pom > only. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-changes-plugin] asfgit closed pull request #18: MCHANGES-340 Support jira serverId configuration
asfgit closed pull request #18: URL: https://github.com/apache/maven-changes-plugin/pull/18 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-archetype] eolivelli commented on pull request #58: [ARCHETYPE-565] - Unable to resolve groovy.json classes when planting
eolivelli commented on pull request #58: URL: https://github.com/apache/maven-archetype/pull/58#issuecomment-685798664 CI is running https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-archetype/job/ARCHETYPE-565/ This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SUREFIRE-1837) NullPointerException at AbstractSurefireMojo$ClasspathCache.setCachedClasspath
[
https://issues.apache.org/jira/browse/SUREFIRE-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189301#comment-17189301
]
Ruslan Sibgatullin commented on SUREFIRE-1837:
--
Update:
After discovering SUREFIRE-1809 and applying
{code:java}
false
{code}
and changing the build command to
{code:java}
mvn test -e -T 1
{code}
described issue is no longer happening.
> NullPointerException at AbstractSurefireMojo$ClasspathCache.setCachedClasspath
> --
>
> Key: SUREFIRE-1837
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1837
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5
> Environment: mvn --version
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: /opt/apache-maven-3.6.3
> Java version: 11.0.8, vendor: Amazon.com Inc., runtime:
> /usr/lib/jvm/java-11-amazon-corretto
> Jenkins ver. 2.204.6 on Ubuntu 18
>Reporter: Ruslan Sibgatullin
>Priority: Major
>
> While migrating a rather old and big project from Java 8 to Java 11 the
> following exception happens occasionally (once in 3-4 builds):
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test)
> on project my_project: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test
> (default-test) on project cachereloader-validation: Execution default-test of
> goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:190)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:186)
> at java.util.concurrent.FutureTask.run (FutureTask.java:264)
> at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)
> at java.util.concurrent.FutureTask.run (FutureTask.java:264)
> at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1128)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:628)
> at java.lang.Thread.run (Thread.java:834)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:148)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:190)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:186)
> at java.util.concurrent.FutureTask.run (FutureTask.java:264)
> at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)
> at java.util.concurrent.FutureTask.run (FutureTask.java:264)
> at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1128)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:628)
> at java.lang.Thread.run (Thread.java:834)
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo$ClasspathCache.setCachedClasspath
> (AbstractSurefireMojo.java:4121)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo$ClasspathCache.access$200
> (AbstractSurefireMojo.java:4102)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.newStartupConfigWithClasspath
> (AbstractSurefireMojo.java:1913)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.createStartupConfiguration
> (AbstractSurefireMojo.java:1894)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.createForkSt
[GitHub] [maven-checkstyle-plugin] eolivelli commented on pull request #28: [MCHECKSTYLE-387] emit a warning when using an old version of checkstyle
eolivelli commented on pull request #28: URL: https://github.com/apache/maven-checkstyle-plugin/pull/28#issuecomment-685791357 @bmhm running CI now https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-checkstyle-plugin/job/MCHECKSTYLE-387/ This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-checkstyle-plugin] eolivelli commented on pull request #17: [MCHECKSTYLE-385] rework code to use a Violation.java class.
eolivelli commented on pull request #17: URL: https://github.com/apache/maven-checkstyle-plugin/pull/17#issuecomment-685790095 CI is running https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-checkstyle-plugin/job/MCHECKSTYLE-385/ I have squashed all of the commits and created a good commit message This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] allen-ball commented on pull request #58: MJAVADOC-661: Fix for tagletArtifact fails to scan multi-release JARs (MRJARs) for Taglets
allen-ball commented on pull request #58:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/58#issuecomment-685786789
I have added `src/it/projects/MJAVADOC-661_mrjar` which creates a
multi-release JAR with a Taglet specific to each release between 9 and
`${java.specification.version}`. The test output *without* the fix is:
```
...
[INFO] Building: MJAVADOC-661_mrjar/pom.xml
[INFO] run post-build script verify.groovy
[INFO] The post-build script did not succeed. ['com.foo.Taglet9',
'com.foo.Taglet10', 'com.foo.Taglet11', not found]. Expression:
(required.size() == 0)
[INFO] MJAVADOC-661_mrjar/pom.xml ... FAILED
(13.8 s)
...
[INFO] -
[INFO] Build Summary:
[INFO] Passed: 68, Failed: 1, Errors: 0, Skipped: 3
[INFO] -
[ERROR] The following builds failed:
[ERROR] * MJAVADOC-661_mrjar/pom.xml
[INFO] -
...
```
I believe `src/test/resources/unit/tagletArtifacts-test` takes care of the
Java 8 and before regressive case.
Thanks for your consideration.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-assembly-plugin] elharo opened a new pull request #36: revert jaxen scope
elharo opened a new pull request #36: URL: https://github.com/apache/maven-assembly-plugin/pull/36 let's see if this does anything This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-assembly-plugin] elharo closed pull request #35: revert last commit to fix build (maybe, might just be flaky)
elharo closed pull request #35: URL: https://github.com/apache/maven-assembly-plugin/pull/35 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-assembly-plugin] elharo opened a new pull request #35: revert last commit to fix build (maybe, might just be flaky)
elharo opened a new pull request #35: URL: https://github.com/apache/maven-assembly-plugin/pull/35 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-assembly-plugin] elharo merged pull request #33: docs: https links
elharo merged pull request #33: URL: https://github.com/apache/maven-assembly-plugin/pull/33 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-assembly-plugin] elharo opened a new pull request #34: declare dependencies
elharo opened a new pull request #34: URL: https://github.com/apache/maven-assembly-plugin/pull/34 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-archetype] acanda commented on pull request #56: [ARCHETYPE-605] Allow .gitignore file in archetype resources
acanda commented on pull request #56: URL: https://github.com/apache/maven-archetype/pull/56#issuecomment-685665037 Hi @cchacin I'm not sure what you mean. This PR hasn't been merged so far and is neither part of `v3.1.2` nor `v3.2.0`. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-assembly-plugin] elharo opened a new pull request #33: docs: https links
elharo opened a new pull request #33: URL: https://github.com/apache/maven-assembly-plugin/pull/33 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-6846) conditional overwrite
[
https://issues.apache.org/jira/browse/MNG-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189112#comment-17189112
]
Robert Scholte commented on MNG-6846:
-
It depends on the kind of pom if the value of revision should be replaced or
not. With MNG-6656 it will be easier to control this.
> conditional overwrite
> -
>
> Key: MNG-6846
> URL: https://issues.apache.org/jira/browse/MNG-6846
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
>Affects Versions: 3.5.0-alpha-1, 3.5.0-beta-1, 3.5.0, 3.5.2, 3.5.3, 3.5.4,
> 3.6.0, 3.6.1, 3.6.2, 3.6.3
> Environment: os:windows
> maven:3.6.2
>Reporter: zhaoyx
>Priority: Major
> Labels: beginner, newbie
> Attachments: image-2020-01-10-20-51-23-490.png
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator＃createValueSources＃lin：167
> when I use dynamic ci, I find that if the variable {{${revision}}} exists in
> other projects, it will be forced to change the version. This part should be
> filtered out. We cannot control the version of other projects. I tested the
> sample used [mng-6846|https://github.com/zhaoyunxing92/mng-6846]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MDEP-724) Dependency plugin bypasses reactor when resolving dependencies
[
https://issues.apache.org/jira/browse/MDEP-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189107#comment-17189107
]
Tuure Laurinolli commented on MDEP-724:
---
It seems that the dependency on reactor projects was added as resolution to
MDEP-409. Previously reactor projects weren't passed to the Maven dependency
graph builder
([https://github.com/apache/maven-dependency-plugin/commit/f0b51ae1f1e1176a6bf973cf56447a14498e8519#diff-1eef0a88ad828dd0e79215e74e8964d8L237).]
I suppose the JARs are not what is required.
> Dependency plugin bypasses reactor when resolving dependencies
> --
>
> Key: MDEP-724
> URL: https://issues.apache.org/jira/browse/MDEP-724
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: tree
>Affects Versions: 2.8
>Reporter: Tuure Laurinolli
>Priority: Major
> Attachments: resolution.zip
>
>
> When running {{mvn dependency:tree}} on a multi-module project, inter-module
> dependencies are not resolved through reactor. Using another goal in the same
> build (e.g. {{mvn compile dependency:tree}}) as suggested in
> http://www.mail-archive.com/users@maven.apache.org/msg104341.html resolves
> the immediate issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-shade-plugin] dependabot[bot] closed pull request #70: Bump mockito-core from 2.28.2 to 3.5.9
dependabot[bot] closed pull request #70: URL: https://github.com/apache/maven-shade-plugin/pull/70 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-shade-plugin] dependabot[bot] commented on pull request #70: Bump mockito-core from 2.28.2 to 3.5.9
dependabot[bot] commented on pull request #70: URL: https://github.com/apache/maven-shade-plugin/pull/70#issuecomment-685461636 Looks like org.mockito:mockito-core is no longer being updated by Dependabot, so this is no longer needed. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-6216) ArrayIndexOutOfBoundsException when parsing POM
[ https://issues.apache.org/jira/browse/MNG-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189080#comment-17189080 ] Robert Scholte commented on MNG-6216: - There are 2 rootcauses for getting the ArrayIndexOutOfBoundsException and AFAIK MNG-6281 is still an issue, unless something has been changed in Maven Resolver, assuming the real issue is there. > ArrayIndexOutOfBoundsException when parsing POM > > > Key: MNG-6216 > URL: https://issues.apache.org/jira/browse/MNG-6216 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Marc Savy >Priority: Major > Fix For: 3.7.x-candidate > > Attachments: log > > > When building apiman https://github.com/apiman/apiman.git on Maven 3.5.0 the > XML parser seems to have some issues parsing the apiman-test-common module. > If you want to reproduce, you can simply use mvn clean install, no profiles > needed. > Log: https://gist.github.com/msavy/a1b4307fb238a543dfd6af426b42d446 > Also attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MDEP-724) Dependency plugin bypasses reactor when resolving dependencies
[
https://issues.apache.org/jira/browse/MDEP-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189077#comment-17189077
]
Robert Scholte commented on MDEP-724:
-
[~martinkanters] is correct. I don't know the history why {{dependency:tree}}
needs the jars (I would expect that poms are good enough), but because of that
the reactor must provide the jars or classes-directory too, hence a compile
call is required in such case.
> Dependency plugin bypasses reactor when resolving dependencies
> --
>
> Key: MDEP-724
> URL: https://issues.apache.org/jira/browse/MDEP-724
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: tree
>Affects Versions: 2.8
>Reporter: Tuure Laurinolli
>Priority: Major
> Attachments: resolution.zip
>
>
> When running {{mvn dependency:tree}} on a multi-module project, inter-module
> dependencies are not resolved through reactor. Using another goal in the same
> build (e.g. {{mvn compile dependency:tree}}) as suggested in
> http://www.mail-archive.com/users@maven.apache.org/msg104341.html resolves
> the immediate issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Moved] (MDEP-724) Dependency plugin bypasses reactor when resolving dependencies
[
https://issues.apache.org/jira/browse/MDEP-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte moved MNG-6101 to MDEP-724:
--
Component/s: (was: Reactor and workspace)
(was: Dependencies)
tree
Fix Version/s: (was: 3.x / Backlog)
Key: MDEP-724 (was: MNG-6101)
Affects Version/s: (was: 3.3.9)
2.8
Issue Type: Improvement (was: Bug)
Project: Maven Dependency Plugin (was: Maven)
> Dependency plugin bypasses reactor when resolving dependencies
> --
>
> Key: MDEP-724
> URL: https://issues.apache.org/jira/browse/MDEP-724
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: tree
>Affects Versions: 2.8
>Reporter: Tuure Laurinolli
>Priority: Major
> Attachments: resolution.zip
>
>
> When running {{mvn dependency:tree}} on a multi-module project, inter-module
> dependencies are not resolved through reactor. Using another goal in the same
> build (e.g. {{mvn compile dependency:tree}}) as suggested in
> http://www.mail-archive.com/users@maven.apache.org/msg104341.html resolves
> the immediate issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
