Meta tags:

Headings (most frequently used words):

june, 2013, is, blog, wednesday, friday, tuesday, 2011, eclipse, democamp, in, poznan, eclipser, october, 2014, 28, march, 20, 2012, it, really, simple, november, 29, monday, may, 30, rapid, course, links, writers, archive, workspace, unsaved, changes, mystery, demystified, summary, after, poster, done, coming, ignore, optional, compile, problems, now, available, with, m6, time, to, say, goodbye, very, interesting, bug, report,

Text of the page (most frequently used words):
the (76), #eclipse (53), you (42), and (33), that (28), workspace (24), core (22), org (21), this (18), resources (16), for (14), will (14), plug (14), build (13), your (12), java (12), #unsaved (11), was (11), with (10), have (10), internal (10), true (10), june (9), not (9), changes (8), szymon (8), one (8), are (8), change (8), after (8), can (8), see (8), which (8), november (7), blog (7), posted (7), time (7), warning (7), save (7), may (6), ptaszkiewicz (6), comments (6), from (6), problems (6), like (6), option (6), find (6), error (6), event (6), some (6), during (6), file (6), session (6), march (5), october (5), krzysztof (5), daniel (5), more (5), bug (5), very (5), ibm (5), poznan (5), work (5), but (5), want (5), any (5), all (5), new (5), because (5), there (5), democamp (5), part (5), events (5), february (4), 2013 (4), 2014 (4), chris (4), our (4), page (4), just (4), since (4), know (4), source (4), would (4), following (4), what (4), next (4), already (4), now (4), then (4), good (4), ignore (4), compile (4), auto (4), generated (4), code (4), done (4), out (4), something (4), here (4), enable (4), trace (4), stop (4), resource (4), snapshot (4), external (4), libraries (4), run (4), asked (4), notificationmanager (4), savemanager (4), april (3), july (3), august (3), september (3), december (3), january (3), 2011 (3), than (3), years (3), between (3), could (3), how (3), say (3), once (3), get (3), yes (3), available (3), project (3), optional (3), warnings (3), without (3), ever (3), join (3), wednesday (3), most (3), first (3), although (3), example (3), startup (3), searchable (3), previous (3), exit (3), debug (3), additional (3), notifyjob (3), message (3), annoying (3), down (3), recover (3), 2012 (2), mystery (2), demystified (2), posts (2), older (2), report (2), interesting (2), should (2), start (2), writing (2), post (2), support (2), been (2), almost (2), entire (2), kind (2), university (2), technology (2), main (2), help (2), their (2), many (2), based (2), even (2), those (2), never (2), had (2), enough (2), open (2), share (2), please (2), thank (2), only (2), jdt (2), every (2), person (2), don (2), tuesday (2), answer (2), few (2), turn (2), folder (2), compiler (2), errors (2), great (2), who (2), noteworthy (2), preferences (2), looked (2), view (2), sure (2), when (2), left (2), about (2), friday (2), let (2), people (2), showed (2), were (2), options (2), data (2), using (2), normally (2), look (2), txt (2), line (2), where (2), problematic (2), ins (2), means (2), whenever (2), ask (2), content (2), operation (2), delta (2), happened (2), culprit (2), need (2), quite (2), full (2), lang (2), runtimeexception (2), scheduling (2), jobs (2), job (2), notifications (2), tracing (2), did (2), saying (2), modified (2), knowledge (2), requested (2), semi (2), cases (2), worker (2), caused (2), power (2), badly (2), written (2), way (2), tries (2), probably (2), well (2), bad (2), closed (2), crash (2), why (2), properly (2), saved (2), poznań (2), eclipser (2), skip (2), 2007, 2008, 2009, 2010, archive, kaźmierczyk, writers, linux, wymaganiach, official, webpage, links, link, rec, rapid, course, subscribe, atom, home, image, worth, thousand, words, check, real, monday, think, stating, guest, longer, member, crew, has, office, formed, joint, venture, responsibility, customers, related, rational, products, server, side, actively, participate, development, barely, managed, number, bugs, corporations, perceived, solutions, experience, gathered, border, enterprise, worlds, rather, unique, guess, summarized, xkcd, strip, started, realizing, careers, hard, wonder, stay, tuned, announce, newly, created, gets, added, planet, opened, publicly, megert, his, incredibly, reliable, nominate, him, community, awards, recognition, reading, hope, much, age, glad, clueless, five, ago, eclipsecon, goodbye, above, questions, news, finally, several, busy, weeks, configurable, clicks, away, each, toggle, value, set, suppress, configured, wouldn, satyam, markus, spent, lof, reviewing, patches, thanks, guys, other, things, 220928, properties, path, really, simple, specific, problem, drowned, somewhere, tried, avoid, excessive, reporting, containing, overwhelmed, thousands, potentially, unimportant, make, beer, pizza, come, hurry, seats, register, hosted, information, wiki, brothers, pub, version, popular, ides, ready, coming, comment, poster, present, photos, over, went, lot, registered, fortunately, local, big, hold, everyone, presentations, survey, sent, participants, turned, actual, live, demo, attractive, summary, preference, expand, node, them, strictly, necessary, better, gather, attempt, observe, log, followed, contains, happy, hunting, whole, investigation, practice, take, identified, fixed, near, future, hopefully, 444988, modifies, results, subsequent, being, populated, triggering, end, give, having, thing, responsible, fix, unexpected, type, post_change, null, two, lines, read, suspicious, easy, tue, sep, cest, modalcontext, threadjob, implicit, starting, relevant, says, exited, failure, interrupt, invoking, needbuild, needbuildstack, stacktrace, platform, window, general, eclipsec, exe, add, ini, command, consolelog, case, investigated, order, including, capture, console, output, manually, reality, tell, triggered, solution, plays, role, autobuildjob, enabled, mention, these, classes, entry, 10035, 511, requestor, updating, stack, remembersnapshotrequestor, 553, snapshotifneeded, 1476, endoperation, 1499, 2321, became, decided, spend, adjust, behaviour, distinguish, automatic, logged, modify, sdk, i20140930, 0800, didn, anything, wrong, shut, curious, easier, said, especially, happens, shutdown, warned, bit, too, late, fine, happen, 100, right, last, nothing, process, blue, screen, etc, lost, however, able, detect, situation, fancy, recovery, does, informative, recovered, behind, scenes, far, bet, paid, attention, harmless, explain, developer, seen, least, below, enthusiasts, poland, center, sidebar,

