Yes, you are right of course. My build didn't see the dependency until
I did clean, reverted and sorry for the noise. Just installed gradle
as well.
Kalle
On Mon, May 23, 2011 at 10:52 PM, Howard Lewis Ship wrote:
> Not sure why this was necessary ... tapestry-core has a transitive
> dependency
The command line works well for me, but a Gradle-aware plugin for
Eclipse was just released. I haven't checked it out yet. I'm looking
forward to deleting the Maven POM files, once all the tools and such
are ready. For the moment, I'm maintaining things in two places.
On Tue, May 24, 2011 at 5:4
There's technically a plugin available for IntelliJ, although I found it
faster/easier to use command-line gradle rather than the plugin.
Robert
On May 24, 2011, at 5/247:38 AM , Igor Drobiazko wrote:
> As far as I know there is no plugin available that provides a comparable
> functionality as
As far as I know there is no plugin available that provides a comparable
functionality as m2eclipse. You can generate eclipse project configuration
by executing "gradle eclipse".
http://www.gradle.org/eclipse_plugin.html
On Tue, May 24, 2011 at 2:15 PM, Ulrich Stärk wrote:
> Btw, how good is ID
Btw, how good is IDE integration for Gradle? Until now I just pointed m2eclipse
to the Tapestry SVN
repo and it imported everything including setting up the multi-module project,
populating the
classpath with Maven dependencies and so on so that it was extremely easy to
get up and running.
Uli
Gradle creates maven artifacts, so our users will not even know that we
switched to gradle. Tapestry jars will be still available in Maven repos.
However, I'm not sure about the status of the migration progress.
On Tue, May 24, 2011 at 1:37 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> w
On Tue, 24 May 2011 07:10:27 -0300, Igor Drobiazko
wrote:
Why do we actually still maintain Maven poms? Shouldn't we remove them
as we are on gradle now?
Unless Gradle is set up Maven POMs, removing the existing ones would be a
pain to all the Maven users out there (including me), and th
Why do we actually still maintain Maven poms? Shouldn't we remove them as we
are on gradle now?
On Tue, May 24, 2011 at 7:52 AM, Howard Lewis Ship wrote:
> Not sure why this was necessary ... tapestry-core has a transitive
> dependency on plastic via tapestry-ioc.
>
> On Mon, May 23, 2011 at 8:1
Not sure why this was necessary ... tapestry-core has a transitive
dependency on plastic via tapestry-ioc.
On Mon, May 23, 2011 at 8:16 PM, wrote:
> Author: kaosko
> Date: Tue May 24 03:16:38 2011
> New Revision: 1126839
>
> URL: http://svn.apache.org/viewvc?rev=1126839&view=rev
> Log:
> Fix cor
