New plugin idea: banner-maven-plugin

[metrizzle]

Hi all,

I created a maven plugin that prints ascii banner as 

part of the build: 

https://github.com/metrizzle/jfiglet-maven-plugin

Would that be of interest for the sandbox?

I think a ascii/banner/figlet plugin would be

a nice addon for the haus. 

Best regards,

metrizzle 

                                 

  _______  __ ___________ ___.__.

_/ __ \  \/ _/ __ \_  __ <   |  |

\  ___/\   /\  ___/|  | \/\___  |

 \___  >\_/  \___  |__|   / ____|

___. \/          \.___    \/     

\_ |__   ____   __| ____.__.     

 | __ \ /  _ \ / __ <   |  |     

 | \_\ (  <_> / /_/ |\___  |     

 |___  /\____/\____ |/ ____|     

.__  .__ __        \/\/          

|  | |__|  | __ ____   ______    

|  | |  |  |/ _/ __ \ /  ___/    

|  |_|  |    <\  ___/ \___ \     

|____|__|__|_ \\___  /____  >    

             \/    \/.__.__/     

_____    ______ ____ |__|__|     

\__  \  /  ____/ ___\|  |  |     

 / __ \_\___ \\  \___|  |  |     

(____  /____  >\___  |__|__|     

     \/     \/     \/            

[Karl Heinz Marbaise]

Hi,

first it looks great...but one question. Is Java 8 really needed? Most of the plugins here at MojoHaus are Java 6 (or less) based...

Kind regards

Karl Heinz Marbaise

[Manfred Moser]

I think its just fine to require Java 8 for a plugin. Or is there a requirement for mojohaus plugins to support Java 6? If so I think this should be dropped. 

Manfred

--
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 post to this group, send email to mojoha...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/b2414f34-aef5-4b8a-b77b-d8c06de1ff88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Markus Karg]

Java 8 exists for several years and is even available for conservative linux distributions like Debian or for rather "exotic" hardware like Raspberry or IBM System Z. It is not a special demand that makes one use Java 8, it is simply normal to do that. I do not see any problem using Java 8 for new plugins or new releases of existing plugins. If someone baldy wants to stay with Java 6, he is free to invest the additonal time needed to support and maintain a fork. Forcing people to stay away from latest technology for too long time simply leads to the fact that those people leave a project.

[Mirko Friedenhagen]

I completely agree with Markus here. People who need to stay with old JDKs just should stay with old plugins/build tooling as well.

Regards
Mirko
--
Sent from my mobile

Am 19.06.2016 08:50 schrieb "Markus Karg" <mar...@headcrashing.eu>:

Java 8 exists for several years and is even available for conservative linux distributions like Debian or for rather "exotic" hardware like Raspberry or IBM System Z. It is not a special demand that makes one use Java 8, it is simply normal to do that. I do not see any problem using Java 8 for new plugins or new releases of existing plugins. If someone baldy wants to stay with Java 6, he is free to invest the additonal time needed to support and maintain a fork. Forcing people to stay away from latest technology for too long time simply leads to the fact that those people leave a project.

--

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 post to this group, send email to mojoha...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/73551f48-b242-40f8-8bd4-2e7f6bfe439b%40googlegroups.com.

[Baptiste Mathus]

(BTW, this might be an additional point to my other /governance/ thread. Should we have an official baseline for the project or not, and so on.)

IMO, this is fine. 

I for one would maybe still be ready to spend some spare time to investigate Java 7 issues, still only if simple, but not below. I've got more interesting things to do.

It's just too old and people stuck with that are generally enterprisey softwares that could probably afford a specific support contract.

On the other hand, we, as a community, probably cannot afford the associated cost: developers not interested to participate, or losing interest because they're forced to use the same old stack as if they were supporting paying customers. 

The only thing IMO we want to find an agreement on is to find a way to make that clear for users.

-- Baptiste

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

[Karl Heinz Marbaise]

Hi Markus,

it exists for about 2 Years and 3 months..(18. March 2014)...

https://blogs.oracle.com/thejavatutorials/entry/jdk_8_is_released

But is there a real need for JDK 8 to create "simple things" like a banner (be aware of the quotes don't take me wrong)? 

That was the foundation of my question...

And Yes I would also VOTE for JDK 7 as minimum. We should have a clear base line for the MojoHaus project as well...I started migration of other plugins (for example MRM to get 1.0.0 out and than migration to Maven 3 only than there is no problem to say JDK 7 minimum or if we decide different JDK 8..)...

Kind regards

Karl Heinz

[Markus Karg]

Again, it is not about whether it is needed. It is simply current. Developing new plugins on old runtimes simply feels odd.

Forcing people to check ready-to-run code whether it could run on totally outdated Java runtimes simply annoys them. It binds valueable time and enthusiasm, and possibly ends up with answers like: "Yes, we use just two or three lines of Java 8 that could be replaced by 20 or 30 lines of Java 6. So no, it is not needed, but backporting it costs us another day which nobody likes to invest."

So I would say, for any new functionality, particularly brand-new plugins, let people just use the latest published Java. I do not see any need to take care of older Java versions for new features. It should be enough to stick with the same major Java release within LTS branches of existing plugins.

[Manfred Moser]

I totally agree with Markus. New plugin - latest publicly available Java. 

--

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 post to this group, send email to mojoha...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/01a9a491-7271-45c9-b03e-8999db8bf26a%40googlegroups.com.

[Jochen Wiedmann]

Besides, keep in mind: This would be a plugin, that could easily be
enabled only, if the JRE matches. It obviously wouldn't be relevant
for the build.

For that reason, this discussion strikes me as quite odd.

Jochen

> https://groups.google.com/d/msgid/mojohaus-dev/CABffhO64SoHf-TPoPunwyGfj9-E22ckJ8LCvRjCK4U8ygR1dbA%40mail.gmail.com.

> For more options, visit https://groups.google.com/d/optout.

--
The next time you hear: "Don't reinvent the wheel!"

http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg

[metrizzle]

Hi,

sorry for the late reply. I thought there is no interested at first.

I just pushed a new version of the plugin that inherits the 

java properties/config from the mojo-parent (version 40); supporting older

java version should not be too difficult in case of this plugins context.

So then, I would go ahead with refactorings to meet the dev guidelines?

What about the name: banner-maven-plugin Ok? 

Figlet or ascii plugin sounds also very nice. 

Best Regards,

Nils