Community
Participate
Working Groups
The "The project cannot be built until its prerequisite {0} is built" problem marker should be more useful. It would be helpful: - If the project name of the failing projected is included in the message - If the problem marker links to the the project, e.g., if you click on the project it should jump to the associated project
(In reply to Lars Vogel from comment #0) > - If the project name of the failing projected is included in the message You mean the project that is given as the location of the error?
(In reply to Stephan Herrmann from comment #1) > (In reply to Lars Vogel from comment #0) > > - If the project name of the failing projected is included in the message > > You mean the project that is given as the location of the error? Yes
Does this message come from JDT or from the Resource model?
(In reply to Mickael Istria from comment #3) > Does this message come from JDT or from the Resource model? I don't know. Julian, you worked on this before. Do you know?
(In reply to Mickael Istria from comment #3) > Does this message come from JDT or from the Resource model? It's created by JavaBuilder.
(In reply to Lars Vogel from comment #0) > The "The project cannot be built until its prerequisite {0} is built" > problem marker should be more useful. It would be helpful: > > - If the project name of the failing projected is included in the message as confirmed in comment 2 this information is already available, so including its name in the problem message will be redundant and at the same time push relevant information to the right. As a result the Problems view will likely cut off this relevant information. > - If the problem marker links to the the project, e.g., if you click on the > project it should jump to the associated project Still when you say "the project" this is not clear, since we are speaking about problems on one project blocking build of another project. So: which one?? In case you want to navigate to the project *causing* the problem, then perhaps you meant that the problem *hover* should turn this part of the error message into a clickable link. Moving to JDT/UI for comments on this idea.
(In reply to Stephan Herrmann from comment #6) > (In reply to Lars Vogel from comment #0) > > The "The project cannot be built until its prerequisite {0} is built" > > problem marker should be more useful. It would be helpful: > > > > - If the project name of the failing projected is included in the message > > as confirmed in comment 2 this information is already available, so > including its name in the problem message will be redundant and at the same > time push relevant information to the right. As a result the Problems view > will likely cut off this relevant information. Agreed. You should already see the name of the project having this problem in the "Resource" column of the Problems view. For navigation to the project having this problem, the right-click > Go to Resource can be activated and it can highlight the project in the Package Explorer view. Note that the same should already be available via right-click > Show In > Package Explorer. > In case you want to navigate to the project *causing* the problem, then > perhaps you meant that the problem *hover* should turn this part of the > error message into a clickable link. This can be tried or something can be added in Ctrl+1 (right-click > Quick Fix) to navigate.
Typically a double click on an error brings you to the element which has the error. See for example a compile error. This should also be done here (jump to project).
(In reply to Noopur Gupta from comment #7) > For navigation to the project having this problem, the right-click > Go to > Resource can be activated and it can highlight the project in the Package > Explorer view. Note that the same should already be available via > right-click > Show In > Package Explorer. (In reply to Lars Vogel from comment #8) > Typically a double click on an error brings you to the element which has the > error. See for example a compile error. This should also be done here (jump > to project). I think the double-click is linked to the activation of right-click > Go to Resource.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
