Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » TMF (Xtext) » should Xtext builder lock the entire workspace?
should Xtext builder lock the entire workspace? [message #986400] Tue, 20 November 2012 10:30 Go to next message
Vlad Dumitrescu is currently offline Vlad DumitrescuFriend
Messages: 322
Registered: July 2009
Location: Gothenburg
Senior Member
Hi,

As a follow-up on my previous questions, I have tested (somewhat empirically) to modify the Xtext builder so that it only locks the current project, instead of the whole workspace (which is the default). This allows splitting large projects into smaller parts and allow users to work while doing a clean or initial build of the worrkspace.

I didn't see any adverse problems, but it's a bit difficult to know if one has caught the corner cases. In order to not affect users that don't need this, a global flag could be used.

The code change would be something along the lines of
	@Override
	public ISchedulingRule getRule(int kind, Map<String, String> args) {
                if(Sytem.getProperty("xtext.builder.partial.lock").equals("true"))
		    return getProject();
                return super.getRule(kind, args);
	}


Please let me know if you would consider implementing something like this soon. I will open a ticket right away.

best regards,
Vlad
Re: should Xtext builder lock the entire workspace? [message #987295 is a reply to message #986400] Sun, 25 November 2012 20:03 Go to previous messageGo to next message
Sebastian Zarnekow is currently offline Sebastian ZarnekowFriend
Messages: 2961
Registered: July 2009
Senior Member
Am 20.11.12 11:30, schrieb Vlad Dumitrescu:
> Hi,
>
> As a follow-up on my previous questions, I have tested (somewhat
> empirically) to modify the Xtext builder so that it only locks the
> current project, instead of the whole workspace (which is the default).
> This allows splitting large projects into smaller parts and allow users
> to work while doing a clean or initial build of the worrkspace.
>
> I didn't see any adverse problems, but it's a bit difficult to know if
> one has caught the corner cases. In order to not affect users that don't
> need this, a global flag could be used.
>
> The code change would be something along the lines of
> @Override
> public ISchedulingRule getRule(int kind, Map<String, String> args) {
>
> if(Sytem.getProperty("xtext.builder.partial.lock").equals("true"))
> return getProject();
> return super.getRule(kind, args);
> }
>
> Please let me know if you would consider implementing something like
> this soon. I will open a ticket right away.
>
> best regards,
> Vlad
>

Please open a ticket.

Thanks,
Sebastian
--
Looking for professional support for Xtext, Xtend or Eclipse Modeling?
Go visit: http://xtext.itemis.com
Re: should Xtext builder lock the entire workspace? [message #987296 is a reply to message #987295] Sun, 25 November 2012 20:09 Go to previous message
Vlad Dumitrescu is currently offline Vlad DumitrescuFriend
Messages: 322
Registered: July 2009
Location: Gothenburg
Senior Member
Sorry, I forgot to post the link: https://bugs.eclipse.org/bugs/show_bug.cgi?id=394632

regards,
Vlad
Previous Topic:Same optional Modifiers at multiple alternatives
Next Topic:javadoc for generated artifacts
Goto Forum:
  


Current Time: Sun Dec 21 11:33:01 GMT 2014

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

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