Can you please add this dependency to the dashboard, organisation unit and visualizer web modules? (Having a merged branch in my checkout so cannot commit myself)
Should be ok now. The same problem was also there in web import-export module. I guess servlet-api was being picked up as a dependency of camel. Should we put it in web commons instead of dotted around all these poms?
Can you please add this dependency to the dashboard, organisation unit and visualizer web modules? (Having a merged branch in my checkout so cannot commit myself)
Funny thing is it's already in commons... But is seems Maven is not picking
it up properly. Could be some exclusions going on.
···
On Tue, Oct 1, 2013 at 6:03 PM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:
Should be ok now. The same problem was also there in web import-export
module. I guess servlet-api was being picked up as a dependency of camel.
Should we put it in web commons instead of dotted around all these poms?
Yes well the important short term thing is to get trunk building again. Then we can investigate this further. (My local build is happy again. And I see jenkins has just completed) Hate it when a 1 hour job takes the whole afternoon
The integration module is now completely gone. Just need to purge from the docs.
Should be ok now. The same problem was also there in web import-export module. I guess servlet-api was being picked up as a dependency of camel. Should we put it in web commons instead of dotted around all these poms?
Funny thing is it’s already in commons… But is seems Maven is not picking it up properly. Could be some exclusions going on.
Yes well the important short term thing is to get trunk building again. Then we can investigate this further. (My local build is happy again. And I see jenkins has just completed) Hate it when a 1 hour job takes the whole afternoon
The integration module is now completely gone. Just need to purge from the docs.
Should be ok now. The same problem was also there in web import-export module. I guess servlet-api was being picked up as a dependency of camel. Should we put it in web commons instead of dotted around all these poms?
Funny thing is it’s already in commons… But is seems Maven is not picking it up properly. Could be some exclusions going on.