Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » is git.auto.fetch implemented at all?
is git.auto.fetch implemented at all? [message #1226792] Thu, 02 January 2014 18:21 Go to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1419
Registered: July 2009
Senior Member
Hi

Is git.auto.fetch considered during materialization?

I have it in my rmap, but if I materialize an eclipse workspace again
(using the same cloned repository) it never auto pulls changes (I saw
also this http://www.eclipse.org/forums/index.php/t/221619/ ). The same
holds if I remove the eclipse workspace and start the materialization again.

Indeed, by looking at
http://git.eclipse.org/c/buckminster/buckminster.git/tree/org.eclipse.buckminster.git/src/org/eclipse/buckminster/git/internal/RepositoryAccess.java
the property is stored in the field autoFetch but never used later...

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
Re: is git.auto.fetch implemented at all? [message #1229407 is a reply to message #1226792] Thu, 09 January 2014 11:33 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1419
Registered: July 2009
Senior Member
anyone?

On 02/01/2014 19:21, Lorenzo Bettini wrote:
> Hi
>
> Is git.auto.fetch considered during materialization?
>
> I have it in my rmap, but if I materialize an eclipse workspace again
> (using the same cloned repository) it never auto pulls changes (I saw
> also this http://www.eclipse.org/forums/index.php/t/221619/ ). The same
> holds if I remove the eclipse workspace and start the materialization again.
>
> Indeed, by looking at
> http://git.eclipse.org/c/buckminster/buckminster.git/tree/org.eclipse.buckminster.git/src/org/eclipse/buckminster/git/internal/RepositoryAccess.java
> the property is stored in the field autoFetch but never used later...
>
> cheers
> Lorenzo
>


--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
Re: is git.auto.fetch implemented at all? [message #1233781 is a reply to message #1226792] Mon, 20 January 2014 13:04 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3232
Registered: July 2009
Senior Member
On 2014-01-02 19:21, Lorenzo Bettini wrote:
> Hi
>
> Is git.auto.fetch considered during materialization?
>
Not really. That functionality was written as part of the first incarnation of the git support feature. I didn't know
enough about git to do a proper evaluation for a requirement spec. My current recommendation would be to not use it. If
someone has the time to look into how this should be implemented properly, then I'd be very interested in reviewing a
patch. One thing that comes to mind immediately is that the auto.fetch should be called auto.pull (since that's what it
was intended as).

- thomas

> I have it in my rmap, but if I materialize an eclipse workspace again
> (using the same cloned repository) it never auto pulls changes (I saw
> also this http://www.eclipse.org/forums/index.php/t/221619/ ). The same
> holds if I remove the eclipse workspace and start the materialization again.
>
> Indeed, by looking at
> http://git.eclipse.org/c/buckminster/buckminster.git/tree/org.eclipse.buckminster.git/src/org/eclipse/buckminster/git/internal/RepositoryAccess.java
> the property is stored in the field autoFetch but never used later...
>
> cheers
> Lorenzo
>
Re: is git.auto.fetch implemented at all? [message #1236869 is a reply to message #1233781] Tue, 28 January 2014 09:06 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1419
Registered: July 2009
Senior Member
On 20/01/2014 14:04, Thomas Hallgren wrote:
> On 2014-01-02 19:21, Lorenzo Bettini wrote:
>> Hi
>>
>> Is git.auto.fetch considered during materialization?
>>
> Not really. That functionality was written as part of the first
> incarnation of the git support feature. I didn't know enough about git
> to do a proper evaluation for a requirement spec. My current
> recommendation would be to not use it. If someone has the time to look
> into how this should be implemented properly, then I'd be very
> interested in reviewing a patch. One thing that comes to mind
> immediately is that the auto.fetch should be called auto.pull (since
> that's what it was intended as).

OK, I'll submit a bug and see whether I can come up with something :)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
Re: is git.auto.fetch implemented at all? [message #1438136 is a reply to message #1236869] Sun, 05 October 2014 15:16 Go to previous messageGo to next message
Ed Willink is currently offline Ed WillinkFriend
Messages: 4188
Registered: July 2009
Senior Member
Hi

What is the status of this?

I appear to need to delete my Hudson Workspace to get a GIT 'refresh'.
Searching comes up with this correspondence.

On my Hudson HIPP I appear to have only the choice of Buckminster 4.2 so
perhaps 4.3 or 4.4 may have already fixed it.

But when I look at

https://projects.eclipse.org/projects/tools.buckminster/governance

I see that the current version of Buckminster is 2.0.0 perhaps released
18 months ago but if so without a release review. No plans for further
releases.

I'm really confused. What is the best Buckminster version and does it
fix the GIT refresh problem?

Regards

Ed Willink

On 28/01/2014 09:06, Lorenzo Bettini wrote:
> On 20/01/2014 14:04, Thomas Hallgren wrote:
>> On 2014-01-02 19:21, Lorenzo Bettini wrote:
>>> Hi
>>>
>>> Is git.auto.fetch considered during materialization?
>>>
>> Not really. That functionality was written as part of the first
>> incarnation of the git support feature. I didn't know enough about git
>> to do a proper evaluation for a requirement spec. My current
>> recommendation would be to not use it. If someone has the time to look
>> into how this should be implemented properly, then I'd be very
>> interested in reviewing a patch. One thing that comes to mind
>> immediately is that the auto.fetch should be called auto.pull (since
>> that's what it was intended as).
>
> OK, I'll submit a bug and see whether I can come up with something :)
>
> cheers
> Lorenzo
>
Re: is git.auto.fetch implemented at all? [message #1462520 is a reply to message #1438136] Wed, 05 November 2014 17:13 Go to previous message
Ed Willink is currently offline Ed WillinkFriend
Messages: 4188
Registered: July 2009
Senior Member
Hi

Ping. Anyone able to comment?

Regards

Ed Willink

On 05/10/2014 16:16, Ed Willink wrote:
> Hi
>
> What is the status of this?
>
> I appear to need to delete my Hudson Workspace to get a GIT 'refresh'.
> Searching comes up with this correspondence.
>
> On my Hudson HIPP I appear to have only the choice of Buckminster 4.2 so
> perhaps 4.3 or 4.4 may have already fixed it.
>
> But when I look at
>
> https://projects.eclipse.org/projects/tools.buckminster/governance
>
> I see that the current version of Buckminster is 2.0.0 perhaps released
> 18 months ago but if so without a release review. No plans for further
> releases.
>
> I'm really confused. What is the best Buckminster version and does it
> fix the GIT refresh problem?
>
> Regards
>
> Ed Willink
>
> On 28/01/2014 09:06, Lorenzo Bettini wrote:
>> On 20/01/2014 14:04, Thomas Hallgren wrote:
>>> On 2014-01-02 19:21, Lorenzo Bettini wrote:
>>>> Hi
>>>>
>>>> Is git.auto.fetch considered during materialization?
>>>>
>>> Not really. That functionality was written as part of the first
>>> incarnation of the git support feature. I didn't know enough about git
>>> to do a proper evaluation for a requirement spec. My current
>>> recommendation would be to not use it. If someone has the time to look
>>> into how this should be implemented properly, then I'd be very
>>> interested in reviewing a patch. One thing that comes to mind
>>> immediately is that the auto.fetch should be called auto.pull (since
>>> that's what it was intended as).
>>
>> OK, I'll submit a bug and see whether I can come up with something :)
>>
>> cheers
>> Lorenzo
>>
>
Previous Topic:java.lang.IllegalStateException: Preference node "file:" has been removed.
Next Topic:Trouble fetching a maven dependency
Goto Forum:
  


Current Time: Mon Dec 22 15:50:05 GMT 2014

Powered by FUDForum. Page generated in 0.02553 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software