[ve-dev] VE version 1.3 and 1.4

["Janak Mulani" <janak.mulani@xxxxxxxxx>]

Hi Yves,
 
When are VE 1.3 (for Europa) and VE 1.4 (for Ganymede) likely to be
officially available from Eclipse VE site?

Thanks and regards,

Janak

-----------------------------------------
Janak Mulani

email: janak.mulani@xxxxxxxxx
url: http://www.canoo.com <http://www.canoo.com/> 

Beyond AJAX - Java Rich Internet Applications

http://www.canoo.com/ulc
----------------------------------------- 

 


________________________________

	From: ve-dev-bounces@xxxxxxxxxxx
[mailto:ve-dev-bounces@xxxxxxxxxxx] On Behalf Of Yves YANG
	Sent: Friday, November 28, 2008 5:26 PM
	To: 'Discussions people developing code for the Visual Editor
project'
	Subject: RE: [ve-dev] Changes being proposed for JEM bundle
structure ... 
	
	

	Hi David,

	 

	I have posted a message to follow this issue and to see the impact
for VE. 

	 

	Best regards

	Yves YANG

	Soyatec - Eclipse OutSourcing & XAML for java

	http://www.soyatec.com <http://www.soyatec.com/> 

	Tel: +33 1 60 13 06 67

	Mobile: +33 6 20 74 39 45

	Fax: +33 9 58 07 06 67

	________________________________

		From: ve-dev-bounces@xxxxxxxxxxx
[mailto:ve-dev-bounces@xxxxxxxxxxx] On Behalf Of David Williams
	Sent: Wednesday, November 26, 2008 8:53 AM
	To: ve-dev@xxxxxxxxxxx
	Subject: [ve-dev] Changes being proposed for JEM bundle structure
... 

	 

	As I hope you know, the JEE Tools project took over stewardship of
JEM a couple of years ago. 
	
	We've had a bug/feature request to un-nest some embedded jars, so
that people can compile against the binary version of those bundles and
jars and not have to have the complete source tree present.
	This is, sort of, a well known PDE limitation, where it works a
little differently that what a pure OSGi runtime would allow. 
	
	I think it is feasible to un-nest these jars, given OSGi, compared
to the original Eclipse Plugin model, which was used when this JEM code
was first designed and developed. That is, we'd refactor the nested jars
out of the current bundle, and make them bundles too. That makes PDE
happy, and the bundles can still be used as ordinary jars (and the OSGi
directives ignored). 
	
	If this works, it will be nothing but good news for projects that
pre-req all of WTP anyway (not sure what VE does) but for projects who
"pick and choose" exactly which bundles to get for their feature or
products, then they will have to be aware of the fact that they need to
get two additional bundles from JEM. Their code should not have to change
at all ... the bundles just have to be present (they used to be present by
virtue of being nested inside of other jars, which they no longer will
be). 
	
	You can follow along in this bug, if you are interested. 
	https://bugs.eclipse.org/bugs/show_bug.cgi?id=256441
	
	The "rub" is that we would like to provide this new structure in
our Ganymede SR2 release. Normally, restructuring should be avoided for a
maintenance release, but since there's no real change of code or
dependencies, I think it is reasonable to propose. 
	
	Let us know if you object, or if are overjoyed because it will
make VE easier to build :) 
	Comments in the bugs are fine, and once it's ready, if any of you
can give it an early test, that would be very helpful. 
	
	Thanks,