For our gradle transition, we found it necessary to create a "local"
repository for testing out our gradle plugin builds. This is a
"local" folder repository that lives in the gradle cache folder and we
run a gradle "uploadArchiveLocal" task that publishes to the local
repo. Before we had this, we had to publish to the global repo to run
our integration tests.
To me, it seems odd that it was necessary to create this local repo.
This seems a like a fairly common need to me, and I have been told
that maven has this function built in. Is this a feature that is
planned for gradle? Or is our plugin development approach
fundamentally flawed in some way? I think we will need this approach
for our product integration tests as well....
Any comments would be appreciated.
Thanks,
phil
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
