Add support for multiline description; remove 70 chars limitation

[eugeniyk]

fixes #596

This PR aim for supporting multiline description, with custom line breaks and removing custom 70 symbols pseudo new line
As for me it can be obsoleted since it's now up to you how to format the description

Example:

description = \
Welcome to AG scala service seed!\n\
Let's create service with our best practices!\n\
\n\
Help about parameters:\n\
- organization => logical separation, part of package name (eg. platform, connectivity, ..)\n\
- project => human-readable name of the project. Do not include 'api' postfix in it\n\
- ssot => system name that we use internally to identify the service. This name may include 'api' postfix\n\
- git_* => gitlab settings\n\
- harbor_organization => allows to override harbor organization
- gen_* => whether to include generation of dedicated components; yes / no\n\

As a result we'll have nice description in the console:

Welcome to AG scala service seed!
Let's create service with our best practices!

Help about parameters:
- organization => logical separation, part of package name (eg. platform, connectivity, ..)
- project => human-readable name of the project. Do not include 'api' postfix in it
- ssot => system name that we use internally to identify the service. This name may include 'api' postfix
- git_* => gitlab settings
- harbor_organization => allows to override harbor organization
- gen_* => whether to include generation of dedicated components; yes / no

[eugeniyk]

@eed3si9n Any update on this one? Do you still want to preserve initial behavior?

[eed3si9n]

@eugeniyk Sorry about the delay. To be honest, I don't have strong opinion on either direction, but I can imagine someone else might file it as a bug if we break the backward compatibility without strong reason. So in my opinion, introducing the new behavior only when the string contains \n is more defensive coding.

[eugeniyk]

This is an expected output of the test:

[eugeniyk]

@eed3si9n ok please check again, I've restored the old behavior

[eed3si9n]

Thanks!

[eugeniyk]

@eed3si9n is there a plan to release new version any soon?

[eed3si9n]

Yea. Maybe in a week or two?

[eugeniyk]

not sure what is scala_xml 2.01

[eed3si9n]

How did you get the error?

[eugeniyk]

if you have sbt native packager (1.9.7) along with latest giter8 and sbt 1.6.1 on scala 2.12/13
anyway, evictionErrorLevel := Level.Info seems hided the issue

[eed3si9n]

Did you add giter8 into the metabuild?
In general though maybe we should consider downgrading those libraries back to 1.x since I don't think we need 2.x.

[eugeniyk]

It is part of plugins.sbt, same as scoverage and other plugins пт, 14 янв. 2022 г. в 00:34, eugene yokota ***@***.***>:

…

Did you add giter8 into the metabuild? In general though maybe we should consider downgrading those libraries back to 1.x since I don't think we need 2.x. — Reply to this email directly, view it on GitHub <#622 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6ACCSACMANVCOJL3BAFM3UV4EK7ANCNFSM5IB54QNA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[eed3si9n]

Giter8 acts as a backend of sbt new, so using it as a plugin doesn't do much.
You can switch the Giter8 version for your template by putting

giter8.version = 0.14.0

in the project/build.properties of the template.