-
Notifications
You must be signed in to change notification settings - Fork 85
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
project archetype: __{impl,app}-artifactId__ #89
Comments
Further info: I tried to remove the artifacts of the archetype first to ensure there is no "corrupt" version in my local Maven repo:
Ensure current working directory is empty:
Generate stuff using archetype project:
As you can already see in the lines above the "parent elements" "...-artifactId__/pom.xml" are used. Inspect the module declarations in the base POM:
|
This does look like a problem, although it appears to be at least partly an issue with the maven-archetype-plugin. I see that you're using version 2.4 of the archetype plugin. Can you try running the generation using version It's also possible that there's more than one thing going on here. The list of |
It seems to make a difference:
|
Well that's positive. Unfortunately I'm not aware of a way to require that an archetype is used with a particular version of the maven-archetype-plugin... |
Would it make sense to change the command on the site to force the version |
That's probably a good idea |
Moved to osgi/osgi.enroute.site#192 |
After playing around with the enroute.osgi.org approach the last days I would like to check the documentation from the beginning to provide fixes if necessary.
The project archetype generation works some time and didn't some time (at least the result contains errors).
If I execute the following line:
sometimes the
modules
elements look like:Also the directories are not names correctly:
I started in an empty directory.
Full log:
The text was updated successfully, but these errors were encountered: