[
https://issues.jboss.org/browse/FORGE-2588?page=com.atlassian.jira.plugin...
]
James Strachan commented on FORGE-2588:
---------------------------------------
so one really simple workaround for this issue is to remove the pom.xml and src folder
before the ArchtypeHelper processes the archetype jar; as for java / maven projects its
going to replace whatever is there with the pom.xml thats inside the archetype anyway and
will generate all the required java source folders with the correct package names or files
from the archetype etc.
Then if there's no pom.xml or src folders in the archetype jar, things just work
beautifully without having to make major changes to ProjectType /
NewProjectWizardImpl.java to defer decisions on what facets are inside a
MavenArchetypeProjectType.java until after the archetype has been generated.
Does this simple patch seem OK to you? It only affects projects created using
MavenArchetypeProjectType.
I did ponder about adding a custom "non-java" marker to the archetype to
restrict the scope of this fix further; but thats harder right now as ArchetypeHelper is
called with an InputStream of the archetype jar so its harder to pre-process the jar first
to look for a magic file to delete pom.xml and src before processing it again.
If you're happy with the above I can submit a PR?
support creating projects from archetypes which don't use maven
---------------------------------------------------------------
Key: FORGE-2588
URL:
https://issues.jboss.org/browse/FORGE-2588
Project: Forge
Issue Type: Feature Request
Reporter: James Strachan
we've a bunch of archetypes for projects like nodejs, golang, swift, python, ruby;
we're also hoping to add archetypes for things like Gradle / SBT etc.
It'd be nice to allow the project-new wizard to not always create a pom.xml and
src/main/* src/test/* folders if the archetype does not contain a pom.xml file.
PR on the way shortly...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)