I agree that dropping modello means using JAXB but it will likely be a
transitive breaking change, ie drop xpp3 too and sadly XPP3 is part of the
maven API and used a lot in extensions and mojo because it enables to
programmatically handle the mojo configuration.
I'd really be to move to an XSD fir
> - For some time, JAXB has been bundled with the JRE.
> As of this writing, this still applies to Java 8.
>In Java 9, and 10, there's --add-modules=java.xml.bind.
> As of Java 11, it has been removed from the JDK.
> I'd consider that to be a migration problem.
You can just include jaxb-a
On Wed, Jun 2, 2021 at 2:38 PM Gary Gregory wrote:
>
> On Wed, Jun 2, 2021 at 8:30 AM Jochen Wiedmann
> wrote:
> >
> > On Wed, Jun 2, 2021 at 1:02 PM Elliotte Rusty Harold
> > wrote:
> >
> > > What do folks think about slowly moving away from Modello where
> > > feasible to simplify the build?
The title suggest it should me moved completely from the Maven codebase, but I
think there's no alternative for Maven Core, as we need quite a huge set of
features. I don't think there's another tool that can keep the model, reader,
writers, mergers, validators and xsd in sync. If you want to re
I don't get how Modello got in your way on these issues: please explain
And it works perfectly on Eclipse: there is a m2e extension for Modello that
does the job.
from a Modello model, we generate:
- Java objects
- serializers and deserializers: there are other options for some APIs, but
not for
Hi Guillaume,
[3] is definitely different from your original problem, but it should
explain (together with [2]) why [1] did not remove the second "compile" in
your problem case.
I wanted to understand why MNG-6566 didn't apply to it. I agree that if it
would have applied (removing 2nd compile in "
On Wed, Jun 2, 2021 at 8:30 AM Jochen Wiedmann
wrote:
>
> On Wed, Jun 2, 2021 at 1:02 PM Elliotte Rusty Harold
> wrote:
>
> > What do folks think about slowly moving away from Modello where
> > feasible to simplify the build? Does anyone find Modello a net
> > positive, especially in longterm ma
On Wed, Jun 2, 2021 at 1:02 PM Elliotte Rusty Harold wrote:
> What do folks think about slowly moving away from Modello where
> feasible to simplify the build? Does anyone find Modello a net
> positive, especially in longterm maintenance, not just in initial code
> generation?
To me, it sounds f
I was looking into
https://issues.apache.org/jira/projects/DOXIATOOLS/issues/DOXIATOOLS-68
and https://issues.apache.org/jira/projects/DOXIATOOLS/issues/DOXIATOOLS-67
when Modello got in my way. So I tried a little experiment to see how
hard it would be to rip Modello out of a project. Result: not
michael-o commented on a change in pull request #237:
URL: https://github.com/apache/maven-site/pull/237#discussion_r643848235
##
File path: content/markdown/repository-management.md
##
@@ -58,6 +58,7 @@ and the features provided by these products.
* https://www.cloudrepo.io";
elharo commented on a change in pull request #237:
URL: https://github.com/apache/maven-site/pull/237#discussion_r643820250
##
File path: content/markdown/repository-management.md
##
@@ -58,6 +58,7 @@ and the features provided by these products.
* https://www.cloudrepo.io"; ta
whatatripp opened a new 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 servi
slachiewicz commented on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-852881088
tested with m-dependency-plugin, works OOB
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
dependabot[bot] closed pull request #38:
URL: https://github.com/apache/maven-artifact-transfer/pull/38
--
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
dependabot[bot] commented on pull request #38:
URL:
https://github.com/apache/maven-artifact-transfer/pull/38#issuecomment-852852394
Looks like actions/cache is up-to-date now, so this is no longer needed.
--
This is an automated message from the Apache Git Service.
To respond to the mes
michael-o commented on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-852851846
I will check when I can...
--
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
michael-o commented on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-852847100
I will check when I can...
--
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
cstamas commented on pull request #24:
URL:
https://github.com/apache/maven-artifact-transfer/pull/24#issuecomment-852822569
Um, anyone?
--
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 spe
18 matches
Mail list logo
