Re: [Gitclipse-devel] javagit plug-in

[Michelle S O. <ms...@ny...>]

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