xtext-dev http://dev.eclipse.org/mhonarc/lists/xtext-dev/maillist.html xtext-dev en-us Fri, 03 May 2013 17:22:07 GMT Fri, 03 May 2013 17:22:07 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) xtext-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/xtext-dev/maillist.html Re: [xtext-dev] Beware of the nightly build http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01109.html Attachment: signature.asc Description: Message signed with OpenPGP using GPGMail Hi, it should be save to install the next green nightly built. Best regards, Sebastian On 06.02.2013, at 18:37, Sebastian Zarnekow wrote: > Hi, > > I pushed a huge bulk of changes into the git repo and until further notice I'd suggest to stick with the M5 instead of the nightly update site. I'll keep you posted on the progress with the merge of the big chunk of changes. > > Regards, > Sebastian > > _______________________________________________ > xtext-dev mailing list > xtext-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/xtext-dev

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

]]> Mon, 11 Feb 2013 01:10:35 GMT http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01109.html Sebastian.Zarnekow@xxxxxxx (Sebastian Zarnekow) [xtext-dev] Beware of the nightly build http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01108.html Hi, I pushed a huge bulk of changes into the git repo and until further notice I'd suggest to stick with the M5 instead of the nightly update site. I'll keep you posted on the progress with the merge of the big chunk of changes. Regards, Sebastian Attachme... Hi, I pushed a huge bulk of changes into the git repo and until further notice I'd suggest to stick with the M5 instead of the nightly update site. I'll keep you posted on the progress with the merge of the big chunk of changes. Regards, Sebastian

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

]]> Wed, 06 Feb 2013 17:37:51 GMT http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01108.html Sebastian.Zarnekow@xxxxxxx (Sebastian Zarnekow) [xtext-dev] Project meta data is out of date for modeling.tmf.xtext http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01107.html Sven, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * Project home page (projecturl = http://www.eclipse.org/Xtext/) is not us... Sven, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * Project home page (projecturl = http://www.eclipse.org/Xtext/) is not using an Eclipse theme. You should think about updating to the Nova theme(http://wiki.eclipse.org/Nova) * The date for release "2.3.0" is in the past, but the release is not marked as completed. If it is completed, it should be marked as completed; if it has been postponed, it should be given a new target date. * There is no next/future release of this project. All Eclipse projects must have a "next release" planned and scheduled. ]]> Tue, 05 Feb 2013 05:00:07 GMT http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01107.html emo@xxxxxxx (portal on behalf of emo) [xtext-dev] Case insensitive file systems http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01106.html Hi, I performend a rename refactoring from StopWatches to Stopwatches which made git go bananas on case insensitive file systems. If you get an error when you try to pull the changes, please delete the files org.eclipse.xtext/plugins/org.eclipse.xtext.util... Hi, I performend a rename refactoring from StopWatches to Stopwatches which made git go bananas on case insensitive file systems. If you get an error when you try to pull the changes, please delete the files org.eclipse.xtext/plugins/org.eclipse.xtext.util/src/org/eclipse/xtext/util/internal/StopWatches.java org.eclipse.xtext/plugins/org.eclipse.xtext.junit4/src/org/eclipse/xtext/junit4/internal/StopwatchRule.java on your disk and try again to pull. Please let me know if those steps do not work for you. Sorry for any inconvenience caused, Sebastian

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

]]> Tue, 29 Jan 2013 10:19:19 GMT http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01106.html Sebastian.Zarnekow@xxxxxxx (Sebastian Zarnekow) Re: [xtext-dev] Xtext + Gerrit / Fwd: [Bug 398639] Enable Gerrit for my project http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01105.html As a side note:gitx does not seem to trigger the generation of a change set, e.g. the Change-ID has to be generated either with EGit or by a dummy git commit --amendThis is how the review page looks like: https://git.eclipse.org/r/#/c/9817/ Cheers,Sebastia... As a side note:

gitx does not seem to trigger the generation of a change set, e.g. the Change-ID has to be generated either with EGit or by a dummy 
git commit --amend

This is how the review page looks like: https://git.eclipse.org/r/#/c/9817/

Cheers,
Sebastian

On 21.01.2013, at 20:14, Sebastian Zarnekow wrote:

Hi everybody,

Xtext uses Gerrit now to (optionally) pre-test changes before they are released into master. Committers can still directly push into the repo, but may choose to release only a tested changeset.

