You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Lawrence Jones (JIRA)" <be...@incubator.apache.org> on 2005/02/10 20:17:15 UTC
[jira] Created: (BEEHIVE-272) We should change ControlAssemblyContext.createJavaOutputFile() to ControlAssemblyContext.getSrcOutputDir()
We should change ControlAssemblyContext.createJavaOutputFile() to ControlAssemblyContext.getSrcOutputDir()
----------------------------------------------------------------------------------------------------------
Key: BEEHIVE-272
URL: http://issues.apache.org/jira/browse/BEEHIVE-272
Project: Beehive
Type: Bug
Components: Controls
Versions: V1Beta
Environment: Windows
Reporter: Lawrence Jones
It is odd to "special-case" .java files as output from the controls assembly phase. We do this by providing a createJavaOutputFile() API on the ControlAssemblyContext context object whereas what we should be doing is providing just the output directory for compilable source and letting the author of the assembler do whatever he/she wants with that directory.
--
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
[jira] Resolved: (BEEHIVE-272) We should change ControlAssemblyContext.createJavaOutputFile() to ControlAssemblyContext.getSrcOutputDir()
Posted by "Kenneth Tam (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-272?page=all ]
Kenneth Tam resolved BEEHIVE-272:
---------------------------------
Resolution: Fixed
Fixed as of rev 164906. createJavaOutputFile() is now gone.
> We should change ControlAssemblyContext.createJavaOutputFile() to ControlAssemblyContext.getSrcOutputDir()
> ----------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-272
> URL: http://issues.apache.org/jira/browse/BEEHIVE-272
> Project: Beehive
> Type: Bug
> Components: Controls
> Versions: V1Beta
> Environment: Windows
> Reporter: Lawrence Jones
> Assignee: Kenneth Tam
> Fix For: V1
>
> It is odd to "special-case" .java files as output from the controls assembly phase. We do this by providing a createJavaOutputFile() API on the ControlAssemblyContext context object whereas what we should be doing is providing just the output directory for compilable source and letting the author of the assembler do whatever he/she wants with that directory.
--
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
[jira] Updated: (BEEHIVE-272) We should change ControlAssemblyContext.createJavaOutputFile() to ControlAssemblyContext.getSrcOutputDir()
Posted by "Kenneth Tam (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-272?page=history ]
Kenneth Tam updated BEEHIVE-272:
--------------------------------
Assign To: Kenneth Tam
Fix Version: V1
createJavaOutputFile() is now deprecated, and getSrcOutputDir() is in place.
> We should change ControlAssemblyContext.createJavaOutputFile() to ControlAssemblyContext.getSrcOutputDir()
> ----------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-272
> URL: http://issues.apache.org/jira/browse/BEEHIVE-272
> Project: Beehive
> Type: Bug
> Components: Controls
> Versions: V1Beta
> Environment: Windows
> Reporter: Lawrence Jones
> Assignee: Kenneth Tam
> Fix For: V1
>
> It is odd to "special-case" .java files as output from the controls assembly phase. We do this by providing a createJavaOutputFile() API on the ControlAssemblyContext context object whereas what we should be doing is providing just the output directory for compilable source and letting the author of the assembler do whatever he/she wants with that directory.
--
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
[jira] Closed: (BEEHIVE-272) We should change ControlAssemblyContext.createJavaOutputFile() to ControlAssemblyContext.getSrcOutputDir()
Posted by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-272?page=all ]
Jeremiah Johnson closed BEEHIVE-272:
------------------------------------
Assign To: Jeremiah Johnson (was: Kenneth Tam)
createJavaOutputFile is no longer a method in ControlAssemblyContext.
> We should change ControlAssemblyContext.createJavaOutputFile() to ControlAssemblyContext.getSrcOutputDir()
> ----------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-272
> URL: http://issues.apache.org/jira/browse/BEEHIVE-272
> Project: Beehive
> Type: Bug
> Components: Controls
> Versions: V1Beta
> Environment: Windows
> Reporter: Lawrence Jones
> Assignee: Jeremiah Johnson
> Fix For: V1
>
> It is odd to "special-case" .java files as output from the controls assembly phase. We do this by providing a createJavaOutputFile() API on the ControlAssemblyContext context object whereas what we should be doing is providing just the output directory for compilable source and letting the author of the assembler do whatever he/she wants with that directory.
--
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