[
https://issues.apache.org/jira/browse/NETBEANS-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269602#comment-17269602
]
Matthias Bläsing commented on NETBEANS-5109:
--------------------------------------------
[~neilcsmith] at this point the the nbjavac repository fixes the distribution
problem by using the maven central infrastructure. Nothing more, nothing less.
We currently have:
# the updatecenters module, that in addition to the regular update centers
also holds an internal update center, that can install 6 NBMs: OpenJFX for
Linux, mac OS and Windows and the nb-javac modules
# the installed modules themselves hold only minimal code and fetch the main
content via an "*.external" file embedded in the module
# the "*.external" file points either to Maven Central (JavaFX) or Apache
NetBeans Controlled Infrastructure (netbeans.osuosl.org or hg.netbeans.org for
nbjavac)
The update to nbjavac will enable movement to maven central and then a followup
PR against netbeans can update the external dependencies to point to maven
central. Step 3 mentioned above is unified to load dependencies from maven
central.
> Remove distribution of nbjavac from apache controlled infrastructure
> --------------------------------------------------------------------
>
> Key: NETBEANS-5109
> URL: https://issues.apache.org/jira/browse/NETBEANS-5109
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
> Affects Versions: 12.3
> Reporter: Matthias Bläsing
> Assignee: Matthias Bläsing
> Priority: Blocker
>
> The ASF has a pretty clear opinion about the handling of the GPLv2-CPE. There
> might be an option to distribute it, but not out of the box. After the
> transition of NetBeans from oracle to the ASF there was a timeframe were use
> of the Oregon State University was ok, as the transition was happening. I
> think we stretched that limit to the max and thus I consider this a blocker
> for the next release. The nbjavac needs to be moved of ASF controlled
> infrastructure.
> There are various options:
> - Oracle could publish nbjavac to maven central
> - Oracle could provide a custom updatecenter distributing the nbjavac
> - Oracle could relicense javac
> - Apache NetBeans could switch to the eclipse java development tools
> Not all of these options are realistic, but publishing to maven central is
> perfectly doable.
> I'll mark this as a blocker for next release, so it is not ignored.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
