Setup Oomph to automate installation and configuration of the Eclipse workspace
I did a split up of the prod and test containers of commons and commons cs. What I could not achieve is the removing of the errors. I really believe this is due to our setup which cover both worlds (osgi and non-osgi aka plain dependencies). No matter how hard I try, there is always one problem left. Thus I would live with the current ordering and ignoring this error for now. If you have a solution to this, please let me know
The order made some problems, thus I needed to put it more to the top. Could be that it still works with the plug-in dependencies. The change to ivy to include prod and test was needed because for me if it still split up with the change of referencing the libs in the lib dir and not in the ivy cache, there were always some problems. And the change to use the lib dir is because we need it for the target definition anyway. I will try to fiddle around with this again tomorrow and see if I can improve it.
So I confirmed it it;s the order (Ivy must be below the Plug-in dependencies) + the change in Ivy to build the classpath from the retrieved dependencies and not ivy cache..
In addition the test configuration should not be exported as now I can use in CommonsCS some test library that is defined in Commons, and this will compile in Eclipse, but will fail during the ant build..
It fine in the new oomph because it's ignored.. This way we can ignore any warning there is, why are we trying so much then if we can simply ignore it (sure ok for some warnings).. Anyway I tested with Mars and new workspace if I go one commit back and revert access restriction property back to warning there are no Access Restrictions.. So they were introduced with this ticket..
Anyway the reason might be the Order and Export tab in the build path properties of projects Commons and CS, as Ivy now moved up in order.. Also before we used to export only ivy prod configuration and have separate non-exported one for the test in both projects.. Did you encounter any problems while you were changing this (like project won't build or something)?
Not sure if we should leave it as it is now..
So in the oomph prepared workspace, everything is fine still? You should try to switch over then as this makes it easier for all of us. The access restriction for me was always there, I needed to ignore this in the latest version of Eclipse Mars anyway, no matter if Oomph was there or not. Thus I now included into the default Preferences. This is standard as far as I understand this warning and the talks about this in the internet.