See below: > Great work on the new installer! I really like the separation between the > "tool to install" and the "project WS to provision". > > However, I have one small problem, it's not working at all ;(. > > I picked Eclipse Standard > > So far I've only ever tried with "Eclipse Standard/SDK" - "Latest (Luna)". > What version did you select? >
Yes, this is the one I tried too. > > > and then the Oomph project. The tooling gets provisioned, although > Eclipse launches about 1/2 way through the provisioning steps (which is > really strange). > > What do you mean by "launches half way..."? Was there an error message on > the Progress page of our Installer? Any suspicious ErrorLog messages? Maybe > you can attach your eclipse/configuration/org.eclipse.oomph.setup/setup.log > file. > This appears to be a problem with the way the log window is rendered. The 'Finish' button doesn't become active until all the log messages are written, but Eclipse will launch before this. In my case, it took 45 minutes to completely write all the log messages. That is, Eclipse launched, and for 45 minutes the window kept rendering messages (mostly about 'Installing XXX'). I've filed [1] for this. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=435851 > But no WS is setup (not repositories cloned, targets set, etc..). > > This seems to be the bigger issue though. After it completed, my WS wasn't provisioned at all. I tried different settings from where to get Oomph from (anonymous git, ssh, etc..) and I tried putting it in different places (<user_home>/git/..., or in my WS). In call cases, no git clone was performed, not target was setup, etc... I've filed [2] for this. [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=435852 > > The build stamp for the setup tool is 20140526-1144, which is actually > 'in the future' for me :-). > > I think that's caused I'm working in your near future :P > > Tycho seems to use (local) Git commit times to determine the > plugin/feature version qualifiers without converting these timestamps to > the timezone of the build machine. I wonder how other projects deal with > this problem. I fear it can even become a real problem in rare cases, e.g., > Europe modifies and kicks a build (in Canada), then, an hour later Canada > modifies and kicks a build. Wouldn't the version qualifier go *down* by ~5 > hours then?! > Yes, this does seem to be a problem -- and if we ever hit it, it would likely cause a lot of confusion. I thought everything was converted to GMT (at least for the platform build) but I could be wrong. If @pascal is on this list, he might know. If not, maybe this is a good question to raise at the next AC meeting (just to see if other projects are having this problem). Cheers, Ian > Cheers > /Eike > > ---- > http://www.esc-net.de > http://thegordian.blogspot.com > http://twitter.com/eikestepper > > > > Cheers, > Ian > > -- > R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 > http://eclipsesource.com | http://twitter.com/eclipsesource > > > _______________________________________________ > oomph-dev mailing > [email protected]https://dev.eclipse.org/mailman/listinfo/oomph-dev > > > > _______________________________________________ > oomph-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/oomph-dev > > -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource
_______________________________________________ oomph-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/oomph-dev