You may want to watch Xtext at https://git.eclipse.org/r/#/settings/projects
And upload your ssh key to https://git.eclipse.org/r/#/settings/ssh-keys (use 
$ pbcopy < ~/.ssh/id_rsa.pub
to copy your public key into your clipboard).

A short intro can be found here: http://wiki.eclipse.org/Gerrit#Logon

What you should do on the cmd line to Gerritty your local repo if you still want to be able to push directly via git push origin:

git remote add review ssh://<username>@git.eclipse.org:29418/tmf/org.eclipse.xtext.git
git remote set-url --push origin ssh://<username>@git.eclipse.org:29418/tmf/org.eclipse.xtext.git
git config remote.review.push HEAD:refs/for/master
git config remote.origin.push HEAD:refs/heads/master
scp -p -P 29418 <username>@git.eclipse.org:hooks/commit-msg .git/hooks/

The last command will install a commit-hook into your git repo. As soon as you commit something, an identifier is generated that allows to track commits which depend on each other. See the tutorial for details on how to work with dependend change-sets in Gerrit.

Please let us know if you face any problems with the setup.

Happy coding,
Sebastian


Begin forwarded message:

Subject: [Bug 398639] Enable Gerrit for my project
Date: 21. Januar 2013 17:13:52 MEZ

https://bugs.eclipse.org/bugs/show_bug.cgi?id=398639
Product/Component: Community / Git

Eclipse Webmaster <webmaster@xxxxxxxxxxx> changed:

          What    |Removed                     |Added
----------------------------------------------------------------------------
            Status|NEW                         |RESOLVED
        Resolution|---                         |FIXED

--- Comment #1 from Eclipse Webmaster <webmaster@xxxxxxxxxxx> ---
I've enabled Gerrit for tmf/org.eclipse.xtext.git.  You can add it to the list
of projects you watch:

https://git.eclipse.org/r/#/settings/projects

Upload your SSH public keys to Gerrit if you wish to use SSH:
https://git.eclipse.org/r/#/settings/ssh-keys

Your Gerrit-enabled repo URLs:
ssh://userid@xxxxxxxxxxxxxxx:29418/tmf/org.eclipse.xtext.git
https://git.eclipse.org/r/p/tmf/org.eclipse.xtext.git

Gerrit@Eclipse docs:
http://wiki.eclipse.org/Gerrit#Logon

-M.

--
You are receiving this mail because:
You are watching the reporter of the bug.

_______________________________________________
xtext-dev mailing list
xtext-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/xtext-dev

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

]]> Mon, 21 Jan 2013 20:02:25 GMT http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01105.html Sebastian.Zarnekow@xxxxxxx (Sebastian Zarnekow) [xtext-dev] Xtext + Gerrit / Fwd: [Bug 398639] Enable Gerrit for my project http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01104.html Hi everybody,Xtext uses Gerrit now to (optionally) pre-test changes before they are released into master. Committers can still directly push into the repo, but may choose to release only a tested changeset.You may want to watch Xtext at https://git.eclipse... Hi everybody,

Xtext uses Gerrit now to (optionally) pre-test changes before they are released into master. Committers can still directly push into the repo, but may choose to release only a tested changeset.

You may want to watch Xtext at https://git.eclipse.org/r/#/settings/projects
And upload your ssh key to https://git.eclipse.org/r/#/settings/ssh-keys (use 
$ pbcopy < ~/.ssh/id_rsa.pub
to copy your public key into your clipboard).

A short intro can be found here: http://wiki.eclipse.org/Gerrit#Logon

What you should do on the cmd line to Gerritty your local repo if you still want to be able to push directly via git push origin:

git remote add review ssh://<username>@git.eclipse.org:29418/tmf/org.eclipse.xtext.git
git remote set-url --push origin ssh://<username>@git.eclipse.org:29418/tmf/org.eclipse.xtext.git
git config remote.review.push HEAD:refs/for/master
git config remote.origin.push HEAD:refs/heads/master
scp -p -P 29418 <username>@git.eclipse.org:hooks/commit-msg .git/hooks/

The last command will install a commit-hook into your git repo. As soon as you commit something, an identifier is generated that allows to track commits which depend on each other. See the tutorial for details on how to work with dependend change-sets in Gerrit.

Please let us know if you face any problems with the setup.

Happy coding,
Sebastian


Begin forwarded message:

