RE: [wtp-incubator-dev] Build problem. Missing EMF validation component

["Branekov, Danail" <danail.branekov@xxxxxxx>]

You are right, we needed to separate the existing JAX-WS tooling from the newly contributed one.
Would removing the "sapnw" fragment be OK? For example, "org.eclipse.jst.ws.jaxws.sapnw.dom.runtime" would result in "org.eclipse.jst.ws.jaxws.dom.runtime"

Shane, Oisin, do you have a better proposal?

Regards, Danail

-----Original Message-----
From: wtp-incubator-dev-bounces@xxxxxxxxxxx [mailto:wtp-incubator-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Monday, September 28, 2009 10:38 AM
To: WTP Incubator Dev list
Subject: RE: [wtp-incubator-dev] Build problem. Missing EMF validation component

> Do you think that such a naming convention is some sort of issue?

Yes. Everything we do must be vendor neutral and having a product name 
(basically) as part of a package name starts to crosses that line. Also, 
remember, once code is donated to Eclipse under the EPL, the code itself 
no longer "belongs" to any particular product or company and I think using 
that convention in the package name could be misinterpreted. I'll assume 
you were not consciously trying to promote SAP or advertise NetWeaver via 
package names and instead it was just handy to use history in keeping 
things straight. But, you'll need to find another way. Preferably based on 
the function and architecture of the bundle and eventually have a fully 
integrated set of bundles whose history does not matter, in the way you 
organize it. 

Let me know if I can help in further discussions. 

Once you have moved/renamed the packages, let me know ... I'd like to 
delete the other, then obsolete directories from CVS. 

Thanks, 







From:
"Branekov, Danail" <danail.branekov@xxxxxxx>
To:
WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
Date:
09/28/2009 02:41 AM
Subject:
RE: [wtp-incubator-dev] Build problem. Missing EMF validation   component
Sent by:
wtp-incubator-dev-bounces@xxxxxxxxxxx



Hi David,

> As I started to look into it, I noticed some packages with 'sap' as part 

> of their name, such as 
> org.eclipse.jst.ws.jaxws.sapnw.dom.runtime
> 
> What does that 'sap' stand for? Surely not 'SAP'?! 

The plugins which SAP contributed and will contribute to Eclipse originate 
from a product called "SAP NetWeaver". This is what "sapnw" stands for. 
Do you think that such a naming convention is some sort of issue?

Regards, Danail


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



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