Re: [wtp-incubator-dev] A note on incubator builds

[David M Williams <david_williams@xxxxxxxxxx>]

> As for the .xml.ui plugins, it
might be an idea to hive these off 
> somewhere else anyway. I would prefer to see them in a separate 
> project thats useful for XML generally, rather than just XSL. What
> do you think?

I think it's fine where it is, and XML
stuff can be "incubated" in XSL (especially since the are all
related to the same Source Editing subproject. of WTP). 
But, I agree, this may be something
that can "graduate" directly into the xml code on it's own schedule
(perhaps this 2008 release?) since it's just enhancing an existing feature,
not really something new.

From:	DOUG SATCHWELL <doug.satchwell@xxxxxxxxxxxxxx>
To:	WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
Date:	01/03/2008 10:57 AM
Subject:	Re: [wtp-incubator-dev] A note on incubator builds

---

Thanks for helping us out David!
 
We should not add the other plugins to the feature at
the moment. I don't think any of the editing/validation is quite ready.
When it is ready, we should probably create 2 further features - one for
the launching and one for the editing. Then this super-feature can just
include those two.
 
The xsl.launch plugin will be deleted eventually. Theres
just a couple of things we need to extract from it first. As for the .xml.ui
plugins, it might be an idea to hive these off somewhere else anyway. I
would prefer to see them in a separate project thats useful for XML generally,
rather than just XSL. What do you think?
 
Cheers,
 
Doug


 
----- Original Message ----
From: David M Williams <david_williams@xxxxxxxxxx>
To: wtp-incubator-dev@xxxxxxxxxxx
Sent: Thursday, 3 January, 2008 3:28:49 PM
Subject: [wtp-incubator-dev] A note on incubator builds


As as been noted, I'll help set up the incubator builds. I'll look into
it over the next few days. 

I'll do which ever is easiest, but my tentative plan is to set it up to
be fully integrated, and built each time WTP is, 
though may set it up to also "pre-req" a specified version of
WTP, and it's pre-reqs. (This is similar to how 
we currently have Dali set up). 

To be sure I understand the intent, though, the only thing to build so
far is the feature called 
org.eclipse.wst.xsl.feature 

which pulls in the following plugins 
org.eclipse.wst.xsl.debug 
org.eclipse.wst.xsl.debug.ui 
org.eclipse.wst.xsl.launching 
org.eclipse.wst.xsl.saxon 
org.eclipse.wst.xsl.xalan 


These leaves 4 other plugins not in a feature: 
org.eclipse.wst.xml.ui.editor.outline 
org.eclipse.wst.xml.xpath.ui 
org.eclipse.wst.xsl.launch 
org.eclipse.wst.xsl.ui 

I'm pretty sure the intent is to archive the 'launch' plugin (that is,
it will never be needed). 

But am not clear on status of the other three. 

Let me know how and when they need to be packaged. 
By guess is two of them could be added to the feature? 
org.eclipse.wst.xml.xpath.ui 
org.eclipse.wst.xsl.ui 

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