Subject: [Bug 398639] Enable Gerrit for my project
Date: 21. Januar 2013 17:13:52 MEZ

https://bugs.eclipse.org/bugs/show_bug.cgi?id=398639
Product/Component: Community / Git

Eclipse Webmaster <webmaster@xxxxxxxxxxx> changed:

          What    |Removed                     |Added
----------------------------------------------------------------------------
            Status|NEW                         |RESOLVED
        Resolution|---                         |FIXED

--- Comment #1 from Eclipse Webmaster <webmaster@xxxxxxxxxxx> ---
I've enabled Gerrit for tmf/org.eclipse.xtext.git.  You can add it to the list
of projects you watch:

https://git.eclipse.org/r/#/settings/projects

Upload your SSH public keys to Gerrit if you wish to use SSH:
https://git.eclipse.org/r/#/settings/ssh-keys

Your Gerrit-enabled repo URLs:
ssh://userid@xxxxxxxxxxxxxxx:29418/tmf/org.eclipse.xtext.git
https://git.eclipse.org/r/p/tmf/org.eclipse.xtext.git

Gerrit@Eclipse docs:
http://wiki.eclipse.org/Gerrit#Logon

-M.

--
You are receiving this mail because:
You are watching the reporter of the bug.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

]]> Mon, 21 Jan 2013 19:14:15 GMT http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01104.html Sebastian.Zarnekow@xxxxxxx (Sebastian Zarnekow) [xtext-dev] Plan and date for the 2.4 release http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01103.html Hi all,we have many cool new features and highly desired bug fixes waiting to be released.The main theme for the next release is the overhauled type system (Re-implement linking, validation and scoping), which solves many issues and even more importantly a... Hi all,

we have many cool new features and highly desired bug fixes waiting to be released.
The main theme for the next release is the overhauled type system (Re-implement linking, validation and scoping), which solves many issues and even more importantly allows for improving execution time of the compiler. We have to hold the release back until it is integrated and does at least what the current type system can do.

Here's a more comprehensive list of what we want to have in the release:

Xtext changes :
 - Workflow generates Xtend-stubs ([generator] Add option to generate Xtend stubs instead of Java stubs)
 - Configurable Issue codes ([Validation] Preferences for Validation Codes.)
 - Full support for import sections in Xbase ([Xbase] Pull up everything about imports from Xtend)

Xtend/Xbase changes:
 - Improved Maven-support
   - build jars (including trace information) ([maven] provide plugin that adds Xtend debug info to class files)
   - better performance ([performance] Measure and improve Standalone Compilation)
   - new archetype for creating a simple project (add maven archetype)
 - Debugging without JSR-45, i.e. Debugging for Android ([Xbase] Alternative to JSR-45 for non supporting VMs)

 - support for annotations, interfaces and poor-man's enums. (Define interfaces, enums and annotations in Xtend)
 - additional operators ([xbase] Add more useful operators)
 - List Literals (Collection Literals)
 - Char literals (Support character literals)
 - Array Support ([Xbase] Add extension methods for array access and length)
 - Elvis Operator non-strict (Surprise: Elvis operator is strict)
 - extension on parameters and local vars (Allow 'extension' keyword on parameters and local variables)
 - SAM-Type Conversion (I'd like to see closures work with SAM classes)
 - Support for @SuppressWarnings ([Xtend] support for @SuppressWarnings)
 - [Provisional] Active Annotations (Active Annotations)

- Editor-Features
  - Formatter (Formatter / Pretty Printer)
  - Compiler Options ([Validation] Preferences for Validation Codes. , )
  - Organize Imports ([Organize imports] reimplemented.)
  - New Refactorings ([xtend] extract method refactoring , [refactoring] Extract local variable refactoring)
  - New Quickfixes ([Quick Fix] Create Java Class, Java Interface, Xtend Class)
  - Improved Content Assist ([content assist] Better proposals for higher-order functions)
  - JavaDoc Support ([JavaDoc] ContentAssist and Validation)

Feature freeze: March 6th
Release date : March 20th

We also want to give Gerrit a try (https://bugs.eclipse.org/bugs/show_bug.cgi?id=398639)

Cheers and happy coding!
Sven

]]> Mon, 21 Jan 2013 14:38:24 GMT http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01103.html sven.efftinge@xxxxxxx (Sven Efftinge) Re: [xtext-dev] Persisting xtext document information http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01102.html Hi Peter,yes, it's possible to store Xtext as ASTs in a model repository, but I wouldn't recommend it, because the AST, as the name Abstract Syntax Tree suggests, does not contain any information about whitespaces, line wraps and comments in your model. Th... Hi Peter,

