Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] CBI Rebasing platform to M7

The following pom.xml block should additionally constrain versions of
org.apache.lucene and org.apache.lucene.analysis bundles to [2.9,3.0)
range at compile time. There are several projects that use this to solve
similar problem, so search for <extraRequirements> in pom.xml files if
you want to see working examples.

  <build>
    <plugins>
      <plugin>
        <groupId>org.eclipse.tycho</groupId>
        <artifactId>target-platform-configuration</artifactId>
        <configuration>
          <dependency-resolution>
            <extraRequirements>
              <requirement>
                <type>eclipse-plugin</type>
                <id>org.apache.lucene</id>
                <versionRange>[2.9,3.0)</versionRange>
              </requirement>
              <requirement>
                <type>eclipse-plugin</type>
                <id>org.apache.lucene.analysis</id>
                <versionRange>[2.9,3.0)</versionRange>
              </requirement>
            </extraRequirements>
          </dependency-resolution>
        </configuration>
      </plugin>
    </plugins>
  </build>


--
Regards,
Igor

On 12-05-08 3:48 PM, Thanh Ha wrote:
On 05/08/2012 02:49 PM, Igor Fedorenko wrote:
It is possible to 'lock' lucene to specific version or version range in
pom.xml but I'd try to understand why the upper bound for the version
was removed first.


How can I lock lucene to a specific version at compile time via pom.xml?

Thanks,


Thanh
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev


Back to the top