You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by arsi <ar...@chello.sk> on 2017/10/24 12:02:41 UTC

Android support analysis

Hi,

I contacted Radim Kubacki author of the NBANDROID project.
According to his words, it has nomotivationto continue development. 
(last commit is from 2015)
But he has nothing against that the community will continue to develop 
the project and that it could part of Apache netbeans.
NBANDROID is under Apache 2 License.


It's an extension of Gradle Support plugin.
And there will be a lot of work to do:

  * Rewrite to new Gradle plugin extension API (GradleProjectExtension2)
  * Remove old Ant support
  *
    Google gradually moving tools from SDK to Android studio. So we have
    to write AVD Manager, SDK Manager and many other things.
  * New visual Layout Editor

I started cleaning the code, I made a maven nb module  and I've already 
fixed some things:

  * Dependency analysis + Code assistance
  * Run + Debug
  * Android Emulator

I suggest continuing as a plugin, and when the project is stabilized, 
you can start thinking about adding it to the NB core

Arsi




AW: Android support analysis

Posted by Christian Lenz <ch...@gmx.net>.
I think first we should treat it like a plugin as it is atm, as you already said. It can moved to github first and we can create tickets and PRs etc. 

Gesendet von Mail für Windows 10

Von: Christian Lenz
Gesendet: Dienstag, 24. Oktober 2017 14:17
An: dev@netbeans.incubator.apache.org
Betreff: AW: Android support analysis

Here is the source: https://twitter.com/jgauravgupta/status/743659073317396480 It is based on JFludion I think.

Gesendet von Mail für Windows 10

Von: arsi
Gesendet: Dienstag, 24. Oktober 2017 14:03
An: dev@netbeans.incubator.apache.org
Betreff: Android support analysis

Hi,

I contacted Radim Kubacki author of the NBANDROID project.
According to his words, it has nomotivationto continue development. 
(last commit is from 2015)
But he has nothing against that the community will continue to develop 
the project and that it could part of Apache netbeans.
NBANDROID is under Apache 2 License.


It's an extension of Gradle Support plugin.
And there will be a lot of work to do:

  * Rewrite to new Gradle plugin extension API (GradleProjectExtension2)
  * Remove old Ant support
  *
    Google gradually moving tools from SDK to Android studio. So we have
    to write AVD Manager, SDK Manager and many other things.
  * New visual Layout Editor

I started cleaning the code, I made a maven nb module  and I've already 
fixed some things:

  * Dependency analysis + Code assistance
  * Run + Debug
  * Android Emulator

I suggest continuing as a plugin, and when the project is stabilized, 
you can start thinking about adding it to the NB core

Arsi






AW: Android support analysis

Posted by Christian Lenz <ch...@gmx.net>.
Here is the source: https://twitter.com/jgauravgupta/status/743659073317396480 It is based on JFludion I think.

Gesendet von Mail für Windows 10

Von: arsi
Gesendet: Dienstag, 24. Oktober 2017 14:03
An: dev@netbeans.incubator.apache.org
Betreff: Android support analysis

Hi,

I contacted Radim Kubacki author of the NBANDROID project.
According to his words, it has nomotivationto continue development. 
(last commit is from 2015)
But he has nothing against that the community will continue to develop 
the project and that it could part of Apache netbeans.
NBANDROID is under Apache 2 License.


It's an extension of Gradle Support plugin.
And there will be a lot of work to do:

  * Rewrite to new Gradle plugin extension API (GradleProjectExtension2)
  * Remove old Ant support
  *
    Google gradually moving tools from SDK to Android studio. So we have
    to write AVD Manager, SDK Manager and many other things.
  * New visual Layout Editor

I started cleaning the code, I made a maven nb module  and I've already 
fixed some things:

  * Dependency analysis + Code assistance
  * Run + Debug
  * Android Emulator

I suggest continuing as a plugin, and when the project is stabilized, 
you can start thinking about adding it to the NB core

Arsi





AW: Android support analysis

Posted by Christian Lenz <ch...@gmx.net>.
Wow, thats cool 😊

There is a Long discussion with gaurap gupta, founder of the Jeddict plugin former as JPA modeler: https://twitter.com/jgauravgupta/status/743659073317396480. He already started a Android modeler, maybe we can extends it?

Gesendet von Mail für Windows 10

Von: arsi
Gesendet: Dienstag, 24. Oktober 2017 14:03
An: dev@netbeans.incubator.apache.org
Betreff: Android support analysis

Hi,

I contacted Radim Kubacki author of the NBANDROID project.
According to his words, it has nomotivationto continue development. 
(last commit is from 2015)
But he has nothing against that the community will continue to develop 
the project and that it could part of Apache netbeans.
NBANDROID is under Apache 2 License.


It's an extension of Gradle Support plugin.
And there will be a lot of work to do:

  * Rewrite to new Gradle plugin extension API (GradleProjectExtension2)
  * Remove old Ant support
  *
    Google gradually moving tools from SDK to Android studio. So we have
    to write AVD Manager, SDK Manager and many other things.
  * New visual Layout Editor

I started cleaning the code, I made a maven nb module  and I've already 
fixed some things:

  * Dependency analysis + Code assistance
  * Run + Debug
  * Android Emulator

I suggest continuing as a plugin, and when the project is stabilized, 
you can start thinking about adding it to the NB core

Arsi





Re: Android support analysis

Posted by arsi <ar...@chello.sk>.
Hi,

I made a repository on Github: https://github.com/NBANDROIDTEAM/NBANDROID-V2

License reports:

https://github.com/NBANDROIDTEAM/NBANDROID-V2/wiki/Third-Party-Licenses
https://github.com/NBANDROIDTEAM/NBANDROID-V2/wiki/Third-Party-Sources

Any help is welcome!

Arsi

Re: Android support analysis

Posted by arsi <ar...@chello.sk>.
Hi,

After end of the first phase, I'll put it back under the Ant.

Arsi



------------------------------------------------------------------------

*From:* Geertjan Wielenga
*Sent:* Tuesday, October 24, 2017 4:44PM
*To:* Dev
*Subject:* Re: Android support analysis


Sure, though be aware that stabilizing and cleaning up can be done at
Apache too.

On the other hand, as long as the code is based on Maven, it can't be
integrated into Apache NetBeans, since it is built on Ant.

Developing it in a separate GitHub repo until you decide that others can
collaborate with you in the context of having it integrated into Apache
NetBeans, is perfectly fine.

Gj

On Tue, Oct 24, 2017 at 4:26 PM, arsi <ar...@chello.sk> wrote:

> Hi,
>
> Radim wrote that he does not want to solve any administration..
> I can send you my communication with Radim, but it is Czech and Slovak..
>
> I made one maven module,because it will often need to change versions of
> android dependencies.
> And it needs to be cleaned. (Old Ant Android support)
>
> Please wait with the branch until the end of this year,it really needs to
> be stabilized and cleaned up..
>
> Arsi
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Geertjan Wielenga
> *Sent:* Tuesday, October 24, 2017 3:40PM
>
> *To:* Dev
> *Subject:* Re: Android support analysis
>
>
> A problem is that, while Apache NetBeans is built on Ant, the sources you
> have provided build via Maven.
>
> Not sure what the right approach should be. Maybe the source structure
> should be in Ant, if it's going to be part of Apache NetBeans?
>
> (I don't see NetBeans moving to Maven very soon.)
>
> Gj
>
> On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
> OK, I have created an 'android' branch:
>> https://github.com/apache/incubator-netbeans/branches
>>
>> Are you sure we're able to simply take the content of that tar.gz and put
>> it into the android branch?
>>
>> I.e., these files are (or can be) licensed to Apache?
>>
>> Gj
>>
>>
>> On Tue, Oct 24, 2017 at 3:27 PM, arsi <ar...@chello.sk> wrote:
>>
>> Hi,
>>> OKwe can move it there..
>>> but I do not know how to do it..
>>>
>>> The sources are here: http://server.arsi.sk/Gradle-A
>>> ndroid-support.tar.gz
>>>
>>>
>>>
>>> Arsi
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Geertjan Wielenga
>>> *Sent:* Tuesday, October 24, 2017 2:50PM
>>>
>>> *To:* Dev
>>> *Subject:* Re: Android support analysis
>>>
>>>
>>> Great. Note that if you want to collaborate with others, regardless of
>>> how
>>> stable it is right now, etc, the Apache Way of doing things is to
>>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
>>> outside Apache, but in Apache itself. I.e., the way would be to create a
>>> branch off of the main Apache NetBeans repo and put the code there and
>>> work
>>> on it there -- that is, if you want to collaborate with others on
>>> something
>>> that will be part of Apache NetBeans at some stage.
>>>
>>> Gj
>>>
>>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:
>>>
>>> Hi,
>>>
>>>> I think it should be a separate repository.
>>>> I started under NB81, where Radim ended. As I wrote it should first be
>>>> stabilized under NB 81/82 as plugin.
>>>>
>>>> And after all my life I work with hg, git kills me ;)
>>>>
>>>>
>>>>
>>>> Arsi
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------
>>>> ------------
>>>>
>>>> *From:* Geertjan Wielenga
>>>> *Sent:* Tuesday, October 24, 2017 2:15PM
>>>> *To:* Dev
>>>> *Subject:* Re: Android support analysis
>>>>
>>>>
>>>>
>>>> Excellent news!
>>>>
>>>> Maybe you could consider making an android branch of Apache NetBeans,
>>>> just
>>>> like these:
>>>>
>>>> https://github.com/apache/incubator-netbeans/branches
>>>>
>>>> So that others can collaborate with you on your work?
>>>>
>>>> I.e., this would be a new feature branch.
>>>>
>>>> Gj
>>>>
>>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I contacted Radim Kubacki author of the NBANDROID project.
>>>>> According to his words, it has nomotivationto continue development.
>>>>> (last
>>>>> commit is from 2015)
>>>>> But he has nothing against that the community will continue to develop
>>>>> the
>>>>> project and that it could part of Apache netbeans.
>>>>> NBANDROID is under Apache 2 License.
>>>>>
>>>>>
>>>>> It's an extension of Gradle Support plugin.
>>>>> And there will be a lot of work to do:
>>>>>
>>>>>      * Rewrite to new Gradle plugin extension API
>>>>> (GradleProjectExtension2)
>>>>>      * Remove old Ant support
>>>>>      *
>>>>>        Google gradually moving tools from SDK to Android studio. So we
>>>>> have
>>>>>        to write AVD Manager, SDK Manager and many other things.
>>>>>      * New visual Layout Editor
>>>>>
>>>>> I started cleaning the code, I made a maven nb module  and I've already
>>>>> fixed some things:
>>>>>
>>>>>      * Dependency analysis + Code assistance
>>>>>      * Run + Debug
>>>>>      * Android Emulator
>>>>>
>>>>> I suggest continuing as a plugin, and when the project is stabilized,
>>>>> you
>>>>> can start thinking about adding it to the NB core
>>>>>
>>>>> Arsi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>







