Skip to content

Consider a switch to use maintained nv-i18n package - #285

Open
alangdundee wants to merge 1 commit into
52North:developfrom
alangdundee:agraham/nv-i18n
Open

Consider a switch to use maintained nv-i18n package#285
alangdundee wants to merge 1 commit into
52North:developfrom
alangdundee:agraham/nv-i18n

Conversation

@alangdundee

Copy link
Copy Markdown

The original nv-i18n is no longer being maintained. Our company app relies on it, and needed newly created entries. A colleague and I have forked and published a new version of it. Due to our reliance on it we will be continuing to maintain it.

https://github.com/foundationsedge/nv-i18n

Mvn Repo location

https://central.sonatype.com/artifact/uk.co.foundationsedge/nv-i18n

The original nv-i18n is no longer being maintained. Our company app relies on it, and needed newly created entries.
A colleague and I have forked and published a new version of it.
Due to our reliance on it we will be continuing to maintain it.

https://github.com/foundationsedge/nv-i18n

Mvn Repo location

https://central.sonatype.com/artifact/uk.co.foundationsedge/nv-i18n
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant