Scout 3.9 nightly buildhttps://www.eclipse.org/forums/index.php/mv/msg/469018/1032673/#msg_1032673
i'm trying to install Scout 3.9 with the nightly build (http://download.eclipse.org/scout/nightly) but the installation can not be completed because of missing requirements:

]]>David Marx2013-04-03T09:29:51-00:00Re: Scout 3.9 nightly buildhttps://www.eclipse.org/forums/index.php/mv/msg/469018/1033591/#msg_1033591
I usually use a classic Eclipse SDK version that you can find at [1] (Juno 3.8.2) or [2] (Juno 4.2.2) for example. However, the following installation guide should also work for Eclipse Java Developers EPP.

To install Scout Nightly into your Eclipse IDE, first add the Scout Nightyl Updatesite [3] by using "Help -> Install New Software...".
To get a "complete" Scout incl. runtime, SDK and RAP, you should choose the features according to the picture [4].
Please verify that you have checked the box "Contact all update site during install to find required software" so that depending bundles at the Juno updatesite are used.

The "Eclipse Scout" feature that was introduced with Scout 3.9 is a so-called super-feature and contains the following sub-features:

Eclipse Scout Runtime

Eclipse Scout Runtime Testing

Eclipse Scout SDK

Eclipse Scout SDK RAP

The feature "Eclipse Scout RAP Target" contains the RAP bundles so that you can extract them to your local file system when creating a Scout project with the RAP UI.

David]]>David Marx2013-04-04T12:29:52-00:00Re: Scout 3.9 nightly buildhttps://www.eclipse.org/forums/index.php/mv/msg/469018/1036311/#msg_1036311
I get the following errors:

From those marked in green, I assume that I first need to uninstall Scout 3.8.1, is this correct?
Will this automatically resolve the unresolvable dependencies marked in red, as well, or do I need to do anything else to fix this?

From those marked in green, I assume that I first need to uninstall Scout 3.8.1, is this correct?

Hi Urs,

Yes, your assumption is absolutely correct. Please have a look at [1], in your case especially at bug [2].
In summary, feature ids were renamed in Scout 3.9, that's why an update from Scout 3.8 to Scout 3.9 does not work anymore.
That was the reason why I used an Eclipse Classic SDK version (i.e. without a previous version of Scout installed) for my above guide.

The red part should not appear if you use an Eclipse version where Scout is not installed.

in the Scout View I open the Shared tree and select "Icons", this gives me the "Open Icons Editor" link in the "Scout Object Property" view. Clicking on that link shows me an empty table without any icons whatsoever.
The dropdown list for the IconId property on forms (and other Scout elements) still work, though. Is this a known issue when migrating from Scout SDK 3.8.1 to 3.9.0 (i.e. can I fix this myself), or is this a bug introduced as part of the Kepler SDK?

adding a new Form to my client in the past distributed the files as follows:
- org.eclipse.minicrm.client.ui.forms.MyForm
- org.eclipse.minicrm.shared.security.*MyPermission
- org.eclipse.minicrm.shared.services.process.IMyService
- org.eclipse.minicrm.shared.services.process.MyFormData
- org.eclipse.minicrm.server.services.process.MyService
Since upgrading to the nightly build these files are placed as follows:
- org.eclipse.minicrm.client.subpackage.MyForm
- org.eclipse.minicrm.shared.subpackage.*MyPermission
- org.eclipse.minicrm.shared.subpackage.IMyService
- org.eclipse.minicrm.shared.subpackage.MyFormData
- org.eclipse.minicrm.server.subpackage.MyService
In my eyes, this is a step backwards, as I liked having the created files grouped by "topic", not by "form/subpackage". I could see how having the "subpackage" part added below the "topic" packages (i.e. below client.ui.forms, shared.permissions, shared.services.process, server.services.process), but adding them on the top level seems nonsenical to me. Is this intentional or a bug? Can the old behaviour be restored somehow?

If neither of the above is intended behaviour, do you want me to open bugs for those two issues?]]>

A short summary:
- The icons editor was a bug that has been fixed. Thank you for pointing that out!
- The location of new java files is intentional. We think you get a better grouping of what belongs together than when grouping by class type. there is no possibility to revert to the old behavior.

regards,
m]]>Matthias Villiger2013-04-15T11:39:58-00:00Re: Scout 3.9 nightly buildhttps://www.eclipse.org/forums/index.php/mv/msg/469018/1042224/#msg_1042224
Thanks for your responses (I saw them in the bugs). The new way of grouping will take a little getting used to. I saw the fix for the icons editor. When I tried Help->Check for Updates this morning, Eclipse told me there weren't any, so I'll check again next week (I'll be out of the office for the rest of the week) and post a comment to the bug when I have verified the fix.]]>Urs Beeli2013-04-16T06:23:20-00:00Re: Scout 3.9 nightly buildhttps://www.eclipse.org/forums/index.php/mv/msg/469018/1042272/#msg_1042272
Urs Beeli wrote on Tue, 16 April 2013 02:23

When I tried Help->Check for Updates this morning, Eclipse told me there weren't any, so I'll check again next week

Hi Urs,

There are currently some problems with the Eclipse Hudson [1] so there haven't been any Nightly Builds since April 14th.
If Hudson is up and running again, the latest changes from Matthias should be included in the build.