Re: Gradle project created by Grails has error on load

2018-04-16 Thread Paul Franz
My guess is that Gradle 3.4.x does not recognize the new java version. 
From Java 1.0 to Java 8.0. The version string has always been 1.x. So 
for JDK 8 the version string is actually 1.8 not 8.0. In JDK 9, this was 
change (URL: 
https://blogs.oracle.com/java-platform-group/a-new-jdk-9-version-string-scheme 
). So I think this requires the use of either JDK 8 or a newer version 
of Gradle. The latest being 4.6 .


Paul Franz
Senior Principal Applications Engineer
Oracle Transportation Management
Phone  #: 1-610-729-3347
Skype Id: PaulPFranz


On 16 Apr 2018, at 2:18, Matthias Barmeier wrote:


Hi all,

I have created a Gradle project with grails 3. The I try to load it i 
get this exception:


Stack trace:
org.gradle.tooling.GradleConnectionException: Could not create an 
instance of Tooling API implementation using the specified Gradle 
distribution 
'https://services.gradle.org/distributions/gradle-3.4.1-bin.zip'.
	at 
org.gradle.tooling.internal.consumer.loader.DefaultToolingImplementationLoader.create(DefaultToolingImplementationLoader.java:110)
	at 
org.gradle.tooling.internal.consumer.loader.CachingToolingImplementationLoader.create(CachingToolingImplementationLoader.java:44)

….
   Caused by: java.lang.IllegalArgumentException: Could not determine 
java version from '9.0.4'.

at org.gradle.api.JavaVersion.toVersion(JavaVersion.java:70)
at org.gradle.api.JavaVersion.current(JavaVersion.java:80)
	at 
org.gradle.internal.jvm.UnsupportedJavaRuntimeException.assertUsingVersion(UnsupportedJavaRuntimeException.java:29)


What means Could not determine java version from ‚9.0.4‘ isn’t 
netbeans 9 for Java 9 ?


Ciao
Matze


-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Re: Programmatically select a node after being created

2018-04-16 Thread Marco Rossi
Ok, I decided to subclass my beanTreeView.

public final class LibraryViewerTopComponent extends TopComponent implements 
ExplorerManager.Provider {
private final ExplorerManager explorerManager = new ExplorerManager();
private BeanTreeView beanTreeView;

private final class LibraryTreeView extends BeanTreeView implements 
TreeModelListener {

@Override
protected NodeTreeModel createModel() {
NodeTreeModel model = super.createModel();
model.addTreeModelListener(this);
return model;
}

@Override
public void treeNodesInserted(TreeModelEvent e) {
Object[] children = e.getChildren();
if (children.length > 0) {
TreePath tp = e.getTreePath();

tree.setSelectionPath(tp.pathByAddingChild(children[0]));
}
}

@Override
public void treeNodesRemoved(TreeModelEvent e) {
// NOP
}

@Override
public void treeNodesChanged(TreeModelEvent e) {
// NOP
}

@Override
public void treeStructureChanged(TreeModelEvent e) {
// NOP
}
}

public LibraryViewerTopComponent() {
initComponents();
// initialize data model
…
…
}

private void initComponents() {
beanTreeView = new LibraryTreeView();
setBackground(java.awt.Color.white);
setOpaque(true);
setLayout(new java.awt.BorderLayout());
add(beanTreeView, java.awt.BorderLayout.CENTER);
}

@Override
public ExplorerManager getExplorerManager() {
return explorerManager;
}
}

It works but I appreciate any other suggestions/comments.


> Il giorno 14 apr 2018, alle ore 08:56, Emilian Bold 
>  ha scritto:
> 
> I'm also curious about this.
> 
> It seems to me the API is somewhat incomplete, specifically in the async 
> area. We have no Future to listen to and react. So, it's all fire-and-forget 
> when often times you want to do something after the node has been created / 
> shown.
> 
> In your case you control the beanTreeView so as a last resort I guess you 
> could subclass the view and listen on the JTree directly (it's a protected 
> field). Still... it's ugly.
> 
> Not really sure if there's some other way. If you do find it, please come 
> back on the mailing list and let us know.
> 
> --emi
> 
> ‐‐‐ Original Message ‐‐‐
> 
> On 13 April 2018 12:28 PM, Marco Rossi  wrote:
> 
>> Hi there,
>> 
>> can someone tell me how to programmatically select a node in my beanTreeView 
>> (backed up by an explorerManager) after being created in my data model? I 
>> tried to do this in parent node, by adding a NodeListener like this:
>> 
>> parentNode.addNodeListener(new NodeAdapter() {
>> 
>> @Override
>> 
>> public void childrenAdded(NodeMemberEvent ev) {
>> 
>> if (ev.isAddEvent()) {
>> 
>> final Node node = ev.getNode();
>> 
>> SwingUtilities.invokeLater(new Runnable() {
>> 
>> @Override
>> 
>> public void run() {
>> 
>> try {
>> 
>> LibraryViewerTopComponent.findInstance().getExplorerManager().setSelectedNodes(new
>>  Node[] { node });
>> 
>> } catch (PropertyVetoException ex) {
>> 
>> MessageBox.error(ex);
>> 
>> }
>> 
>> }
>> 
>> });
>> 
>> }
>> 
>> }
>> 
>> });
>> 
>> When I create a new item in my data model, the ChildFactory refreshes 
>> asynchronously itself and creates a new node representing the data. 
>> Unfortunately this does’t work because the child node may be not exists yet 
>> in the explorer manager. Any suggestions?


-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Gradle project created by Grails has error on load

2018-04-16 Thread Matthias Barmeier
Hi all,

I have created a Gradle project with grails 3. The I try to load it i get this 
exception:

Stack trace:
org.gradle.tooling.GradleConnectionException: Could not create an instance 
of Tooling API implementation using the specified Gradle distribution 
'https://services.gradle.org/distributions/gradle-3.4.1-bin.zip'.
at 
org.gradle.tooling.internal.consumer.loader.DefaultToolingImplementationLoader.create(DefaultToolingImplementationLoader.java:110)
at 
org.gradle.tooling.internal.consumer.loader.CachingToolingImplementationLoader.create(CachingToolingImplementationLoader.java:44)
….
   Caused by: java.lang.IllegalArgumentException: Could not determine java 
version from '9.0.4'.
at org.gradle.api.JavaVersion.toVersion(JavaVersion.java:70)
at org.gradle.api.JavaVersion.current(JavaVersion.java:80)
at 
org.gradle.internal.jvm.UnsupportedJavaRuntimeException.assertUsingVersion(UnsupportedJavaRuntimeException.java:29)

What means Could not determine java version from ‚9.0.4‘ isn’t netbeans 9 for 
Java 9 ?

Ciao
Matze

smime.p7s
Description: S/MIME cryptographic signature