Le lun. 12 juin 2023 à 01:36, Guillaume Nodet a écrit :
> Le dim. 11 juin 2023 à 23:12, Romain Manni-Bucau a
> écrit :
>
> >
> >
> > Le dim. 11 juin 2023 à 22:28, Guillaume Nodet a
> > écrit :
> >
> >> Those are actually two different questions, but I'd like to raise those
> >> together, since
Le dim. 11 juin 2023 à 23:54, Hervé Boutemy a
écrit :
> Le vendredi 9 juin 2023, 11:22:26 CEST Guillaume Nodet a écrit :
> > Le ven. 9 juin 2023 à 08:59, Hervé Boutemy a
> écrit :
> > > adding a new POM element in build POM was supposed to be something for
> > > Maven 5
> > > and to trigger a PO
Isn't the schema named in the POM document itself? Can't we just allow use of
"extended" (read backwards compatible) schemas as the POM is versioned? Then
if/once a specific schema for a use case becomes popular it can be added to
parsers as the required version if needed. Or perhaps that's
Le dim. 11 juin 2023 à 23:12, Romain Manni-Bucau a
écrit :
>
>
> Le dim. 11 juin 2023 à 22:28, Guillaume Nodet a
> écrit :
>
>> Those are actually two different questions, but I'd like to raise those
>> together, since they do affect the same feature.
>>
>> 1/ We currently don't have an XML sche
Le dimanche 11 juin 2023, 23:31:36 CEST Hunter C Payne a écrit :
> Strange question but maybe it will inspire someone else. Why does the POM
> the user uses to control the build the exact same format as the POMs
> created to express the results of the build? Is that necessary?
it has been done i
wow, what a release!
+1
Reproducible build ok
Regards,
Hervé
Le dimanche 11 juin 2023, 19:02:05 CEST Slawomir Jaranowski a écrit :
> Hi,
>
> We solved 25 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&ve
> rsion=12352680
>
> Commits:
> https://github.com/
Le vendredi 9 juin 2023, 11:22:26 CEST Guillaume Nodet a écrit :
> Le ven. 9 juin 2023 à 08:59, Hervé Boutemy a écrit :
> > adding a new POM element in build POM was supposed to be something for
> > Maven 5
> > and to trigger a POM 5 version, to make clear that we are leaving the
> > Maven 3
> > s
Strange question but maybe it will inspire someone else. Why does the POM the
user uses to control the build the exact same format as the POMs created to
express the results of the build? Is that necessary? It seems to me the
discussion is about the drawbacks of that approach. Perhaps its n
+1
niedz., 11 cze 2023 o 22:16 Tamás Cservenák
napisał(a):
> +1
>
> On Sun, Jun 11, 2023, 22:14 Michael Osipov wrote:
>
> > Hi,
> >
> > we solved 17 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121&version=12350597
> >
> > There are still a couple of i
Le dim. 11 juin 2023 à 22:28, Guillaume Nodet a écrit :
> Those are actually two different questions, but I'd like to raise those
> together, since they do affect the same feature.
>
> 1/ We currently don't have an XML schema for the build POM. One
> possibility would be to relax a bit the const
Those are actually two different questions, but I'd like to raise those
together, since they do affect the same feature.
1/ We currently don't have an XML schema for the build POM. One
possibility would be to relax a bit the constraints on the main POM schema (
http://maven.apache.org/xsd/maven-4
+1
On Sun, Jun 11, 2023, 22:14 Michael Osipov wrote:
> Hi,
>
> we solved 17 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121&version=12350597
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MWAR/issues
>
> Stagin
Hi,
we solved 17 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121&version=12350597
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MWAR/issues
Staging repo:
https://repository.apache.org/content/repositories/maven-1955/
h
+1
Le dim. 11 juin 2023 à 19:02, Slawomir Jaranowski
a écrit :
> Hi,
>
> We solved 25 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12352680
>
> Commits:
> https://github.com/apache/maven-apache-parent/compare/apache-29...apache-30
>
> Staging repo
+1
niedz., 11 cze 2023, 19:15 użytkownik Tamás Cservenák
napisał:
> +1
>
> On Sun, Jun 11, 2023 at 7:02 PM Slawomir Jaranowski <
> s.jaranow...@gmail.com>
> wrote:
>
> > Hi,
> >
> > We solved 25 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=1
Hi,
we solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525&version=12353076
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINVOKER%20AND%20resolution%20%3D%20Unresolved
Staging repo:
https://rep
+1
On Sun, Jun 11, 2023 at 7:02 PM Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 25 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12352680
>
> Commits:
> https://github.com/apache/maven-apache-parent/compare/apache-29...apache-30
>
> Staging repo:
Am 2023-06-11 um 19:02 schrieb Slawomir Jaranowski:
Hi,
We solved 25 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12352680
Commits:
https://github.com/apache/maven-apache-parent/compare/apache-29...apache-30
Staging repo:
https://repository.apache.o
Hi,
We solved 25 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12352680
Commits:
https://github.com/apache/maven-apache-parent/compare/apache-29...apache-30
Staging repo:
https://repository.apache.org/content/repositories/orgapacheapache-1035/
https://
19 matches
Mail list logo
