Hello

My 2¢. Big +1 for bringing in build-helper-maven-plugin under
org.apache.maven.plugins - its add-[test]-(re)source goals are really the
"core" of Maven. But also attach-artifact.

I don't quite like using attributes for configuration - these were
historically (at least since Maven 2) meta configuration (combine.children,
combine.self). And even if using elements is more verbose, verbosity is the
theme of Maven - some may don't like it but after working with Maven 2+ for
15+ years, it's the best way to ensure build safety and good maintenance.

Another plugin that I'd love to see under org.apache.maven.plugins is
versions-maven-plugin, so please consider it as well ;)

kind regards
Grzegorz Grzybek

pt., 12 lip 2024 o 21:20 Karl Heinz Marbaise <khmarba...@gmx.de.invalid>
napisał(a):

> Hi,
>
> good questions.
>
> On 12.07.24 15:53, Elliotte Rusty Harold wrote:
> > Meta-question: how do you plan to change group IDs and licenses?
> > Presumably everything would now be under the Apache license instead of
> > MIT or whatever they're currently using. I hope the licenses are all
> > compatible with this shift.
>
>
> First based on the licenses that is simply not possible, because it's a
> different license apart from the legal aspects(INAL!!) (in my opinion!).
> This would requires also to ask everyone of the committers (MojoHaus;
> and even contributors) if they agree on the license change... (INAL) but
> I doubt that this is even possible or practically will work...
>
> Furthermore we need to go through a ip-clearance (if I see it correctly)
> as we did with the resolver (aka aether)..
>
> My suggestions is to create new plugins (maven 4 based) with the
> functionality we need instead ... or integrate that into Maven core...
> instead...
>
>
> Kind regards
> Karl Heinz Marbaise
> >
> > Should the group IDs change too? Ideally they wouldn't, but we'd need
> > to make sure that the Apache project and the Maven PMC has the same
> > rights to publish the artifacts to Maven Central that they have for
> > current artifacts under org.apache. This shouldn't be tied to
> > individual developers.
> >
> > On Fri, Jul 12, 2024 at 9:27 AM Guillaume Nodet <gno...@apache.org>
> wrote:
> >>
> >> I've been working on migrating the build-helper-maven-plugin to the
> >> Maven 4.x API.
> >> The work is available at [1] (PR is red, but that's a CI configuration
> problem).
> >> While doing so, I've had a hard time figuring out why some plugins are
> >> hosted at the ASF while some others are hosted at MojoHaus.
> >> This plugin in particular is used a lot (to add generated
> >> source/resources and attach artifacts) and there's no other way to do
> >> it.  This is essentially a core feature of Maven, and thus, I think it
> >> should be provided by a Maven plugin.
> >> I've created a repo and migrated it at [2], but now raising the
> discussion...
> >>
> >> If that causes a problem, I think we should provide a new plugin with
> >> just those goals (add main/test source/resources directory, and attach
> >> artifact).
> >>
> >> It just feels weird that Maven does not provide the required plugins
> directly...
> >>
> >> That said, I think we have some old plugins that have not been
> >> released since nearly 10 years [3], probably indicating they are not
> >> used anymore: verifier, acr ?, jmod, changelog, changes, doap, jdeps,
> >> linkcheck, jarsigner, jdeprscan, patch, pdf, stage.
> >> I think those should be retired...
> >>
> >> [1] https://github.com/mojohaus/build-helper-maven-plugin/pull/215
> >> [2] https://github.com/apache/maven-build-helper-plugin
> >> [3] https://maven.apache.org/plugins/
> >>
> >> --
> >> ------------------------
> >> Guillaume Nodet
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Reply via email to