:information_source: Hi :wave: @here In case the ...

# arrow-meta

[Rachel]

ℹ️ Hi 👋

@here In case the latest version under development 1.5.0-SNAPSHOT is being used.

Some changes were introduced today!

compiler-plugin has been moved to compiler-plugin-core and there is a new artifact for every compiler plugin.

You can find more details in `arrow-meta-examples` repository and setup

compiler-plugin for 1.5.0-SNAPSHOT will be removed tomorrow to avoid misunderstandings.

Thanks for your interest!

[raulraja]

thanks @Rachel!

[Rachel]

cc @dalexander (it seems @here is not allowed in this Slack, sorry)

[dalexander]

Oh, thanks for the update!

[Ben Woodworth]

Just curious, what's the rationale for naming it -core (here or in general)? I'm starting to write a library and am definitely overthinking it :)

[raulraja]

Hi @Ben Woodworth, We are currently considering the following name conventions for compiler plugins for 1.0.

io.arrow-kt:arrow-meta:<version> //base core compiler plugin others depend on
io.arrow-kt:arrow-proofs-plugin:<version> // a proofs plugin
io.arrow-kt:arrow-optics-plugin:<version> //an optics plugin
io.arrow-kt:arrow-refined-types-plugin:<version> // a refined types plugin

The base compiler plugin is going to get the arrow-meta name once we remove the final processor we have in Arrow for optics.
The old kapt artifacts is also arrow-meta but in th 1.x series it won’t be based of kapt.