<commit_before>
[[_appendix_migration]]
= Migrating from Griffon 1.x
:numbered:

Griffon 2.x has tried to be as close as possible to Griffon 1.x in terms of concepts
and APIs, however some changes were introduced that require your attention when
migrating an application from Griffon 1.x

== Build Configuration

There is no longer a specific Griffon buildtime tool nor configuration settings.
You must pick a build tool (we recommend http://gradle.org[Gradle]) and use that
tool's configuration to match your needs. The simplest way to get started is to
select an appropriate http://github.com/pledbrook/layzbones[Lazybones] template
to create an empty project, then copy the files you need.

Build time plugins and scripts are now within the realm of a particular build tool.

=== Dependencies

Dependencies used to be configured inside `griffon-app/conf/BuildConfig.groovy`. Now
that the file is gone you must configured dependencies using the native support of
the build tool you choose. Of particular note is that all griffon dependencies are
now standard JAR archives available from Maven compatible repositories, so they should
work no matter which dependency resolution you pick.
<commit_msg>Fix typo in guide<commit_after>
[[_appendix_migration]]
= Migrating from Griffon 1.x
:numbered:

Griffon 2.x has tried to be as close as possible to Griffon 1.x in terms of concepts
and APIs, however some changes were introduced that require your attention when
migrating an application from Griffon 1.x

== Build Configuration

There is no longer a specific Griffon buildtime tool nor configuration settings.
You must pick a build tool (we recommend http://gradle.org[Gradle]) and use that
tool's configuration to match your needs. The simplest way to get started is to
select an appropriate http://github.com/pledbrook/layzbones[Lazybones] template
to create an empty project, then copy the files you need.

Build time plugins and scripts are now within the realm of a particular build tool.

=== Dependencies

Dependencies used to be configured inside `griffon-app/conf/BuildConfig.groovy`. Now
that the file is gone you must configure dependencies using the native support of
the build tool you choose. Of particular note is that all griffon dependencies are
now standard JAR archives available from Maven compatible repositories, so they should
work no matter which dependency resolution you pick.

{'fraction_non_alphanumeric': 0.043279234290470245, 'fraction_numerical': 0.0033291718684977114, 'mean_word_length': 4.892156862745098, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6985599', 'n_tokens_mistral': 613, 'n_tokens_neox': 578, 'n_words': 343}