Thanks Hans for you input.
Works well. Since this work is at the moment more a "nice to have" i
invest just minutes per day/week on this build stuff. So to get the
whole build run will take some time. I let you hear about my efforts
and of cause about my problems while moving a osgi/eclipse rcp based
app to gradle.
regards,
René
Am 24.09.2008 um 14:59 schrieb Hans Dockter:
On Sep 24, 2008, at 12:50 AM, Rene Groeschke wrote:
Hello gradle,
I have nearly finished an Eclipse RCP project. At the moment my
releng is based on ant, which starts an eclipse pde build. this
takes a lot of time and isn't what i expect from a clear build
process. First I tried the great apache ivy with bushel. But plain
ivy and bushel seems to be very complicated.
After viewing the gradle prasentation in berlin, being a fan of
groovy and just finishing my holidays I decided to move my build to
gradle.
My app is based on different projects, which represent the
different osgi bundles. I decided to move to gradle step by step:
1. build every osgi bundle project with gradle
2. assembly all builds to a ready deployable application
3. (nice to have) base the ivy dependecies on my bundle manifests.
To resolve the bundle dependencies I add them manually to my gradle
file and use the
addFlatDirResolver('lib', target_plugins) command to resolve my
eclipse plugin directory
and here (TADAAA) i got my first problem:
eclipse bundles are named with a '_' to divide the version number
from the lib name. is there a better way to
use addFlatDirResolver without replacing all '_' with a '-'?
Nice to hear from you Rene :)
You can say for example:
addFlatDirResolver(...).addArtifactPattern('[artifact]_[revision].
[ext]')
This is Ivy syntax.
- Hans
with kind regards
René Gröschke
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
