[GitHub] [maven-mvnd] oehme commented on pull request #764: Fix core export provider

2023-01-17 Thread GitBox
oehme commented on PR #764: URL: https://github.com/apache/maven-mvnd/pull/764#issuecomment-1385112808 Would it be possible to get an m2 for this? I'd love to run our extensions full CI build against this to make sure we work properly when 1.0 comes out. -- This is an automated message fr

[GitHub] [maven-mvnd] oehme commented on pull request #764: Fix core export provider

2023-01-17 Thread GitBox
oehme commented on PR #764: URL: https://github.com/apache/maven-mvnd/pull/764#issuecomment-1385098837 @ppalaga this should be good to go :) -- 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 s

[GitHub] [maven-mvnd] oehme commented on pull request #764: Fix core export provider

2023-01-11 Thread GitBox
oehme commented on PR #764: URL: https://github.com/apache/maven-mvnd/pull/764#issuecomment-1379354001 @gnodet The test infrastructure assumes that every test case is a single project, but for my case I had to install the extension first before using it in the consuming build. I hacked arou

[GitHub] [maven-mvnd] oehme commented on pull request #764: Fix core export provider

2023-01-11 Thread GitBox
oehme commented on PR #764: URL: https://github.com/apache/maven-mvnd/pull/764#issuecomment-1378387110 Yes, I'll add one -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

[GitHub] [maven-mvnd] oehme commented on pull request #764: Fix core export provider

2023-01-05 Thread GitBox
oehme commented on PR #764: URL: https://github.com/apache/maven-mvnd/pull/764#issuecomment-1372212690 The underlying reason why the default logic doesn't work is because the [discovery method](https://github.com/apache/maven/blob/fc2d94f0777998000f7b886d45efb88c28fc09cd/maven-core/src/main