Re: IDE release

[Emilian Bold]

There is no such 'resolution'. nb-javac is the only module important enough to 
have a first-run/jit installer and we have received a go-ahead from LEGAL. The 
go-ahead was *not* for all (L)GPL modules we might also have in the current 
codebase.

The goal, imho, it to have a public NetBeans installer with Java 9 support for 
our users, preferably in 2017. In order to accomplish that, cutting arbitrary 
secondary modules/features seems an acceptable tradeoff.

The java cluster depends on the ide cluster which has a *lot* of modules. Most 
of those are not necessary to make a Java IDE with Java 9, Maven, etc.

--emi


> Original Message 
>Subject: Re: IDE release
>Local Time: November 23, 2017 8:21 PM
>UTC Time: November 23, 2017 6:21 PM
>From: mblaes...@doppel-helix.eu
>To: dev@netbeans.incubator.apache.org
>
>Hey,
>
> Am Donnerstag, den 23.11.2017, 07:52 -0500 schrieb Emilian Bold:
>>You can make a fine Java IDE with Java 9 support even if you have no
>> MySQL connector out of the box or other secondary features which
>> would need more work otherwise.
>>
>> I disagree. The resolution is to remove the mysql connector and add a
>> JIRA issue to track the development of an "jit" installer.
>>
>> Removing the driver is trivial and if the module needs a justification,
>> there are other databases, that offer nicer licenses.
>>
>> If we now start to cut arbitrary modules, we begin to discuss the color
>> of the bike shed.
>>
>> Greetings
>>
>> Matthias
>

[GitHub] steffendietz commented on issue #279: [NETBEANS-162] Restore autoupdate.services tests

[GitBox]

steffendietz commented on issue #279: [NETBEANS-162] Restore 
autoupdate.services tests
URL: 
https://github.com/apache/incubator-netbeans/pull/279#issuecomment-346710961
 
 
   I revisited point 1 from [above](#issuecomment-346595065). I'm now using the 
correct method of providing an executable file list by using the 
`nbm.executable.files` property.
   
   I also opened a JIRA issue regarding this change, but couldn't link it on 
the Confluence page.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Hibernate and Apache NetBeans

[Sven Reimers]

Hi,

1. the friend entries are not a problem, but I think long term we should
have better official API's instead of making everyone a friend.

(anecdotal reference -> http://hg.netbeans.org/main-silver/rev/0144a346f983)

2. Seems ok for me.

Sven

On Tue, Nov 21, 2017 at 11:43 PM, John McDonnell 
wrote:

> Hi,
>
> I like the idea of an external GitHub that we can use to quickly fire
> in some of the troublesome modules into to get around the license
> issues like Camel did, and it seems there's already a GitHub
> Organisation lying there in wait for modules ;)
>
> Just did a quick search for usages of "hibernate" in the repository,
> and got a couple of questions.
>
> 1. Alot of modules in the project.xml have a friend-packages element with:
> org.netbeans.modules.hibernate
>
> I assume even if this "friend" module doesn't exist in the IDE it
> shouldn't affect the module, correct?
>
> 2. The j2ee.persistence module has references to icons from the
> hibernate package, provided there Oracles images, and not Hibernate, I
> assume we could just move the icon and reference, no?
>
> private static final String HB_MAPPING_ICON =
> "org/netbeans/modules/hibernate/resources/hibernate-mapping.png";
> //NOI18N
>
>
> A lot of the other references are references to hibernate in text,
> again from a quick search I don't fully know how or what their being
> used for, I assume unless someone with intimate knowledge of this area
> speaks up, we'll probably have to get down there and dig around...
>
> If I get time over the next few days / next week, I might see about
> removing references to the Hibernate modules locally and seeing what
> breaks in relation to the JPA / Persistence Units etc stuff in the UI.
> - maybe see if there are any 8.2 NetCat test specs for this to use as
> an acceptance test...
>
>
>
> Regards
>
> John
>
>
>
> On 21 November 2017 at 22:17, Jan Lahoda  wrote:
> > Hi Sven,
> >
> > Thanks for looking at this. For completeness, I think (but IANAL) we
> could
> > have code here that depends on Hibernate (or other GPL libraries), but it
> > a) needs to be an optional component; b) we cannot distribute the GPL
> > library from Apache:
> > https://www.apache.org/legal/resolved.html#optional
> >
> > if it makes more sense for the hibernate support to be distributed
> disabled
> > with the IDE (so the user would only install the library if desired) or
> > separately is a question, but I personally know almost nothing about it,
> so
> > I don't have an opinion on that.
> >
> > Jan
> >
> >
> > On Tue, Nov 21, 2017 at 10:45 PM, Sven Reimers 
> > wrote:
> >
> >> Hi all,
> >>
> >> Jan just asked about a couple of problematic external libraries - one of
> >> them is hibernate.
> >>
> >> Looking at the rules I think we cannot distribute modules relying on
> >> Hibernate with Apache NetBeans.
> >>
> >> So I did a quick dive and found a major problem. At the moment there is
> a
> >> special support module for Hibernate (supporting stuff like HQL..). I
> think
> >> we have to get rid of that (still have to check for further modules
> >> depending on this module). This is the only module using "import
> >> org.hibernate.*" statements.
> >>
> >> Idea: Maybe we can move the Hibernate Support module over to another
> >> community place so the code does not get lost and we can try to release
> a
> >> plugin from there - how about that? Not sure what the correct process
> and
> >> correct licensing for this module would be..
> >>
> >> I found this http://camel.apache.org/hibernate.html and
> >> https://github.com/camel-extra/camel-extra/tree/master/
> >> components/camel-hibernate
> >> as an example of another Apache project not being able to use LGPL
> >> components at Apache.
> >>
> >> There is https://github.com/netbeans-community - some distant time in
> the
> >> past Florian and I thought this may be a good place to bundle community
> >> efforts around NetBeans - maybe we could use this now?
> >>
> >> Comments?
> >>
> >> -Sven
> >>
> >> P.S. I think if we get the JavaEE part this will be much harder - I
> assume
> >> some of the JPA magic will rely on use of Hibernate - we will have to
> >> switch this over to OpenJPA or EclipseLink (both should be good in
> terms of
> >> license - I think...)
> >>
>



-- 
Sven Reimers

* Senior Expert Software Architect
* Java Champion
* NetBeans Dream Team Member: http://dreamteam.netbeans.org
* Community Leader  NetBeans: http://community.java.net/netbeans
  Desktop Java:
http://community.java.net/javadesktop
* JUG Leader JUG Bodensee: http://www.jug-bodensee.de
* Duke's Choice Award Winner 2009

* XING: https://www.xing.com/profile/Sven_Reimers8
* LinkedIn: http://www.linkedin.com/in/svenreimers

[GitHub] junichi11 commented on issue #290: Add .gitattributes file to repo

[GitBox]

junichi11 commented on issue #290: Add .gitattributes file to repo
URL: 
https://github.com/apache/incubator-netbeans/pull/290#issuecomment-346710178
 
 
   It's nice. `.form` ?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] geertjanw commented on issue #271: [NETBEANS-54] excluding specific files, e.g., licenses via Rat

[GitBox]

geertjanw commented on issue #271: [NETBEANS-54] excluding specific files, 
e.g., licenses via Rat
URL: 
https://github.com/apache/incubator-netbeans/pull/271#issuecomment-346706801
 
 
   Thank you! :-)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] jlahoda opened a new pull request #291: Ability to depend on JDK modules

[GitBox]

jlahoda opened a new pull request #291: Ability to depend on JDK modules
URL: https://github.com/apache/incubator-netbeans/pull/291
 
 
   This is a work-in-progress patch, mostly for discussion, not intended to be 
merged as is.
   
   The goal here is to allow NetBeans modules (modules in the NetBeans Module 
System) depend on JDK modules. As a result dependencies on JDK modules are much 
more precise. Some more information is here:
   
https://cwiki.apache.org/confluence/display/NETBEANS/JDK+Modules+Support+in+NetBeans+Module+System
   
   There are 3 commits in this request, the middle one " Automatically adding 
JDK module dependencies to existing modules." is mechanically generated, based 
on jdeps output for the given module.
   
   Feedback is welcome.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] lbruun commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

lbruun commented on issue #289: [NETBEANS-126] Replace with trademark free icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346685560
 
 
   @matthiasblaesing 
   Excellent links. I think it would be wonderful if this was the case. And is 
also what I've always thought myself. The whole _fair use_ thing. This is why I 
started out with suggesting 
[PR251](https://github.com/apache/incubator-netbeans/pull/251) but perhaps it 
went haywire because I said "please validate assumption before merging" in the 
request or perhaps it went haywire because I opened LEGAL-343 and because we 
don't get a response. (I suspect ASF legal are volunteers like the rest of us)
   
   I still don't understand why Oracle chose to remove exactly these icons - 
out of literally hundreds of icons in the NetBeans code base. Why?  I don't 
think they removed them because of problems with the art-work license, because 
then they would have removed the generic icon from the same folder too.
   
   How to move on?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] lbruun commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

lbruun commented on issue #289: [NETBEANS-126] Replace with trademark free icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346685560
 
 
   @matthiasblaesing 
   Excellent links. I think it would be wonderful if this was the case. And is 
also what I've always thought myself. The whole _fair use_ thing. This is why I 
started out with suggesting 
[PR251](https://github.com/apache/incubator-netbeans/pull/251) but perhaps it 
went haywire because I said "please validate assumption before merging" in the 
request or perhaps it went haywire because I opened LEGAL-343 and because we 
don't get a response. (I suspect ASF legal are volunteers like the rest of us)
   
   I still don't understand why Oracle chose to remove exactly these - out of 
literally hundreds of icons in the NetBeans code base. Why?  I don't think they 
removed them because of problems with the art-work license, because then they 
would have removed the generic icon from the same folder too.
   
   How to move on?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] asfgit closed pull request #271: [NETBEANS-54] excluding specific files, e.g., licenses via Rat

