michael-o commented on a change in pull request #212:
URL: https://github.com/apache/maven-site/pull/212#discussion_r510405068
##
File path: content/apt/guides/mini/guide-http-settings.apt
##
@@ -30,31 +30,13 @@ Advanced Configuration of the HttpClient HTTP Wagon
%{toc}
michael-o commented on a change in pull request #212:
URL: https://github.com/apache/maven-site/pull/212#discussion_r512874854
##
File path: content/apt/guides/mini/guide-http-settings.apt
##
@@ -33,28 +33,28 @@ Advanced Configuration of the HttpClient HTTP Wagon
You can
elharo commented on a change in pull request #212:
URL: https://github.com/apache/maven-site/pull/212#discussion_r512861684
##
File path: content/apt/guides/mini/guide-http-settings.apt
##
@@ -33,28 +33,28 @@ Advanced Configuration of the HttpClient HTTP Wagon
You can use
michael-o commented on a change in pull request #212:
URL: https://github.com/apache/maven-site/pull/212#discussion_r512876692
##
File path: content/apt/guides/mini/guide-http-settings.apt
##
@@ -88,7 +88,7 @@ the target server's authentication.
problems with HTTP servers and
sparsick opened a new pull request #222:
URL: https://github.com/apache/maven-site/pull/222
This setting file was created by importing checkstyle settings in idea. Then
I compared it with @bmarwell self-created Intellji setting file for Maven
projects and add his XML code settings.
michael-o commented on a change in pull request #191:
URL: https://github.com/apache/maven-site/pull/191#discussion_r549468517
##
File path:
content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
##
@@ -174,9 +174,10 @@ Introduction to the Dependency
sparsick commented on pull request #222:
URL: https://github.com/apache/maven-site/pull/222#issuecomment-751847950
@slawekjaranowski Thanks for reviewing
This is an automated message from the Apache Git Service.
To respond
slawekjaranowski commented on a change in pull request #222:
URL: https://github.com/apache/maven-site/pull/222#discussion_r549464651
##
File path: content/resources/developers/maven-idea-codestyle.xml
##
@@ -216,17 +79,34 @@ under the License.
+
+
+
elharo commented on a change in pull request #222:
URL: https://github.com/apache/maven-site/pull/222#discussion_r549498982
##
File path: content/resources/developers/maven-idea-codestyle.xml
##
@@ -16,186 +16,49 @@ KIND, either express or implied. See the License for the
mthmulders commented on pull request #222:
URL: https://github.com/apache/maven-site/pull/222#issuecomment-751827068
I don't know what the current style guidelines are, so I cannot really
review. But I'm definitely +1 for maintaining it in configuration files so we
can all easily conform
slawekjaranowski commented on a change in pull request #222:
URL: https://github.com/apache/maven-site/pull/222#discussion_r549502187
##
File path: content/resources/developers/maven-idea-codestyle.xml
##
@@ -16,186 +16,49 @@ KIND, either express or implied. See the License
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r549926035
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r549927249
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
asfgit closed pull request #48:
URL: https://github.com/apache/maven-doxia/pull/48
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
asfgit closed pull request #47:
URL: https://github.com/apache/maven-doxia/pull/47
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
philsttr edited a comment on pull request #223:
URL: https://github.com/apache/maven-site/pull/223#issuecomment-752319875
@slachiewicz , since [all the other
guides](https://github.com/apache/maven-site/tree/master/content/apt/guides)
are in apt, I'd rather keep this one in apt for
philsttr commented on pull request #223:
URL: https://github.com/apache/maven-site/pull/223#issuecomment-752319875
@slachiewicz , since all the other guides are in apt, I'd rather keep this
one in apt for consistency. I'm focused on the content for now. If it is
indeed important to
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r549926099
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
michael-o commented on pull request #223:
URL: https://github.com/apache/maven-site/pull/223#issuecomment-752641357
>
>
> @slachiewicz , since [all the other
guides](https://github.com/apache/maven-site/tree/master/content/apt/guides)
are in apt, I'd rather keep this one in apt
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550308234
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550285056
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
michael-o commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550299955
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550285056
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
philsttr opened a new pull request #223:
URL: https://github.com/apache/maven-site/pull/223
Suggested by @michael-o via
https://github.com/apache/maven-deploy-plugin/pull/15#issuecomment-750933613
This is an automated
bertysentry opened a new pull request #49:
URL: https://github.com/apache/maven-doxia/pull/49
Broad update to **doxia-module-markdown**
* Properly exposed language class in fenced code blocks
* Re-implemented metadata processing
* Added unit tests
* Added integration tests
slachiewicz closed pull request #21:
URL: https://github.com/apache/maven-artifact-transfer/pull/21
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
slachiewicz commented on pull request #20:
URL:
https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752469411
Do we have anywhere documented this recommendation? I think we still have on
wiki to use this artefact.
Also with this changes we can easily switch to new
rfscholte commented on pull request #20:
URL:
https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752440522
Please don't do this. The intention of maven-artifact-transfer is a bridge
to any Aether implementation.
rfscholte commented on pull request #20:
URL:
https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752454346
Sorry @slachiewicz if you've spend a lot of time on this, but I need to
close this. Once everything is using Maven 3.1+ we can simply archive
rfscholte closed pull request #20:
URL: https://github.com/apache/maven-artifact-transfer/pull/20
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
rfscholte commented on pull request #20:
URL:
https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752506877
I still consider adding the `org.apache.maven.shared.transfer.project`
package a bad choice, because it introduces a dependency on Maven.
michael-o commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550214607
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
khmarbaise commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550224261
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
michael-o commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550329282
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550377021
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550376753
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550376789
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550376753
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
michael-o commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550452528
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
asfgit closed pull request #223:
URL: https://github.com/apache/maven-site/pull/223
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
bertysentry opened a new pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34
* Fixed integration tests for **doxia-formats* wrt fenced code blocks
* Upgraded to Doxia 1.10-SNAPSHOT
This is an
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-753665247
@michael-o Please note:
* I upgraded to Doxia 1.10-SNAPSHOT (not sure you wanted this here, just let
me know)
* I wondered whether we should actually remove
michael-o commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-753673025
Thanks, will look into it.
This is an automated message from the Apache Git Service.
To respond to the
michael-o commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-753697914
I won't merge before anyway because I never depend on snapshots.
This is an automated message from the
elharo commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-754589531
I think I agree that these should be moved. If they're only testing doxia
functionality, and we can test them in doxia, then that's better. Or perhaps
tests belong in both
elharo closed pull request #51:
URL: https://github.com/apache/maven-doxia/pull/51
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
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-754944421
@hboutemy We will keep some integration tests in *maven-site-plugin* that
involve *doxia-module-markdown*. I want to remove specific Doxia tests (like
"quotes were
bertysentry edited a comment on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-754944421
@hboutemy We will keep some integration tests in *maven-site-plugin* that
involve *doxia-module-markdown*. I want to remove specific Doxia tests (like
"quotes
hboutemy commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-754936536
is it causing issues, so they *need* to be removed?
if you're sure you have sufficient tests nowadays in Doxia, Doxia Sitetools
and skins to check that a new feature
bertysentry opened a new pull request #52:
URL: https://github.com/apache/maven-doxia/pull/52
* doxia-module-markdown: Re-incorporated integration tests from
**maven-site-plugin**
* doxia-module-markdown: Merged DOXIA-616 integration tests into **general**
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-754969798
Submitted PR for Doxia: https://github.com/apache/maven-doxia/pull/52
Thank you!
This is an
michael-o commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-754273143
In my opinion they need to bemoved because we test the entire site
generation, and not Doxia specific modules. @hboutemy WDYT?
mthmulders opened a new pull request #225:
URL: https://github.com/apache/maven-site/pull/225
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
slawekjaranowski commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553961399
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -100,9 +100,11 @@ Introduction to Build Profiles
profile
slawekjaranowski commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553964597
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal
slawekjaranowski commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553964597
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal
mthmulders commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553966399
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
elharo closed pull request #53:
URL: https://github.com/apache/maven-doxia/pull/53
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
mthmulders commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553965389
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -100,9 +100,11 @@ Introduction to Build Profiles
profile IDs to
michael-o commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554041608
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
MartinKanters commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554058099
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
pzygielo commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554014876
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
michael-o commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553996067
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
michael-o commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554064780
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
MartinKanters commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554007128
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
mthmulders commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554024978
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
pzygielo commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554014876
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
slawekjaranowski commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553961399
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -100,9 +100,11 @@ Introduction to Build Profiles
profile
michael-o commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553996067
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
mthmulders commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r553965389
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -100,9 +100,11 @@ Introduction to Build Profiles
profile IDs to
elharo closed pull request #53:
URL: https://github.com/apache/maven-doxia/pull/53
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
MartinKanters commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554007128
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
rfscholte commented on a change in pull request #225:
URL: https://github.com/apache/maven-site/pull/225#discussion_r554558015
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -307,7 +309,7 @@ mvn groupId:artifactId:goal -Denvironment=test
strkkk opened a new pull request #35:
URL: https://github.com/apache/maven-site-plugin/pull/35
Example is not good since self-closing tag wont work, so it is changed to
correct example.
See
michael-o merged pull request #35:
URL: https://github.com/apache/maven-site-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
dependabot[bot] opened a new pull request #55:
URL: https://github.com/apache/maven-doxia/pull/55
Bumps fop from 2.5 to 2.6.
[![Dependabot compatibility
elharo merged pull request #55:
URL: https://github.com/apache/maven-doxia/pull/55
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
bertysentry edited a comment on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-760137856
More build failures: Connection timeout with www.w3.org, which is totally
unrelated to this PR.
Edit: Things run smoothly on my fork. See
elharo commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-760160299
We really should resolve the CI issues before proceeding with this or any
other changes.
This is an
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-760182619
@elharo IMO there is no need to wait to merge this PR. This PR ensures the
integration tests won't break when upgrading to Doxia 1.10.
The integration tests
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-760137856
More build failures: Connection timeout with www.w3.org, which is totally
unrelated to this PR.
This
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-760124289
Oh, last update: I reverted Doxia version to **1.9.1**. MSITE integration
tests will pass with both 1.9.1 and 1.10 (no more checks on specific Doxia
formatting
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-760381651
@elharo Any idea on how to retrieve the **build.log** files from GitHub
Actions/Workflows? I must be missing something here, but I can't find any link
to any
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-766418215
@michael-o @hboutemy @elharo Friendly reminder that this PR is still
waiting, and its content is not going to change with regards to the failed
builds, which are
michael-o commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-766434017
I won't be able to review before mid Feb due to circumstances here.
This is an automated message from
slachiewicz commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-766441620
I'll look at it tomorrow
This is an automated message from the Apache Git Service.
To respond to the
elharo merged pull request #55:
URL: https://github.com/apache/maven-doxia/pull/55
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
mabrarov commented on pull request #10:
URL: https://github.com/apache/maven-archiver/pull/10#issuecomment-763180478
Is this PR still actual?
This is an automated message from the Apache Git Service.
To respond to the
elharo commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-762430570
That one wasn't merged by me. :-)
This is an automated message from the Apache Git Service.
To respond to
michael-o commented on pull request #10:
URL: https://github.com/apache/maven-archiver/pull/10#issuecomment-763471268
Likely, @hboutemy WDYT?
This is an automated message from the Apache Git Service.
To respond to the
elharo closed pull request #10:
URL: https://github.com/apache/maven-archiver/pull/10
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
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-759814944
Okay, PR has been updated as below:
* Removed Doxia-specific integration tests
* Added integration tests on the various document formats
* Integration tests on
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-762494128
One recurring error is:
```log
Error: |[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.10.0-SNAPSHOT:site (default-cli)
on
elharo commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-762208210
Some though not all of the errors seem related to this:
: |[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.10.0-SNAPSHOT:site
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-762209071
This was just a temporary network issue of GitHub Actions. If you re-run the
workflow, you won't get these errors.
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-762210778
Also, PR #35 just got merged to *master* 3 days ago, with the same CI
failures.
This is an automated
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-762187924
@hboutemy @michael-o @elharo Will you have a chance to review these changes?
This ensures the **maven-site-plugin** integration tests don't break when
upgrading from
elharo commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-762197773
Before this can move further, someone needs to debug and fix the CI
failures. That's likely not caused by this PR, but checking in when the CI is
broken is never a good
bertysentry commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-762198733
@elharo We cannot access the integration test logs, how are we going to fix
this?
This is an
elharo commented on pull request #34:
URL: https://github.com/apache/maven-site-plugin/pull/34#issuecomment-762205983
It might need someone who has more permissions on the project. I'm not sure.
This is an automated message
601 - 700 of 1543 matches
Mail list logo
