[
https://issues.apache.org/jira/browse/MBUILDCACHE-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622538#comment-17622538
]
ASF GitHub Bot commented on MBUILDCACHE-24:
---
AlexanderAshitkin opened a new pull request,
[
https://issues.apache.org/jira/browse/MBUILDCACHE-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated MBUILDCACHE-24:
--
Labels: pull-request-available (was: )
> Cache cannot be processed in presence of
AlexanderAshitkin opened a new pull request, #30:
URL: https://github.com/apache/maven-build-cache-extension/pull/30
Current implementation relies on lifecycle phases presence in
`MojoExecution`. In case of forked execution
`MojoExecution#getLifecyclePhase` could return null which
dependabot[bot] closed pull request #60: Bump mockito-core from 2.28.2 to 4.8.0
URL: https://github.com/apache/maven-doxia-sitetools/pull/60
--
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
dependabot[bot] commented on PR #60:
URL:
https://github.com/apache/maven-doxia-sitetools/pull/60#issuecomment-1287533059
Superseded by #66.
--
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
dependabot[bot] opened a new pull request, #66:
URL: https://github.com/apache/maven-doxia-sitetools/pull/66
Bumps [mockito-core](https://github.com/mockito/mockito) from 2.28.2 to
4.8.1.
Release notes
Sourced from https://github.com/mockito/mockito/releases;>mockito-core's
dependabot[bot] opened a new pull request, #256:
URL: https://github.com/apache/maven-dependency-plugin/pull/256
Bumps [mockito-core](https://github.com/mockito/mockito) from 4.8.0 to 4.8.1.
Release notes
Sourced from https://github.com/mockito/mockito/releases;>mockito-core's
[
https://issues.apache.org/jira/browse/MSHADE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622476#comment-17622476
]
Hudson commented on MSHADE-413:
---
Build succeeded in Jenkins: Maven » Maven TLP » maven-shade-plugin »
[
https://issues.apache.org/jira/browse/MSHADE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MSHADE-413:
---
Summary: Maven shade plugin enters endless loop (was: Maven share plugin
enters endless
[
https://issues.apache.org/jira/browse/MSHADE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MSHADE-413.
--
Assignee: Guillaume Nodet
Resolution: Fixed
> Maven share plugin enters endless loop
>
gnodet merged PR #124:
URL: https://github.com/apache/maven-shade-plugin/pull/124
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
[
https://issues.apache.org/jira/browse/MSHADE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MSHADE-148:
---
Fix Version/s: 3.2.2
> Shade Plugin gets stuck in infinite loop building dependency reduced
[
https://issues.apache.org/jira/browse/MSHADE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622454#comment-17622454
]
Guillaume Nodet edited comment on MSHADE-148 at 10/21/22 7:53 PM:
--
This
[
https://issues.apache.org/jira/browse/MSHADE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622454#comment-17622454
]
Guillaume Nodet edited comment on MSHADE-148 at 10/21/22 7:51 PM:
--
This
dependabot[bot] closed pull request #562: Bump mockito-core from 2.28.2 to 4.8.0
URL: https://github.com/apache/maven-surefire/pull/562
--
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
dependabot[bot] opened a new pull request, #572:
URL: https://github.com/apache/maven-surefire/pull/572
Bumps [mockito-core](https://github.com/mockito/mockito) from 2.28.2 to
4.8.1.
Release notes
Sourced from https://github.com/mockito/mockito/releases;>mockito-core's
releases.
dependabot[bot] commented on PR #562:
URL: https://github.com/apache/maven-surefire/pull/562#issuecomment-1287369670
Superseded by #572.
--
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
[
https://issues.apache.org/jira/browse/MSHADE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622454#comment-17622454
]
Guillaume Nodet commented on MSHADE-148:
This issue seems to have been fixed in
[
https://issues.apache.org/jira/browse/SUREFIRE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622401#comment-17622401
]
Václav Haisman commented on SUREFIRE-2121:
--
OK. I was too quick. It fixes the test for me but
gnodet commented on code in PR #255:
URL:
https://github.com/apache/maven-dependency-plugin/pull/255#discussion_r1002059135
##
src/main/java/org/apache/maven/plugins/dependency/analyze/AnalyzeDuplicateMojo.java:
##
@@ -151,15 +150,9 @@ private void createMessage( Set
gnodet commented on code in PR #255:
URL:
https://github.com/apache/maven-dependency-plugin/pull/255#discussion_r1002052466
##
src/main/java/org/apache/maven/plugins/dependency/analyze/AnalyzeDuplicateMojo.java:
##
@@ -151,15 +150,9 @@ private void createMessage( Set
wilx commented on PR #571:
URL: https://github.com/apache/maven-surefire/pull/571#issuecomment-1287262009
OK. I was too quick. It fixes the test for me but it breaks other parts of
surefire because of API changes in Jupiter Engine. I am not sure I know how to
deal with those.
--
ppalaga commented on PR #717:
URL: https://github.com/apache/maven-mvnd/pull/717#issuecomment-1287247495
I think both proposals boil down to having a reusable piece of
shell/PowerShell for linking/moving `mvnd` to the right file. I like that idea.
@gnodet variant would also be able to
[
https://issues.apache.org/jira/browse/MBUILDCACHE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Ashitkin updated MBUILDCACHE-25:
--
Description:
In forked executions present in build, project checksum will
[
https://issues.apache.org/jira/browse/MBUILDCACHE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Ashitkin updated MBUILDCACHE-25:
--
Description:
In forked executions present in build, project checksum will
Alexander Ashitkin created MBUILDCACHE-25:
-
Summary: Project checksum recalculated multiple time in presence
of forked executions
Key: MBUILDCACHE-25
URL:
[
https://issues.apache.org/jira/browse/MBUILDCACHE-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622364#comment-17622364
]
Alexander Ashitkin commented on MBUILDCACHE-24:
---
Please assign this ticket to me, work
[
https://issues.apache.org/jira/browse/MBUILDCACHE-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Ashitkin updated MBUILDCACHE-24:
--
Description:
Current implementation relies on lifecycle phases presence in
Alexander Ashitkin created MBUILDCACHE-24:
-
Summary: Cache cannot be processed in presence of forked executions
Key: MBUILDCACHE-24
URL: https://issues.apache.org/jira/browse/MBUILDCACHE-24
wilx opened a new pull request, #571:
URL: https://github.com/apache/maven-surefire/pull/571
This pull request updates JUnit5 dependencies including its Vintage engine
to current to fix the bug where it is unable to parse junit 4.13.2 version
number.
Following this checklist to help
Václav Haisman created SUREFIRE-2121:
Summary: Failed to parse version of junit:junit: 4.13.2
Key: SUREFIRE-2121
URL: https://issues.apache.org/jira/browse/SUREFIRE-2121
Project: Maven Surefire
[
https://issues.apache.org/jira/browse/SUREFIRE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622349#comment-17622349
]
Andreas Pabst commented on SUREFIRE-2120:
-
I had a look at this issue since I was just working
[
https://issues.apache.org/jira/browse/MNG-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622337#comment-17622337
]
Hudson commented on MNG-7566:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #114
See
gzm55 commented on PR #717:
URL: https://github.com/apache/maven-mvnd/pull/717#issuecomment-1287149373
> These changes seem to be addressing what I'd call install time concerns.
Whether the given build of mvnd native executable can run on the current
machine can be decided once at install
gnodet closed pull request #838: Fix project versions not updated during release
URL: https://github.com/apache/maven/pull/838
--
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.
gnodet commented on PR #838:
URL: https://github.com/apache/maven/pull/838#issuecomment-1287136310
Fixed by
https://github.com/apache/maven/commit/0d70f7295de75fcd00d69789a19d2866348f97bb
for the most important part. A cleanup using the BOM / dependency management
needs to follow.
--
gnodet commented on code in PR #255:
URL:
https://github.com/apache/maven-dependency-plugin/pull/255#discussion_r1001931149
##
src/main/java/org/apache/maven/plugins/dependency/analyze/AnalyzeDuplicateMojo.java:
##
@@ -151,15 +150,9 @@ private void createMessage( Set
gnodet commented on code in PR #255:
URL:
https://github.com/apache/maven-dependency-plugin/pull/255#discussion_r1001931149
##
src/main/java/org/apache/maven/plugins/dependency/analyze/AnalyzeDuplicateMojo.java:
##
@@ -151,15 +150,9 @@ private void createMessage( Set
gnodet commented on code in PR #255:
URL:
https://github.com/apache/maven-dependency-plugin/pull/255#discussion_r1001931149
##
src/main/java/org/apache/maven/plugins/dependency/analyze/AnalyzeDuplicateMojo.java:
##
@@ -151,15 +150,9 @@ private void createMessage( Set
[
https://issues.apache.org/jira/browse/MJLINK-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622320#comment-17622320
]
Sebastian Stenzel commented on MJLINK-64:
-
Not sure if this is related, but the very example that
khmarbaise commented on code in PR #255:
URL:
https://github.com/apache/maven-dependency-plugin/pull/255#discussion_r1001889182
##
src/main/java/org/apache/maven/plugins/dependency/analyze/AnalyzeDuplicateMojo.java:
##
@@ -151,15 +150,9 @@ private void createMessage( Set
gnodet commented on code in PR #255:
URL:
https://github.com/apache/maven-dependency-plugin/pull/255#discussion_r1001874458
##
src/main/java/org/apache/maven/plugins/dependency/analyze/AnalyzeDuplicateMojo.java:
##
@@ -151,15 +150,9 @@ private void createMessage( Set
gnodet commented on code in PR #255:
URL:
https://github.com/apache/maven-dependency-plugin/pull/255#discussion_r1001874458
##
src/main/java/org/apache/maven/plugins/dependency/analyze/AnalyzeDuplicateMojo.java:
##
@@ -151,15 +150,9 @@ private void createMessage( Set
gnodet commented on code in PR #255:
URL:
https://github.com/apache/maven-dependency-plugin/pull/255#discussion_r1001874458
##
src/main/java/org/apache/maven/plugins/dependency/analyze/AnalyzeDuplicateMojo.java:
##
@@ -151,15 +150,9 @@ private void createMessage( Set
[
https://issues.apache.org/jira/browse/MNG-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622312#comment-17622312
]
Hudson commented on MNG-7543:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-837 #2
See
gnodet commented on PR #717:
URL: https://github.com/apache/maven-mvnd/pull/717#issuecomment-1287030925
> These changes seem to be addressing what I'd call install time concerns.
Whether the given build of mvnd native executable can run on the current
machine can be decided once at install
nielsbasjes commented on PR #838:
URL: https://github.com/apache/maven/pull/838#issuecomment-1287022003
Sure, go for it and I'll close this 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
[
https://issues.apache.org/jira/browse/MNG-7571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622267#comment-17622267
]
Guillaume Nodet commented on MNG-7571:
--
> It would be nice to hide the Modello Velocity Plugin from
gnodet opened a new pull request, #844:
URL: https://github.com/apache/maven/pull/844
... so that it won't be shown in the API documentation
--
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
gnodet commented on PR #838:
URL: https://github.com/apache/maven/pull/838#issuecomment-1286963027
@nielsbasjes do you mind if I do the changes locally, that's really a nasty
problem and should be fixed asap imho.
--
This is an automated message from the Apache Git Service.
To respond to
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622250#comment-17622250
]
ASF GitHub Bot commented on MNG-7038:
-
gnodet commented on PR #840:
URL:
gnodet commented on PR #840:
URL: https://github.com/apache/maven/pull/840#issuecomment-1286950230
> * check parent of current (non-effective) pom
> * if it has relative path being non empty, check the given path
> * check recursively until no more relative path is set/not found
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622242#comment-17622242
]
ASF GitHub Bot commented on MNG-7038:
-
gnodet commented on PR #840:
URL:
gnodet commented on PR #840:
URL: https://github.com/apache/maven/pull/840#issuecomment-1286933973
I fully agree to have a new `${project.topdir}` that won't go outside of the
tree.
For the `${project.topdir}/.mvn/settings.xml` use case, I'm not sure how
that could be handled if
pzygielo opened a new pull request, #153:
URL: https://github.com/apache/maven-compiler-plugin/pull/153
Following this checklist to help us incorporate your
contribution quickly and easily:
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MCOMPILER)
gnodet commented on code in PR #117:
URL:
https://github.com/apache/maven-plugin-tools/pull/117#discussion_r1001740948
##
maven-plugin-tools-annotations/src/main/java/org/apache/maven/tools/plugin/extractor/annotations/scanner/MojoAnnotationsScanner.java:
##
@@ -37,13 +37,21
cstamas commented on PR #205:
URL: https://github.com/apache/maven-indexer/pull/205#issuecomment-1286900272
superseded by https://github.com/apache/maven-indexer/pull/255
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
[
https://issues.apache.org/jira/browse/MNG-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1763#comment-1763
]
ASF GitHub Bot commented on MNG-7569:
-
kwin opened a new pull request, #842:
URL:
kwin opened a new pull request, #842:
URL: https://github.com/apache/maven/pull/842
Improve descriptions
Add anchors
[MNG-7575] Remove deprecated requiresReports
Relax validation of "configuration" by marking it as "DOM"
Following this checklist to help us incorporate your
[
https://issues.apache.org/jira/browse/MNG-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned MNG-7569:
Assignee: Konrad Windszus
> Plugin descriptor model should contain all elements understood
[
https://issues.apache.org/jira/browse/MNG-7575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned MNG-7575:
Assignee: Konrad Windszus
> Remove deprecated elements from plugin descriptor
>
cstamas opened a new pull request, #255:
URL: https://github.com/apache/maven-indexer/pull/255
This change (ingesting GZIP files raw records into Lucene index on multiple
threads) on my PC halves the execution time: while BasicUsageExample on master
takes over 15 minutes to finish (when
cstamas closed pull request #205: [MINDEXER-151] Proof of concept
URL: https://github.com/apache/maven-indexer/pull/205
--
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
ppalaga commented on PR #717:
URL: https://github.com/apache/maven-mvnd/pull/717#issuecomment-1286855833
These changes seem to be addressing what I'd call install time concerns.
Whether the given build of mvnd native executable can run on the current
machine can be decided once at install
marcphilipp commented on issue #725:
URL: https://github.com/apache/maven-mvnd/issues/725#issuecomment-1286834546
The Gradle team is currently working on making the extension compatible with
the Maven daemon. So far we haven't hit any road blocks.
--
This is an automated message from the
Herve Boutemy created DOXIASITETOOLS-269:
Summary: get insight into existing static site generators
Key: DOXIASITETOOLS-269
URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-269
ppalaga commented on PR #722:
URL: https://github.com/apache/maven-mvnd/pull/722#issuecomment-1286749932
> I'm OK to the switch, and it is reasonable for a package manager to always
to call the native image. In this pr, we can focus on providing the fallback
function, keeping the most
[
https://issues.apache.org/jira/browse/MSHADE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MSHADE-430.
--
Resolution: Fixed
> Remove usage of deprecated ModelBase#getReports()
>
[
https://issues.apache.org/jira/browse/MNG-7571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622166#comment-17622166
]
Guillaume Nodet commented on MNG-7571:
--
It would be nice to hide the Modello Velocity Plugin from the
nielsbasjes commented on code in PR #838:
URL: https://github.com/apache/maven/pull/838#discussion_r1001600141
##
maven-model/pom.xml:
##
@@ -37,16 +37,22 @@ under the License.
org.apache.maven
maven-api-model
- 4.0.0-alpha-3-SNAPSHOT
+
[
https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622159#comment-17622159
]
ASF GitHub Bot commented on MNG-6609:
-
kwin commented on code in PR #835:
URL:
kwin commented on code in PR #835:
URL: https://github.com/apache/maven/pull/835#discussion_r1001597973
##
maven-model-builder/src/main/java/org/apache/maven/model/profile/ProfileActivationContext.java:
##
@@ -30,6 +30,12 @@
*/
public interface ProfileActivationContext
{
+
[
https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622155#comment-17622155
]
ASF GitHub Bot commented on MNG-6609:
-
gnodet commented on code in PR #835:
URL:
gnodet commented on code in PR #835:
URL: https://github.com/apache/maven/pull/835#discussion_r1001591928
##
maven-model-builder/src/main/java/org/apache/maven/model/profile/ProfileActivationContext.java:
##
@@ -30,6 +30,12 @@
*/
public interface ProfileActivationContext
{
gnodet commented on code in PR #838:
URL: https://github.com/apache/maven/pull/838#discussion_r1001585461
##
maven-model/src/test/resources/xml/pom.xml:
##
@@ -37,12 +37,12 @@ under the License.
org.apache.maven
maven-api-model
- 4.0.0-alpha-1-SNAPSHOT
[
https://issues.apache.org/jira/browse/MNG-7576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622150#comment-17622150
]
ASF GitHub Bot commented on MNG-7576:
-
gnodet opened a new pull request, #841:
URL:
gnodet opened a new pull request, #841:
URL: https://github.com/apache/maven/pull/841
Restore `ModelReader` compatibility which had been switched to new api too
soon...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
[
https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622137#comment-17622137
]
ASF GitHub Bot commented on MNG-6609:
-
kwin commented on PR #835:
URL:
[
https://issues.apache.org/jira/browse/MNG-7576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-7576:
-
Description: {{MavenBuildTimestamp}}
kwin commented on PR #835:
URL: https://github.com/apache/maven/pull/835#issuecomment-1286667062
Agreed, it is kind of a workaround, but given that I think it is consensus
to stick with POM 4.0 for Maven 4 this is the only near term solution I could
come up with.
--
This is an automated
[
https://issues.apache.org/jira/browse/MNG-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622135#comment-17622135
]
ASF GitHub Bot commented on MNG-6609:
-
gnodet commented on PR #835:
URL:
Guillaume Nodet created MNG-7576:
Summary: Restore compatibility with maven 3
Key: MNG-7576
URL: https://issues.apache.org/jira/browse/MNG-7576
Project: Maven
Issue Type: Task
Affects
gnodet commented on PR #835:
URL: https://github.com/apache/maven/pull/835#issuecomment-1286665218
That really looks like a hack to avoid defining a new activation type to me.
Shouldn't we extend the model to add a packaging based activation ?
--
This is an automated message from the
gzm55 opened a new pull request, #726:
URL: https://github.com/apache/maven-mvnd/pull/726
With the new property set to `true`, the prefix `[INFO] [stdout] ` is
removed in the client terminal output. Then without `--raw-stream`, we can
still get the same behavior with original maven.
--
gzm55 commented on issue #725:
URL: https://github.com/apache/maven-mvnd/issues/725#issuecomment-1286630197
the binding of MavenPluginManager is fixed in the
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622108#comment-17622108
]
ASF GitHub Bot commented on MNG-7038:
-
kwin commented on PR #840:
URL:
kwin commented on PR #840:
URL: https://github.com/apache/maven/pull/840#issuecomment-1286627143
> This also means the (internal) maven.multiModuleProjectDirectory suffers
from the same problem
This is internal for a good reason and should only be used for finding the
`.mvn`
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622106#comment-17622106
]
ASF GitHub Bot commented on MNG-7038:
-
nielsbasjes commented on PR #840:
URL:
nielsbasjes commented on PR #840:
URL: https://github.com/apache/maven/pull/840#issuecomment-1286625160
This also means the (internal) `maven.multiModuleProjectDirectory` suffers
from the same problem: It may traverse outside of the project root. This will
also cause problems if people
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622101#comment-17622101
]
Konrad Windszus edited comment on MNG-7038 at 10/21/22 8:13 AM:
I think
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622102#comment-17622102
]
ASF GitHub Bot commented on MNG-7038:
-
nielsbasjes commented on PR #840:
URL:
nielsbasjes commented on PR #840:
URL: https://github.com/apache/maven/pull/840#issuecomment-1286619888
@kwin You are right.
That is probably a lot better, also because this code in init will travel
outside of the project and even the homedirectory of the user to find the
`.mvn`
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622101#comment-17622101
]
Konrad Windszus commented on MNG-7038:
--
I think this needs further clarification. What should the
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622090#comment-17622090
]
ASF GitHub Bot commented on MNG-7038:
-
kwin commented on PR #840:
URL:
kwin commented on PR #840:
URL: https://github.com/apache/maven/pull/840#issuecomment-1286597191
> I found in the
[init](https://github.com/apache/maven/blob/18eff3baeb899ddd27b34635c8f0d7e47f5c027b/apache-maven/src/assembly/shared/init#L33)
script there is something called basedir
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622079#comment-17622079
]
ASF GitHub Bot commented on MNG-7038:
-
nielsbasjes commented on PR #840:
URL:
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622078#comment-17622078
]
ASF GitHub Bot commented on MNG-7038:
-
nielsbasjes opened a new pull request, #840:
URL:
nielsbasjes commented on PR #840:
URL: https://github.com/apache/maven/pull/840#issuecomment-1286589500
Sidenote: I found in the
[init](https://github.com/apache/maven/blob/18eff3baeb899ddd27b34635c8f0d7e47f5c027b/apache-maven/src/assembly/shared/init#L33)
script there is something called
nielsbasjes opened a new pull request, #840:
URL: https://github.com/apache/maven/pull/840
[MNG-7038: Introduce public property to point to a root directory of
(multi-module) project.](https://issues.apache.org/jira/browse/MNG-7038)
This pull request simply introduces the new
gnodet commented on PR #204:
URL:
https://github.com/apache/maven-integration-testing/pull/204#issuecomment-1286572906
> @gnodet I was waiting for approval but merged it now!
Maybe I'm wrong, but I assumed that when someone approves a PR on `maven`,
the related PR on the ITs is
1 - 100 of 113 matches
Mail list logo
