2009/3/4 Erle Mantos
<emantos@xxxxxxxxx>
I have an inquiry regarding the proper thing to do when we have project on errors:
- If a maven project is in error because of the lack of some dependencies, do we still execute
process-resources and process-test-resources on it? For now, we do. If getting a maven project with
resolveTransitively set to true results to an exception( unresolved dependencies ), does it automatically
mean that executing process-resources and process-test-resources on it would also fail?
I would like to take a step back... I feel I'm lacking context for a meaningful answer :-)
Why do we need to change the current behavior?
- I found out MavenExecutionStatus is handling exceptions, which will lead to that exception being handled
redundantly. First, by MavenExecutionStatus, and second, by the code that initiated its call in the first place
( e.g MavenProjectManager ).
Thoughts?
We need a central place for handling exceptions at the UI level, so the markers can be placed on the Editor.
I feel like we also need some handling at a lower level to adapt maven error conditions to things we can handle at the IAM level (i.e. wrapping exceptions and adding information so IAM does not need to know every possible Maven exception).
So maybe there is place for both? (did not look at the code, so take this as a "philosophical" answer! )
I'm experimenting now on putting error flags on maven projects in the project cache so we don't waste
processor cycles executing other maven calls on it.
Any thoughts as to where to clear this error flag? when the pom is edited?
Currently, the maven builder is also the "pom validator", so it must be always allowed to run after the pom is saved so it can update the error flag status.
--
Cheers,
Erle Czar Mantos
Software Engineer | Exist Global | 412-1155 | Skype: emantos | www.exist.com | Innovation Delivered
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/iam-dev
