Is there a status page for migration of plugins from netbeans.org to
netbeans@apache? Specifically looking for the gradle plugin.
Thank you so much!
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For a
Happy to. Also put together a quickie helloworld.
https://github.com/hanasaki/helloworld-gradle
On 8/8/18 4:06 AM, Geertjan Wielenga wrote:
Hi all,
Now that the dust around the first Apache NetBeans release is settling and
we're converging around a tentative release cycle, maybe we could look
May I also suggest the following pattern for future release consideration?
Maven'like / semver.org : using X.Y.Z
* The netbeans "product" would be X.Y with any value for Z being 100%
compatible with X.Y
* Thus an executable netbeans jar of netbeans-x.y.z.jar and maybe
netbeans-x.y.jar whic
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
Suggestion:
- no need for plugin registry and hashes in plugin registry
- use the maven/gradle resolver lib for plugin dependencies
: reuse repo libs from mvn, gradle or Arquillian
- publish the plugin in standard mvn central
- if there is need of ex
