Re: [Gitclipse-devel] javagit plug-in

[Patrick W. <pat...@ny...>]

> Does that mean that anytime the javagit jar's name changes, our build
> will break until we go in and fix the manifest file? If I understand
> that correctly then maybe we should change the jar's name to something
> static.

Exactly the case.  I think that would be a good plan.  We can just point our
build to the jar, and manually replace it with a new javagit version when it
becomes available.

> In order for one of our plugins to find javagit's classes, I
> have to add the javagit plugin as a dependency in our plugin's manifest
> file. When I do that though, the build breaks. I get the error 'Missing
> required plug-in edu.nyu.cs.javagit_0.0.0'.

Yes, we need to start building the javagit plug-in and it needs to be added
as a dependency to our core plug-in.  This happens in cruise control right?
If this is happening in your IDE, I'm really not sure.

I refrained from adding all of this, because the moment I commit it our
build will break.  We need to get the javagit jar going and decide on how to
handle it.  We should do this Tuesday don't you think?

Have a good Sunday night.
--
Patrick