JavaFX and Boutique

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

JavaFX and Boutique

Andrus Adamchik
I just committed my first experiment with JavaFX and Bootique [1]. It enables injection into JavaFX controllers [2] and gives access to DI from the Application class. The implementation is a bit invasive (requires framework superclass of Application), as we can't easily take over the startup sequence, but otherwise works fine. At least in my simple example :)

My total exposure to JavaFX is a total of 2 hours, so I am pretty sure I overlooked other useful things we can do between Bootique and JavaFX. But that's a start. This code will likely become the future bootique-javafx module.

Mike, were we able to get a new Git repo for the JavaFX modeler?

Andrus

[1] https://github.com/andrus/jfxsandbox
[2] https://github.com/andrus/jfxsandbox/blob/master/src/main/java/com/foo/RootController.java
Reply | Threaded
Open this post in threaded view
|

Re: JavaFX and Boutique

Michael Gentry
A new Git repository is still on my to-do list.  Been a relatively busy
time, so it's been bumped below other more important things.

mrg


On Sat, Dec 10, 2016 at 12:55 PM, Andrus Adamchik <[hidden email]>
wrote:

> I just committed my first experiment with JavaFX and Bootique [1]. It
> enables injection into JavaFX controllers [2] and gives access to DI from
> the Application class. The implementation is a bit invasive (requires
> framework superclass of Application), as we can't easily take over the
> startup sequence, but otherwise works fine. At least in my simple example :)
>
> My total exposure to JavaFX is a total of 2 hours, so I am pretty sure I
> overlooked other useful things we can do between Bootique and JavaFX. But
> that's a start. This code will likely become the future bootique-javafx
> module.
>
> Mike, were we able to get a new Git repo for the JavaFX modeler?
>
> Andrus
>
> [1] https://github.com/andrus/jfxsandbox
> [2] https://github.com/andrus/jfxsandbox/blob/master/src/
> main/java/com/foo/RootController.java
Reply | Threaded
Open this post in threaded view
|

Re: JavaFX and Boutique

Andrus Adamchik
Buddha (and others who wanted to join the fun) --

As you see it is taking us a bit of time to get the JavaFX Modeler project setup. Though we are getting there. If you feel like digging inside other parts of Cayenne in the meantime, I posted a broad TODO list for the next release recently [1]. Perhaps you can give us a hand on some of those tasks?

A good candidate (if you work with Gradle at all) may be #10 - providing Gradle versions of Cayenne tools:

* cgen - template-based class generator.
* cdbimport - DB to ORM synchronization tool.
* cdbgen - ORM to DB generator tool.

These tools work from the Modeler, and are also integrated into Ant and Maven [2]. The Gradle option currently is to call the Ant tasks. We'd like to provide "Gradle-native" plugins instead. There are a few options for writing those. We lean towards using Java (to isolate us from the whole Groovy vs. Kotlin thing going on in the Gradle world).

Other tasks from my list [1] are #6 and #7. They are isolated and mostly well-defined, though will require a bit more discussion and delving into Cayenne runtime stack.

So what do you think?

Andrus


[1] https://lists.apache.org/thread.html/b69fa0eb0457507d5720103a9627252c696b2faec0b71db52762a7c7@%3Cdev.cayenne.apache.org%3E
[2] http://cayenne.apache.org/docs/4.0/cayenne-guide/including-cayenne-in-project.html#maven-projects



> On Dec 12, 2016, at 11:52 PM, Michael Gentry <[hidden email]> wrote:
>
> A new Git repository is still on my to-do list.  Been a relatively busy
> time, so it's been bumped below other more important things.
>
> mrg
>
>
> On Sat, Dec 10, 2016 at 12:55 PM, Andrus Adamchik <[hidden email]>
> wrote:
>
>> I just committed my first experiment with JavaFX and Bootique [1]. It
>> enables injection into JavaFX controllers [2] and gives access to DI from
>> the Application class. The implementation is a bit invasive (requires
>> framework superclass of Application), as we can't easily take over the
>> startup sequence, but otherwise works fine. At least in my simple example :)
>>
>> My total exposure to JavaFX is a total of 2 hours, so I am pretty sure I
>> overlooked other useful things we can do between Bootique and JavaFX. But
>> that's a start. This code will likely become the future bootique-javafx
>> module.
>>
>> Mike, were we able to get a new Git repo for the JavaFX modeler?
>>
>> Andrus
>>
>> [1] https://github.com/andrus/jfxsandbox
>> [2] https://github.com/andrus/jfxsandbox/blob/master/src/
>> main/java/com/foo/RootController.java

Reply | Threaded
Open this post in threaded view
|

Re: JavaFX and Boutique

buddha
Hey Andrus,

I just logged into the jira. We have had a discussion in our java user group monthly meeting this Saturday. I never worked with Gradle myself, but there are a few who did in JUG. I will look at other tasks in the list you have given, and let u know. Or, may be I will learn and take help of some of the people in JUG to take up the ones you listed below.  

Thanks
Buddha

On 13/12/16, 11:21 PM, "Andrus Adamchik" <[hidden email]> wrote:

    Buddha (and others who wanted to join the fun) --
   
    As you see it is taking us a bit of time to get the JavaFX Modeler project setup. Though we are getting there. If you feel like digging inside other parts of Cayenne in the meantime, I posted a broad TODO list for the next release recently [1]. Perhaps you can give us a hand on some of those tasks?
   
    A good candidate (if you work with Gradle at all) may be #10 - providing Gradle versions of Cayenne tools:
   
    * cgen - template-based class generator.
    * cdbimport - DB to ORM synchronization tool.
    * cdbgen - ORM to DB generator tool.
   
    These tools work from the Modeler, and are also integrated into Ant and Maven [2]. The Gradle option currently is to call the Ant tasks. We'd like to provide "Gradle-native" plugins instead. There are a few options for writing those. We lean towards using Java (to isolate us from the whole Groovy vs. Kotlin thing going on in the Gradle world).
   
    Other tasks from my list [1] are #6 and #7. They are isolated and mostly well-defined, though will require a bit more discussion and delving into Cayenne runtime stack.
   
    So what do you think?
   
    Andrus
   
   
    [1] https://lists.apache.org/thread.html/b69fa0eb0457507d5720103a9627252c696b2faec0b71db52762a7c7@%3Cdev.cayenne.apache.org%3E
    [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/including-cayenne-in-project.html#maven-projects
   
   
   
    > On Dec 12, 2016, at 11:52 PM, Michael Gentry <[hidden email]> wrote:
    >
    > A new Git repository is still on my to-do list.  Been a relatively busy
    > time, so it's been bumped below other more important things.
    >
    > mrg
    >
    >
    > On Sat, Dec 10, 2016 at 12:55 PM, Andrus Adamchik <[hidden email]>
    > wrote:
    >
    >> I just committed my first experiment with JavaFX and Bootique [1]. It
    >> enables injection into JavaFX controllers [2] and gives access to DI from
    >> the Application class. The implementation is a bit invasive (requires
    >> framework superclass of Application), as we can't easily take over the
    >> startup sequence, but otherwise works fine. At least in my simple example :)
    >>
    >> My total exposure to JavaFX is a total of 2 hours, so I am pretty sure I
    >> overlooked other useful things we can do between Bootique and JavaFX. But
    >> that's a start. This code will likely become the future bootique-javafx
    >> module.
    >>
    >> Mike, were we able to get a new Git repo for the JavaFX modeler?
    >>
    >> Andrus
    >>
    >> [1] https://github.com/andrus/jfxsandbox
    >> [2] https://github.com/andrus/jfxsandbox/blob/master/src/
    >> main/java/com/foo/RootController.java
   
   


Reply | Threaded
Open this post in threaded view
|

Re: JavaFX and Boutique

Rohit Vaidya
Hello Andrus,
+1 for the Gradle task. We will explore Gradle Native Plugins.

Thanks,
Rohit Vaidya


On Wed, Dec 14, 2016 at 12:00 AM, buddha <[hidden email]> wrote:

> Hey Andrus,
>
> I just logged into the jira. We have had a discussion in our java user
> group monthly meeting this Saturday. I never worked with Gradle myself, but
> there are a few who did in JUG. I will look at other tasks in the list you
> have given, and let u know. Or, may be I will learn and take help of some
> of the people in JUG to take up the ones you listed below.
>
> Thanks
> Buddha
>
> On 13/12/16, 11:21 PM, "Andrus Adamchik" <[hidden email]> wrote:
>
>     Buddha (and others who wanted to join the fun) --
>
>     As you see it is taking us a bit of time to get the JavaFX Modeler
> project setup. Though we are getting there. If you feel like digging inside
> other parts of Cayenne in the meantime, I posted a broad TODO list for the
> next release recently [1]. Perhaps you can give us a hand on some of those
> tasks?
>
>     A good candidate (if you work with Gradle at all) may be #10 -
> providing Gradle versions of Cayenne tools:
>
>     * cgen - template-based class generator.
>     * cdbimport - DB to ORM synchronization tool.
>     * cdbgen - ORM to DB generator tool.
>
>     These tools work from the Modeler, and are also integrated into Ant
> and Maven [2]. The Gradle option currently is to call the Ant tasks. We'd
> like to provide "Gradle-native" plugins instead. There are a few options
> for writing those. We lean towards using Java (to isolate us from the whole
> Groovy vs. Kotlin thing going on in the Gradle world).
>
>     Other tasks from my list [1] are #6 and #7. They are isolated and
> mostly well-defined, though will require a bit more discussion and delving
> into Cayenne runtime stack.
>
>     So what do you think?
>
>     Andrus
>
>
>     [1] https://lists.apache.org/thread.html/
> b69fa0eb0457507d5720103a9627252c696b2faec0b71db52762a7c7@%
> 3Cdev.cayenne.apache.org%3E
>     [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
> including-cayenne-in-project.html#maven-projects
>
>
>
>     > On Dec 12, 2016, at 11:52 PM, Michael Gentry <[hidden email]>
> wrote:
>     >
>     > A new Git repository is still on my to-do list.  Been a relatively
> busy
>     > time, so it's been bumped below other more important things.
>     >
>     > mrg
>     >
>     >
>     > On Sat, Dec 10, 2016 at 12:55 PM, Andrus Adamchik <
> [hidden email]>
>     > wrote:
>     >
>     >> I just committed my first experiment with JavaFX and Bootique [1].
> It
>     >> enables injection into JavaFX controllers [2] and gives access to
> DI from
>     >> the Application class. The implementation is a bit invasive
> (requires
>     >> framework superclass of Application), as we can't easily take over
> the
>     >> startup sequence, but otherwise works fine. At least in my simple
> example :)
>     >>
>     >> My total exposure to JavaFX is a total of 2 hours, so I am pretty
> sure I
>     >> overlooked other useful things we can do between Bootique and
> JavaFX. But
>     >> that's a start. This code will likely become the future
> bootique-javafx
>     >> module.
>     >>
>     >> Mike, were we able to get a new Git repo for the JavaFX modeler?
>     >>
>     >> Andrus
>     >>
>     >> [1] https://github.com/andrus/jfxsandbox
>     >> [2] https://github.com/andrus/jfxsandbox/blob/master/src/
>     >> main/java/com/foo/RootController.java
>
>
>
>
>


