To clarify...

I do nothing to explicitly enable daemon. As far as I know, it is still disabled by default.

And no, I use `gradle`, not `/.gradlew` to execute.


On 05/05/2011 10:31 AM, Steve Ebersole wrote:
Not unless it is enabled by default

On May 5, 2011 10:20 AM, "Szczepan Faber" <[email protected]
<mailto:[email protected]>> wrote:
 > Hey Steve,
 >
 > There was an earlier email on the mailing list with similar problem -
 > apparently it occurred when gradle was running with a deamon. Are you
 > starting gradle using ./gradlew ?
 >
 > Would it be feasible workaround if you try running without a deamon?
 >
 > Hope that helps!
 > Szczepan
 >
 > On Thu, May 5, 2011 at 2:34 PM, Steve Ebersole <[email protected]
<mailto:[email protected]>> wrote:
 >> This is holding up a release
 >>
(http://lists.jboss.org/pipermail/hibernate-dev/2011-May/006411.html), so
 >> please if anyone has ideas...
 >>
 >>
 >> On 05/04/2011 10:18 PM, Steve Ebersole wrote:
 >>>
 >>> I am trying to update my gradle-upload-auth-plugin to work with
 >>> gradle-1.0-milestone-2. Apparently between m1 and m2 the return type of
 >>> org.gradle.api.artifacts.maven.MavenDeployer.getRespository() changed
 >>> from org.apache.maven.artifact.ant.RemoteRepository to Object. No
 >>> worries, so I tried to just cast the returned Object to
 >>> org.apache.maven.artifact.ant.RemoteRepository. But I get this lovely
 >>> message:
 >>>
 >>> Cause: org.apache.maven.artifact.ant.RemoteRepository cannot be cast to
 >>> org.apache.maven.artifact.ant.RemoteRepository
 >>>
 >>> I have to assume this is some form of classpath issue.
 >>>
 >>> Here is my buildscript section:
 >>> buildscript {
 >>> repositories {
 >>> mavenLocal()
 >>> mavenRepo name: 'jboss-nexus', urls:
 >>> "https://repository.jboss.org/nexus/content/groups/public/";
 >>> mavenRepo name: "jboss-snapshots", urls:
 >>> "http://snapshots.jboss.org/maven2/";
 >>> }
 >>> dependencies {
 >>> classpath
 >>> 'org.hibernate.build.gradle:gradle-upload-auth-plugin:1.0.2-SNAPSHOT'
 >>> }
 >>> }
 >>>
 >>> The dependency is being resolved correctly.
 >>>
 >>> Any ideas?
 >>>
 >>
 >> --
 >> Steve Ebersole <[email protected] <mailto:[email protected]>>
 >> http://hibernate.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
 >
 >

--
Steve Ebersole <[email protected]>
http://hibernate.org

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to