Hi, William,
> > but I don't know that it's really relevant to building
> > NetBeans. It is nice, and does the kind of parallelization you're
> > after, but it's more like a meta-build system - a build system for
> > running other build systems. FWIW, NetBSd/SmartOS's pkgsrc is also
> > similar,
On Wed, May 23, 2018 at 10:44 PM, Ate Douma wrote:
>
>
> On 2018-05-23 20:57, Emilian Bold wrote:
>
>> Ate, could we get a vote on this release?
>>
>
> Sure :-)
>
>
>> If you look at https://cwiki.apache.org/confl
>> uence/display/NETBEANS/Apache+NetBeans+9.0+RC1 we are already making
>> progress
Just asking, would Snap packaged NetBeans work on Gentoo as well?
On 05/25/2018 03:19 PM, William L. Thomson Jr. wrote:
On Fri, 25 May 2018 14:12:46 -0400
Emilian Bold wrote:
What I like is deterministic builds, which neither Ant nor Maven
(both Apache projects) seem to hurry to add.
Based
On Fri, 25 May 2018 14:12:46 -0400
Emilian Bold wrote:
> What I like is deterministic builds, which neither Ant nor Maven
> (both Apache projects) seem to hurry to add.
>
> Based on deterministic builds you can have any kind of simple or
> fancy build infrastructure to help you out.
That is kind
I think I have worked out the problem and a solution:
Sources sources = ProjectUtils.getSources(project);
SourceGroup sourceGroup =
sources.getSourceGroups(JavaProjectConstants.SOURCES_TYPE_JAVA)[0];
FileObject sgRoot = sourceGroup.getRootFolder();
Hi Jaroslav,
Sorry for the late response. I'm adding Piotr and Eric from the Gradle
build tool team to have a look at this and see what we can do to help.
Hans
On Thu, Apr 19, 2018 at 11:58 AM Jaroslav Tulach
wrote:
> Hello guys, hello Laszlo.
>
> For a while I was considering to expand the re
On a related note, Maven 5.0+ is using ANSI colors in a very nice way
but this won't work in Netbeans.
I suggest a committer contact the author of JANSI through
https://github.com/fusesource/jansi/issues/87 to debug this further.
Kind regards,
Gili
On 2018-05-25 6:49 AM, Peter Cheung wrote:
What I like is deterministic builds, which neither Ant nor Maven (both Apache
projects) seem to hurry to add.
Based on deterministic builds you can have any kind of simple or fancy build
infrastructure to help you out.
I would like to have the server do some builds in background while I edit my
On Fri, 25 May 2018 17:34:08 +0100
Peter Steele wrote:
>
> Had a quick look at Bazel from Google, sounds like an interesting
> concept. Multi language build system. This seems to match the
> ethos of netbeans quite well (being multi language).
Problem with Bazel and Buck, is they both have pyth
The plugin is Fred Vinet's ANTLR4 plug in. The plugin adds ANTLR4 support to
Netbeans, i.e. syntax checking / highlighting / completion of the grammar and
an automated build via ANT or Maven. IT implements a very useful "Add ANTLR
support" menu option to the file menu which adapts an ANT or Mave
Sorry, did not even realise I was
On 25/05/2018 17:21, Antonio wrote:
Hi,
Please do not cross post to both dev@netbeans.incubator.apache.org and
d...@netbeans.apache.org
The proper email address is dev@netbeans.incubator.apache.org, as
NetBeans is a proud member of the Apache Incubator Pro
+1 Gradle
-1 Maven
Gradle is far superior to maven especially in multi project projects. It
still uses ant for certain tasks such as jar signing but the groovy
scripting allows you to powerfully control how the build works. I will
admit it's a bit of mind set change but once you are over the learn
Hi,
Please do not cross post to both dev@netbeans.incubator.apache.org and
d...@netbeans.apache.org
The proper email address is dev@netbeans.incubator.apache.org, as
NetBeans is a proud member of the Apache Incubator Project.
Thanks,
Antonio
---
On Fri, 25 May 2018 15:58:34 +0100
Neil C Smith wrote:
> On Fri, 25 May 2018 at 02:02 Tim Boudreau wrote:
>
> > IMO, Gradle is a step backward for build systems - scriptability
> > leads to fragile systems, and ones that are impossible for tools to
> > reason about.
> >
> > https://timboudreau.
On Fri, 25 May 2018 at 02:02 Tim Boudreau wrote:
> IMO, Gradle is a step backward for build systems - scriptability leads to
> fragile systems, and ones that are impossible for tools to reason about.
>
> https://timboudreau.com/blog/maven/read
>
>
Nice article! I know you link it in a comment, b
So from the perspective of NetBeans we could either:
1. remove the broken project type for Maven OSGi bundles until it's fixed
upstream
2. adopt the osgi-archetype (there seems to be only 3 authors, they could
donate the code to Apache)
3. re-implement the osgi-archetype
I guess step 1 is manda
On Thu, 24 May 2018 21:02:31 -0400
Tim Boudreau wrote:
> I could tell you whatever you want to know about Gentoo's build
> system,
Really? I have completely redesign how Java is handled... I would doubt
there are more familiar with it than me, at least regarding Java on
Gentoo. Though my work i
On Fri, May 25, 2018 at 11:50 AM, sgpa...@mainscreen.com <
sgpa...@mainscreen.com> wrote:
> Hi,
> Can someone please direct me to the correct place for asking questions
> regarding plugin devlopment?
> I am having trouble contributing a fix to a bug in a third-party NB 8
> plugin
Which 3rd part
Sorry, I misunderstood what you were getting at. FQN is:
org.netbeans.modules.java.api.common.classpath.ClassPathModifier
On 2018/05/25 12:57:10, Peter Nabbefeld wrote:
>
> Hi Stephen,
>
> the package is exported as public (not friend), so You should be able to
> look for the implementation
The upstream project seems to be orphaned, so it seems either the
project has to be forked/continued by somebody else or some other
implementation should be implemented, probably template-based.
Regards
P.
Am 25.05.2018 um 14:02 schrieb Emilian Bold:
Commented on issue.
--emi
‐‐‐ Orig
Hi Stephen,
the package is exported as public (not friend), so You should be able to
look for the implementation (which might not be public, but we only need
the FQCN).
What "parameter 3" are You referring to?
Regards
P.
Am 25.05.2018 um 14:44 schrieb sgpa...@mainscreen.com:
I'll try lo
I'll try looking up the pcpmi if the visibility will let me - The pcpmi can at
least provide a list of the extensible source groups, which should lead to the
right value for the second parameter to addLibraries. How do get the list of
types for parameter 3 I wonder?
On 2018/05/25 11:57:42, Pete
Commented on issue.
--emi
‐‐‐ Original Message ‐‐‐
On 25 May 2018 1:23 PM, Peter Nabbefeld wrote:
> Hello,
>
> will it be possible to fix
>
> https://issues.apache.org/jira/browse/NETBEANS-595 before release? I
>
> added a comment so it should be straightforward for somebody knowing
Oops, sorry for the duplicate postings - had some problems with my email
client.
Regards
Peter
Am 25.05.2018 um 12:11 schrieb Peter Nabbefeld:
Hi Stephen,
what does it mean, You "cannot get it working"? Which problems
(behaviour or exceptions) do You have exactly?
Kind regards
Peter
Am
Hi Stephen,
I've found the following source code:
@SuppressWarnings("deprecation")
public static
org.netbeans.spi.java.project.classpath.ProjectClassPathExtender
extenderForModifier(final Project p) {
return new
org.netbeans.spi.java.project.classpath.ProjectClassPathExtender
Hello Stephen,
as it's Your source code, the right place for questions is here.
I haven't used ProjectClassPathModifier or ProjectClassPathExtender yet,
but from the JavaDoc I'd guess You should probably be able to use
"ProjectClassPathExtender pcpe = pcpm.extenderForModifier(pcpe);". While
Hi Peter,
Thanks for the quick reply.
The plugin adds a library to the classpath, currently by rewriting the projevct
properties file. I am trying to use the API instead. I can get it working using
ProjectClassPathExtender but not ProjectClassPathModifier, which gives me:
Java.lang.UnsupportedOpe
i am using system.out
Thanks
From Peter
From: Emilian Bold
Sent: Friday, May 25, 2018 1:02:26 AM
To: dev@netbeans.incubator.apache.org
Subject: Re: output window coloring question
Maven is being executed as an external process which writes to a terminal.
NetBea
Hi
Am 25.05.2018 um 10:21 schrieb sgpa...@mainscreen.com:
I am currently developing a fix for a bug in a NB 8.2 plugin but I am running
into an issue regarding ProjectClassPathModifier versus
ProjectClassPathExtender. Can someone please direct me to the correct place to
ask a ques
On Fri, 25 May 2018 at 03:56 Efrem Mc wrote:
> Hi Geertjan, thanks for taking the to follow-up. I believe this
> issues on Netbeans-488 is set as a Minor defect.
>
This isn't currently a defect in NetBeans as such - code was added in a
recent PR to assert certain visual library methods are bein
I am currently developing a fix for a bug in a NB 8.2 plugin but I am running
into an issue regarding ProjectClassPathModifier versus
ProjectClassPathExtender. Can someone please direct me to the correct place to
ask a question on such an issue? Thanks.
-
Hello,
will it be possible to fix
https://issues.apache.org/jira/browse/NETBEANS-595 before release? I
added a comment so it should be straightforward for somebody knowing
about the Maven modules implementation.
Kind regards
Peter
---
Hi Stephen,
what does it mean, You "cannot get it working"? Which problems
(behaviour or exceptions) do You have exactly?
Kind regards
Peter
Am 25.05.2018 um 11:50 schrieb sgpa...@mainscreen.com:
Hi,
Can someone please direct me to the correct place for asking questions
regarding plugin d
Hi,
Can someone please direct me to the correct place for asking questions
regarding plugin devlopment?
I am having trouble contributing a fix to a bug in a third-party NB 8 plugin -
I have a fix using the deprecated ProjectClassPathExtender class but I want to
use the replacement ProjectClassPa
34 matches
Mail list logo