[GitBox]

asfgit closed pull request #271: [NETBEANS-54] excluding specific files, e.g., 
licenses via Rat
URL: https://github.com/apache/incubator-netbeans/pull/271
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/nbbuild/build.xml b/nbbuild/build.xml
index 5a0c39c84..1d7f74287 100644
--- a/nbbuild/build.xml
+++ b/nbbuild/build.xml
@@ -2032,6 +2032,7 @@ It is possible to use -Ddebug.port=3234 -Ddebug.pause=y 
to start the system in d
  
  
  
+ 
  
  
  
@@ -2060,6 +2061,7 @@ It is possible to use -Ddebug.port=3234 -Ddebug.pause=y 
to start the system in d
  
  

  
+ 
  
  

  
@@ -2077,8 +2079,10 @@ It is possible to use -Ddebug.port=3234 -Ddebug.pause=y 
to start the system in d
  
  
  
+ 

  

  
+ 
  
  
  
@@ -2093,6 +2097,7 @@ It is possible to use -Ddebug.port=3234 -Ddebug.pause=y 
to start the system in d
  
  
  
+ 
  
  
  
@@ -2139,6 +2144,7 @@ It is possible to use -Ddebug.port=3234 -Ddebug.pause=y 
to start the system in d
  
  
  
+ 
  

  
  


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] neilcsmith-net commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

neilcsmith-net commented on issue #289: [NETBEANS-126] Replace with trademark 
free icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346684354
 
 
   @geertjanw is there any documentation of how the icons ended up in the 
NetBeans source tree in the first place and where they came from (ie. where the 
copyright lies)?
   
   @matthiasblaesing sounds reasonable, and I assume if Oracle didn't request 
permission before, the way this was done previously.  So, if that's the case, 
it's not as mentioned in the legal issue ticket a case-by-case thing, but 
something where I presume we'd still want a blanket OK from legal on when and 
where trademark fair-use is allowed in an Apache project? One to ask [mentors]? 
Must have come up before, surely!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] matthiasblaesing commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

matthiasblaesing commented on issue #289: [NETBEANS-126] Replace with trademark 
free icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346683201
 
 
   I see two distinct problems we need to solve:
   1. Copyright: Are we allowed to use artwork and
   2. Trademarks: Are we allowed to use a "symbol" and "name"
   
   I read some more and (I'm not a lawyer and I know that quoting from 
wikipedia is questionable):
   
   https://en.wikipedia.org/wiki/Fair_use_(U.S._trademark_law)
   
   > A nonowner may also use a trademark nominatively?to refer to the actual 
trademarked product or its source. In addition to protecting product criticism 
and analysis, United States law actually encourages nominative usage by 
competitors in the form of comparative advertising.
   
   Some more, that might better hold up:
   
   
https://www.inta.org/TrademarkBasics/FactSheets/Pages/Fair-Use-of-TrademarksNL.aspx
   
   > Nominative fair use generally is permissible as long as (1) the product or 
service in question is not readily identifiable without use of the trademark, 
(2) only so much of the mark as is reasonably necessary to identify the product 
or service is used and (3) use of the mark does not suggest sponsorship or 
endorsement by the trademark owner. 
   
   My reading: The trademark part would be ok, as it is the intention to refer 
to the product itself and it is required to be quickly recognizable.
   
   The remaining thing is copyright: We don't know where the icons come from. 
