> Is this a bug, do I need to raise an issue? Yes, please. Looks like a bug to me.
Cheers! On Thu, Jul 14, 2011 at 6:09 AM, Mike Mills <[email protected]> wrote: > I have come across an issue with the idea plugin and dependency > declarations with gradle 1.0 milestone 3. > > > if you create a simple project with just these dependency declarations > coming from mavenCentral: > > dependencies { > runtime (group: 'org.springframework.ws', name: 'spring-ws-core', > version: '1.5.9') { > exclude(group: 'commons-logging', module: 'commons-logging') > exclude(group: 'wsdl4j', module: 'wsdl4j') > } > > testCompile group: 'junit', name: 'junit', version: '4.4' > testCompile (group: 'org.springframework', name: 'spring-context', > version: '2.5.5') > } > > > then create a simple test case: > > @Test > public void someTest() { > > ClassPathXmlApplicationContext context = new > ClassPathXmlApplicationContext(); > context.setAllowBeanDefinitionOverriding(false); > } > > > When you run "gradle build", the test case is executed fine. > > When you try "gradle idea", and open the test case, you will find that > Idea does not have the spring-context jar in its test scope. > > As far as I can tell the above dependency declaration gets resolved to > have spring-context set to "runtime" scope in Idea. This is due to > spring-context being a transitive dependency of spring-ws-core. > > If you remove the runtime dependency from build.gradle, then both > "gradle build" and "gradle idea" work as expected. > > Currently, after running "gradle idea" I have to manually go into the > dependencies section and set the spring-context to test scope. > > Is this a bug, do I need to raise an issue? > > Regards, > > Mike > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Szczepan Faber Principal engineer@gradleware Lead@mockito --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
