Community
Participate
Working Groups
We need to figure out a way to get the COSMOS demo on the web site. This is what we have currently: 1. a few different Wiki pages that describe a time-consuming, error-prone approach for building up a live end-to-end scenario 2. a zip file that can be extracted and run almost immediately, but contains code we can't legally redistribute on our side (e.g. Dojo & Tomcat) I am wondering if a middle ground approach would be workable. If we could remove dojo and Tomcat from our zip file, perhaps we can provide the current zip file, and then give simple instructions for downloading Dojo and Tomcat into that extracted structure. This is assuming that we can include all of Eclipse 3.3 in our zip. If not, then that would be one extra step, and one more thing the user has to do and might mess up. I don't know enough on the legalities of that to say, but I would think the fact that our site is on eclipse.org would help our chances.
A potential solution for this issue is to write an Ant script to pull down the right versions of Tomcat and Dojo so we don't have to bundle those. I have a question in to the Eclipse people on bundling Eclipse as part of our zip file. But I think an Ant script would make the setup still pretty painless, and Ant will be available because of Eclipse being part of the zip file. We should then be easily able to put the demo zip file up on the Eclipse site once that script is complete.
Got this info from Bjorn: "As long as the sample bat files and ant scripts are checked into the Eclipse CVS, yes, it sounds good. (In other words, the entire distro needs to be open source.)" So basically we would just need to get the scripts, etc. into one of our build/releng projects, and make sure they have all the appropriate copyrights, etc.
(In reply to comment #2) > Got this info from Bjorn: > > "As long as the sample bat files and ant scripts are checked into the Eclipse > CVS, yes, it sounds good. (In other words, the entire distro needs to be open > source.)" > > So basically we would just need to get the scripts, etc. into one of our > build/releng projects, and make sure they have all the appropriate copyrights, > etc. > In the past this was specifically forbidden in TPTP. We were not allowed to place automatic download links or scripts to Apache Muse for example until Muse was legally approved because Eclipse Legal told us that we cannot specifically endorse another unapproved open source project. We should check with the Eclipse Legal folks - Janet Campbell and Sharon Corbett on the idea of the script.
(In reply to comment #3) > We should check with the > Eclipse Legal folks - Janet Campbell and Sharon Corbett on the idea of the > script. Janet Campbell was the one I had emailed about it originally. She cc:'d Bjorn on her initial reply, and then he replied with the answer I included and cc:'d her. She voiced no objection to what he said. However, we need to be sure our internal legal team is also ok with it... I have an email out that should get some attention next week.
We should investigate the work to create a "cosmos setup wizard", e.g. simple RCP app. A more direct approach may be something like the "setConfig" command of the TPTP agent controller.
I agree with Mark that we need to make something easy to use that will help people over this hurdle. It is clear that COSMOS is not the only Eclipse project these days with a requirement to work with components that we don't or can't ship. Perhaps a common approach will eventually emerge among the Eclipse community but for now, it is encouraging that Eclipse Legal is more accepting of the requirements to loosely integrate with other "runtime" components.
The packaging for i8 has been addressed. We have a zip that include all runtime components required to run the end-to-end demo. The demo zip file includes a program that can be used to configure the COSMOS components with settings specific to the installation environment. There is an SDK zip that includes plugins required in the development environment, with necessary dependency plugins. The setup of the dev environment is much easier than before. There will be a follow up enhancement for i9 to revisit the packaging design.
QA has verified the zip that contains the e2e demo.
please mark verified defects using the VERIFIED status by clicking the radio button
closing
