Mailing-List: contact dev-help@beehive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Developers" <dev@beehive.apache.org>
Message-ID: <22808087.1145394978667.JavaMail.jira@brutus>
Date: Tue, 18 Apr 2006 21:16:18 +0000 (GMT+00:00)
From: "matt c (JIRA)" <dev@beehive.apache.org>
To: dev@beehive.apache.org
Subject: [jira] Commented: (BEEHIVE-372) Change AptTask to do up-front
 copying of all files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/BEEHIVE-372?page=comments#action_12374996 ] 

matt c commented on BEEHIVE-372:
--------------------------------

Verified as fixed.  This bug can be closed, as the original issue revolves around using the non-java extensions, and that is no longer a supported way of creating webservices and jpfs in beehive.

This bug can be closed.

> 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: Jacob Danner
>     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