]
Fred Bricon updated JBIDE-10018:
--------------------------------
Attachment: JBIDE-10018-resolveRemoteArchetypes.patch
Using similar hack to m2e to actually download archetypes before actual properties
resolution.
Example Archetypes don't resolve correctly if their remote
repository is not declared in the settings.xml
----------------------------------------------------------------------------------------------------------
Key: JBIDE-10018
URL:
https://issues.jboss.org/browse/JBIDE-10018
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, project-examples
Affects Versions: 3.3.0.M4
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 3.3.0.Beta1
Attachments: JBIDE-10018-resolveRemoteArchetypes.patch
While testing the EAP6 repository, it occured to me that Archetype properties were not
resolved correctly for our AS7 archetype based examples. Since the *required* properties
cannot be resolved, they're not displayed to the user. Eventually, the project
creation fails due to these missing properties.
This is similar to an upstream issue
(
https://bugs.eclipse.org/bugs/show_bug.cgi?id=359855), where the maven/aether session is
not correctly provided to the resolver.
Actually, there already is a hack in m2e that deals with that remote archetype resolution
issue. This need to be reproduced in JBT.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: