Le vendredi 17 juin 2016 11:25:43 Christian Schulte a écrit : > Am 06/17/16 um 09:39 schrieb Robert Scholte: > > Hi, > > > > a few remarks to the API ( I like the idea of it ). > > - use strong() instead of highlight() > > - use text() instead of a() > > Do we want to be able to nest styles (or mimic it)? > > e.g *strong* please ensure to replace this method before *warn* 1-1-2017 > > *_warn* !!! *_bold* > > If so, we'd better use matching closing methods, like we do with Doxia > > Sink > > JANSI api shouldn't be leading, but what we think is general enough for > > every ANSI implementation > > Maybe also split API and implementation. So that jansi becomes a runtime > dependency (implementation) and does not appear on any compile > classpath. Leaves the option to replace jansi with something else in the > future, if we need to. this is already the case wuthout splitting API and implementation: look at my last commit on maven-site-plugin, jansi is not put as dependency any more, and there is no jansi package name in any .java source file
That's one of the benefits of using our own API, which is fairly simple (and feared more complex scenario at the beginning) Regards, Hervé > > > --------------------------------------------------------------------- > 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
