| [buckminster-dev] Mercurial plugin [message #635637] |
Wed, 27 October 2010 10:46  |
Eclipse User |
|
|
|
The Mercurial plugin I talked about earlier is working pretty well for
us right now. I started looking at the Git plugin because it would
seem logical that the two plugins should behave similarly. In Git it
seems that you specify a local repository and then optionally specify
a remote repository if you want to synchronize. In the Mercurial
plugin I only allow one repository to be specified and I clone it to a
temp directory if it is a remote repository.
My concern with the way the Git plugin works is that local paths are
platform specific. If I specify c:\whatever it is not going to work
when I move the rspec file over to a linux box. Does anyone have any
experience with this? Is this a non-issue in practice?
Also, what paperwork do I need from my employer if I can convince them
to contribute the code?
Thanks,
Phil
|
|
|
| Re: [buckminster-dev] Mercurial plugin [message #635652 is a reply to message #635637] |
Wed, 27 October 2010 11:55  |
| Eclipse User |
|
|
|
Hi Phil,
The paths in the rmap are subject to property expansion, so you can write things like ${user.home}/whatever. Properties
can be passed to the query in many ways. Command line options, cquery file, or as defaults in the rmap.
A contribution is normally provided as a patch or a zip in a bugzilla. The "paperwork" involved is a comment and a
header in all source files. The expected contents can best be described by the following request from the Eclipse EMO
pertaining to an earlier contribution:
Can you please have the contributor make the following confirmations on the
bug:
1. Contributor authored 100% of the content
2. Contributor has the rights to donate the content to Eclipse under the EPL
3. Contributor has arranged all source files to include the Eclipse default
Copyright and License Notice
Regarding point #3, the default copyright and license notice used is not the
standard template. The contributor will need to "redo" and you will need to
provide a new attachment to this CQ. Please see the following URL -
http://www.eclipse.org/legal/copyrightandlicensenotice.php
Regarding #1 and #2 you just need to add a comment to the bugzilla with something like:
"I hereby declare that I have authored the 100% of the code and that I have the rights to donate the code to Eclipse
under the EPL."
#3 means that you must update the header of all sources according to the one found at the link and provide a new zip.
Sorry about that. I didn't know it was that strict.
Kind Regards,
Thomas Hallgren
On 10/27/2010 04:46 PM, Phil Borlin wrote:
> The Mercurial plugin I talked about earlier is working pretty well for
> us right now. I started looking at the Git plugin because it would
> seem logical that the two plugins should behave similarly. In Git it
> seems that you specify a local repository and then optionally specify
> a remote repository if you want to synchronize. In the Mercurial
> plugin I only allow one repository to be specified and I clone it to a
> temp directory if it is a remote repository.
>
> My concern with the way the Git plugin works is that local paths are
> platform specific. If I specify c:\whatever it is not going to work
> when I move the rspec file over to a linux box. Does anyone have any
> experience with this? Is this a non-issue in practice?
>
> Also, what paperwork do I need from my employer if I can convince them
> to contribute the code?
>
> Thanks,
> Phil
|
|
|
Powered by
FUDForum. Page generated in 0.06351 seconds
Home