See the following blog post for instruction on how to create a patch feature:
http://aniefer.blogspot.com/2009/06/patching-features-with-p2.html - Konstantin -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Patric Rufflar Sent: Tuesday, March 15, 2011 8:26 AM To: General discussion of project-wide or architectural issues. Subject: Re: [wtp-dev] "java indexing" thread causes high cpu load after build Hi Nicolas, thank you for your answer. Filtering some files because of some rules (e.g. derived state) would be very cool. Should I log an enhancement request? Btw: I locally changed the WTP sources to not consider derived ressources using the PDE. How can I create a patched plugin/feature patch to make these changes persistent and to share them with my colleagues? Best regards, Patric Quoting NICHOLAS SANDONATO <[email protected]>: > Hi Patric, > > This indexing of JSPs is so that Java references in them can be used for > search and refactoring. Right now, there is no way to disable this > indexing as it potentially removes a lot of functionality. The preference > to include JSP matches in Java searches pertains only to the reporting in > the view and not to the actual indexing of these files. We would likely > be able to enhance the indexer to ignore particular files based on some > rules like if it's derived. > > > > > From: > Patric Rufflar <[email protected]> > To: > [email protected] > Date: > 03/11/2011 12:43 PM > Subject: > [wtp-dev] "java indexing" thread causes high cpu load after build > Sent by: > [email protected] > > > > Hello, > > I am experiencing the reproducible problem that > the java indexing thread causes high cpu load for several minutes > after a build took place. > > My build procedure includes a special builder which (more or less) > copies all jsps to another directory in my project (and marks these > copies as derived). > > All Web/WTP validators are configured as suspended in the preference > dialog. > > Please have a look at the following thread dump which has been taken > after a build finished and while the cpu usage can be seen: > (although I cannot see any active background tasks in the progress > monitor) > > org.eclipse.jst.jsp.core.internal.parser.internal.JSPTokenizer.primGetNextTo ken() > (line: > 2120) > org.eclipse.jst.jsp.core.internal.parser.internal.JSPTokenizer.getNextToken( ) > > (line: 1643) > org.eclipse.wst.xml.core.internal.parser.XMLSourceParser.getNextRegion() > (line: 189) > org.eclipse.jst.jsp.core.internal.parser.JSPSourceParser.parseNodes() > (line: 237) > org.eclipse.wst.xml.core.internal.parser.XMLSourceParser.getDocumentRegions( ) > > (line: 173) > org.eclipse.wst.sse.core.internal.text.StructuredDocumentReParser._core_repa rse_text(int, > > int) > org.eclipse.wst.sse.core.internal.text.StructuredDocumentReParser.core_repar se(int, > int, org.eclipse.wst.sse.core.internal.text.CoreNodeList, boolean) (line: > 710) > org.eclipse.jst.jsp.core.internal.parser.JSPReParser.reparse(org.eclipse.wst .sse.core.internal.provisional.text.IStructuredDocumentRegion, > org.eclipse.wst.sse.core.internal.provisional.text.IStructuredDocumentRegion ) > (line: > 143) > org.eclipse.wst.sse.core.internal.text.StructuredDocumentReParser.reparse() > > (line: 1291) > org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.updateModel(j ava.lang.Object, > int, int, java.lang.String) (line: > 2709) > org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalRepla ceText(java.lang.Object, > int, int, java.lang.String, long, boolean) (line: > 1923) > org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(j ava.lang.Object, > int, int, java.lang.String, long, boolean) (line: > 2419) > org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.setText(java. lang.Object, > java.lang.String) (line: > 2606) > org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.setText(jav a.lang.Object, > java.lang.String) (line: > 188) > org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.set(java.lang .String) > (line: > 2481) > org.eclipse.jst.jsp.core.internal.java.XMLJSPRegionHelper.parse(java.lang.St ring) > (line: > 159) > org.eclipse.jst.jsp.core.internal.java.JSPTranslator.handleIncludeFile(java. lang.String) > (line: > 2310) > org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translateDirective(java .util.Iterator) > (line: > 2033) > org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translateJSPNode(org.ec lipse.wst.sse.core.internal.provisional.text.ITextRegion, > java.util.Iterator, java.lang.String, int) (line: > 1766) > org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translateRegionContaine r(org.eclipse.wst.sse.core.internal.provisional.text.ITextRegionCollection, > int) (line: > 1349) > org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translate() (line: > 1127) > org.eclipse.jst.jsp.core.internal.java.JSPTranslationAdapter.getJSPTranslati on() > (line: > 153) > org.eclipse.jst.jsp.core.internal.java.search.JSPSearchDocument.getJSPTransl ation() > (line: > 120) > org.eclipse.jst.jsp.core.internal.java.search.JSPSearchDocument.getCharConte nts() > (line: > 77) > org.eclipse.jst.jsp.core.internal.java.search.JavaSearchDocumentDelegate.get CharContents() > org.eclipse.jdt.internal.core.search.indexing.SourceIndexer.indexDocument() > > (line: 60) > org.eclipse.jdt.internal.core.search.JavaSearchParticipant.indexDocument(org .eclipse.jdt.core.search.SearchDocument, > org.eclipse.core.runtime.IPath) (line: > 72) > org.eclipse.jst.jsp.core.internal.java.search.JSPSearchParticipant.indexDocu ment(org.eclipse.jdt.core.search.SearchDocument, > org.eclipse.core.runtime.IPath) (line: > 72) > org.eclipse.jdt.internal.core.search.indexing.IndexManager.indexDocument(org .eclipse.jdt.core.search.SearchDocument, > org.eclipse.jdt.core.search.SearchParticipant, > org.eclipse.jdt.internal.core.index.Index, org.eclipse.core.runtime.IPath) > (line: > 453) > org.eclipse.jdt.internal.core.search.indexing.IndexManager$1.execute(org.ecl ipse.core.runtime.IProgressMonitor) > (line: > 853) > org.eclipse.jdt.internal.core.search.processing.JobManager.run() (line: > 404) > java.lang.Thread.run() (line: 662) > > > "Include JSP matches in Java searches" is disabled. > I am using the most recent Eclipse 3.6.2 / WTP 3.2.3 > > My questions: > - What does this java indexing do in my case? > - Is this is bug? Or did I miss an important configuration option? > - Is there a workaround? Can I disable this indexing or at least for > all derived files? > > Thank you and best regards, > Patric > > > _______________________________________________ > wtp-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/wtp-dev > > > _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