--
Regards,
Rohit Vaidya
Reply | Threaded
Open this post in threaded view
|

Re: JavaFX and Boutique

Andrus Adamchik
Hi Rohit,

Great! Feel free to ask questions here.

The best place to check which configuration properties are supported for each tool is probably the Maven "mojo" classes [1]. Maven plugin docs [2] should also be up-to-date.

Andrus

[1] https://github.com/apache/cayenne/tree/master/plugins/maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
[2] http://cayenne.apache.org/docs/4.0/cayenne-guide/including-cayenne-in-project.html#maven-projects

> On Dec 14, 2016, at 9:26 PM, Rohit Vaidya <[hidden email]> wrote:
>
> Hello Andrus,
> +1 for the Gradle task. We will explore Gradle Native Plugins.
>
> Thanks,
> Rohit Vaidya
>
>
> On Wed, Dec 14, 2016 at 12:00 AM, buddha <[hidden email]> wrote:
>
>> Hey Andrus,
>>
>> I just logged into the jira. We have had a discussion in our java user
>> group monthly meeting this Saturday. I never worked with Gradle myself, but
>> there are a few who did in JUG. I will look at other tasks in the list you
>> have given, and let u know. Or, may be I will learn and take help of some
>> of the people in JUG to take up the ones you listed below.
>>
>> Thanks
>> Buddha
>>
>> On 13/12/16, 11:21 PM, "Andrus Adamchik" <[hidden email]> wrote:
>>
>>    Buddha (and others who wanted to join the fun) --
>>
>>    As you see it is taking us a bit of time to get the JavaFX Modeler
>> project setup. Though we are getting there. If you feel like digging inside
>> other parts of Cayenne in the meantime, I posted a broad TODO list for the
>> next release recently [1]. Perhaps you can give us a hand on some of those
>> tasks?
>>
>>    A good candidate (if you work with Gradle at all) may be #10 -
>> providing Gradle versions of Cayenne tools:
>>
>>    * cgen - template-based class generator.
>>    * cdbimport - DB to ORM synchronization tool.
>>    * cdbgen - ORM to DB generator tool.
>>
>>    These tools work from the Modeler, and are also integrated into Ant
>> and Maven [2]. The Gradle option currently is to call the Ant tasks. We'd
>> like to provide "Gradle-native" plugins instead. There are a few options
>> for writing those. We lean towards using Java (to isolate us from the whole
>> Groovy vs. Kotlin thing going on in the Gradle world).
>>
>>    Other tasks from my list [1] are #6 and #7. They are isolated and
>> mostly well-defined, though will require a bit more discussion and delving
>> into Cayenne runtime stack.
>>
>>    So what do you think?
>>
>>    Andrus
>>
>>
>>    [1] https://lists.apache.org/thread.html/
>> b69fa0eb0457507d5720103a9627252c696b2faec0b71db52762a7c7@%
>> 3Cdev.cayenne.apache.org%3E
>>    [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
>> including-cayenne-in-project.html#maven-projects
>>
>>
>>
>>> On Dec 12, 2016, at 11:52 PM, Michael Gentry <[hidden email]>
>> wrote:
>>>
>>> A new Git repository is still on my to-do list.  Been a relatively
>> busy
>>> time, so it's been bumped below other more important things.
>>>
>>> mrg
>>>
>>>
>>> On Sat, Dec 10, 2016 at 12:55 PM, Andrus Adamchik <
>> [hidden email]>
>>> wrote:
>>>
>>>> I just committed my first experiment with JavaFX and Bootique [1].
>> It
>>>> enables injection into JavaFX controllers [2] and gives access to
>> DI from
>>>> the Application class. The implementation is a bit invasive
>> (requires
>>>> framework superclass of Application), as we can't easily take over
>> the
>>>> startup sequence, but otherwise works fine. At least in my simple
>> example :)
>>>>
>>>> My total exposure to JavaFX is a total of 2 hours, so I am pretty
>> sure I
>>>> overlooked other useful things we can do between Bootique and
>> JavaFX. But
>>>> that's a start. This code will likely become the future
>> bootique-javafx
>>>> module.
>>>>
>>>> Mike, were we able to get a new Git repo for the JavaFX modeler?
>>>>
>>>> Andrus
>>>>
>>>> [1] https://github.com/andrus/jfxsandbox
>>>> [2] https://github.com/andrus/jfxsandbox/blob/master/src/
>>>> main/java/com/foo/RootController.java
>>
>>
>>
>>
>>
>
>
> --
> Regards,
> Rohit Vaidya

Reply | Threaded
Open this post in threaded view
|

Re: JavaFX and Boutique

Rohit Vaidya
Hi Andrus,
1. The cayenne documentation says "Cayenne artifacts are available from
Maven Central for use with Maven, Ivy, Gradle or any other dependency
management tool" So what is the expected out of this task?
We found the following xml in the cayenne-tools project.

*<antlib>*
*  <taskdef name="cgen"
classname="org.apache.cayenne.tools.CayenneGeneratorTask"/>*
*  <taskdef name="cdbgen"
classname="org.apache.cayenne.tools.DbGeneratorTask"/>*
*  <taskdef name="cdataport"
classname="org.apache.cayenne.tools.DataPortTask"/>*
*  <taskdef name="cdbimport"
classname="org.apache.cayenne.tools.DbImporterTask"/>*
*</antlib>*
2.Will the Gradle native plugin be similar to the Ant classes that we see
under the cayennetools project?
3.Can we find some more information about these tools somewhere?
4.Is there a JIRA issue to track this task so that we can pick it up and
work on it?

Currently we are working on the following
1. At this point we have completed the tutorial
http://cayenne.apache.org/docs/4.0/tutorial/index.html
2. We are currently playing with Gradle native plugins.

Thanks,
Rohit Vaidya

On Thu, Dec 15, 2016 at 12:11 AM, Andrus Adamchik <[hidden email]>
wrote:

