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




 

On Tuesday, June 21, 2016 at 9:35:15 AM UTC+2, Jochen Wiedmann wrote:
>
> 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 
>
>
> On Mon, Jun 20, 2016 at 10:34 PM, Manfred Moser <[email protected] 
> <javascript:>> wrote: 
> > I totally agree with Markus. New plugin - latest publicly available 
> Java. 
> > 
> > On Mon, Jun 20, 2016 at 10:08 AM, Markus Karg <[email protected] 
> <javascript:>> 
> > wrote: 
> >> 
> >> 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. 
> >> 
> >> Am Sonntag, 19. Juni 2016 15:32:43 UTC+2 schrieb 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 
> >>> 
> >>> On Sunday, June 19, 2016 at 8:50:40 AM UTC+2, Markus Karg wrote: 
> >>>> 
> >>>> 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 [email protected] <javascript:>. 
> >> To post to this group, send email to [email protected] 
> <javascript:>. 
> >> To view this discussion on the web visit 
> >> 
> https://groups.google.com/d/msgid/mojohaus-dev/01a9a491-7271-45c9-b03e-8999db8bf26a%40googlegroups.com.
>  
>
> >> 
> >> For more options, visit https://groups.google.com/d/optout. 
> > 
> > 
> > -- 
> > 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 [email protected] <javascript:>. 
> > To post to this group, send email to [email protected] 
> <javascript:>. 
> > To view this discussion on the web visit 
> > 
> 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
>  
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mojohaus-dev/43abda00-4d97-4ae9-ba32-54519ac524e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to