Re: Android support analysis

Posted by Geertjan Wielenga <ge...@googlemail.com>.
Sure, though be aware that stabilizing and cleaning up can be done at
Apache too.

On the other hand, as long as the code is based on Maven, it can't be
integrated into Apache NetBeans, since it is built on Ant.

Developing it in a separate GitHub repo until you decide that others can
collaborate with you in the context of having it integrated into Apache
NetBeans, is perfectly fine.

Gj

On Tue, Oct 24, 2017 at 4:26 PM, arsi <ar...@chello.sk> wrote:

> Hi,
>
> Radim wrote that he does not want to solve any administration..
> I can send you my communication with Radim, but it is Czech and Slovak..
>
> I made one maven module,because it will often need to change versions of
> android dependencies.
> And it needs to be cleaned. (Old Ant Android support)
>
> Please wait with the branch until the end of this year,it really needs to
> be stabilized and cleaned up..
>
> Arsi
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Geertjan Wielenga
> *Sent:* Tuesday, October 24, 2017 3:40PM
>
> *To:* Dev
> *Subject:* Re: Android support analysis
>
>
> A problem is that, while Apache NetBeans is built on Ant, the sources you
> have provided build via Maven.
>
> Not sure what the right approach should be. Maybe the source structure
> should be in Ant, if it's going to be part of Apache NetBeans?
>
> (I don't see NetBeans moving to Maven very soon.)
>
> Gj
>
> On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
> OK, I have created an 'android' branch:
>>
>> https://github.com/apache/incubator-netbeans/branches
>>
>> Are you sure we're able to simply take the content of that tar.gz and put
>> it into the android branch?
>>
>> I.e., these files are (or can be) licensed to Apache?
>>
>> Gj
>>
>>
>> On Tue, Oct 24, 2017 at 3:27 PM, arsi <ar...@chello.sk> wrote:
>>
>> Hi,
>>>
>>> OKwe can move it there..
>>> but I do not know how to do it..
>>>
>>> The sources are here: http://server.arsi.sk/Gradle-A
>>> ndroid-support.tar.gz
>>>
>>>
>>>
>>> Arsi
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Geertjan Wielenga
>>> *Sent:* Tuesday, October 24, 2017 2:50PM
>>>
>>> *To:* Dev
>>> *Subject:* Re: Android support analysis
>>>
>>>
>>> Great. Note that if you want to collaborate with others, regardless of
>>> how
>>> stable it is right now, etc, the Apache Way of doing things is to
>>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
>>> outside Apache, but in Apache itself. I.e., the way would be to create a
>>> branch off of the main Apache NetBeans repo and put the code there and
>>> work
>>> on it there -- that is, if you want to collaborate with others on
>>> something
>>> that will be part of Apache NetBeans at some stage.
>>>
>>> Gj
>>>
>>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:
>>>
>>> Hi,
>>>
>>>> I think it should be a separate repository.
>>>> I started under NB81, where Radim ended. As I wrote it should first be
>>>> stabilized under NB 81/82 as plugin.
>>>>
>>>> And after all my life I work with hg, git kills me ;)
>>>>
>>>>
>>>>
>>>> Arsi
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------
>>>> ------------
>>>>
>>>> *From:* Geertjan Wielenga
>>>> *Sent:* Tuesday, October 24, 2017 2:15PM
>>>> *To:* Dev
>>>> *Subject:* Re: Android support analysis
>>>>
>>>>
>>>>
>>>> Excellent news!
>>>>
>>>> Maybe you could consider making an android branch of Apache NetBeans,
>>>> just
>>>> like these:
>>>>
>>>> https://github.com/apache/incubator-netbeans/branches
>>>>
>>>> So that others can collaborate with you on your work?
>>>>
>>>> I.e., this would be a new feature branch.
>>>>
>>>> Gj
>>>>
>>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I contacted Radim Kubacki author of the NBANDROID project.
>>>>> According to his words, it has nomotivationto continue development.
>>>>> (last
>>>>> commit is from 2015)
>>>>> But he has nothing against that the community will continue to develop
>>>>> the
>>>>> project and that it could part of Apache netbeans.
>>>>> NBANDROID is under Apache 2 License.
>>>>>
>>>>>
>>>>> It's an extension of Gradle Support plugin.
>>>>> And there will be a lot of work to do:
>>>>>
>>>>>     * Rewrite to new Gradle plugin extension API
>>>>> (GradleProjectExtension2)
>>>>>     * Remove old Ant support
>>>>>     *
>>>>>       Google gradually moving tools from SDK to Android studio. So we
>>>>> have
>>>>>       to write AVD Manager, SDK Manager and many other things.
>>>>>     * New visual Layout Editor
>>>>>
>>>>> I started cleaning the code, I made a maven nb module  and I've already
>>>>> fixed some things:
>>>>>
>>>>>     * Dependency analysis + Code assistance
>>>>>     * Run + Debug
>>>>>     * Android Emulator
>>>>>
>>>>> I suggest continuing as a plugin, and when the project is stabilized,
>>>>> you
>>>>> can start thinking about adding it to the NB core
>>>>>
>>>>> Arsi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>>>
>
>

Re: Android support analysis

Posted by Geertjan Wielenga <ge...@googlemail.com>.
Right, good point.

Gj

On Tue, Oct 24, 2017 at 4:50 PM, arsi <ar...@chello.sk> wrote:

> Hi,
>
> And one more thing. First, we need to integrate the Gradle support plugin
> from Attila Kelemen.
> NBANDROID is extension of Gradle support plugin.
>
> Arsi
>
>
> ------------------------------------------------------------------------
>
> *From:* Arsi
> *Sent:* Tuesday, October 24, 2017 4:26PM
>
> *To:* Dev
> *Subject:* Re: Android support analysis
>
>
> Hi,
>
> Radim wrote that he does not want to solve any administration..
> I can send you my communication with Radim, but it is Czech and Slovak..
>
> I made one maven module,because it will often need to change versions of
> android dependencies.
> And it needs to be cleaned. (Old Ant Android support)
>
> Please wait with the branch until the end of this year,it really needs to
> be stabilized and cleaned up..
>
> Arsi
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Geertjan Wielenga
> *Sent:* Tuesday, October 24, 2017 3:40PM
> *To:* Dev
> *Subject:* Re: Android support analysis
>
>
> A problem is that, while Apache NetBeans is built on Ant, the sources you
> have provided build via Maven.
>
> Not sure what the right approach should be. Maybe the source structure
> should be in Ant, if it's going to be part of Apache NetBeans?
>
> (I don't see NetBeans moving to Maven very soon.)
>
> Gj
>
> On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
> OK, I have created an 'android' branch:
>>
>> https://github.com/apache/incubator-netbeans/branches
>>
>> Are you sure we're able to simply take the content of that tar.gz and put
>> it into the android branch?
>>
>> I.e., these files are (or can be) licensed to Apache?
>>
>> Gj
>>
>>
>> On Tue, Oct 24, 2017 at 3:27 PM, arsi <ar...@chello.sk> wrote:
>>
>> Hi,
>>>
>>> OKwe can move it there..
>>> but I do not know how to do it..
>>>
>>> The sources are here: http://server.arsi.sk/Gradle-A
>>> ndroid-support.tar.gz
>>>
>>>
>>>
>>> Arsi
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Geertjan Wielenga
>>> *Sent:* Tuesday, October 24, 2017 2:50PM
>>>
>>> *To:* Dev
>>> *Subject:* Re: Android support analysis
>>>
>>>
>>> Great. Note that if you want to collaborate with others, regardless of
>>> how
>>> stable it is right now, etc, the Apache Way of doing things is to
>>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
>>> outside Apache, but in Apache itself. I.e., the way would be to create a
>>> branch off of the main Apache NetBeans repo and put the code there and
>>> work
>>> on it there -- that is, if you want to collaborate with others on
>>> something
>>> that will be part of Apache NetBeans at some stage.
>>>
>>> Gj
>>>
>>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:
>>>
>>> Hi,
>>>
>>>> I think it should be a separate repository.
>>>> I started under NB81, where Radim ended. As I wrote it should first be
>>>> stabilized under NB 81/82 as plugin.
>>>>
>>>> And after all my life I work with hg, git kills me ;)
>>>>
>>>>
>>>>
>>>> Arsi
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> *From:* Geertjan Wielenga
>>>> *Sent:* Tuesday, October 24, 2017 2:15PM
>>>> *To:* Dev
>>>> *Subject:* Re: Android support analysis
>>>>
>>>>
>>>>
>>>> Excellent news!
>>>>
>>>> Maybe you could consider making an android branch of Apache NetBeans,
>>>> just
>>>> like these:
>>>>
>>>> https://github.com/apache/incubator-netbeans/branches
>>>>
>>>> So that others can collaborate with you on your work?
>>>>
>>>> I.e., this would be a new feature branch.
>>>>
>>>> Gj
>>>>
>>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I contacted Radim Kubacki author of the NBANDROID project.
>>>>> According to his words, it has nomotivationto continue development.
>>>>> (last
>>>>> commit is from 2015)
>>>>> But he has nothing against that the community will continue to develop
>>>>> the
>>>>> project and that it could part of Apache netbeans.
>>>>> NBANDROID is under Apache 2 License.
>>>>>
>>>>>
>>>>> It's an extension of Gradle Support plugin.
>>>>> And there will be a lot of work to do:
>>>>>
>>>>>     * Rewrite to new Gradle plugin extension API
>>>>> (GradleProjectExtension2)
>>>>>     * Remove old Ant support
>>>>>     *
>>>>>       Google gradually moving tools from SDK to Android studio. So we
>>>>> have
>>>>>       to write AVD Manager, SDK Manager and many other things.
>>>>>     * New visual Layout Editor
>>>>>
>>>>> I started cleaning the code, I made a maven nb module  and I've already
>>>>> fixed some things:
>>>>>
>>>>>     * Dependency analysis + Code assistance
>>>>>     * Run + Debug
>>>>>     * Android Emulator
>>>>>
>>>>> I suggest continuing as a plugin, and when the project is stabilized,
>>>>> you
>>>>> can start thinking about adding it to the NB core
>>>>>
>>>>> Arsi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
>
>
>
>

