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:
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
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
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
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!
> >
> >
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
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
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?
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
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.
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
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
>
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
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
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:
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,
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
>
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
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
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
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
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
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
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:
25 matches
Mail list logo
