Hi, I did subscribed to the mailing list already.
So, as I understand I should wait for the JavaEE cluster gets integrated. And try to roll back the Grails changes. And then we can see where to go from there. Regards, Oleg On Thu, Jan 3, 2019 at 3:08 PM Sven Reimers <[email protected]> wrote: > Hi, > > there is some kind of dependency between grails and the java ee cluster... > > For a first step just reenabling should be good enough, but I think we may > need a better decoupling between grails and ee stuff. > > I assume there may be more frameworks benefiting from this.. > > -Sven > > Am Do., 3. Jan. 2019, 09:10 hat Geertjan Wielenga > <[email protected]> geschrieben: > >> First, join the mailing list so that I do not have to keep approving your >> mails, i.e., your mails will come in automatically: >> >> https://netbeans.apache.org/community/mailing-lists.html >> >> Then do a fork of Apache NetBeans GitHub and then revert this and then >> provide a pull request: >> >> >> https://github.com/apache/incubator-netbeans/pull/904/commits/1a5259cfcba106430d95f039480578ff9ba41e34 >> >> But it seems like there's a dependency between Grails and the enterprise >> cluster -- Sven Reimers, can you remember why this is the case? Probably >> because Grails applications can be deployed to a server and until the >> enterprise cluster is re-included, there's no server support? >> >> Gj >> >> >> On Thu, Jan 3, 2019 at 1:51 AM Oleg Minukhin <[email protected]> wrote: >> >> > Hi, >> > >> > I could start with reintegrating Grails as it was before. That is what >> I >> > am interesting in initially, as I am working on an old Grails project >> from >> > time to time. >> > >> > Regards, >> > Oleg >> > >> > On Wed, Jan 2, 2019 at 5:21 PM Geertjan Wielenga < >> > [email protected]> wrote: >> > >> >> Let's start with a definition of the requirements. >> >> >> >> Gj >> >> >> >> >> >> On Wed, Jan 2, 2019 at 11:35 PM Oleg Minukhin <[email protected]> >> wrote: >> >> >> >>> Hi Geertjan, >> >>> >> >>> I am interesting to help with some Groovy / Grails integration, at >> least >> >>> to the degree it was before. How would I start? >> >>> >> >>> Regards, >> >>> Oleg >> >>> >> >>> >> >>> On Sat, Dec 29, 2018, 11:00 AM Geertjan Wielenga < >> >>> [email protected] wrote: >> >>> >> >>>> That makes sense. It was probably right to disable the old Grails >> >>>> support that we had. >> >>>> >> >>>> If someone can provide a 'hello world' Grails/Micronaut sample, we >> can >> >>>> integrate that and, if needed, build support around it. Maybe we can >> reuse >> >>>> some of the old Grails support, but probably not. >> >>>> >> >>>> Gj >> >>>> >> >>>> On Sat, Dec 29, 2018 at 5:54 PM Rik Scarborough <[email protected]> >> >>>> wrote: >> >>>> >> >>>>> The Grails team has made a statement that they intend on moving >> Grails >> >>>>> into >> >>>>> the Micronaut structure. >> >>>>> >> >>>>> ~Rik >> >>>>> Believe in good >> >>>>> >> >>>>> On Sat, Dec 29, 2018, 10:51 AM Geertjan Wielenga >> >>>>> <[email protected] wrote: >> >>>>> >> >>>>> > Hi all, especially Jasen and Oleg, who recently commented on >> Grails >> >>>>> support >> >>>>> > in Apache NetBeans, >> >>>>> > >> >>>>> > Now that we have released Apache NetBeans 10, and are looking to >> >>>>> Apache >> >>>>> > NetBeans 11, which will included the enterprise cluster, i.e., >> >>>>> including >> >>>>> > support for application servers, which is relevant for Grails >> >>>>> deployment, >> >>>>> > maybe we could look at reintegrating Grails features into Apache >> >>>>> NetBeans >> >>>>> > 11? >> >>>>> > >> >>>>> > Here's the related PR where we disabled Grails support (because of >> >>>>> lack of >> >>>>> > enterprise cluster integration and because the version of Grails >> >>>>> supported >> >>>>> > was outdated): >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> >> https://github.com/apache/incubator-netbeans/pull/904/commits/1a5259cfcba106430d95f039480578ff9ba41e34 >> >>>>> > >> >>>>> > Or should we not focus on Grails at all, or Micronaut instead? >> Would >> >>>>> be >> >>>>> > good to define what we'd like to achieve with Grails together and >> >>>>> come up >> >>>>> > with a plan. >> >>>>> > >> >>>>> > Thanks, >> >>>>> > >> >>>>> > Gj >> >>>>> > >> >>>>> >> >>>> >> >
