Hi,
I would appreciate some cleanup of the branches after
https://issues.apache.org/jira/browse/MPLUGIN-523.
I see now
1) master
2) mvn4
3) maven-plugin-tools-3.7.x
4) maven-plugin-tools-3.x
IIUC only 1 and 4 is relevant.
Also in 1) I see a lot of code not relevant for v4 plugins like
-
http
Hi,
I'm try to build site in maven-parent with new version
mvn clean site -f docs -Dversion.maven-site-plugin=3.20.0 -Papache-stage -e
- apache-stage - my profile with staging repo ...
I have:
[WARNING] Site model of 'org.apache.maven:docs:pom:44-SNAPSHOT' for default
locale is still using the
Howdy,
as am going over multiple plugins (as it is time to upgrade parent, some
bugfix, etc), all I see is:
* a LOT of code duplication across plugins (some even have comments like in
plugin X "this should be shared with Y")
* some "forcefully" pushed out "shared" artifact to share them across
* j
Hi,
Although I do see the benefits from a Maven Dev perspective for Consumers this
is worse.
In the past often individual plugin versions suffered from regressions for
certain edge cases.
Having individual separate plugins allowed consumers to deliberately use an old
version of one plugin (e.g
The concrete example I suffered from was
https://issues.apache.org/jira/browse/MRESOURCES-289 which forced me to stay on
3.1.0
(https://github.com/apache/jackrabbit-filevault-package-maven-plugin/blob/58ef9f5f28d8e54c4d26d35011b1caff570a1b1d/pom.xml#L111-L115).
> On 15. Aug 2024, at 13:35, Konr
Hi,
We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12344384
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20ma
As an outsider I would welcome that especially if it (1) made it simpler to
write new plug-ins and/or (2) I would get new features or bug fixes "for
free" if my plug-ins reused the right superclass or class.
2c,
Gary
On Thu, Aug 15, 2024, 7:15 AM Tamás Cservenák wrote:
> Howdy,
>
> as am going
I would think the benefit of having a single plugin would be to have faster
release cycles, as the amount of work for a single release is quite
important imho. So having a single release cycle would lower the ration
work/ nb mojos.
That said, I think that could also be achieved by using a reactor
+1
czw., 15 sie 2024, 14:12 użytkownik Slawomir Jaranowski <
s.jaranow...@gmail.com> napisał:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12344384
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache
I think the main problem is that "maven-core" is often rejecting request
for providing useful things in the first place.
That leads to all kind of "helper", "util", ... so maybe instead of
having a maven-core-plugin, it would better to have a maven-plugin-core
module (what of course can for ex
For me, if it's only dependency updates or matching versions of sibling
jars, it's a valuable new release because it says "We _know_ 100% this
combination works". Assuming the combination is tested.
Gary
On Thu, Aug 15, 2024, 9:01 AM Guillaume Nodet wrote:
> I would think the benefit of having
Is this proposal because elements from the super pom has been removed from
4.x?
https://issues.apache.org/jira/browse/MNG-6054
https://maven.apache.org/ref/3.9.8/maven-model-builder/super-pom.html
https://maven.apache.org/ref/4.0.0-alpha-9/maven-model-builder/super-pom.html
Which changes a new use
This sounds like an opportunity to cite my all-time favorite xkcd:
https://xkcd.com/927/
On Thu, Aug 15, 2024 at 7:15 AM Tamás Cservenák wrote:
>
> Howdy,
>
> as am going over multiple plugins (as it is time to upgrade parent, some
> bugfix, etc), all I see is:
> * a LOT of code duplication acro
Eliotte,
Who would "compete" within the ASF Maven project?
T
On Thu, Aug 15, 2024 at 4:37 PM Elliotte Rusty Harold
wrote:
> This sounds like an opportunity to cite my all-time favorite xkcd:
>
> https://xkcd.com/927/
>
> On Thu, Aug 15, 2024 at 7:15 AM Tamás Cservenák
> wrote:
> >
> > Howdy,
Think we should either assume it and make these plugins embedded in core
(same loader) or just let it like that and if needed extract reusable
services in core when dep free.
Le jeu. 15 août 2024 à 16:39, Tamás Cservenák a
écrit :
> Eliotte,
>
> Who would "compete" within the ASF Maven project?
AFAIK, Tamas suggested to *move* all plugins in a single maven-core-plugin,
not to extract reusable data in a new git repo.
Le jeu. 15 août 2024 à 15:42, Christoph Läubrich a
écrit :
>
> I think the main problem is that "maven-core" is often rejecting request
> for providing useful things in the
Yes, I don’t understand either.
I think the proposal is just to merge all core plugins into a single
project.
Guillaume Nodet
Le jeu. 15 août 2024 à 16:39, Tamás Cservenák a
écrit :
> Eliotte,
>
> Who would "compete" within the ASF Maven project?
>
> T
>
> On Thu, Aug
No, it seems to be a proposal for a new core plugin, not just
reorganzing the git repo. I predict if someone tries that we'll still
have all the old plugins plus the new maven-core-plugin. I have seen
this play out so many times over the years. Another old favorite:
https://www.youtube.com/watch?
Am 2024-08-15 um 12:53 schrieb Slawomir Jaranowski:
Hi,
I'm try to build site in maven-parent with new version
mvn clean site -f docs -Dversion.maven-site-plugin=3.20.0 -Papache-stage -e
- apache-stage - my profile with staging repo ...
I have:
[WARNING] Site model of 'org.apache.maven:docs:
Am 2024-08-14 um 17:47 schrieb Michael Osipov:
Hi,
we solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12354665
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolutio
Am 2024-08-15 um 10:38 schrieb Konrad Windszus:
Hi,
I would appreciate some cleanup of the branches after
https://issues.apache.org/jira/browse/MPLUGIN-523.
I see now
1) master
2) mvn4
3) maven-plugin-tools-3.7.x
4) maven-plugin-tools-3.x
IIUC only 1 and 4 is relevant.
I agree, but I would l
Am 2024-08-14 um 18:06 schrieb Michael Osipov:
Hi,
NOTE: Read the details on this release here:
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack#TowardsDoxia2.0.0Stack-MavenSitePlugin3.20.0/4.0.0
we solved 85 issues:
https://issues.apache.org/jira/secure/ReleaseNote
Am 2024-08-15 um 14:11 schrieb Slawomir Jaranowski:
Hi,
We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12344384
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20reso
Hi,
I am wondering why org.eclipse.aether.resolution.VersionResult[1] uses the type
String for the resolved version while
org.eclipse.aether.resolution.VersionRangeResult[2] uses type
org.eclipse.aether.version.Version.
This doesn’t seem very consistent. Is there a reason why it is not parsed fo
Just to be clear, your argument seems to be that a new plugin must always
add new functionality,
not that its existence should make its ancestors obsolete
(since by that measure Ubuntu has failed since Debian still exists)
But still, the xkcd comic is about *competing* standards (A/C adaptors,
cha
Hi,
we solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926&version=12354803
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%2
+1
śr., 14 sie 2024, 17:48 użytkownik Michael Osipov
napisał:
> Hi,
>
> we solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12354665
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%2
+1
Small remark, reporting API and impl has version 4.x that suggests Maven 4.
śr., 14 sie 2024, 18:06 użytkownik Michael Osipov
napisał:
> Hi,
>
> NOTE: Read the details on this release here:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack#TowardsDoxia2.0.0Stac
+1
czw., 15 sie 2024, 19:36 użytkownik Michael Osipov
napisał:
> Hi,
>
> we solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926&version=12354803
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%
Am 2024-08-15 um 19:43 schrieb Sylwester Lachiewicz:
+1
Small remark, reporting API and impl has version 4.x that suggests Maven 4.
Yes and no, it was a tradeoff I had to make :-( Didn't see a better way
to do milestones w/o bumping the major version...
M
-
On Thu, Aug 15, 2024 at 1:24 PM Delany wrote:
> The $5000 question is how can the old plugins still even exist if the code
> for them has been moved to a new core plugin?
In the git repo. In Maven central. In absolutely every existing plugin
and build that depends on these today. They aren't go
Well this would be the same plugins, not duplicates….
Guillaume Nodet
Le jeu. 15 août 2024 à 20:10, Elliotte Rusty Harold a
écrit :
> On Thu, Aug 15, 2024 at 1:24 PM Delany wrote:
>
> > The $5000 question is how can the old plugins still even exist if the
> code
> >
Howdy,
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317524&version=12354620
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MINSTALL/issues
Staging repo:
https://repository.apache.org/content/repositories/maven-21
Howdy,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317228&version=12354621
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MDEPLOY/issues
Staging repo:
https://repository.apache.org/content/repositories/maven-218
Am 2024-08-15 um 21:52 schrieb Tamás Cservenák:
Howdy,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317228&version=12354621
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MDEPLOY/issues
Staging repo:
https://re
Am 2024-08-15 um 21:52 schrieb Tamás Cservenák:
Howdy,
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317524&version=12354620
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MINSTALL/issues
Staging repo:
https://r
+1
czw., 15 sie 2024, 21:56 użytkownik Michael Osipov
napisał:
> Am 2024-08-15 um 21:52 schrieb Tamás Cservenák:
> > Howdy,
> >
> > We solved 2 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317524&version=12354620
> >
> > There are still a couple of issues left
+1
czw., 15 sie 2024, 21:56 użytkownik Michael Osipov
napisał:
> Am 2024-08-15 um 21:52 schrieb Tamás Cservenák:
> > Howdy,
> >
> > We solved 5 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317228&version=12354621
> >
> > There are still a couple of issues left
Hi,
we solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12354945
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resolution%20%3D%20Unresolved
Staging repo:
https://rep
Howdy,
This is on purpose.
VersionResult is "version resolution", that in case of input:
* release version (ie. "1.0") is really a no-op (you get same value back)
* snapshot version (ie. "1.0-SNAPSHOT") is operation involving metadata
(and you get back timestamped snapshot)
* etc
And, _usually_
+1
czw., 15 sie 2024, 22:06 użytkownik Michael Osipov
napisał:
> Hi,
>
> we solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12354945
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%
Where are you stay? Do you know me brother?
ในวันที่ ศ. 16 ส.ค. 2024 03:06 Sylwester Lachiewicz
เขียนว่า:
> +1
>
> czw., 15 sie 2024, 21:56 użytkownik Michael Osipov
> napisał:
>
> > Am 2024-08-15 um 21:52 schrieb Tamás Cservenák:
> > > Howdy,
> > >
> > > We solved 5 issues:
> > >
> >
> https:/
42 matches
Mail list logo
