You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/10/24 18:12:08 UTC
[jira] Commented: (MAVEN-1419) having maven xmlns causes 'Goal "xxx" does not exist in this project'
The following comment has been added to this issue:
Author: Malachi de AElfweald
Created: Sun, 24 Oct 2004 12:11 PM
Body:
Well, I can answer that for you.
If you put the right xmlns in, then visual editors will quit showing it as an error and also popup with the valid options whenever you start to type a new tag or attribute.
Realistically, the schemas for the various XML formats should be mentioned in the documentation; as it would be easier for developers to write tools for maven.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1419?page=comments#action_25751
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1419
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1419
Summary: having maven xmlns causes 'Goal "xxx" does not exist in this project'
Type: Improvement
Status: Closed
Priority: Minor
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Assignee:
Reporter: Malachi de AElfweald
Created: Sun, 8 Aug 2004 12:01 AM
Updated: Sun, 24 Oct 2004 12:11 PM
Description:
I had added this to my maven.xml so that the editor could validate and suggest tag names:
xmlns="http://maven.apache.org/xsd/maven-project-3.0.0.xsd"
built-in goals worked fine. however, trying to access any goals in the project by name would say:
'Goal "xxx" does not exist in this project.'
Searching Google, I found many people who had that problem, but were unsure how to fix it. The only suggestion I even found was to delete the *.cache files, which did not help.
Removing the xmlns, the goals work fine. Either maven should be able to handle this, or the documentation should at least warn against doing it.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org