Ok, thanks! I almost have enough of a shell to start tying Gradle in.
I created a separation between the IDE and the main plugin logic so
that I can test the plugin with a headless IDE. I'm working on
learning Groovy unit testing for Java code real quick and starting my
first tests for the basic startup/shutdown of the plugin and settings
storage. Then I'll continue into the body and revamp the main
methods. I'll be sure to update before I do the refactoring so the
patch is close to the head of SVN.
--j
On 4-Jun-08, at 11:51 PM, Hans Dockter wrote:
Hi Jayson,
On Jun 5, 2008, at 8:04 AM, Jayson Minard wrote:
Hey Hans,
I really could use some restructuring of the main() startup point
for Gradle. As it stands, going through the ToolsMain or Main
classes isolates me from being able to see the internals of the
build as it happens, or when it is between stages, or even done.
I have expected this issue :)
I also may want to have events that allow me to post progress other
than just log output.
http://jira.codehaus.org/browse/GRADLE-3
Do you have any issues with me taking a stab at the refactoring?
Or would you rather have a list of requirements (they'll be coming
incrementally as I discover them) for you to make changes towards?
No issues at all. That would be awesome. I'm really looking forward
that people like you getting into the internals of Gradle, give
feedback and make it more and more a collaborative effort.
If you have an issue you want me to solve just ping me and I will do
it with high priority.
Lastly, are you aware of any static variables (i.e. static cache)
that I may run into when running multiple instances of Gradle at
the same time across different projects?
Gradle itself has no static state except the loggers. For the two-
phase logging I need to refactor logging anyway and could have a
look into this. Right now nothing will break because of logging, the
logs would be just not separated. As there is console logging only
right now this is no problem. There could be also issues with Ivy if
multiple Gradle instances use the same cache. Ivy offers some
isolation functionality for this, but I haven't had a look at this
yet.
- Hans
Thanks!
-- Jayson
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
