- This topic has 9 replies, 7 voices, and was last updated 18 years, 10 months ago by
.
-
Posts
-
Many of the features that I am eagerly anticipating (facelets, multiple application server instances, facelets, etc.) are scheduled for the 5.0 release.
1. What will be officially included in that release?
2. When the release will be available?Many of the features that I am eagerly anticipating (facelets, multiple application server instances, facelets, etc.) are scheduled for the 5.0 release.
Don’t confuse my comment in the facelets thread about the “5.x release stream” and 5.0, facelets have not been committed to the 5.0 release at this time. The only thing that will officially be in is what is on our roadmap here: http://www.myeclipseide.com/ContentExpress-display-ceid-6.html
Keeping in mind that this may change based on demand and based on if we do a 4.2, some features may come out of the 5.0 release and go into 4.2 or visa versa. We are a quick moving company which means far-off targets are not chisled in stone… which so far has been a very good thing for our customers.
@support-rkalla wrote:
We are a quick moving company which means far-off targets are not chisled in stone…
I completely agree. It is perfect for quickly supporting new technologies such as facelets.
I would make a bid for facelets at least minimal facelets support in 5.0:
1. I think that it would be easy to implement. You would only need to apply your ‘Classic’ JSP Editor to the .xhtml extensions and extend your tld support to the facelet-taglib_1_0.dtd.
2. With the recent 1.0 release, it should start gaining popularity.
3. Facelets is the perfect combination of the industry supported component model found in JSF and the well-loved non-JSP templating found in tapestry.Here is where I could use some support from other Facelets fans to back me up with the +1’s.
Well Facelets are nice, but face it WTP 1.0.1 support is much more important, since almost all eclipse extensions are currently moving towards it. Face it witout wtp 1.0.1 no birt, no dali nothing which is remotely db or web centric.
Up until now it was good that myeclipse did not move towards WTP 0.x because until 1.0.1 the WTP hat too many bugs, but the situation changes now. Facelets can be done without a dedicated editor, but getting all the eclipse db and webcentric extensions up and running will be impossible without a WTP foundation in the near future.werpu,
Your assessment is dead on, which is why MyEclipse 5.0 is such an important move for future work.Is the first milestone still planned for end March? I noticed the roadmap hasn’t been updated for a few months.
