jira-importer

**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** commented What do you expect to happen?

**[Cameron Hudson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cameronhudson8)** commented I expected it to inform the user that the package name was invalid (ideally, explaining why it's invalid), and to present the prompt again. I've added this...

**[Marcel Schutte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mschutte)** commented patch against commit d2e45a6

**[Elliotte Rusty Harold](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=elharo)** commented patch needs tests

**[Scott MacDonald](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=scanguskhan)** commented Just ran into this exact  issue on maven 3.6.2 with the  bundled archetype plugin, and it also occurs  on latest 3.2.1 archetype  plugin.  Came here to log...

**[Elliotte Rusty Harold](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=elharo)** commented What are our rules about incompatible API changes?

**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented for such internal API, no strong strategy: the only question is to know if this could cause an issue for an IDE plugin, for example and even...

**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** commented And you guarantee them to work thread safe?

**[Thomas Pischke](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tpischke)** commented This would also be fixed by the PR in ARCHETYPE-548, but that issue is marked as closed.

**[Thomas Pischke](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tpischke)** commented We have a quick and dirty local patch to fix this problem, but still need to clean it up for submission. Might end up looking very similar...