[ http://issues.apache.org/jira/browse/BEEHIVE-487?page=history ]
Kyle Marvin reassigned BEEHIVE-487:
-----------------------------------
Assign To: Rich Feit (was: Kyle Marvin)
There really isn't a way to do this w/ generic APT; the basic processing model
is code/filegen, followed by compile, and there is no 'callback' model to let a
processor know that a downstream compile failed.
Even if it did, you'd have to be careful what you did when you got the
notification. You might actually end up deleting artifacts you need to
diagnose the failure (for example, if it failed on a code-generated artifact).
Is the fact that there are some generated artifacts even though the build
failed? In a regular compile failure, I might (I think) be left w/ some
.class files for part of the build that did succeed.
As long as we give a reasonable error indicating that the build failed, the
fact that it is in some intermediate state just doesn't seem like a big issue
to me.
In other words, I'd be tempted to "Won't Fix" this. Kicking back to Rich to
let him make the judgement call.
Interested parties should add a comment to this JIRA issue.
> The Struts Config for the attached pageflow is being generated even when it
> generates compiler errors
> -----------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-487
> URL: http://issues.apache.org/jira/browse/BEEHIVE-487
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1
> Reporter: Alejandro Ramirez
> Assignee: Rich Feit
> Fix For: V1
> Attachments: Test10.zip
>
> 1.- Compile the attached pageflow.
> Expected: The compiler should generate the following error message and the
> struts config file should NOT be generated:
> [apt] <pathToYourPageFlow>\Controller.java:38: ')' expected
> [apt] myattribute = "testing")
> [apt] ^
> [apt] 1 error
> Actual: The compiler throws the error above. However, the struts config
> file for the pageflow is generated (see attached).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
