Re: Absolute paths written to all-resources.dat which break the IDE if moved entirely
There should be no absolute paths in the caches for anything under regular
cluster installation and userdir. There are even tests to make sure that is
true. They pass OK on Linux. One of them is known to fail on Windows:
https://builds.apache.org/job/incubator-netbeans-windows/lastCompletedBuild/
testReport/org.netbeans.core.startup.layers/CachingPreventsFileTouchesTest/
testCachesDontUseAbsolutePaths/
We don't test on Mac OS X as far as I know.
-jt
Dne středa 2. ledna 2019 0:22:29 CET, Emilian Bold napsal(a):
> If somebody downloads to ~/Downloads and starts the app from there the
> userdir on macOS will be in ~/Library/Application Support/ so there's
> no relative path between them and the paths are stored as absolute
> ("abs" identification).
>
> I suspect the saving netbeans.home in lastModified/all-checksum.txt
> fixes the problem since it will invalidate the cache:
>
> diff --git a/platform/o.n.bootstrap/src/org/netbeans/Stamps.java
> b/platform/o.n.bootstrap/src/org/netbeans/Stamps.java
> index e41c90897..7231bd827 100644
> --- a/platform/o.n.bootstrap/src/org/netbeans/Stamps.java
> +++ b/platform/o.n.bootstrap/src/org/netbeans/Stamps.java
> @@ -313,6 +313,7 @@ public final class Stamps {
> String[] relativeDirs = Clusters.relativeDirsWithHome();
> String home = System.getProperty ("netbeans.home"); // NOI18N
> if (home != null) {
> +sb.append("home=").append(home).append("\n");
> long stamp = stampForCluster (new File (home), result,
> newestFile, processedDirs, checkStampFile, true, null);
>
> sb.append(relativeDirs[0]).append('=').append(stamp).append('\n'); }
>
> Does this make sense? I wonder why I can't reproduce it with 8.2?
>
> --emi
>
> http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!
>
> On Tue, Jan 1, 2019 at 11:58 PM Emilian Bold wrote:
> > I'm still investigating but it seems to me that under some conditions
> > absolute paths are saved in all-resources.dat (and the other .dat
> > files).
> >
> > Problem is that if the user moves the application to another folder
> > (like from the Desktop to /Applications) then the IDE doesn't start
> > because it can't find any module! (Module could not be found...
> > ignoring).
> >
> > So, is there something rather obvious to anyone going on here?
> >
> > I suspect I will best reproduce this with a Platform app packaged as
> > macOS, but that script has another (unrelated) error which I also have
> > to report.
> >
> > --emi
> >
> > http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Felix and JDK11 and API related news
Hi. I wanted to do something refreshing and useful during the Christmas break and as such I took a look at the here in discussed Felix & JDK11 problem. By upgrading to version 6.0.1 I think the problem is solved: https://github.com/apache/incubator-netbeans/pull/1063 the tests of platform/core.netigso module (that use Felix as an OSGi container) pass OK with my local JDK11 installation. When at it I also decided to setup a Jenkins builder to build and test the NetBeans Platform on JDK11. Here it is together with PR that contains majority of the related changes: https://builds.apache.org/job/incubator-netbeans-linux-jdk11/ https://github.com/apache/incubator-netbeans/pull/1068 as you can see there is still a lot of failing tests. Your help investigating what is wrong and fixing them is more than welcomed! We want Apache NetBeans to build and run also on JDK11 at the end, right? I was a bit sad to see that the NetBeans Linux Jenkins job https://builds.apache.org/job/incubator-netbeans-linux/ is no longer blue. Then I realized that it is because of J2EE licenses. Hence I moved the licenses tests away: https://builds.apache.org/job/incubator-netbeans-license/lastCompletedBuild/ testReport/ please track the licenses cleanup progress there. As a result the NetBeans Linux Jenkins job is blue again! Last, but not least, I integrated snapshots of Apache NetBeans 10.0 APIs into the master branch. That should help us to keep backward compatibility: https://github.com/apache/incubator-netbeans/pull/1064#discussion_r244659441 Accidentally removing an API element should break module build (F11 in the IDE). Please contact me (by CCing) directly if you find some problems with this approach. Happy New Year. NetBeans never dies! -jt - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Maven 1st was: Gradle Support for Apache NetBeans
Dne sobota 29. prosince 2018 20:57:14 CET, Laszlo Kishalmi napsal(a): > I would like to donate my Gradle works to Apache NetBeans. Having Gradle support is important. Thanks for working on that. However I'd like to also know how it will work with the proposed "Maven first" approach and Toni's realization of it https://github.com/apache/incubator-netbeans/pull/1038 ? -jt - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Grails and Apache NetBeans
Hi, I did subscribed to the mailing list already. So, as I understand I should wait for the JavaEE cluster gets integrated. And try to roll back the Grails changes. And then we can see where to go from there. Regards, Oleg On Thu, Jan 3, 2019 at 3:08 PM Sven Reimers wrote: > Hi, > > there is some kind of dependency between grails and the java ee cluster... > > For a first step just reenabling should be good enough, but I think we may > need a better decoupling between grails and ee stuff. > > I assume there may be more frameworks benefiting from this.. > > -Sven > > Am Do., 3. Jan. 2019, 09:10 hat Geertjan Wielenga > geschrieben: > >> First, join the mailing list so that I do not have to keep approving your >> mails, i.e., your mails will come in automatically: >> >> https://netbeans.apache.org/community/mailing-lists.html >> >> Then do a fork of Apache NetBeans GitHub and then revert this and then >> provide a pull request: >> >> >> https://github.com/apache/incubator-netbeans/pull/904/commits/1a5259cfcba106430d95f039480578ff9ba41e34 >> >> But it seems like there's a dependency between Grails and the enterprise >> cluster -- Sven Reimers, can you remember why this is the case? Probably >> because Grails applications can be deployed to a server and until the >> enterprise cluster is re-included, there's no server support? >> >> Gj >> >> >> On Thu, Jan 3, 2019 at 1:51 AM Oleg Minukhin wrote: >> >> > Hi, >> > >> > I could start with reintegrating Grails as it was before. That is what >> I >> > am interesting in initially, as I am working on an old Grails project >> from >> > time to time. >> > >> > Regards, >> > Oleg >> > >> > On Wed, Jan 2, 2019 at 5:21 PM Geertjan Wielenga < >> > geertjan.wiele...@googlemail.com> wrote: >> > >> >> Let's start with a definition of the requirements. >> >> >> >> Gj >> >> >> >> >> >> On Wed, Jan 2, 2019 at 11:35 PM Oleg Minukhin >> wrote: >> >> >> >>> Hi Geertjan, >> >>> >> >>> I am interesting to help with some Groovy / Grails integration, at >> least >> >>> to the degree it was before. How would I start? >> >>> >> >>> Regards, >> >>> Oleg >> >>> >> >>> >> >>> On Sat, Dec 29, 2018, 11:00 AM Geertjan Wielenga < >> >>> geertjan.wiele...@googlemail.com wrote: >> >>> >> That makes sense. It was probably right to disable the old Grails >> support that we had. >> >> If someone can provide a 'hello world' Grails/Micronaut sample, we >> can >> integrate that and, if needed, build support around it. Maybe we can >> reuse >> some of the old Grails support, but probably not. >> >> Gj >> >> On Sat, Dec 29, 2018 at 5:54 PM Rik Scarborough >> wrote: >> >> > The Grails team has made a statement that they intend on moving >> Grails >> > into >> > the Micronaut structure. >> > >> > ~Rik >> > Believe in good >> > >> > On Sat, Dec 29, 2018, 10:51 AM Geertjan Wielenga >> > > > >> > > Hi all, especially Jasen and Oleg, who recently commented on >> Grails >> > support >> > > in Apache NetBeans, >> > > >> > > Now that we have released Apache NetBeans 10, and are looking to >> > Apache >> > > NetBeans 11, which will included the enterprise cluster, i.e., >> > including >> > > support for application servers, which is relevant for Grails >> > deployment, >> > > maybe we could look at reintegrating Grails features into Apache >> > NetBeans >> > > 11? >> > > >> > > Here's the related PR where we disabled Grails support (because of >> > lack of >> > > enterprise cluster integration and because the version of Grails >> > supported >> > > was outdated): >> > > >> > > >> > > >> > >> https://github.com/apache/incubator-netbeans/pull/904/commits/1a5259cfcba106430d95f039480578ff9ba41e34 >> > > >> > > Or should we not focus on Grails at all, or Micronaut instead? >> Would >> > be >> > > good to define what we'd like to achieve with Grails together and >> > come up >> > > with a plan. >> > > >> > > Thanks, >> > > >> > > Gj >> > > >> > >> >> >
Re: Gradle Support for Apache NetBeans
This is the only missing piece for the stuff I use most. Right now this is
the only reason I still have 8.2 around.
On Wed, Jan 2, 2019, 6:54 PM Laszlo Kishalmi
> On 12/30/18 10:22 AM, Jan Lahoda wrote:
> > Hi Laszlo,
> >
> > It will be great to have Gradle support - thanks for that!
> >
> > Regarding the:
> > groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
> >
> > I don't think that can be in the source distro ("compiled code not
> > allowed"), but it shouldn't be too problematic to download that during
> > build as well, right?
> I've checked a few Apache projects how they are solving this issue, then
> as of we have Ant as a wrapper around the Gradle phase, I added some
> tweaks to download the wrapper from Gradle's git repo. So that concern
> has been solved.
> > Thanks for doing this!
> >
> > Jan
> >
> > On Sat, Dec 29, 2018 at 8:57 PM Laszlo Kishalmi <
> laszlo.kisha...@gmail.com>
> > wrote:
> >
> >> Dear all,
> >>
> >> I would like to donate my Gradle works to Apache NetBeans.
> >>
> >> Right now the code is here:
> >> https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support
> >>
> >> I just recently rebased it on master, so there is no conflicts. If I'd
> >> create a PR from it that would mean 317 new files and ~35k line of code.
> >>
> >> The current state of the plugin:
> >>
> >>* It Opens Gradle Projects resource efficiently
> >>* It is based on the ideas found in our Maven Plugin
> >>* It supports JavaSE and Groovy development
> >>* Unit Testing
> >>* Code Coverage
> >>* JPA projects
> >>* Spring (the little support we have for that)
> >>* Navigator for project task
> >>* Custom Task execution
> >>* Output processing
> >>* Debugging (even single methods)
> >>* Creating new projects
> >>
> >> The shady side:
> >>
> >>* The Gradle <-> NetBeans project discovery and communication.
> >> Based on simple property serialization. Ugly Groovy code, well the
> >> deserialization Java code isn't that nice as well
> >>* Limited number of unittest
> >>* Being a sole developer there could be glitches here and there as of
> >> lack of wider testing.
> >>* Gradle is required to build the NetBeans <-> Gradle tooling
> >> This adds a binary
> >>
> groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
> >> to the source distribution package, though this file is not
> >> distributed. So Apace might agree with that.
> >>
> >> Introduced External Dependencies:
> >>
> >>* Gradle Tooling API (Apache Licensed)
> >>o slf4j (Apache Licensed)
> >>* JaCoCo Core Library (EPL 1.0)
> >> The whole JaCoCo project uses other libraries distributed under
> >> different licenses, I need to make sure that the core is EPL 1.0
> only
> >>
> >> Areas to Improve:
> >>
> >>* There is no support for Ergonomy
> >>* Module versions might be incorrectly specified, I did the best I
> could
> >>* Add Groovy project support (could be trivial)
> >>* Improve Gradle <-> JDK incompatibility check.
> >>* Profiling
> >>* Compile on Save (that's an icy territory)
> >>* Improve project Settings
> >>* Whatever you think...
> >>
> >> Future Works:
> >>
> >>* I also have a JavaEE support module started, I can donate somewhat
> >> later to the enterprise cluster.
> >>
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
JIRA Maintenace: Make Version 10.0 released
Dear all, I need some help, in order to make version 10.0 released in our JIRA, also rename "Next" -> 11.0 and create a new "Next" version. Thank you! - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Automatic error reporting in pre-Apache NetBeans versions, going forward
This could work for future versions but it would have to be written and the users would have to (want to) register. NetBeans 8.2 allows anonymous bug reporting which is nice. I doubt this could automatically work for error reports we will get from 8.2 installs (which this thread is about). Also remember that you might get a whole lot of duplicates so posting straight to JIRA might not be so well unless we have a bot auto-closing duplicates. The default error reporter sends more than just a stacktrace, we might have to filter what gets uploader. --emi http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! On Thu, Jan 3, 2019 at 11:27 PM John McDonnell wrote: > > Is this not something that could be customised to point to JIRA? > > If I remember correctly it allowed for credentials to be supplied and we > could use the JIRA REST API to create tickets on that portal? > > This would keep all issues in the same place, so we don't have 2 areas > where reporting is done? > > Regards > > John > > On Thu, 3 Jan 2019 at 21:21, Emilian Bold wrote: > > > I'm basically suggesting this since I have the infrastructure already > > set up for CoolBeans and I could just take the 8.2 reports in (perhaps > > by adding another server, not sure how heavy that stream is). > > > > Under Apache we already take no error reporting at all, so I doubt we > > could take error reports from products released outside Apache... > > > > --emi > > > > http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! > > > > On Thu, Jan 3, 2019 at 10:45 PM Sven Reimers > > wrote: > > > > > > Is there no way to do this inside Apache NetBeans? > > > > > > Preferring one distribution over another will not help us in the long > > run. > > > > > > So I would prefer a solution based on the NetBeans VM (where things like > > > synergy are hosted).. > > > > > > -Sven > > > > > > Am Do., 3. Jan. 2019, 21:25 hat Geertjan Wielenga > > > geschrieben: > > > > > > > I see no objection, sounds like a solution. > > > > > > > > Gj > > > > > > > > On Thu, Jan 3, 2019 at 8:08 PM Emilian Bold > > > > wrote: > > > > > > > > > Hello, > > > > > > > > > > NetBeans used to have an automated mechanism where users could upload > > > > > their errors directly from the IDE. > > > > > > > > > > I expect that all the error reporting will stop working for NetBeans > > > > > 8.2 considering netbeans.org is moving to Apache infrastructure. > > > > > > > > > > I wonder if it wouldn't be valuable to redirect those error reports > > to > > > > > CoolBeans infrastructure. I expect that many of the issues users will > > > > > report will still be relevant for current NetBeans version (although, > > > > > obviously, a chunk of them will have been fixed since 8.2). > > > > > > > > > > From an implementation standpoint it's probably a single 301 > > redirect. > > > > > > > > > > --emi > > > > > > > > > > http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and > > > > more! > > > > > > > > > > - > > > > > To unsubscribe, e-mail: > > dev-unsubscr...@netbeans.incubator.apache.org > > > > > For additional commands, e-mail: > > dev-h...@netbeans.incubator.apache.org > > > > > > > > > > For further information about the NetBeans mailing lists, visit: > > > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > > > > > > > > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Automatic error reporting in pre-Apache NetBeans versions, going forward
Is this not something that could be customised to point to JIRA? If I remember correctly it allowed for credentials to be supplied and we could use the JIRA REST API to create tickets on that portal? This would keep all issues in the same place, so we don't have 2 areas where reporting is done? Regards John On Thu, 3 Jan 2019 at 21:21, Emilian Bold wrote: > I'm basically suggesting this since I have the infrastructure already > set up for CoolBeans and I could just take the 8.2 reports in (perhaps > by adding another server, not sure how heavy that stream is). > > Under Apache we already take no error reporting at all, so I doubt we > could take error reports from products released outside Apache... > > --emi > > http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! > > On Thu, Jan 3, 2019 at 10:45 PM Sven Reimers > wrote: > > > > Is there no way to do this inside Apache NetBeans? > > > > Preferring one distribution over another will not help us in the long > run. > > > > So I would prefer a solution based on the NetBeans VM (where things like > > synergy are hosted).. > > > > -Sven > > > > Am Do., 3. Jan. 2019, 21:25 hat Geertjan Wielenga > > geschrieben: > > > > > I see no objection, sounds like a solution. > > > > > > Gj > > > > > > On Thu, Jan 3, 2019 at 8:08 PM Emilian Bold > > > wrote: > > > > > > > Hello, > > > > > > > > NetBeans used to have an automated mechanism where users could upload > > > > their errors directly from the IDE. > > > > > > > > I expect that all the error reporting will stop working for NetBeans > > > > 8.2 considering netbeans.org is moving to Apache infrastructure. > > > > > > > > I wonder if it wouldn't be valuable to redirect those error reports > to > > > > CoolBeans infrastructure. I expect that many of the issues users will > > > > report will still be relevant for current NetBeans version (although, > > > > obviously, a chunk of them will have been fixed since 8.2). > > > > > > > > From an implementation standpoint it's probably a single 301 > redirect. > > > > > > > > --emi > > > > > > > > http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and > > > more! > > > > > > > > - > > > > To unsubscribe, e-mail: > dev-unsubscr...@netbeans.incubator.apache.org > > > > For additional commands, e-mail: > dev-h...@netbeans.incubator.apache.org > > > > > > > > For further information about the NetBeans mailing lists, visit: > > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > > > > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: Automatic error reporting in pre-Apache NetBeans versions, going forward
I'm basically suggesting this since I have the infrastructure already set up for CoolBeans and I could just take the 8.2 reports in (perhaps by adding another server, not sure how heavy that stream is). Under Apache we already take no error reporting at all, so I doubt we could take error reports from products released outside Apache... --emi http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! On Thu, Jan 3, 2019 at 10:45 PM Sven Reimers wrote: > > Is there no way to do this inside Apache NetBeans? > > Preferring one distribution over another will not help us in the long run. > > So I would prefer a solution based on the NetBeans VM (where things like > synergy are hosted).. > > -Sven > > Am Do., 3. Jan. 2019, 21:25 hat Geertjan Wielenga > geschrieben: > > > I see no objection, sounds like a solution. > > > > Gj > > > > On Thu, Jan 3, 2019 at 8:08 PM Emilian Bold > > wrote: > > > > > Hello, > > > > > > NetBeans used to have an automated mechanism where users could upload > > > their errors directly from the IDE. > > > > > > I expect that all the error reporting will stop working for NetBeans > > > 8.2 considering netbeans.org is moving to Apache infrastructure. > > > > > > I wonder if it wouldn't be valuable to redirect those error reports to > > > CoolBeans infrastructure. I expect that many of the issues users will > > > report will still be relevant for current NetBeans version (although, > > > obviously, a chunk of them will have been fixed since 8.2). > > > > > > From an implementation standpoint it's probably a single 301 redirect. > > > > > > --emi > > > > > > http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and > > more! > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > > > For further information about the NetBeans mailing lists, visit: > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > > > > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Grails and Apache NetBeans
Hi, there is some kind of dependency between grails and the java ee cluster... For a first step just reenabling should be good enough, but I think we may need a better decoupling between grails and ee stuff. I assume there may be more frameworks benefiting from this.. -Sven Am Do., 3. Jan. 2019, 09:10 hat Geertjan Wielenga geschrieben: > First, join the mailing list so that I do not have to keep approving your > mails, i.e., your mails will come in automatically: > > https://netbeans.apache.org/community/mailing-lists.html > > Then do a fork of Apache NetBeans GitHub and then revert this and then > provide a pull request: > > > https://github.com/apache/incubator-netbeans/pull/904/commits/1a5259cfcba106430d95f039480578ff9ba41e34 > > But it seems like there's a dependency between Grails and the enterprise > cluster -- Sven Reimers, can you remember why this is the case? Probably > because Grails applications can be deployed to a server and until the > enterprise cluster is re-included, there's no server support? > > Gj > > > On Thu, Jan 3, 2019 at 1:51 AM Oleg Minukhin wrote: > > > Hi, > > > > I could start with reintegrating Grails as it was before. That is what I > > am interesting in initially, as I am working on an old Grails project > from > > time to time. > > > > Regards, > > Oleg > > > > On Wed, Jan 2, 2019 at 5:21 PM Geertjan Wielenga < > > geertjan.wiele...@googlemail.com> wrote: > > > >> Let's start with a definition of the requirements. > >> > >> Gj > >> > >> > >> On Wed, Jan 2, 2019 at 11:35 PM Oleg Minukhin > wrote: > >> > >>> Hi Geertjan, > >>> > >>> I am interesting to help with some Groovy / Grails integration, at > least > >>> to the degree it was before. How would I start? > >>> > >>> Regards, > >>> Oleg > >>> > >>> > >>> On Sat, Dec 29, 2018, 11:00 AM Geertjan Wielenga < > >>> geertjan.wiele...@googlemail.com wrote: > >>> > That makes sense. It was probably right to disable the old Grails > support that we had. > > If someone can provide a 'hello world' Grails/Micronaut sample, we can > integrate that and, if needed, build support around it. Maybe we can > reuse > some of the old Grails support, but probably not. > > Gj > > On Sat, Dec 29, 2018 at 5:54 PM Rik Scarborough > wrote: > > > The Grails team has made a statement that they intend on moving > Grails > > into > > the Micronaut structure. > > > > ~Rik > > Believe in good > > > > On Sat, Dec 29, 2018, 10:51 AM Geertjan Wielenga > > > > > > Hi all, especially Jasen and Oleg, who recently commented on Grails > > support > > > in Apache NetBeans, > > > > > > Now that we have released Apache NetBeans 10, and are looking to > > Apache > > > NetBeans 11, which will included the enterprise cluster, i.e., > > including > > > support for application servers, which is relevant for Grails > > deployment, > > > maybe we could look at reintegrating Grails features into Apache > > NetBeans > > > 11? > > > > > > Here's the related PR where we disabled Grails support (because of > > lack of > > > enterprise cluster integration and because the version of Grails > > supported > > > was outdated): > > > > > > > > > > > > https://github.com/apache/incubator-netbeans/pull/904/commits/1a5259cfcba106430d95f039480578ff9ba41e34 > > > > > > Or should we not focus on Grails at all, or Micronaut instead? > Would > > be > > > good to define what we'd like to achieve with Grails together and > > come up > > > with a plan. > > > > > > Thanks, > > > > > > Gj > > > > > > >
Re: Automatic error reporting in pre-Apache NetBeans versions, going forward
If possible, would be preferable. Gj On Thu, Jan 3, 2019 at 9:45 PM Sven Reimers wrote: > Is there no way to do this inside Apache NetBeans? > > Preferring one distribution over another will not help us in the long run. > > So I would prefer a solution based on the NetBeans VM (where things like > synergy are hosted).. > > -Sven > > Am Do., 3. Jan. 2019, 21:25 hat Geertjan Wielenga > geschrieben: > > > I see no objection, sounds like a solution. > > > > Gj > > > > On Thu, Jan 3, 2019 at 8:08 PM Emilian Bold > > wrote: > > > > > Hello, > > > > > > NetBeans used to have an automated mechanism where users could upload > > > their errors directly from the IDE. > > > > > > I expect that all the error reporting will stop working for NetBeans > > > 8.2 considering netbeans.org is moving to Apache infrastructure. > > > > > > I wonder if it wouldn't be valuable to redirect those error reports to > > > CoolBeans infrastructure. I expect that many of the issues users will > > > report will still be relevant for current NetBeans version (although, > > > obviously, a chunk of them will have been fixed since 8.2). > > > > > > From an implementation standpoint it's probably a single 301 redirect. > > > > > > --emi > > > > > > http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and > > more! > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > > For additional commands, e-mail: > dev-h...@netbeans.incubator.apache.org > > > > > > For further information about the NetBeans mailing lists, visit: > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > > > > >
Re: Automatic error reporting in pre-Apache NetBeans versions, going forward
Is there no way to do this inside Apache NetBeans? Preferring one distribution over another will not help us in the long run. So I would prefer a solution based on the NetBeans VM (where things like synergy are hosted).. -Sven Am Do., 3. Jan. 2019, 21:25 hat Geertjan Wielenga geschrieben: > I see no objection, sounds like a solution. > > Gj > > On Thu, Jan 3, 2019 at 8:08 PM Emilian Bold > wrote: > > > Hello, > > > > NetBeans used to have an automated mechanism where users could upload > > their errors directly from the IDE. > > > > I expect that all the error reporting will stop working for NetBeans > > 8.2 considering netbeans.org is moving to Apache infrastructure. > > > > I wonder if it wouldn't be valuable to redirect those error reports to > > CoolBeans infrastructure. I expect that many of the issues users will > > report will still be relevant for current NetBeans version (although, > > obviously, a chunk of them will have been fixed since 8.2). > > > > From an implementation standpoint it's probably a single 301 redirect. > > > > --emi > > > > http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and > more! > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > >
Re: Automatic error reporting in pre-Apache NetBeans versions, going forward
I see no objection, sounds like a solution. Gj On Thu, Jan 3, 2019 at 8:08 PM Emilian Bold wrote: > Hello, > > NetBeans used to have an automated mechanism where users could upload > their errors directly from the IDE. > > I expect that all the error reporting will stop working for NetBeans > 8.2 considering netbeans.org is moving to Apache infrastructure. > > I wonder if it wouldn't be valuable to redirect those error reports to > CoolBeans infrastructure. I expect that many of the issues users will > report will still be relevant for current NetBeans version (although, > obviously, a chunk of them will have been fixed since 8.2). > > From an implementation standpoint it's probably a single 301 redirect. > > --emi > > http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Automatic error reporting in pre-Apache NetBeans versions, going forward
Hello, NetBeans used to have an automated mechanism where users could upload their errors directly from the IDE. I expect that all the error reporting will stop working for NetBeans 8.2 considering netbeans.org is moving to Apache infrastructure. I wonder if it wouldn't be valuable to redirect those error reports to CoolBeans infrastructure. I expect that many of the issues users will report will still be relevant for current NetBeans version (although, obviously, a chunk of them will have been fixed since 8.2). >From an implementation standpoint it's probably a single 301 redirect. --emi http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
New project list
Hi, I'd like to introduce a new maven project type in the list (with maybe some maven specific settings if i can). Where and how may i do that ? -- Emmanuel Hugonnet http://www.ehsavoie.com http://twitter.com/ehsavoie
Re: About the NetBeans brand and our trademark
For the records, the License FAQ explicitly clarifies the "Powered by" et al vs. TradeMarks: http://www.apache.org/foundation/license-faq.html#Name-changes Cheers, Antonio El 03/01/2019 a las 16:32, Antonio escribió: Hi, "Powered by Spark" may be a good example for us: https://spark.apache.org/powered-by.html Quoting: Names like “Spark BigCoProduct” are not OK, as are names including “Spark” in general. The above links, however, describe some exceptions, like for names such as “BigCoProduct, powered by Apache Spark” or “BigCoProduct for Apache Spark”. Feliz Año, Antonio El 03/01/2019 a las 14:09, Emilian Bold escribió: Apache has a 'Powered by' program which seems a good fit for the NetBeans Platform. --emi On Thu, 3 Jan 2019 at 14:52, Antonio wrote: Hi all, We should get Apache NetBeans added to the list of ASF Trademarks at https://www.apache.org/foundation/marks/list/ (NetBeans is already a tracermark of Apache, isn't it?). We should also mention that Apache NetBeans is a trademark of the ASF at the footer of all web pages in our site. As we all there's a great ecosystem of apps built on top of the NetBeans Platform, and I think it could be good to acknowledge and promote this. I don't think something like "Built on Top of the Apache NetBeans Platform" is contrary to the ASF tracemark policies. Cheers, Antonio El 03/01/2019 a las 12:04, Bertrand Delacretaz escribió: Hi, On Thu, Jan 3, 2019 at 11:22 AM Emilian Bold wrote: Is it really wise to create a separate FAQ from the Apache trademarks pages?... If you keep it minimal I think it's good - you probably just need 2-3 good examples of naming for the types of things that people are doing with NetBeans. And of course point to the ASF trademarks pages and avoid duplicating their information. But that's a decision for this PPMC to make - whoever does the work gets to decide, and that's not me ;-) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists -- --emi - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: About the NetBeans brand and our trademark
Hi, "Powered by Spark" may be a good example for us: https://spark.apache.org/powered-by.html Quoting: Names like “Spark BigCoProduct” are not OK, as are names including “Spark” in general. The above links, however, describe some exceptions, like for names such as “BigCoProduct, powered by Apache Spark” or “BigCoProduct for Apache Spark”. Feliz Año, Antonio El 03/01/2019 a las 14:09, Emilian Bold escribió: Apache has a 'Powered by' program which seems a good fit for the NetBeans Platform. --emi On Thu, 3 Jan 2019 at 14:52, Antonio wrote: Hi all, We should get Apache NetBeans added to the list of ASF Trademarks at https://www.apache.org/foundation/marks/list/ (NetBeans is already a tracermark of Apache, isn't it?). We should also mention that Apache NetBeans is a trademark of the ASF at the footer of all web pages in our site. As we all there's a great ecosystem of apps built on top of the NetBeans Platform, and I think it could be good to acknowledge and promote this. I don't think something like "Built on Top of the Apache NetBeans Platform" is contrary to the ASF tracemark policies. Cheers, Antonio El 03/01/2019 a las 12:04, Bertrand Delacretaz escribió: Hi, On Thu, Jan 3, 2019 at 11:22 AM Emilian Bold wrote: Is it really wise to create a separate FAQ from the Apache trademarks pages?... If you keep it minimal I think it's good - you probably just need 2-3 good examples of naming for the types of things that people are doing with NetBeans. And of course point to the ASF trademarks pages and avoid duplicating their information. But that's a decision for this PPMC to make - whoever does the work gets to decide, and that's not me ;-) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists -- --emi - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: About the NetBeans brand and our trademark
Apache has a 'Powered by' program which seems a good fit for the NetBeans Platform. --emi On Thu, 3 Jan 2019 at 14:52, Antonio wrote: > Hi all, > > We should get Apache NetBeans added to the list of ASF Trademarks at > https://www.apache.org/foundation/marks/list/ (NetBeans is already a > tracermark of Apache, isn't it?). We should also mention that Apache > NetBeans is a trademark of the ASF at the footer of all web pages in our > site. > > As we all there's a great ecosystem of apps built on top of the NetBeans > Platform, and I think it could be good to acknowledge and promote this. > > I don't think something like "Built on Top of the Apache NetBeans > Platform" is contrary to the ASF tracemark policies. > > Cheers, > Antonio > > > El 03/01/2019 a las 12:04, Bertrand Delacretaz escribió: > > Hi, > > > > On Thu, Jan 3, 2019 at 11:22 AM Emilian Bold > wrote: > >> > >> Is it really wise to create a separate FAQ from the Apache trademarks > >> pages?... > > > > If you keep it minimal I think it's good - you probably just need 2-3 > > good examples of naming for the types of things that people are doing > > with NetBeans. > > > > And of course point to the ASF trademarks pages and avoid duplicating > > their information. > > > > But that's a decision for this PPMC to make - whoever does the work > > gets to decide, and that's not me ;-) > > > > -Bertrand > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > -- --emi
Re: About the NetBeans brand and our trademark
Hi all, We should get Apache NetBeans added to the list of ASF Trademarks at https://www.apache.org/foundation/marks/list/ (NetBeans is already a tracermark of Apache, isn't it?). We should also mention that Apache NetBeans is a trademark of the ASF at the footer of all web pages in our site. As we all there's a great ecosystem of apps built on top of the NetBeans Platform, and I think it could be good to acknowledge and promote this. I don't think something like "Built on Top of the Apache NetBeans Platform" is contrary to the ASF tracemark policies. Cheers, Antonio El 03/01/2019 a las 12:04, Bertrand Delacretaz escribió: Hi, On Thu, Jan 3, 2019 at 11:22 AM Emilian Bold wrote: Is it really wise to create a separate FAQ from the Apache trademarks pages?... If you keep it minimal I think it's good - you probably just need 2-3 good examples of naming for the types of things that people are doing with NetBeans. And of course point to the ASF trademarks pages and avoid duplicating their information. But that's a decision for this PPMC to make - whoever does the work gets to decide, and that's not me ;-) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: About the NetBeans brand and our trademark
Hi, On Thu, Jan 3, 2019 at 11:22 AM Emilian Bold wrote: > > Is it really wise to create a separate FAQ from the Apache trademarks > pages?... If you keep it minimal I think it's good - you probably just need 2-3 good examples of naming for the types of things that people are doing with NetBeans. And of course point to the ASF trademarks pages and avoid duplicating their information. But that's a decision for this PPMC to make - whoever does the work gets to decide, and that's not me ;-) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [MENTORS] Re: Maturity Model Assessment and Incubator Status Report
Hi, On Thu, Jan 3, 2019 at 11:17 AM Geertjan Wielenga wrote: > ...Aside from the maturity assessment, which we’re working on, > what’s the process for graduation... https://incubator.apache.org/guides/graduation.html has a checklist. One thing that I like to add is checking that the suggested PMC roster is realistic, i.e. consists of people who are actually active. https://whimsy.apache.org/roster/ppmc/netbeans lists 85 PPMC members, I suppose a number of them aren't really active. To prune this roster I suggest that the PPMC asks all these people (via this list, with an [IMPORTANT] subject line header maybe) to confirm that they are active or intend to become active again soon. And mention that if they don't reply within a given amount of time they won't be included in the proposed PMC roster. Maybe just send the proposed roster here and ask people to confirm. If someone is removed and becomes active again after graduation it's easy to re-add them with a PMC vote, so I think it's better to start with a smaller but realistic list of PMC members. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: About the NetBeans brand and our trademark
Is it really wise to create a separate FAQ from the Apache trademarks pages? I think that page is pretty clear on what Apache allows and doesn't allow. More importantly we should *read* those pages and understand as a community (and at PPMC level) what the ASF wants and what our approach should be when we see the trademark being used. --emi http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! On Thu, Jan 3, 2019 at 12:13 PM Bertrand Delacretaz wrote: > > Hi, > > On Mon, Dec 31, 2018 at 4:32 PM Emilian Bold wrote: > > ...we should be proactive about our trademark > > Indeed. The simplest might be to create a FAQ about how people can use > the Apache NetBeans name in specific cases, like creating their own > installer or extension or creating an app built on NetBeans. > > -Bertrand > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[MENTORS] Re: Maturity Model Assessment and Incubator Status Report
Mentors, See below. Aside from the maturity assessment, which we’re working on, what’s the process for graduation — please advise and guide on this, the last part where your help is needed! :-) Gj On Sunday, December 30, 2018, Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > Hi all, > > Our mentors have suggested, several times, that it's time for us to > discuss becoming a top level project, i.e., to move out of the incubator. > > A first step is to do a maturity model assessment and I have started that > here, feel free to add to it and tweak, it's not complete by any means, > just a starting point: > > https://cwiki.apache.org/confluence/display/NETBEANS/ > Apache+Maturity+Model+Assessment+for+NetBeans > > Mentors, what's the next step after the above? > > Also, as always, periodically, we need to contribute our current status to > the incubator status report and our turn is coming up in the January 2019 > report, I have added some content already, feel free to indicate here about > anything else should be added or add it yourself: > > https://wiki.apache.org/incubator/January2019 > > For reference, here's the previous one where we were included: > > https://wiki.apache.org/incubator/October2018 > > Thanks, > > Gj > >
Re: About the NetBeans brand and our trademark
Hi, On Mon, Dec 31, 2018 at 4:32 PM Emilian Bold wrote: > ...we should be proactive about our trademark Indeed. The simplest might be to create a FAQ about how people can use the Apache NetBeans name in specific cases, like creating their own installer or extension or creating an app built on NetBeans. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Grails and Apache NetBeans
First, join the mailing list so that I do not have to keep approving your mails, i.e., your mails will come in automatically: https://netbeans.apache.org/community/mailing-lists.html Then do a fork of Apache NetBeans GitHub and then revert this and then provide a pull request: https://github.com/apache/incubator-netbeans/pull/904/commits/1a5259cfcba106430d95f039480578ff9ba41e34 But it seems like there's a dependency between Grails and the enterprise cluster -- Sven Reimers, can you remember why this is the case? Probably because Grails applications can be deployed to a server and until the enterprise cluster is re-included, there's no server support? Gj On Thu, Jan 3, 2019 at 1:51 AM Oleg Minukhin wrote: > Hi, > > I could start with reintegrating Grails as it was before. That is what I > am interesting in initially, as I am working on an old Grails project from > time to time. > > Regards, > Oleg > > On Wed, Jan 2, 2019 at 5:21 PM Geertjan Wielenga < > geertjan.wiele...@googlemail.com> wrote: > >> Let's start with a definition of the requirements. >> >> Gj >> >> >> On Wed, Jan 2, 2019 at 11:35 PM Oleg Minukhin wrote: >> >>> Hi Geertjan, >>> >>> I am interesting to help with some Groovy / Grails integration, at least >>> to the degree it was before. How would I start? >>> >>> Regards, >>> Oleg >>> >>> >>> On Sat, Dec 29, 2018, 11:00 AM Geertjan Wielenga < >>> geertjan.wiele...@googlemail.com wrote: >>> That makes sense. It was probably right to disable the old Grails support that we had. If someone can provide a 'hello world' Grails/Micronaut sample, we can integrate that and, if needed, build support around it. Maybe we can reuse some of the old Grails support, but probably not. Gj On Sat, Dec 29, 2018 at 5:54 PM Rik Scarborough wrote: > The Grails team has made a statement that they intend on moving Grails > into > the Micronaut structure. > > ~Rik > Believe in good > > On Sat, Dec 29, 2018, 10:51 AM Geertjan Wielenga > > > Hi all, especially Jasen and Oleg, who recently commented on Grails > support > > in Apache NetBeans, > > > > Now that we have released Apache NetBeans 10, and are looking to > Apache > > NetBeans 11, which will included the enterprise cluster, i.e., > including > > support for application servers, which is relevant for Grails > deployment, > > maybe we could look at reintegrating Grails features into Apache > NetBeans > > 11? > > > > Here's the related PR where we disabled Grails support (because of > lack of > > enterprise cluster integration and because the version of Grails > supported > > was outdated): > > > > > > > https://github.com/apache/incubator-netbeans/pull/904/commits/1a5259cfcba106430d95f039480578ff9ba41e34 > > > > Or should we not focus on Grails at all, or Micronaut instead? Would > be > > good to define what we'd like to achieve with Grails together and > come up > > with a plan. > > > > Thanks, > > > > Gj > > >