> Hi Rohit,
>
> Great! Feel free to ask questions here.
>
> The best place to check which configuration properties are supported for
> each tool is probably the Maven "mojo" classes [1]. Maven plugin docs [2]
> should also be up-to-date.
>
> Andrus
>
> [1] https://github.com/apache/cayenne/tree/master/plugins/
> maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
> [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
> including-cayenne-in-project.html#maven-projects
>
> > On Dec 14, 2016, at 9:26 PM, Rohit Vaidya <[hidden email]> wrote:
> >
> > Hello Andrus,
> > +1 for the Gradle task. We will explore Gradle Native Plugins.
> >
> > Thanks,
> > Rohit Vaidya
> >
> >
> > On Wed, Dec 14, 2016 at 12:00 AM, buddha <[hidden email]>
> wrote:
> >
> >> Hey Andrus,
> >>
> >> I just logged into the jira. We have had a discussion in our java user
> >> group monthly meeting this Saturday. I never worked with Gradle myself,
> but
> >> there are a few who did in JUG. I will look at other tasks in the list
> you
> >> have given, and let u know. Or, may be I will learn and take help of
> some
> >> of the people in JUG to take up the ones you listed below.
> >>
> >> Thanks
> >> Buddha
> >>
> >> On 13/12/16, 11:21 PM, "Andrus Adamchik" <[hidden email]>
> wrote:
> >>
> >>    Buddha (and others who wanted to join the fun) --
> >>
> >>    As you see it is taking us a bit of time to get the JavaFX Modeler
> >> project setup. Though we are getting there. If you feel like digging
> inside
> >> other parts of Cayenne in the meantime, I posted a broad TODO list for
> the
> >> next release recently [1]. Perhaps you can give us a hand on some of
> those
> >> tasks?
> >>
> >>    A good candidate (if you work with Gradle at all) may be #10 -
> >> providing Gradle versions of Cayenne tools:
> >>
> >>    * cgen - template-based class generator.
> >>    * cdbimport - DB to ORM synchronization tool.
> >>    * cdbgen - ORM to DB generator tool.
> >>
> >>    These tools work from the Modeler, and are also integrated into Ant
> >> and Maven [2]. The Gradle option currently is to call the Ant tasks.
> We'd
> >> like to provide "Gradle-native" plugins instead. There are a few options
> >> for writing those. We lean towards using Java (to isolate us from the
> whole
> >> Groovy vs. Kotlin thing going on in the Gradle world).
> >>
> >>    Other tasks from my list [1] are #6 and #7. They are isolated and
> >> mostly well-defined, though will require a bit more discussion and
> delving
> >> into Cayenne runtime stack.
> >>
> >>    So what do you think?
> >>
> >>    Andrus
> >>
> >>
> >>    [1] https://lists.apache.org/thread.html/
> >> b69fa0eb0457507d5720103a9627252c696b2faec0b71db52762a7c7@%
> >> 3Cdev.cayenne.apache.org%3E
> >>    [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
> >> including-cayenne-in-project.html#maven-projects
> >>
> >>
> >>
> >>> On Dec 12, 2016, at 11:52 PM, Michael Gentry <[hidden email]>
> >> wrote:
> >>>
> >>> A new Git repository is still on my to-do list.  Been a relatively
> >> busy
> >>> time, so it's been bumped below other more important things.
> >>>
> >>> mrg
> >>>
> >>>
> >>> On Sat, Dec 10, 2016 at 12:55 PM, Andrus Adamchik <
> >> [hidden email]>
> >>> wrote:
> >>>
> >>>> I just committed my first experiment with JavaFX and Bootique [1].
> >> It
> >>>> enables injection into JavaFX controllers [2] and gives access to
> >> DI from
> >>>> the Application class. The implementation is a bit invasive
> >> (requires
> >>>> framework superclass of Application), as we can't easily take over
> >> the
> >>>> startup sequence, but otherwise works fine. At least in my simple
> >> example :)
> >>>>
> >>>> My total exposure to JavaFX is a total of 2 hours, so I am pretty
> >> sure I
> >>>> overlooked other useful things we can do between Bootique and
> >> JavaFX. But
> >>>> that's a start. This code will likely become the future
> >> bootique-javafx
> >>>> module.
> >>>>
> >>>> Mike, were we able to get a new Git repo for the JavaFX modeler?
> >>>>
> >>>> Andrus
> >>>>
> >>>> [1] https://github.com/andrus/jfxsandbox
> >>>> [2] https://github.com/andrus/jfxsandbox/blob/master/src/
> >>>> main/java/com/foo/RootController.java
> >>
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Regards,
> > Rohit Vaidya
>
>


--
Regards,
Rohit Vaidya
Reply | Threaded
Open this post in threaded view
|

Re: JavaFX and Boutique

Aristedes Maniatis-2
You can easily enough call the ant tasks from gradle, and I've made a wrapper around those ant tasks. But I didn't bother to support the things I didn't need immediately, so it needs to be fleshed out.

https://github.com/ari/cayenne-gradle

Fork or copy and of that you find useful.

Ari


On 24/12/16 6:30pm, Rohit Vaidya wrote:

> Hi Andrus,
> 1. The cayenne documentation says "Cayenne artifacts are available from
> Maven Central for use with Maven, Ivy, Gradle or any other dependency
> management tool" So what is the expected out of this task?
> We found the following xml in the cayenne-tools project.
>
> *<antlib>*
> *  <taskdef name="cgen"
> classname="org.apache.cayenne.tools.CayenneGeneratorTask"/>*
> *  <taskdef name="cdbgen"
> classname="org.apache.cayenne.tools.DbGeneratorTask"/>*
> *  <taskdef name="cdataport"
> classname="org.apache.cayenne.tools.DataPortTask"/>*
> *  <taskdef name="cdbimport"
> classname="org.apache.cayenne.tools.DbImporterTask"/>*
> *</antlib>*
> 2.Will the Gradle native plugin be similar to the Ant classes that we see
> under the cayennetools project?
> 3.Can we find some more information about these tools somewhere?
> 4.Is there a JIRA issue to track this task so that we can pick it up and
> work on it?
>
> Currently we are working on the following
> 1. At this point we have completed the tutorial
> http://cayenne.apache.org/docs/4.0/tutorial/index.html
> 2. We are currently playing with Gradle native plugins.
>
> Thanks,
> Rohit Vaidya
>
> On Thu, Dec 15, 2016 at 12:11 AM, Andrus Adamchik <[hidden email]>
> wrote:
>
>> Hi Rohit,
>>
>> Great! Feel free to ask questions here.
>>
>> The best place to check which configuration properties are supported for
>> each tool is probably the Maven "mojo" classes [1]. Maven plugin docs [2]
>> should also be up-to-date.
>>
>> Andrus
>>
>> [1] https://github.com/apache/cayenne/tree/master/plugins/
>> maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
>> [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
>> including-cayenne-in-project.html#maven-projects
>>
>>> On Dec 14, 2016, at 9:26 PM, Rohit Vaidya <[hidden email]> wrote:
>>>
>>> Hello Andrus,
>>> +1 for the Gradle task. We will explore Gradle Native Plugins.
>>>
>>> Thanks,
>>> Rohit Vaidya
>>>
>>>
>>> On Wed, Dec 14, 2016 at 12:00 AM, buddha <[hidden email]>
>> wrote:
>>>
>>>> Hey Andrus,
>>>>
>>>> I just logged into the jira. We have had a discussion in our java user
>>>> group monthly meeting this Saturday. I never worked with Gradle myself,
>> but
>>>> there are a few who did in JUG. I will look at other tasks in the list
>> you
>>>> have given, and let u know. Or, may be I will learn and take help of
>> some
>>>> of the people in JUG to take up the ones you listed below.
>>>>
>>>> Thanks
>>>> Buddha
>>>>
>>>> On 13/12/16, 11:21 PM, "Andrus Adamchik" <[hidden email]>
>> wrote:
>>>>
>>>>    Buddha (and others who wanted to join the fun) --
>>>>
>>>>    As you see it is taking us a bit of time to get the JavaFX Modeler
>>>> project setup. Though we are getting there. If you feel like digging
>> inside
>>>> other parts of Cayenne in the meantime, I posted a broad TODO list for
>> the
>>>> next release recently [1]. Perhaps you can give us a hand on some of
>> those
>>>> tasks?
>>>>
>>>>    A good candidate (if you work with Gradle at all) may be #10 -
>>>> providing Gradle versions of Cayenne tools:
>>>>
>>>>    * cgen - template-based class generator.
>>>>    * cdbimport - DB to ORM synchronization tool.
>>>>    * cdbgen - ORM to DB generator tool.
>>>>
>>>>    These tools work from the Modeler, and are also integrated into Ant
>>>> and Maven [2]. The Gradle option currently is to call the Ant tasks.
>> We'd
>>>> like to provide "Gradle-native" plugins instead. There are a few options
>>>> for writing those. We lean towards using Java (to isolate us from the
>> whole
>>>> Groovy vs. Kotlin thing going on in the Gradle world).
>>>>
>>>>    Other tasks from my list [1] are #6 and #7. They are isolated and
>>>> mostly well-defined, though will require a bit more discussion and
>> delving
>>>> into Cayenne runtime stack.
>>>>
>>>>    So what do you think?
>>>>
>>>>    Andrus
>>>>
>>>>
>>>>    [1] https://lists.apache.org/thread.html/
>>>> b69fa0eb0457507d5720103a9627252c696b2faec0b71db52762a7c7@%
>>>> 3Cdev.cayenne.apache.org%3E
>>>>    [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
>>>> including-cayenne-in-project.html#maven-projects
>>>>
>>>>
>>>>
>>>>> On Dec 12, 2016, at 11:52 PM, Michael Gentry <[hidden email]>
>>>> wrote:
>>>>>
>>>>> A new Git repository is still on my to-do list.  Been a relatively
>>>> busy
>>>>> time, so it's been bumped below other more important things.
>>>>>
>>>>> mrg
>>>>>
>>>>>
>>>>> On Sat, Dec 10, 2016 at 12:55 PM, Andrus Adamchik <
>>>> [hidden email]>
>>>>> wrote:
>>>>>
>>>>>> I just committed my first experiment with JavaFX and Bootique [1].
>>>> It
>>>>>> enables injection into JavaFX controllers [2] and gives access to
>>>> DI from
>>>>>> the Application class. The implementation is a bit invasive
>>>> (requires
>>>>>> framework superclass of Application), as we can't easily take over
>>>> the
>>>>>> startup sequence, but otherwise works fine. At least in my simple
>>>> example :)
>>>>>>
>>>>>> My total exposure to JavaFX is a total of 2 hours, so I am pretty
>>>> sure I
>>>>>> overlooked other useful things we can do between Bootique and
>>>> JavaFX. But
>>>>>> that's a start. This code will likely become the future
>>>> bootique-javafx
>>>>>> module.
>>>>>>
>>>>>> Mike, were we able to get a new Git repo for the JavaFX modeler?
>>>>>>
>>>>>> Andrus
>>>>>>
>>>>>> [1] https://github.com/andrus/jfxsandbox
>>>>>> [2] https://github.com/andrus/jfxsandbox/blob/master/src/
>>>>>> main/java/com/foo/RootController.java
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Regards,
>>> Rohit Vaidya
>>
>>
>
>


--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
Reply | Threaded
Open this post in threaded view
|

Re: JavaFX and Boutique

buddha
Ari, they are useful…

However, Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks… So just checking if our understanding is right before we begin working on it.

On 24/12/16, 1:21 PM, "Aristedes Maniatis" <[hidden email]> wrote:

    You can easily enough call the ant tasks from gradle, and I've made a wrapper around those ant tasks. But I didn't bother to support the things I didn't need immediately, so it needs to be fleshed out.
   
    https://github.com/ari/cayenne-gradle
   
    Fork or copy and of that you find useful.
   
    Ari
   
   
    On 24/12/16 6:30pm, Rohit Vaidya wrote:
    > Hi Andrus,
    > 1. The cayenne documentation says "Cayenne artifacts are available from
    > Maven Central for use with Maven, Ivy, Gradle or any other dependency
    > management tool" So what is the expected out of this task?
    > We found the following xml in the cayenne-tools project.
    >
    > *<antlib>*
    > *  <taskdef name="cgen"
    > classname="org.apache.cayenne.tools.CayenneGeneratorTask"/>*
    > *  <taskdef name="cdbgen"
    > classname="org.apache.cayenne.tools.DbGeneratorTask"/>*
    > *  <taskdef name="cdataport"
    > classname="org.apache.cayenne.tools.DataPortTask"/>*
    > *  <taskdef name="cdbimport"
    > classname="org.apache.cayenne.tools.DbImporterTask"/>*
    > *</antlib>*
    > 2.Will the Gradle native plugin be similar to the Ant classes that we see
    > under the cayennetools project?
    > 3.Can we find some more information about these tools somewhere?
    > 4.Is there a JIRA issue to track this task so that we can pick it up and
    > work on it?
    >
    > Currently we are working on the following
    > 1. At this point we have completed the tutorial
    > http://cayenne.apache.org/docs/4.0/tutorial/index.html
    > 2. We are currently playing with Gradle native plugins.
    >
    > Thanks,
    > Rohit Vaidya
    >
    > On Thu, Dec 15, 2016 at 12:11 AM, Andrus Adamchik <[hidden email]>
    > wrote:
    >
    >> Hi Rohit,
    >>
    >> Great! Feel free to ask questions here.
    >>
    >> The best place to check which configuration properties are supported for
    >> each tool is probably the Maven "mojo" classes [1]. Maven plugin docs [2]
    >> should also be up-to-date.
    >>
    >> Andrus
    >>
    >> [1] https://github.com/apache/cayenne/tree/master/plugins/
    >> maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
    >> [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
    >> including-cayenne-in-project.html#maven-projects
    >>
    >>> On Dec 14, 2016, at 9:26 PM, Rohit Vaidya <[hidden email]> wrote:
    >>>
    >>> Hello Andrus,
    >>> +1 for the Gradle task. We will explore Gradle Native Plugins.
    >>>
    >>> Thanks,
    >>> Rohit Vaidya
    >>>
    >>>
    >>> On Wed, Dec 14, 2016 at 12:00 AM, buddha <[hidden email]>
    >> wrote:
    >>>
    >>>> Hey Andrus,
    >>>>
    >>>> I just logged into the jira. We have had a discussion in our java user
    >>>> group monthly meeting this Saturday. I never worked with Gradle myself,
    >> but
    >>>> there are a few who did in JUG. I will look at other tasks in the list
    >> you
    >>>> have given, and let u know. Or, may be I will learn and take help of
    >> some
    >>>> of the people in JUG to take up the ones you listed below.
    >>>>
    >>>> Thanks
    >>>> Buddha
    >>>>
    >>>> On 13/12/16, 11:21 PM, "Andrus Adamchik" <[hidden email]>
    >> wrote:
    >>>>
    >>>>    Buddha (and others who wanted to join the fun) --
    >>>>
    >>>>    As you see it is taking us a bit of time to get the JavaFX Modeler
    >>>> project setup. Though we are getting there. If you feel like digging
    >> inside
    >>>> other parts of Cayenne in the meantime, I posted a broad TODO list for
    >> the
    >>>> next release recently [1]. Perhaps you can give us a hand on some of
    >> those
    >>>> tasks?
    >>>>
    >>>>    A good candidate (if you work with Gradle at all) may be #10 -
    >>>> providing Gradle versions of Cayenne tools:
    >>>>
    >>>>    * cgen - template-based class generator.
    >>>>    * cdbimport - DB to ORM synchronization tool.
    >>>>    * cdbgen - ORM to DB generator tool.
    >>>>
    >>>>    These tools work from the Modeler, and are also integrated into Ant
    >>>> and Maven [2]. The Gradle option currently is to call the Ant tasks.
    >> We'd
    >>>> like to provide "Gradle-native" plugins instead. There are a few options
    >>>> for writing those. We lean towards using Java (to isolate us from the
    >> whole
    >>>> Groovy vs. Kotlin thing going on in the Gradle world).
    >>>>
    >>>>    Other tasks from my list [1] are #6 and #7. They are isolated and
    >>>> mostly well-defined, though will require a bit more discussion and
    >> delving
    >>>> into Cayenne runtime stack.
    >>>>
    >>>>    So what do you think?
    >>>>
    >>>>    Andrus
    >>>>
    >>>>
    >>>>    [1] https://lists.apache.org/thread.html/
    >>>> b69fa0eb0457507d5720103a9627252c696b2faec0b71db52762a7c7@%
    >>>> 3Cdev.cayenne.apache.org%3E
    >>>>    [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
    >>>> including-cayenne-in-project.html#maven-projects
    >>>>
    >>>>
    >>>>
    >>>>> On Dec 12, 2016, at 11:52 PM, Michael Gentry <[hidden email]>
    >>>> wrote:
    >>>>>
    >>>>> A new Git repository is still on my to-do list.  Been a relatively
    >>>> busy
    >>>>> time, so it's been bumped below other more important things.
    >>>>>
    >>>>> mrg
    >>>>>
    >>>>>
    >>>>> On Sat, Dec 10, 2016 at 12:55 PM, Andrus Adamchik <
    >>>> [hidden email]>
    >>>>> wrote:
    >>>>>
    >>>>>> I just committed my first experiment with JavaFX and Bootique [1].
    >>>> It
    >>>>>> enables injection into JavaFX controllers [2] and gives access to
    >>>> DI from
    >>>>>> the Application class. The implementation is a bit invasive
    >>>> (requires
    >>>>>> framework superclass of Application), as we can't easily take over
    >>>> the
    >>>>>> startup sequence, but otherwise works fine. At least in my simple
    >>>> example :)
    >>>>>>
    >>>>>> My total exposure to JavaFX is a total of 2 hours, so I am pretty
    >>>> sure I
    >>>>>> overlooked other useful things we can do between Bootique and
    >>>> JavaFX. But
    >>>>>> that's a start. This code will likely become the future
    >>>> bootique-javafx
    >>>>>> module.
    >>>>>>
    >>>>>> Mike, were we able to get a new Git repo for the JavaFX modeler?
    >>>>>>
    >>>>>> Andrus
    >>>>>>
    >>>>>> [1] https://github.com/andrus/jfxsandbox
    >>>>>> [2] https://github.com/andrus/jfxsandbox/blob/master/src/
    >>>>>> main/java/com/foo/RootController.java
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>
    >>>
    >>>
    >>> --
    >>> Regards,
    >>> Rohit Vaidya
    >>
    >>
    >
    >
   
   
    --
    -------------------------->
    Aristedes Maniatis
    GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
   


Reply | Threaded
Open this post in threaded view
|

Re: JavaFX and Boutique

Aristedes Maniatis-2
Sure, it would be more elegant to call the Cayenne API directly rather than through ant.

I added some instructions to the plugin to show how it might be called. I think several things are needed to make this really nice:

1. call the Cayenne API directly without ant
2. clean the whole thing up (it was written in 2012) to ensure it maps to modern gradle practices
3. publish it to the gradle plugin repo
4. add any more features people might want
5. Remove the dependency on a specific version of Cayenne and allow the user to define that in their gradle build somewhere


Ari


On 24/12/16 8:51pm, buddha wrote:

> Ari, they are useful…
>
> However, Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks… So just checking if our understanding is right before we begin working on it.
>
> On 24/12/16, 1:21 PM, "Aristedes Maniatis" <[hidden email]> wrote:
>
>     You can easily enough call the ant tasks from gradle, and I've made a wrapper around those ant tasks. But I didn't bother to support the things I didn't need immediately, so it needs to be fleshed out.
>    
>     https://github.com/ari/cayenne-gradle
>    
>     Fork or copy and of that you find useful.
>    
>     Ari
>    
>    
>     On 24/12/16 6:30pm, Rohit Vaidya wrote:
>     > Hi Andrus,
>     > 1. The cayenne documentation says "Cayenne artifacts are available from
>     > Maven Central for use with Maven, Ivy, Gradle or any other dependency
>     > management tool" So what is the expected out of this task?
>     > We found the following xml in the cayenne-tools project.
>     >
>     > *<antlib>*
>     > *  <taskdef name="cgen"
>     > classname="org.apache.cayenne.tools.CayenneGeneratorTask"/>*
>     > *  <taskdef name="cdbgen"
>     > classname="org.apache.cayenne.tools.DbGeneratorTask"/>*
>     > *  <taskdef name="cdataport"
>     > classname="org.apache.cayenne.tools.DataPortTask"/>*
>     > *  <taskdef name="cdbimport"
>     > classname="org.apache.cayenne.tools.DbImporterTask"/>*
>     > *</antlib>*
>     > 2.Will the Gradle native plugin be similar to the Ant classes that we see
>     > under the cayennetools project?
>     > 3.Can we find some more information about these tools somewhere?
>     > 4.Is there a JIRA issue to track this task so that we can pick it up and
>     > work on it?
>     >
>     > Currently we are working on the following
>     > 1. At this point we have completed the tutorial
>     > http://cayenne.apache.org/docs/4.0/tutorial/index.html
>     > 2. We are currently playing with Gradle native plugins.
>     >
>     > Thanks,
>     > Rohit Vaidya
>     >
>     > On Thu, Dec 15, 2016 at 12:11 AM, Andrus Adamchik <[hidden email]>
>     > wrote:
>     >
>     >> Hi Rohit,
>     >>
>     >> Great! Feel free to ask questions here.
>     >>
>     >> The best place to check which configuration properties are supported for
>     >> each tool is probably the Maven "mojo" classes [1]. Maven plugin docs [2]
>     >> should also be up-to-date.
>     >>
>     >> Andrus
>     >>
>     >> [1] https://github.com/apache/cayenne/tree/master/plugins/
>     >> maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
>     >> [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
>     >> including-cayenne-in-project.html#maven-projects
>     >>
>     >>> On Dec 14, 2016, at 9:26 PM, Rohit Vaidya <[hidden email]> wrote:
>     >>>
>     >>> Hello Andrus,
>     >>> +1 for the Gradle task. We will explore Gradle Native Plugins.
>     >>>
>     >>> Thanks,
>     >>> Rohit Vaidya
>     >>>
>     >>>
>     >>> On Wed, Dec 14, 2016 at 12:00 AM, buddha <[hidden email]>
>     >> wrote:
>     >>>
>     >>>> Hey Andrus,
>     >>>>
>     >>>> I just logged into the jira. We have had a discussion in our java user
>     >>>> group monthly meeting this Saturday. I never worked with Gradle myself,
>     >> but
>     >>>> there are a few who did in JUG. I will look at other tasks in the list
>     >> you
>     >>>> have given, and let u know. Or, may be I will learn and take help of
>     >> some
>     >>>> of the people in JUG to take up the ones you listed below.
>     >>>>
>     >>>> Thanks
>     >>>> Buddha
>     >>>>
>     >>>> On 13/12/16, 11:21 PM, "Andrus Adamchik" <[hidden email]>
>     >> wrote:
>     >>>>
>     >>>>    Buddha (and others who wanted to join the fun) --
>     >>>>
>     >>>>    As you see it is taking us a bit of time to get the JavaFX Modeler
>     >>>> project setup. Though we are getting there. If you feel like digging
>     >> inside
>     >>>> other parts of Cayenne in the meantime, I posted a broad TODO list for
>     >> the
>     >>>> next release recently [1]. Perhaps you can give us a hand on some of
>     >> those
>     >>>> tasks?
>     >>>>
>     >>>>    A good candidate (if you work with Gradle at all) may be #10 -
>     >>>> providing Gradle versions of Cayenne tools:
>     >>>>
>     >>>>    * cgen - template-based class generator.
>     >>>>    * cdbimport - DB to ORM synchronization tool.
>     >>>>    * cdbgen - ORM to DB generator tool.
>     >>>>
>     >>>>    These tools work from the Modeler, and are also integrated into Ant
>     >>>> and Maven [2]. The Gradle option currently is to call the Ant tasks.
>     >> We'd
>     >>>> like to provide "Gradle-native" plugins instead. There are a few options
>     >>>> for writing those. We lean towards using Java (to isolate us from the
>     >> whole
>     >>>> Groovy vs. Kotlin thing going on in the Gradle world).
>     >>>>
>     >>>>    Other tasks from my list [1] are #6 and #7. They are isolated and
>     >>>> mostly well-defined, though will require a bit more discussion and
>     >> delving
>     >>>> into Cayenne runtime stack.
>     >>>>
>     >>>>    So what do you think?
>     >>>>
>     >>>>    Andrus
>     >>>>
>     >>>>
>     >>>>    [1] https://lists.apache.org/thread.html/
>     >>>> b69fa0eb0457507d5720103a9627252c696b2faec0b71db52762a7c7@%
>     >>>> 3Cdev.cayenne.apache.org%3E
>     >>>>    [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
>     >>>> including-cayenne-in-project.html#maven-projects
>     >>>>
>     >>>>
>     >>>>
>     >>>>> On Dec 12, 2016, at 11:52 PM, Michael Gentry <[hidden email]>
>     >>>> wrote:
>     >>>>>
>     >>>>> A new Git repository is still on my to-do list.  Been a relatively
>     >>>> busy
>     >>>>> time, so it's been bumped below other more important things.
>     >>>>>
>     >>>>> mrg
>     >>>>>
>     >>>>>
>     >>>>> On Sat, Dec 10, 2016 at 12:55 PM, Andrus Adamchik <
>     >>>> [hidden email]>
>     >>>>> wrote:
>     >>>>>
>     >>>>>> I just committed my first experiment with JavaFX and Bootique [1].
>     >>>> It
>     >>>>>> enables injection into JavaFX controllers [2] and gives access to
>     >>>> DI from
>     >>>>>> the Application class. The implementation is a bit invasive
>     >>>> (requires
>     >>>>>> framework superclass of Application), as we can't easily take over
>     >>>> the
>     >>>>>> startup sequence, but otherwise works fine. At least in my simple
>     >>>> example :)
>     >>>>>>
>     >>>>>> My total exposure to JavaFX is a total of 2 hours, so I am pretty
>     >>>> sure I
>     >>>>>> overlooked other useful things we can do between Bootique and
>     >>>> JavaFX. But
>     >>>>>> that's a start. This code will likely become the future
>     >>>> bootique-javafx
>     >>>>>> module.
>     >>>>>>
>     >>>>>> Mike, were we able to get a new Git repo for the JavaFX modeler?
>     >>>>>>
>     >>>>>> Andrus
>     >>>>>>
>     >>>>>> [1] https://github.com/andrus/jfxsandbox
>     >>>>>> [2] https://github.com/andrus/jfxsandbox/blob/master/src/
>     >>>>>> main/java/com/foo/RootController.java
>     >>>>
>     >>>>
>     >>>>
>     >>>>
>     >>>>
>     >>>
>     >>>
>     >>> --
>     >>> Regards,
>     >>> Rohit Vaidya
>     >>
>     >>
>     >
>     >
>    
>    
>     --
>     -------------------------->
>     Aristedes Maniatis
>     GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>    
>
>


--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
Reply | Threaded
Open this post in threaded view
|

Re: JavaFX and Boutique

buddha
Cool… thanks.

On 24/12/16, 3:38 PM, "Aristedes Maniatis" <[hidden email]> wrote:

    Sure, it would be more elegant to call the Cayenne API directly rather than through ant.
   
    I added some instructions to the plugin to show how it might be called. I think several things are needed to make this really nice:
   
    1. call the Cayenne API directly without ant
    2. clean the whole thing up (it was written in 2012) to ensure it maps to modern gradle practices
    3. publish it to the gradle plugin repo
    4. add any more features people might want
    5. Remove the dependency on a specific version of Cayenne and allow the user to define that in their gradle build somewhere
   
   
    Ari
   
   
    On 24/12/16 8:51pm, buddha wrote:
    > Ari, they are useful…
    >
    > However, Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks… So just checking if our understanding is right before we begin working on it.
    >
    > On 24/12/16, 1:21 PM, "Aristedes Maniatis" <[hidden email]> wrote:
    >
    >     You can easily enough call the ant tasks from gradle, and I've made a wrapper around those ant tasks. But I didn't bother to support the things I didn't need immediately, so it needs to be fleshed out.
    >    
    >     https://github.com/ari/cayenne-gradle
    >    
    >     Fork or copy and of that you find useful.
    >    
    >     Ari
    >    
    >    
    >     On 24/12/16 6:30pm, Rohit Vaidya wrote:
    >     > Hi Andrus,
    >     > 1. The cayenne documentation says "Cayenne artifacts are available from
    >     > Maven Central for use with Maven, Ivy, Gradle or any other dependency
    >     > management tool" So what is the expected out of this task?
    >     > We found the following xml in the cayenne-tools project.
    >     >
    >     > *<antlib>*
    >     > *  <taskdef name="cgen"
    >     > classname="org.apache.cayenne.tools.CayenneGeneratorTask"/>*
    >     > *  <taskdef name="cdbgen"
    >     > classname="org.apache.cayenne.tools.DbGeneratorTask"/>*
    >     > *  <taskdef name="cdataport"
    >     > classname="org.apache.cayenne.tools.DataPortTask"/>*
    >     > *  <taskdef name="cdbimport"
    >     > classname="org.apache.cayenne.tools.DbImporterTask"/>*
    >     > *</antlib>*
    >     > 2.Will the Gradle native plugin be similar to the Ant classes that we see
    >     > under the cayennetools project?
    >     > 3.Can we find some more information about these tools somewhere?
    >     > 4.Is there a JIRA issue to track this task so that we can pick it up and
    >     > work on it?
    >     >
    >     > Currently we are working on the following
    >     > 1. At this point we have completed the tutorial
    >     > http://cayenne.apache.org/docs/4.0/tutorial/index.html
    >     > 2. We are currently playing with Gradle native plugins.
    >     >
    >     > Thanks,
    >     > Rohit Vaidya
    >     >
    >     > On Thu, Dec 15, 2016 at 12:11 AM, Andrus Adamchik <[hidden email]>
    >     > wrote:
    >     >
    >     >> Hi Rohit,
    >     >>
    >     >> Great! Feel free to ask questions here.
    >     >>
    >     >> The best place to check which configuration properties are supported for
    >     >> each tool is probably the Maven "mojo" classes [1]. Maven plugin docs [2]
    >     >> should also be up-to-date.
    >     >>
    >     >> Andrus
    >     >>
    >     >> [1] https://github.com/apache/cayenne/tree/master/plugins/
    >     >> maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
    >     >> [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
    >     >> including-cayenne-in-project.html#maven-projects
    >     >>
    >     >>> On Dec 14, 2016, at 9:26 PM, Rohit Vaidya <[hidden email]> wrote:
    >     >>>
    >     >>> Hello Andrus,
    >     >>> +1 for the Gradle task. We will explore Gradle Native Plugins.
    >     >>>
    >     >>> Thanks,
    >     >>> Rohit Vaidya
    >     >>>
    >     >>>
    >     >>> On Wed, Dec 14, 2016 at 12:00 AM, buddha <[hidden email]>
    >     >> wrote:
    >     >>>
    >     >>>> Hey Andrus,
    >     >>>>
    >     >>>> I just logged into the jira. We have had a discussion in our java user
    >     >>>> group monthly meeting this Saturday. I never worked with Gradle myself,
    >     >> but
    >     >>>> there are a few who did in JUG. I will look at other tasks in the list
    >     >> you
    >     >>>> have given, and let u know. Or, may be I will learn and take help of
    >     >> some
    >     >>>> of the people in JUG to take up the ones you listed below.
    >     >>>>
    >     >>>> Thanks
    >     >>>> Buddha
    >     >>>>
    >     >>>> On 13/12/16, 11:21 PM, "Andrus Adamchik" <[hidden email]>
    >     >> wrote:
    >     >>>>
    >     >>>>    Buddha (and others who wanted to join the fun) --
    >     >>>>
    >     >>>>    As you see it is taking us a bit of time to get the JavaFX Modeler
    >     >>>> project setup. Though we are getting there. If you feel like digging
    >     >> inside
    >     >>>> other parts of Cayenne in the meantime, I posted a broad TODO list for
    >     >> the
    >     >>>> next release recently [1]. Perhaps you can give us a hand on some of
    >     >> those
    >     >>>> tasks?
    >     >>>>
    >     >>>>    A good candidate (if you work with Gradle at all) may be #10 -
    >     >>>> providing Gradle versions of Cayenne tools:
    >     >>>>
    >     >>>>    * cgen - template-based class generator.
    >     >>>>    * cdbimport - DB to ORM synchronization tool.
    >     >>>>    * cdbgen - ORM to DB generator tool.
    >     >>>>
    >     >>>>    These tools work from the Modeler, and are also integrated into Ant
    >     >>>> and Maven [2]. The Gradle option currently is to call the Ant tasks.
    >     >> We'd
    >     >>>> like to provide "Gradle-native" plugins instead. There are a few options
    >     >>>> for writing those. We lean towards using Java (to isolate us from the
    >     >> whole
    >     >>>> Groovy vs. Kotlin thing going on in the Gradle world).
    >     >>>>
    >     >>>>    Other tasks from my list [1] are #6 and #7. They are isolated and
    >     >>>> mostly well-defined, though will require a bit more discussion and
    >     >> delving
    >     >>>> into Cayenne runtime stack.
    >     >>>>
    >     >>>>    So what do you think?
    >     >>>>
    >     >>>>    Andrus
    >     >>>>
    >     >>>>
    >     >>>>    [1] https://lists.apache.org/thread.html/
    >     >>>> b69fa0eb0457507d5720103a9627252c696b2faec0b71db52762a7c7@%
    >     >>>> 3Cdev.cayenne.apache.org%3E
    >     >>>>    [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
    >     >>>> including-cayenne-in-project.html#maven-projects
    >     >>>>
    >     >>>>
    >     >>>>
    >     >>>>> On Dec 12, 2016, at 11:52 PM, Michael Gentry <[hidden email]>
    >     >>>> wrote:
    >     >>>>>
    >     >>>>> A new Git repository is still on my to-do list.  Been a relatively
    >     >>>> busy
    >     >>>>> time, so it's been bumped below other more important things.
    >     >>>>>
    >     >>>>> mrg
    >     >>>>>
    >     >>>>>
    >     >>>>> On Sat, Dec 10, 2016 at 12:55 PM, Andrus Adamchik <
    >     >>>> [hidden email]>
    >     >>>>> wrote:
    >     >>>>>
    >     >>>>>> I just committed my first experiment with JavaFX and Bootique [1].
    >     >>>> It
    >     >>>>>> enables injection into JavaFX controllers [2] and gives access to
    >     >>>> DI from
    >     >>>>>> the Application class. The implementation is a bit invasive
    >     >>>> (requires
    >     >>>>>> framework superclass of Application), as we can't easily take over
    >     >>>> the
    >     >>>>>> startup sequence, but otherwise works fine. At least in my simple
    >     >>>> example :)
    >     >>>>>>
    >     >>>>>> My total exposure to JavaFX is a total of 2 hours, so I am pretty
    >     >>>> sure I
    >     >>>>>> overlooked other useful things we can do between Bootique and
    >     >>>> JavaFX. But
    >     >>>>>> that's a start. This code will likely become the future
    >     >>>> bootique-javafx
    >     >>>>>> module.
    >     >>>>>>
    >     >>>>>> Mike, were we able to get a new Git repo for the JavaFX modeler?
    >     >>>>>>
    >     >>>>>> Andrus
    >     >>>>>>
    >     >>>>>> [1] https://github.com/andrus/jfxsandbox
    >     >>>>>> [2] https://github.com/andrus/jfxsandbox/blob/master/src/
    >     >>>>>> main/java/com/foo/RootController.java
    >     >>>>
    >     >>>>
    >     >>>>
    >     >>>>
    >     >>>>
    >     >>>
    >     >>>
    >     >>> --
    >     >>> Regards,
    >     >>> Rohit Vaidya
    >     >>
    >     >>
    >     >
    >     >
    >    
    >    
    >     --
    >     -------------------------->
    >     Aristedes Maniatis
    >     GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
    >    
    >
    >
   
   
    --
    -------------------------->
    Aristedes Maniatis
    GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
   


Reply | Threaded
Open this post in threaded view
|

Gradle plugin

Andrus Adamchik
In reply to this post by buddha

> Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks…

That would be my preference. Don't want to depend on Ant tasks. Support for those has been on the decline, and they have some user-facing API peculiarities that I don't want to see propagated to Gradle. So let's try to build native plugins, using Maven Mojos as API prototypes as I suggested earlier [1].

>> 1. The cayenne documentation says "Cayenne artifacts are available from
>> Maven Central for use with Maven, Ivy, Gradle or any other dependency
>> management tool"

My understanding that "canonical" repo for Gradle plugins is this: https://plugins.gradle.org/ So that's where we publish them when we do our next official release.

>> So what is the expected out of this task? We found the following xml in the cayenne-tools project.


Let's ignore the Ant tasks for a moment.

>> 2.Will the Gradle native plugin be similar to the Ant classes that we see
>> under the cayennetools project?

We need matching Gradle plugins mirroring the API/configuration of the corresponding Maven plugins [1]. We do not need "cdataport", but we do need these 3:

* cgen [2]
* cdbimport [3]
* cdbgen [4]

>> 4.Is there a JIRA issue to track this task so that we can pick it up and work on it?


Good idea. I just created 3 Jiras - [2,3,4]

Andrus


[1] https://github.com/apache/cayenne/tree/master/plugins/maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
[2] https://issues.apache.org/jira/browse/CAY-2180
[3] https://issues.apache.org/jira/browse/CAY-2181
[4] https://issues.apache.org/jira/browse/CAY-2182


> On Dec 24, 2016, at 12:51 PM, buddha <[hidden email]> wrote:
>
> Ari, they are useful…
>
> However, Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks… So just checking if our understanding is right before we begin working on it.
>
> On 24/12/16, 1:21 PM, "Aristedes Maniatis" <[hidden email]> wrote:
>
>    You can easily enough call the ant tasks from gradle, and I've made a wrapper around those ant tasks. But I didn't bother to support the things I didn't need immediately, so it needs to be fleshed out.
>
>    https://github.com/ari/cayenne-gradle
>
>    Fork or copy and of that you find useful.
>
>    Ari
>
>
>    On 24/12/16 6:30pm, Rohit Vaidya wrote:
>> Hi Andrus,
>> 1. The cayenne documentation says "Cayenne artifacts are available from
>> Maven Central for use with Maven, Ivy, Gradle or any other dependency
>> management tool" So what is the expected out of this task?
>> We found the following xml in the cayenne-tools project.
>>
>> *<antlib>*
>> *  <taskdef name="cgen"
>> classname="org.apache.cayenne.tools.CayenneGeneratorTask"/>*
>> *  <taskdef name="cdbgen"
>> classname="org.apache.cayenne.tools.DbGeneratorTask"/>*
>> *  <taskdef name="cdataport"
>> classname="org.apache.cayenne.tools.DataPortTask"/>*
>> *  <taskdef name="cdbimport"
>> classname="org.apache.cayenne.tools.DbImporterTask"/>*
>> *</antlib>*
>> 2.Will the Gradle native plugin be similar to the Ant classes that we see
>> under the cayennetools project?
>> 3.Can we find some more information about these tools somewhere?
>> 4.Is there a JIRA issue to track this task so that we can pick it up and
>> work on it?
>>
>> Currently we are working on the following
>> 1. At this point we have completed the tutorial
>> http://cayenne.apache.org/docs/4.0/tutorial/index.html
>> 2. We are currently playing with Gradle native plugins.
>>
>> Thanks,
>> Rohit Vaidya
>>
>> On Thu, Dec 15, 2016 at 12:11 AM, Andrus Adamchik <[hidden email]>
>> wrote:
>>
>>> Hi Rohit,
>>>
>>> Great! Feel free to ask questions here.
>>>
>>> The best place to check which configuration properties are supported for
>>> each tool is probably the Maven "mojo" classes [1]. Maven plugin docs [2]
>>> should also be up-to-date.
>>>
>>> Andrus
>>>
>>> [1] https://github.com/apache/cayenne/tree/master/plugins/
>>> maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
>>> [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
>>> including-cayenne-in-project.html#maven-projects
>>>
>>>> On Dec 14, 2016, at 9:26 PM, Rohit Vaidya <[hidden email]> wrote:
>>>>
>>>> Hello Andrus,
>>>> +1 for the Gradle task. We will explore Gradle Native Plugins.
>>>>
>>>> Thanks,
>>>> Rohit Vaidya
>>>>

Reply | Threaded
Open this post in threaded view
|

Re: Gradle plugin

buddha
Thanks Andrus, for the clarification. Will start on these.

On 24/12/16, 3:53 PM, "Andrus Adamchik" <[hidden email]> wrote:

   
    > Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks…
   
    That would be my preference. Don't want to depend on Ant tasks. Support for those has been on the decline, and they have some user-facing API peculiarities that I don't want to see propagated to Gradle. So let's try to build native plugins, using Maven Mojos as API prototypes as I suggested earlier [1].
   
    >> 1. The cayenne documentation says "Cayenne artifacts are available from
    >> Maven Central for use with Maven, Ivy, Gradle or any other dependency
    >> management tool"
   
    My understanding that "canonical" repo for Gradle plugins is this: https://plugins.gradle.org/ So that's where we publish them when we do our next official release.
   
    >> So what is the expected out of this task? We found the following xml in the cayenne-tools project.
   
   
    Let's ignore the Ant tasks for a moment.
   
    >> 2.Will the Gradle native plugin be similar to the Ant classes that we see
    >> under the cayennetools project?
   
    We need matching Gradle plugins mirroring the API/configuration of the corresponding Maven plugins [1]. We do not need "cdataport", but we do need these 3:
   
    * cgen [2]
    * cdbimport [3]
    * cdbgen [4]
   
    >> 4.Is there a JIRA issue to track this task so that we can pick it up and work on it?
   
   
    Good idea. I just created 3 Jiras - [2,3,4]
   
    Andrus
   
   
    [1] https://github.com/apache/cayenne/tree/master/plugins/maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
    [2] https://issues.apache.org/jira/browse/CAY-2180
    [3] https://issues.apache.org/jira/browse/CAY-2181
    [4] https://issues.apache.org/jira/browse/CAY-2182
   
   
    > On Dec 24, 2016, at 12:51 PM, buddha <[hidden email]> wrote:
    >
    > Ari, they are useful…
    >
    > However, Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks… So just checking if our understanding is right before we begin working on it.
    >
    > On 24/12/16, 1:21 PM, "Aristedes Maniatis" <[hidden email]> wrote:
    >
    >    You can easily enough call the ant tasks from gradle, and I've made a wrapper around those ant tasks. But I didn't bother to support the things I didn't need immediately, so it needs to be fleshed out.
    >
    >    https://github.com/ari/cayenne-gradle
    >
    >    Fork or copy and of that you find useful.
    >
    >    Ari
    >
    >
    >    On 24/12/16 6:30pm, Rohit Vaidya wrote:
    >> Hi Andrus,
    >> 1. The cayenne documentation says "Cayenne artifacts are available from
    >> Maven Central for use with Maven, Ivy, Gradle or any other dependency
    >> management tool" So what is the expected out of this task?
    >> We found the following xml in the cayenne-tools project.
    >>
    >> *<antlib>*
    >> *  <taskdef name="cgen"
    >> classname="org.apache.cayenne.tools.CayenneGeneratorTask"/>*
    >> *  <taskdef name="cdbgen"
    >> classname="org.apache.cayenne.tools.DbGeneratorTask"/>*
    >> *  <taskdef name="cdataport"
    >> classname="org.apache.cayenne.tools.DataPortTask"/>*
    >> *  <taskdef name="cdbimport"
    >> classname="org.apache.cayenne.tools.DbImporterTask"/>*
    >> *</antlib>*
    >> 2.Will the Gradle native plugin be similar to the Ant classes that we see
    >> under the cayennetools project?
    >> 3.Can we find some more information about these tools somewhere?
    >> 4.Is there a JIRA issue to track this task so that we can pick it up and
    >> work on it?
    >>
    >> Currently we are working on the following
    >> 1. At this point we have completed the tutorial
    >> http://cayenne.apache.org/docs/4.0/tutorial/index.html
    >> 2. We are currently playing with Gradle native plugins.
    >>
    >> Thanks,
    >> Rohit Vaidya
    >>
    >> On Thu, Dec 15, 2016 at 12:11 AM, Andrus Adamchik <[hidden email]>
    >> wrote:
    >>
    >>> Hi Rohit,
    >>>
    >>> Great! Feel free to ask questions here.
    >>>
    >>> The best place to check which configuration properties are supported for
    >>> each tool is probably the Maven "mojo" classes [1]. Maven plugin docs [2]
    >>> should also be up-to-date.
    >>>
    >>> Andrus
    >>>
    >>> [1] https://github.com/apache/cayenne/tree/master/plugins/
    >>> maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
    >>> [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
    >>> including-cayenne-in-project.html#maven-projects
    >>>
    >>>> On Dec 14, 2016, at 9:26 PM, Rohit Vaidya <[hidden email]> wrote:
    >>>>
    >>>> Hello Andrus,
    >>>> +1 for the Gradle task. We will explore Gradle Native Plugins.
    >>>>
    >>>> Thanks,
    >>>> Rohit Vaidya
    >>>>
   
   


Reply | Threaded
Open this post in threaded view
|

Re: Gradle plugin

Nikita Timofeev
Hi all,

We are approaching 4.0.BETA pretty fast and I wanted to check
is there any news about Gradle plugin, as it could be a really nice
final touch for the release.

Currently we have some resources and made small research on
how to integrate Gradle plugin correctly into Cayenne's maven
build routines and ready to either integrate it or proceed and
implement it.

So it will be really great if there is some code ready that we can
just grab and carry on, and even if it's not final you can still make
a pull request so we can continue.

Thanks,
Nikita.

On Sat, Dec 24, 2016 at 12:27 PM, buddha <[hidden email]> wrote:

> Thanks Andrus, for the clarification. Will start on these.
>
> On 24/12/16, 3:53 PM, "Andrus Adamchik" <[hidden email]> wrote:
>
>
>     > Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks…
>
>     That would be my preference. Don't want to depend on Ant tasks. Support for those has been on the decline, and they have some user-facing API peculiarities that I don't want to see propagated to Gradle. So let's try to build native plugins, using Maven Mojos as API prototypes as I suggested earlier [1].
>
>     >> 1. The cayenne documentation says "Cayenne artifacts are available from
>     >> Maven Central for use with Maven, Ivy, Gradle or any other dependency
>     >> management tool"
>
>     My understanding that "canonical" repo for Gradle plugins is this: https://plugins.gradle.org/ So that's where we publish them when we do our next official release.
>
>     >> So what is the expected out of this task? We found the following xml in the cayenne-tools project.
>
>
>     Let's ignore the Ant tasks for a moment.
>
>     >> 2.Will the Gradle native plugin be similar to the Ant classes that we see
>     >> under the cayennetools project?
>
>     We need matching Gradle plugins mirroring the API/configuration of the corresponding Maven plugins [1]. We do not need "cdataport", but we do need these 3:
>
>     * cgen [2]
>     * cdbimport [3]
>     * cdbgen [4]
>
>     >> 4.Is there a JIRA issue to track this task so that we can pick it up and work on it?
>
>
>     Good idea. I just created 3 Jiras - [2,3,4]
>
>     Andrus
>
>
>     [1] https://github.com/apache/cayenne/tree/master/plugins/maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
>     [2] https://issues.apache.org/jira/browse/CAY-2180
>     [3] https://issues.apache.org/jira/browse/CAY-2181
>     [4] https://issues.apache.org/jira/browse/CAY-2182
>
>
>     > On Dec 24, 2016, at 12:51 PM, buddha <[hidden email]> wrote:
>     >
>     > Ari, they are useful…
>     >
>     > However, Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks… So just checking if our understanding is right before we begin working on it.
>     >
>     > On 24/12/16, 1:21 PM, "Aristedes Maniatis" <[hidden email]> wrote:
>     >
>     >    You can easily enough call the ant tasks from gradle, and I've made a wrapper around those ant tasks. But I didn't bother to support the things I didn't need immediately, so it needs to be fleshed out.
>     >
>     >    https://github.com/ari/cayenne-gradle
>     >
>     >    Fork or copy and of that you find useful.
>     >
>     >    Ari
>     >
>     >
>     >    On 24/12/16 6:30pm, Rohit Vaidya wrote:
>     >> Hi Andrus,
>     >> 1. The cayenne documentation says "Cayenne artifacts are available from
>     >> Maven Central for use with Maven, Ivy, Gradle or any other dependency
>     >> management tool" So what is the expected out of this task?
>     >> We found the following xml in the cayenne-tools project.
>     >>
>     >> *<antlib>*
>     >> *  <taskdef name="cgen"
>     >> classname="org.apache.cayenne.tools.CayenneGeneratorTask"/>*
>     >> *  <taskdef name="cdbgen"
>     >> classname="org.apache.cayenne.tools.DbGeneratorTask"/>*
>     >> *  <taskdef name="cdataport"
>     >> classname="org.apache.cayenne.tools.DataPortTask"/>*
>     >> *  <taskdef name="cdbimport"
>     >> classname="org.apache.cayenne.tools.DbImporterTask"/>*
>     >> *</antlib>*
>     >> 2.Will the Gradle native plugin be similar to the Ant classes that we see
>     >> under the cayennetools project?
>     >> 3.Can we find some more information about these tools somewhere?
>     >> 4.Is there a JIRA issue to track this task so that we can pick it up and
>     >> work on it?
>     >>
>     >> Currently we are working on the following
>     >> 1. At this point we have completed the tutorial
>     >> http://cayenne.apache.org/docs/4.0/tutorial/index.html
>     >> 2. We are currently playing with Gradle native plugins.
>     >>
>     >> Thanks,
>     >> Rohit Vaidya
>     >>
>     >> On Thu, Dec 15, 2016 at 12:11 AM, Andrus Adamchik <[hidden email]>
>     >> wrote:
>     >>
>     >>> Hi Rohit,
>     >>>
>     >>> Great! Feel free to ask questions here.
>     >>>
>     >>> The best place to check which configuration properties are supported for
>     >>> each tool is probably the Maven "mojo" classes [1]. Maven plugin docs [2]
>     >>> should also be up-to-date.
>     >>>
>     >>> Andrus
>     >>>
>     >>> [1] https://github.com/apache/cayenne/tree/master/plugins/
>     >>> maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
>     >>> [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
>     >>> including-cayenne-in-project.html#maven-projects
>     >>>
>     >>>> On Dec 14, 2016, at 9:26 PM, Rohit Vaidya <[hidden email]> wrote:
>     >>>>
>     >>>> Hello Andrus,
>     >>>> +1 for the Gradle task. We will explore Gradle Native Plugins.
>     >>>>
>     >>>> Thanks,
>     >>>> Rohit Vaidya
>     >>>>
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Gradle plugin

buddha
Hello Nikita,

Sorry for delay. The extent of my work is so minimal, I just created a new maven module and a skelton class for gradle plugin. No logic has been implemented yet. I can certainly push if you want to use those but I would suggest you create fresh as my build isn’t passing yet.

Thanks
Buddha

On 04/05/17, 2:00 PM, "Nikita Timofeev" <[hidden email]> wrote:

    Hi all,
   
    We are approaching 4.0.BETA pretty fast and I wanted to check
    is there any news about Gradle plugin, as it could be a really nice
    final touch for the release.
   
    Currently we have some resources and made small research on
    how to integrate Gradle plugin correctly into Cayenne's maven
    build routines and ready to either integrate it or proceed and
    implement it.
   
    So it will be really great if there is some code ready that we can
    just grab and carry on, and even if it's not final you can still make
    a pull request so we can continue.
   
    Thanks,
    Nikita.
   
    On Sat, Dec 24, 2016 at 12:27 PM, buddha <[hidden email]> wrote:
    > Thanks Andrus, for the clarification. Will start on these.
    >
    > On 24/12/16, 3:53 PM, "Andrus Adamchik" <[hidden email]> wrote:
    >
    >
    >     > Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks…
    >
    >     That would be my preference. Don't want to depend on Ant tasks. Support for those has been on the decline, and they have some user-facing API peculiarities that I don't want to see propagated to Gradle. So let's try to build native plugins, using Maven Mojos as API prototypes as I suggested earlier [1].
    >
    >     >> 1. The cayenne documentation says "Cayenne artifacts are available from
    >     >> Maven Central for use with Maven, Ivy, Gradle or any other dependency
    >     >> management tool"
    >
    >     My understanding that "canonical" repo for Gradle plugins is this: https://plugins.gradle.org/ So that's where we publish them when we do our next official release.
    >
    >     >> So what is the expected out of this task? We found the following xml in the cayenne-tools project.
    >
    >
    >     Let's ignore the Ant tasks for a moment.
    >
    >     >> 2.Will the Gradle native plugin be similar to the Ant classes that we see
    >     >> under the cayennetools project?
    >
    >     We need matching Gradle plugins mirroring the API/configuration of the corresponding Maven plugins [1]. We do not need "cdataport", but we do need these 3:
    >
    >     * cgen [2]
    >     * cdbimport [3]
    >     * cdbgen [4]
    >
    >     >> 4.Is there a JIRA issue to track this task so that we can pick it up and work on it?
    >
    >
    >     Good idea. I just created 3 Jiras - [2,3,4]
    >
    >     Andrus
    >
    >
    >     [1] https://github.com/apache/cayenne/tree/master/plugins/maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
    >     [2] https://issues.apache.org/jira/browse/CAY-2180
    >     [3] https://issues.apache.org/jira/browse/CAY-2181
    >     [4] https://issues.apache.org/jira/browse/CAY-2182
    >
    >
    >     > On Dec 24, 2016, at 12:51 PM, buddha <[hidden email]> wrote:
    >     >
    >     > Ari, they are useful…
    >     >
    >     > However, Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks… So just checking if our understanding is right before we begin working on it.
    >     >
    >     > On 24/12/16, 1:21 PM, "Aristedes Maniatis" <[hidden email]> wrote:
    >     >
    >     >    You can easily enough call the ant tasks from gradle, and I've made a wrapper around those ant tasks. But I didn't bother to support the things I didn't need immediately, so it needs to be fleshed out.
    >     >
    >     >    https://github.com/ari/cayenne-gradle
    >     >
    >     >    Fork or copy and of that you find useful.
    >     >
    >     >    Ari
    >     >
    >     >
    >     >    On 24/12/16 6:30pm, Rohit Vaidya wrote:
    >     >> Hi Andrus,
    >     >> 1. The cayenne documentation says "Cayenne artifacts are available from
    >     >> Maven Central for use with Maven, Ivy, Gradle or any other dependency
    >     >> management tool" So what is the expected out of this task?
    >     >> We found the following xml in the cayenne-tools project.
    >     >>
    >     >> *<antlib>*
    >     >> *  <taskdef name="cgen"
    >     >> classname="org.apache.cayenne.tools.CayenneGeneratorTask"/>*
    >     >> *  <taskdef name="cdbgen"
    >     >> classname="org.apache.cayenne.tools.DbGeneratorTask"/>*
    >     >> *  <taskdef name="cdataport"
    >     >> classname="org.apache.cayenne.tools.DataPortTask"/>*
    >     >> *  <taskdef name="cdbimport"
    >     >> classname="org.apache.cayenne.tools.DbImporterTask"/>*
    >     >> *</antlib>*
    >     >> 2.Will the Gradle native plugin be similar to the Ant classes that we see
    >     >> under the cayennetools project?
    >     >> 3.Can we find some more information about these tools somewhere?
    >     >> 4.Is there a JIRA issue to track this task so that we can pick it up and
    >     >> work on it?
    >     >>
    >     >> Currently we are working on the following
    >     >> 1. At this point we have completed the tutorial
    >     >> http://cayenne.apache.org/docs/4.0/tutorial/index.html
    >     >> 2. We are currently playing with Gradle native plugins.
    >     >>
    >     >> Thanks,
    >     >> Rohit Vaidya
    >     >>
    >     >> On Thu, Dec 15, 2016 at 12:11 AM, Andrus Adamchik <[hidden email]>
    >     >> wrote:
    >     >>
    >     >>> Hi Rohit,
    >     >>>
    >     >>> Great! Feel free to ask questions here.
    >     >>>
    >     >>> The best place to check which configuration properties are supported for
    >     >>> each tool is probably the Maven "mojo" classes [1]. Maven plugin docs [2]
    >     >>> should also be up-to-date.
    >     >>>
    >     >>> Andrus
    >     >>>
    >     >>> [1] https://github.com/apache/cayenne/tree/master/plugins/
    >     >>> maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
    >     >>> [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
    >     >>> including-cayenne-in-project.html#maven-projects
    >     >>>
    >     >>>> On Dec 14, 2016, at 9:26 PM, Rohit Vaidya <[hidden email]> wrote:
    >     >>>>
    >     >>>> Hello Andrus,
    >     >>>> +1 for the Gradle task. We will explore Gradle Native Plugins.
    >     >>>>
    >     >>>> Thanks,
    >     >>>> Rohit Vaidya
    >     >>>>
    >
    >
    >
   


Reply | Threaded
Open this post in threaded view
|

Re: Gradle plugin

Nikita Timofeev
Hello Buddha,

Thank you for update!
We'll go with a clean start then.

On Thu, May 11, 2017 at 9:04 AM, buddha <[hidden email]> wrote:

> Hello Nikita,
>
> Sorry for delay. The extent of my work is so minimal, I just created a new maven module and a skelton class for gradle plugin. No logic has been implemented yet. I can certainly push if you want to use those but I would suggest you create fresh as my build isn’t passing yet.
>
> Thanks
> Buddha
>
> On 04/05/17, 2:00 PM, "Nikita Timofeev" <[hidden email]> wrote:
>
>     Hi all,
>
>     We are approaching 4.0.BETA pretty fast and I wanted to check
>     is there any news about Gradle plugin, as it could be a really nice
>     final touch for the release.
>
>     Currently we have some resources and made small research on
>     how to integrate Gradle plugin correctly into Cayenne's maven
>     build routines and ready to either integrate it or proceed and
>     implement it.
>
>     So it will be really great if there is some code ready that we can
>     just grab and carry on, and even if it's not final you can still make
>     a pull request so we can continue.
>
>     Thanks,
>     Nikita.
>
>     On Sat, Dec 24, 2016 at 12:27 PM, buddha <[hidden email]> wrote:
>     > Thanks Andrus, for the clarification. Will start on these.
>     >
>     > On 24/12/16, 3:53 PM, "Andrus Adamchik" <[hidden email]> wrote:
>     >
>     >
>     >     > Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks…
>     >
>     >     That would be my preference. Don't want to depend on Ant tasks. Support for those has been on the decline, and they have some user-facing API peculiarities that I don't want to see propagated to Gradle. So let's try to build native plugins, using Maven Mojos as API prototypes as I suggested earlier [1].
>     >
>     >     >> 1. The cayenne documentation says "Cayenne artifacts are available from
>     >     >> Maven Central for use with Maven, Ivy, Gradle or any other dependency
>     >     >> management tool"
>     >
>     >     My understanding that "canonical" repo for Gradle plugins is this: https://plugins.gradle.org/ So that's where we publish them when we do our next official release.
>     >
>     >     >> So what is the expected out of this task? We found the following xml in the cayenne-tools project.
>     >
>     >
>     >     Let's ignore the Ant tasks for a moment.
>     >
>     >     >> 2.Will the Gradle native plugin be similar to the Ant classes that we see
>     >     >> under the cayennetools project?
>     >
>     >     We need matching Gradle plugins mirroring the API/configuration of the corresponding Maven plugins [1]. We do not need "cdataport", but we do need these 3:
>     >
>     >     * cgen [2]
>     >     * cdbimport [3]
>     >     * cdbgen [4]
>     >
>     >     >> 4.Is there a JIRA issue to track this task so that we can pick it up and work on it?
>     >
>     >
>     >     Good idea. I just created 3 Jiras - [2,3,4]
>     >
>     >     Andrus
>     >
>     >
>     >     [1] https://github.com/apache/cayenne/tree/master/plugins/maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
>     >     [2] https://issues.apache.org/jira/browse/CAY-2180
>     >     [3] https://issues.apache.org/jira/browse/CAY-2181
>     >     [4] https://issues.apache.org/jira/browse/CAY-2182
>     >
>     >
>     >     > On Dec 24, 2016, at 12:51 PM, buddha <[hidden email]> wrote:
>     >     >
>     >     > Ari, they are useful…
>     >     >
>     >     > However, Our understanding is that we will build native gradle plugins that don’t rely on Ant tasks… So just checking if our understanding is right before we begin working on it.
>     >     >
>     >     > On 24/12/16, 1:21 PM, "Aristedes Maniatis" <[hidden email]> wrote:
>     >     >
>     >     >    You can easily enough call the ant tasks from gradle, and I've made a wrapper around those ant tasks. But I didn't bother to support the things I didn't need immediately, so it needs to be fleshed out.
>     >     >
>     >     >    https://github.com/ari/cayenne-gradle
>     >     >
>     >     >    Fork or copy and of that you find useful.
>     >     >
>     >     >    Ari
>     >     >
>     >     >
>     >     >    On 24/12/16 6:30pm, Rohit Vaidya wrote:
>     >     >> Hi Andrus,
>     >     >> 1. The cayenne documentation says "Cayenne artifacts are available from
>     >     >> Maven Central for use with Maven, Ivy, Gradle or any other dependency
>     >     >> management tool" So what is the expected out of this task?
>     >     >> We found the following xml in the cayenne-tools project.
>     >     >>
>     >     >> *<antlib>*
>     >     >> *  <taskdef name="cgen"
>     >     >> classname="org.apache.cayenne.tools.CayenneGeneratorTask"/>*
>     >     >> *  <taskdef name="cdbgen"
>     >     >> classname="org.apache.cayenne.tools.DbGeneratorTask"/>*
>     >     >> *  <taskdef name="cdataport"
>     >     >> classname="org.apache.cayenne.tools.DataPortTask"/>*
>     >     >> *  <taskdef name="cdbimport"
>     >     >> classname="org.apache.cayenne.tools.DbImporterTask"/>*
>     >     >> *</antlib>*
>     >     >> 2.Will the Gradle native plugin be similar to the Ant classes that we see
>     >     >> under the cayennetools project?
>     >     >> 3.Can we find some more information about these tools somewhere?
>     >     >> 4.Is there a JIRA issue to track this task so that we can pick it up and
>     >     >> work on it?
>     >     >>
>     >     >> Currently we are working on the following
>     >     >> 1. At this point we have completed the tutorial
>     >     >> http://cayenne.apache.org/docs/4.0/tutorial/index.html
>     >     >> 2. We are currently playing with Gradle native plugins.
>     >     >>
>     >     >> Thanks,
>     >     >> Rohit Vaidya
>     >     >>
>     >     >> On Thu, Dec 15, 2016 at 12:11 AM, Andrus Adamchik <[hidden email]>
>     >     >> wrote:
>     >     >>
>     >     >>> Hi Rohit,
>     >     >>>
>     >     >>> Great! Feel free to ask questions here.
>     >     >>>
>     >     >>> The best place to check which configuration properties are supported for
>     >     >>> each tool is probably the Maven "mojo" classes [1]. Maven plugin docs [2]
>     >     >>> should also be up-to-date.
>     >     >>>
>     >     >>> Andrus
>     >     >>>
>     >     >>> [1] https://github.com/apache/cayenne/tree/master/plugins/
>     >     >>> maven-cayenne-plugin/src/main/java/org/apache/cayenne/tools
>     >     >>> [2] http://cayenne.apache.org/docs/4.0/cayenne-guide/
>     >     >>> including-cayenne-in-project.html#maven-projects
>     >     >>>
>     >     >>>> On Dec 14, 2016, at 9:26 PM, Rohit Vaidya <[hidden email]> wrote:
>     >     >>>>
>     >     >>>> Hello Andrus,
>     >     >>>> +1 for the Gradle task. We will explore Gradle Native Plugins.
>     >     >>>>
>     >     >>>> Thanks,
>     >     >>>> Rohit Vaidya
>     >     >>>>
>     >
>     >
>     >
>
>
>



--
Best regards,
Nikita Timofeev