Hi,
1) I think this is an issue with the way the plugin executes against "peer"
projects - it first executes against the project you happen to be in, then
the other projects defined in settings.gradle. This doesn't happen when
you've got a project structure like:
/RASFFRoot/
core
configurator
web
I don't know why this has changed between 0.6 and 0.8.
2) We've noticed something similar though weirdly it on happens with one
project. Gradle consumes loads of CPU before eventually finishing.
Both things are on my list of "stuff to look at if someone else doesn't
first" as it's annoying people at work.
Phil.
Rwanou wrote:
>
> Hi all,
>
> I started migrating from 0.6 to 0.8, and I'm facing a real issue with the
> Eclipse plugin. It was working (quite) good before, now it's just not
> working at all...
> 2 main problems :
>
> 1) my multi-project architecture is this way:
> /RASFF-configurator
> /RASFF-core
> /RASFF-web/RASFF-web
>
> knowing that core is the central piece, and that configurator and web both
> depend on it.
>
> the first issue is that the Eclipse plugin, when running
> RASFF-configurator", is complaining that it cannot find "RASFF-core.jar"
> in any repository. Of course, I didn't deploy any jar yet... So why is the
> eclipse plugin trying to run "configurator" tasks first BEFORE running
> "core" task (whereas build task is doing ok)???
>
> 2) I suppressed configurator from the settings.gradle (web doesn't depend
> on it).
> the eclipseCp tasks takes 12 minutes for the RASFF-web project. How can
> that be? There is nothing that exotic, and all dependencies are downloaded
> already.
> Debugging leaves me with this last lines:
> 15:38:17.582 [main] DEBUG org.gradle.logging.IvyLoggingAdaper -
> resolve done (10390ms resolve - 157ms download)
> 15:38:17.582 [main] DEBUG o.g.a.i.a.i.DefaultIvyDependencyResolver -
> Timing: Ivy resolve took 11.813 secs
> 15:38:17.707 [main] DEBUG o.g.a.i.a.i.DefaultIvyReportConverter - Timing:
> Translating report for configuration configuration 'testRuntime' took
> 0.125 secs
> 15:50:27.678 [main] DEBUG org.gradle.api.internal.AbstractTask - Finished
> executing Task: :RASFF-web:RASFF-web:eclipseCp
> 15:50:27.678 [main] DEBUG o.g.execution.DefaultTaskExecuter - Timing:
> Executing the DAG took 12 mins 22.737 secs
> 15:50:27.678 [main] INFO org.gradle.Main -
> BUILD SUCCESSFUL
>
> Any help and information would really be appreciated.
> Thanks in advance
>
>
>
--
View this message in context:
http://www.nabble.com/eclipse-plugin-fails-and-stalls-tp25681650p25822466.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
