[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jgit-dev] Eclipse project dependences stopped working

yes, this is faster, since the EGit target platform references the release train repository which is huge
so downloading its index takes a while.

Sometimes clicking "Reload"Âin this preference dialogÂon the target platform is necessary if the
cached bundle pool is corrupted.

-Matthias

On Thu, Jun 25, 2015 at 11:23 PM, Dave Borowitz <dborowitz@xxxxxxxxxx> wrote:
Believe it or not I managed to keep my projects open between when I reported this issue just now. Terry's workaround worked just fine, and much more quickly than setting the target platform from the egit project.

On Thu, Jun 11, 2015 at 10:19 AM, Terry Parker <tparker@xxxxxxxxxx> wrote:
On Wed, Jun 10, 2015 at 2:27 PM, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:
On Wed, Jun 10, 2015 at 6:56 PM, Dave Borowitz <dborowitz@xxxxxxxxxx> wrote:
Recently, every time I close and reopen the set of JGit projects in Eclipse, it stops being able to recognize any third-party dependencies.

For example, the first 3 errors in the problems tab for org.eclipse.jgit right now are:
 Bundle 'com.jcraft.jsch' cannot be resolved
 No available bundle exports package 'com.googlecode.javaewah'
 No available bundle exports package 'java.crypto'
and it goes on from there.

Reopening projects, cleaning, etc. does not work.

I am using the "Use a Target Platform" option from the EGit contributor guide.

The only way I have found to reliably get the dependencies back in order is to remove the projects from my workspace, reload the target platform from the org.eclipse.egit.target project, and readd the projects.

Shawn Pearce tells me he has been having the same problem recently, so it's not just me.

Anybody else have any ideas what the heck is going on?

- which Eclipse package / version are you using ?
- which target platform are you setting ?
- any suspicious errors or warnings in the Eclipse error log ?

When using a milestone or release candidate Mars committer package from
I sometimes faced the problem that the complete build was broken all of a sudden.
Restarting Eclipse fixed this issue. No idea why this happens. I didn't see this with Luna.

The dependencies from the selected target platform are cached in the bundle pool under
<workspace>/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/

Maybe some metadata in your Eclipse workspace is corrupt, try to create a new one
and see if this fixes the problem.

-Matthias

_______________________________________________
jgit-dev mailing list
jgit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jgit-dev

I ran into this too. It looks like somehow after pulling, the target platform became unselected. Using Window > Preferences > Plug-in Development > Target Platform to reselect the target platform cleared all but a handful of API version issues.

--Terry