Re: Android support analysis

Posted by arsi <ar...@chello.sk>.
Hi,

And one more thing. First, we need to integrate the Gradle support 
plugin from Attila Kelemen.
NBANDROID is extension of Gradle support plugin.

Arsi


------------------------------------------------------------------------

*From:* Arsi
*Sent:* Tuesday, October 24, 2017 4:26PM
*To:* Dev
*Subject:* Re: Android support analysis


Hi,

Radim wrote that he does not want to solve any administration..
I can send you my communication with Radim, but it is Czech and Slovak..

I made one maven module,because it will often need to change versions of 
android dependencies.
And it needs to be cleaned. (Old Ant Android support)

Please wait with the branch until the end of this year,it really needs 
to be stabilized and cleaned up..

Arsi








------------------------------------------------------------------------

*From:* Geertjan Wielenga
*Sent:* Tuesday, October 24, 2017 3:40PM
*To:* Dev
*Subject:* Re: Android support analysis


A problem is that, while Apache NetBeans is built on Ant, the sources you
have provided build via Maven.

Not sure what the right approach should be. Maybe the source structure
should be in Ant, if it's going to be part of Apache NetBeans?

(I don't see NetBeans moving to Maven very soon.)

Gj

On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:

> OK, I have created an 'android' branch:
>
> https://github.com/apache/incubator-netbeans/branches
>
> Are you sure we're able to simply take the content of that tar.gz and put
> it into the android branch?
>
> I.e., these files are (or can be) licensed to Apache?
>
> Gj
>
>
> On Tue, Oct 24, 2017 at 3:27 PM, arsi <ar...@chello.sk> wrote:
>
>> Hi,
>>
>> OKwe can move it there..
>> but I do not know how to do it..
>>
>> The sources are here: 
>> http://server.arsi.sk/Gradle-Android-support.tar.gz
>>
>>
>>
>> Arsi
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Geertjan Wielenga
>> *Sent:* Tuesday, October 24, 2017 2:50PM
>>
>> *To:* Dev
>> *Subject:* Re: Android support analysis
>>
>>
>> Great. Note that if you want to collaborate with others, regardless 
>> of how
>> stable it is right now, etc, the Apache Way of doing things is to
>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
>> outside Apache, but in Apache itself. I.e., the way would be to create a
>> branch off of the main Apache NetBeans repo and put the code there and
>> work
>> on it there -- that is, if you want to collaborate with others on
>> something
>> that will be part of Apache NetBeans at some stage.
>>
>> Gj
>>
>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:
>>
>> Hi,
>>> I think it should be a separate repository.
>>> I started under NB81, where Radim ended. As I wrote it should first be
>>> stabilized under NB 81/82 as plugin.
>>>
>>> And after all my life I work with hg, git kills me ;)
>>>
>>>
>>>
>>> Arsi
>>>
>>>
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> *From:* Geertjan Wielenga
>>> *Sent:* Tuesday, October 24, 2017 2:15PM
>>> *To:* Dev
>>> *Subject:* Re: Android support analysis
>>>
>>>
>>>
>>> Excellent news!
>>>
>>> Maybe you could consider making an android branch of Apache NetBeans,
>>> just
>>> like these:
>>>
>>> https://github.com/apache/incubator-netbeans/branches
>>>
>>> So that others can collaborate with you on your work?
>>>
>>> I.e., this would be a new feature branch.
>>>
>>> Gj
>>>
>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
>>>
>>> Hi,
>>>
>>>> I contacted Radim Kubacki author of the NBANDROID project.
>>>> According to his words, it has nomotivationto continue development.
>>>> (last
>>>> commit is from 2015)
>>>> But he has nothing against that the community will continue to develop
>>>> the
>>>> project and that it could part of Apache netbeans.
>>>> NBANDROID is under Apache 2 License.
>>>>
>>>>
>>>> It's an extension of Gradle Support plugin.
>>>> And there will be a lot of work to do:
>>>>
>>>>     * Rewrite to new Gradle plugin extension API
>>>> (GradleProjectExtension2)
>>>>     * Remove old Ant support
>>>>     *
>>>>       Google gradually moving tools from SDK to Android studio. So we
>>>> have
>>>>       to write AVD Manager, SDK Manager and many other things.
>>>>     * New visual Layout Editor
>>>>
>>>> I started cleaning the code, I made a maven nb module  and I've 
>>>> already
>>>> fixed some things:
>>>>
>>>>     * Dependency analysis + Code assistance
>>>>     * Run + Debug
>>>>     * Android Emulator
>>>>
>>>> I suggest continuing as a plugin, and when the project is stabilized,
>>>> you
>>>> can start thinking about adding it to the NB core
>>>>
>>>> Arsi
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>
>>









Re: Android support analysis

Posted by arsi <ar...@chello.sk>.
Hi,

Radim wrote that he does not want to solve any administration..
I can send you my communication with Radim, but it is Czech and Slovak..

I made one maven module,because it will often need to change versions of 
android dependencies.
And it needs to be cleaned. (Old Ant Android support)

Please wait with the branch until the end of this year,it really needs 
to be stabilized and cleaned up..

Arsi








------------------------------------------------------------------------

*From:* Geertjan Wielenga
*Sent:* Tuesday, October 24, 2017 3:40PM
*To:* Dev
*Subject:* Re: Android support analysis


A problem is that, while Apache NetBeans is built on Ant, the sources you
have provided build via Maven.

Not sure what the right approach should be. Maybe the source structure
should be in Ant, if it's going to be part of Apache NetBeans?

(I don't see NetBeans moving to Maven very soon.)

Gj

On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:

> OK, I have created an 'android' branch:
>
> https://github.com/apache/incubator-netbeans/branches
>
> Are you sure we're able to simply take the content of that tar.gz and put
> it into the android branch?
>
> I.e., these files are (or can be) licensed to Apache?
>
> Gj
>
>
> On Tue, Oct 24, 2017 at 3:27 PM, arsi <ar...@chello.sk> wrote:
>
>> Hi,
>>
>> OKwe can move it there..
>> but I do not know how to do it..
>>
>> The sources are here: http://server.arsi.sk/Gradle-Android-support.tar.gz
>>
>>
>>
>> Arsi
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Geertjan Wielenga
>> *Sent:* Tuesday, October 24, 2017 2:50PM
>>
>> *To:* Dev
>> *Subject:* Re: Android support analysis
>>
>>
>> Great. Note that if you want to collaborate with others, regardless of how
>> stable it is right now, etc, the Apache Way of doing things is to
>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
>> outside Apache, but in Apache itself. I.e., the way would be to create a
>> branch off of the main Apache NetBeans repo and put the code there and
>> work
>> on it there -- that is, if you want to collaborate with others on
>> something
>> that will be part of Apache NetBeans at some stage.
>>
>> Gj
>>
>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:
>>
>> Hi,
>>> I think it should be a separate repository.
>>> I started under NB81, where Radim ended. As I wrote it should first be
>>> stabilized under NB 81/82 as plugin.
>>>
>>> And after all my life I work with hg, git kills me ;)
>>>
>>>
>>>
>>> Arsi
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Geertjan Wielenga
>>> *Sent:* Tuesday, October 24, 2017 2:15PM
>>> *To:* Dev
>>> *Subject:* Re: Android support analysis
>>>
>>>
>>>
>>> Excellent news!
>>>
>>> Maybe you could consider making an android branch of Apache NetBeans,
>>> just
>>> like these:
>>>
>>> https://github.com/apache/incubator-netbeans/branches
>>>
>>> So that others can collaborate with you on your work?
>>>
>>> I.e., this would be a new feature branch.
>>>
>>> Gj
>>>
>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
>>>
>>> Hi,
>>>
>>>> I contacted Radim Kubacki author of the NBANDROID project.
>>>> According to his words, it has nomotivationto continue development.
>>>> (last
>>>> commit is from 2015)
>>>> But he has nothing against that the community will continue to develop
>>>> the
>>>> project and that it could part of Apache netbeans.
>>>> NBANDROID is under Apache 2 License.
>>>>
>>>>
>>>> It's an extension of Gradle Support plugin.
>>>> And there will be a lot of work to do:
>>>>
>>>>     * Rewrite to new Gradle plugin extension API
>>>> (GradleProjectExtension2)
>>>>     * Remove old Ant support
>>>>     *
>>>>       Google gradually moving tools from SDK to Android studio. So we
>>>> have
>>>>       to write AVD Manager, SDK Manager and many other things.
>>>>     * New visual Layout Editor
>>>>
>>>> I started cleaning the code, I made a maven nb module  and I've already
>>>> fixed some things:
>>>>
>>>>     * Dependency analysis + Code assistance
>>>>     * Run + Debug
>>>>     * Android Emulator
>>>>
>>>> I suggest continuing as a plugin, and when the project is stabilized,
>>>> you
>>>> can start thinking about adding it to the NB core
>>>>
>>>> Arsi
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>
>>



AW: Android support analysis

Posted by Christian Lenz <ch...@gmx.net>.
Ok, thx.

Gesendet von Mail für Windows 10

Von: Geertjan Wielenga
Gesendet: Dienstag, 24. Oktober 2017 16:20
An: dev@netbeans.incubator.apache.org
Betreff: Re: Android support analysis

Yup.

In the case of Android, it would be really cool to have it directly inside
NetBeans, at some point. Initial development elsewhere is fine until then,
of course.

Gj

On Tuesday, October 24, 2017, Christian Lenz <ch...@gmx.net> wrote:

> But we can work together on the 3rd-party-plugin anyway. Of Course, if the
> plan is still having it right inside NetBeans core from the beginning ok,
> but I think this was done with Twig and Git before it went to the NetBeans
> repo after a specific period. NBTS, could be part of NetBeans too one day.
> But for now it is good as it is, to separate it from the core.
>
> Thx for the clarification here.
>
> Regards
>
>
> Chris
>
> Von: Geertjan Wielenga
> Gesendet: Dienstag, 24. Oktober 2017 15:58
> An: dev@netbeans.incubator.apache.org <javascript:;>
> Betreff: Re: Android support analysis
>
> You're absolutely right, Chris.
>
> However, the problem comes in if many of us will want to work together on
> the Android support, i.e., if we'll want to collaborate on this feature,
> and if we want it to be part of Apache NetBeans itself. That's when it will
> be applicable that we'll have a branch, etc, for working on this together.
>
> Hope that clarifies,
>
> Gj
>
>
> On Tue, Oct 24, 2017 at 3:56 PM, Christian Lenz <christian.lenz@gmx.net
> <javascript:;>>
> wrote:
>
> > What is the Problem of having a 3rd-party-plugin, which is not yet inside
> > of the NetBeans core, but has licensed as Apache 2? No one can test the
> > state of the plugin, until you clone the whole source of NetBeans, build
> it
> > and try the plugin inside of it? Since when we are against
> > 3rd-party-plugins? I have a lot and maybe one day, they can be part of
> > NetBeans, but not until we have a better release strategy, which faster
> > release cycles etc.
> >
> > Only my 2 cents here, it would be best to have it as a separate repo
> > outside of Apache NetBeans, but licensed with Apache 2.0, There is
> nothing
> > wrong with it, isn’t it?
> >
> >
> > Regards
> >
> > Chris
> >
> > Gesendet von Mail für Windows 10
> >
> > Von: Geertjan Wielenga
> > Gesendet: Dienstag, 24. Oktober 2017 15:46
> > An: dev@netbeans.incubator.apache.org <javascript:;>
> > Betreff: Re: Android support analysis
> >
> > And I think it would be best if Radim Kubacki himself would commit those
> > sources to the Android branch of Apache NetBeans, since he is the author
> of
> > that code.
> >
> > Gj
> >
> > On Tue, Oct 24, 2017 at 3:40 PM, Geertjan Wielenga <
> > geertjan.wielenga@googlemail.com <javascript:;>> wrote:
> >
> > > A problem is that, while Apache NetBeans is built on Ant, the sources
> you
> > > have provided build via Maven.
> > >
> > > Not sure what the right approach should be. Maybe the source structure
> > > should be in Ant, if it's going to be part of Apache NetBeans?
> > >
> > > (I don't see NetBeans moving to Maven very soon.)
> > >
> > > Gj
> > >
> > > On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
> > > geertjan.wielenga@googlemail.com <javascript:;>> wrote:
> > >
> > >> OK, I have created an 'android' branch:
> > >>
> > >> https://github.com/apache/incubator-netbeans/branches
> > >>
> > >> Are you sure we're able to simply take the content of that tar.gz and
> > put
> > >> it into the android branch?
> > >>
> > >> I.e., these files are (or can be) licensed to Apache?
> > >>
> > >> Gj
> > >>
> > >>
> > >> On Tue, Oct 24, 2017 at 3:27 PM, arsi <arsi@chello.sk <javascript:;>>
> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> OKwe can move it there..
> > >>> but I do not know how to do it..
> > >>>
> > >>> The sources are here: http://server.arsi.sk/Gradle-A
> > >>> ndroid-support.tar.gz
> > >>>
> > >>>
> > >>>
> > >>> Arsi
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> ------------------------------------------------------------
> > ------------
> > >>>
> > >>> *From:* Geertjan Wielenga
> > >>> *Sent:* Tuesday, October 24, 2017 2:50PM
> > >>>
> > >>> *To:* Dev
> > >>> *Subject:* Re: Android support analysis
> > >>>
> > >>>
> > >>> Great. Note that if you want to collaborate with others, regardless
> of
> > >>> how
> > >>> stable it is right now, etc, the Apache Way of doing things is to
> > >>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
> > >>> outside Apache, but in Apache itself. I.e., the way would be to
> create
> > a
> > >>> branch off of the main Apache NetBeans repo and put the code there
> and
> > >>> work
> > >>> on it there -- that is, if you want to collaborate with others on
> > >>> something
> > >>> that will be part of Apache NetBeans at some stage.
> > >>>
> > >>> Gj
> > >>>
> > >>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <arsi@chello.sk <javascript:;>>
> wrote:
> > >>>
> > >>> Hi,
> > >>>>
> > >>>> I think it should be a separate repository.
> > >>>> I started under NB81, where Radim ended. As I wrote it should first
> be
> > >>>> stabilized under NB 81/82 as plugin.
> > >>>>
> > >>>> And after all my life I work with hg, git kills me ;)
> > >>>>
> > >>>>
> > >>>>
> > >>>> Arsi
> > >>>>
> > >>>>
> > >>>>
> > >>>> ------------------------------------------------------------
> > >>>> ------------
> > >>>>
> > >>>> *From:* Geertjan Wielenga
> > >>>> *Sent:* Tuesday, October 24, 2017 2:15PM
> > >>>> *To:* Dev
> > >>>> *Subject:* Re: Android support analysis
> > >>>>
> > >>>>
> > >>>>
> > >>>> Excellent news!
> > >>>>
> > >>>> Maybe you could consider making an android branch of Apache
> NetBeans,
> > >>>> just
> > >>>> like these:
> > >>>>
> > >>>> https://github.com/apache/incubator-netbeans/branches
> > >>>>
> > >>>> So that others can collaborate with you on your work?
> > >>>>
> > >>>> I.e., this would be a new feature branch.
> > >>>>
> > >>>> Gj
> > >>>>
> > >>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <arsi@chello.sk
> <javascript:;>> wrote:
> > >>>>
> > >>>> Hi,
> > >>>>
> > >>>>> I contacted Radim Kubacki author of the NBANDROID project.
> > >>>>> According to his words, it has nomotivationto continue development.
> > >>>>> (last
> > >>>>> commit is from 2015)
> > >>>>> But he has nothing against that the community will continue to
> > develop
> > >>>>> the
> > >>>>> project and that it could part of Apache netbeans.
> > >>>>> NBANDROID is under Apache 2 License.
> > >>>>>
> > >>>>>
> > >>>>> It's an extension of Gradle Support plugin.
> > >>>>> And there will be a lot of work to do:
> > >>>>>
> > >>>>>    * Rewrite to new Gradle plugin extension API
> > >>>>> (GradleProjectExtension2)
> > >>>>>    * Remove old Ant support
> > >>>>>    *
> > >>>>>      Google gradually moving tools from SDK to Android studio. So
> we
> > >>>>> have
> > >>>>>      to write AVD Manager, SDK Manager and many other things.
> > >>>>>    * New visual Layout Editor
> > >>>>>
> > >>>>> I started cleaning the code, I made a maven nb module  and I've
> > already
> > >>>>> fixed some things:
> > >>>>>
> > >>>>>    * Dependency analysis + Code assistance
> > >>>>>    * Run + Debug
> > >>>>>    * Android Emulator
> > >>>>>
> > >>>>> I suggest continuing as a plugin, and when the project is
> stabilized,
> > >>>>> you
> > >>>>> can start thinking about adding it to the NB core
> > >>>>>
> > >>>>> Arsi
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >
> >
> >
>
>


Re: Android support analysis

Posted by Geertjan Wielenga <ge...@googlemail.com>.
Yup.

In the case of Android, it would be really cool to have it directly inside
NetBeans, at some point. Initial development elsewhere is fine until then,
of course.

Gj

On Tuesday, October 24, 2017, Christian Lenz <ch...@gmx.net> wrote:

> But we can work together on the 3rd-party-plugin anyway. Of Course, if the
> plan is still having it right inside NetBeans core from the beginning ok,
> but I think this was done with Twig and Git before it went to the NetBeans
> repo after a specific period. NBTS, could be part of NetBeans too one day.
> But for now it is good as it is, to separate it from the core.
>
> Thx for the clarification here.
>
> Regards
>
>
> Chris
>
> Von: Geertjan Wielenga
> Gesendet: Dienstag, 24. Oktober 2017 15:58
> An: dev@netbeans.incubator.apache.org <javascript:;>
> Betreff: Re: Android support analysis
>
> You're absolutely right, Chris.
>
> However, the problem comes in if many of us will want to work together on
> the Android support, i.e., if we'll want to collaborate on this feature,
> and if we want it to be part of Apache NetBeans itself. That's when it will
> be applicable that we'll have a branch, etc, for working on this together.
>
> Hope that clarifies,
>
> Gj
>
>
> On Tue, Oct 24, 2017 at 3:56 PM, Christian Lenz <christian.lenz@gmx.net
> <javascript:;>>
> wrote:
>
> > What is the Problem of having a 3rd-party-plugin, which is not yet inside
> > of the NetBeans core, but has licensed as Apache 2? No one can test the
> > state of the plugin, until you clone the whole source of NetBeans, build
> it
> > and try the plugin inside of it? Since when we are against
> > 3rd-party-plugins? I have a lot and maybe one day, they can be part of
> > NetBeans, but not until we have a better release strategy, which faster
> > release cycles etc.
> >
> > Only my 2 cents here, it would be best to have it as a separate repo
> > outside of Apache NetBeans, but licensed with Apache 2.0, There is
> nothing
> > wrong with it, isn’t it?
> >
> >
> > Regards
> >
> > Chris
> >
> > Gesendet von Mail für Windows 10
> >
> > Von: Geertjan Wielenga
> > Gesendet: Dienstag, 24. Oktober 2017 15:46
> > An: dev@netbeans.incubator.apache.org <javascript:;>
> > Betreff: Re: Android support analysis
> >
> > And I think it would be best if Radim Kubacki himself would commit those
> > sources to the Android branch of Apache NetBeans, since he is the author
> of
> > that code.
> >
> > Gj
> >
> > On Tue, Oct 24, 2017 at 3:40 PM, Geertjan Wielenga <
> > geertjan.wielenga@googlemail.com <javascript:;>> wrote:
> >
> > > A problem is that, while Apache NetBeans is built on Ant, the sources
> you
> > > have provided build via Maven.
> > >
> > > Not sure what the right approach should be. Maybe the source structure
> > > should be in Ant, if it's going to be part of Apache NetBeans?
> > >
> > > (I don't see NetBeans moving to Maven very soon.)
> > >
> > > Gj
> > >
> > > On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
> > > geertjan.wielenga@googlemail.com <javascript:;>> wrote:
> > >
> > >> OK, I have created an 'android' branch:
> > >>
> > >> https://github.com/apache/incubator-netbeans/branches
> > >>
> > >> Are you sure we're able to simply take the content of that tar.gz and
> > put
> > >> it into the android branch?
> > >>
> > >> I.e., these files are (or can be) licensed to Apache?
> > >>
> > >> Gj
> > >>
> > >>
> > >> On Tue, Oct 24, 2017 at 3:27 PM, arsi <arsi@chello.sk <javascript:;>>
> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> OKwe can move it there..
> > >>> but I do not know how to do it..
> > >>>
> > >>> The sources are here: http://server.arsi.sk/Gradle-A
> > >>> ndroid-support.tar.gz
> > >>>
> > >>>
> > >>>
> > >>> Arsi
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> ------------------------------------------------------------
> > ------------
> > >>>
> > >>> *From:* Geertjan Wielenga
> > >>> *Sent:* Tuesday, October 24, 2017 2:50PM
> > >>>
> > >>> *To:* Dev
> > >>> *Subject:* Re: Android support analysis
> > >>>
> > >>>
> > >>> Great. Note that if you want to collaborate with others, regardless
> of
> > >>> how
> > >>> stable it is right now, etc, the Apache Way of doing things is to
> > >>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
> > >>> outside Apache, but in Apache itself. I.e., the way would be to
> create
> > a
> > >>> branch off of the main Apache NetBeans repo and put the code there
> and
> > >>> work
> > >>> on it there -- that is, if you want to collaborate with others on
> > >>> something
> > >>> that will be part of Apache NetBeans at some stage.
> > >>>
> > >>> Gj
> > >>>
> > >>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <arsi@chello.sk <javascript:;>>
> wrote:
> > >>>
> > >>> Hi,
> > >>>>
> > >>>> I think it should be a separate repository.
> > >>>> I started under NB81, where Radim ended. As I wrote it should first
> be
> > >>>> stabilized under NB 81/82 as plugin.
> > >>>>
> > >>>> And after all my life I work with hg, git kills me ;)
> > >>>>
> > >>>>
> > >>>>
> > >>>> Arsi
> > >>>>
> > >>>>
> > >>>>
> > >>>> ------------------------------------------------------------
> > >>>> ------------
> > >>>>
> > >>>> *From:* Geertjan Wielenga
> > >>>> *Sent:* Tuesday, October 24, 2017 2:15PM
> > >>>> *To:* Dev
> > >>>> *Subject:* Re: Android support analysis
> > >>>>
> > >>>>
> > >>>>
> > >>>> Excellent news!
> > >>>>
> > >>>> Maybe you could consider making an android branch of Apache
> NetBeans,
> > >>>> just
> > >>>> like these:
> > >>>>
> > >>>> https://github.com/apache/incubator-netbeans/branches
> > >>>>
> > >>>> So that others can collaborate with you on your work?
> > >>>>
> > >>>> I.e., this would be a new feature branch.
> > >>>>
> > >>>> Gj
> > >>>>
> > >>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <arsi@chello.sk
> <javascript:;>> wrote:
> > >>>>
> > >>>> Hi,
> > >>>>
> > >>>>> I contacted Radim Kubacki author of the NBANDROID project.
> > >>>>> According to his words, it has nomotivationto continue development.
> > >>>>> (last
> > >>>>> commit is from 2015)
> > >>>>> But he has nothing against that the community will continue to
> > develop
> > >>>>> the
> > >>>>> project and that it could part of Apache netbeans.
> > >>>>> NBANDROID is under Apache 2 License.
> > >>>>>
> > >>>>>
> > >>>>> It's an extension of Gradle Support plugin.
> > >>>>> And there will be a lot of work to do:
> > >>>>>
> > >>>>>    * Rewrite to new Gradle plugin extension API
> > >>>>> (GradleProjectExtension2)
> > >>>>>    * Remove old Ant support
> > >>>>>    *
> > >>>>>      Google gradually moving tools from SDK to Android studio. So
> we
> > >>>>> have
> > >>>>>      to write AVD Manager, SDK Manager and many other things.
> > >>>>>    * New visual Layout Editor
> > >>>>>
> > >>>>> I started cleaning the code, I made a maven nb module  and I've
> > already
> > >>>>> fixed some things:
> > >>>>>
> > >>>>>    * Dependency analysis + Code assistance
> > >>>>>    * Run + Debug
> > >>>>>    * Android Emulator
> > >>>>>
> > >>>>> I suggest continuing as a plugin, and when the project is
> stabilized,
> > >>>>> you
> > >>>>> can start thinking about adding it to the NB core
> > >>>>>
> > >>>>> Arsi
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >
> >
> >
>
>

AW: Android support analysis

Posted by Christian Lenz <ch...@gmx.net>.
But we can work together on the 3rd-party-plugin anyway. Of Course, if the plan is still having it right inside NetBeans core from the beginning ok, but I think this was done with Twig and Git before it went to the NetBeans repo after a specific period. NBTS, could be part of NetBeans too one day. But for now it is good as it is, to separate it from the core.

Thx for the clarification here.

Regards


Chris

Von: Geertjan Wielenga
Gesendet: Dienstag, 24. Oktober 2017 15:58
An: dev@netbeans.incubator.apache.org
Betreff: Re: Android support analysis

You're absolutely right, Chris.

However, the problem comes in if many of us will want to work together on
the Android support, i.e., if we'll want to collaborate on this feature,
and if we want it to be part of Apache NetBeans itself. That's when it will
be applicable that we'll have a branch, etc, for working on this together.

Hope that clarifies,

Gj


On Tue, Oct 24, 2017 at 3:56 PM, Christian Lenz <ch...@gmx.net>
wrote:

> What is the Problem of having a 3rd-party-plugin, which is not yet inside
> of the NetBeans core, but has licensed as Apache 2? No one can test the
> state of the plugin, until you clone the whole source of NetBeans, build it
> and try the plugin inside of it? Since when we are against
> 3rd-party-plugins? I have a lot and maybe one day, they can be part of
> NetBeans, but not until we have a better release strategy, which faster
> release cycles etc.
>
> Only my 2 cents here, it would be best to have it as a separate repo
> outside of Apache NetBeans, but licensed with Apache 2.0, There is nothing
> wrong with it, isn’t it?
>
>
> Regards
>
> Chris
>
> Gesendet von Mail für Windows 10
>
> Von: Geertjan Wielenga
> Gesendet: Dienstag, 24. Oktober 2017 15:46
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Android support analysis
>
> And I think it would be best if Radim Kubacki himself would commit those
> sources to the Android branch of Apache NetBeans, since he is the author of
> that code.
>
> Gj
>
> On Tue, Oct 24, 2017 at 3:40 PM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
> > A problem is that, while Apache NetBeans is built on Ant, the sources you
> > have provided build via Maven.
> >
> > Not sure what the right approach should be. Maybe the source structure
> > should be in Ant, if it's going to be part of Apache NetBeans?
> >
> > (I don't see NetBeans moving to Maven very soon.)
> >
> > Gj
> >
> > On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
> > geertjan.wielenga@googlemail.com> wrote:
> >
> >> OK, I have created an 'android' branch:
> >>
> >> https://github.com/apache/incubator-netbeans/branches
> >>
> >> Are you sure we're able to simply take the content of that tar.gz and
> put
> >> it into the android branch?
> >>
> >> I.e., these files are (or can be) licensed to Apache?
> >>
> >> Gj
> >>
> >>
> >> On Tue, Oct 24, 2017 at 3:27 PM, arsi <ar...@chello.sk> wrote:
> >>
> >>> Hi,
> >>>
> >>> OKwe can move it there..
> >>> but I do not know how to do it..
> >>>
> >>> The sources are here: http://server.arsi.sk/Gradle-A
> >>> ndroid-support.tar.gz
> >>>
> >>>
> >>>
> >>> Arsi
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> ------------------------------------------------------------
> ------------
> >>>
> >>> *From:* Geertjan Wielenga
> >>> *Sent:* Tuesday, October 24, 2017 2:50PM
> >>>
> >>> *To:* Dev
> >>> *Subject:* Re: Android support analysis
> >>>
> >>>
> >>> Great. Note that if you want to collaborate with others, regardless of
> >>> how
> >>> stable it is right now, etc, the Apache Way of doing things is to
> >>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
> >>> outside Apache, but in Apache itself. I.e., the way would be to create
> a
> >>> branch off of the main Apache NetBeans repo and put the code there and
> >>> work
> >>> on it there -- that is, if you want to collaborate with others on
> >>> something
> >>> that will be part of Apache NetBeans at some stage.
> >>>
> >>> Gj
> >>>
> >>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:
> >>>
> >>> Hi,
> >>>>
> >>>> I think it should be a separate repository.
> >>>> I started under NB81, where Radim ended. As I wrote it should first be
> >>>> stabilized under NB 81/82 as plugin.
> >>>>
> >>>> And after all my life I work with hg, git kills me ;)
> >>>>
> >>>>
> >>>>
> >>>> Arsi
> >>>>
> >>>>
> >>>>
> >>>> ------------------------------------------------------------
> >>>> ------------
> >>>>
> >>>> *From:* Geertjan Wielenga
> >>>> *Sent:* Tuesday, October 24, 2017 2:15PM
> >>>> *To:* Dev
> >>>> *Subject:* Re: Android support analysis
> >>>>
> >>>>
> >>>>
> >>>> Excellent news!
> >>>>
> >>>> Maybe you could consider making an android branch of Apache NetBeans,
> >>>> just
> >>>> like these:
> >>>>
> >>>> https://github.com/apache/incubator-netbeans/branches
> >>>>
> >>>> So that others can collaborate with you on your work?
> >>>>
> >>>> I.e., this would be a new feature branch.
> >>>>
> >>>> Gj
> >>>>
> >>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>>> I contacted Radim Kubacki author of the NBANDROID project.
> >>>>> According to his words, it has nomotivationto continue development.
> >>>>> (last
> >>>>> commit is from 2015)
> >>>>> But he has nothing against that the community will continue to
> develop
> >>>>> the
> >>>>> project and that it could part of Apache netbeans.
> >>>>> NBANDROID is under Apache 2 License.
> >>>>>
> >>>>>
> >>>>> It's an extension of Gradle Support plugin.
> >>>>> And there will be a lot of work to do:
> >>>>>
> >>>>>    * Rewrite to new Gradle plugin extension API
> >>>>> (GradleProjectExtension2)
> >>>>>    * Remove old Ant support
> >>>>>    *
> >>>>>      Google gradually moving tools from SDK to Android studio. So we
> >>>>> have
> >>>>>      to write AVD Manager, SDK Manager and many other things.
> >>>>>    * New visual Layout Editor
> >>>>>
> >>>>> I started cleaning the code, I made a maven nb module  and I've
> already
> >>>>> fixed some things:
> >>>>>
> >>>>>    * Dependency analysis + Code assistance
> >>>>>    * Run + Debug
> >>>>>    * Android Emulator
> >>>>>
> >>>>> I suggest continuing as a plugin, and when the project is stabilized,
> >>>>> you
> >>>>> can start thinking about adding it to the NB core
> >>>>>
> >>>>> Arsi
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >
>
>


Re: Android support analysis

Posted by Geertjan Wielenga <ge...@googlemail.com>.
You're absolutely right, Chris.

However, the problem comes in if many of us will want to work together on
the Android support, i.e., if we'll want to collaborate on this feature,
and if we want it to be part of Apache NetBeans itself. That's when it will
be applicable that we'll have a branch, etc, for working on this together.

Hope that clarifies,

Gj


On Tue, Oct 24, 2017 at 3:56 PM, Christian Lenz <ch...@gmx.net>
wrote:

> What is the Problem of having a 3rd-party-plugin, which is not yet inside
> of the NetBeans core, but has licensed as Apache 2? No one can test the
> state of the plugin, until you clone the whole source of NetBeans, build it
> and try the plugin inside of it? Since when we are against
> 3rd-party-plugins? I have a lot and maybe one day, they can be part of
> NetBeans, but not until we have a better release strategy, which faster
> release cycles etc.
>
> Only my 2 cents here, it would be best to have it as a separate repo
> outside of Apache NetBeans, but licensed with Apache 2.0, There is nothing
> wrong with it, isn’t it?
>
>
> Regards
>
> Chris
>
> Gesendet von Mail für Windows 10
>
> Von: Geertjan Wielenga
> Gesendet: Dienstag, 24. Oktober 2017 15:46
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Android support analysis
>
> And I think it would be best if Radim Kubacki himself would commit those
> sources to the Android branch of Apache NetBeans, since he is the author of
> that code.
>
> Gj
>
> On Tue, Oct 24, 2017 at 3:40 PM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
> > A problem is that, while Apache NetBeans is built on Ant, the sources you
> > have provided build via Maven.
> >
> > Not sure what the right approach should be. Maybe the source structure
> > should be in Ant, if it's going to be part of Apache NetBeans?
> >
> > (I don't see NetBeans moving to Maven very soon.)
> >
> > Gj
> >
> > On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
> > geertjan.wielenga@googlemail.com> wrote:
> >
> >> OK, I have created an 'android' branch:
> >>
> >> https://github.com/apache/incubator-netbeans/branches
> >>
> >> Are you sure we're able to simply take the content of that tar.gz and
> put
> >> it into the android branch?
> >>
> >> I.e., these files are (or can be) licensed to Apache?
> >>
> >> Gj
> >>
> >>
> >> On Tue, Oct 24, 2017 at 3:27 PM, arsi <ar...@chello.sk> wrote:
> >>
> >>> Hi,
> >>>
> >>> OKwe can move it there..
> >>> but I do not know how to do it..
> >>>
> >>> The sources are here: http://server.arsi.sk/Gradle-A
> >>> ndroid-support.tar.gz
> >>>
> >>>
> >>>
> >>> Arsi
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> ------------------------------------------------------------
> ------------
> >>>
> >>> *From:* Geertjan Wielenga
> >>> *Sent:* Tuesday, October 24, 2017 2:50PM
> >>>
> >>> *To:* Dev
> >>> *Subject:* Re: Android support analysis
> >>>
> >>>
> >>> Great. Note that if you want to collaborate with others, regardless of
> >>> how
> >>> stable it is right now, etc, the Apache Way of doing things is to
> >>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
> >>> outside Apache, but in Apache itself. I.e., the way would be to create
> a
> >>> branch off of the main Apache NetBeans repo and put the code there and
> >>> work
> >>> on it there -- that is, if you want to collaborate with others on
> >>> something
> >>> that will be part of Apache NetBeans at some stage.
> >>>
> >>> Gj
> >>>
> >>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:
> >>>
> >>> Hi,
> >>>>
> >>>> I think it should be a separate repository.
> >>>> I started under NB81, where Radim ended. As I wrote it should first be
> >>>> stabilized under NB 81/82 as plugin.
> >>>>
> >>>> And after all my life I work with hg, git kills me ;)
> >>>>
> >>>>
> >>>>
> >>>> Arsi
> >>>>
> >>>>
> >>>>
> >>>> ------------------------------------------------------------
> >>>> ------------
> >>>>
> >>>> *From:* Geertjan Wielenga
> >>>> *Sent:* Tuesday, October 24, 2017 2:15PM
> >>>> *To:* Dev
> >>>> *Subject:* Re: Android support analysis
> >>>>
> >>>>
> >>>>
> >>>> Excellent news!
> >>>>
> >>>> Maybe you could consider making an android branch of Apache NetBeans,
> >>>> just
> >>>> like these:
> >>>>
> >>>> https://github.com/apache/incubator-netbeans/branches
> >>>>
> >>>> So that others can collaborate with you on your work?
> >>>>
> >>>> I.e., this would be a new feature branch.
> >>>>
> >>>> Gj
> >>>>
> >>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>>> I contacted Radim Kubacki author of the NBANDROID project.
> >>>>> According to his words, it has nomotivationto continue development.
> >>>>> (last
> >>>>> commit is from 2015)
> >>>>> But he has nothing against that the community will continue to
> develop
> >>>>> the
> >>>>> project and that it could part of Apache netbeans.
> >>>>> NBANDROID is under Apache 2 License.
> >>>>>
> >>>>>
> >>>>> It's an extension of Gradle Support plugin.
> >>>>> And there will be a lot of work to do:
> >>>>>
> >>>>>    * Rewrite to new Gradle plugin extension API
> >>>>> (GradleProjectExtension2)
> >>>>>    * Remove old Ant support
> >>>>>    *
> >>>>>      Google gradually moving tools from SDK to Android studio. So we
> >>>>> have
> >>>>>      to write AVD Manager, SDK Manager and many other things.
> >>>>>    * New visual Layout Editor
> >>>>>
> >>>>> I started cleaning the code, I made a maven nb module  and I've
> already
> >>>>> fixed some things:
> >>>>>
> >>>>>    * Dependency analysis + Code assistance
> >>>>>    * Run + Debug
> >>>>>    * Android Emulator
> >>>>>
> >>>>> I suggest continuing as a plugin, and when the project is stabilized,
> >>>>> you
> >>>>> can start thinking about adding it to the NB core
> >>>>>
> >>>>> Arsi
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >
>
>

AW: Android support analysis

Posted by Christian Lenz <ch...@gmx.net>.
What is the Problem of having a 3rd-party-plugin, which is not yet inside of the NetBeans core, but has licensed as Apache 2? No one can test the state of the plugin, until you clone the whole source of NetBeans, build it and try the plugin inside of it? Since when we are against 3rd-party-plugins? I have a lot and maybe one day, they can be part of NetBeans, but not until we have a better release strategy, which faster release cycles etc.

Only my 2 cents here, it would be best to have it as a separate repo outside of Apache NetBeans, but licensed with Apache 2.0, There is nothing wrong with it, isn’t it?


Regards

Chris

Gesendet von Mail für Windows 10

Von: Geertjan Wielenga
Gesendet: Dienstag, 24. Oktober 2017 15:46
An: dev@netbeans.incubator.apache.org
Betreff: Re: Android support analysis

And I think it would be best if Radim Kubacki himself would commit those
sources to the Android branch of Apache NetBeans, since he is the author of
that code.

Gj

On Tue, Oct 24, 2017 at 3:40 PM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:

> A problem is that, while Apache NetBeans is built on Ant, the sources you
> have provided build via Maven.
>
> Not sure what the right approach should be. Maybe the source structure
> should be in Ant, if it's going to be part of Apache NetBeans?
>
> (I don't see NetBeans moving to Maven very soon.)
>
> Gj
>
> On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
>> OK, I have created an 'android' branch:
>>
>> https://github.com/apache/incubator-netbeans/branches
>>
>> Are you sure we're able to simply take the content of that tar.gz and put
>> it into the android branch?
>>
>> I.e., these files are (or can be) licensed to Apache?
>>
>> Gj
>>
>>
>> On Tue, Oct 24, 2017 at 3:27 PM, arsi <ar...@chello.sk> wrote:
>>
>>> Hi,
>>>
>>> OKwe can move it there..
>>> but I do not know how to do it..
>>>
>>> The sources are here: http://server.arsi.sk/Gradle-A
>>> ndroid-support.tar.gz
>>>
>>>
>>>
>>> Arsi
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Geertjan Wielenga
>>> *Sent:* Tuesday, October 24, 2017 2:50PM
>>>
>>> *To:* Dev
>>> *Subject:* Re: Android support analysis
>>>
>>>
>>> Great. Note that if you want to collaborate with others, regardless of
>>> how
>>> stable it is right now, etc, the Apache Way of doing things is to
>>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
>>> outside Apache, but in Apache itself. I.e., the way would be to create a
>>> branch off of the main Apache NetBeans repo and put the code there and
>>> work
>>> on it there -- that is, if you want to collaborate with others on
>>> something
>>> that will be part of Apache NetBeans at some stage.
>>>
>>> Gj
>>>
>>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:
>>>
>>> Hi,
>>>>
>>>> I think it should be a separate repository.
>>>> I started under NB81, where Radim ended. As I wrote it should first be
>>>> stabilized under NB 81/82 as plugin.
>>>>
>>>> And after all my life I work with hg, git kills me ;)
>>>>
>>>>
>>>>
>>>> Arsi
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------
>>>> ------------
>>>>
>>>> *From:* Geertjan Wielenga
>>>> *Sent:* Tuesday, October 24, 2017 2:15PM
>>>> *To:* Dev
>>>> *Subject:* Re: Android support analysis
>>>>
>>>>
>>>>
>>>> Excellent news!
>>>>
>>>> Maybe you could consider making an android branch of Apache NetBeans,
>>>> just
>>>> like these:
>>>>
>>>> https://github.com/apache/incubator-netbeans/branches
>>>>
>>>> So that others can collaborate with you on your work?
>>>>
>>>> I.e., this would be a new feature branch.
>>>>
>>>> Gj
>>>>
>>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
>>>>
>>>> Hi,
>>>>
>>>>> I contacted Radim Kubacki author of the NBANDROID project.
>>>>> According to his words, it has nomotivationto continue development.
>>>>> (last
>>>>> commit is from 2015)
>>>>> But he has nothing against that the community will continue to develop
>>>>> the
>>>>> project and that it could part of Apache netbeans.
>>>>> NBANDROID is under Apache 2 License.
>>>>>
>>>>>
>>>>> It's an extension of Gradle Support plugin.
>>>>> And there will be a lot of work to do:
>>>>>
>>>>>    * Rewrite to new Gradle plugin extension API
>>>>> (GradleProjectExtension2)
>>>>>    * Remove old Ant support
>>>>>    *
>>>>>      Google gradually moving tools from SDK to Android studio. So we
>>>>> have
>>>>>      to write AVD Manager, SDK Manager and many other things.
>>>>>    * New visual Layout Editor
>>>>>
>>>>> I started cleaning the code, I made a maven nb module  and I've already
>>>>> fixed some things:
>>>>>
>>>>>    * Dependency analysis + Code assistance
>>>>>    * Run + Debug
>>>>>    * Android Emulator
>>>>>
>>>>> I suggest continuing as a plugin, and when the project is stabilized,
>>>>> you
>>>>> can start thinking about adding it to the NB core
>>>>>
>>>>> Arsi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>


Re: Android support analysis

Posted by Geertjan Wielenga <ge...@googlemail.com>.
And I think it would be best if Radim Kubacki himself would commit those
sources to the Android branch of Apache NetBeans, since he is the author of
that code.

Gj

On Tue, Oct 24, 2017 at 3:40 PM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:

> A problem is that, while Apache NetBeans is built on Ant, the sources you
> have provided build via Maven.
>
> Not sure what the right approach should be. Maybe the source structure
> should be in Ant, if it's going to be part of Apache NetBeans?
>
> (I don't see NetBeans moving to Maven very soon.)
>
> Gj
>
> On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
>> OK, I have created an 'android' branch:
>>
>> https://github.com/apache/incubator-netbeans/branches
>>
>> Are you sure we're able to simply take the content of that tar.gz and put
>> it into the android branch?
>>
>> I.e., these files are (or can be) licensed to Apache?
>>
>> Gj
>>
>>
>> On Tue, Oct 24, 2017 at 3:27 PM, arsi <ar...@chello.sk> wrote:
>>
>>> Hi,
>>>
>>> OKwe can move it there..
>>> but I do not know how to do it..
>>>
>>> The sources are here: http://server.arsi.sk/Gradle-A
>>> ndroid-support.tar.gz
>>>
>>>
>>>
>>> Arsi
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Geertjan Wielenga
>>> *Sent:* Tuesday, October 24, 2017 2:50PM
>>>
>>> *To:* Dev
>>> *Subject:* Re: Android support analysis
>>>
>>>
>>> Great. Note that if you want to collaborate with others, regardless of
>>> how
>>> stable it is right now, etc, the Apache Way of doing things is to
>>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
>>> outside Apache, but in Apache itself. I.e., the way would be to create a
>>> branch off of the main Apache NetBeans repo and put the code there and
>>> work
>>> on it there -- that is, if you want to collaborate with others on
>>> something
>>> that will be part of Apache NetBeans at some stage.
>>>
>>> Gj
>>>
>>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:
>>>
>>> Hi,
>>>>
>>>> I think it should be a separate repository.
>>>> I started under NB81, where Radim ended. As I wrote it should first be
>>>> stabilized under NB 81/82 as plugin.
>>>>
>>>> And after all my life I work with hg, git kills me ;)
>>>>
>>>>
>>>>
>>>> Arsi
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------
>>>> ------------
>>>>
>>>> *From:* Geertjan Wielenga
>>>> *Sent:* Tuesday, October 24, 2017 2:15PM
>>>> *To:* Dev
>>>> *Subject:* Re: Android support analysis
>>>>
>>>>
>>>>
>>>> Excellent news!
>>>>
>>>> Maybe you could consider making an android branch of Apache NetBeans,
>>>> just
>>>> like these:
>>>>
>>>> https://github.com/apache/incubator-netbeans/branches
>>>>
>>>> So that others can collaborate with you on your work?
>>>>
>>>> I.e., this would be a new feature branch.
>>>>
>>>> Gj
>>>>
>>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
>>>>
>>>> Hi,
>>>>
>>>>> I contacted Radim Kubacki author of the NBANDROID project.
>>>>> According to his words, it has nomotivationto continue development.
>>>>> (last
>>>>> commit is from 2015)
>>>>> But he has nothing against that the community will continue to develop
>>>>> the
>>>>> project and that it could part of Apache netbeans.
>>>>> NBANDROID is under Apache 2 License.
>>>>>
>>>>>
>>>>> It's an extension of Gradle Support plugin.
>>>>> And there will be a lot of work to do:
>>>>>
>>>>>    * Rewrite to new Gradle plugin extension API
>>>>> (GradleProjectExtension2)
>>>>>    * Remove old Ant support
>>>>>    *
>>>>>      Google gradually moving tools from SDK to Android studio. So we
>>>>> have
>>>>>      to write AVD Manager, SDK Manager and many other things.
>>>>>    * New visual Layout Editor
>>>>>
>>>>> I started cleaning the code, I made a maven nb module  and I've already
>>>>> fixed some things:
>>>>>
>>>>>    * Dependency analysis + Code assistance
>>>>>    * Run + Debug
>>>>>    * Android Emulator
>>>>>
>>>>> I suggest continuing as a plugin, and when the project is stabilized,
>>>>> you
>>>>> can start thinking about adding it to the NB core
>>>>>
>>>>> Arsi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>

Re: Android support analysis

Posted by Geertjan Wielenga <ge...@googlemail.com>.
A problem is that, while Apache NetBeans is built on Ant, the sources you
have provided build via Maven.

Not sure what the right approach should be. Maybe the source structure
should be in Ant, if it's going to be part of Apache NetBeans?

(I don't see NetBeans moving to Maven very soon.)

Gj

On Tue, Oct 24, 2017 at 3:32 PM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:

> OK, I have created an 'android' branch:
>
> https://github.com/apache/incubator-netbeans/branches
>
> Are you sure we're able to simply take the content of that tar.gz and put
> it into the android branch?
>
> I.e., these files are (or can be) licensed to Apache?
>
> Gj
>
>
> On Tue, Oct 24, 2017 at 3:27 PM, arsi <ar...@chello.sk> wrote:
>
>> Hi,
>>
>> OKwe can move it there..
>> but I do not know how to do it..
>>
>> The sources are here: http://server.arsi.sk/Gradle-Android-support.tar.gz
>>
>>
>>
>> Arsi
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Geertjan Wielenga
>> *Sent:* Tuesday, October 24, 2017 2:50PM
>>
>> *To:* Dev
>> *Subject:* Re: Android support analysis
>>
>>
>> Great. Note that if you want to collaborate with others, regardless of how
>> stable it is right now, etc, the Apache Way of doing things is to
>> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
>> outside Apache, but in Apache itself. I.e., the way would be to create a
>> branch off of the main Apache NetBeans repo and put the code there and
>> work
>> on it there -- that is, if you want to collaborate with others on
>> something
>> that will be part of Apache NetBeans at some stage.
>>
>> Gj
>>
>> On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:
>>
>> Hi,
>>>
>>> I think it should be a separate repository.
>>> I started under NB81, where Radim ended. As I wrote it should first be
>>> stabilized under NB 81/82 as plugin.
>>>
>>> And after all my life I work with hg, git kills me ;)
>>>
>>>
>>>
>>> Arsi
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Geertjan Wielenga
>>> *Sent:* Tuesday, October 24, 2017 2:15PM
>>> *To:* Dev
>>> *Subject:* Re: Android support analysis
>>>
>>>
>>>
>>> Excellent news!
>>>
>>> Maybe you could consider making an android branch of Apache NetBeans,
>>> just
>>> like these:
>>>
>>> https://github.com/apache/incubator-netbeans/branches
>>>
>>> So that others can collaborate with you on your work?
>>>
>>> I.e., this would be a new feature branch.
>>>
>>> Gj
>>>
>>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
>>>
>>> Hi,
>>>
>>>> I contacted Radim Kubacki author of the NBANDROID project.
>>>> According to his words, it has nomotivationto continue development.
>>>> (last
>>>> commit is from 2015)
>>>> But he has nothing against that the community will continue to develop
>>>> the
>>>> project and that it could part of Apache netbeans.
>>>> NBANDROID is under Apache 2 License.
>>>>
>>>>
>>>> It's an extension of Gradle Support plugin.
>>>> And there will be a lot of work to do:
>>>>
>>>>    * Rewrite to new Gradle plugin extension API
>>>> (GradleProjectExtension2)
>>>>    * Remove old Ant support
>>>>    *
>>>>      Google gradually moving tools from SDK to Android studio. So we
>>>> have
>>>>      to write AVD Manager, SDK Manager and many other things.
>>>>    * New visual Layout Editor
>>>>
>>>> I started cleaning the code, I made a maven nb module  and I've already
>>>> fixed some things:
>>>>
>>>>    * Dependency analysis + Code assistance
>>>>    * Run + Debug
>>>>    * Android Emulator
>>>>
>>>> I suggest continuing as a plugin, and when the project is stabilized,
>>>> you
>>>> can start thinking about adding it to the NB core
>>>>
>>>> Arsi
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>
>>
>>
>

Re: Android support analysis

Posted by Geertjan Wielenga <ge...@googlemail.com>.
OK, I have created an 'android' branch:

https://github.com/apache/incubator-netbeans/branches

Are you sure we're able to simply take the content of that tar.gz and put
it into the android branch?

I.e., these files are (or can be) licensed to Apache?

Gj


On Tue, Oct 24, 2017 at 3:27 PM, arsi <ar...@chello.sk> wrote:

> Hi,
>
> OKwe can move it there..
> but I do not know how to do it..
>
> The sources are here: http://server.arsi.sk/Gradle-Android-support.tar.gz
>
>
>
> Arsi
>
>
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Geertjan Wielenga
> *Sent:* Tuesday, October 24, 2017 2:50PM
>
> *To:* Dev
> *Subject:* Re: Android support analysis
>
>
> Great. Note that if you want to collaborate with others, regardless of how
> stable it is right now, etc, the Apache Way of doing things is to
> collaborate at Apache, i.e., not in a separate GitHub repo somewhere
> outside Apache, but in Apache itself. I.e., the way would be to create a
> branch off of the main Apache NetBeans repo and put the code there and work
> on it there -- that is, if you want to collaborate with others on something
> that will be part of Apache NetBeans at some stage.
>
> Gj
>
> On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:
>
> Hi,
>>
>> I think it should be a separate repository.
>> I started under NB81, where Radim ended. As I wrote it should first be
>> stabilized under NB 81/82 as plugin.
>>
>> And after all my life I work with hg, git kills me ;)
>>
>>
>>
>> Arsi
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Geertjan Wielenga
>> *Sent:* Tuesday, October 24, 2017 2:15PM
>> *To:* Dev
>> *Subject:* Re: Android support analysis
>>
>>
>>
>> Excellent news!
>>
>> Maybe you could consider making an android branch of Apache NetBeans, just
>> like these:
>>
>> https://github.com/apache/incubator-netbeans/branches
>>
>> So that others can collaborate with you on your work?
>>
>> I.e., this would be a new feature branch.
>>
>> Gj
>>
>> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
>>
>> Hi,
>>
>>> I contacted Radim Kubacki author of the NBANDROID project.
>>> According to his words, it has nomotivationto continue development. (last
>>> commit is from 2015)
>>> But he has nothing against that the community will continue to develop
>>> the
>>> project and that it could part of Apache netbeans.
>>> NBANDROID is under Apache 2 License.
>>>
>>>
>>> It's an extension of Gradle Support plugin.
>>> And there will be a lot of work to do:
>>>
>>>    * Rewrite to new Gradle plugin extension API (GradleProjectExtension2)
>>>    * Remove old Ant support
>>>    *
>>>      Google gradually moving tools from SDK to Android studio. So we have
>>>      to write AVD Manager, SDK Manager and many other things.
>>>    * New visual Layout Editor
>>>
>>> I started cleaning the code, I made a maven nb module  and I've already
>>> fixed some things:
>>>
>>>    * Dependency analysis + Code assistance
>>>    * Run + Debug
>>>    * Android Emulator
>>>
>>> I suggest continuing as a plugin, and when the project is stabilized, you
>>> can start thinking about adding it to the NB core
>>>
>>> Arsi
>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
>
>

Re: Android support analysis

Posted by arsi <ar...@chello.sk>.
Hi,

OKwe can move it there..
but I do not know how to do it..

The sources are here: http://server.arsi.sk/Gradle-Android-support.tar.gz



Arsi





------------------------------------------------------------------------

*From:* Geertjan Wielenga
*Sent:* Tuesday, October 24, 2017 2:50PM
*To:* Dev
*Subject:* Re: Android support analysis


Great. Note that if you want to collaborate with others, regardless of how
stable it is right now, etc, the Apache Way of doing things is to
collaborate at Apache, i.e., not in a separate GitHub repo somewhere
outside Apache, but in Apache itself. I.e., the way would be to create a
branch off of the main Apache NetBeans repo and put the code there and work
on it there -- that is, if you want to collaborate with others on something
that will be part of Apache NetBeans at some stage.

Gj

On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:

> Hi,
>
> I think it should be a separate repository.
> I started under NB81, where Radim ended. As I wrote it should first be
> stabilized under NB 81/82 as plugin.
>
> And after all my life I work with hg, git kills me ;)
>
>
>
> Arsi
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Geertjan Wielenga
> *Sent:* Tuesday, October 24, 2017 2:15PM
> *To:* Dev
> *Subject:* Re: Android support analysis
>
>
>
> Excellent news!
>
> Maybe you could consider making an android branch of Apache NetBeans, just
> like these:
>
> https://github.com/apache/incubator-netbeans/branches
>
> So that others can collaborate with you on your work?
>
> I.e., this would be a new feature branch.
>
> Gj
>
> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
>
> Hi,
>> I contacted Radim Kubacki author of the NBANDROID project.
>> According to his words, it has nomotivationto continue development. (last
>> commit is from 2015)
>> But he has nothing against that the community will continue to develop the
>> project and that it could part of Apache netbeans.
>> NBANDROID is under Apache 2 License.
>>
>>
>> It's an extension of Gradle Support plugin.
>> And there will be a lot of work to do:
>>
>>    * Rewrite to new Gradle plugin extension API (GradleProjectExtension2)
>>    * Remove old Ant support
>>    *
>>      Google gradually moving tools from SDK to Android studio. So we have
>>      to write AVD Manager, SDK Manager and many other things.
>>    * New visual Layout Editor
>>
>> I started cleaning the code, I made a maven nb module  and I've already
>> fixed some things:
>>
>>    * Dependency analysis + Code assistance
>>    * Run + Debug
>>    * Android Emulator
>>
>> I suggest continuing as a plugin, and when the project is stabilized, you
>> can start thinking about adding it to the NB core
>>
>> Arsi
>>
>>
>>
>>
>>







Re: Android support analysis

Posted by Geertjan Wielenga <ge...@googlemail.com>.
Great. Note that if you want to collaborate with others, regardless of how
stable it is right now, etc, the Apache Way of doing things is to
collaborate at Apache, i.e., not in a separate GitHub repo somewhere
outside Apache, but in Apache itself. I.e., the way would be to create a
branch off of the main Apache NetBeans repo and put the code there and work
on it there -- that is, if you want to collaborate with others on something
that will be part of Apache NetBeans at some stage.

Gj

On Tue, Oct 24, 2017 at 2:37 PM, arsi <ar...@chello.sk> wrote:

> Hi,
>
> I think it should be a separate repository.
> I started under NB81, where Radim ended. As I wrote it should first be
> stabilized under NB 81/82 as plugin.
>
> And after all my life I work with hg, git kills me ;)
>
>
>
> Arsi
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Geertjan Wielenga
> *Sent:* Tuesday, October 24, 2017 2:15PM
> *To:* Dev
> *Subject:* Re: Android support analysis
>
>
>
> Excellent news!
>
> Maybe you could consider making an android branch of Apache NetBeans, just
> like these:
>
> https://github.com/apache/incubator-netbeans/branches
>
> So that others can collaborate with you on your work?
>
> I.e., this would be a new feature branch.
>
> Gj
>
> On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:
>
> Hi,
>>
>> I contacted Radim Kubacki author of the NBANDROID project.
>> According to his words, it has nomotivationto continue development. (last
>> commit is from 2015)
>> But he has nothing against that the community will continue to develop the
>> project and that it could part of Apache netbeans.
>> NBANDROID is under Apache 2 License.
>>
>>
>> It's an extension of Gradle Support plugin.
>> And there will be a lot of work to do:
>>
>>   * Rewrite to new Gradle plugin extension API (GradleProjectExtension2)
>>   * Remove old Ant support
>>   *
>>     Google gradually moving tools from SDK to Android studio. So we have
>>     to write AVD Manager, SDK Manager and many other things.
>>   * New visual Layout Editor
>>
>> I started cleaning the code, I made a maven nb module  and I've already
>> fixed some things:
>>
>>   * Dependency analysis + Code assistance
>>   * Run + Debug
>>   * Android Emulator
>>
>> I suggest continuing as a plugin, and when the project is stabilized, you
>> can start thinking about adding it to the NB core
>>
>> Arsi
>>
>>
>>
>>
>>
>

Re: Android support analysis

Posted by arsi <ar...@chello.sk>.
Hi,

I think it should be a separate repository.
I started under NB81, where Radim ended. As I wrote it should first be 
stabilized under NB 81/82 as plugin.

And after all my life I work with hg, git kills me ;)



Arsi



------------------------------------------------------------------------

*From:* Geertjan Wielenga
*Sent:* Tuesday, October 24, 2017 2:15PM
*To:* Dev
*Subject:* Re: Android support analysis


Excellent news!

Maybe you could consider making an android branch of Apache NetBeans, just
like these:

https://github.com/apache/incubator-netbeans/branches

So that others can collaborate with you on your work?

I.e., this would be a new feature branch.

Gj

On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:

> Hi,
>
> I contacted Radim Kubacki author of the NBANDROID project.
> According to his words, it has nomotivationto continue development. (last
> commit is from 2015)
> But he has nothing against that the community will continue to develop the
> project and that it could part of Apache netbeans.
> NBANDROID is under Apache 2 License.
>
>
> It's an extension of Gradle Support plugin.
> And there will be a lot of work to do:
>
>   * Rewrite to new Gradle plugin extension API (GradleProjectExtension2)
>   * Remove old Ant support
>   *
>     Google gradually moving tools from SDK to Android studio. So we have
>     to write AVD Manager, SDK Manager and many other things.
>   * New visual Layout Editor
>
> I started cleaning the code, I made a maven nb module  and I've already
> fixed some things:
>
>   * Dependency analysis + Code assistance
>   * Run + Debug
>   * Android Emulator
>
> I suggest continuing as a plugin, and when the project is stabilized, you
> can start thinking about adding it to the NB core
>
> Arsi
>
>
>
>


Re: Android support analysis

Posted by Geertjan Wielenga <ge...@googlemail.com>.
Excellent news!

Maybe you could consider making an android branch of Apache NetBeans, just
like these:

https://github.com/apache/incubator-netbeans/branches

So that others can collaborate with you on your work?

I.e., this would be a new feature branch.

Gj

On Tue, Oct 24, 2017 at 2:02 PM, arsi <ar...@chello.sk> wrote:

> Hi,
>
> I contacted Radim Kubacki author of the NBANDROID project.
> According to his words, it has nomotivationto continue development. (last
> commit is from 2015)
> But he has nothing against that the community will continue to develop the
> project and that it could part of Apache netbeans.
> NBANDROID is under Apache 2 License.
>
>
> It's an extension of Gradle Support plugin.
> And there will be a lot of work to do:
>
>  * Rewrite to new Gradle plugin extension API (GradleProjectExtension2)
>  * Remove old Ant support
>  *
>    Google gradually moving tools from SDK to Android studio. So we have
>    to write AVD Manager, SDK Manager and many other things.
>  * New visual Layout Editor
>
> I started cleaning the code, I made a maven nb module  and I've already
> fixed some things:
>
>  * Dependency analysis + Code assistance
>  * Run + Debug
>  * Android Emulator
>
> I suggest continuing as a plugin, and when the project is stabilized, you
> can start thinking about adding it to the NB core
>
> Arsi
>
>
>
>