that seems like a deficiency in the implementation if the only way i can get todo marker support is if the resource resides in a source folder.
source folders are great for managing language modules but that breaks down when you introduce stand alone scripts into the mix. what are the implications of offering up some way to build resources that aren't included as part of a source folder?
the following project structure seems common enough:
project
etc/
lib/
module A
module B
script.xy
if i make project a source folder, then 'etc' automatically becomes a source folder, and i don't want that, yet i still want script.xy to be treated like everything under lib.
On Mon, Sep 22, 2008 at 9:04 PM, Alex Panchenko
<alex@xxxxxxxxx> wrote:
Hi all,
org.eclipse.dltk.validators.core.buildParticipant is the correct way to go (org.eclipse.dltk.validators.core.validator is still supported for compatibility, but it was introduced for external validators so it would be better to have different extension points).
BuildParticipants are called during build process, but everything outside of the source folders is not build - so there are no tasks and annotations.
Regards,
Alex
Sent: Tuesday, September 23, 2008 1:36:09 AM GMT +06:00 Almaty, Novosibirsk
Subject: [Dltk-dev] todo marker question/problem
hello all -
question first:
i'm working on adding 'todo' marker support to my perl plugin (along w/ the python and _javascript_ plugins since they don't have it yet) and i noticed today's extension point change. i currently have the following configuration in my plugin.xml file:
<extension
point="org.eclipse.dltk.validators.core.validator">
<validatorType
class="org.perlipse.internal.parser.PerlTodoTaskParserType"
id="org.perlipse.core.todo"
nature="org.perlipse.core.perlipseNature">
</validatorType>
</extension>
i noticed that the ruby configuration was updated to this:
<extension
point="org.eclipse.dltk.validators.core.buildParticipant">
<buildParticipant
class="org.eclipse.dltk.ruby.internal.parser.RubyTodoParserType"
id="org.eclipse.dltk.ruby.todo"
nature="org.eclipse.dltk.ruby.core.nature">
</buildParticipant>
</extension>
in both cases, the todo markers are still processed correctly, so what is the difference between these two extension points? it's no big deal for me to make adjustments, i just want to understand what the difference is.
now for the issue:
todo markers are not making their way into the editor rulers or the 'tasks' view if the source file sits outside of a 'source' folder. this may be very similiar to the issue i reported last week where i was unable to save changes to scripts that were not contained within a source folder.
--
-jae
--
-jae
