Very awesome. Thanks David! I added a rule for **/provisional/** and all
is good.
Cheers,
Doug.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David M Williams
Sent: Friday, May 30, 2008 6:52 PM
To: Equinox development ma
I fyou run the installer in shared mode it uses one profile registry and
creates a new profile for every different thing you install.
Jeff
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:equinox-dev-
> [EMAIL PROTECTED] On Behalf Of Thomas Hallgren
> Sent: Friday, May 30, 2008 5:38
> It would be interesting to raise an enhancement request on PDE to
> allow developers to ignore the errors/warnings from certain bundles.
> The problem now is that if you turn off the warning you don?t get it
> for any other uses of non-API.
I'm sure new features could add to ease-of-use, but
For now we are targeting 3.5. However I hope to have a large chunck of the
API defined for early 2009.
|>
| From: |
|>
>--
Since nobody bit on Jeff's request for an enhancement request, I opened bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=234947 to discuss these
issues.
Tom
From:
I'm curious about how the profile registry is intended to be used. At
present, each eclipse installation will have it's own registry. Are
there any plans to have some kind of registry hierarchy (global,
machine, user) or other ideas that would make it possible to for
instance discover all insta
The bundle activation policy (specified by the Bundle-ActivationPolicy
header) indicates to the framework how the bundle should be activated when
Bundle#start(Bundle.START_ACTIVATION_POLICY) is called. When the policy is
"lazy" then the BundleActivator#start(BundleContext) method is delayed
until
Jeff McAffer wrote:
Darn! You have discovered the secret plan. By annoying people we will
get more contributions… Hmmm, perhaps not. Good news is that in the
next release you should expect to see some real API.
Just for my clarification...is that next release 3.5 (eta June 2009) or
someth
Warren,
1) This is what I notice when I tried running your director command on a
product I exported:
- the "-metadataRepository" and "-artifactRepository" values need to be
URLs: use "file:C:\testproduct\repository"
- I found I needed to specify -installIU to get anything out. In this
case th
Hi all,
I had a doubt about bundle activation. I have been reading the sections about
lazy activation policy in osgi spec and i am a little confused.
1) What is the difference between Bundle Activation and calling
BundleActivator.start() method.
2) Does bundle activation mean loading of all cl
Darn! You have discovered the secret plan. By annoying people we will get
more contributions. Hmmm, perhaps not. Good news is that in the next
release you should expect to see some real API.
If it makes you feel any better, our own tools are not friends and we get
all the warnings in our cod
Well good thing I'm so dedicated to p2 then ;)
Thanks for the clarification Jeff. Maybe my solution is to contribute
everything I'm doing to p2 so it can get included in the allowed list :)
Cheers,
Doug
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED
It was the joint decision of the team and the PMC that p2 would not have any
API. By definition, anything that is not API is marked as x-internal =
true. As a result, and by design, you get a warning that you are using
something that is not API. I agree that this is annoying however, no one
will
The map file has been updated for the following Bug changes:
+ Bug 228247. [ui] After updating to a newer I build, should not prompt to
"Apply Changes" (FIXED)
+ Bug 233596. [ui] Externalized license text can get whitespace compressed
(FIXED)
+ Bug 234154. Names in .properties files are not used
Hey gang,
I'm just wondering why you've hidden all of the provisional APIs away
from everyone other than p2 itself? I'm getting really tired of seeing
Discouraged access warnings in my generators and installers. Just
curious (and venting :)
Doug.
___
Toni made exactly the same comment via my bug tracker!
I agree, I've intended all along to write such a chapter, I just need
to get around to it...
Thanks
Neil
On Fri, May 30, 2008 at 9:45 AM, Alin Dreghiciu <[EMAIL PROTECTED]> wrote:
> +1 for having the api as a separated bundle (third in this
Yes Toni , Its separate you are right !
Regards,
Santosh Akhilesh
Ph: 9845482201
**
This email and its attachments contain confidential information from
HUAWEI, which is intended only for the person or entit
Dear Toni, Neil , Alin,
Thanks for your suggestions.
I was toying with OSGI and it was my first program, I understand that having
things exported from Bundle makes more sense and its clean approach.
However I just wanted to know what the real reason was since I faced this
problem.
Now I am cle
+1 for a "best practices" chapter in a "OSGi in practice" book!
Just added an issue for that here
http://neilbartlett.name/mantis/view.php?id=33 so you can't go away without it
;-)
Original-Nachricht
> Datum: Fri, 30 May 2008 10:45:55 +0200
> Von: "Alin Dreghiciu" <[EMAIL PROTE
+1 for having the api as a separated bundle (third in this case)
Neil, you could add an "Best Practices" chapter to your book.
--
Alin Dreghiciu
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
http://www.qi4j.org - New Energy for Java - Domain Driven Developme
@Neil,
You are right hence i expected the need to include the api inside the bundle as
well as a given need.
Many implementations of services include the api as a convinience for the end
user.
(they sometimes just want - say - logging and don't care of stupid compdium
bundles as reqirement).
As
Santosh,
I'm glad you got this working but please bear in mind that it is a
poor design choice to export an interface from the same bundle that
provides the service, because it does not truly de-couple the consumer
from the provider, and it makes it much harder for you to update the
provider bundl
22 matches
Mail list logo