Text of the page (random words):
eclipser blog skip to main skip to sidebar eclipser blog this is a blog of eclipse enthusiasts from poznań poland who would like to share their knowledge of eclipse we work for the ibm support center for eclipse at poznań university of technology wednesday october 1 2014 workspace unsaved changes mystery demystified are you an eclipse plug in developer and you have seen at least once a warning saying something about unsaved changes in the previous session like the one below well i bet you did although you probably never paid attention to it since the warning is quite harmless although can be very annoying let me explain why the warning is generated during eclipse startup if your workspace was not properly saved during the previous session not properly saved means that something bad happened like process crash blue screen power down etc and normally you would lost your work however eclipse is able to detect this situation and recover not a very fancy recovery but it does the job and so the warning message is very informative because it s good to know that eclipse just recovered your work behind the scenes so far so good the annoying part is that it can happen even if you are 100 sure that you closed your eclipse the right way without any crash and all looked good when you closed it the last time so why eclipse tries to recover something if there is should be nothing to recover the answer is that in most cases you didn t do anything wrong and the unsaved change was generated by some badly written plug in that modified your workspace after you already asked eclipse to shut down if you are a curious person like i am you will probably ask fine but which of the plug ins is the bad one well easier said than done especially because it happens during shutdown and you will be warned there was some unsaved change during next eclipse startup this is a bit too late the warning became so annoying that i decided to spend some time to adjust the workspace save behaviour so that we can distinguish unsaved change caused by power down from the one caused by a badly written plug in and then find out in a semi automatic way which plug in is the culprit since eclipse sdk 4 5 build id i20140930 0800 additional error message will be logged if there is any code that tries to modify your workspace after you already asked eclipse to stop here is an example entry org eclipse core resources 4 10035 2014 09 30 17 27 37 511 message the workspace will exit with unsaved changes in this session snapshot requestor org eclipse core internal events notificationmanager notifyjob updating workspace stack 0 java lang runtimeexception scheduling workspace snapshot at org eclipse core internal resources savemanager remembersnapshotrequestor savemanager java 553 at org eclipse core internal resources savemanager snapshotifneeded savemanager java 1476 at org eclipse core internal resources workspace endoperation workspace java 1499 at org eclipse core internal resources workspace run workspace java 2321 at org eclipse core internal events notificationmanager notifyjob run notificationmanager java 41 at org eclipse core internal jobs worker run worker java 55 if you have auto build enabled in most cases the error will mention one of these classes org eclipse core internal events autobuildjob org eclipse core internal events notificationmanager notifyjob this is the code that requested additional workspace save after you manually asked eclipse to stop but in reality this is not the problematic part of the code so how can you tell which workspace operation triggered an auto build which in turn requested additional workspace save here is where the semi part of the solution plays a role whenever you see an error saying that the workspace will exit with unsaved changes in this session you already know that some plug in modified your workspace without your knowledge after you asked eclipse to stop in order to find this plug in you need to enable a few debug options including the new debug option for resource change notifications and then capture the console output to a file in the case i investigated here is what i did 1 add consolelog to your eclipse ini file 2 run eclipse using the following command eclipsec exe trace txt 2 1 3 go to window preferences general tracing preference page 4 enable the enable tracing option 5 expand the platform core resources node and enable the following options org eclipse core resources build delta true org eclipse core resources build failure true org eclipse core resources build interrupt true org eclipse core resources build invoking true org eclipse core resources build needbuild true org eclipse core resources build needbuildstack true org eclipse core resources build stacktrace true org eclipse core resources debug true org eclipse core resources notifications true org eclipse core resources save true not all of them are strictly necessary but since you don t want to do this more than once it s better to gather all the data at first attempt 6 start using your eclipse normally and observe the error log view if you see the workspace will exit with unsaved changes in this session error followed by the workspace exited with unsaved changes in the previous session warning it is time to look at the trace txt file the relevant part of the trace file is between the line that says tue sep 30 17 27 34 cest 2014 modalcontext org eclipse core internal jobs threadjob implicit job full save on workspace starting and the first line that contains java lang runtimeexception scheduling workspace snapshot any resource change event that happened between this two lines could be the culprit of unsaved changes so now you need to read the trace file and see which event is suspicious in my example it was quite easy because the following event was generated after every full save on workspace type post_change build kind 0 resource null delta external plug in libraries external plug in libraries searchable content what it means is that whenever i ask eclipse to stop some plug in modifies the content of external plug in libraries searchable file as part of the save operation this results in subsequent resource change events being populated and triggering auto build and in the end workspace snapshot which will give the unexpected change warning during next startup having all this data the only thing that is left is to find out which plug in is responsible for external plug in libraries searchable and then fix it if you want to see an example how the whole investigation was done in practice take a look at bug 444988 where one of the problematic plug ins was identified and will be fixed in the near future hopefully happy hunting posted by szymon ptaszkiewicz at 2 10 pm no comments friday june 28 2013 summary after democamp in poznan eclipse democamp in poznan is over it went great and a lot of people showed up we had 55 people registered from which 44 showed up during the event fortunately the local was big enough to hold everyone presentations were very interesting although after the survey we sent to participants it turned out that those with an actual live demo were more attractive here are some photos of our democamp if you want to join us and present something in november let me know see you in november szymon posted by szymon ptaszkiewicz at 12 36 pm no comments friday june 7 2013 poster is done posted by szymon ptaszkiewicz at 10 55 am 1 comment wednesday june 5 2013 eclipse democamp in poznan is coming the next version of one of the most popular ides is almost done get ready to be the first to see what s new in it join our eclipse democamp in poznan and find out the event will be hosted at the brothers pub on wednesday june 12 at 6 30 pm you can find more information about the event on our wiki page if you want to join us please register so that we can make sure you can get beer and pizza when you come and hurry up because there are not many seats left see you there szymon posted by szymon ptaszkiewicz at 5 58 pm no comments tuesday march 20 2012 ignore optional compile problems is now available with 3 8 4 2 m6 have you ever been overwhelmed by thousands of potentially unimportant warnings in your java project have you ever tried to avoid excessive error reporting from a source folder containing auto generated code have you ever looked for a specific problem and could not find it because it drowned somewhere in the problems view if answer to any of the above questions is yes then i have good news for you finally after several busy weeks we have an option to ignore all configurable compile problems just a few clicks away it s really simple you can turn on the new ignore optional compile problems option for each source folder available in your java project to do that go to project properties java build path source and toggle the value of ignore optional compile problems to yes with this option set to yes jdt compiler will suppress errors and warnings configured in the preferences java compiler errors warnings page we wouldn t have the new option without great help from satyam and markus who spent a lof of time reviewing patches for bug 220928 thanks guys for other noteworthy things available in 3 8 4 2 m6 see the entire new and noteworthy posted by szymon ptaszkiewicz at 6 42 pm no comments tuesday november 29 2011 time to say goodbye i think i should start this writing from stating that this is a guest post as i am no longer a member of ibm eclipse support crew it has been almost 5 entire years since my office was formed as a kind of joint venture between poznan university of technology and ibm my main responsibility was to help customers with their eclipse related problems as you know many ibm rational products are eclipse based even those server side so i never had enough time to blog or actively participate in eclipse development i barely managed to open a number of bugs that could change how corporations perceived eclipse and eclipse based solutions i d say that my experience gathered on the border of open source and enterprise worlds is a rather unique one and i would like to share it with you at eclipsecon i guess that my 5 years of work for ibm may be summarized with the following xkcd strip i just started realizing that careers are hard every age i m glad i m not the clueless person i was five years ago but now i don t want to get any older if you wonder what i will do next please stay tuned i will announce that on my newly created blog once it gets added to the planet eclipse i have already opened a bug for that i would like to publicly say thank you to daniel megert for his incredibly reliable work not only in jdt and nominate him to eclipse community awards in recognition thank you for reading this post i hope that i will have now much more time for writing krzysztof chris daniel posted by krzysztof chris daniel at 9 17 pm 3 comments monday may 30 2011 a very interesting bug report one image is worth more than a thousand of words just check this real bug report posted by krzysztof chris daniel at 9 02 am no comments older posts home subscribe to posts atom rapid eclipse course link to rec page links our official webpage blog o wymaganiach w it eclipse and linux writers krzysztof chris daniel krzysztof kaźmierczyk szymon ptaszkiewicz blog archive 2014 1 october 1 workspace unsaved changes mystery demystified 2013 3 june 3 2012 1 march 1 2011 5 november 1 may 1 april 1 february 2 2010 2 june 1 january 1 2009 29 december 1 november 4 october 2 september 2 august 2 july 2 june 5 may 1 march 3 february 1 january 6 2008 48 december 3 november 11 october 1 september 2 august 3 july 5 june 2 may 2 april 7 march 2 february 6 january 4 2007 37 december 3 november 9 october 4 september 4 august 4 july 3 june 2 may 2 april 3 march 2 february 1