| Question about build path problem [message #260590] |
Fri, 12 June 2009 12:06  |
Eclipse User |
|
|
|
Hey,
I want to create an error marker if there is some problem in the build
path of a java project based on our specific rule. I don't want the java
builder to build the project if the project has that kinkd of problem.
However, I don't know where is the best place to create the marker. My
scenario is very similar to the eclipse behavior that, in eclipse, if the
build path of a java project is broken, e.g. an imported jar does not
exist, eclipse shows a error marker on the problem. Then, the java builder
is not kicked in.
I tried to use the CompilationParticipant extension but I could not
prevent the java builder from being called. Any thought.
Thanks.
|
|
|
| Re: Question about build path problem [message #260642 is a reply to message #260590] |
Tue, 16 June 2009 09:28  |
| Eclipse User |
|
|
|
Raymond wrote:
> Hey,
>
> I want to create an error marker if there is some problem in the build
> path of a java project based on our specific rule. I don't want the
> java builder to build the project if the project has that kinkd of
> problem. However, I don't know where is the best place to create the
> marker. My scenario is very similar to the eclipse behavior that, in
> eclipse, if the build path of a java project is broken, e.g. an
> imported jar does not exist, eclipse shows a error marker on the
> problem. Then, the java builder is not kicked in.
> I tried to use the CompilationParticipant extension but I could not
> prevent the java builder from being called. Any thought.
You have to create the marker on the project and remove the Java builder
from the projects build spec, see
org.eclipse.core.resources.IProjectDescription.getBuildSpec( ) for details.
Dani
> Thanks.
|
|
|
Powered by
FUDForum. Page generated in 0.05743 seconds
Home