[
http://jira.codehaus.org/browse/ARCHETYPE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138050#action_138050
]
Eugene Kuleshov commented on ARCHETYPE-174:
-------------------------------------------
If you are referring to [WARNING] entries in the log, then it is not
sufficient.
We need a programmatic way to retrieve those warnings, so they could be shown
in the wizard UI. Looking at your comment in that issue we still getting only
"org.apache.maven.archetypes:maven-archetype-quickstart:1.0 is not configured"
error, which isn't very helpful. That exception should contain all details
about missing properties and provide accessors to retrive those details, so we
could retrieve them in wizard UI.
On a side note, it would be more intuitive if error printed by mvn cli would
look like the following, so you won't have to hunt for the warnings somewhere
up in the log (perhaps by tuning toString() of the archetype exception):
{noformat}
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Archetype org.apache.maven.archetypes:maven-archetype-quickstart:1.0 is
not configured
Property groupId is missing. Add -DgroupId=someValue
Property artifactId is missing. Add -DartifactId=someValue
Property package is missing. Add -Dpackage=someValue
{noformat}
Also note that, "Add -DgroupId=someValue" text is unnecessary in the wizard UI
as it would be confusing there, so error accessors shouldn't include this text.
> The archetype is not configured error does not provide error details
> --------------------------------------------------------------------
>
> Key: ARCHETYPE-174
> URL: http://jira.codehaus.org/browse/ARCHETYPE-174
> Project: Maven Archetype
> Issue Type: Bug
> Reporter: Eugene Kuleshov
>
> When archetype is created (from ide) and does not specify required property,
> error message does not say what property is not specified. See test project
> attached at MNGECLIPSE-612
> org.apache.maven.archetype.exception.ArchetypeNotConfigured: The archetype is
> not configured
> at
> org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:98)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:215)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:130)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:290)
> at
> org.apache.maven.archetype.DefaultArchetype.generateProjectFromArchetype(DefaultArchetype.java:75)
> at
> org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.createArchetypeProject(ProjectConfigurationManager.java:362)
> at
> org.maven.ide.eclipse.wizards.MavenProjectWizard$4.runInWorkspace(MavenProjectWizard.java:227)
> at
> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
