Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334348 - Build errors found in Today's Datatools 1.9.0 Build (BuildId: v20110114-1459 )
Summary: Build errors found in Today's Datatools 1.9.0 Build (BuildId: v20110114-1459 )
Status: CLOSED FIXED
Alias: None
Product: Data Tools
Classification: Tools
Component: SQL Results View (show other bugs)
Version: 1.9   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: dtp.sqldevtools-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-14 02:44 EST by Yong Jiang CLA
Modified: 2011-01-16 03:17 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yong Jiang CLA 2011-01-14 02:44:41 EST
Error log:
Bundle org.eclipse.datatools.sqltools.result_0.0.0 failed to resolve.:
        Unsatisfied import package org.apache.lucene.analysis_[1.9.0,3.0.0).
        Unsatisfied import package org.apache.lucene.analysis.standard_[1.9.0,3.0.0).
        Unsatisfied import package org.apache.lucene.document_[1.9.0,3.0.0).
        Unsatisfied import package org.apache.lucene.index_[1.9.0,3.0.0).
        Unsatisfied import package org.apache.lucene.queryParser_[1.9.0,3.0.0).
        Unsatisfied import package org.apache.lucene.search_[1.9.0,3.0.0).
        Unsatisfied import package org.apache.lucene.store_[1.9.0,3.0.0).

Can also refer to build.log for details:
http://www.eclipse.org/downloads/download.php?file=/datatools/downloads/drops/N_DTP_1.9/build.log
Comment 1 Brian Payton CLA 2011-01-14 13:39:53 EST
I'm trying to fix bug 333514, so I replaced the Require-Bundle of org.apache.lucene in the MANIFEST.MF of org.eclipse.datatools.sqltools.result with a set of Import-Package statements.  Following good OSGi practice, I included version ranges on the Import-Package statements.  However, it turns out that while Lucene 2.9.1 has package versions, Lucene 1.9.1 does not.  I made the mistake of building with Eclipse 3.7 (Lucene 2.9.1) instead of Eclipse 3.6.1, so I didn't catch the error.

I'll remove the package version ranges from the Import-Package statements.

Unfortunately this leaves us exposed to a potential future problem in that Lucene can change again with a major (breaking) version change without us being aware of it.
Comment 2 Brian Payton CLA 2011-01-14 13:54:56 EST
Checked in fix.  See bug 333514.
Comment 3 Yong Jiang CLA 2011-01-16 03:17:15 EST
Verified in DTP 1.9.0 v20110116-1352