This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 247445 - Invalid site reference error with dtp-sdk-1.6.1RC2-200809090500
Summary: Invalid site reference error with dtp-sdk-1.6.1RC2-200809090500
Status: RESOLVED DUPLICATE of bug 247379
Alias: None
Product: Data Tools
Classification: Tools
Component: DataTools (show other bugs)
Version: 1.6.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: dtp.connectivity-inbox CLA
QA Contact: John Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-16 08:48 EDT by kiril mitov CLA
Modified: 2008-09-16 12:09 EDT (History)
3 users (show)

See Also:


Attachments
Error log (4.42 KB, text/plain)
2008-09-16 08:49 EDT, kiril mitov CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description kiril mitov CLA 2008-09-16 08:48:21 EDT
I was executing the smoke test for Java EE in WebTools with versions installed as described at 
http://build.eclipse.org/webtools/committers/wtp-R3.1-I/20080915064732/I-3.1-20080915064732/.

The DTP version is:
dtp-sdk-1.6.1RC2-200809090500.zip

While executing the tests there were errors from org.eclipse.datatools.* in the error log. Error log attached.

The errors were of type
Invalid site reference: %updateSiteURL in feature: org.eclipse.datatools.sqltools.doc.user
Comment 1 kiril mitov CLA 2008-09-16 08:49:22 EDT
Created attachment 112660 [details]
Error log
Comment 2 Brian Fitzpatrick CLA 2008-09-16 09:20:54 EDT
John? Do you have any idea what's going on here?
Comment 3 Brian Fitzpatrick CLA 2008-09-16 09:21:46 EDT
When we use the 3.4 build with the latest DTP builds the features have worked fine, so I have to wonder if there's something wrong with our feature definitions somewhere?
Comment 4 Brian Fitzpatrick CLA 2008-09-16 09:22:06 EDT
Xiaoying, any ideas?
Comment 5 John Graham CLA 2008-09-16 12:09:00 EDT

*** This bug has been marked as a duplicate of bug 247379 ***