They were distributed with netbeans, but they could be distributed with the 
source as "fair use". So I could live with just readding the icons (#251) or 
taking the icons from another source under a compatible license.
   
   **Edit:** I would then close the legal ticket.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Xmas IDE Release Plan Proposal (was Re: Kanban / Scrum / Boards)

[Jan Lahoda]

Hi,

On Thu, Nov 23, 2017 at 7:03 PM, Antonio  wrote:

> Hi all,
>
> For the "2017 Xmas NetBeans Java 9 IDE" (long name? right date?) I think
> we could have the following Kanban stages in an IDE specific Kanban board.
>

I suspect the timing may be about right (I doubt we can plan for a much
sooner release).


>
> I think we could think of these as an empowered version of the old
> NetBeans' bugzilla "plan" and "umbrella" keywords that have been used over
> the years, but with a visual interface (as in [1]).
>
> For the IDE we could set up a Kanban board with the following stages, for
> example:
>
> 0. Find all offenders
> I think Jan Lahoda has done a great job detecting offending licensed
> modules (Hibernate, Beans Binding, etc.). But, are there any others? Maybe
> our first stage could be to identify which are the offenders. After all we
> wouldn't want to find offenders later on and start all over again.
>

I think "ant verify-libs-and-licenses" is the tool for this. It will
(should) report binaries without licenses; malformed files with licenses,
GPL dependencies (with exceptions). If we find a problem, we should at
least try to add a check for it to this task, so that the checks run for us
automatically.

(See also:
https://github.com/apache/incubator-netbeans/pull/285
)

Jan


> 1. Evaluate the damage
> Do a second "dependency analysys" phase, where we determine what the
> dependencies are with Hibernate, Beans Binding and other offending modules.
> Evaluate the damage among us. This could contain one or more issues (one
> issue for hibernate dependencies, another for beans binding, etc.).
>
> 2. Get rid of offenders
> We could then think about trimming the "ide" cluster as Emilian suggested
> in another email. Offending modules could be set up somewhere else at
> github, with some plugin download URL. Issues here could be "cluster
> trimming", "github setup", "github move", and "create plugin url to
> download offending modules". Is this just one stage or two?
>
> 3. Prepare the website (specific Kanban board for this?)
> We could then start preparing the website. Wade Chandler has done a superb
> job and we have 1.5Gb of web pages to classify and organize in sections.
> This is so huge that I think we'll need a specific board for this to get
> done. Just classifying the web site into sections seems dauntling to me
> (tutorials/arch.xml links/javadoc/branding...).
>
> 4. Prepare the IDE release.
> Build the resulting cluster and start with tests and QA Testing.
>
> 5. Xmas party
>
> I assume we can add/remove stages and fine tune the board as we move
> along. Opinions? Ideas?
>
> Cheers,
> Antonio
>
> [1] https://docs.microsoft.com/en-us/vsts/work/kanban/add-columns
>
> P.S.:
>
> Some time in the future we could use Kanban boards for documenting/running
> existing NetBeans workflows.
>
> The workflow described at http://wiki.netbeans.org/APIDevelopment
> describes what was required to submit a new NetBeans module. I find these
> workflows very valuable because they have worked well over the years, and I
> wouldn't like losing these in the transition.
>
>
> El 23/11/17 a las 18:19, John McDonnell escribió:
>
>> Very easy to create, I think the catch here will be making sure
>> tickets are marked with a label or something and we only include those
>> labelled items.
>>
>>
>> Regards
>>
>> John
>>
>> On 23 November 2017 at 17:13, Antonio  wrote:
>>
>>> What about a "NetBeans 2017 Java 9 IDE" board we can use for releasing
>>> the
>>> Java IDE by Xmas?
>>>
>>> Cheers,
>>> Antonio
>>>
>>> El 23/11/17 a las 18:10, John McDonnell escribió:
>>>
>>> It's very slow to load...

 Probably due to the number of sections.  What we might do is setup a
 Kanban board per cluster maybe and have then smaller groups in each
 board if that improves the performance of the board...

 On 23 November 2017 at 17:02, Antonio  wrote:

>
> Hi John,
>
> This is great news! I'll take an in-dept look later on. It seems to me
> the
> page is very slow, isn't it? Or is it just me?
>
> Thanks,
> Antonio
>
> El 23/11/17 a las 17:25, John McDonnell escribió:
>
> So the Kanban board is now visible here to all:
>>
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>
>> I still need to kick off the change in ticket types with the Infra
>> team, in order to enable epics.
>>
>> Regards
>>
>> John
>>
>> On 18 November 2017 at 08:24, Antonio  wrote:
>>
>>>
>>>
>>> So I played the "find the differences" game at [1] and I think that
>>> this
>>> holds:
>>>
>>> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
>>> (documentation,
>>> task, Sub-task).
>>>
>>> I don't know the differences between "Task" and "Technical task",
>>> maybe
>>> we
>>> can go 

[GitHub] neilcsmith-net commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

neilcsmith-net commented on issue #289: [NETBEANS-126] Replace with trademark 
free icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346679539
 
 
   @Chris2011 why would you use FontAwesome or another icon font as SVG? Swing 
can use icon fonts directly - came up on discussion in dev mailing list a while 
ago, and @emilianbold was experimenting with this (pinged for thoughts). Of 
course, that might be a discussion for another time (retina, etc.) since they 
don't solve the direct trademark issue anyway.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: IDE release

[Matthias Bläsing]

Hey,

Am Donnerstag, den 23.11.2017, 07:52 -0500 schrieb Emilian Bold:
> You can make a fine Java IDE with Java 9 support even if you have no
> MySQL connector out of the box or other secondary features which
> would need more work otherwise.

I disagree. The resolution is to remove the mysql connector and add a
JIRA issue to track the development of an "jit" installer.

Removing the driver is trivial and if the module needs a justification,
there are other databases, that offer nicer licenses.

If we now start to cut arbitrary modules, we begin to discuss the color
of the bike shed.

Greetings

Matthias

Xmas IDE Release Plan Proposal (was Re: Kanban / Scrum / Boards)

[Antonio]

Hi all,

For the "2017 Xmas NetBeans Java 9 IDE" (long name? right date?) I think 
we could have the following Kanban stages in an IDE specific Kanban board.


I think we could think of these as an empowered version of the old 
NetBeans' bugzilla "plan" and "umbrella" keywords that have been used 
over the years, but with a visual interface (as in [1]).


For the IDE we could set up a Kanban board with the following stages, 
for example:


0. Find all offenders
I think Jan Lahoda has done a great job detecting offending licensed 
modules (Hibernate, Beans Binding, etc.). But, are there any others? 
Maybe our first stage could be to identify which are the offenders. 
After all we wouldn't want to find offenders later on and start all over 
again.


1. Evaluate the damage
Do a second "dependency analysys" phase, where we determine what the 
dependencies are with Hibernate, Beans Binding and other offending 
modules. Evaluate the damage among us. This could contain one or more 
issues (one issue for hibernate dependencies, another for beans binding, 
etc.).


2. Get rid of offenders
We could then think about trimming the "ide" cluster as Emilian 
suggested in another email. Offending modules could be set up somewhere 
else at github, with some plugin download URL. Issues here could be 
"cluster trimming", "github setup", "github move", and "create plugin 
url to download offending modules". Is this just one stage or two?


3. Prepare the website (specific Kanban board for this?)
We could then start preparing the website. Wade Chandler has done a 
superb job and we have 1.5Gb of web pages to classify and organize in 
sections. This is so huge that I think we'll need a specific board for 
this to get done. Just classifying the web site into sections seems 
dauntling to me (tutorials/arch.xml links/javadoc/branding...).


4. Prepare the IDE release.
Build the resulting cluster and start with tests and QA Testing.

5. Xmas party

I assume we can add/remove stages and fine tune the board as we move 
along. Opinions? Ideas?


Cheers,
Antonio

[1] https://docs.microsoft.com/en-us/vsts/work/kanban/add-columns

P.S.:

Some time in the future we could use Kanban boards for 
documenting/running existing NetBeans workflows.


The workflow described at http://wiki.netbeans.org/APIDevelopment 
describes what was required to submit a new NetBeans module. I find 
these workflows very valuable because they have worked well over the 
years, and I wouldn't like losing these in the transition.



El 23/11/17 a las 18:19, John McDonnell escribió:

Very easy to create, I think the catch here will be making sure
tickets are marked with a label or something and we only include those
labelled items.


Regards

John

On 23 November 2017 at 17:13, Antonio  wrote:

What about a "NetBeans 2017 Java 9 IDE" board we can use for releasing the
Java IDE by Xmas?

Cheers,
Antonio

El 23/11/17 a las 18:10, John McDonnell escribió:


It's very slow to load...

Probably due to the number of sections.  What we might do is setup a
Kanban board per cluster maybe and have then smaller groups in each
board if that improves the performance of the board...

On 23 November 2017 at 17:02, Antonio  wrote:


Hi John,

This is great news! I'll take an in-dept look later on. It seems to me
the
page is very slow, isn't it? Or is it just me?

Thanks,
Antonio

El 23/11/17 a las 17:25, John McDonnell escribió:


So the Kanban board is now visible here to all:

https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216

I still need to kick off the change in ticket types with the Infra
team, in order to enable epics.

Regards

John

On 18 November 2017 at 08:24, Antonio  wrote:



So I played the "find the differences" game at [1] and I think that
this
holds:

"Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
(documentation,
task, Sub-task).

I don't know the differences between "Task" and "Technical task", maybe
we
can go with the simplest one, the "Agile Scrum Issue Type" and decide
whether a task is "Technical" or not by adding a prefix in the task
name.

So +1 for the "Agile Scrum Issue Type".

Cheers,
Antonio

[1]
Find the differences game:

https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes



On 17/11/17 17:46, John McDonnell wrote:




Had a quick look before I created the INFRA ticket, and it seems that
there are 4 possible settings for Apache's JIRA:



https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes

We're currently on the top left, 'Apache Default Issue Type Scheme'
When we raise a ticket, we should probably know which scheme we want
to go with going forward.  The 'Agile Scrum Issue Type Scheme' seems
logical to me, but I'm just one person.

Anyone see any need for any of the other schemes?

Regards

John

On 17 November 2017 at 08:45, John McDonnell

wrote:




Hi Wade,

While I wait for the INFRA 

Re: IDE release

[Neil C Smith]

On Thu, Nov 23, 2017 at 12:53 PM Emilian Bold 
wrote:

> I don't have any code yet but the idea is simple: just start excluding
> whole modules from the ide/java cluster.
>

Would a j2se / j2ee cluster split handle all the problems?  Would that be
pulling too much out of a first release?

Best wishes,

Neil
-- 
Neil C Smith
Artist & Technologist
www.neilcsmith.net

Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org

Re: Kanban / Scrum / Boards

[John McDonnell]

Very easy to create, I think the catch here will be making sure
tickets are marked with a label or something and we only include those
labelled items.


Regards

John

On 23 November 2017 at 17:13, Antonio  wrote:
> What about a "NetBeans 2017 Java 9 IDE" board we can use for releasing the
> Java IDE by Xmas?
>
> Cheers,
> Antonio
>
> El 23/11/17 a las 18:10, John McDonnell escribió:
>
>> It's very slow to load...
>>
>> Probably due to the number of sections.  What we might do is setup a
>> Kanban board per cluster maybe and have then smaller groups in each
>> board if that improves the performance of the board...
>>
>> On 23 November 2017 at 17:02, Antonio  wrote:
>>>
>>> Hi John,
>>>
>>> This is great news! I'll take an in-dept look later on. It seems to me
>>> the
>>> page is very slow, isn't it? Or is it just me?
>>>
>>> Thanks,
>>> Antonio
>>>
>>> El 23/11/17 a las 17:25, John McDonnell escribió:
>>>
 So the Kanban board is now visible here to all:

 https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216

 I still need to kick off the change in ticket types with the Infra
 team, in order to enable epics.

 Regards

 John

 On 18 November 2017 at 08:24, Antonio  wrote:
>
>
> So I played the "find the differences" game at [1] and I think that
> this
> holds:
>
> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
> (documentation,
> task, Sub-task).
>
> I don't know the differences between "Task" and "Technical task", maybe
> we
> can go with the simplest one, the "Agile Scrum Issue Type" and decide
> whether a task is "Technical" or not by adding a prefix in the task
> name.
>
> So +1 for the "Agile Scrum Issue Type".
>
> Cheers,
> Antonio
>
> [1]
> Find the differences game:
>
> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>
>
>
> On 17/11/17 17:46, John McDonnell wrote:
>>
>>
>>
>> Had a quick look before I created the INFRA ticket, and it seems that
>> there are 4 possible settings for Apache's JIRA:
>>
>>
>>
>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>
>> We're currently on the top left, 'Apache Default Issue Type Scheme'
>> When we raise a ticket, we should probably know which scheme we want
>> to go with going forward.  The 'Agile Scrum Issue Type Scheme' seems
>> logical to me, but I'm just one person.
>>
>> Anyone see any need for any of the other schemes?
>>
>> Regards
>>
>> John
>>
>> On 17 November 2017 at 08:45, John McDonnell
>> 
>> wrote:
>>>
>>>
>>>
>>> Hi Wade,
>>>
>>> While I wait for the INFRA ticket to be looked at, I've added you to
>>> the board's admin list, so I believe you should be able to see it
>>> now.
>>> I've created swimlanes for all top-level components that came from
>>> BugZilla.
>>>
>>> As for epics, I've not seen this listed in the admin portal, seems we
>>> are using an 'Apache Default Issue Type Scheme', which allows for
>>> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
>>> created.  I assume this might require an INFRA ticket as well?
>>>
>>> Regards
>>>
>>> John
>>>
>>> On 17 November 2017 at 04:00, Wade Chandler 
>>> wrote:



 +1 for Kanban



> On Nov 16, 2017, at 17:07, John McDonnell
> 
> wrote:
>
> I created a basic Kanban board there to get a starting point, I’ll
> look
> to clean it up next week.
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>
> 
>
> I’ll also need to make it visible to others, since its restricted
> at
> the moment - Think this needs an INFRA ticket…
>
> Regards
>
> John
>
>> On 16 Nov 2017, at 20:05, Antonio  wrote:
>>
>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in
>> Apache Mesos?
>>
>> Maybe the icon/splash/about dialog set of issues is a small
>> project
>> we
>> could use to give Jira's boards a spin.
>>
>> Cheers,
>> Antonio
>>
>> [1]
>>
>> - Apache Mesos Kanban
>>
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>
>> - Apache Mesos Sprint 68
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62

Re: Kanban / Scrum / Boards

[Antonio]

What about a "NetBeans 2017 Java 9 IDE" board we can use for releasing 
the Java IDE by Xmas?


Cheers,
Antonio

El 23/11/17 a las 18:10, John McDonnell escribió:

It's very slow to load...

Probably due to the number of sections.  What we might do is setup a
Kanban board per cluster maybe and have then smaller groups in each
board if that improves the performance of the board...

On 23 November 2017 at 17:02, Antonio  wrote:

Hi John,

This is great news! I'll take an in-dept look later on. It seems to me the
page is very slow, isn't it? Or is it just me?

Thanks,
Antonio

El 23/11/17 a las 17:25, John McDonnell escribió:


So the Kanban board is now visible here to all:

https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216

I still need to kick off the change in ticket types with the Infra
team, in order to enable epics.

Regards

John

On 18 November 2017 at 08:24, Antonio  wrote:


So I played the "find the differences" game at [1] and I think that this
holds:

"Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
(documentation,
task, Sub-task).

I don't know the differences between "Task" and "Technical task", maybe
we
can go with the simplest one, the "Agile Scrum Issue Type" and decide
whether a task is "Technical" or not by adding a prefix in the task name.

So +1 for the "Agile Scrum Issue Type".

Cheers,
Antonio

[1]
Find the differences game:
https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes



On 17/11/17 17:46, John McDonnell wrote:



Had a quick look before I created the INFRA ticket, and it seems that
there are 4 possible settings for Apache's JIRA:


https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes

We're currently on the top left, 'Apache Default Issue Type Scheme'
When we raise a ticket, we should probably know which scheme we want
to go with going forward.  The 'Agile Scrum Issue Type Scheme' seems
logical to me, but I'm just one person.

Anyone see any need for any of the other schemes?

Regards

John

On 17 November 2017 at 08:45, John McDonnell 
wrote:



Hi Wade,

While I wait for the INFRA ticket to be looked at, I've added you to
the board's admin list, so I believe you should be able to see it now.
I've created swimlanes for all top-level components that came from
BugZilla.

As for epics, I've not seen this listed in the admin portal, seems we
are using an 'Apache Default Issue Type Scheme', which allows for
Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
created.  I assume this might require an INFRA ticket as well?

Regards

John

On 17 November 2017 at 04:00, Wade Chandler 
wrote:



+1 for Kanban




On Nov 16, 2017, at 17:07, John McDonnell 
wrote:

I created a basic Kanban board there to get a starting point, I’ll
look
to clean it up next week.

https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216


I’ll also need to make it visible to others, since its restricted at
the moment - Think this needs an INFRA ticket…

Regards

John


On 16 Nov 2017, at 20:05, Antonio  wrote:

Do we want to try out Jira's Kanban/Scrum boards like these [1] in
Apache Mesos?

Maybe the icon/splash/about dialog set of issues is a small project
we
could use to give Jira's boards a spin.

Cheers,
Antonio

[1]

- Apache Mesos Kanban
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111

- Apache Mesos Sprint 68
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62

Re: Kanban / Scrum / Boards

[John McDonnell]

It's very slow to load...

Probably due to the number of sections.  What we might do is setup a
Kanban board per cluster maybe and have then smaller groups in each
board if that improves the performance of the board...

On 23 November 2017 at 17:02, Antonio  wrote:
> Hi John,
>
> This is great news! I'll take an in-dept look later on. It seems to me the
> page is very slow, isn't it? Or is it just me?
>
> Thanks,
> Antonio
>
> El 23/11/17 a las 17:25, John McDonnell escribió:
>
>> So the Kanban board is now visible here to all:
>>
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>
>> I still need to kick off the change in ticket types with the Infra
>> team, in order to enable epics.
>>
>> Regards
>>
>> John
>>
>> On 18 November 2017 at 08:24, Antonio  wrote:
>>>
>>> So I played the "find the differences" game at [1] and I think that this
>>> holds:
>>>
>>> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
>>> (documentation,
>>> task, Sub-task).
>>>
>>> I don't know the differences between "Task" and "Technical task", maybe
>>> we
>>> can go with the simplest one, the "Agile Scrum Issue Type" and decide
>>> whether a task is "Technical" or not by adding a prefix in the task name.
>>>
>>> So +1 for the "Agile Scrum Issue Type".
>>>
>>> Cheers,
>>> Antonio
>>>
>>> [1]
>>> Find the differences game:
>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>>
>>>
>>>
>>> On 17/11/17 17:46, John McDonnell wrote:


 Had a quick look before I created the INFRA ticket, and it seems that
 there are 4 possible settings for Apache's JIRA:


 https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes

 We're currently on the top left, 'Apache Default Issue Type Scheme'
 When we raise a ticket, we should probably know which scheme we want
 to go with going forward.  The 'Agile Scrum Issue Type Scheme' seems
 logical to me, but I'm just one person.

 Anyone see any need for any of the other schemes?

 Regards

 John

 On 17 November 2017 at 08:45, John McDonnell 
 wrote:
>
>
> Hi Wade,
>
> While I wait for the INFRA ticket to be looked at, I've added you to
> the board's admin list, so I believe you should be able to see it now.
> I've created swimlanes for all top-level components that came from
> BugZilla.
>
> As for epics, I've not seen this listed in the admin portal, seems we
> are using an 'Apache Default Issue Type Scheme', which allows for
> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
> created.  I assume this might require an INFRA ticket as well?
>
> Regards
>
> John
>
> On 17 November 2017 at 04:00, Wade Chandler 
> wrote:
>>
>>
>> +1 for Kanban
>>
>>
>>
>>> On Nov 16, 2017, at 17:07, John McDonnell 
>>> wrote:
>>>
>>> I created a basic Kanban board there to get a starting point, I’ll
>>> look
>>> to clean it up next week.
>>>
>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>> 
>>>
>>> I’ll also need to make it visible to others, since its restricted at
>>> the moment - Think this needs an INFRA ticket…
>>>
>>> Regards
>>>
>>> John
>>>
 On 16 Nov 2017, at 20:05, Antonio  wrote:

 Do we want to try out Jira's Kanban/Scrum boards like these [1] in
 Apache Mesos?

 Maybe the icon/splash/about dialog set of issues is a small project
 we
 could use to give Jira's boards a spin.

 Cheers,
 Antonio

 [1]

 - Apache Mesos Kanban
 https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111

 - Apache Mesos Sprint 68
 https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>>>
>>>
>>>
>>
>>>
>

Re: Kanban / Scrum / Boards

[Antonio]

Hi John,

This is great news! I'll take an in-dept look later on. It seems to me 
the page is very slow, isn't it? Or is it just me?


Thanks,
Antonio

El 23/11/17 a las 17:25, John McDonnell escribió:

So the Kanban board is now visible here to all:

https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216

I still need to kick off the change in ticket types with the Infra
team, in order to enable epics.

Regards

John

On 18 November 2017 at 08:24, Antonio  wrote:

So I played the "find the differences" game at [1] and I think that this
holds:

"Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" + (documentation,
task, Sub-task).

I don't know the differences between "Task" and "Technical task", maybe we
can go with the simplest one, the "Agile Scrum Issue Type" and decide
whether a task is "Technical" or not by adding a prefix in the task name.

So +1 for the "Agile Scrum Issue Type".

Cheers,
Antonio

[1]
Find the differences game:
https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes



On 17/11/17 17:46, John McDonnell wrote:


Had a quick look before I created the INFRA ticket, and it seems that
there are 4 possible settings for Apache's JIRA:

https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes

We're currently on the top left, 'Apache Default Issue Type Scheme'
When we raise a ticket, we should probably know which scheme we want
to go with going forward.  The 'Agile Scrum Issue Type Scheme' seems
logical to me, but I'm just one person.

Anyone see any need for any of the other schemes?

Regards

John

On 17 November 2017 at 08:45, John McDonnell 
wrote:


Hi Wade,

While I wait for the INFRA ticket to be looked at, I've added you to
the board's admin list, so I believe you should be able to see it now.
I've created swimlanes for all top-level components that came from
BugZilla.

As for epics, I've not seen this listed in the admin portal, seems we
are using an 'Apache Default Issue Type Scheme', which allows for
Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
created.  I assume this might require an INFRA ticket as well?

Regards

John

On 17 November 2017 at 04:00, Wade Chandler 
wrote:


+1 for Kanban




On Nov 16, 2017, at 17:07, John McDonnell 
wrote:

I created a basic Kanban board there to get a starting point, I’ll look
to clean it up next week.

https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216


I’ll also need to make it visible to others, since its restricted at
the moment - Think this needs an INFRA ticket…

Regards

John


On 16 Nov 2017, at 20:05, Antonio  wrote:

Do we want to try out Jira's Kanban/Scrum boards like these [1] in
Apache Mesos?

Maybe the icon/splash/about dialog set of issues is a small project we
could use to give Jira's boards a spin.

Cheers,
Antonio

[1]

- Apache Mesos Kanban
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111

- Apache Mesos Sprint 68
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62

Re: instantiate the evt object of KeyEvent Class

[Antonio]

Hi Eyad,

These sort of questions are best answered in the user mailing list 
(us...@netbeans.incubator.apache.org). I've sent your email there, 
please respond in that list.


Java has something called the "AWT Event Thread", which is an internal 
thread that is automatically started by Java for you.


When you click a button, or move the mouse, this "AWT Event Thread" 
(internal to Java) creates some Java objects called "Events" which 
contain information about what was clicked, or which is the position of 
the mouse in the screen.


So the answer to your question is "The Event objects are created for you 
by the Java AWT Event Thread", and "The Event objects are sent to the 
listeners you specify.


For more information about events see "Writing Event Listeners" at 
https://docs.oracle.com/javase/tutorial/uiswing/events/index.html


Hope this helps,
Antonio


El 23/11/17 a las 17:06, Eyad Khalel escribió:

May someone explain me this issue in netbeans (java) : I can't find the
code which *instantiate* the *evt* object of KeyEvent Class in the
following java code which is generated by netbeans :

textPrice.addKeyListener(new java.awt.event.KeyAdapter() {
 public void keyTyped(java.awt.event.KeyEvent evt) {
 textPriceKeyTyped(evt);
 }
 });

Where can I find the source code that instantiate the *evt* object of the
KeyEvent class?

Can we call *evt* methods without instantiating it like the code below?

  private void textPriceKeyTyped(java.awt.event.KeyEvent evt) {
 // TODO add your handling code here:
 char c = evt.getKeyChar();
 if(!(Character.isDigit(c) )||(c==KeyEvent.VK_BACKSPACE) ||
(c==KeyEvent.VK_DELETE)){
 getToolkit().beep();
 evt.consume();

 }}

Thanks

instantiate the evt object of KeyEvent Class

[Eyad Khalel]

May someone explain me this issue in netbeans (java) : I can't find the
code which *instantiate* the *evt* object of KeyEvent Class in the
following java code which is generated by netbeans :

textPrice.addKeyListener(new java.awt.event.KeyAdapter() {
public void keyTyped(java.awt.event.KeyEvent evt) {
textPriceKeyTyped(evt);
}
});

Where can I find the source code that instantiate the *evt* object of the
KeyEvent class?

Can we call *evt* methods without instantiating it like the code below?

 private void textPriceKeyTyped(java.awt.event.KeyEvent evt) {
// TODO add your handling code here:
char c = evt.getKeyChar();
if(!(Character.isDigit(c) )||(c==KeyEvent.VK_BACKSPACE) ||
(c==KeyEvent.VK_DELETE)){
getToolkit().beep();
evt.consume();

}}

Thanks

Re: Kanban / Scrum / Boards

[John McDonnell]

So the Kanban board is now visible here to all:

https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216

I still need to kick off the change in ticket types with the Infra
team, in order to enable epics.

Regards

John

On 18 November 2017 at 08:24, Antonio  wrote:
> So I played the "find the differences" game at [1] and I think that this
> holds:
>
> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" + (documentation,
> task, Sub-task).
>
> I don't know the differences between "Task" and "Technical task", maybe we
> can go with the simplest one, the "Agile Scrum Issue Type" and decide
> whether a task is "Technical" or not by adding a prefix in the task name.
>
> So +1 for the "Agile Scrum Issue Type".
>
> Cheers,
> Antonio
>
> [1]
> Find the differences game:
> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>
>
>
> On 17/11/17 17:46, John McDonnell wrote:
>>
>> Had a quick look before I created the INFRA ticket, and it seems that
>> there are 4 possible settings for Apache's JIRA:
>>
>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>
>> We're currently on the top left, 'Apache Default Issue Type Scheme'
>> When we raise a ticket, we should probably know which scheme we want
>> to go with going forward.  The 'Agile Scrum Issue Type Scheme' seems
>> logical to me, but I'm just one person.
>>
>> Anyone see any need for any of the other schemes?
>>
>> Regards
>>
>> John
>>
>> On 17 November 2017 at 08:45, John McDonnell 
>> wrote:
>>>
>>> Hi Wade,
>>>
>>> While I wait for the INFRA ticket to be looked at, I've added you to
>>> the board's admin list, so I believe you should be able to see it now.
>>> I've created swimlanes for all top-level components that came from
>>> BugZilla.
>>>
>>> As for epics, I've not seen this listed in the admin portal, seems we
>>> are using an 'Apache Default Issue Type Scheme', which allows for
>>> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
>>> created.  I assume this might require an INFRA ticket as well?
>>>
>>> Regards
>>>
>>> John
>>>
>>> On 17 November 2017 at 04:00, Wade Chandler 
>>> wrote:

 +1 for Kanban



