To
Equinox development mailing list
cc
Subject
Re: [equinox-dev] Fw: [Bug 214801] [api tools] consider Export-Package as
API
I agree that tooling is needed in order to make this somewhat feasable.
On the OSGi mailing list there was a question posted about using EMF on
another framework
Darin Wright/Ottawa/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01/15/2008 03:19 PM
Please respond to
Equinox development mailing list
To
Equinox development mailing list
cc
[EMAIL PROTECTED]
Subject
Re: [equinox-dev] Fw: [Bug 214801] [api tools] consider
Export-Package as API
ubject
Re: [equinox-dev] Fw: [Bug 214801] [api tools] consider
Export-Package as API
Darin,
The bug report you refer to also mentions flagging when version ranges are
missing from the consumers (Import-Package/Require-Bundle). Turning both
the producer (Export-Package) and co
: [EMAIL PROTECTED]
Date: 01/15/2008 02:25 PM
Subject: Re: [equinox-dev] Fw: [Bug 214801] [api tools] consider
/2008 04:24 PM
Please respond to
Equinox development mailing list
To
Equinox development mailing list
cc
Subject
Re: [equinox-dev] Fw: [Bug 214801] [api tools] consider Export-Package as
API
I agree that tooling is needed in order to make this somewhat feasable.
On the OSGi mailing list t
John Arthorne <[EMAIL PROTECTED]>
To:
Equinox development mailing list
Date:
01/11/2008 03:27 PM
Subject:
Re: [equinox-dev] Fw: [Bug 214801] [api tools] consider Export-Package as
API
I don't think we can even contemplate this without full tooling
automation. As Tom says, we s
:24 PM
Please respond to
Equinox development mailing list
To
Equinox development mailing list
cc
Subject
Re: [equinox-dev] Fw: [Bug 214801] [api tools] consider Export-Package as
API
I agree that tooling is needed in order to make this somewhat feasable.
On the OSGi mailing list there
g list
Date: 01/11/2008 03:27 PM
Subject: Re: [equinox-dev] Fw: [Bug 214801] [api tools] consider
Export-Package
: [Bug 214801] [api tools] consider
Export-Package as API
Without tooling this will be difficult. If we wanted to use the big hammer
approach the we would have the API tooling (or plain old PDE) mark exports
without versions as a warning/error by default or update each project
settings
list
To
Equinox development mailing list
cc
Subject
Re: [equinox-dev] Fw: [Bug 214801] [api tools] consider Export-Package as
API
Without tooling this will be difficult. If we wanted to use the big hammer
approach the we would have the API tooling (or plain old PDE) mark exports
witho
Date: 01/11/2008 02:17 PM
Subject:[equinox-dev] Fw: [Bug 214801] [api tools] consider
Export-Package
Tom raises a good point that we keep letting slide. Are we going to
ensure that all export package statements have version numbers for 3.4? If
we have API tooling for this then it would likely be reasonable to start
doing. Even without tooling today, we could introduce version numbers
based o
12 matches
Mail list logo
