eclipse plugin fails and stalls
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
eclipse plugin fails and stalls
by Rwanou
::
Rate this Message:
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 |
|
|
Re: eclipse plugin fails and stalls
by Phil Messenger
::
Rate this Message:
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.
|
|
|
RE: eclipse plugin fails and stalls
by Rwanou
::
Rate this Message:
Thanks for your answer,
1) indeed my project looks like you describe: I changed the names so they describe best my structure. I have 3 projects in total. RASFF/Configurator RASFF/Core RASFF/WEB/WAR (WEB is not a project, just a folder containing all the WEB related projects, being only one at this time). So when I execute "gradle build" inside the RASFF (root) folder, it will start by building Core, then Configurator and then WAR. If I execute "gradle eclipse" in the same RASFF (root) folder, then it will start with Configurator. I have the feeling that the eclipse task will not look at the dependencies between projects, but rather process within it's folder in alphabetical order. I didn't test this though. 2) Weird indeed. Let me know if you need my configurations, in order to reproduce the behaviour. Let me note that our maven repositories are proxies, but it shouldn't matter since all libsare already downloaded when hanging occurs. Erwan -----Original Message----- From: Phil Messenger [mailto:phil@...] Sent: Friday, October 09, 2009 4:47 PM To: user@... Subject: Re: [gradle-user] eclipse plugin fails and stalls 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 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
RE: eclipse plugin fails and stalls
by Phil Messenger
::
Rate this Message:
This is a daft question, but does Configuration have a project dependency on Core declared in the build.gradle file?
Phil.
|
|
|
RE: eclipse plugin fails and stalls
by Rwanou
::
Rate this Message:
I have this:
dependencies { // needed for compile compile project(':RASFF-core') compile module("eu.sanco.gras:gras:1.15.6") { dependency("eu.sanco:saas:1.1.5") dependency("commons-lang:commons-lang:2.3") (...) I tried to put: dependsOn(":RASFF-core") with no success. I could give it a second shot if you like. Erwan -----Original Message----- From: Phil Messenger [mailto:phil@...] Sent: Friday, October 09, 2009 5:03 PM To: user@... Subject: RE: [gradle-user] eclipse plugin fails and stalls This is a daft question, but does Configuration have a project dependency on Core declared in the build.gradle file? Phil. Rwanou wrote: > > Thanks for your answer, > > 1) indeed my project looks like you describe: > I changed the names so they describe best my structure. I have 3 projects > in total. > RASFF/Configurator > RASFF/Core > RASFF/WEB/WAR (WEB is not a project, just a folder containing all the WEB > related projects, being only one at this time). > > So when I execute "gradle build" inside the RASFF (root) folder, it will > start by building Core, then Configurator and then WAR. > If I execute "gradle eclipse" in the same RASFF (root) folder, then it > will start with Configurator. > > I have the feeling that the eclipse task will not look at the dependencies > between projects, but rather process within it's folder in alphabetical > order. I didn't test this though. > > 2) Weird indeed. Let me know if you need my configurations, in order to > reproduce the behaviour. Let me note that our maven repositories are > proxies, but it shouldn't matter since all libsare already downloaded when > hanging occurs. > > Erwan > > -----Original Message----- > From: Phil Messenger [mailto:phil@...] > Sent: Friday, October 09, 2009 4:47 PM > To: user@... > Subject: Re: [gradle-user] eclipse plugin fails and stalls > > > 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 > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- View this message in context: http://www.nabble.com/eclipse-plugin-fails-and-stalls-tp25681650p25822718.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 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |
