Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Bundle Version Management

Markus,

I see! That's a good example we'd never considered. I think our tool would produce a warning saying these are duplicates when in fact that's intended to include two different versions. We'll make the necessary changes to support that. Thanks!!

Cheers,
Ed


On 17/08/2012 4:01 PM, Markus Keller wrote:
John Arthorne wrote on 2012-08-17 15:52:04:
Ed Merks <ed.merks@xxxxxxxxx> wrote on 08/17/2012 08:49:16 AM:
2. And the more general question, is there any value in hard coding
the number even for include and plugin declarations?
I don't think I've ever seen anything other than 0.0.0, but one
possibility is a case where you don't actually want to include the
"greatest" available version of something.
We have an example of this in the org.eclipse.jdt/feature.xml. We ship
both JUnit 3 and JUnit 4, so we need at least one entry with a fixed
version number (we made them both fixed -- not sure if replacing 4.10.0.q
with 0.0.0 would work):

...
    <plugin
          id="org.eclipse.jdt.ui"
          download-size="0"
          install-size="0"
          version="0.0.0"
          unpack="false"/>

    <plugin
          id="org.junit"
          download-size="0"
          install-size="0"
          version="4.10.0.qualifier"/>

    <plugin
          id="org.junit"
          download-size="0"
          install-size="0"
          version="3.8.2.qualifier"/>
...

Markus

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



Back to the top