On 10/06/2008, at 10:29 PM, Olivier Lamy wrote:
Can we let it in 1.2 ?
I think it's better to help users to understand "What's wrong here !"
;-)
I agree, though the reason I started culling minor issues was that as
long as we leave these in 1.2, users still have this problem with the
current production release (1.1), as well as the 70 others already
fixed in 1.2 :)
- Brett
--
Olivier
2008/6/10 Brett Porter (JIRA) <[EMAIL PROTECTED]>:
[ http://jira.codehaus.org/browse/CONTINUUM-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated CONTINUUM-1675:
------------------------------------
Fix Version/s: (was: 1.2)
1.3
Improve error message when scm element is missing from a child pom
------------------------------------------------------------------
Key: CONTINUUM-1675
URL: http://jira.codehaus.org/browse/CONTINUUM-1675
Project: Continuum
Issue Type: Improvement
Components: Web - UI
Affects Versions: 1.1
Reporter: Wendy Smoak
Priority: Minor
Fix For: 1.3
When adding a multi-module project, if one of the child projects
does not have a scm element, I still get the generic message:
"Missing 'scm' element in the POM."
In the log file, I can see that it knows exactly which pom is
missing the element:
INFO | jvm 1 | 2008/02/25 11:16:35 | 2008-02-25 11:16:35,530
[SocketListener0-7] ERROR MavenBuilderHelper:default - Missing
'scm' element in the ExampleWebapp POM.
(This happened because the child project did not have a <parent>
element.)
The web page should display the more specific error message.
--
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
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
