In earlier systems, I did hack profile.ijs to load my personal profile (not adding anything to profile.ijs other than the link). This was a pain because moving from j501b to j502a then j503bbeta, j503cbeta, j503ebeta, finally to j503a, then j504 then j601 and so forth required that I look at and modify profile.ijs each time...
I was very happy when j602 introduced profilex.ijs and I could stop having the tedium of analyzing then hacking the system profile.ijs. Now it seems like my happiness only lasted one release.... (unless there is an official way to set paths for things like j701-user). I too am for minimizing complexity, but loosing profilex.ijs seems like a step in the wrong direction for that goal... At 12:15 +1200 2010/06/10, Sherlock, Ric wrote: > > From: Joey K Tuttle >> Sent: Thursday, 10 June 2010 07:15 >> >> On the negative side, jconsole doesn't work (the way I want it to) >> out of the box. My problem has to do with profile.ijs - >> >> The previous mechanism of profilex.ijs as derived from >> profilex_template.ijs seems to have been abandoned. This has two >> damaging effects on my normal setup in OSX - one is the ability to >> have the Jxxx-user directory located in Documents rather than at my >> user root (I like to avoid clutter!) >> >> The other is bringing in my ancient profile - the profile.ijs seems >> to be saying that startup.ijs is the tool, and I guess that was >> available before along with profilex.ijs, but I never used it. This >> is an issue in both OSX and Linux. >> >> I don't mind adapting, but hope that things will stabilize so that >> updating j doesn't cause the environment to break... By the way, my >> old profile.ijs stuff is also missing, of course, in the browser >> session and the j701-user directory is plopped into user root.... I >> think that the move in j602 to avoid the need for hacking profile.ijs >> was a good one - is there a reason for abandoning profilex.ijs ?? >> >> What is the recommended way to get the previous behaviors in jconsole? > >With regards profile.ijs, profilex_template.ijs, profilex.ijs: >I think the thinking behind the removal of profilex.ijs goes >something like this: > >Because j701 will use JAL to do much more of its updating than in >previous versions, users won't be reinstalling their J installations >as much and therefore it is not so important to have a mechanism for >retaining system folder configurations between installs. It is >therefore possible to removing the complexity of profilex.ijs with >little impact. If you want to customize the location of your system >folders you would now do so directly in profile.ijs. > >I've reserved judgement for the time being - I'm all for reduced >complexity, but I liked the robustness that profilex.ijs provided. > >With regards to where to put your other "starting configuration >stuff", I think that you are correct that the intention is for you >not to put anything in profile(x).ijs that isn't to do with setting >paths to system folders. As you surmise "other stuff" should be in >~config/startup.ijs. > >For j602 jconsole loaded the startup file >"~config/startup_console.ijs" if it was present, while jwd loaded >"~config/startup.ijs". In the current j701 beta I think that all >front ends are presently loading ~config/startup.ijs > >---------------------------------------------------------------------- >For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