yes, it's possible to store Xtext as ASTs in a model repository, but I wouldn't recommend it, because the AST, as the name Abstract Syntax Tree suggests, does not contain any information about whitespaces, line wraps and comments in your model. Therefore, you'd have to persist them separately.

You might want to look at the OCLinEcore Editor from Eclipse OCL. It can open Ecore files (XMI) and make the content available as text in an Xtext editor.

Are you aware that Xtext ships with two serializers? The old one "ParseTreeConstructorFragment" has been superseded by the "SerializerFragment". 

The new serializer will not produce a different syntax as long as it still has the old whitespace. And even with lost whitespace, the serializer will only do changes that your grammar explicitly allows: For example, if you use unordered groups, the order of the elements is usually not stored in your AST, and therefore the serializer can not recreate the old order if no whitespace information is available. 

If you want to go further in this direction, you should also think about how you want to persist documents with syntax errors. Since these documents can not be parsed completely you won't have a complete AST. Consequently, if you only persist the AST, the user will loose all parts of the document that are involved in syntax errors. If Syntax errors are so severe that the parser can't recover, the user will use the complete tail of the document.

regards,
  Moritz

On Jan 18, 2013, at 10:44 AM, Peter Pedron <Peter.Pedron@xxxxxxxxxxxx> wrote:

Hello xtext developers,
 
with EMFStore it is possible to persist and share EMF model instances.
I was wondering, whether it is possible, feasible or imaginable, to store and restore xtext document structure information (as far as I know this is stored in the AST) along with the model instance, in order that the original xtext document which generated a certain model instance can be restored when loading a model from the store. As you already might have understood, I try to avoid of being dependent on the generated xtext Serializer of the grammar. The use of the standard grammar serializer, when loading a model from an EMFStore, would guarantee the right semantic in the created xtext document, but might produce a different syntax and order of statements compared to the xtext document which was originally used to create the model.
 
Looking forward to your answers and opinions about this topic.
 
Peter Pedron
 
 
_______________________________________________
xtext-dev mailing list
xtext-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/xtext-dev

]]> Fri, 18 Jan 2013 10:03:23 GMT http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01102.html moritz.eysholdt@xxxxxxx (Moritz Eysholdt) [xtext-dev] Persisting xtext document information http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01101.html Hello xtext developers, with EMFStore it is possible to persist and share EMF model instances. I was wondering, whether it is possible, feasible or imaginable, to store and restore xtext document structure information (as far as I know this is stored in...

Hello xtext developers,

 

with EMFStore it is possible to persist and share EMF model instances.

I was wondering, whether it is possible, feasible or imaginable, to store and restore xtext document structure information (as far as I know this is stored in the AST) along with the model instance, in order that the original xtext document which generated a certain model instance can be restored when loading a model from the store. As you already might have understood, I try to avoid of being dependent on the generated xtext Serializer of the grammar. The use of the standard grammar serializer, when loading a model from an EMFStore, would guarantee the right semantic in the created xtext document, but might produce a different syntax and order of statements compared to the xtext document which was originally used to create the model.

 

Looking forward to your answers and opinions about this topic.

 

Peter Pedron

 

 

]]> Fri, 18 Jan 2013 09:44:40 GMT http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01101.html Peter.Pedron@xxxxxxx (Peter Pedron) [xtext-dev] Welcome Sebastian Benz as a new modeling.tmf.xtext Committer http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01100.html modeling.tmf.xtext Committers, This automatically generated message marks the completion of all the legal paperwork and webmaster provisioning for Sebastian Benz. Sebastian Benz is a new full Committer on the modeling.tmf.xtext project. Welcome! modeling.tmf.xtext Committers, This automatically generated message marks the completion of all the legal paperwork and webmaster provisioning for Sebastian Benz. Sebastian Benz is a new full Committer on the modeling.tmf.xtext project. Welcome! ]]> Tue, 15 Jan 2013 14:40:01 GMT http://dev.eclipse.org/mhonarc/lists/xtext-dev/msg01100.html sven.efftinge@xxxxxxx (portal on behalf of Sven Efftinge)