[ http://jira.codehaus.org/browse/MAVEN-1673?page=all ]
Arnaud Heritier updated MAVEN-1673:
-----------------------------------
Fix Version: (was: 1.1-beta-3)
> <ant:element-without-taskdef> does not indicate failure
> -------------------------------------------------------
>
> Key: MAVEN-1673
> URL: http://jira.codehaus.org/browse/MAVEN-1673
> Project: Maven
> Type: Bug
> Components: jelly/ant integration
> Versions: 1.1-beta-1, 1.0.2
> Environment: OS X 10.4.2, JRE 1.4.2_07-215
> Reporter: Scott Lamb
> Priority: Minor
> Attachments: element-without-taskdef.tar.gz
>
>
> maven does not error out when it encounters an ant element with no taskdef.
> This is horribly confusing. ant produces a nice error message when run
> directly.
> This is likely to happen frequently on maven 1.1, since it no longer includes
> many optional taskdefs.
> In my tests, maven 1.0.2 completely ignores the unknown element. maven
> 1.1-beta-1 prints out the literal element but still does nothing.
> To reproduce with the attached testcase (not jUnit; sorry):
> $ tar xvzf element-without-taskdef.tar.gz
> $ cd element-without-taskdef
> $ maven shouldfail
> __ __
> | \/ |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-1
> build:start:
> shouldfail:
> <element-without-taskdef></element-without-taskdef>BUILD SUCCESSFUL
> Total time : 1 seconds
> Finished at : Wednesday, August 24, 2005 4:01:53 PM PDT
> vs ant:
> $ ant shouldfail
> Buildfile: build.xml
> shouldfail:
> BUILD FAILED
> /private/tmp/element-without-taskdef/build.xml:8: Could not create task or
> type of type: element-without-taskdef.
> ...
--
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
