| [technology-pmc] Work with discussion/approval required for gxt-all.css Version: 2.3.1 |
|
PMC Members, we have another "works with" to consider. Please add your comments to the discussion and/or approve. Thanks, Wayne -------- Original Message --------
http://dev.eclipse.org/ipzilla/show_bug.cgi?id=8210 Wes Johnson <wes.johnson@xxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|awaiting_pmc |new --- Comment #17 from Wes Johnson <wes.johnson@xxxxxxxxxxxx> 2014-05-07 14:09:24 --- Comments inline: I'm not comfortable with this. My understanding is that the Kura UI makes absolutely no sense without this library being present. WES> This is true - but the same is true for the GXT jar which was already approved as a workswith dep. This is the required CSS to go with GXT. How fundamental to the project is the UI? AFAICT, its not mentioned in the scope, so I'm guessing that it is not fundamental, but need some assurances. WES> Not very. Kura can be configured multiple ways including hand modification to an XML file or configuration via MQTT messages. The UI is a nice to have that makes local configuration changes easier. Also we are actively working on a replacement for the GXT dependency (via Vaadin) which shows this is truely a 'workswith' in that there will be multiple options. The project currently has nothing in its downloads. Does the notion of downloads make sense for Kura? WES> I'm not sure understand this. The 'download' will occur via a configuration change in the build. See below for more details. Can Kura be built without the UI? Can somebody pull in the Kura git repository and run some build script which does not pull in GXT? WES> The plan is for the default build to not include the UI. We use Maven+Tycho for Kura builds. So, for automated builds via the Eclipse build server we will build Kura and provide Kura releases w/o the UI. However, we will include the code developed by Kura committers in the source of Kura. In addition, we'll host the GXT workswith dependencies in a third party maven repo. So, if one wanted the UI, they would simply pull in the source, switch a flag in a pom, and run 'mvn clean install'. The switching of that flag and running the build will pull in the workswith (GXT) dependencies from the third party site and produce a Kura build with the UI. So, at no point will Eclipse repositories ever host these deps either in binary or source format. Furthermore, Kura will build run and be usable without the UI by default. We are only trying to include it as a 'nice to have' for those that build from source. -- Configure CQmail: http://dev.eclipse.org/ipzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the CQ. You are watching someone on the CC list of the CQ. You are watching the assignee of the CQ. --
Wayne Beaton Director of Open Source Projects, The Eclipse Foundation Learn about Eclipse Projects  |