Hey,
there is a Long discussion going on here:
https://issues.apache.org/jira/browse/NETBEANS-1802
In short, I have the problem that NetBeans, forces me into one project type
(here maven) when there are two or more files/folders of different Project
types (pom.xml, package.json, etc.). So my
Hi,
With the DNS upgrade the mavenutilties has new home
http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/index.html and
the mojohaus team put all former repository has readonly so the new pointer
his https://github.com/apache/incubator-netbeans-mavenutils.
Fill free improve site.
> At the end, I need to find a proper solution for that, I can’t be the only
> one who has this problem. I already have it with 3 projects.
You are literally the only one to have ever complained about this. At
least from what I can remember.
Having a user-configurable priority for project types
Hello,
NetBeans has a Scala support plugin which is, unsurprisingly, written in Scala.
It would be quite awesome if our language plugins would be written in
the specific language (and basically self-hosted in a way).
This might give specific developers a better way to contribute, since
ebarboni commented on issue #9: Add a parent for the conveniences libraries
URL:
https://github.com/apache/incubator-netbeans-mavenutils/pull/9#issuecomment-456404508
The parent artefact that we may release and use as parent for all the
netbeans artefacts (api,clusters,modules,externals)
ebarboni commented on issue #10: Allow possibility to use a parent to populate
with
URL:
https://github.com/apache/incubator-netbeans-mavenutils/pull/10#issuecomment-456404012
Hi as stated in the mailiing list in early december this maybe a solution to
have nice artefact populated
Many congratulations for this awesome work, can’t wait to try it out. :-)
Gj
On Tuesday, January 22, 2019, Laszlo Kishalmi
wrote:
> Dear all,
>
> I've merged the Gradle Support into master. The first build with that:
>
> https://builds.apache.org/job/incubator-netbeans-linux/975/a
>
Awesome...
Will try to check it out
-Sven
On Tue, Jan 22, 2019 at 9:09 PM Geertjan Wielenga
wrote:
> Many congratulations for this awesome work, can’t wait to try it out. :-)
>
> Gj
>
> On Tuesday, January 22, 2019, Laszlo Kishalmi
> wrote:
>
> > Dear all,
> >
> > I've merged the Gradle
Dear all,
I've merged the Gradle Support into master. The first build with that:
https://builds.apache.org/job/incubator-netbeans-linux/975/artifact/nbbuild/
We need to add some components to our JIRA, unlike for Maven I'm
thinking of one component called: *gradle-support* and later on
For early adopters see the issue and workaround when using Java 11:
https://issues.apache.org/jira/browse/NETBEANS-1970
On 1/22/19 12:12 PM, Sven Reimers wrote:
Awesome...
Will try to check it out
-Sven
On Tue, Jan 22, 2019 at 9:09 PM Geertjan Wielenga
wrote:
Many congratulations for
Thank you, Laszlo!! This is so cool!!
El 22/01/2019 a las 21:08, Laszlo Kishalmi escribió:
Dear all,
I've merged the Gradle Support into master. The first build with that:
https://builds.apache.org/job/incubator-netbeans-linux/975/artifact/nbbuild/
We need to add some components to our
Actually, I have had mutliple complaints about this in the past. Almost
always (the exceptions were, when there are multiple build tools
temporarily, due to porting between build tools), the issue was the
presence of the `package.json` (implying a particular project type). That
said, I don't know
12 matches
Mail list logo
