Dear Netbeans team,
I do not get a point to add newer and newer Java support especially as it is
not LTS as I think that it should be
higher priority to have complete package as known before Apache times.
So I think that it takes too long.
Even I do not want to open issues about bugs
Maybe consider A="netbeans-parent" In the absence of OSGI, "parent" is
common and ambiguous across multiple projects. Example: I have been on
projects that ended up with transitive dependencies of multiple
"utility.jar" from different groups. While less likely with a parent,
IMHO still a col
Hi,
It's ok for me. I hope that others part of the pom are correct. I will prepare
a new parent.
I will also refactor the mavenutilities to follow the rules (package were from
codehaus and need change anyway, and coordinate).
For the Apache NetBeans artefacts, RELEASE90,RELEASE100 as they wi
On 18/02/2019 17.54, Eric Barboni wrote:
Hi,
On the coordinate, I thought that we were allowed to keep org.netbeans as we
have done some release on org.netbeans.html for html4j.
The usage of org.netbeans for html4j was primarily (only) OK to provide
transitional compatibility with existing
Hey Mark,
Am Montag, den 18.02.2019, 19:10 +0100 schrieb Mark Herkrath:
> at least under Windows 10 and Maven 3.5.4, the handy Check Out... feature
> at [Maven project] > Dependencies > [artifact] > View Artifact Details >
> Project > Source Control Management > Check Out... is broken. After filli
Dne pondělí 18. února 2019 16:55:52 CET, Ate Douma napsal(a):
> This *new* maven artifact is using Maven groupId: org.netbeans.maven.
> Which IMO can and should at least use the org.apache.netbeans prefix.
> There is no existing usage, yet, so *not* using the org.apache. prefix
> as expected seems
Laszlo -
Thanks for your reply. I don't think either is a critical for me...the
excludes in our project include some sample files that wouldn't normally
compile, so I get the nice red exclamation point, but the gradle build still
works correctly, so it is not really an issue.
Mike
-Ori
Hi,
at least under Windows 10 and Maven 3.5.4, the handy Check Out... feature
at [Maven project] > Dependencies > [artifact] > View Artifact Details >
Project > Source Control Management > Check Out... is broken. After filling
the dialog and pressing CheckOut, the Maven error "The goal you specifi
Dear Mike,
Well, I think it is Ok to report these here.
Yes, it is true that excludes as well as includes are not supported by
right now, I've created
https://issues.apache.org/jira/browse/NETBEANS-2136 for that.
For the other one, it is good to encounter non-default project layouts
from ti
Hi,
On the coordinate, I thought that we were allowed to keep org.netbeans as we
have done some release on org.netbeans.html for html4j. We ask infra to have
the right to publish on this coordinate.
org(.apache).netbeans:parent:1 can make a better coordinate than
org(.apache).netbeans.maven:net
Please redirect me if appropriate...
I am using the gradle support new in 11.0. I am noticing the following:
* It appears the exclude options are not being applied:
sourceSets {
main {
java {
srcDir 'JavaV2/Src'
srcDir 'JavaV2/API/Src'
srcDir 'JavaV2/Fedex/Src'
Sorry for the (too) late response, but I only just now noticed this
vote, and the currently running subsequent vote on general@.
However I have some objections to the proposed parent pom with respect
to the used maven coordinates, which make me inclined to vote -1 on
the vote at general@, but fir
12 matches
Mail list logo