> On Nov 16, 2017, at 17:07, John McDonnell 
> wrote:
>
> I created a basic Kanban board there to get a starting point, I’ll look
> to clean it up next week.
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
> 
>
> I’ll also need to make it visible to others, since its restricted at
> the moment - Think this needs an INFRA ticket…
>
> Regards
>
> John
>
>> On 16 Nov 2017, at 20:05, Antonio  wrote:
>>
>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in
>> Apache Mesos?
>>
>> Maybe the icon/splash/about dialog set of issues is a small project we
>> could use to give Jira's boards a spin.
>>
>> Cheers,
>> Antonio
>>
>> [1]
>>
>> - Apache Mesos Kanban
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>
>> - Apache Mesos Sprint 68
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>
>

>

[GitHub] lbruun commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

lbruun commented on issue #289: [NETBEANS-126] Replace with trademark free icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346610061
 
 
   @Chris2011.  How would these icons that you propose be any better (from an 
AFS legal point of view) than the icons that were in NetBeans 8.2? , the ones 
that Oracle removed from the donation. Those icons were also "free". Again: The 
problem is _not_ the license of the art-work. 
   
   The problem is that we cannot use a trademarked logo (in whatever form) 
until we get an ok in 
[LEGAL-343](https://issues.apache.org/jira/browse/LEGAL-343). Until then we 
have to use something which for sure is acceptable meaning until then we err on 
the side of caution, legally.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Could Oracle donate the beansbinding library too?

[Fabrizio Giudici]

On Thu, 23 Nov 2017 15:06:43 +0100, Emilian Bold  
 wrote:



This is a very old library from java.net, it's becoming hard even to  
find traces of it. See eg:  
https://web.archive.org/web/20070618134019/https://beansbinding.dev.java.net/


When it was dismissed, I forked it and worked on it, but only for a short  
time - because JavaFX2 came with its own binding stuff and then I moved to  
it. In any case, just for the record, you can find it here:


https://bitbucket.org/tidalwave/betterbeansbinding-src/

Googling for "BetterBeansBinding" you'll find some forks here and there by  
people that maintained it (I don't know whether they are doing it still  
now, or gave up at some time).


Of course, the problem with the licensing still holds, because I couldn't  
do but keeping the original LGPL.


--
Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
"We make Java work. Everywhere."
http://tidalwave.it/fabrizio/blog - fabrizio.giud...@tidalwave.it

[GitHub] lbruun commented on issue #264: Check whether line endings are LF with Travis CI

[GitBox]

lbruun commented on issue #264: Check whether line endings are LF with Travis CI
URL: 
https://github.com/apache/incubator-netbeans/pull/264#issuecomment-346633726
 
 
   @junichi11 
   I think we should monitor if this works or not. As far as I can tell the 
check relies on Git's ability to predict if a certain file is to be considered 
a text file or not. There may be some text files where we actually find it ok 
for them to use CRLF.  Files of type `.rc` comes to mind. These are Windows 
resource scripts and have no relevance outside of Windows. Just an example.
   
   I've now proposed 
[PR290](https://github.com/apache/incubator-netbeans/pull/290). These two PRs 
will complement each other.
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Ending the @netbeans.org mailing lists.

[Bertrand Delacretaz]

Hi,

On Thu, Nov 23, 2017 at 3:03 PM, Ate Douma  wrote:
> ...Please add wording that users migrating to the users@ or dev@ list should
> *subscribe* to those lists by sending an empty email to
> users-subscr...@netbeans.apache.org or dev-subscr...@netbeans.apache.org
> otherwise we (moderators) will get swamped...

IMO all that information on mailing lists should be under
http://netbeans.apache.org/ at a permanent URL.

See http://sling.apache.org/project-information.html#mailing-lists for
an example, though there's room for improvement there, like what Ate
mentions about using lists.a.o for browsing.

-Bertrand

Could Oracle donate the beansbinding library too?

[Emilian Bold]

Hello,

o.jdesktop.beansbinding is used by various Swing panels and by the form editor 
to provide some very nice binding features.

Sadly, it is LGPL 2.1: 
https://github.com/JFormDesigner/swing-beansbinding/blob/master/beansbinding/license.txt

I don't know if there is another drop-in comparable library.

Still, this is a library created by Sun Microsystems as a reference 
implementation for JSR 295.

It would be ideal if Oracle would just donate the beansbinding code to Apache 
NetBeans and we release it under Apache 2.0 ourselves.

This is a very old library from java.net, it's becoming hard even to find 
traces of it. See eg: 
https://web.archive.org/web/20070618134019/https://beansbinding.dev.java.net/

--emi

Re: Ending the @netbeans.org mailing lists.

[Ate Douma]

Please add wording that users migrating to the users@ or dev@ list 
should *subscribe* to those lists by sending an empty email to

users-subscr...@netbeans.apache.org or dev-subscr...@netbeans.apache.org
otherwise we (moderators) will get swamped...
Maybe also helpful to remark that you can anonymously browse the mail
archives via https://lists.apache.org/list.html?us...@netbeans.apache.org
and https://lists.apache.org/list.html?d...@netbeans.apache.org

All this typically is/should be documented already on the website, but
as we don't have any real (ASF) content yet at netbeans.apache.org new
users easily will get lost.

I think the website really needs to get priority attention, also because
otherwise there is no place to communicate and provide the download
links for the current HTML/Java API and upcoming platform releases...

Ate

On 2017-11-23 12:06, Geertjan Wielenga wrote:

Hi all,

We should, at some stage, put an end to the various netbeans.org mailing
lists, e.g., nbus...@netbeans.org and the dozen or so other netbeans.org
mailing lists and ensure that everyone asks questions about NetBeans on the
Apache NetBeans mailing lists instead. Jiri Kovalsky and I, who have
managed the NetBeans.org mailing lists over the years, propose we send the
following to ALL the netbeans.org mailing lists at the beginning of next
week.

Subject for the mail: “January 1st, 2018: End of @netbeans.org Mailing

Lists and Forum"

Text:

“If you’ve been following Oracle's Apache NetBeans donation process,
you’ll be aware that a large part of NetBeans is in Apache Git already. You
should also be aware that mailing lists are available at Apache for
purposes of discussing the development and usage of Apache NetBeans.

By means of this e-mail, we’re letting you know that as of January 1st,
2018, the @netbeans.org mailing lists will be deleted (they are archived
at netbeans.markmail.org), all references to @netbeans.org will, where
possible, be replaced with references to Apache NetBeans mailing lists, and
everyone will need to manually move to the Apache NetBeans @dev (
dev@netbeans.incubator.apache.org) and Apache NetBeans @user (
us...@netbeans.incubator.apache.org) mailing lists.




Anyone asking questions about the usage of NetBeans, whether for Java,
JavaScript, C/C++, or any other language or technology, as well as those
using the NetBeans APIs for developing modules and applications, will use
the Apache NetBeans @user mailing list. If and when it turns out that too
many developers of one category dominate the @user mailing list, a separate
Apache NetBeans mailing list will be created for them. The Apache NetBeans
@dev mailing list is specifically for those committed to working on the
development of Apache NetBeans itself, as well as those committed to
promoting and documenting it, via events and tutorials, etc.

Note that we will be discontinuing the web forums, i.e.,
forums.netbeans.org, and that in Apache there is no replacement for that
— Apache projects work with mailing lists only.

Hoping to see you all on the Apache NetBeans mailing lists, you’re
encouraged to move there as soon as possible and to not write to the @
netbeans.org mailing lists anymore.

Kind regards,

Geertjan & Jirka




Feedback/comments welcome. We'd like to send the above to all the @
netbeans.org mailing lists at the beginning of next week.

Thanks,

Gj and Jirka

RE: Ending the @netbeans.org mailing lists.

[Eric Barboni]

Hi, +1

Maybe we can tell to put a prefix tag in subjet like the NetCat one.

Regards
 
-Message d'origine-
De : Geertjan Wielenga [mailto:geertjan.wiele...@googlemail.com] 
Envoyé : jeudi 23 novembre 2017 12:06
À : dev@netbeans.incubator.apache.org
Objet : Ending the @netbeans.org mailing lists.

Hi all,

We should, at some stage, put an end to the various netbeans.org mailing lists, 
e.g., nbus...@netbeans.org and the dozen or so other netbeans.org mailing lists 
and ensure that everyone asks questions about NetBeans on the Apache NetBeans 
mailing lists instead. Jiri Kovalsky and I, who have managed the NetBeans.org 
mailing lists over the years, propose we send the following to ALL the 
netbeans.org mailing lists at the beginning of next week.

Subject for the mail: “January 1st, 2018: End of @netbeans.org Mailing
> Lists and Forum"
>
> Text:
>
> “If you’ve been following Oracle's Apache NetBeans donation process, 
> you’ll be aware that a large part of NetBeans is in Apache Git 
> already. You should also be aware that mailing lists are available at 
> Apache for purposes of discussing the development and usage of Apache 
> NetBeans.
>
> By means of this e-mail, we’re letting you know that as of January 
> 1st, 2018, the @netbeans.org mailing lists will be deleted (they are 
> archived at netbeans.markmail.org), all references to @netbeans.org 
> will, where possible, be replaced with references to Apache NetBeans 
> mailing lists, and everyone will need to manually move to the Apache 
> NetBeans @dev (
> dev@netbeans.incubator.apache.org) and Apache NetBeans @user (
> us...@netbeans.incubator.apache.org) mailing lists.


> Anyone asking questions about the usage of NetBeans, whether for Java, 
> JavaScript, C/C++, or any other language or technology, as well as 
> those using the NetBeans APIs for developing modules and applications, 
> will use the Apache NetBeans @user mailing list. If and when it turns 
> out that too many developers of one category dominate the @user 
> mailing list, a separate Apache NetBeans mailing list will be created 
> for them. The Apache NetBeans @dev mailing list is specifically for 
> those committed to working on the development of Apache NetBeans 
> itself, as well as those committed to promoting and documenting it, via 
> events and tutorials, etc.
>
> Note that we will be discontinuing the web forums, i.e., 
> forums.netbeans.org, and that in Apache there is no replacement for 
> that — Apache projects work with mailing lists only.
>
> Hoping to see you all on the Apache NetBeans mailing lists, you’re 
> encouraged to move there as soon as possible and to not write to the @ 
> netbeans.org mailing lists anymore.
>
> Kind regards,
>
> Geertjan & Jirka
>


Feedback/comments welcome. We'd like to send the above to all the @ 
netbeans.org mailing lists at the beginning of next week.

Thanks,

Gj and Jirka

Re: IDE release

[Geertjan Wielenga]

I agree with that.

Gj

On Thu, Nov 23, 2017 at 1:52 PM, Emilian Bold 
wrote:

> I don't have any code yet but the idea is simple: just start excluding
> whole modules from the ide/java cluster.
>
> You can make a fine Java IDE with Java 9 support even if you have no MySQL
> connector out of the box or other secondary features which would need more
> work otherwise.
>
> --emi
>
> > Original Message 
> >Subject: Re: IDE release
> >Local Time: November 23, 2017 2:50 PM
> >UTC Time: November 23, 2017 12:50 PM
> >From: geertjan.wiele...@googlemail.com
> >To: dev@netbeans.incubator.apache.org, Emilian Bold <
> emilian.b...@protonmail.ch>
> >
> >On Thu, Nov 23, 2017 at 1:48 PM, Emilian Bold emilian.b...@protonmail.ch
> > wrote:
> >>My point was that a cluster reorganization would help us release in 2017.
> >>
> >
> >What would that reorganization look like and do feel free to submit a PR
> > for evaluation.
> >
> > Gj
> >
> >
> >
> >
> >>--emi
> >>> Original Message 
> >>> Subject: Re: IDE release
> >>> Local Time: November 23, 2017 7:50 AM
> >>> UTC Time: November 23, 2017 5:50 AM
> >>> From: anto...@vieiro.net
> >>> To: dev@netbeans.incubator.apache.org
> >>>Hi all,
> >>>Some comments inlined below
> >>>El 22/11/17 a las 23:26, Emilian Bold escribió:
> A NetBeans release supporting Java 9 seems of utmost importance in
> 2017.
> Fully agree. I'm not sure 2017 is feasible, though.
> Initially we could just carve-out the pieces we can't ship. It's
>  unfortunate but not a roadblock for a Java developer not to have
> Hibernate
>  tooling or a MySQL connector in NetBeans. In time we can move those to
>  separate community (ie. non-Apache) plugins.
> >
> Definitely: I'd prefer starting as small as possible, and grow upon
> that
> >>> (and see how strong we are now during the process).
> >>>Regarding IDE modules, and as a wise man once said: "Either use an
> >>> Apache compatible license, adopt it, or get out of the way as a plugin
> >>> module(s) somewhere at github".
> I remember we had an open discussion with the Hibernate folks about
>  relicensing some DTDs. Are we also using JARs from Hibernate?
> >Maybe we should look into the way our clusters are grouped. I don't
> see
>  why the Java editor would have any kind of dependency on db.drivers.
> >We could make a tinyide cluster and put less modules in there and have
>  the java cluster depend on tinyide and extide.
> >I'm not sure cluster reorganization is feasible if we want to release
> in
>  2017. If cluster reorganization is the way to go then maybe the sooner
>  the better.
> But we may want to do that later on, and try to take JDK modules into
> >>> account. Clusters could be organized to require as less JDK modules as
> >>> possible. I'd love to see a "tiny platform cluster" run on top of
> >>> java.base only.
> >>>Un abrazo,
> >>> Antonio
> --emi
>  ​
> > Original Message 
> > Subject: IDE release
> > Local Time: November 21, 2017 10:30 PM
> > UTC Time: November 21, 2017 8:30 PM
> > From: lah...@gmail.com
> > To: dev@netbeans.incubator.apache.org
> > Hi,
> > I assume we should work on getting the code into a state where we
> could
> > release a (beta) of (Java) IDE. When the platform/alpha is released,
> > I'll
> >>change the release job:
> >https://builds.apache.org/view/Incubator Projects/job/incubator-
> > netbeans-release/
> >>to build the IDE (I'll let it build platform separately as well) and
> run
> > the appropriate tests, including "ant verify-libs-and-licenses"
> (which
> > checks that every external binary has a license file, and that the
> > license
> >>file passes some basic checks). I ran verify-libs-and-licenses
> > manually,
> >>and there is (unsurprisingly) a lot of failures. I fixed a few here:
> >https://github.com/apache/incubator-netbeans/pull/285
> > Among other problems there are several (L)GPL libraries we will need
> to
> > solve somehow besides javac:
> > db.drivers/external/mysql-connector-java-5.1.23-license.txt
> > hibernate4lib/external/hibernate-4.3.1-lib-license.txt
> > libs.jshell.compile/external/nb-jshell-license.txt
> > (presumably compile-time only at this time)
> > o.jdesktop.beansbinding/external/beansbinding-1.2.1-license.txt
> > My question is whether someone would be willing to work on the GPL
> > libraries (I personally know very little about the db+hibernate
> ones);
> > or
> >>on cleaning up the verify-and-licenses (I don't think this is big
> > enough to
> >>enter the violations into a wiki, but there's quite a few of them, so
> > it
> >>will take some time to clean them up).
> > (When verify-libs-and-licenses is clean, we need to look at
> DEPENDENCIES
> > and fix any problems we spot, but I don't think it 

Re: IDE release

[Emilian Bold]

I don't have any code yet but the idea is simple: just start excluding whole 
modules from the ide/java cluster.

You can make a fine Java IDE with Java 9 support even if you have no MySQL 
connector out of the box or other secondary features which would need more work 
otherwise.

--emi

> Original Message 
>Subject: Re: IDE release
>Local Time: November 23, 2017 2:50 PM
>UTC Time: November 23, 2017 12:50 PM
>From: geertjan.wiele...@googlemail.com
>To: dev@netbeans.incubator.apache.org, Emilian Bold 
>
>
>On Thu, Nov 23, 2017 at 1:48 PM, Emilian Bold emilian.b...@protonmail.ch
> wrote:
>>My point was that a cluster reorganization would help us release in 2017.
>>
>
>What would that reorganization look like and do feel free to submit a PR
> for evaluation.
>
> Gj
>
>
>
>
>>--emi
>>> Original Message 
>>> Subject: Re: IDE release
>>> Local Time: November 23, 2017 7:50 AM
>>> UTC Time: November 23, 2017 5:50 AM
>>> From: anto...@vieiro.net
>>> To: dev@netbeans.incubator.apache.org
>>>Hi all,
>>>Some comments inlined below
>>>El 22/11/17 a las 23:26, Emilian Bold escribió:
A NetBeans release supporting Java 9 seems of utmost importance in 2017.
Fully agree. I'm not sure 2017 is feasible, though.
Initially we could just carve-out the pieces we can't ship. It's
 unfortunate but not a roadblock for a Java developer not to have Hibernate
 tooling or a MySQL connector in NetBeans. In time we can move those to
 separate community (ie. non-Apache) plugins.
>
Definitely: I'd prefer starting as small as possible, and grow upon that
>>> (and see how strong we are now during the process).
>>>Regarding IDE modules, and as a wise man once said: "Either use an
>>> Apache compatible license, adopt it, or get out of the way as a plugin
>>> module(s) somewhere at github".
I remember we had an open discussion with the Hibernate folks about
 relicensing some DTDs. Are we also using JARs from Hibernate?
>Maybe we should look into the way our clusters are grouped. I don't see
 why the Java editor would have any kind of dependency on db.drivers.
>We could make a tinyide cluster and put less modules in there and have
 the java cluster depend on tinyide and extide.
>I'm not sure cluster reorganization is feasible if we want to release in
 2017. If cluster reorganization is the way to go then maybe the sooner
 the better.
But we may want to do that later on, and try to take JDK modules into
>>> account. Clusters could be organized to require as less JDK modules as
>>> possible. I'd love to see a "tiny platform cluster" run on top of
>>> java.base only.
>>>Un abrazo,
>>> Antonio
--emi
 ​
> Original Message 
> Subject: IDE release
> Local Time: November 21, 2017 10:30 PM
> UTC Time: November 21, 2017 8:30 PM
> From: lah...@gmail.com
> To: dev@netbeans.incubator.apache.org
> Hi,
> I assume we should work on getting the code into a state where we could
> release a (beta) of (Java) IDE. When the platform/alpha is released,
> I'll
>>change the release job:
>https://builds.apache.org/view/Incubator Projects/job/incubator-
> netbeans-release/
>>to build the IDE (I'll let it build platform separately as well) and run
> the appropriate tests, including "ant verify-libs-and-licenses" (which
> checks that every external binary has a license file, and that the
> license
>>file passes some basic checks). I ran verify-libs-and-licenses
> manually,
>>and there is (unsurprisingly) a lot of failures. I fixed a few here:
>https://github.com/apache/incubator-netbeans/pull/285
> Among other problems there are several (L)GPL libraries we will need to
> solve somehow besides javac:
> db.drivers/external/mysql-connector-java-5.1.23-license.txt
> hibernate4lib/external/hibernate-4.3.1-lib-license.txt
> libs.jshell.compile/external/nb-jshell-license.txt
> (presumably compile-time only at this time)
> o.jdesktop.beansbinding/external/beansbinding-1.2.1-license.txt
> My question is whether someone would be willing to work on the GPL
> libraries (I personally know very little about the db+hibernate ones);
> or
>>on cleaning up the verify-and-licenses (I don't think this is big
> enough to
>>enter the violations into a wiki, but there's quite a few of them, so
> it
>>will take some time to clean them up).
> (When verify-libs-and-licenses is clean, we need to look at DEPENDENCIES
> and fix any problems we spot, but I don't think it makes much sense to
> look
>>at that when there are significant verify-libs-and-licenses failures.)
> Thanks,
> Jan
>

[GitHub] Chris2011 commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

Chris2011 commented on issue #289: [NETBEANS-126] Replace with trademark free 
icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346610604
 
 
   I didn't get that point, I thought there is a problem, because of the 
license for the icons from oracle or smth like that.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: IDE release

[Geertjan Wielenga]

On Thu, Nov 23, 2017 at 1:48 PM, Emilian Bold 
wrote:

> My point was that a cluster reorganization would help us release in 2017.
>


What would that reorganization look like and do feel free to submit a PR
for evaluation.

Gj





>
> --emi
>
> > Original Message 
> >Subject: Re: IDE release
> >Local Time: November 23, 2017 7:50 AM
> >UTC Time: November 23, 2017 5:50 AM
> >From: anto...@vieiro.net
> >To: dev@netbeans.incubator.apache.org
> >
> >Hi all,
> >
> > Some comments inlined below
> >
> > El 22/11/17 a las 23:26, Emilian Bold escribió:
> >>A NetBeans release supporting Java 9 seems of utmost importance in 2017.
> >>
> >Fully agree. I'm not sure 2017 is feasible, though.
> >>Initially we could just carve-out the pieces we can't ship. It's
> unfortunate but not a roadblock for a Java developer not to have Hibernate
> tooling or a MySQL connector in NetBeans. In time we can move those to
> separate community (ie. non-Apache) plugins.
> >>
> >Definitely: I'd prefer starting as small as possible, and grow upon that
> > (and see how strong we are now during the process).
> >
> > Regarding IDE modules, and as a wise man once said: "Either use an
> > Apache compatible license, adopt it, or get out of the way as a plugin
> > module(s) somewhere at github".
> >
> >>I remember we had an open discussion with the Hibernate folks about
> relicensing some DTDs. Are we also using JARs from Hibernate?
> >>Maybe we should look into the way our clusters are grouped. I don't see
> why the Java editor would have any kind of dependency on db.drivers.
> >>We could make a tinyide cluster and put less modules in there and have
> the java cluster depend on tinyide and extide.
> >>
> >> I'm not sure cluster reorganization is feasible if we want to release in
> >>2017. If cluster reorganization is the way to go then maybe the sooner
> > the better.
> >
> > But we may want to do that later on, and try to take JDK modules into
> > account. Clusters could be organized to require as less JDK modules as
> > possible. I'd love to see a "tiny platform cluster" run on top of
> > java.base only.
> >
> > Un abrazo,
> > Antonio
> >
> >>--emi
> >> ​
> >>> Original Message 
> >>> Subject: IDE release
> >>> Local Time: November 21, 2017 10:30 PM
> >>> UTC Time: November 21, 2017 8:30 PM
> >>> From: lah...@gmail.com
> >>> To: dev@netbeans.incubator.apache.org
> >>>Hi,
> >>>I assume we should work on getting the code into a state where we could
> >>> release a (beta) of (Java) IDE. When the platform/alpha is released,
> I'll
> >>> change the release job:
> >>>https://builds.apache.org/view/Incubator Projects/job/incubator-
> netbeans-release/
> >>>to build the IDE (I'll let it build platform separately as well) and run
> >>> the appropriate tests, including "ant verify-libs-and-licenses" (which
> >>> checks that every external binary has a license file, and that the
> license
> >>> file passes some basic checks). I ran verify-libs-and-licenses
> manually,
> >>> and there is (unsurprisingly) a lot of failures. I fixed a few here:
> >>>https://github.com/apache/incubator-netbeans/pull/285
> >>>Among other problems there are several (L)GPL libraries we will need to
> >>> solve somehow besides javac:
> >>> db.drivers/external/mysql-connector-java-5.1.23-license.txt
> >>> hibernate4lib/external/hibernate-4.3.1-lib-license.txt
> >>> libs.jshell.compile/external/nb-jshell-license.txt
> >>> (presumably compile-time only at this time)
> >>> o.jdesktop.beansbinding/external/beansbinding-1.2.1-license.txt
> >>>My question is whether someone would be willing to work on the GPL
> >>> libraries (I personally know very little about the db+hibernate ones);
> or
> >>> on cleaning up the verify-and-licenses (I don't think this is big
> enough to
> >>> enter the violations into a wiki, but there's quite a few of them, so
> it
> >>> will take some time to clean them up).
> >>>(When verify-libs-and-licenses is clean, we need to look at DEPENDENCIES
> >>> and fix any problems we spot, but I don't think it makes much sense to
> look
> >>> at that when there are significant verify-libs-and-licenses failures.)
> >>>Thanks,
> >>> Jan
> >
>

[GitHub] lbruun commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

lbruun commented on issue #289: [NETBEANS-126] Replace with trademark free icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346610061
 
 
   @Chris2011.  How would these icons that you propose be any better (from an 
AFS legal point of view) than the icons that were in NetBeans 8.2? , the ones 
that Oracle removed from the donation. Those icons were also "free". Again: The 
problem is _not_ the license of the art-work. 
   
   The problem is that we cannot use a trademarked logo (in whatever form) 
until we get an ok in 
[LEGAL-343](https://issues.apache.org/jira/browse/LEGAL-343). Until then we 
have to use something which for sure is acceptable meaning until then we err on 
the side of cation, legally.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] geertjanw commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

geertjanw commented on issue #289: [NETBEANS-126] Replace with trademark free 
icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346599227
 
 
   OK, try them, submit a pull request. Until then, I propose we accept this 
pull request.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] Chris2011 commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

Chris2011 commented on issue #289: [NETBEANS-126] Replace with trademark free 
icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346599047
 
 
   Yeah but we can use SVG files, convert it to PNG and use them. I found a lot 
when I search for: https://www.google.de/search?q=free+browser+icon. Of course, 
not everything can be used but I think some, like this: 
https://dribbble.com/shots/1545132-Free-Flat-Browser-Icons maybe?
   
   So he said, you can use it for free and commercial use. I don't know the 
license problems there but why can't we try those icons?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] steffendietz commented on issue #279: Restore autoupdate.services tests

[GitBox]

steffendietz commented on issue #279: Restore autoupdate.services tests
URL: 
https://github.com/apache/incubator-netbeans/pull/279#issuecomment-346595065
 
 
   The tests were fixed by only reverse engineering the missing assets and the 
use
   cases they try to simulate. So I'm pretty confident that this is fine for 
now.
   
   However, two of the cases could probably need a more subject-specific 
review, although
   it could also happen after the merge, by opening a "reminder" ticket of 
sorts.
   
   1. The `ExecutablePermissionsTest` checks if there is a `bin` directory with 
an
   executable `start.sh` in the user directory, after installing the 
`executable-permissions` NBM. 
   
   I'm currently using an installer in the NBM to create this file and make 
it executable.
   While this works, I'm not sure if this quite captures the essence of the 
test, or
   if it tries to verify some NBM specific behavior, like specifying an 
executable file
   in the manifest. (I could not find anything about this, that's why I went 
with the installer.)
   
   2. The `UpdateUnitFactoryTest.testGroupInstalledAndUpdates` test checks 
whether one of the installed modules has an update available in the 
`test-updates-provider` created in the test.
   
The problem I had here is, that there is no test module installed at 
this point, only real
   modules, with correct specification versions. I couldn't think of a clean 
way to always provide
   an update, if the specification version of the installed modules could 
*someday* exceed
   the version available in the static update provider.
   
   I still haven't figured this out, but I'm now providing an update with 
an absurdly
   high specification version, as mentioned [above](#issuecomment-346498142).
   
   Besides these minor gripes I have, everything should be fine. ? 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Ending the @netbeans.org mailing lists.

[Fabrizio Giudici]

On Thu, 23 Nov 2017 12:17:47 +0100, Delfi Ramirez  
 wrote:



+1


+1

--
Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
"We make Java work. Everywhere."
http://tidalwave.it/fabrizio/blog - fabrizio.giud...@tidalwave.it

Re: Ending the @netbeans.org mailing lists.

[Delfi Ramirez]

+1


On 23/11/2017 12:06, Geertjan Wielenga wrote:

Hi all,

We should, at some stage, put an end to the various netbeans.org mailing
lists, e.g., nbus...@netbeans.org and the dozen or so other netbeans.org
mailing lists and ensure that everyone asks questions about NetBeans on the
Apache NetBeans mailing lists instead. Jiri Kovalsky and I, who have
managed the NetBeans.org mailing lists over the years, propose we send the
following to ALL the netbeans.org mailing lists at the beginning of next
week.

Subject for the mail: “January 1st, 2018: End of @netbeans.org Mailing

Lists and Forum"

Text:

“If you’ve been following Oracle's Apache NetBeans donation process,
you’ll be aware that a large part of NetBeans is in Apache Git already. You
should also be aware that mailing lists are available at Apache for
purposes of discussing the development and usage of Apache NetBeans.

By means of this e-mail, we’re letting you know that as of January 1st,
2018, the @netbeans.org mailing lists will be deleted (they are archived
at netbeans.markmail.org), all references to @netbeans.org will, where
possible, be replaced with references to Apache NetBeans mailing lists, and
everyone will need to manually move to the Apache NetBeans @dev (
dev@netbeans.incubator.apache.org) and Apache NetBeans @user (
us...@netbeans.incubator.apache.org) mailing lists.



Anyone asking questions about the usage of NetBeans, whether for Java,
JavaScript, C/C++, or any other language or technology, as well as those
using the NetBeans APIs for developing modules and applications, will use
the Apache NetBeans @user mailing list. If and when it turns out that too
many developers of one category dominate the @user mailing list, a separate
Apache NetBeans mailing list will be created for them. The Apache NetBeans
@dev mailing list is specifically for those committed to working on the
development of Apache NetBeans itself, as well as those committed to
promoting and documenting it, via events and tutorials, etc.

Note that we will be discontinuing the web forums, i.e.,
forums.netbeans.org, and that in Apache there is no replacement for that
— Apache projects work with mailing lists only.

Hoping to see you all on the Apache NetBeans mailing lists, you’re
encouraged to move there as soon as possible and to not write to the @
netbeans.org mailing lists anymore.

Kind regards,

Geertjan & Jirka



Feedback/comments welcome. We'd like to send the above to all the @
netbeans.org mailing lists at the beginning of next week.

Thanks,

Gj and Jirka






smime.p7s
Description: S/MIME Cryptographic Signature

Ending the @netbeans.org mailing lists.

[Geertjan Wielenga]

Hi all,

We should, at some stage, put an end to the various netbeans.org mailing
lists, e.g., nbus...@netbeans.org and the dozen or so other netbeans.org
mailing lists and ensure that everyone asks questions about NetBeans on the
Apache NetBeans mailing lists instead. Jiri Kovalsky and I, who have
managed the NetBeans.org mailing lists over the years, propose we send the
following to ALL the netbeans.org mailing lists at the beginning of next
week.

Subject for the mail: “January 1st, 2018: End of @netbeans.org Mailing
> Lists and Forum"
>
> Text:
>
> “If you’ve been following Oracle's Apache NetBeans donation process,
> you’ll be aware that a large part of NetBeans is in Apache Git already. You
> should also be aware that mailing lists are available at Apache for
> purposes of discussing the development and usage of Apache NetBeans.
>
> By means of this e-mail, we’re letting you know that as of January 1st,
> 2018, the @netbeans.org mailing lists will be deleted (they are archived
> at netbeans.markmail.org), all references to @netbeans.org will, where
> possible, be replaced with references to Apache NetBeans mailing lists, and
> everyone will need to manually move to the Apache NetBeans @dev (
> dev@netbeans.incubator.apache.org) and Apache NetBeans @user (
> us...@netbeans.incubator.apache.org) mailing lists.


> Anyone asking questions about the usage of NetBeans, whether for Java,
> JavaScript, C/C++, or any other language or technology, as well as those
> using the NetBeans APIs for developing modules and applications, will use
> the Apache NetBeans @user mailing list. If and when it turns out that too
> many developers of one category dominate the @user mailing list, a separate
> Apache NetBeans mailing list will be created for them. The Apache NetBeans
> @dev mailing list is specifically for those committed to working on the
> development of Apache NetBeans itself, as well as those committed to
> promoting and documenting it, via events and tutorials, etc.
>
> Note that we will be discontinuing the web forums, i.e.,
> forums.netbeans.org, and that in Apache there is no replacement for that
> — Apache projects work with mailing lists only.
>
> Hoping to see you all on the Apache NetBeans mailing lists, you’re
> encouraged to move there as soon as possible and to not write to the @
> netbeans.org mailing lists anymore.
>
> Kind regards,
>
> Geertjan & Jirka
>


Feedback/comments welcome. We'd like to send the above to all the @
netbeans.org mailing lists at the beginning of next week.

Thanks,

Gj and Jirka

[GitHub] geertjanw commented on issue #271: [NETBEANS-54] excluding specific files, e.g., licenses via Rat

[GitBox]

geertjanw commented on issue #271: [NETBEANS-54] excluding specific files, 
e.g., licenses via Rat
URL: 
https://github.com/apache/incubator-netbeans/pull/271#issuecomment-346583435
 
 
   OK, I'll use that to pull this into my tree, but does anything from here 
need to be pushed to Apache NetBeans Git? Sorry, it's getting too complex for 
me in this PR, if there's a way you can commit this, that would be great.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] geertjanw commented on issue #279: Restore autoupdate.services tests

[GitBox]

geertjanw commented on issue #279: Restore autoupdate.services tests
URL: 
https://github.com/apache/incubator-netbeans/pull/279#issuecomment-346583127
 
 
   Great, thanks for your work on this. Is there any specific part of this that 
needs more review than another part, i.e., or are you very confident that this 
is all good?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] lbruun commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

lbruun commented on issue #289: [NETBEANS-126] Replace with trademark free icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346582847
 
 
   @Chris2011 Java Swing doesn't support SVG. As for using some other icons:   
If we choose something which for sure isn't trademarked then by definition it 
won't look like the real brand icon, i.e. user will not instantly recognize it 
representing e.g. Safari. In other words it defeats the purpose. The legal 
question here is not what art-work of say a Safari logo we can use (there are 
lots to choose from and there are many which have a license compatible with 
Apache). Nope, the question is - as I understand it - if we can distribute with 
the release something which is a trademarked logo.  So the question is if we 
can use the Safari logo itself, not which icon suite to get it from.  (Safari 
used here as an example)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] geertjanw commented on issue #288: Fix the license header template for NetBeans modules

[GitBox]

geertjanw commented on issue #288: Fix the license header template for NetBeans 
modules
URL: 
https://github.com/apache/incubator-netbeans/pull/288#issuecomment-346582812
 
 
   +1 looks good.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] geertjanw commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

geertjanw commented on issue #289: [NETBEANS-126] Replace with trademark free 
icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346582688
 
 
   +1 I think this is a really great solution, unless someone provides 
something concretely different to compare this with.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] lbruun commented on issue #251: [NETBEANS-126] Re-instate browser icons

[GitBox]

lbruun commented on issue #251: [NETBEANS-126] Re-instate browser icons
URL: 
https://github.com/apache/incubator-netbeans/pull/251#issuecomment-346580145
 
 
   [PR289](https://github.com/apache/incubator-netbeans/pull/289) is an 
alternative to this pull request which I think is what should be done for now. 
   
   However, I'll leave this PR intact so that it can be activated later if need 
be.
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] Chris2011 commented on issue #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

Chris2011 commented on issue #289: [NETBEANS-126] Replace with trademark free 
icons
URL: 
https://github.com/apache/incubator-netbeans/pull/289#issuecomment-346579247
 
 
   I think there are other icons, which are out of trademark. What about using 
fontawesome icons and convert the SVG back to PNG? Os try to use the SVG 
instead? Or finding others instead of creating new ones.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] lbruun opened a new pull request #289: [NETBEANS-126] Replace with trademark free icons

[GitBox]

lbruun opened a new pull request #289: [NETBEANS-126] Replace with trademark 
free icons
URL: https://github.com/apache/incubator-netbeans/pull/289
 
 
   In an effort to move on with the ASF release, the icons which were 
removed(*) from the donation are now replaced with icons which may not be the 
prettiest but which are free from trademark or other restrictions. If the 
outcome of [LEGAL-343](https://issues.apache.org/jira/browse/LEGAL-343) is that 
the original icons are OK to be distributed as part of Apache NetBeans, then 
this can be reversed, i.e. the original icons can be re-instated as per 
[PR251](https://github.com/apache/incubator-netbeans/pull/251).
   
   *) Technically they weren't removed but were replaced by Oracle with an NB 
dummy icon
   
   Changes are explained below.
   
   ### css.editor
   
   The icons which hints the user about CSS support for various browsers looked 
like this in NetBeans 8.2:
   
   
![browser-css-support-before](https://user-images.githubusercontent.com/32431476/33167606-543d1732-d03e-11e7-8a97-b61d10e18646.png)
   
   After this PR they'll look like this:
   
   
![browser-css-support-after](https://user-images.githubusercontent.com/32431476/33167612-5a38828e-d03e-11e7-8c57-493588674db2.png)
   
   (icons are made by me, which is why they are so ugly, but they serve the 
purpose for now)
   
   ### web.browser.api
   
   All browser-logo icons are replaced by the generic browser icon (which was 
already there in same location)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services