Xtend 2.4.3 is out

[Sven Efftinge]

The subject already states it: Version 2.4.3 has been released.
That said, the archives on maven central are not fully there yet but will be later today.

I have written a blog post giving an overview of the included changes:

http://blog.efftinge.de/2013/09/xtend-and-xtext-243-is-out.html

Cheers,
Sven

[Christian Vogel]

Just want to say, great work guys.

[Meinte Boersma]

Nice work! :)

The blog and change list doesn't state it explicitly, but I think performance has been improved as well: does my perception match reality? ;)

[Artur Biesiadowski]

Seems that entire world tries to download new xtend right now, update site is soo slow...

[Sven Efftinge]

On Sep 4, 2013, at 4:31 PM, Meinte Boersma <meinte....@gmail.com> wrote:

> Nice work! :)
>
> The blog and change list doesn't state it explicitly, but I think performance has been improved as well: does my perception match reality? ;)

Yes, performance improvements have highest priority, also for the next release again.

[Tristan de Inés]

Great work guys. I definitively also notice performance improvements while working with Xtend. I like the i18n example on Sven's blog and have already added it to my repertoire. I hope I won't get sued.  ;)

I suppose you have an extension method defined that isn't mentioned though? "field.initializerAsString" won't work on it's own, so I replaced it with "field.initializer.toString"

[Sven Efftinge]

On Sep 6, 2013, at 4:48 PM, Tristan de Inés <tristan...@gmail.com> wrote:

I suppose you have an extension method defined that isn't mentioned though? "field.initializerAsString" won't work on it's own, so I replaced it with "field.initializer.toString"

Oh yes, I left that out. It should be :

def getInitializerAsString(FieldDeclaration f) {

val string = f.initializer?.toString

if(string == null)

return "empty string"

return string.substring(1, string.length - 1)

}

[panuvi...@gmail.com]

I would like to move an existing legacy Java project INCREMENTALLY to Xtend. 

However the lack of an Ant task is currently holding me back. One alternative

solution would be if there was a way for Eclipse XTend tooling to generated the Java-

files in the same directory as the XTend-file. Then my Ant scripts would

automatically pick the Java-file and not worry about Xtends, I presume. 

The ability to easily mix Xtend and Java would entice more users

to use Xtend.

Cheers

-Panu

[Sven Efftinge]

You can change the compiler preferences in eclipse on a per project level or per workspace.

For ant there is :

<project default="compile">
	<!--  
	Assuming target/libs folder contains:
		aopalliance-1.0.jar
		guava-10.0.1.jar
		guice-3.0.jar
		hamcrest-core-1.1.jar
		javax.inject-1.jar
		jsr305-1.3.9.jar
		junit-4.10.jar
		log4j-1.2.15.jar
		org.eclipse.xtend.lib-2.4.3.jar
		org.eclipse.xtend.standalone-2.4.3.jar
		org.eclipse.xtext.xbase.lib-2.4.3.jar
	-->
	
	<property name="libs-dir" location="target/libs" />

	<path id="xtend.deps">
		<fileset dir="${libs-dir}">
			<include name="*.jar" />
		</fileset>
	</path>

	<taskdef name="xtendc" classname="org.eclipse.xtend.core.compiler.batch.XtendCompilerAntTask">
		<classpath>
			<fileset dir="${libs-dir}">
				<include name="org.eclipse.xtend.standalone-2.4.2*.jar" />
			</fileset>
		</classpath>
	</taskdef>

	<target name="compile">
		<xtendc destdir="ant-gen" srcdir="src/main/java">
			<classpath refid="xtend.deps" />
		</xtendc>
	</target>
</project>

Multiple source folders can be defined as a path:
<target name="compile">
	<xtendc destdir="ant-gen">
		<srcdir>
			<pathelement path="src/main/java" />
			<pathelement path="src/main/java2" />
		</srcdir>
		<classpath refid="xtend.deps" />
	</xtendc>
</target>

--
You received this message because you are subscribed to the Google Groups "Xtend Programming Language" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xtend-lang+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.