-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Locally installed archetypes not detected #82
Comments
@paroxayte Could you share the way you are using local-catalog? So we can think about how to improve the experience? |
Forgot to say, yes, currently it only fetches the catalog from maven central repo, and caches it locally. The drop list of maven archetypes is loaded from the cached catelog. So we want to know how you install your archetype, and how to get the list of archetypes installed to local-catalog, and how you use command line to generate projects from that archetype. It would help a lot. Thanks. |
@Eskibear Yes, certainly! When installing an archetype from source I run
You can similarly do this with install:install-file and a local archetype jar.
Then to generate a project from the now installed archetype I cd into my workspace directory and run |
Yes, by executing Plan
Do you think this works for you and other local-catalog users ? |
Yes, I believe this plan would cover most/all local catalog users. Note that if you use |
Fixed in PR #86 . Will be shipped with v1.0.0. You can checkout the latest code if you want to try it now. |
Installing an archetype and updating the local-catalog to contain said archetype does not cause it to appear in the list of available archetypes from the Maven: Generate from Maven Archetype command. I have verified that my archetype is correctly installed by cat'ng the local-catalog as well as generating a project using the archetype from the command line.
OS: Debian Stretch
The text was updated successfully, but these errors were encountered: