RE: Installers

[Kenneth Fogel]

After a bizarre experience with Eclipse's Windows installer, it dumped 350 meg 
into the user AppData folder in addition to where it was actually installed, I 
am questioning installers for Windows. I solved my Eclipse problem by just 
downloading the zipped version. NetBeans does not require any special treatment 
for Windows. It can be unzipped and a shortcut created. I assume it will no 
longer ship with Glassfish, a good thing, so its not necessary to deal with the 
GlassFish installation which is only to unzip it into a folder anyways. When 
NetBeans starts up it will create whatever folders it needs in the User folder. 
Yes, an installer is nice but all it should do on the Windows platform is unzip 
NetBeans in the folder of choice and add a shortcut. What about the Java 
Packager or is that not usable due to licensing?

Ken


-Original Message-
From: Carl Mosca  
Sent: August 10, 2018 7:33 AM
To: dev@netbeans.incubator.apache.org
Subject: Re: Installers

Well first off is MacOS dmg because that's where I code mostly.  Secondly I 
like the idea of both an RPM and a deb for those Linux distros but I get the 
"yum install" "apt-get" thing to it's just as high a priority for me.

And yes, I know Windows has to be addressed a well but that's my order of 
interest at this point.  On Windows, I would have to look because I don't know 
what the msi/exe preference is these days.

Carl

On Fri, Aug 10, 2018 at 7:10 AM Geertjan Wielenga 
 wrote:

> Which kinds of installers, i.e., for which operating systems, do you 
> want to create installers?
>
> Indeed, makes sense to me the idea of them being created during the build.
>
> Gj
>
> On Friday, August 10, 2018, Carl Mosca  wrote:
>
> > OK but I probably should have been a little more specific about the 
> > coordination part of my question.
> >
> > I am assuming that building the installers would, at some point, be 
> > part
> of
> > the build process.
> >
> > I believe Jenkins and ant are currently used.  Is there any history 
> > or preference with solutions to create the installers I should be aware of?
> >
> > Thank you,
> > Carl
> >
> > On Fri, Aug 10, 2018 at 2:36 AM Geertjan Wielenga 
> >  wrote:
> >
> > > Yes, if you can create installers, that would be wonderful!
> > >
> > > I’ve seen about three different Mac OSX installers around so far.
> > >
> > > Please don’t wait, create installers if you can, and write back 
> > > here
> with
> > > instructions when you’ve done so.
> > >
> > > Gj
> > >
> > > On Wednesday, August 8, 2018, Carl Mosca  wrote:
> > >
> > > > I am wondering if anyone is working on these. I would like to 
> > > > help if needed.
> > > >
> > >
> >
> >
> > --
> > Carl J. Mosca
> >
>


--
Carl J. Mosca

Setting breakpoints in NetBeans IDE dev code

[mark stephens]

I have NetBeans IDE building from NetBeans sources using excellent instructions 
on https://cwiki.apache.org/confluence/display/NETBEANS/Development+Environment

I can build and run it with tryme.

I have identified a module I want to edit. I have opened the module in NetBeans 
IDE and can reinstall it with reload it in target platform from NetBeans IDE. I 
am now trying to figure out if I can set breakpoints and step through the code 
in the IDE.

Is this possible and any hints?

Kind Regards,

MArk
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Public vs. Friend API Reloaded (Round 2)

[Tim Boudreau]

I'll pitch a couple of things in here:

1. Part of the problem with friend apis is your that the term gets
overloaded for two different concerns: A. APIs undergoing stabilization,
where the expectation is that a stable api will emerge, and B. Dependencies
which are never intended to produce an API. Because at the technical level
the module system doesn't need to distinguish those two things, we have a
single term representing both, resulting in confused expectations.

2. That being said, something Jarda and I used to stress in our api design
talks was "you are always writing an api" - if you followed good api design
patterns, opening a friend api should not be sentencing yourself to
code-jail. So I'd suggest splitting out the question of "should existing
apis become public" from "how do we encourage more public apis in the
future".

3. If you don't like the current situation with friend apis, you probably
want to support some proposal other than maintaining the status quo, or you
can expect more of the same.

-Tim

On Thu, Aug 9, 2018 at 2:38 PM Laszlo Kishalmi 
wrote:

> Go on People, share your thoughts!
>
> Thanks for Neil who already did that!
> Thanks for Jarda to adding one more option to select from!
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Public+vs+Friend+API
>
> On 08/08/2018 01:26 AM, Laszlo Kishalmi wrote:
> >
> > Dear all,
> >
> > I'd like to start the second round of discussion on this topic.
> >
> > Oliver Retting was so kind to summarize the opinions presented on our
> > mailing lists.
> >
> > I myself stared a mini analysis on each option, mentioning my attitude
> > to them as well.
> >
> > Please take your time, extend, modify and share your opinions and
> > attitude!
> >
> > Remember I'm just trying to drive this discussion not dictate it. So
> > any idea, opposition, pro and con are welcome!
> >
> >
> https://cwiki.apache.org/confluence/display/NETBEANS/Public+vs+Friend+API
> >
> > Let's give this round another 2 weeks, what can be extended with
> > another two if we feel the need.
> >
>
> --
http://timboudreau.com

Re: Installers

[Will Hartung]

On Fri, Aug 10, 2018 at 1:10 PM, Kenneth Fogel 
wrote:

> Yes, an installer is nice but all it should do on the Windows platform is
> unzip NetBeans in the folder of choice and add a shortcut.
>

For some reason that I don't understand, and perhaps someone could explain,
the installer for MacOS requires Administration privileges.

Being that it, too, is essentially a "zip file" (it's an application
bundle), I never really understood why it needs admin privs to install.

Maybe it's some Mac specific thing.

Re: Installers

[Carl Mosca]

I work in a place where you need admin rights to install on Windows as well
but that's a policy.

As far as the MacOS goes, it's based on BSD.

Therefore if /Applications is owned by root:wheel (or something similar
that's not the current user), you need privileges to "su or sudo" in order
to complete the installation process.  That is to say, the filesystem is
requiring the elevated access which in my opinion is a good thing.

One could/should be able to install in his/her home directory and not need
such access and I have seen apps take that approach as well.

Carl

On Fri, Aug 10, 2018 at 5:57 PM Will Hartung  wrote:

> On Fri, Aug 10, 2018 at 1:10 PM, Kenneth Fogel  >
> wrote:
>
> > Yes, an installer is nice but all it should do on the Windows platform is
> > unzip NetBeans in the folder of choice and add a shortcut.
> >
>
> For some reason that I don't understand, and perhaps someone could explain,
> the installer for MacOS requires Administration privileges.
>
> Being that it, too, is essentially a "zip file" (it's an application
> bundle), I never really understood why it needs admin privs to install.
>
> Maybe it's some Mac specific thing.
>


-- 
Carl J. Mosca

Re: Apache Jenkins Help Needed: Testing Snap package build

[Laszlo Kishalmi]

Thanks John!

Finally it worked. We can produce a snap image on Apache infrastructure.

BTW what should be the strategy with these Jenkins files. Separate repo? 
In the future I'd like to track two branches with this: master and the 
actual release.



On 08/09/2018 03:21 PM, John McDonnell wrote:
Right now it doesn't look like its set up correctly, as it cannot find 
'snapcraft', see:

https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-snap-packages/1/console


On Thu, 9 Aug 2018 at 23:16, Laszlo Kishalmi 
mailto:laszlo.kisha...@gmail.com>> wrote:


Thanks John!

Good idea! Now my question, where shall I put my Jenkinsfile?
NetBeans repository? Which branch: master or release90, or some
unique one, or in a separate repo?
Right now I just need to know if snapcraft set up correctly for
NetBeans on node H29

On 08/09/2018 01:05 AM, John McDonnell wrote:

@Laszlo Kishalmi 

If write a Jenkinsfile and commit it, then the Jenkins Job
properties are yours to adjust at any time, and the jenkins job
will update accordingly. We just need to create a pipeline job
and point it to the Jenkinsfile.


Regards

John



On Tue, 7 Aug 2018 at 22:48, Laszlo Kishalmi
mailto:laszlo.kisha...@gmail.com>> wrote:

Just made the Subject more descriptive.


On 08/07/2018 01:22 PM, Laszlo Kishalmi wrote:
>
> Hi there!
>
> I need a bit of Jenkins help. We are preparing the Apache
> infrastructure to be able to build a Snap package out of
our code.
> (https://issues.apache.org/jira/browse/INFRA-16728)
>
> I would need somebody who can configure a simple job for
test purposes
> on Apache Jenkins Grid.
>
> The job details:
>
>  1. Please tie it to node: H29
>  2. Clone the netbeans git repository
>  3. Use the release90 branch
>  4. There shall be a shell build step:
>     cd nbbuild/packaging/ && snapcraft
>
> That's all.
>
>
> Thanks!
>

Launchpad Account for an Apache Project for Publishing Snap-s

[Laszlo Kishalmi]

Dear Support,

We've reached two important milestones recently. We did our first 
release under Apache a few weeks ago and we were able to built our first 
Snap on Apache infrastructure yesterday.


We would like to move forward with the process uploading our Snaps to 
snapstore. In order to do that we need a Launchpad account. Though I 
have one personal account there, I've thought that it would be better if 
the project would have one.


I would like to know what we need to do to have an account for the project.

Thank you!

Laszlo Kishalmi

Apache (incubator) NetBeans Committer and PPMC member


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Apache Jenkins Help Needed: Testing Snap package build

[John McDonnell]

Hi,
No problem Laszlo, glad I could help.

So Jenkinsfiles can be stored in the same repo, let's say in
nbbuild directory for example (maybe under a CI or Jenkins folder), and
with multi-branch pipeline job in Jenkins, Jenkins will automatically
create jobs for each branch.

I've taken a look earlier at our Jenkins jobs, and I can see we have 5
Jenkins jobs, which I believe could be merged into 1 pipeline script, as
some of the jobs repeat steps, and I think if we had 1 pipeline we could
save on the resources we actually use in some places.

As a starting point, I was planning on looking into creating an
experimental pipeline next week and documenting the 2 approaches.  Later
on, we can add steps to the pipeline in relation to the release process,
and this is where could kick off a snap package build once a release is
performed.

I haven't looked at your setup yet, but what is required per release (I
guess there's a variable for the name of the build, 9.0, or dev etc?)

Regards

John



On Fri, 10 Aug 2018 at 22:33, Laszlo Kishalmi 
wrote:

> Thanks John!
>
> Finally it worked. We can produce a snap image on Apache infrastructure.
>
> BTW what should be the strategy with these Jenkins files. Separate repo?
> In the future I'd like to track two branches with this: master and the
> actual release.
>
>
> On 08/09/2018 03:21 PM, John McDonnell wrote:
>
> Right now it doesn't look like its set up correctly, as it cannot find 
> 'snapcraft',
> see:
>
> https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-snap-packages/1/console
>
>
> On Thu, 9 Aug 2018 at 23:16, Laszlo Kishalmi 
> wrote:
>
>> Thanks John!
>>
>> Good idea! Now my question, where shall I put my Jenkinsfile?
>> NetBeans repository? Which branch: master or release90, or some unique
>> one, or in a separate repo?
>> Right now I just need to know if snapcraft set up correctly for NetBeans
>> on node H29
>>
>> On 08/09/2018 01:05 AM, John McDonnell wrote:
>>
>> @Laszlo Kishalmi 
>>
>> If write a Jenkinsfile and commit it, then the Jenkins Job properties are
>> yours to adjust at any time, and the jenkins job will update accordingly.
>> We just need to create a pipeline job and point it to the Jenkinsfile.
>>
>>
>> Regards
>>
>> John
>>
>>
>>
>> On Tue, 7 Aug 2018 at 22:48, Laszlo Kishalmi 
>> wrote:
>>
>>> Just made the Subject more descriptive.
>>>
>>>
>>> On 08/07/2018 01:22 PM, Laszlo Kishalmi wrote:
>>> >
>>> > Hi there!
>>> >
>>> > I need a bit of Jenkins help. We are preparing the Apache
>>> > infrastructure to be able to build a Snap package out of our code.
>>> > (https://issues.apache.org/jira/browse/INFRA-16728)
>>> >
>>> > I would need somebody who can configure a simple job for test purposes
>>> > on Apache Jenkins Grid.
>>> >
>>> > The job details:
>>> >
>>> >  1. Please tie it to node: H29
>>> >  2. Clone the netbeans git repository
>>> >  3. Use the release90 branch
>>> >  4. There shall be a shell build step:
>>> > cd nbbuild/packaging/ && snapcraft
>>> >
>>> > That's all.
>>> >
>>> >
>>> > Thanks!
>>> >
>>>
>>>
>>
>

Re: Setting breakpoints in NetBeans IDE dev code

[Will Hartung]

On Fri, Aug 10, 2018 at 7:35 AM, mark stephens <
marksteph...@idrsolutions.com> wrote:

> I have identified a module I want to edit. I have opened the module in
> NetBeans IDE and can reinstall it with reload it in target platform from
> NetBeans IDE. I am now trying to figure out if I can set breakpoints and
> step through the code in the IDE.
>
> Is this possible and any hints?
>

Should Just Work(tm). Should be able to set breakpoints, then Debug the
module.

What problems are you having?

Re: ApacheCon Montreal NetBeans Presentation Suggestions

[Antonio Vieiro]

The more the merrier, as Emilian once said (I think)

El El mié, 8 ago 2018 a las 10:39, mark stephens <
marksteph...@idrsolutions.com> escribió:

>
>
> > On 7 Aug 2018, at 21:39, Antonio Vieiro  wrote:
> >
> > So we can update our events page at
> > http://netbeans.apache.org/community/events.html, right? That page
> requires
> > some love...
>
>
> Should events like Oracle’s CodeOne be on there? There are several
> NetBeans talks in the schedule. I am currently writing 2 of them….
>
> Kind Regards,
>
> MArk

Re: Installers

[Scott Palmer]

The macOS “installer” should be nothing more than a disk image with the 
application bundle. It should not be a .pkg file that might require admin 
privileges as it would be a drag and drop install. The user should be able to 
drag the app bundle wherever they want.

Scott

> On Aug 10, 2018, at 6:54 PM, Carl Mosca  wrote:
> 
> I work in a place where you need admin rights to install on Windows as well
> but that's a policy.
> 
> As far as the MacOS goes, it's based on BSD.
> 
> Therefore if /Applications is owned by root:wheel (or something similar
> that's not the current user), you need privileges to "su or sudo" in order
> to complete the installation process.  That is to say, the filesystem is
> requiring the elevated access which in my opinion is a good thing.
> 
> One could/should be able to install in his/her home directory and not need
> such access and I have seen apps take that approach as well.
> 
> Carl
> 
>> On Fri, Aug 10, 2018 at 5:57 PM Will Hartung  wrote:
>> 
>> On Fri, Aug 10, 2018 at 1:10 PM, Kenneth Fogel >> 
>> wrote:
>> 
>>> Yes, an installer is nice but all it should do on the Windows platform is
>>> unzip NetBeans in the folder of choice and add a shortcut.
>>> 
>> 
>> For some reason that I don't understand, and perhaps someone could explain,
>> the installer for MacOS requires Administration privileges.
>> 
>> Being that it, too, is essentially a "zip file" (it's an application
>> bundle), I never really understood why it needs admin privs to install.
>> 
>> Maybe it's some Mac specific thing.
>> 
> 
> 
> -- 
> Carl J. Mosca

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Apache NetBeans Release Cycle

[Wilfred Kigenyi]

On 2018/08/07 08:46:06, Geertjan Wielenga 
wrote:
> Hi all,>
>
> We've discussed this informally, i.e., the topic of the release>
> cycle/cadence, a few times over the past months.>
>
> Let's nail it down as far as possible so that we can give clarity to our>
> users about our intentions and also to enable us to organize features>
> coming in through donations and otherwise into releases.>
>
>
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+Cycle>

>
> Right now, we have a clear suggestion around in which month of the year
we>
> will release. I.e., the Apache NetBeans (incubating) 9.0 release was our>
> August release (and we even managed to release it a few days early, in>
> July, hurray!). So, this year, we will have another release in November,>
> that's our next big target, if we agree with the above proposal.>
>
> However, a separate discussion is about release numbers. Our current>
> release is 9.0. How do we decide to number the other releases? A simple>
> proposal might be to have our major release in August of each year and
then>
> all then make all the other releases minor. However, that's just a
thought,>
> another one could be that we should simply consider how large the
features>
> are that we have added and base major/minor on that. Or we could try to>
> follow the JDK release numbering more or less.>
>
> Anyway, thoughts welcome,>
>
> Gj>
>
Support for other languages should not be ignored. I am very happy excited
about support for Python in NVm
WK

Re: Apache NetBeans Release Cycle

[alex]

An IDE release is not same as language support release. NetBeans (or any other) 
IDE, as far as I am concerned is “just an editor” and a framework for other 
language plugins. Then, say, PHP and even Java rides on top of that. Mixing 
these two concepts together creates too much conflict. 
Then, there is a sour feeling when hear how next version of language plugin is 
already done, yet it’s not allowed to use until some arbitrary release party.
I have 1.3 million views Zend Framework (PHP) tutorials and I regularly get 
asked to show how to setup NetBeans instead of proprietary one I currently use 
they cannot afford. Unfortunately, that is a non-starter as the lessons showing 
what Zend Framework is capable of in *current, yet already half-a-year-old* 
version is not possible in editor that has even older version. I am not going 
to teach outdated content just to promote NetBeans on the screen, even though 
that would be excellent motivation for me to show it off.
Some replies here have idea about psychological comfort of frequent releases. 
As a language user, I do not notice much underlying platform releases. Again, 
this feeling may come from the conflict in my first point. More releases mean 
that NetBeans has a better chance to keep up with *ALL* languages by maximizing 
probability that do not have to wait long for next version of, say, EcmaScript. 
However, do language plugin users really care about the underlying *IDE 
framework* release version? Sure, there may come a time when NetBeans 14 might 
have some fancy editor feature so have to wait until “PHP plugin version 21” or 
even “Java plugin version 7” catches up to IDE release, but that is a VERY 
tolerable wait that does not actively prohibit usage. Then the editor framework 
can take however many years to have releases.


On 2018/08/07 08:46:06, Geertjan Wielenga 
 wrote: 
> Hi all,
> 
> We've discussed this informally, i.e., the topic of the release
> cycle/cadence, a few times over the past months.
> 
> Let's nail it down as far as possible so that we can give clarity to our
> users about our intentions and also to enable us to organize features
> coming in through donations and otherwise into releases.
> 
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+Cycle
> 
> Right now, we have a clear suggestion around in which month of the year we
> will release. I.e., the Apache NetBeans (incubating) 9.0 release was our
> August release (and we even managed to release it a few days early, in
> July, hurray!). So, this year, we will have another release in November,
> that's our next big target, if we agree with the above proposal.
> 
> However, a separate discussion is about release numbers. Our current
> release is 9.0. How do we decide to number the other releases? A simple
> proposal might be to have our major release in August of each year and then
> all then make all the other releases minor. However, that's just a thought,
> another one could be that we should simply consider how large the features
> are that we have added and base major/minor on that. Or we could try to
> follow the JDK release numbering more or less.
> 
> Anyway, thoughts welcome,
> 
> Gj
> 

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Apache NetBeans Release Cycle

[Alexander Romanenko]

An IDE release is not same as language support release. NetBeans (or any
other) IDE, as far as I am concerned is “just an editor” and a framework
for other language plugins. Then, say, PHP and even Java rides on top of
that. Mixing these two concepts together creates too much conflict.

Then, there is a sour feeling when hear how next version of language plugin
is already done, yet it’s not allowed to be used/shipped until some
arbitrary release party.

I have 1.3 million views Zend Framework (PHP) tutorials and I regularly get
asked to show how to setup free editor instead of proprietary one I
currently use they cannot afford. Unfortunately, that is a non-starter as
the lessons showing what Zend Framework is capable of in **current, yet
already half-a-year-old** version is not possible in editor that has even
older version. I am not going to teach outdated content just to promote
NetBeans on the screen, even though that would be excellent motivation for
me to show it off.

Some replies here have idea about psychological comfort of frequent
releases. As a language user, I do not notice much underlying platform
releases. Again, this feeling may come from the conflict in my first point.
More releases mean that NetBeans has a better chance to keep up with *ALL*
languages by maximizing probability that do not have to wait long for next
version of, say, EcmaScript. This increased probability gives false sense
of keeping up or innovating.

However, do language plugin users really care about the underlying *IDE
framework* release version? Sure, there may come a time when NetBeans 14
might have some fancy editor feature so have to wait until “PHP plugin
version 21” or “Java plugin version 7” catches up to IDE release, but that
is a VERY tolerable wait that does not actively prohibit usage. Then the
IDE  framework can take however many years to have releases.

AW: Case sensitive in directory name it is a issue

[Christian Lenz]

Which operating System do you have? For Windows, it is one Directory. If you 
have MyProjectFolder and myprojectfolder, it is the same.


Cheers

Chris

Von: Piotr Hoppe
Gesendet: Donnerstag, 9. August 2018 21:30
An: dev@netbeans.incubator.apache.org
Betreff: Case sensitive in directory name it is a issue

When you have in the project two directories with the same name but one 
of them uses lowercase letters and the second uses the uppercase letter, 
for example backend and Backend, so these name are differ only size of 
letters.
Then in the project tree you can see only one of this directories with 
them content.

In the project tree It should be visible both directories.

Earlier, I have already reported a similar problem 
https://netbeans.org/bugzilla/show_bug.cgi?id=268044

This issue occurs in the NetBeans 9.0 when I works on the PHP projects.

-- 
Piotr Hoppe

Re: Installers

[Geertjan Wielenga]

Yes, if you can create installers, that would be wonderful!

I’ve seen about three different Mac OSX installers around so far.

Please don’t wait, create installers if you can, and write back here with
instructions when you’ve done so.

Gj

On Wednesday, August 8, 2018, Carl Mosca  wrote:

> I am wondering if anyone is working on these. I would like to help if
> needed.
>

Re: AW: Case sensitive in directory name it is a issue

[Piotr Hoppe]

This issue occurs for:

- NetBeans 9.0

- PHP projects

- Mac OS high Sierra 10.13.6 with case sensitive APFS partition.


W dniu 10.08.2018 o 09:18, Christian Lenz pisze:

Which operating System do you have? For Windows, it is one Directory. If you 
have MyProjectFolder and myprojectfolder, it is the same.


Cheers

Chris

Von: Piotr Hoppe
Gesendet: Donnerstag, 9. August 2018 21:30
An: dev@netbeans.incubator.apache.org
Betreff: Case sensitive in directory name it is a issue

When you have in the project two directories with the same name but one
of them uses lowercase letters and the second uses the uppercase letter,
for example backend and Backend, so these name are differ only size of
letters.
Then in the project tree you can see only one of this directories with
them content.

In the project tree It should be visible both directories.

Earlier, I have already reported a similar problem
https://netbeans.org/bugzilla/show_bug.cgi?id=268044

This issue occurs in the NetBeans 9.0 when I works on the PHP projects.



--
Piotr Hoppe

Ta wiadomosc jest poufna i przeznaczona wylacznie dla adresata. Jesli 
jestes niezamierzonym odbiorca, to pilnie powiadom o tym nadawce. Nikomu 
nie ujawiaj tresci tej wiadomosci oraz nie uzywaj, nie kopiuj, nie 
drukuj, nie przechowuj, ani nie przekazuj dalej. Upewnij sie, ze zostala 
trwale usunieta. G-Forces Web Management Polska sp. z o.o., Ul. Trzy 
Lipy 3, 80-172 Gdańsk NIP: 583-292-04-23 REGON: 220105616 KRS: 246596

Re: [GROOVY] Enhancements to groovy support

[Josh Juneau]

Hi Sven,

I'd be interested in helping out as time allows.

Thanks

On Thu, Aug 9, 2018 at 4:58 PM John McDonnell 
wrote:

> Not sure how I'll be set work wise in September but I'd be happy to learn
> and help out if free or just learn from a distance if not.
>
> I do some stuff with Jenkinsfiles every so often at work and having better
> groovy support NetBeans might help here.
>
> Reach out closer to the time and I'll know myself how I'm sorted then...
>
> Regards
>
> John
>
> On Thu, 9 Aug 2018 at 22:27, Sven Reimers  wrote:
>
> > HI all,
> >
> > with Groovy support now donated and in master I want to come back to
> > something I started a long time ago:
> >
> > http://wiki.netbeans.org/MakeGroovyInNetBeansGreatAgain
> >
> > The results are some patches sitting around i various branches somewhere
> > 
> > Things I started work on
> > - support for traits
> > - flow typing (guess types where Groovy just sees Object)
> > - hint infrastructure (early prototype)
> > - .. probably more things just escaping me now
> >
> > Anyone interested in rebooting this effort?
> >
> > I hope to get the change rebased to master early September.
> >
> > I think it would be nice to have a wiki page collecting ideas how to
> > improve the support and afterwards start to file concrete issues to get
> > this started.
> >
> > Anyone interested in learning stuff about CSL, editors, parsers, Groovy
> > internals? This is the place to be if you want to have some real fun...
> >
> > - Sven
> >
>
-- 
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866

Creating Installers for 32 and 64 bit in the UI

[Oliver Rettig]

Hi,

for my platform apps I typically use the build-in installer creation for 
windows and linux 
installers. The new situation for me is that I need to create 64bit and 32 bit 
installers/
applications. This is of course possible easy by changing properties in the ant 
scripts but it 
would be more comfortable to have the switch available in the netbeans UI the 
same way as 
I can switch between creation of installers for windows and linux. 

Anybody else interested in this functionality? Any interest in such feature 
addition? Any idea 
how this can be implemented? I think it should be not very difficult to find 
the place where to 
add corresponding code. But it looks a bit hacky the combination of java-code 
and ant-
Scripts. Shouldnt the java-code automatically recognize some properties and 
build 
automatically some UI? Or is this an overkill?

best regards
Oliver

> Yes, if you can create installers, that would be wonderful!
> 
> I’ve seen about three different Mac OSX installers around so far.
> 
> Please don’t wait, create installers if you can, and write back here with
> instructions when you’ve done so.
> 
> Gj
> 
> On Wednesday, August 8, 2018, Carl Mosca  wrote:
> > I am wondering if anyone is working on these. I would like to help if
> > needed.

Re: Installers

[Carl Mosca]

OK but I probably should have been a little more specific about the
coordination part of my question.

I am assuming that building the installers would, at some point, be part of
the build process.

I believe Jenkins and ant are currently used.  Is there any history or
preference with solutions to create the installers I should be aware of?

Thank you,
Carl

On Fri, Aug 10, 2018 at 2:36 AM Geertjan Wielenga
 wrote:

> Yes, if you can create installers, that would be wonderful!
>
> I’ve seen about three different Mac OSX installers around so far.
>
> Please don’t wait, create installers if you can, and write back here with
> instructions when you’ve done so.
>
> Gj
>
> On Wednesday, August 8, 2018, Carl Mosca  wrote:
>
> > I am wondering if anyone is working on these. I would like to help if
> > needed.
> >
>


-- 
Carl J. Mosca

Re: Installers

[Geertjan Wielenga]

Which kinds of installers, i.e., for which operating systems, do you want
to create installers?

Indeed, makes sense to me the idea of them being created during the build.

Gj

On Friday, August 10, 2018, Carl Mosca  wrote:

> OK but I probably should have been a little more specific about the
> coordination part of my question.
>
> I am assuming that building the installers would, at some point, be part of
> the build process.
>
> I believe Jenkins and ant are currently used.  Is there any history or
> preference with solutions to create the installers I should be aware of?
>
> Thank you,
> Carl
>
> On Fri, Aug 10, 2018 at 2:36 AM Geertjan Wielenga
>  wrote:
>
> > Yes, if you can create installers, that would be wonderful!
> >
> > I’ve seen about three different Mac OSX installers around so far.
> >
> > Please don’t wait, create installers if you can, and write back here with
> > instructions when you’ve done so.
> >
> > Gj
> >
> > On Wednesday, August 8, 2018, Carl Mosca  wrote:
> >
> > > I am wondering if anyone is working on these. I would like to help if
> > > needed.
> > >
> >
>
>
> --
> Carl J. Mosca
>

Re: AW: Case sensitive in directory name it is a issue

[William Beebe]

And if that is the case it will also effect any Linux distribution.

On Fri, Aug 10, 2018 at 3:21 AM Piotr Hoppe  wrote:

> This issue occurs for:
>
> - NetBeans 9.0
>
> - PHP projects
>
> - Mac OS high Sierra 10.13.6 with case sensitive APFS partition.
>
>
> W dniu 10.08.2018 o 09:18, Christian Lenz pisze:
> > Which operating System do you have? For Windows, it is one Directory. If
> you have MyProjectFolder and myprojectfolder, it is the same.
> >
> >
> > Cheers
> >
> > Chris
> >
> > Von: Piotr Hoppe
> > Gesendet: Donnerstag, 9. August 2018 21:30
> > An: dev@netbeans.incubator.apache.org
> > Betreff: Case sensitive in directory name it is a issue
> >
> > When you have in the project two directories with the same name but one
> > of them uses lowercase letters and the second uses the uppercase letter,
> > for example backend and Backend, so these name are differ only size of
> > letters.
> > Then in the project tree you can see only one of this directories with
> > them content.
> >
> > In the project tree It should be visible both directories.
> >
> > Earlier, I have already reported a similar problem
> > https://netbeans.org/bugzilla/show_bug.cgi?id=268044
> >
> > This issue occurs in the NetBeans 9.0 when I works on the PHP projects.
> >
>
> --
> Piotr Hoppe
>
> Ta wiadomosc jest poufna i przeznaczona wylacznie dla adresata. Jesli
> jestes niezamierzonym odbiorca, to pilnie powiadom o tym nadawce. Nikomu
> nie ujawiaj tresci tej wiadomosci oraz nie uzywaj, nie kopiuj, nie
> drukuj, nie przechowuj, ani nie przekazuj dalej. Upewnij sie, ze zostala
> trwale usunieta. G-Forces Web Management Polska sp. z o.o.,
> 
> Ul. Trzy
> Lipy 3, 80-172 Gdańsk NIP: 583-292-04-23 REGON: 220105616 KRS: 246596
>

Re: Installers

[Carl Mosca]

Well first off is MacOS dmg because that's where I code mostly.  Secondly I
like the idea of both an RPM and a deb for those Linux distros but I get
the "yum install" "apt-get" thing to it's just as high a priority for me.

And yes, I know Windows has to be addressed a well but that's my order of
interest at this point.  On Windows, I would have to look because I don't
know what the msi/exe preference is these days.

Carl

On Fri, Aug 10, 2018 at 7:10 AM Geertjan Wielenga
 wrote:

> Which kinds of installers, i.e., for which operating systems, do you want
> to create installers?
>
> Indeed, makes sense to me the idea of them being created during the build.
>
> Gj
>
> On Friday, August 10, 2018, Carl Mosca  wrote:
>
> > OK but I probably should have been a little more specific about the
> > coordination part of my question.
> >
> > I am assuming that building the installers would, at some point, be part
> of
> > the build process.
> >
> > I believe Jenkins and ant are currently used.  Is there any history or
> > preference with solutions to create the installers I should be aware of?
> >
> > Thank you,
> > Carl
> >
> > On Fri, Aug 10, 2018 at 2:36 AM Geertjan Wielenga
> >  wrote:
> >
> > > Yes, if you can create installers, that would be wonderful!
> > >
> > > I’ve seen about three different Mac OSX installers around so far.
> > >
> > > Please don’t wait, create installers if you can, and write back here
> with
> > > instructions when you’ve done so.
> > >
> > > Gj
> > >
> > > On Wednesday, August 8, 2018, Carl Mosca  wrote:
> > >
> > > > I am wondering if anyone is working on these. I would like to help if
> > > > needed.
> > > >
> > >
> >
> >
> > --
> > Carl J. Mosca
> >
>


-- 
Carl J. Mosca

RE: AW: Case sensitive in directory name it is a issue

[Delfi Ramirez]

Hi all:

Case sensitive is  a mandatory directive in folders [ considered as 
Internationalized Resource Identifiers (IRIs) ] and or timestamps namespaces  
UUID URN Namespaces

https://www.ietf.org/rfc/rfc3987.txt

https://www.ietf.org/rfc/rfc4122.txt

may this be the issue? 

Delfi Ramirez

Segonquart Studio

https://segonquart.net

From: Piotr Hoppe
Sent: 10 August 2018 08:21
To: dev@netbeans.incubator.apache.org
Subject: Re: AW: Case sensitive in directory name it is a issue

This issue occurs for:

- NetBeans 9.0

- PHP projects

- Mac OS high Sierra 10.13.6 with case sensitive APFS partition.


W dniu 10.08.2018 o 09:18, Christian Lenz pisze:
> Which operating System do you have? For Windows, it is one Directory. If you 
> have MyProjectFolder and myprojectfolder, it is the same.
>
>
> Cheers
>
> Chris
>
> Von: Piotr Hoppe
> Gesendet: Donnerstag, 9. August 2018 21:30
> An: dev@netbeans.incubator.apache.org
> Betreff: Case sensitive in directory name it is a issue
>
> When you have in the project two directories with the same name but one
> of them uses lowercase letters and the second uses the uppercase letter,
> for example backend and Backend, so these name are differ only size of
> letters.
> Then in the project tree you can see only one of this directories with
> them content.
>
> In the project tree It should be visible both directories.
>
> Earlier, I have already reported a similar problem
> https://netbeans.org/bugzilla/show_bug.cgi?id=268044
>
> This issue occurs in the NetBeans 9.0 when I works on the PHP projects.
>

-- 
Piotr Hoppe

Ta wiadomosc jest poufna i przeznaczona wylacznie dla adresata. Jesli 
jestes niezamierzonym odbiorca, to pilnie powiadom o tym nadawce. Nikomu 
nie ujawiaj tresci tej wiadomosci oraz nie uzywaj, nie kopiuj, nie 
drukuj, nie przechowuj, ani nie przekazuj dalej. Upewnij sie, ze zostala 
trwale usunieta. G-Forces Web Management Polska sp. z o.o., Ul. Trzy 
Lipy 3, 80-172 Gdańsk NIP: 583-292-04-23 REGON: 220105616 KRS: 246596