I'm new(ish) to Java/Netbeans/ControlsFX. I know about Javadoc and would like NetBeans to show me javadoc for ControlsFX. I see the online version of the docs for ControlsFX but that defeats (at least part of) the purpose of using an IDE? I know how to add the doc zip file in NetBeans but I don't see the doc file for ControlsFX.
Am I missing something?
Found this lately. ControlFx java doc. You can manipulate the version number at the end of the url to get to page of any other version of the doc if it is in existence. Download the jar version on that page to use it locally controlsfx-version-javadoc.jar. Then you can add the jar in your netbeans Javafx project.
Related
My builds broke when I moved to Gradle 5 becasue Gradle v5.2 bundles with Groovy v2.5.4. These projects use the dynamic support build for Groovy.
Invoke dynamic support
groovy-all-2.5.4-indy.jar
This file is not being resolved for either JCenter or MavenCentral. However I did find a copy here:
Sonatyoe repo: https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/2.5.4/
groovy-2.5.4-indy.jar
but no groovy-all-2.5.4-indy.jar
I am not sure what can be done for Gradle to 'resolve' this file and actually find it.
Can someone tell me were I should be getting this JAR file from?
I'm using coordinates: "org.codehaus.groovy:groovy-all:2.5.4:indy"
Is that still the correct expression?
Is this a bug or am I just looking in the wrong places (see #1)?
Im ny build.gradle I was using jcenter() and tried changing that to mavenCentral().
Neither option came up with the JAR in question.
A final wrinkle is that we run an instance of Nexus. Is there some way to force Nexus to go outside and look-for this JAR?
This is not entirely conclusive, but it seems that the -indy jar was there in groovy versions prior to 2.5.0 because those versions supported java versions prior to 1.7.
The indy jar was there so that you could optionally enable support for the invokedynamic instruction introduced in java 1.7 while still supporting java versions prior to 1.7 which did not include invokedynamic (groovy docs for indy).
It seems that groovy 2.5 bumped the minimum jdk requirement to, quote:
JDK requirements changes
Groovy 2.5 requires JDK8+ to build and JDK7 is the minimum version of the JRE that we support.
(from http://groovy-lang.org/releasenotes/groovy-2.5.html)
which would make this whole duality of supporting both invokedynamic and without unnecessary.
So my guess would be that they just dumped the indy jar and always include the invokedynamic instruction in the normal groovy jar file set as the required jdk versions will always include it.
I have successfully implemented some ColumnRenderer classes for adapting java.time types for display with Vaadin Grid. See source code here if curious.
Now I would like to publish these as an Add-On in the Vaadin Directory. I read these directions in the Vaadin guide, but they seem incomplete and outdated.
There is discussion of exporting from Eclipse which is not relevant to me (using IntelliJ) and is probably old-school now that Vaadin team has moved to thorough support of Maven.
The "Manifest" is mentioned but not documented with no mention of file name nor file location. No documentation on format or individual values.
I found a manifest file MANIFEST.MF in my Maven-created project, but it is in a format of key+colon+value while the manifest shown in that documentation seems to be XML format. Which format is currently correct?
My found MANIFEST.MF file contains variable names such as ${Vaadin-Addon} and ${Vaadin-License-Title} and ${Implementation-Version}. Where are these defined?
I have a plugin which is custom built for Jira 6.x and I want to make the same plugin to work for Jira 7.x. What are the ways to do this?
Say the only resource I have is the .jar plugin file which has all the information about classes, dependencies, related to old version of jira.
If I make changes to the pom.xml file and upload the addon to jira, will it work with Jira 7.x?
Error From Log:
/rest/issueNav/1/issueTable [c.atlassian.ozymandias.SafePluginPointAccess] A LinkageError indicates that plugin code was compiled with outdated versions.Unable to run plugin code because of 'java.lang.AbstractMethodError - null'.
Thank You.
There are API changes which requires source code changes, some details here:
https://developer.atlassian.com/jiradev/latest-updates/preparing-for-jira-7-0/jira-7-0-api-changes
Usually I learn new frameworks by going through each line of the source code
I have spring 3.2 in my eclipse project but java aspect classes are not included.
I tried to decompile them but they look messed up
Any where can I find them?
If you have your code a maven project, and it is setup well, it will download the sources automatically. So I recommend you setup your project in maven.
you can find here a good configuration of a spring 3.2 project with maven,
https://github.com/andonescu/springmvc-freemarker
and use maven to download source code, see this link to help you
Maven – Always download sources and javadocs
On http://code.google.com/p/ksoap2-android/wiki/NeedHelp
It says Android Development Toolkit (Eclipse plugin) based environment you will have to manually download the source and javadoc jar files from the assembly project.
I have all ready attached the source for my javaSDK (so I believe I know what I'm doing), but I cant find where the source code for ksoap2-android is even given that download link to the assembly project.
What am I missing? Can someone tell me exactly what i should be downloading ?.
Here is the exact link, attaching in Eclipse hope fully is as easy.
https://github.com/mosabua/ksoap2-android/downloads