Resending to dev ...

________________________________

From: Glaeser, Thomas 
Sent: Friday, March 04, 2011 1:01 AM
To: 'Niclas Hedhman'
Cc: '[email protected]'
Subject: RE: Gradle's OSGi plugin



Hi Niclas - Thanks for contacting me on this. I noticed recently that
qi4j switched to Gradle ... Good move ...

I believe that my early comments on GRADLE-1107 were wrong and initially
I was proposing some form of redefinition of the configurations meaning.
However with my statement from 3/Dec/10 I believe I'm right. So let me
explain a little more detailed ...

Let's ignore initially that the *runtime configurations usually extend
the *compile configurations. I'm not 100% sure if this is always the
case, but I believe all configurations in Gradle follow this paradigm.

Let's also ignore for now that I proposed a third pair of configurations
called supply*. We can come back to this when we are in agreement on the
other two pairs of configurations.

So for now let's consider these two runtime configurations only:

(1) runtime
(2) providedRuntime

These configurations exist already in Gradle and Maven and we do not
want to redefine them.

The two configurations are required for building Web Archives (WAR).
Please see the Gradle WAR Plugin documentation
<http://www.gradle.org/1.0-milestone-1/docs/userguide/war_plugin.html#N1
269E>  for their meaning. What we can take from here is that the
libraries from the runtime configuration are embedded into the WAR while
the dependencies from the providedRuntime configuration are provided by
the hosting container.

Now, how does this all map to Web Application Bundle (WAB)? Please see
the BND documentation <http://www.aqute.biz/Bnd/Format#wab> .

So someone who used the Gradle War Plugin should get a valid WAB by
simply also applying the OSGi Plugin. In my opinion this would be the
first use case the new OSGi Plugin needs to pass.

Please let me know if this makes all sense to you. I'm very much
interested in getting this right. So let's stay in touch on this topic.

Cheers,
Thomas


-----Original Message-----
From: Niclas Hedhman [mailto:[email protected]
<mailto:[email protected]> ]
Sent: Thursday, March 03, 2011 5:45 PM
To: Glaeser, Thomas
Cc: [email protected]
Subject: Gradle's OSGi plugin


[5] You wrote in GRADLE-1107 "runtime extends compile, Dependencies
declared under this configuration will be embedded into the OSGi
bundle". It doesn't sound right at all, unless you intend to redefine
what the configurations mean. Now, I kind of oppose that since one of
the projects I work on, Qi4j (http://www.qi4j.org <http://www.qi4j.org>
) we need to produce jars, ivy and maven poms that are useful for
stand-alone apps as well.
So I don't see how 'runtime' can get a new meaning.


Reply via email to