Adopting buildplan-maven-plugin

[Hervé Boutemy]

Hello everyone,

Recently, I discovered an incredibly nice Maven plugin to clarify some magic of Maven builds: Buildplan Maven Plugin

http://buildplan.jcgay.fr/usage.html

This plugin is not useful as part of a build, but on command line: the only issue is that you must configure the groupId in your settings.xml to be able to just run "mvn buildplan:list"

I fear not many people will learn how to do that, particularly those who would really need an easy way to learn how Maven is not completely magic.

Then I contacted the author -- Jean Christophe Gay, a french guy I had the opportunity to meet at Devoxx France 2 days ago :) -- and asked him if he would be interested to join us and move the plugin to MojoHaus: everybody would win from that. He loved the idea.

Then now it's up to you to accept or reject the idea: what do you think?

Regards,

Hervé

[Olivier Lamy]

+1

looks interesting!

--
You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAJ0Jt%3Dn%2BnJxCwonzbunaRDa6D--coio3w5UosqrJzDGWzxBoQw%40mail.gmail.com.

--

Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

[Slawomir Jaranowski]

+1 for adopting

+1 for new maintainer ... :-)

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAPoyBqRZWFMC3dbjCDwqOjU7Q4yGUFPrOSzaXrnGT7qQ_ZArUA%40mail.gmail.com.

--

Sławomir Jaranowski

[mfried...@gmx.de]

+1 for adopting, I already have used this in the past.

Best Regards
Mirko Friedenhagen
—
Sent from my mobile

Am 23.04.22 um 11:26 schrieb Hervé Boutemy

[Oliver B. Fischer]

Hi,

being only a normal user of the Maven, so maybe my voice is here not so important. But the plugin seems to very useful for everyone, who would like to analyse his Maven build. It provides very usefull insides.

Bye,

Oliver

Am 23.04.22 um 11:25 schrieb Hervé Boutemy:

--
You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAJ0Jt%3Dn%2BnJxCwonzbunaRDa6D--coio3w5UosqrJzDGWzxBoQw%40mail.gmail.com.

-- 
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538 
E o.b.f...@swe-blog.net 
S oliver.b.fischer
J oliver.b...@jabber.org
X http://xing.to/obf

[Arnaud Héritier]

It makes sense to me

+1

--

You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAJ0Jt%3Dn%2BnJxCwonzbunaRDa6D--coio3w5UosqrJzDGWzxBoQw%40mail.gmail.com.

--

Arnaud Héritier

Twitter/GitHub/... : aheritier

[Hervé Boutemy]

good, everybody looks ok: I'll add JC to the MojoHaus team

next question: should we import buildplan-maven-plugin as buildplan-maven-plugin or as bp-maven-plugin?

given it's intended for command line, "mvn bp:list" could be easier to use (even if its full name will remain BuildPlan Maven Plugin)

WDYT?

Regards,

Hervé

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAFNCU-8nSHVeMXw2yGABHALHL0G3hYwexWV2eAgwBeJ650f%2BnA%40mail.gmail.com.

[Oliver B. Fischer]

Hi,

Am 27.04.22 um 18:52 schrieb Hervé Boutemy:

> good, everybody looks ok: I'll add JC to the MojoHaus team
>
> next question: should we import buildplan-maven-plugin as
> buildplan-maven-plugin or as bp-maven-plugin?
> given it's intended for command line, "mvn bp:list" could be easier to
> use (even if its full name will remain BuildPlan Maven Plugin)

Is there another plugin, using such a short name? All plugins I know
don't us abbreviations.

Bye,

Oliver

[mfried...@gmx.de]

Hi,

I would keep the longer name, BP Maven plugin sounds like something producing fossile fuels 😅

Best Regards
Mirko Friedenhagen
—
Sent from my mobile

Am 27.04.22 um 19:04 schrieb Oliver B. Fischer

> --
> You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/515985ff-b7c5-1074-dd6a-4f96b0bb94ba%40swe-blog.net.
>

[Hervé Boutemy]

I fully agree with you that I don't want "BP Maven Plugin", that is at best cryptic and at worst a bad company reference

but I still called it "Buildplan Maven Plugin", it's only the command line which would be bp:list

I know, it's unusual to have the id not exactly the same as the full name prefix

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/trinity-48c22c2d-2f71-4a5a-86bb-7a56e0d4c333-1651087355149%40msvc-mesg-gmx026.

[Oliver B. Fischer]

I agree.

Am 28.04.22 um 08:48 schrieb Hervé Boutemy:

I fully agree with you that I don't want "BP Maven Plugin", that is at best cryptic and at worst a bad company reference

but I still called it "Buildplan Maven Plugin", it's only the command line which would be bp:list

I know, it's unusual to have the id not exactly the same as the full name prefix

Le mer. 27 avr. 2022 à 21:22, <mfried...@gmx.de> a écrit :

Hi,

I would keep the longer name, BP Maven plugin sounds like something producing fossile fuels 😅

Best Regards
Mirko Friedenhagen
—
Sent from my mobile

Am 27.04.22 um 19:04 schrieb Oliver B. Fischer

[Jean-Christophe GAY]

Hi,

Thanks for having me in!

Modifying the goal prefix to use bp:list could be great I think.

I don't really know plugins using such short names either. Isn't there a risk of clash between different plugins ?

Let me know what's next, Hervé .

Bye,

Jc

[Hervé Boutemy]

I just invited you to the team

