Re: [Gitclipse-devel] javagit plug-in

[Michelle S O. <ms...@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.

I noticed something else when using (or at least trying to use) javagit. 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'. Is this something that you've already taken care of in your build script changes, or is it a different problem?

Michelle

----- Original Message -----
From: Patrick Winters <pat...@ny...>
Date: Sunday, July 20, 2008 0:57 am
Subject: RE: [Gitclipse-devel] javagit plug-in
To: 'Michelle S Osborne' <ms...@ny...>
Cc: Gitclipse Devel <git...@li...>

> This is made a little difficult because the javagit plug-in needs to
> hardcode the jar filename in its manifest.  What it does is include 
> the jar
> in the packaged plug-in and add it to its own classpath.  I don't think
> there's any way for us to make the plug-in dymanic.  We'll need to modify
> the plug-in as versions and javagit filenames change.
> 
> All we can do is point the build script to the filename to copy it 
> into the
> plug-in project.  Unless of course we rename the published javagit jar 
> file
> to something static, devoid of version number.
> --
> Patrick
> 
> > -----Original Message-----
> > From: Michelle S Osborne [mailto:ms...@ny...]
> > Sent: Saturday, July 19, 2008 2:04 PM
> > To: pat...@ny...
> > Cc: git...@li...
> > Subject: Re: [Gitclipse-devel] javagit plug-in
> > 
> > Patrick,
> > 
> > I like the idea of putting the location into a property file and then
> > copying from that location into the plugin. Should we add it to
> > build.local.properties? If we did that, we could have every successful
> > javagit build publish the jar file to the location that the property
> > file points to. This way we'd always have the most up-to-date working
> > version.
> > 
> > What do people think? If that sounds reasonable let me know and I can
> > do it.
> > 
> > Michelle
> > 
> > ----- Original Message -----
> > From: Patrick Winters <pat...@ny...>
> > Date: Saturday, July 19, 2008 3:18 am
> > Subject: [Gitclipse-devel] javagit plug-in
> > To: git...@li...
> > 
> > > Hey All,
> > >   There is a plug-in project now for javagit that wraps the jar
> > inside
> > > a
> > > plug-in.  You can get the project from the gitclispe source.  It only
> > > requires that the "javagit-0.01-SNAPSHOT.jar" be in the project root.
> > > We'll have to update the project as the versions change.  I decided
> > to
> > > not check-in the jar file to the gitclipse repository, and require
> > you
> > > to build it yourself.
> > >   Michelle when you're ready I'll check-in modifications to the build
> > > script and feature that include this javagit plug-in with the build.
> > > Again, it will require the JAR to be inside the project directory.
> > >   Should we integrate this into our build process somehow, or just
> > add
> > > the location of the javagit jar in a property file so it can be
> > copied
> > > in?
> > > --
> > > Patrick
> > >
> > >
> > > ---------------------------------------------------------------------
> > ----
> > > This SF.Net email is sponsored by the Moblin Your Move Developer's
> > challenge
> > > Build the coolest Linux based applications with Moblin SDK & win
> > great
> > > prizes
> > > Grand prize is a trip for two to an Open Source event anywhere in 
> the
> > > world
> > > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > > _______________________________________________
> > > Gitclipse-devel mailing list
> > > Git...@li...
> > > https://lists.sourceforge.net/lists/listinfo/gitclipse-devel
>