beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chad Schoettger (JIRA)" <...@beehive.apache.org>
Subject [jira] Resolved: (BEEHIVE-372) Change AptTask to do up-front copying of all files
Date Mon, 28 Nov 2005 22:28:41 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-372?page=all ]
     
Chad Schoettger resolved BEEHIVE-372:
-------------------------------------

    Resolution: Won't Fix

Moving away from specific file extensions for controls (using .java instead) has the same
effect and won't cause back compat issues.

> Change AptTask to do up-front copying of all files
> --------------------------------------------------
>
>          Key: BEEHIVE-372
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-372
>      Project: Beehive
>         Type: Improvement
>   Components: Controls
>     Versions: V1Beta
>     Reporter: Kyle Marvin
>     Assignee: Chad Schoettger
>     Priority: Minor

>
> If the ANT AptTask uses the "compileByExtension" flag, it incrementally processes each
file extension on the input list one by one. For each extension, it will copy all input sources
files of that extension to a .java file, then process/compile all files w/ the same extension
as a group. (The copy is needed because apt will only take .java files as input)
> The rub comes if a file w/ one extension wants to reference a type declared in a file
w/ a different non-java extension that is processed after it. Because the copy-to-java doesn't
happen until the latter extension is reached in the list, the source parser can't find it
and will ultimately give unresolved type errors.
> A better algorithm would be to do the copy-to-java step for all input files as a precursor
to attempting to process any of them. This will offer much more flexibility in cross-extension
type references.
> As a workaround, the user is always able to handle dependency ordering more directly
by breaking a project build down into a series of <apt> invocations based upon dependency
ordering requirements.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message