I agree with a lot of what has been said towards keeping modello in use. There
is really no existing drop-in alternative. The benefits of moving off
Modello are mostly unknown until we actually do the work. And in the end it
should be mostly internal refactoring.
However that work is a very la
asfgit closed pull request #51:
URL: https://github.com/apache/maven-site-plugin/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 the specific comment.
For queries about this service, p
dependabot[bot] commented on pull request #51:
URL: https://github.com/apache/maven-site-plugin/pull/51#issuecomment-854228833
OK, I won't notify you again about this release, but will get in touch when
a new version is available. You can also ignore all major, minor, or patch
releases for
cstamas edited a comment on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-854121719
Note to myself: I'd do one more thing in this PR: move out things into own
packages (the "provider" ones), as currently all I did is just move out things
in
cstamas edited a comment on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-854121719
Note to myself: I'd do one more thing in this PR: move out things into own
packages (the "provider" ones), as currently all I did is just move out things
in
cstamas edited a comment on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-854121719
Note to myself: I'd do one more thing in this PR: move out things into own
packages (the "provider" ones), as currently all I did is just move out things
in
cstamas edited a comment on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-854121719
Note to myself: I'd do one more thing in this PR: move out things into own
packages (the "provider" ones), as currently all I did is just move out things
in
cstamas edited a comment on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-854121719
Note to myself: I'd do one more thing in this PR: move out things into own
packages (the "provider" ones), as currently all I did is just move out things
in
cstamas commented on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-854121719
Note to myself: I'd do one more thing in this PR: move out things into own
packages (the "provider" ones), as currently all I did is just move out things
in their p
cstamas commented on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-854119930
@slachiewicz cool, thanks for testing, maybe drop here some more plugins
that use m-a-t and have nice IT suite, so I could test some of those as well...
--
This i
elharo merged pull request #238:
URL: https://github.com/apache/maven-site/pull/238
--
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
elharo opened a new pull request #238:
URL: https://github.com/apache/maven-site/pull/238
@slachiewicz
--
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 th
elharo commented on a change in pull request #237:
URL: https://github.com/apache/maven-site/pull/237#discussion_r644745845
##
File path: content/markdown/repository-management.md
##
@@ -58,6 +58,7 @@ and the features provided by these products.
* https://www.cloudrepo.io"; ta
Le jeu. 3 juin 2021 à 13:24, Gary Gregory a écrit :
> Wouldn't the first step to move from XPP3 to a standard API?
>
Don't think it is something we can target for maven 4/5, will break too
much the ecosystem requiring users to use a maven wrapper solution which is
always a sign of a fragile buil
Wouldn't the first step to move from XPP3 to a standard API?
Gary
On Thu, Jun 3, 2021, 03:13 Markus Karg wrote:
> In the very long term I would be +1 for JAXB, as clearly much more Java
> programmers on earth are used to JAXB than with Modello due to it being a
> former part of the JRE. It now
asfgit closed pull request #212:
URL: https://github.com/apache/maven-site/pull/212
--
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
slachiewicz closed pull request #37:
URL: https://github.com/apache/maven-site/pull/37
--
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, ple
asfgit closed pull request #222:
URL: https://github.com/apache/maven-site/pull/222
--
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
slachiewicz commented on a change in pull request #237:
URL: https://github.com/apache/maven-site/pull/237#discussion_r644551072
##
File path: content/markdown/repository-management.md
##
@@ -58,6 +58,7 @@ and the features provided by these products.
* https://www.cloudrepo.io
slachiewicz merged pull request #237:
URL: https://github.com/apache/maven-site/pull/237
--
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, p
In the very long term I would be +1 for JAXB, as clearly much more Java
programmers on earth are used to JAXB than with Modello due to it being a
former part of the JRE. It now is open source at the Eclipse Foundation, so we
all can contribute to it, which could make it a success story.
But I am
21 matches
Mail list logo
