On Jan 13, 2009, at 1:57 PM, tao wen wrote:
Yeah, that is what I am doing currently. But is that annoying to
have to keep a list of java project name, and a list of groovy
project name. What if they have more variates?
As said, in this case this is not even necessary. You can declare
usePlugin('java') for any groovy project. And later on you can declare
usePlugin('groovy') specifically for the groovy project.
You can also do more advanced filtering based on project properties.
- Hans
2009/1/13 Hans Dockter <[email protected]>
On Jan 13, 2009, at 10:40 AM, tao wen wrote:
Hi,
I have a multi-project structure like this
root
- D groovyPrj
- D javaPrj1
- D javaPrj2
in the root project I shared some common dependencies and other
default settings (like test includes/excludes). What is the best way
to let the groovyPrj share the root settings as well? The difficulty
is currently, I am using
subprojects {
usePlugin('java')
...
}
this will not work for groovy project.
As the Groovy plugin works on top of the Java plugin you can safely
declare usePlugin('java') for the Groovy project, and later declare
usePlugin('groovy'). It has the same effect as just declaring
usePlugin('java').
But you could also do something like:
subprojects {
if (!project.name.startsWith('groovy')) {
usePlugin('java')
}
...
}
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
