Community
Participate
Working Groups
I have a workspace with several .target definitions that use Software sites. They have all be loaded at one time or another so all artifacts (and presumably metadata) are available in the workspace. Of course, one of them is set as current. There are several issues with the target platform support wrt offline function. 1) if for some reason you need to change a setting or (de)select the content of the current target, you are not able to as when you open that target is shows errors because it cannot connect to the software site. 2) if you happen to click Set as target with one of these targets that cannot connect then your target state is hosed and your workspace no longer compiles 3) If you happen to exit Eclipse with a .target file open (say, prior to going off line) and then start up the workspace while offline, the target gets refreshed and effectively invalidated. I'm not sure if this affects the workspace (assuming you don't click the Set as target link) but it is distracting to the user to see the red Xs 4) Given that a target def has been loaded at some point, it is unclear why we need to force a connection to the repo as a blocking operation. That is, I have a valid target that works for me. Just because PDE cannot talk to the repo does not make the target any less valid. Users should be able to open, edit, add more locations, set as target, tweak content, set paramters, ... all without touching the server. this is especially true if the target is set to not add prerequisites.
Yes, this is a significant concern. We are hoping that as part of the target model changes we can make this happen.
Removing target milestone. The work in the branch is not going in for 3.6. I have this working in the target_api_changes branch. If you had provisioned a target previously, the profile had all the necessary information to load the active target on startup. This could be done without pinging anything online. However, opening of the UI still ends up trying to contact the update sites (I had hoped that metadata would be cached by p2).
Working with target platforms based on p2 repos on computers with temporary internet connection is not possible without this feature.
Just an idea - and untested at that, but have you considered to create a local p2 repository mirror on your laptop that aggregates all the repos your .target definitions need and point your target definitions to that location instead... (this is probably, how .target definition should internally be working)
(In reply to comment #4) This probably works. However, I explicitely want to point to a remote repository to get updates more or less automatically (which doesn't work as expected for other reasons). Anyway, a good workaround.
The solution to bug 276326 may offer a better offline experience.
A possible fix has been committed to HEAD. All of the problems Jeff reported in comment #0 worked for me. Only thing I noticed was that p2 doesn't recover well when you reconnect, it continues to say that repos are unavailable. If possible, give the next I build a try and see how it works for you.
Marking as FIXED. Except for p2 not trying to reconnect after I go online again, this works for me. Obviously if anyone has any issues, open a new bug report.