on bp-maven-plugin, there is nothing in Central until now https://search.maven.org/search?q=bp-maven-plugin

then no worry on creating one :)

Le sam. 30 avr. 2022 à 14:52, Dev <con...@jeanchristophegay.com> a écrit :

Hi,

Thanks for having me in!

Modifying the goal prefix to use bp:list could be great I think.

I don't really know plugins using such short names either. Isn't there a risk of clash between different plugins ?

Let me know what's next, Hervé 😇.

Bye,

Jc

 

[Hervé Boutemy]

forked https://github.com/mojohaus/bp-maven-plugin

[Olivier Lamy]

Why bp-maven-plugin in git repo whereas the artifactId is buildplan-maven-plugin?

my understanding was we didn't like this bp? (which I agree too :))

--
You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAJ0Jt%3DkjjuttvDESUDsWeCSP3Sekz__T%3DYHzGiSY5TdoBkmB8g%40mail.gmail.com.

[Hervé Boutemy]

I answered to the few feedback: its full name is "BuildPlan Maven Plugin", even if it's "bp:list"

it seems a more active discussion is happening on the first PR https://github.com/mojohaus/bp-maven-plugin/pull/1

you can drop the fork, rename if you want: I have no problem to people establishing a different consensus to what I did, the most important is that we're bringing JC and his code to the right location :)

JC and rest of the team, floor is yours :)

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAPoyBqQykzBu16t60xAVFiGDnWsSAXMh__G_8u3nVXpB94PR0w%40mail.gmail.com.

[Olivier Lamy]

hehe too many ways of communication :) 

I have just renamed the repo.

Maybe JC can now make the transfer?

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAJ0Jt%3DmNutBnYP%3DjSFHQ3%3Do-k6ktxSin6NLDQ5%3Dxc21B5j8e1A%40mail.gmail.com.

[Benjamin Marwell]

Or even better:

Make the new fork in Mojohaus the new primary repo. Don't delete or transfer anything. Opened an issue to get your attention. Brian did the same with maven-wrapper. Advantage: you can edit the readme on the old one and then archive it. 

[Olivier Lamy]

On Wed, 4 May 2022 at 16:45, Benjamin Marwell <bmar...@apache.org> wrote:

Or even better:

Make the new fork in Mojohaus the new primary repo. Don't delete or transfer anything. Opened an issue to get your attention. Brian did the same with maven-wrapper. Advantage: you can edit the readme on the old one and then archive it. 

Which option can preserve current issues and PRs from the original repo?

 

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/1f53fffd-b80a-46fb-8d33-b58779f079e6n%40googlegroups.com.

[Jean-Christophe GAY]

Only the ownership transfer keeps issues, watchers, stars, etc (https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository#whats-transferred-with-a-repository).

But issue links in commits in the fork are correctly redirecting to the original repository, so that the history is still readable and intact 👍

Example in https://github.com/mojohaus/buildplan-maven-plugin/commit/45c2cd9be647193dacb0f3607a78cc6bca069fe3

[Andreas Sewe]

Hervé Boutemy wrote:
> I fully agree with you that I don't want "BP Maven Plugin", that is at
> best cryptic and at worst a bad company reference
> but I still called it "Buildplan Maven Plugin", it's only the command
> line which would be bp:list
> I know, it's unusual to have the id not exactly the same as the full
> name prefix

Just 2 cents from a regular Maven user:

There is another place where the shortened name may prove cryptic: in
your <pluginManagement> section.

To ensure reproducibility, I use <pluginManagement> to also fix versions
for plugins that I only use from the command line, the
versions-maven-plugin being the prime example. And there, reading
something like bp-maven-plugin will make the casual reader go "huh",
whereas buildplan-maven-plugin is totally obvious.

Hence, I would very much prefer the slightly longer name. buildplan:list
is not that bad.

Best wishes,

Andreas

[Olivier Lamy]

On Thu, 5 May 2022 at 04:59, Jean-Christophe GAY <gay.jch...@gmail.com> wrote:

Only the ownership transfer keeps issues, watchers, stars, etc (https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository#whats-transferred-with-a-repository).

I'm for transfer especially to keep issues.

but if you prefer start a new life and forgot about all the previous issues it's up2u 🤣

 

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/75ba9202-eb24-4cc8-a737-a66a46f50823n%40googlegroups.com.

[Hervé Boutemy]

ok, I'll drop the current fork and let's have JC do the transfer 

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAPoyBqTFqkOy34QPWTauFVgT-8qz9S1zTaGhsZC7g%2Bc1QFZ68A%40mail.gmail.com.

[Olivier Lamy]

sounds good.

But to do the transfer you need to be part of the owner team of the target organisation (e.g mojohaus). 

Do we want everybody to be an owner?

Maybe ask JC to be admin of the source repository to do the transfer yourself?

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAJ0Jt%3DnnKK-GndcxoctF4GzO0cNbkfq5i3L%3DsDr8ya8inO39sw%40mail.gmail.com.

[Hervé Boutemy]

I'll work with JC to check who can do the job

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAPoyBqTX%3DN%3DzsDmKxOWN-hOO9x_9-KiOcRU9%3D-2tV986jUu16A%40mail.gmail.com.

[Jean-Christophe GAY]

I've just done the transfer 🎇 : https://github.com/mojohaus/buildplan-maven-plugin

Thanks everyone :)

[Olivier Lamy]

Thanks and welcome!

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/64e8ae1a-5a05-4538-8e5a-5e8b13f14a10n%40googlegroups.com.