Re: [equinox-dev] p2-gerrit HIPP instance is unavailable
Hi, This is not normal. I've just hit the restart button and the restart has not completed yet. I suspect that the instance is actually up and probably building a contribution, but not accessible. I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=509179 Pascal On 12/13/2016 4:53 PM, Mykola Nikishov wrote: Hi there, Is it expected that https://hudson.eclipse.org/equinox/job/p2-gerrit/ AKA hipp2 is unavailable right now: This HIPP instance is currently unavailable. It may be turned off, or it may be unresponsive. Members of the project can restart this service using the HIPP Control tools ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Convergence between p2 and the OSGiresolver+repository
From an API level I do not think there is a big deal. The resolver could just fetch all resources at start. It can of course only return a single solution. This might be unfortunate but I find it hard to see why that is a limitation since any solution that satisfies all requirements should be ok. The first case where this matters is install time, where you want to make sure that users are getting the most recent versions of bundles (if of course it is eligible). The second case where we do more advance solution search is during the reconciliation, where we need to search for the solution that will include the least number of IU to remove. Kind regards, Peter Kriens On 17 nov. 2016, at 14:41, Thomas Watson <tjwat...@us.ibm.com <mailto:tjwat...@us.ibm.com>> wrote: I will be interested to see if you can successfully map the OSGi uses concept into the SAT solver p2 uses. I briefly looked at that a long time ago when we were refactoring the Equinox framework (Luna) and were replacing the old Equinox resolver. It was far from obvious how you would achieve this. At that time I opt'ed to collaborate with a common resolver in Felix for the Equinox framework. But this is no magic implementation. There are still cases where the OSGi resolver algorithm will blow up. In Equinox we try to minimize that possibility by avoiding the resolution of all (1) bundles at once. But as Pascal states, this does leave out some possible valid solutions that you will then not discover while resolving. If you do focus on how to map uses into the SAT solver in p2 I would be interested in collaborating to see if such a resolver would outperform the Felix resolver we use at runtime. My hope at the time I was looking into this was to map an OSGi Resolver service on top of the SAT solver implementation. But I cannot remember how the SAT solver is driven. I suspect the split between the OSGI Resovler and the OSGi ResolveContext will not fit well into the SAT implementation model. Tom From: Todor Boev <rinsv...@gmail.com <mailto:rinsv...@gmail.com>> To: Equinox development mailing list <equinox-dev@eclipse.org <mailto:equinox-dev@eclipse.org>> Date: 11/17/2016 02:22 AM Subject: Re: [equinox-dev] Convergence between p2 and the OSGi resolver+repository Sent by: equinox-dev-boun...@eclipse.org <mailto:equinox-dev-boun...@eclipse.org> - Regarding batch resolution: Ultimately I think the batch processing is about performance. At provisioning time where finding the best solution trumps speed the resolver can be executed against the entire set. But I have to try this. After than the equinox runtime should be able to re-create a correct (maybe not identical) resolution from the much smaller set of resources. I have tried the resolver against about 700 bundles and it did okay, but this is well short of 10,000. More research requiredsome day. - Regarding the additional p2 concepts: Can you point me to the documentation of how the resolution problem is converted to a SAT formula? Best regards On Thu, Nov 17, 2016 at 6:20 AM, Pascal Rapicault <_pascal@rapicault.net_ <mailto:pas...@rapicault.net>> wrote: On 11/16/2016 10:49 AM, Todor Boev wrote: - Regarding resolver behavior: The goal is actually to replace the behavior of the objective function with the behavior of the resolver. This is the best way to guarantee that both p2 and the OSGi runtime agree on what is a consistent set of bundles. For example p2 does not take into account package uses constraints which leads to p2 selecting bundles that later fail to resolve at runtime. It does not matter which way to resolve is better, so long as they agree. Since the OSGi resolver is very unlikely to change it falls on p2 to match it's behavior. My current company (software ag) has had quite a number of issues where essentially p2 sets up the resolver to fail. - Regarding resolver scalability: The resolution is split between the resolver which processes the current set of resources and the resolver context which selects candidates when asked. If the goal is to support a very high number of candidates - a resolver context impl optimized for searches in a large candidate space can be provided. If the goal is to produce a solution that includes a very high number of resources - more research is required. Even if the initial set is 10,000 the resolver can be asked to process them not all at once, but incrementally in batches or even one by one. Which is in fact what equinox does today. The thing is that if you look at a subset of the available bundles, you may find a solution that is not the optimal one. p2 will consider all the possible candidates in one resolution invocation. I am trying to determine if it makes sense to invest effort in prototyping this giv
[equinox-dev] Uses constraints in p2 (was Convergence between p2 and the OSGiresolver+repository)
On 11/17/2016 8:54 AM, Peter Kriens wrote: I remember trying to map uses constraints to a boolean expression but could not find any way that did not blow up the expression size. This seemed very unfortunate because I think they can actually be used to reduce the search space considerably. I'm really happy to see that there is at least 3 people if not more interested in the exercise of seeing how to encode uses constraints to SAT. How do you guys want to get moving on this? Peter, would you happen to still have what you had done? From an API level I do not think there is a big deal. The resolver could just fetch all resources at start. It can of course only return a single solution. This might be unfortunate but I find it hard to see why that is a limitation since any solution that satisfies all requirements should be ok. Kind regards, Peter Kriens On 17 nov. 2016, at 14:41, Thomas Watson <tjwat...@us.ibm.com <mailto:tjwat...@us.ibm.com>> wrote: I will be interested to see if you can successfully map the OSGi uses concept into the SAT solver p2 uses. I briefly looked at that a long time ago when we were refactoring the Equinox framework (Luna) and were replacing the old Equinox resolver. It was far from obvious how you would achieve this. At that time I opt'ed to collaborate with a common resolver in Felix for the Equinox framework. But this is no magic implementation. There are still cases where the OSGi resolver algorithm will blow up. In Equinox we try to minimize that possibility by avoiding the resolution of all (1) bundles at once. But as Pascal states, this does leave out some possible valid solutions that you will then not discover while resolving. If you do focus on how to map uses into the SAT solver in p2 I would be interested in collaborating to see if such a resolver would outperform the Felix resolver we use at runtime. My hope at the time I was looking into this was to map an OSGi Resolver service on top of the SAT solver implementation. But I cannot remember how the SAT solver is driven. I suspect the split between the OSGI Resovler and the OSGi ResolveContext will not fit well into the SAT implementation model. Tom From: Todor Boev <rinsv...@gmail.com <mailto:rinsv...@gmail.com>> To: Equinox development mailing list <equinox-dev@eclipse.org <mailto:equinox-dev@eclipse.org>> Date: 11/17/2016 02:22 AM Subject: Re: [equinox-dev] Convergence between p2 and the OSGi resolver+repository Sent by: equinox-dev-boun...@eclipse.org <mailto:equinox-dev-boun...@eclipse.org> - Regarding batch resolution: Ultimately I think the batch processing is about performance. At provisioning time where finding the best solution trumps speed the resolver can be executed against the entire set. But I have to try this. After than the equinox runtime should be able to re-create a correct (maybe not identical) resolution from the much smaller set of resources. I have tried the resolver against about 700 bundles and it did okay, but this is well short of 10,000. More research requiredsome day. - Regarding the additional p2 concepts: Can you point me to the documentation of how the resolution problem is converted to a SAT formula? Best regards On Thu, Nov 17, 2016 at 6:20 AM, Pascal Rapicault <_pascal@rapicault.net_ <mailto:pas...@rapicault.net>> wrote: On 11/16/2016 10:49 AM, Todor Boev wrote: - Regarding resolver behavior: The goal is actually to replace the behavior of the objective function with the behavior of the resolver. This is the best way to guarantee that both p2 and the OSGi runtime agree on what is a consistent set of bundles. For example p2 does not take into account package uses constraints which leads to p2 selecting bundles that later fail to resolve at runtime. It does not matter which way to resolve is better, so long as they agree. Since the OSGi resolver is very unlikely to change it falls on p2 to match it's behavior. My current company (software ag) has had quite a number of issues where essentially p2 sets up the resolver to fail. - Regarding resolver scalability: The resolution is split between the resolver which processes the current set of resources and the resolver context which selects candidates when asked. If the goal is to support a very high number of candidates - a resolver context impl optimized for searches in a large candidate space can be provided. If the goal is to produce a solution that includes a very high number of resources - more research is required. Even if the initial set is 10,000 the resolver can be asked to process them not all at once, but incrementally in batches or even one by one. Which is in fact what equinox does today. The thing is that if you look at a subset of the available bundles, you may find a solut
Re: [equinox-dev] Convergence between p2 and the OSGi resolver+repository
On 11/17/2016 3:22 AM, Todor Boev wrote: - Regarding batch resolution: Ultimately I think the batch processing is about performance. At provisioning time where finding the best solution trumps speed the resolver can be executed against the entire set. But I have to try this. After than the equinox runtime should be able to re-create a correct (maybe not identical) resolution from the much smaller set of resources. I have tried the resolver against about 700 bundles and it did okay, but this is well short of 10,000. More research requiredsome day. - Regarding the additional p2 concepts: Can you point me to the documentation of how the resolution problem is converted to a SAT formula? Daniel pointed you at an article, the code can be found here http://git.eclipse.org/c/equinox/rt.equinox.p2.git/tree/bundles/org.eclipse.equinox.p2.director/src/org/eclipse/equinox/internal/p2/director/Projector.java Best regards On Thu, Nov 17, 2016 at 6:20 AM, Pascal Rapicault <pas...@rapicault.net <mailto:pas...@rapicault.net>> wrote: On 11/16/2016 10:49 AM, Todor Boev wrote: - Regarding resolver behavior: The goal is actually to replace the behavior of the objective function with the behavior of the resolver. This is the best way to guarantee that both p2 and the OSGi runtime agree on what is a consistent set of bundles. For example p2 does not take into account package uses constraints which leads to p2 selecting bundles that later fail to resolve at runtime. It does not matter which way to resolve is better, so long as they agree. Since the OSGi resolver is very unlikely to change it falls on p2 to match it's behavior. My current company (software ag) has had quite a number of issues where essentially p2 sets up the resolver to fail. - Regarding resolver scalability: The resolution is split between the resolver which processes the current set of resources and the resolver context which selects candidates when asked. If the goal is to support a very high number of candidates - a resolver context impl optimized for searches in a large candidate space can be provided. If the goal is to produce a solution that includes a very high number of resources - more research is required. Even if the initial set is 10,000 the resolver can be asked to process them not all at once, but incrementally in batches or even one by one. Which is in fact what equinox does today. The thing is that if you look at a subset of the available bundles, you may find a solution that is not the optimal one. p2 will consider all the possible candidates in one resolution invocation. I am trying to determine if it makes sense to invest effort in prototyping this given that subtle changes in behavior are in fact a goal, rather than an issue. Even though on the surface p2 resolver looks similar to what the OSGi resolver does, p2 has at least 2 additional concepts: 1) the expression of strict negation 2) the concept of patch I'm tempted to think that it is probably simpler to add support for the uses-clause in p2 (this has been a known issue for years, but I can't seem to find the bug tonight) than it is to replace the resolver completely and get all the tests to pass. The encoding of dependencies to a SAT formula is well documented and so are the optimization functions. On Wed, Nov 16, 2016 at 4:44 AM, Pascal Rapicault <pas...@rapicault.net <mailto:pas...@rapicault.net>> wrote: On 11/15/2016 12:52 PM, Todor Boev wrote: Hello, Are there any plans to bring together p2 and OSGi resolver+repository standards? There is no immediate plan for this. It should be beneficial to have similar (maybe identical?) dependency resolution at provisioning time and later at runtime. The install time and runtime resolvers resolve a slightly different problem because the install time resolver has to look for candidates in a large space, whereas the runtime one has to connect as many components together. I have not tried replacing the p2 resolver with the new OSGi resolver so I can't tell how it would perform. Specifically: - Is it possible to publish the bundle generic capabilities/requirements to the p2 repository? Yes this should be possible. The underlying p2 capability / requirement model is really extensible and the current limitation is only the serialized format. - Is it possible to use the equinox Resolver inside the p2 Planner? It is possible to get something going but I'm not sure if this will scale (p2 resolver is able to perform seamlessly on 10's of thousands of IUs), nor if you will be a
Re: [equinox-dev] Convergence between p2 and the OSGi resolver+repository
On 11/16/2016 10:49 AM, Todor Boev wrote: - Regarding resolver behavior: The goal is actually to replace the behavior of the objective function with the behavior of the resolver. This is the best way to guarantee that both p2 and the OSGi runtime agree on what is a consistent set of bundles. For example p2 does not take into account package uses constraints which leads to p2 selecting bundles that later fail to resolve at runtime. It does not matter which way to resolve is better, so long as they agree. Since the OSGi resolver is very unlikely to change it falls on p2 to match it's behavior. My current company (software ag) has had quite a number of issues where essentially p2 sets up the resolver to fail. - Regarding resolver scalability: The resolution is split between the resolver which processes the current set of resources and the resolver context which selects candidates when asked. If the goal is to support a very high number of candidates - a resolver context impl optimized for searches in a large candidate space can be provided. If the goal is to produce a solution that includes a very high number of resources - more research is required. Even if the initial set is 10,000 the resolver can be asked to process them not all at once, but incrementally in batches or even one by one. Which is in fact what equinox does today. The thing is that if you look at a subset of the available bundles, you may find a solution that is not the optimal one. p2 will consider all the possible candidates in one resolution invocation. I am trying to determine if it makes sense to invest effort in prototyping this given that subtle changes in behavior are in fact a goal, rather than an issue. Even though on the surface p2 resolver looks similar to what the OSGi resolver does, p2 has at least 2 additional concepts: 1) the expression of strict negation 2) the concept of patch I'm tempted to think that it is probably simpler to add support for the uses-clause in p2 (this has been a known issue for years, but I can't seem to find the bug tonight) than it is to replace the resolver completely and get all the tests to pass. The encoding of dependencies to a SAT formula is well documented and so are the optimization functions. On Wed, Nov 16, 2016 at 4:44 AM, Pascal Rapicault <pas...@rapicault.net <mailto:pas...@rapicault.net>> wrote: On 11/15/2016 12:52 PM, Todor Boev wrote: Hello, Are there any plans to bring together p2 and OSGi resolver+repository standards? There is no immediate plan for this. It should be beneficial to have similar (maybe identical?) dependency resolution at provisioning time and later at runtime. The install time and runtime resolvers resolve a slightly different problem because the install time resolver has to look for candidates in a large space, whereas the runtime one has to connect as many components together. I have not tried replacing the p2 resolver with the new OSGi resolver so I can't tell how it would perform. Specifically: - Is it possible to publish the bundle generic capabilities/requirements to the p2 repository? Yes this should be possible. The underlying p2 capability / requirement model is really extensible and the current limitation is only the serialized format. - Is it possible to use the equinox Resolver inside the p2 Planner? It is possible to get something going but I'm not sure if this will scale (p2 resolver is able to perform seamlessly on 10's of thousands of IUs), nor if you will be able to replicate the subtleties that result from having an objective function. - Even if the equinox Resolver can not be used is it possible for p2 to handle generic requirements/capabilities? Yes. This should not be too much work. Regards, Todor Boev ___ equinox-dev mailing list equinox-dev@eclipse.org <mailto:equinox-dev@eclipse.org> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev <https://dev.eclipse.org/mailman/listinfo/equinox-dev> ___ equinox-dev mailing list equinox-dev@eclipse.org <mailto:equinox-dev@eclipse.org> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev <https://dev.eclipse.org/mailman/listinfo/equinox-dev> ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Vote for Committer status for Mykola Nikishov
On 11/16/2016 10:05 AM, Daniel Megert wrote: > But if the platform is ok with that and you are happy to deal with the consequences. This is an RT PMC problem where the Platform has no say, unless we move Equinox back to the Eclipse top-level project. The problem is that p2 is not active enough anymore and patches from people like Mykola sit around for weeks if not months. So, unless p2 (Equinox now) committers don't commit to review incoming contributions in a timely manner then the RT PMC must come up with a plan to fix this. I've responded to that matter yesterday. This is the PMC's job as part of the EDP. At the Eclipse top-level project we are currently working on a plan to fix our projects where there's not enough activity. I'm not an Equinox committer, but from what I've seen from Mykola I would +1 his nomination. Dani ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Convergence between p2 and the OSGi resolver+repository
On 11/15/2016 12:52 PM, Todor Boev wrote: Hello, Are there any plans to bring together p2 and OSGi resolver+repository standards? There is no immediate plan for this. It should be beneficial to have similar (maybe identical?) dependency resolution at provisioning time and later at runtime. The install time and runtime resolvers resolve a slightly different problem because the install time resolver has to look for candidates in a large space, whereas the runtime one has to connect as many components together. I have not tried replacing the p2 resolver with the new OSGi resolver so I can't tell how it would perform. Specifically: - Is it possible to publish the bundle generic capabilities/requirements to the p2 repository? Yes this should be possible. The underlying p2 capability / requirement model is really extensible and the current limitation is only the serialized format. - Is it possible to use the equinox Resolver inside the p2 Planner? It is possible to get something going but I'm not sure if this will scale (p2 resolver is able to perform seamlessly on 10's of thousands of IUs), nor if you will be able to replicate the subtleties that result from having an objective function. - Even if the equinox Resolver can not be used is it possible for p2 to handle generic requirements/capabilities? Yes. This should not be too much work. Regards, Todor Boev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] -1 for Mykola Nikishov on rt.equinox by Pascal Rapicault
Stefan, I agree with you on that. I have not been great at helping him and recognizing the problem I've talked to my manager at Ericsson (my current contract) and earlier this week he has agreed to let me spend some time on p2 to help contribs go through. The other thing that did not help me here is that I never fully understand why so much changes were needed when only SHA256 was required. I think you got some of that context by talking to Mykola and maybe I will need to catch up with you for this. Pascal with On 11/15/2016 12:43 PM, Stefan Xenos wrote: Pascal, if you think he needs more time this is fine. However, you'll need to be more responsive regarding his code reviews. The work Mykola has been doing on checksums has been in the review queue for a very long time (some time around May, if I recall) and you are the best subject matter expert for most of the areas it touches. Please spend some time teaching him what he needs to learn, so we can get the benefit of him as a full committer soon. The sort of security and privacy concerns that Mykola seems so keen to work on would really benefit the project. - Stefan On Tue, Nov 15, 2016 at 8:37 AM portal on behalf of <portal-nore...@eclipse.org <mailto:portal-nore...@eclipse.org>> wrote: Pascal Rapicault voted: -1 Mykola has definitely shown tenacity and a strong desire to commit and this is great. However I\'m concerned that he is not quite ready because: - He needs to better grasp the implication of the changes he is proposing (backward and forward compatibility) and the impact they have on the overall ecosystem (Tycho, b3, PDE Build, the Platform) - Some of the changes are causing unnecessary churn in the code Before giving in the +1, I would like to wait until all the work he is proposing on SHA256 gets in. Voting summary: http://portal.eclipse.org/ ___ equinox-dev mailing list equinox-dev@eclipse.org <mailto:equinox-dev@eclipse.org> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Vote for Committer status for Mykola Nikishov was started by Thomas Watson
But if the platform is ok with that and you are happy to deal with the consequences. On 11/15/2016 9:38 AM, portal on behalf of wrote: rt.equinox Committers, This automatically generated message signals that Thomas Watson has nominated Mykola Nikishov as a Committer on the rt.equinox project. The reason given is as follows: Mykola has continued to show great interest in enhancing and fixing issues in p2. This is evident by the following list of bugs he has authored fixes for: Bug 493193 - MirrorApplication should explicitly use MD5 artifact comparator Bug 494822 - Pass a range specification unconditionally Bug 336246 - Remove the metadata generator Bug 490028 - Extract MD5 checksum calculation into a separate class Bug 471875 - [IconExe] Improve error message when launcher's icons has not been replaced As well as several other contributions reviewed through gerrit: https://git.eclipse.org/r/#/c/84519 https://git.eclipse.org/r/#/c/72223 https://git.eclipse.org/r/#/c/58861 https://git.eclipse.org/r/#/c/57915 https://git.eclipse.org/r/#/c/52386 Mikola also has a number of contributions awaiting review in gerrit. I think this is a good time to welcome Mikola as a committer for Equinox to enable Mikola to continue to make improvements to p2 and perhaps other components in Equinox. Note that Equinox subprojects have merged [1] so this is not only a nomination for committership to the p2 codebase, but the entire Equinox project which includes the framework and all the equinox bundles. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=488579 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=493193 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=494822 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=336246 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=490028 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=471875 The vote is being held via the MyFoundation portal: voters *must* use the portal for the votes to be properly recorded. The voting will continue until either all 37 existing Committers have voted or until they have been given enough time to vote, even if they do not do so (defined as at least one week). Mykola Nikishov must receive at least three +1s and no -1s for a successful election. Eligible Committers must cast their votes through their My Foundation portal page (do NOT just reply to this email; your vote will not be correctly recorded unless you use the portal): http://portal.eclipse.org/ The project Committers eligible to vote are: John Arthorne Raymond Auge Oleg Besedin Stoyan Boshev Ian Bull Krzysztof Daniel Pavlin Dobrev John Duimovich Bogdan Gheorghe Ted Habeck Thomas Hallgren BJ Hargrave Simon Kaegi Borislav Kapukaranov Markus Keller Lazar Kirchev Peter Kriens Daniel Le Berre Stefan Liebig Henrik Lindberg Martin Lippert Susan McCourt Shawn Minto Kim Moir Glyn Normington Tobias Oberlies Matthew Piggott Steffen Pingel Silenio Quarti Pascal Rapicault John Ross Arun Thondapu Teodor Todorov Thomas Watson Mike Wilson Stefan Xenos Meng Xin Zhu *NOTE*: Successful elections are left open for a maximum of 120 days to allow for processing of paperwork. After that time the election will be expired, regardless of its current status. Should papework processing on the part of the candidate take more time than allowed, a new election will have to be held. If you have any questions, please do not hesitate to contact your project lead, PMC member, or the EMO <e...@eclipse.org> ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Merge of equinox committer groups
Makes sense to me On 3/1/2016 8:49 AM, Thomas Watson wrote: Right now the equinox project has the following sub-projects, each with their own committer groups rt.equinox - parent project, no real code here, but it does contain the website rt.equinox.framework - where the OSGi framework and Equinox native launcher lives rt.equinox.bundles - where everything else is, besides p2 rt.equinox.p2 - where p2 is I plan to request the foundation fold rt.equinox.framework and rt.equinox.bundles into the parent project rt.equinox. I do not think there is a need to separate committers of the various equinox bundles from committers of the framework/launcher or the website. I do not plan to request p2 be folded into rt.equinox unless the existing p2 community of committers request that to happen. p2 is a fairly large codebase so it makes sense to keep it separate if the committers want that. But the rest of Equinox is not that large and maintaining 3 separate committer groups is not worth it in my opinion. Committers, please voice your concerns if you have them. Tom ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Concierge and the IDE?
This is not a goal of the equinox team, nor do I believe this is a goal of the concierge team. They both address very different use cases. We've optimized Equinox to be extremely fast on "warm" startups by implementing a number of caching strategies, which makes the implementation bigger. This is what makes Eclipse able to handle thousands of bundles On the other hand Concierge is optimized to be usable on small devices but I don't believe it is meant to support the same number of bundles. On 15-11-20 11:22 AM, Lars Vogel wrote: Hi, I read in a German newsticker that Concierge is a new OSGi 5.0 implementation which is super fast and small. https://projects.eclipse.org/projects/iot.concierge/downloads I didn't know about this effort. Is the intention to use this runtime for the Eclipse IDE in the future? Best regards, Lars ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Installing into Region
The usage of regions seems to be a good solution for what you are trying to achieve. However I'm still not clear about the problem you are running into. On 15-11-16 12:57 PM, Florian Pirchner wrote: I need to isolate the IDE e4 stuff from the Vaaclipse e4 stuff and only share some defined api like services and packages. Florian Pirchner> schrieb am Mo., 16. Nov. 2015 18:53: Hey Cristiano, yep. It should become some kind of "Vaaclipse Perspective WYSIWYG Editor". The Vaaclipse preview is embedded in the workspace as an MPart. IDE instance and "Vaaclipse Designer" run in same OSGi instance. A launch config in the IDE to launch the designer in an additional vaaclipse-e4-instance is not an option ;( Later I need to create an additional Region "E4 Model Exchange", that allows sharing information about the "Vaaclipse Designer" and the Xtext-Model. This region will allow to share some services. And provides implementations for event-exchange from and two IDE and Vaaclipse-Designer. Example: I am changing a setting in the Vaaclipse designer. This sends an event. And the IDE will change the Xtext-Model in the XtextResourceSet. Or I change the Xtext-Model and an event to the Vaaclipse-Designer will rerender and/or repaint the Web-UI. WDYT? Any ideas? Thanks Cristiano Gavião > schrieb am Mo., 16. Nov. 2015 18:29: Hello. some doubts... do you want a preview provider... but instead of use the "run as container way" that will open a new instance with a set of defined bundles, do you want to use the same container instance for both pde/jde/platform and your preview provider that will read/use the opening projects from the workspace projects? 2015-11-16 13:46 GMT-03:00 Florian Pirchner >: Hi, we got a problem using equinox regions. Our usecase: We run an Eclipse IDE based on eclipse e4. There is a project called vaaclipse that also uses the e4 kernel and added Vaadin renderer to it. And we need to show up a "Preview View" for the vaaclipse application in the IDE. The problem: Installing Vaaclipse into the IDE is not a good idea, since it will confuse the IDE by Extensions, OSGi-Services,... Our approach: 1) Starting up the IDE 2) Creating a new Region called "Vaaclipse" 2a) If a Region was available, we remove it first 2b) Reading all bundles from a specified target folder 2c) Installing the bundles from the target folder into the region 3) Setting startlevels,... and starting the application For us it seems to be possible, since the "rootRegion" and the "Vaaclipse" region are completely decoupled (the have no connection) But if we do so, stop the IDE and start the IDE again, all the bundles originally available in Eclipse have gone. Only the "system bundle" is left. The installed "target folder bundles" related with Region "Vaaclipse" are still there. Here a short idea about our first prototype approach: public void start(BundleContext bc) throws Exception { Activator.context = bc; try { ServiceReference ref = bc .getServiceReference(RegionDigraph.class); digraph = bc.getService(ref); vaaclipseRegion = digraph.getRegion("vaaclipse"); if (vaaclipseRegion != null) { digraph.removeRegion(vaaclipseRegion); } vaaclipseRegion = digraph.createRegion("vaaclipse"); File folder = new File("/Users/florianpirchner/Work/temp/tp"); for (File tpBundle : FileUtils.listFilesAndDirs(folder, FileFilterUtils.trueFileFilter(), FileFilterUtils.falseFileFilter())) { if(tpBundle.isDirectory()) { continue; } Bundle newB = vaaclipseRegion.installBundle("file:" + tpBundle .getAbsolutePath()); vaaclipseRegion.addBundle(newB); } } catch (BundleException e) { e.printStackTrace(); } } Thanks a lot for any help!
Re: [equinox-dev] Debugging equinox
Make sure you have the version of the source matching the binary (you can check that by making sure both have the same last segment in the version (e.g. v20150820-1432). If it is the case, then I encourage you to use the Eclipse IDE ;) On 15-11-12 05:18 AM, Chiranga Alwis wrote: Hi, I have been attempting to debug the Equinox SDK by attaching source jars delivered along with the SDK's plugins. But the breakpoints I have added to the extracted source code of org.eclipse.equinox.launcher.source_1.3.100.v20150511-1540.jar and org.eclipse.osgi.source_3.10.101.v20150820-1432.jar at positions which execute when the Equinox SDK is launched are not detected. The connection between IDEA Intellij and the port takes place successfully, but the execution listens to the port for few moments and then proceeds with further execution. Any ideas on the steps to follow for this purpose or any possible mistakes I make in the above mentioned procedure are highly appreciated. ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] OS X native launcher build
From having poked at those scripts recently, I agree :) Please be sure to open a bug in releng so David W. can be aware of this change and I will happily push the commits On 03/10/2015 09:51 AM, Mikael Barbero wrote: Hi, While currently trying to build natives on the Eclipse FoundationiInfra (see cbi-dev ML for information and https://hudson.eclipse.org/cbi/view/natives/ for builds), I hit an issue with Mac native launchers. Don't take the green status of https://hudson.eclipse.org/cbi/view/natives/job/cbi-launcher-macosx-x86_64/ for granted. It is actually failing. The issue is that features/org.eclipse.equinox.executable.feature/pom.xml starts features/org.eclipse.equinox.executable.feature/library/carbon/build.xml which itself starts features/org.eclipse.equinox.executable.feature/library/carbon/build.sh build.sh takes arguments about the platform to build but build.xml does not set any. pom.xml on the other hand defines the variable native as a string ws.os.arch. So I updated build.xml to take these string and split it to be able to run build.sh accordingly. See my patch here https://git.eclipse.org/r/#/c/43538/. With this patch, I am able to properly build native launcher my local OS X with the command mvn clean verify -P build-individual-bundles -Dnative=cocoa.macosx.x86_64 -f rt.equinox.framework/features/org.eclipse.equinox.executable.feature/pom.xml Another issue is with the mvn clean. It was not triggering the build.sh clean in the end, so I update the features/org.eclipse.equinox.executable.feature/pom.xml for that too (https://git.eclipse.org/r/#/c/43539/1). Do you agree with my analysis and solution? Thank you for your feedback. Mikael ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Syncronize a cluster of Equniox instances on several Tomcats with the ServletBridge?
Even though it is not based on Tomcat and the servlet bridge, I believe that pieces of the gyrex project (https://eclipse.org/gyrex/) could be useful for you. On 12/15/2014 04:23 AM, Pablo Beltran wrote: Hi, I have to synchronize several instances of Tomcat which I do not control. However, I'm able to deploy Equinox on them by using the ServletBridge in a WAR file. Then, I have to build a single cluster for all the Equinox instances deployed in such way in order to keep them synchronized (by using some remote events or something similar). I've read about Zookeeper, ECF and others. which might met my requirements though they are still a bit confusing for me in order to run them under the ServletBridge and what would it be the right choice? Thanks! Pablo ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] milestones in a maven repo
The barrier are ease of implementation, desire and time from the current committers. These could be overcome with contributions. On 22/08/2014 1:26 PM, Raymond Auge wrote: Hey All, I'd like to ask again what is the barrier to getting milestone builds into a maven repo? I mean https://repo.eclipse.org/content/repositories/eclipse/ exists. Why not extend it's use for publishing milestones? Wouldn't it quite literally be a single extra command invoked during the release process? -- *Raymond Augé* http://www.liferay.com/web/raymond.auge/profile (@rotty3000) Senior Software Architect *Liferay, Inc.* http://www.liferay.com (@Liferay) ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Fwd: Re: [rt-pmc] Eclipse project winrun4j depends upon Java project org.eclipse.equinox.launcher
You can find the source at http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of David Brown Sent: February-07-14 2:31 PM To: equinox-dev@eclipse.org Subject: [equinox-dev] Fwd: Re: [rt-pmc] Eclipse project winrun4j depends upon Java project org.eclipse.equinox.launcher Original Message Return-Path: rt-pmc-boun...@eclipse.orgmailto:rt-pmc-boun...@eclipse.org X-Original-To: da...@davidwbrown.namemailto:da...@davidwbrown.name Delivered-To: da...@davidwbrown.namemailto:da...@davidwbrown.name Received: from mail.eclipse.org (mail.eclipse.org [198.41.30.200]) by dobbeltganger.com (Postfix) with SMTP id 218A7BC2E7 for da...@davidwbrown.namemailto:da...@davidwbrown.name; Fri, 7 Feb 2014 18:46:34 + (UTC) Received: from [172.30.3.7] (localhost [127.0.0.1]) by mail.eclipse.org (Postfix) with ESMTP id 327C92DCCEF; Fri, 7 Feb 2014 13:46:33 -0500 (EST) X-Original-To: rt-...@eclipse.orgmailto:rt-...@eclipse.org Delivered-To: rt-...@eclipse.orgmailto:rt-...@eclipse.org Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) by mail.eclipse.org (Postfix) with ESMTP id 5A3C02DCC6F for rt-...@eclipse.orgmailto:rt-...@eclipse.org; Fri, 7 Feb 2014 13:46:10 -0500 (EST) Received: from /spool/local by e35.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for rt-...@eclipse.orgmailto:rt-...@eclipse.org from tjwat...@us.ibm.commailto:tjwat...@us.ibm.com; Fri, 7 Feb 2014 11:46:11 -0700 Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e35.co.us.ibm.com (192.168.1.135) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 7 Feb 2014 11:46:09 -0700 Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 5BD94C40002 for rt-...@eclipse.orgmailto:rt-...@eclipse.org; Fri, 7 Feb 2014 11:46:09 -0700 (MST) Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by b03cxnp08025.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s17Ik9VN3211684 for rt-...@eclipse.orgmailto:rt-...@eclipse.org; Fri, 7 Feb 2014 19:46:09 +0100 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s17Ijroj013893 for rt-...@eclipse.orgmailto:rt-...@eclipse.org; Fri, 7 Feb 2014 11:45:53 -0700 Received: from d03nm120.boulder.ibm.com (d03nm120.boulder.ibm.com [9.63.40.226]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s17Ijr9B012883 for rt-...@eclipse.orgmailto:rt-...@eclipse.org; Fri, 7 Feb 2014 11:45:53 -0700 In-Reply-To: 52f52848.8050...@davidwbrown.namemailto:52f52848.8050...@davidwbrown.name References: 52f52848.8050...@davidwbrown.namemailto:52f52848.8050...@davidwbrown.name X-KeepSent: D5351924:BAB7DF29-86257C78:0066F4CA; type=4; name=$KeepSent To: Runtime Project PMC mailing list rt-...@eclipse.orgmailto:rt-...@eclipse.org X-Mailer: Lotus Notes Release 8.5.3FP2 July 02, 2012 Message-ID: ofd5351924.bab7df29-on86257c78.0066f4ca-86257c78.00670...@us.ibm.commailto:ofd5351924.bab7df29-on86257c78.0066f4ca-86257c78.00670...@us.ibm.com From: Thomas Watson tjwat...@us.ibm.commailto:tjwat...@us.ibm.com Date: Fri, 7 Feb 2014 12:45:42 -0600 X-MIMETrack: Serialize by Router on D03NM120/03/M/IBM(Release 9.0.1IF1|November 26, 2013) at 02/07/2014 11:45:53 MIME-Version: 1.0 X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14020718-6688---063307D0 Subject: Re: [rt-pmc] Eclipse project winrun4j depends upon Java project org.eclipse.equinox.launcher X-BeenThere: rt-...@eclipse.orgmailto:rt-...@eclipse.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Runtime Project PMC mailing list rt-...@eclipse.orgmailto:rt-...@eclipse.org List-Id: Runtime Project PMC mailing list rt-pmc.eclipse.org List-Unsubscribe: https://dev.eclipse.org/mailman/options/rt-pmchttps://dev.eclipse.org/mailman/options/rt-pmc, mailto:rt-pmc-requ...@eclipse.org?subject=unsubscribemailto:rt-pmc-requ...@eclipse.org?subject=unsubscribe List-Archive: https://dev.eclipse.org/mailman/private/rt-pmchttps://dev.eclipse.org/mailman/private/rt-pmc List-Post: mailto:rt-...@eclipse.orgmailto:rt-...@eclipse.org List-Help: mailto:rt-pmc-requ...@eclipse.org?subject=helpmailto:rt-pmc-requ...@eclipse.org?subject=help List-Subscribe: https://dev.eclipse.org/mailman/listinfo/rt-pmchttps://dev.eclipse.org/mailman/listinfo/rt-pmc, mailto:rt-pmc-requ...@eclipse.org?subject=subscribemailto:rt-pmc-requ...@eclipse.org?subject=subscribe Content-Type: multipart/mixed; boundary2171390776023843189== Errors-To: rt-pmc-boun...@eclipse.orgmailto:rt-pmc-boun...@eclipse.org Sender:
Re: [equinox-dev] Fwd: Re: [rt-pmc] Eclipse project winrun4j depends upon Java project org.eclipse.equinox.launcher
I just cloned the repo and imported the launcher project successfully. When git has completed the clone and the wizard prompts you to import project, make sure to use the "import existing project". After a little while, I deselected everything and then reselected the org.eclipse.equinox.launcher entry. Now I have the code loaded in my workspace. HTH On 07/02/2014 3:45 PM, David Brown wrote: Hello, thanks for the speedy reply. Very accurate: the source is at the location in the URL but I was hoping to clone the project using the Eclipse git perspective and one of the 3 git URIs: git://git.eclipse.org/gitroot/equinox/rt.equinox.framework.git ssh://git.eclipse.org/gitroot/equinox/rt.equinox.framework.git http://git.eclipse.org/gitroot/equinox/rt.equinox.framework.git found here: http://git.eclipse.org/c/equinox/rt.equinox.framework.git Notwithstanding, the project is cloned as an Eclipse Java project after much on-screen busy-work activity as: org.eclipse.equinox.launcher but the /src directory is empty. No source. And, Eclipse problems tab errors list increases from 2 errors: Project 'org.boris.winrun4j.eclipsedde' is missing required java project: 'org.eclipse.equinox.lanucher' The Project cannot be built until build path errors are resolved. To a couple of dozen or so because the basic package: org.eclipse.equinox is missing. So the only solution is to grab the source straight from the web page directories? Please advise, David. On 02/07/2014 01:38 PM, Pascal Rapicault wrote: You can find the source at http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of David Brown Sent: February-07-14 2:31 PM To: equinox-dev@eclipse.org Subject: [equinox-dev] Fwd: Re: [rt-pmc] Eclipse project winrun4j depends upon Java project org.eclipse.equinox.launcher Original Message Return-Path: rt-pmc-boun...@eclipse.org X-Original-To: da...@davidwbrown.name Delivered-To: da...@davidwbrown.name Received: from mail.eclipse.org (mail.eclipse.org [198.41.30.200]) by dobbeltganger.com (Postfix) with SMTP id 218A7BC2E7 for da...@davidwbrown.name; Fri, 7 Feb 2014 18:46:34 + (UTC) Received: from [172.30.3.7] (localhost [127.0.0.1]) by mail.eclipse.org (Postfix) with ESMTP id 327C92DCCEF; Fri, 7 Feb 2014 13:46:33 -0500 (EST) X-Original-To: rt-...@eclipse.org Delivered-To: rt-...@eclipse.org Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) by mail.eclipse.org (Postfix) with ESMTP id 5A3C02DCC6F for rt-...@eclipse.org; Fri, 7 Feb 2014 13:46:10 -0500 (EST)
Re: [equinox-dev] Fwd: Re: [rt-pmc] Eclipse project winrun4j depends upon Java project org.eclipse.equinox.launcher
Preferences PDE API Baselines warning (in the bottom right corner) On 07/02/2014 4:25 PM, David Brown wrote: Hello Pascal, thanks for the speedy and remedial reply. Yes, the new project wizard instead of existing project is a killer. Now, I only have a single Eclipse problems tab error: An API baseline has not been set for the current workspace. I googled this but not a lot of relevance except this one bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=409811 The bug stated above has status: new but is directed at Mac and so seems not relevant. Missing packages I understand but the issue above is just too obscure without help. Thanks and any ideas welcomed. On 02/07/2014 02:58 PM, Pascal Rapicault wrote: I just cloned the repo and imported the launcher project successfully. When git has completed the clone and the wizard prompts you to import project, make sure to use the "import existing project". After a little while, I deselected everything and then reselected the org.eclipse.equinox.launcher entry. Now I have the code loaded in my workspace. HTH On 07/02/2014 3:45 PM, David Brown wrote: Hello, thanks for the speedy reply. Very accurate: the source is at the location in the URL but I was hoping to clone the project using the Eclipse git perspective and one of the 3 git URIs: git://git.eclipse.org/gitroot/equinox/rt.equinox.framework.git ssh://git.eclipse.org/gitroot/equinox/rt.equinox.framework.git http://git.eclipse.org/gitroot/equinox/rt.equinox.framework.git found here: http://git.eclipse.org/c/equinox/rt.equinox.framework.git Notwithstanding, the project is cloned as an Eclipse Java project after much on-screen busy-work activity as: org.eclipse.equinox.launcher but the /src directory is empty. No source. And, Eclipse problems tab errors list increases from 2 errors: Project 'org.boris.winrun4j.eclipsedde' is missing required java project: 'org.eclipse.equinox.lanucher' The Project cannot be built until build path errors are resolved. To a couple of dozen or so because the basic package: org.eclipse.equinox is missing. So the only solution is to grab the source straight from the web page directories? Please advise, David. On 02/07/2014 01:38 PM, Pascal Rapicault wrote: You can find the source at http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of David Brown Sent: February-07-14 2:31 PM To: equinox-dev@eclipse.org Subject: [equinox-dev] Fwd: Re: [rt-pmc] Eclipse project winrun4j depends upon Java project org.eclipse.equinox.launcher Original Message Return-Path: rt-pmc-boun...@eclipse.org X-Original-To: da...@davidwbrown.name Delivered-To: da...@davidwbrown.name Received: from mail.eclipse.org (mail.eclipse.org [198.41.30.200]) by dobbeltganger.com (Postfix) wi
Re: [equinox-dev] Can I avoid having all my OSDI containers copied?
This happens in a couple cases: - the bundle is installed without using the reference: URL - the bundle which is shipped as a jar contains inner jars in which case they will be extracted - the bundle contains resources (files, images, etc) and the code require a file URL to those HTH From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Patrick Valsecchi Sent: November-19-13 3:20 AM To: equinox-dev@eclipse.org Subject: [equinox-dev] Can I avoid having all my OSDI containers copied? Hi, I'm running on a platform that has very limited disk space and I was looking at disk usage of OpenDaylight. The biggest directories are the plugins and configuration/org.eclipse.osgi/bundlesdirectories. The plugins directory is where all my bundles are, so I'm OK with it. But theconfiguration/org.eclipse.osgi/bundles directory seems to contain mostly copies of my bundles. For example configuration/org.eclipse.osgi/bundles/117/1/bundlefile is an exact copy ofplugins/org.opendaylight.controller.clustering.services-implementation-0.4.0.jar. That is a big waste of disk space. I've tried to find a configuration option to disable that and found nothing. Is there something? I've looked at the Equinox source code as well and didn't find anything. Can somebody point me to the location in the code where this is done? I'd like to disable that or at least replace it by a hard link. Thanks ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Can I avoid having all my OSDI containers copied?
If you don't mind manually maintaining a list of bundles that you want to include in your application (at least to start with), then you may be interested in using org.eclipse.equinox.simpleconfigurator. This small bundles reads a file called configuration/org.eclipse.equinox.simpleconfigurator/bundles.info, and install all the bundles listed into the framework and supports reference. From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Patrick Valsecchi Sent: November-19-13 9:50 AM To: equinox-dev@eclipse.org Subject: Re: [equinox-dev] Can I avoid having all my OSDI containers copied? Hi all, In the config.ini file, all my bundle paths start with reference:. But only the core ones are loaded like that. Looking at how my other bundles are loaded, I found that this is done by org.apache.felix.fileinstall. I've looked at the documentation of this lib and found no way to make the automatically installed bundle treated as references. I've started to look at the fileinstall code, and it's quite convoluted... so I have trouble to find where to add the reference:. I'll continue my search tomorrow... The solution to remove my source bundles will be my last resort, I guess. Thanks everybody for your help. On 11/19/2013 03:14 PM, Thomas Watson wrote: As Pascal and others have mentioned, Equinox (and Felix) support reference installs which is just a form of a file: URL that has reference: prepended to it (e.g. reference:file:/path/to/bundle.jarfile:///\\path\to\bundle.jar). I imagine you already have your own custom launcher, or at least our own provisioning bundle that is doing the installs for your. Reference installs are the way to go if your provisioning bundle has a managed storage area where it is downloading and storing the bundle artifacts before actually installing them AND you are happy with the framework using the content from this managed storage area at runtime. This is how the Eclipse platform (with p2) manages the installed bundles in Eclipse (i.e. the bundles are stored in the plugins/ folder) without having duplicates on disk. But if you do not have that kind of provisioning storage area then you should consider Neil's suggestion. Note that if you do not want to use the simple BundleContext.installBundle(String location) method which requires the bundle location to be a proper URL (e.g. reference:file:/path/to/bundle.jarfile:///\\path\to\bundle.jar), but instead you want to control your location strings to be something else then you can use the installBundle(String location, InputStream content) like this: bc.instsallBundle(mylocation, new URL(reference:file:/path/to/bundle.jarfile:///\\path\to\bundle.jar).openstream()); Tom [Inactivehide details for Neil Bartlett ---11/19/2013 06:34:30 AM---OSGi persists the state of all installed bundles in the Fra]Neil Bartlett ---11/19/2013 06:34:30 AM---OSGi persists the state of all installed bundles in the Framework storage directory; by default in E From: Neil Bartlett njbartl...@gmail.commailto:njbartl...@gmail.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Patrick Valsecchi pvals...@cisco.commailto:pvals...@cisco.com, Date: 11/19/2013 06:34 AM Subject: Re: [equinox-dev] Can I avoid having all my OSDI containers copied? Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org OSGi persists the state of all installed bundles in the Framework storage directory; by default in Equinox this is 'configuration/org.osgi.eclipse'. Therefore, once the bundles are installed they are no longer needed in the external plugins directory. You might want to consider writing a custom OSGi launcher. On first use it could download the bundles from a URL or temporary filesystem. The BundleContext.installBundle() method can read bundles from any InputStream, so local files are not necessarily required. This will cache the bundles into the framework storage dir. Then on subsequent uses the framework will start up with all the same bundles in the same state. Alternatively you could pre-cache the bundles as part of the install process before shipping the device to users. This has the advantage that Equinox will persist the resolution state, which may improve start-up time. Regards Neil On 19 November 2013 at 08:21:03, Patrick Valsecchi (pvals...@cisco.commailto://pvals...@cisco.com/) wrote: Hi, I'm running on a platform that has very limited disk space and I was looking at disk usage of OpenDaylight. The biggest directories are the plugins and configuration/org.eclipse.osgi/bundlesdirectories. The plugins directory is where all my bundles are, so I'm OK with it. But theconfiguration/org.eclipse.osgi/bundles directory seems to contain mostly copies of my bundles. For example configuration/org.eclipse.osgi/bundles/117/1/bundlefile
Re: [equinox-dev] Getting an instance of a source bundle
What I meant is that you could copy the code in PDE :) From: andrew.eisenb...@gmail.com [mailto:andrew.eisenb...@gmail.com] On Behalf Of Andrew Eisenberg Sent: April-23-13 5:03 PM To: Pascal Rapicault Cc: Equinox development mailing list Subject: Re: [equinox-dev] Getting an instance of a source bundle Thanks, but unfortunately not so useful. I can't guarantee that users will have PDE installed. Since I know the full path to the bundle and I know the symbolic name of the source bundle, I can generate the path to the source bundle from the bundle. (I'd miss the case where the source bundle and the bundle are installed in different locations, but that seems rare enough that I won't worry about it). On Tue, Apr 23, 2013 at 11:40 AM, Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com wrote: The source jars are all available in a file called source.infohttp://source.info located in eclipse\configuration\org.eclipse.equinox.source p2 writes these files using SimpleConfigurationManipulatorImpl but I assume that PDE has some logic / helper code that does all the logic you are interested in since it needs to look at the p2 metadata to figure out the bundle to source relationship. HTH Pascal From: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org] On Behalf Of Andrew Eisenberg Sent: April-23-13 2:36 PM To: Equinox development mailing list Subject: [equinox-dev] Getting an instance of a source bundle I would like to get a handle on a source bundle, but they do not seem to be installed in the running Eclipse. For example, I would like to be able to do this: Bundle jdtUiSource = Platform.getBundle(org.eclipse.jdt.ui.source); However, this always returns null. Indeed, when I look use the OSGi console, I see something like this, even though the source bundle is available: osgi ss org.eclipse.jdt.ui Framework is launched. idState Bundle 243ACTIVE org.eclipse.jdt.ui_3.8.2.v20130107-165834 What I really need is a way to find the filesystem path to a source bundle (or null if not available). So, I don't need the bundle instance, but this just seems like a handy way to get the path. Does anyone have some ideas on what I can do? thanks, Andrew ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Use Maven to build osgi applications
AFAIK, the only Maven plugin that will generate the config.ini file is Tycho when using the eclipse-product packaging type. HTH On 2013-04-01, at 1:55 AM, Prasad Jeewantha wrote: Hi all, I am trying to build an osgi application with Maven. I am using maven-bundle-plugin and maven-scr-plugin to create the bundles. I have all the bundles created in 3 separate directories in the final distribution. What I want is to run all the osgi bundles in an OSGi container with a single command (may be using a shell script). I believe I have to create a config.ini file listing all the bundles which need to be run in the container. Is there a way to generate this file from Maven at compilation time? Or is there a better way to create the project without manually creating the configuration files? Any advice is greatly appreciated. Thanks in advance, PJ PS. I created a Stack overflow question on this topic. http://stackoverflow.com/q/15729182/1411653 ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Eclipse 4.3 M6 and Equinox Kepler M6 are available
Sorry to crash the party but none of the actual downloads of the Eclipse SDK are working. From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of David M Williams Sent: March-15-13 6:00 PM To: General development mailing list of the Eclipse project.; Equinox development mailing list Subject: [equinox-dev] Eclipse 4.3 M6 and Equinox Kepler M6 are available See what's new! http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M6-201303141330/news/ Get a download! http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M6-201303141330/ Or update from our repository! http://download.eclipse.org/eclipse/updates/4.3milestones/ As Tom previously announced on equinox-dev list, there is no download site for the Equinox specific deliverables this milestone, as there normally would be at http://download.eclipse.org/equinox/ simply because there has not been time or people to update that part of our publish scripts after moving to our new build technology. (But its high on the do next list.) In the mean time, all the artifacts should be available in the milestones repository referenced above. And remember, as previously announced, our milestone repository now contains only M6, instead of it and all previous milestones, as it normally would. Please let us know if that causes any unanticipated problems. Thanks to all that made this milestone possible. In addition to the hard working committers, thanks goes to the CBI Team who provided a prototype of our Tycho/Maven build and who continue to help us improve it to fit our needs and requirements and quirks -- this is our first milestone delivered using that technology. A good time to test early and test often! Thanks, ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] individual bundle downloads
I have not checked but I would assume that they are available from the p2 repo like juno (http://download.eclipse.org/releases/juno). You then have two ways to download it: - Peruse the remote filesystem (on one of the mirror since the foundation does not allow that) to find the file. - Use the p2 mirror to get it. From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Raymond Auge Sent: February-04-13 9:42 PM To: Equinox development mailing list Subject: [equinox-dev] individual bundle downloads I've googled around, looked at orbit, and the incubator pages and so on, but can't find individual downloads for bundles like: org.eclipse.equinox.console_1.0.0.v20120522-1841.jar as found in the equinox-SDK-*.zip Are these available individually anywhere? Sincerely, - Ray ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [p2] IPlanner and package imports from JRE
The reason is simple. The p2 planner is Java agnostic. It only knows about the capabilities and requirements that are provided to it. (Sidenote - this is what allows p2 to resolve any other kind of dependencies like RPM, deb, etc.). For the planner to know about the packages coming from the EE, you need to provide an IU that describe this EE. Normally you should be able to find such an IU in the Eclipse release repo under the name a.jre. Also if you use the mirroring application this IU should be brought in. HTH Pascal On 2013-02-01, at 6:08 AM, Tom Schindl wrote: Hi, Yesterday in the night I tried to understand why IPlanner reports an error when a bundle does a package import coming from the JRE which by default is then exported through the system bundle. The reason I tried to understand this is that I've started build a target platform which contains the complete set of plugins to develop (including even org.eclipse.osgi, ). You can see a description of it at http://www.eclipse.org/forums/index.php/t/452288/. Is there a possibility to teach the resolver that e.g. javax.net.ssl is coming from the JRE/system.bundle, I guess it would need to have EE informations for this, right? Tom -- B e s t S o l u t i o n . a tEDV Systemhaus GmbH tom schindl geschäftsführer/CEO eduard-bodem-gasse 5-7/1 A-6020 innsbruck fax ++43 512 935833 http://www.BestSolution.at phone++43 512 935834 ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Equinox/p2/Installer
Glad to hear that some ppl are using it :). If you are interested in improving it, or adding more functionality to it, feel free to provide patches and I'll incorporate them. Also we could try to re-enable the build, once the migration to the Eclipse CBI is complete. From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of scalpel4k Sent: January-31-13 2:56 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Equinox/p2/Installer I am using the installer from 2009 because the newer versions are not working. You can install an IU into a profile but that's all you can do. Updating or uninstalling doesn't work ... at least for me. At some point I realized maybe I was the only one using it now we're two ;-) bye Michi On Thursday 31 Jan 2013 13:20:01 Vladimir Sosnin wrote: Thank you! I'll try to evaluate this functionality. On Thu, Jan 31, 2013 at 2:01 AM, Ian Bull irb...@eclipsesource.commailto:irb...@eclipsesource.com wrote: We stopped building the install (mostly because there were some code related issues, and there was very little interest in the tool). However, you can use the old builds (Eclipse Helios I think). The repository formats have not changed, so the tool should be fine. Also, as Pascal said, you can get the source and build it yourself for your own needs. cheers, ian On Wed, Jan 30, 2013 at 1:23 PM, Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com wrote: The installer code can be found at http://git.eclipse.org/c/equinox/rt.equinox.p2.git/tree/bundles/org.eclipse.equinox.p2.installer From: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org] On Behalf Of Vladimir Sosnin Sent: January-30-13 2:07 PM To: equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org Subject: [equinox-dev] Equinox/p2/Installer Hello, Where I can find Equinox p2 Installer described at http://wiki.eclipse.org/Equinox/p2/Installer? Can be achieved same functionality using last (Juno) Equinox builds? Regards, Vladimir ___ equinox-dev mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource ___ equinox-dev mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev -- Regards, Vladimir ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Equinox/p2/Installer
The installer code can be found at http://git.eclipse.org/c/equinox/rt.equinox.p2.git/tree/bundles/org.eclipse.equinox.p2.installer From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Vladimir Sosnin Sent: January-30-13 2:07 PM To: equinox-dev@eclipse.org Subject: [equinox-dev] Equinox/p2/Installer Hello, Where I can find Equinox p2 Installer described at http://wiki.eclipse.org/Equinox/p2/Installer? Can be achieved same functionality using last (Juno) Equinox builds? Regards, Vladimir ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Does the fwk load the config.ini
Aren’t we reading it for the case where the fwk is started w/o using the launcher? From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-25-13 9:03 AM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini Sounds reasonable to do that check. I always thought it was a bit silly to re-read the config.ini in the EclipseStarter if the launcher already did it! Tom [Inactive hide details for Pascal Rapicault ---01/24/2013 08:19:04 PM---I’ve decided to stop reading the user configuration whe]Pascal Rapicault ---01/24/2013 08:19:04 PM---I’ve decided to stop reading the user configuration when the base has changed to minimize the risk o From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/24/2013 08:19 PM Subject: Re: [equinox-dev] Does the fwk load the config.ini Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org I’ve decided to stop reading the user configuration when the base has changed to minimize the risk of having erroneous information in the config.ini (bundles that are no longer available, config entries no longer relevant) that could harm the startup process. A similar logic has been implemented in the simpleconfigurator and will be merged in master by Sunday night. The code is currently available in a branch called prapicau/sharedInstall-part1. The code that needs to be added to EclipseStarter is as simple as an if statement accessing a system property set by the launcher. From: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-24-13 5:13 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini Out of curiosity, why do you need to prevent the reading of the user's configuration if the base has changed? I guess you released some changes to the launcher to do this same kind of logic. You just now need to apply that logic in EclipseStarter so it does not clobber the changes you did to the launcher? Tom [Inactive hide details for Pascal Rapicault ---01/24/2013 03:54:51 PM---Your recollection is correct. Today the launcher reads t]Pascal Rapicault ---01/24/2013 03:54:51 PM---Your recollection is correct. Today the launcher reads the user configuration and then merges the ba From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/24/2013 03:54 PM Subject: Re: [equinox-dev] Does the fwk load the config.ini Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org Your recollection is correct. Today the launcher reads the user configuration and then merges the based configuration, whereas the EclipseStarter only reads the user configuration. The reason I’m looking into this is because I need to change the EclipseStarter logic to bypass the reading of the config.ini when the base has changed (which I can do easily since the heavy lifting is done in the launcher) but I wanted to be sure that not loading any properties in the FrameworkProperties would not be an issue. From: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-24-13 4:42 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini Now that you mention that I am not sure what is expected to happen with the shared configuration and the config.ini files. I guess it should read the users configuration and then merge in the parent configuration, or is it the other way around? If I recall correctly the launcher does do cascade reading of the shared configurations, but I am unsure if the user's configuration overrides the parents or not. At any rate, for shared configurations I think we depend on the launcher to do the merging of the cascaded configurations. Tom [Inactive hide details for Pascal Rapicault ---01/24/2013 03:35:04 PM---Thanks for the pointer Tom. I've looked at the code and]Pascal Rapicault ---01/24/2013 03:35:04 PM---Thanks for the pointer Tom. I've looked at the code and I'm a bit surprise to see that this code is From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/24/2013 03:35 PM Subject: Re: [equinox-dev] Does the fwk load the config.ini Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org Thanks
Re: [equinox-dev] Does the fwk load the config.ini
At this point the logic to bypass the loading of the config.ini in the fwk would only apply when we are in shared install. I will push that later today. We can look into doing a systematic bypass later. Thanks for reverting the change to the launcher. From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-25-13 10:36 AM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini Yes, and we should continue to do so. If I understand you correctly, you are suggesting we avoid re-reading the config.ini in the case where the launcher already did it. I think that is a good thing and I always thought it was a bit of waste that we re-read a file that the launcher already loaded for us. As a side note, lets hold of on incrementing version numbers of the launchers until we get past M5 since we need to update all the host version ranges of the launcher fragments when we do that (https://bugs.eclipse.org/bugs/show_bug.cgi?id=399037) Tom [Inactive hide details for Pascal Rapicault ---01/25/2013 09:15:16 AM---Aren’t we reading it for the case where the fwk is star]Pascal Rapicault ---01/25/2013 09:15:16 AM---Aren’t we reading it for the case where the fwk is started w/o using the launcher? From: equinox-dev From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/25/2013 09:15 AM Subject: Re: [equinox-dev] Does the fwk load the config.ini Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org Aren’t we reading it for the case where the fwk is started w/o using the launcher? From: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-25-13 9:03 AM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini Sounds reasonable to do that check. I always thought it was a bit silly to re-read the config.ini in the EclipseStarter if the launcher already did it! Tom [Inactive hide details for Pascal Rapicault ---01/24/2013 08:19:04 PM---I’ve decided to stop reading the user configuration whe]Pascal Rapicault ---01/24/2013 08:19:04 PM---I’ve decided to stop reading the user configuration when the base has changed to minimize the risk o From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/24/2013 08:19 PM Subject: Re: [equinox-dev] Does the fwk load the config.ini Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org I’ve decided to stop reading the user configuration when the base has changed to minimize the risk of having erroneous information in the config.ini (bundles that are no longer available, config entries no longer relevant) that could harm the startup process. A similar logic has been implemented in the simpleconfigurator and will be merged in master by Sunday night. The code is currently available in a branch called prapicau/sharedInstall-part1. The code that needs to be added to EclipseStarter is as simple as an if statement accessing a system property set by the launcher. From: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-24-13 5:13 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini Out of curiosity, why do you need to prevent the reading of the user's configuration if the base has changed? I guess you released some changes to the launcher to do this same kind of logic. You just now need to apply that logic in EclipseStarter so it does not clobber the changes you did to the launcher? Tom [Inactive hide details for Pascal Rapicault ---01/24/2013 03:54:51 PM---Your recollection is correct. Today the launcher reads t]Pascal Rapicault ---01/24/2013 03:54:51 PM---Your recollection is correct. Today the launcher reads the user configuration and then merges the ba From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/24/2013 03:54 PM Subject: Re: [equinox-dev] Does the fwk load the config.ini Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org Your recollection is correct. Today the launcher reads the user configuration and then merges the based configuration, whereas the EclipseStarter only reads the user configuration. The reason I’m looking into this is because I need
[equinox-dev] Does the fwk load the config.ini
When running eclipse, does the framework also load the config.ini or does always leave that to the launcher? thx Pascal ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Changes to the launcher
As part of the work to improve the support for shared installs (https://bugs.eclipse.org/bugs/show_bug.cgi?id=304132) I have merged back in master the launcher code that detects whether the config.ini in the base has changed. The p2 work that goes along with it will also be merged in master in the following days (ideally before no later than Sunday). Pascal ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Does the fwk load the config.ini
Thanks for the pointer Tom. I've looked at the code and I'm a bit surprise to see that this code is not handling shared configuration. Is that expected or am I missing something obvious? Thx Pascal From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-24-13 3:18 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini If the framework is launched with EclipseStarter (which the launcher uses) then yes it does [1]. Tom [1] see org.eclipse.core.runtime.adaptor.EclipseStarter.loadConfigurationInfo() [Inactive hide details for Pascal Rapicault ---01/24/2013 12:25:23 PM---When running eclipse, does the framework also load the c]Pascal Rapicault ---01/24/2013 12:25:23 PM---When running eclipse, does the framework also load the config.ini or does always leave that to the l From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/24/2013 12:25 PM Subject: [equinox-dev] Does the fwk load the config.ini Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org When running eclipse, does the framework also load the config.ini or does always leave that to the launcher? thx Pascal ___ equinox-dev mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: image001.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Does the fwk load the config.ini
Your recollection is correct. Today the launcher reads the user configuration and then merges the based configuration, whereas the EclipseStarter only reads the user configuration. The reason I’m looking into this is because I need to change the EclipseStarter logic to bypass the reading of the config.ini when the base has changed (which I can do easily since the heavy lifting is done in the launcher) but I wanted to be sure that not loading any properties in the FrameworkProperties would not be an issue. From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-24-13 4:42 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini Now that you mention that I am not sure what is expected to happen with the shared configuration and the config.ini files. I guess it should read the users configuration and then merge in the parent configuration, or is it the other way around? If I recall correctly the launcher does do cascade reading of the shared configurations, but I am unsure if the user's configuration overrides the parents or not. At any rate, for shared configurations I think we depend on the launcher to do the merging of the cascaded configurations. Tom [Inactive hide details for Pascal Rapicault ---01/24/2013 03:35:04 PM---Thanks for the pointer Tom. I've looked at the code and]Pascal Rapicault ---01/24/2013 03:35:04 PM---Thanks for the pointer Tom. I've looked at the code and I'm a bit surprise to see that this code is From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/24/2013 03:35 PM Subject: Re: [equinox-dev] Does the fwk load the config.ini Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org Thanks for the pointer Tom. I’ve looked at the code and I’m a bit surprise to see that this code is not handling shared configuration. Is that expected or am I missing something obvious? Thx Pascal From: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-24-13 3:18 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini If the framework is launched with EclipseStarter (which the launcher uses) then yes it does [1]. Tom [1] see org.eclipse.core.runtime.adaptor.EclipseStarter.loadConfigurationInfo() [Inactive hide details for Pascal Rapicault ---01/24/2013 12:25:23 PM---When running eclipse, does the framework also load the c]Pascal Rapicault ---01/24/2013 12:25:23 PM---When running eclipse, does the framework also load the config.ini or does always leave that to the l From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/24/2013 12:25 PM Subject: [equinox-dev] Does the fwk load the config.ini Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org When running eclipse, does the framework also load the config.ini or does always leave that to the launcher? thx Pascal ___ equinox-dev mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev___ equinox-dev mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: image001.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Does the fwk load the config.ini
I’ve decided to stop reading the user configuration when the base has changed to minimize the risk of having erroneous information in the config.ini (bundles that are no longer available, config entries no longer relevant) that could harm the startup process. A similar logic has been implemented in the simpleconfigurator and will be merged in master by Sunday night. The code is currently available in a branch called prapicau/sharedInstall-part1. The code that needs to be added to EclipseStarter is as simple as an if statement accessing a system property set by the launcher. From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-24-13 5:13 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini Out of curiosity, why do you need to prevent the reading of the user's configuration if the base has changed? I guess you released some changes to the launcher to do this same kind of logic. You just now need to apply that logic in EclipseStarter so it does not clobber the changes you did to the launcher? Tom [Inactive hide details for Pascal Rapicault ---01/24/2013 03:54:51 PM---Your recollection is correct. Today the launcher reads t]Pascal Rapicault ---01/24/2013 03:54:51 PM---Your recollection is correct. Today the launcher reads the user configuration and then merges the ba From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/24/2013 03:54 PM Subject: Re: [equinox-dev] Does the fwk load the config.ini Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org Your recollection is correct. Today the launcher reads the user configuration and then merges the based configuration, whereas the EclipseStarter only reads the user configuration. The reason I’m looking into this is because I need to change the EclipseStarter logic to bypass the reading of the config.ini when the base has changed (which I can do easily since the heavy lifting is done in the launcher) but I wanted to be sure that not loading any properties in the FrameworkProperties would not be an issue. From: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-24-13 4:42 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini Now that you mention that I am not sure what is expected to happen with the shared configuration and the config.ini files. I guess it should read the users configuration and then merge in the parent configuration, or is it the other way around? If I recall correctly the launcher does do cascade reading of the shared configurations, but I am unsure if the user's configuration overrides the parents or not. At any rate, for shared configurations I think we depend on the launcher to do the merging of the cascaded configurations. Tom [Inactive hide details for Pascal Rapicault ---01/24/2013 03:35:04 PM---Thanks for the pointer Tom. I've looked at the code and]Pascal Rapicault ---01/24/2013 03:35:04 PM---Thanks for the pointer Tom. I've looked at the code and I'm a bit surprise to see that this code is From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/24/2013 03:35 PM Subject: Re: [equinox-dev] Does the fwk load the config.ini Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org Thanks for the pointer Tom. I’ve looked at the code and I’m a bit surprise to see that this code is not handling shared configuration. Is that expected or am I missing something obvious? Thx Pascal From: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: January-24-13 3:18 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Does the fwk load the config.ini If the framework is launched with EclipseStarter (which the launcher uses) then yes it does [1]. Tom [1] see org.eclipse.core.runtime.adaptor.EclipseStarter.loadConfigurationInfo() [Inactive hide details for Pascal Rapicault ---01/24/2013 12:25:23 PM---When running eclipse, does the framework also load the c]Pascal Rapicault ---01/24/2013 12:25:23 PM---When running eclipse, does the framework also load the config.ini or does always leave that to the l From: Pascal Rapicault pascal.rapica...@ericsson.commailto:pascal.rapica...@ericsson.com To: equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 01/24/2013 12:25 PM Subject: [equinox-dev
Re: [equinox-dev] provider of equinox.http package
Thx John From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of John W Ross Sent: January-15-13 3:49 PM To: Equinox development mailing list Subject: Re: [equinox-dev] provider of equinox.http package My understanding is in 3.7.x and earlier, the org.eclipse.equinox.http bundle provided that package as x-internal only. The bundle is obsolete and not shipped in 3.8.x or later. The last version is here: http://download.eclipse.org/equinox/drops/R-3.7.2-201202080800/download.php?dropFile=org.eclipse.equinox.http_1.0.500.v20110413.jar. John [equinox-dev] provider of equinox.http package Which bundle provides the org.eclipse.equinox.http package? Pascal___ equinox-dev mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] provider of equinox.http package
Which bundle provides the org.eclipse.equinox.http package? Pascal ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] TrustEngine and other security services
The p2 engine makes use of the TrustEngine, however I don't remember the details of how it works. You may also want to poke around at other parts of p2 as I just happen to remember about this ref in the engine, but there may be others. HTH Pascal On 2012-12-29, at 5:47 AM, Scott Lewis wrote: Hello, Is there documentation on Equinox security services like org.eclipse.osgi.service.security.TrustEngine service...and implementation? I looked in the Equinox Security area [1], but didn't find a lot of service/API docs. Is/are there examples of using the TrustEngine service(s)? Thanks, Scott ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Console behavior change?
Does that ring any bell to anyone involved in the console work? -Original Message- From: p2-dev-boun...@eclipse.org [mailto:p2-dev-boun...@eclipse.org] On Behalf Of Mikhail Kalkov Sent: December-12-12 6:37 AM To: p2-...@eclipse.org Subject: [p2-dev] Question about p2 console activation policy Hi, I've downloaded and unzipped Eclipse Classic (eclipse-SDK-4.2-win32-x86_64.zip), started it, opened the Console View, and opened Host OSGi Console. Now, if I try to run one of p2 commands, I get the following error: osgi provlpquery gogo: CommandNotFoundException: Command not found: provlpquery If I list the status of p2 bundles, they are as follows: osgi ss p2 Framework is launched. id State Bundle 99 ACTIVE org.eclipse.equinox.p2.artifact.repository_1.1.200.v20120430-1959 100 STARTINGorg.eclipse.equinox.p2.console_1.0.300.v20120429-0125 101 ACTIVE org.eclipse.equinox.p2.core_2.2.0.v20120430-0525 102 ACTIVE org.eclipse.equinox.p2.director_2.2.0.v20120524-0542 103 STARTINGorg.eclipse.equinox.p2.director.app_1.0.300.v20120428-0517 104 ACTIVE org.eclipse.equinox.p2.directorywatcher_1.0.300.v20110808-1657 105 ACTIVE org.eclipse.equinox.p2.engine_2.2.0.v20120501-1502 106 ACTIVE org.eclipse.equinox.p2.extensionlocation_1.2.100.v20110808-1657 107 ACTIVE org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110808-1657 108 RESOLVEDorg.eclipse.equinox.p2.jarprocessor_1.0.200.v20110808-1657 109 ACTIVE org.eclipse.equinox.p2.metadata_2.1.0.v20120430-2001 110 ACTIVE org.eclipse.equinox.p2.metadata.repository_1.2.100.v20120524-1717 111 ACTIVE org.eclipse.equinox.p2.operations_2.2.0.v20120524-0542 112 ACTIVE org.eclipse.equinox.p2.publisher_1.2.0.v20120428-0117 113 STARTING org.eclipse.equinox.p2.publisher.eclipse_1.1.0.v20120511-1931 114 STARTINGorg.eclipse.equinox.p2.ql_2.0.100.v20110808-1657 115 ACTIVE org.eclipse.equinox.p2.reconciler.dropins_1.1.200.v20120301-2145 116 ACTIVE org.eclipse.equinox.p2.repository_2.2.0.v20120524-1945 117 STARTING org.eclipse.equinox.p2.repository.tools_2.0.100.v20120501-1314 118 ACTIVE org.eclipse.equinox.p2.touchpoint.eclipse_2.1.100.v20120428-0117 119 STARTING org.eclipse.equinox.p2.touchpoint.natives_1.1.0.v20120524-0542 120 ACTIVE org.eclipse.equinox.p2.transport.ecf_1.0.100.v20120305-0333 121 STARTINGorg.eclipse.equinox.p2.ui_2.2.0.v20120524-0542 122 STARTINGorg.eclipse.equinox.p2.ui.importexport_1.0.1.v20110818-1344 123 STARTINGorg.eclipse.equinox.p2.ui.sdk_1.0.200.v20120515-1650 124 ACTIVE org.eclipse.equinox.p2.ui.sdk.scheduler_1.1.0.v20110815-1744 125 ACTIVE org.eclipse.equinox.p2.updatechecker_1.1.200.v20110808-1657 126 ACTIVE org.eclipse.equinox.p2.updatesite_1.0.400.v20120412-1615 The org.eclipse.equinox.p2.console bundle is stuck in STARTING state no matter how long one waits, and this seem to be correct behaviour according to http://www.osgi.org/javadoc/r4v43/core/org/osgi/framework/Bundle.html#STARTING, because the bundle MANIFEST.MF contains Bundle-ActivationPolicy: lazy, and will not be started until one of its classes is accessed. However, if it is not started, it does not have a chance to contribute its commands to OSGi shell. Once I start the bundle, everything works fine. osgi start 100 osgi provlpquery Please enter a query osgi ss org.eclipse.equinox.p2.console Framework is launched. id State Bundle 100 ACTIVE org.eclipse.equinox.p2.console_1.0.300.v20120429-0125 There must have been a change in equinox behaviour recently because other projects seem to struggle with the same issue: http://jira.codehaus.org/browse/GROOVY-5664 Do you know why this problem has arised and if somebody should fix it by removing the Bundle-ActivationPolicy: lazy line from p2.console's manifest? Kind regards, Mikhail Kalkov Purple Scout AB Software Developer Address: Kyrkogatan 20-22, SE-41110 Gothenburg, Sweden Phone: +46 (0) 732 - 051405 E-mail: mikhail.kal...@purplescout.se Web: www.purplescout.se ___ p2-dev mailing list p2-...@eclipse.org https://dev.eclipse.org/mailman/listinfo/p2-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Equinox Subprojects
Just to be clear, I'm not pushing for this to happen. That was just a thought triggered from Wayne's comment. From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: December-07-12 2:17 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Equinox Subprojects Whatever is currently in the rt.equinox.p2 repo stays with the p2 project IMO ;-) Personally I don't see the advantage of making p2 a separate project under RT, but if the p2 leads want to do it it is fine by me. I don't think it will give you any more freedom than you have today. Tom [Inactive hide details for Ian Bull ---12/07/2012 12:02:08 PM---I certainly wouldn't be opposed to making p2 its own project, bu]Ian Bull ---12/07/2012 12:02:08 PM---I certainly wouldn't be opposed to making p2 its own project, but how much extra overhead in involve From: Ian Bull irb...@eclipsesource.commailto:irb...@eclipsesource.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 12/07/2012 12:02 PM Subject: Re: [equinox-dev] Equinox Subprojects Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org I certainly wouldn't be opposed to making p2 its own project, but how much extra overhead in involved (managerial -- release, docware, etc... and technical -- builds, platform contribution, etc..)? Also, there are a few components (simple configurator for example), which are kinda p2 and kinda platform and sorta equinox. I guess Pascal and Tom would have a good idea of where to place these things (they're in p2 right now). cheers, ian On Fri, Dec 7, 2012 at 12:07 AM, Gunnar Wagenknecht gun...@wagenknecht.orgmailto:gun...@wagenknecht.org wrote: Am 06.12.2012 23:46, schrieb Pascal Rapicault: Another solution is to make p2 a project in of itself. That's what I was thinking. -Gunnar -- Gunnar Wagenknecht gun...@wagenknecht.orgmailto:gun...@wagenknecht.org http://wagenknecht.org/ ___ equinox-dev mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.comhttp://eclipsesource.com/ | http://twitter.com/eclipsesource___ equinox-dev mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: image001.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Equinox Subprojects
Another solution is to make p2 a project in of itself. From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Wayne Beaton Sent: December-06-12 1:02 PM To: equinox-dev@eclipse.org Subject: Re: [equinox-dev] Equinox Subprojects Is there real need to protect different functional areas within the project? Is there danger that a website committer might start hacking p2 code? I'm having trouble understanding why subprojects are required at all. Equinox builds and releases as a single thing. There is a single website. All of the subproject repositories are in a single location. The only reason that I can think of to have subprojects is so that you can have ACLs against different functional areas within the same project. While this may align with the wording of the EDP, I think that it violates the spirit of it. Is there any reason why we can't just collapse *all* of the Equinox subprojects into the parent and be be left with rt.equinox? The CDT project, for example, does this. They have one set of committers. Within the project they manage who accesses what by social convention rather than enforced access control. Is there valid concern that we need to keep p2 committers from touching framework stuff? Collapsing would solve the website problem, wouldn't it? Wayne On 12/06/2012 10:00 AM, John Arthorne wrote: +1 on terminating rt.equinox.security. Effectively we did this during the Git migration and forgot to do the full process. I don't care either way about combining bundles+framework. They do have fairly distinct committer lists and they seem to be functioning fine in their current form. On the other hand I would trust all the committers to only work in their area of expertise so I have nothing against combining them. I tend to agree with Wayne that effectively they operate as a single project. On the website, the other big issue is that the Equinox download directory is owned by the website project. So between the downloads and web sites I do think all the Equinox committers need to have commit rights. Whether that is done via a separate project or ACL magic from the webmasters like Platform does, I don't mind either way. When dealing with several different directories I tend to think the ACL approach would be a pain to manage. Looking at the members of the website ACL, it does look in need of some cleanup at least - even McQ is a committer there :) John From: Thomas Watson tjwat...@us.ibm.commailto:tjwat...@us.ibm.com To: Equinox development mailing list equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 12/06/2012 08:38 AM Subject: Re: [equinox-dev] Equinox Subprojects Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org rt.equinox.security should have been roled up into rt.equinox.bundles. At least we moved all the security code into the rt.equinox.bundles repository and have one commit group for that repository. So technically it is a candidate for termination, but the code did not go away. Personally I would be fine with combining rt.equinox.bundles and rt.equinox.framework into one project under rt.equinox and leaving rt.equinox.p2 as the sole subproject. This means all rt.equinox.bundles committers would gain commit rights to the rt.equinox.framework repo and vise-versa. I'm not sure what to do about rt.equinox.website project. If you have an easy way to also combine it into rt.equinox then that is fine. But we must allow rt.equinox.p2 committers to still have access to the web site repository. Others have opinions? Tom [Inactive hide details for Wayne Beaton ---12/05/2012 04:29:34 PM---I just noticed that some of the Equinox subprojects do not h]Wayne Beaton ---12/05/2012 04:29:34 PM---I just noticed that some of the Equinox subprojects do not have any source repositories listed [1]. From: Wayne Beaton wa...@eclipse.orgmailto:wa...@eclipse.org To: equinox-dev@eclipse.orgmailto:equinox-dev@eclipse.org, Date: 12/05/2012 04:29 PM Subject: [equinox-dev] Equinox Subprojects Sent by: equinox-dev-boun...@eclipse.orgmailto:equinox-dev-boun...@eclipse.org I just noticed that some of the Equinox subprojects do not have any source repositories listed [1]. In fact, most of them have no metadata specified at all. Further, upon inspection, it appears that the rt.equinox.security project has no resources associated with it (no Git repository, no downloads that I can detect, no website). Is this project still viable, or is it a candidate for termination? The rt.equinox.website project is a hold over from the bad-old-days. Is that project still required? Can we kill it and assign the website repository to rt.equinox? Is it still valuable to have Equinox subprojects at all? Based on the use of the projects, it seems that the only purpose is to keep the committer lists distinct. Is this still necessary?
Re: [equinox-dev] Which C file for launcher on mac
Thanks, I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=394520 to now add support to the launcher to support Sun VMs on Mac. On 2012-11-16, at 11:43 AM, Andrew Niefer wrote: The files under library/carbon are used for cocoa, there are ifdefs separating the pieces that are different between carbon cocoa. The dll will contain eclipseCarbon.c and eclipseCarbonCommon.c. If you look near the top of the make_cocoa.mak file, you can see the full list of files for both the executable and the library. The executable contains everything from MAIN_OBJS COMMON_OBJS, the library contains COMMON_OBJS DLL_OBJS. -Andrew graycol.gifPascal Rapicault ---11/16/2012 11:09:06 AM---When the executable for mac / cocoa, is it the eclipseCarbon.c file that finds it way into the dll? From: Pascal Rapicault pas...@rapicault.net To: Equinox development mailing list equinox-dev@eclipse.org, Date: 11/16/2012 11:09 AM Subject: [equinox-dev] Which C file for launcher on mac Sent by: equinox-dev-boun...@eclipse.org When the executable for mac / cocoa, is it the eclipseCarbon.c file that finds it way into the dll? Pascal ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Which C file for launcher on mac
When the executable for mac / cocoa, is it the eclipseCarbon.c file that finds it way into the dll? Pascal ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] New framework?
Yes, adaptor hooks will be reworked. On 2012-09-02, at 1:31 PM, Stephan Herrmann wrote: Hi Tom, On 08/30/2012 02:55 PM, Thomas Watson wrote: In short, yes I have been working on re-implementing the core framework ... Will this affect any clients that use API not specified by OSGi? Specifically, what about the adapter hooks? Will anything change here? thanks, Stephan ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] About the fwk rewrite
I have a couple questions about the framework rewrite: - Is there a document describing the goals of the rewrite - Is there any plan to change how things work on disk? (e.g. config.ini) - Since we are sharing the resolver with Felix, have we considered simply reusing felix in its entirety? Pascal ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] About the fwk rewrite
On 2012-09-04, at 10:23 AM, Thomas Watson wrote: I will be working on documenting the goals and design of the generic model over the coming weeks. No, I did not rework the way EclipseStarter reads config.ini. EclipseStarter is just a launcher (that ends up using org.osgi.framework.launch API). It still reads the config.ini for framework configuration and it still continues to install the initial bundles from the osgi.bundles property. I tried to keep this flow so that the new framework implementation could be boot strapped without tons of changes to the rest of Eclipse. For example, you should be able to launch a self-hosted eclipse with the new implementation from a Juno installation. I was asking because I thought this could be a nice way to change the way files are laid out on disk to make them easier to manage (e.g. have multiple config files that are read and merged at runtime rather than one file). However this would most likely require changes to p2 and PDE which is probably way broader than the scope of the work desired here. But I did greatly simplify how the framework stores its persistent information on disk. That is really the only part the core framework controls as far as layout on disk is concerned. All other aspects are handled by things outside of the core framework (e.g. the plugins folder the configuration/ folder etc.). For the Felix comment. Have I thought of just using the Felix Framework as is? Sure, but I think competition is good and I think it is in the best interest of Eclipse to continue to have ownership of one of the core technologies it is running on. Also, I want to point out that the OSGi Resolver specification is a very small part of a proper OSGi Framework implementation. It is a large leap to go from using one small part of the felix project to moving completely over to the Felix OSGi Framework implementation. Also, I should point out that the Felix Framework is not currently using the OSGi Enterprise Specified Resolver service implementation. It should not be a large amount of work for them to do that but, as of right now, the OSGi Resolver service implementation in Felix is a separate bundle. Richard Hall hopes to eventually merge that implementation into the Felix framework. I was curious since after all collaboration may have been as fruitful than co-opetition. Thanks for taking the time to answer. Pascal Tom graycol.gifPascal Rapicault ---09/04/2012 06:12:46 AM---I have a couple questions about the framework rewrite: ecblank.gif From: ecblank.gif Pascal Rapicault pas...@rapicault.net ecblank.gif To: ecblank.gif Equinox development mailing list equinox-dev@eclipse.org, ecblank.gif Date: ecblank.gif 09/04/2012 06:12 AM ecblank.gif Subject: ecblank.gif [equinox-dev] About the fwk rewrite I have a couple questions about the framework rewrite: - Is there a document describing the goals of the rewrite - Is there any plan to change how things work on disk? (e.g. config.ini) - Since we are sharing the resolver with Felix, have we considered simply reusing felix in its entirety? Pascal ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] New framework?
Thanks for your detailed answer Tom. This is indeed a great news. I will encourage you to talk about this effort more widely and openly, as this is a perfect point in time to get more ppl involved with the project (though to some extent it may even be a tad late). Pascal On 2012-08-30, at 7:55 AM, Thomas Watson wrote: Hi Pascal, In short, yes I have been working on re-implementing the core framework on top of a generic capability and requirements model that was introduced in the Core OSGi Framework R5 specification and the OSGi resolver specification that was released with the OSGi Enterprise R5 specification. As Pascal knows the current Equinox Framework is built upon what I call a strongly typed dependency model where the package org.eclipse.osgi.service.resolver is at the center. This equinox resolver API is quite complex and a bit cumbersome in my opinion. Over the years it has become harder and harder to maintain and adapt as new requirement types (namespaces) get defined by the OSGi alliance. I started this effort in early summer when we thought Java Modularity was going to be released in Java 8. Java Modularity in the VM has the potential to add new dependency types and I wanted a framework implementation that would could easily prototype different dependency types. Instead of re-inventing a dependency model I decided to give the generic resource/capability/requirement model defined by OSGi R5 a try and rebase the framework implementation on that. I also decided not to implement my own OSGi Resolver implementation, but instead have chosen to collaborate with Richard Hall of the Apache Felix project and reuse the OSGi Resolver service implementation from the Felix project. This is why you will notice the occasional CQ note go by over the equinox-dev mailing list for the Felix Resolver. Overall I think the model is quite nice and I have been relatively happy with the implementation on top of this model. So far this has largely been a side project of my own (in a branch called twatson/container). Now that Java Modularity has been pushed out to Java 9 it is not urgent to push a radically different framework implementation into Kepler in preparation for Java Modularity and OSGi inter-op. With that said, I just recently got to the point where the New framework is getting useful and can actually launch Eclipse. But I did break many things in the process. Here is just a short list and I am sure there are others: - completely removed the disabled osgi console implementation - completely removed the provisional composite bundle implementation, I know of some users of this but they have plans to move to OSGi Subsystems or Equinox Region Digraph. - removed much of the provisional security service implementation, I am not aware of anyone using this. - removed support for legacy plugin.xml support - do not provide a PlatformAdmin service implementation, currently working on a fragment that can add it back - all equinox framework extension hook implementations will need to be migrated to new hooks. With that I have been able to trim off 400K from the framework implementation. A couple of weeks ago, when I got Eclipse to launch on the new implementation and I finally got all the OSGi Compliance tests to pass, I was getting tempted to push for getting the new framework implementation into the Kepler plan. But over the coarse of the past two weeks I have decided that it is not the right time. The Equinox team needs to do a in-depth investigation of the impact of such a change and start making preparations to move to the new implementation. That is why you have been seeing mention of a new framework in some of the bug reports. I have been opening up bugs and providing patches that are necessary for eclipse to function on the new implementation. My tentative plan for Kepler is to keep the current implementation but for the most part it will be in maintenance mode. I will be largely focused on getting the new framework implementation in shape and providing patches to other components in Kepler that will allow them to run on both the old and new framework implementations. Tom graycol.gifPascal Rapicault ---08/29/2012 09:44:47 PM---Through a couple of bug reports, it looks like we are working on a new implementation of the framework. Did I get that right? ecblank.gif From: ecblank.gif Pascal Rapicault pas...@rapicault.net ecblank.gif To: ecblank.gif Equinox development mailing list equinox-dev@eclipse.org, ecblank.gif Date: ecblank.gif 08/29/2012 09:44 PM ecblank.gif Subject: ecblank.gif [equinox-dev] New framework? Through a couple of bug reports, it looks like we are working on a new implementation of the framework. Did I get that right? Pascal ___ equinox-dev mailing list equinox-dev
[equinox-dev] New framework?
Through a couple of bug reports, it looks like we are working on a new implementation of the framework. Did I get that right? Pascal ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] looking up binaries
Hey, I have a situation where the binaries for my application are spread across multiple bundles and those libraries depend on each others. For example, I have bundle1 that carries lib1.so and I have bundle2 that carries lib2.so, and bundle1 depends on bundle2. When I try to load lib1.so if lib2.so has not yet been loaded, then the loading of lib1 will fail. Is there a fundamental reason why we loading of the libraries could mimic the loading of classes? Thx Pascal ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] looking up binaries
Yeah, I know that modifying the system prop on the fly would not work. I read the article :) But the trick they mention is equivalent to it though. What you are eluding in the other thread is where I'm going with this, but I'm not sure that preloading all the libraries would not result in additional issues. Anyway thanks for the discussion. If I get to continue the exploration down this path, I will report on my progress. Pascal On 2012-06-10, at 10:51 PM, BJ Hargrave wrote: I don't think modifying java.library.path in the fly will work. See http://blog.cedarsoft.com/2010/11/setting-java-library-path-programmatically/ Like I said, native code support in Java kind of sucks. I would hope that Java 8 will improve things since Jigsaw will slam into this as well. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargr...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From:Pascal Rapicault pas...@rapicault.net To:Equinox development mailing list equinox-dev@eclipse.org, Date:2012/06/10 20:29 Subject:Re: [equinox-dev] looking up binaries Sent by:equinox-dev-boun...@eclipse.org The suggested approach would work but is rather painful. I have about 50 bundles delivering legacy native code so making sure that there is java code initializing all the libs does not seem like it would work all that well, and I'm not sure that I would not end with cyclic dependencies. At this point I have a script that extracts all the binaries into a lib folder and just set the os level library path... So much for modularity. I was hoping that with the ability to change the java.library.path dynamically at runtime[1] and the manifest information pertaining to native code, it would be possible to dynamically set the java.library.path upon loadLibrary to cause the right libs to be part of the library path. What do you think? Pascal [1] - http://blog.cedarsoft.com/2010/11/setting-java-library-path-programmatically/ On 2012-06-10, at 5:23 PM, BJ Hargrave wrote: 'cause that is the way it was designed in Java? System.loadLibrary is typically called from some class' static initializer to define the native methods of the class. System.loadLibrary calls ClassLoader.findLibrary to request advice in locating the native library. For bundle class loaders, this can then provide the location of the native library mentioned in the bundle's Bundle-NativeCode manifest header. In your example, since a class in bundle 1 has a static initializer calling System.loadLibrary(1), then that code needs to first trigger a class loader from bundle 2 where that class' static initializer calls System.loadLibrary(2). This will then make sure lib2.so is loaded before lib1.so. In general, the native code support in Java is really only useful for loading JNI native libraries. How the dependencies of the JNI native libraries are met is not addressed. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargr...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From:Pascal Rapicault pas...@rapicault.net To:Equinox development mailing list equinox-dev@eclipse.org, Date:2012/06/10 16:48 Subject:[equinox-dev] looking up binaries Sent by:equinox-dev-boun...@eclipse.org Hey, I have a situation where the binaries for my application are spread across multiple bundles and those libraries depend on each others. For example, I have bundle1 that carries lib1.so and I have bundle2 that carries lib2.so, and bundle1 depends on bundle2. When I try to load lib1.so if lib2.so has not yet been loaded, then the loading of lib1 will fail. Is there a fundamental reason why we loading of the libraries could mimic the loading of classes? Thx Pascal ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] JVM arguments passed through launcher command line?
See -vmargs on http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fruntime-options.html HTH Pascal On 2012-05-08, at 9:01 AM, Ben Abernathy wrote: I'm not sure if this is the right list to ask, but here it goes. We have an OSGi application built that uses the equinox launcher. I would like to be able to pass -D properties via the command line in order to aid automated integration testing of our application. For example, I'm trying to accomplish this: application.exe -Dsomeprop=somevalue However, this doesn't appear to work. Is this not possible or am I missing something else? I realize I can declare these properties in the launcher ini, but I'd prefer not to do that as I'd have to create a new ini for each integration test. Any help would be greatly appreciated. Ben ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [error] encoded string too long
I would recommend opening a bug report with a real test case or a just a some fake data exhibiting the problem. In this case we may be able to produce a patch that you could apply back on this particular version of the fwk. HTH Pascal On 2012-04-05, at 6:32 PM, Raymond Auge wrote: Hello everyone, My name is Raymond Augé, I'm a senior architect at Liferay, Inc. We're bundling equinox (3.7.2.v20120110-1415) and recently I've started seeing the following error when the Framework tried to save it's state: 18:04:28,630 INFO [org_eclipse_osgi:84] FrameworkEvent STARTLEVEL CHANGED 18:04:38,142 ERROR [org_eclipse_osgi:81] java.io.UTFDataFormatException: encoded string too long: 72142 bytes at java.io.DataOutputStream.writeUTF(DataOutputStream.java:364) at java.io.DataOutputStream.writeUTF(DataOutputStream.java:323) at org.eclipse.osgi.internal.resolver.StateWriter.writeStringOrNull(StateWriter.java:686) at org.eclipse.osgi.internal.resolver.StateWriter.writePlatformProp(StateWriter.java:181) at org.eclipse.osgi.internal.resolver.StateWriter.saveState(StateWriter.java:130) at org.eclipse.osgi.internal.resolver.StateObjectFactoryImpl.writeState(StateObjectFactoryImpl.java:439) at org.eclipse.osgi.internal.baseadaptor.StateManager.writeState(StateManager.java:178) at org.eclipse.osgi.internal.baseadaptor.StateManager.update(StateManager.java:116) at org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveStateData(BaseStorage.java:661) at org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveAllData(BaseStorage.java:458) at org.eclipse.osgi.internal.baseadaptor.BaseStorage$StateSaver.run(BaseStorage.java:1304) at java.lang.Thread.run(Thread.java:679) It appears to be due to a very large number of package exports on the system bundle (the Framework is embedded). Has anyone encountered this? I search bugs.eclipse.org/bugs with no results that seem to match. It appears I may have to create an Storage hook to get around the issue short term. Thoughts? Sincerely, -- Raymond Augé | Senior Software Architect | Liferay, Inc. --- 25 Apr 2012 | Liferay Nordic Symposium | liferay.com/nordic2012 NEW! 17 May 2012 | Liferay Budapest Symposium | liferay.com/budapest2012 23 May 2012 | Liferay France Symposium | liferay.com/france2012 ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] +1 for Bogdan Gheorghe on rt.equinox.framework by Pascal Rapicault
Pascal Rapicault voted: +1 +1 Voting summary: http://portal.eclipse.org/ ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] OSGI jar file built from specific tag differs from OSGI jar included with BIRT runtime?
I'm not surprised by this difference and would argue that the process by which in the past you managed to get the same jar is coincidence / luck, or some wonky things that the BIRT team did :) Several reasons come to mind as to why there is a difference: - the Eclipse build process condition the jar (pack200 then unpack200 it) which rearranges the bytecode - you may be using a different version of the compiler than the one that has been used during the Eclipse build HTH Pascal On 2012-03-28, at 4:13 PM, Hardin, John wrote: The OSGI jar file included with the 3.7.2 version of the BIRT runtime is org.eclipse.osgi_3.7.2.v20120110-1415.jar. When I extract the v20120110-1415 version of the equinox framework from here (http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tag/?id=v20120110-1415), and manually build theorg.eclipse.osgi “bundle” with Eclipse, I get jar contents that are almost completely different than the jar included with BIRT. To compare the jars, I first expand them, run md5sum on all of the constituent files, and compare the results. I’ve attached the results of diff’ing the md5sum results for all of the jar file constituents. As you can see, ALL of the .class files differ! Also, there are files in the BIRT jar’s META-INF directory that don’t exist in the META-INF directory of the jar built from source (e.g., META-INF/ECLIPSEF.RSA,META_INF/ECLIPSEF.SF). I’m able to build an earlier version of the OSGI jar from source, and find its contents are identical to those of the OSGI jar that’s included with a corresponding earlier version of the BIRT runtime; so, I think my process is sound. Can anyone please help me understand what I’m missing in terms of building the OSGI jar file, and why its contents differ so markedly from the contents of the jar file included with the BIRT runtime? Thank you, in advance, for your assistance. Sincerely, -John hardin osgi-jar-file-diffs.html___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Any consumers of the org.eclipse.equinox.http bundle?
Some p2 tests use that bundle. They could probably changed to use the other bundle. On 2011-10-27, at 2:18 PM, Thomas Watson wrote: In Equinox we have a two implementations of the HttpService. 1) org.eclipse.equinox.http - that has a home grown web container and therefore has to implement the complete servlet specification itself. 2) org.eclipse.equinox.http.jetty - that is uses a jetty implementation for the web container implementation. The implementation that uses jetty is by far the most used HttpService implementation we have. For example, it is the one shipped with the eclipse SDK to serve up the help and is used in the server-side equinox project. The old org.eclipse.equinox.http is outdated and gets very little attention by the committers. As we consider moving to support servlet 3.0 and Jetty 8 we also need to consider what, if anything, should be done for the old stand-alone HttpService bundle org.eclipse.equinox.http. For Juno I propose that the Equinox project stops building the old stand-alone HttpService implementation bundle org.eclipse.equinox.http. I would much prefer we focus on the implementation of the HttpService that uses Jetty and keep the implementation of the servlet container in the hands of the experts that know how to implement it (i.e. the jetty team). Please voice any concerns to this mailing list or to the bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=362217 Thanks. Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Office hours
You have beginner or experienced-level questions about Equinox or p2? You want to contribute to Equinox or p2? Just want to chat with us? Join us on our weekly office hours every Tuesday at 1pm EST on the #equinox-dev channel on IRC (http://wiki.eclipse.org/IRC). During these meetings equinox and p2 committers, contributors and aficionados will answer questions on any topic you come up with. Questions to be answered on a first come, first served basis. See you there, PaScaL ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] equinox git repo
We should probably get that old repo removed by the webmaster. I did this for p2. On 2011-08-09, at 5:20 PM, Andrew Niefer wrote: The repositories you want are git://git.eclipse.org/gitroot/equinox/rt.equinox.framework.git git://git.eclipse.org/gitroot/equinox/rt.equinox.bundles.git git://git.eclipse.org/gitroot/equinox/rt.equinox.p2.git git://git.eclipse.org/gitroot/equinox/rt.equinox.security.git “git://dev.eclipse.org/org.eclipse.equinox/org.eclipse.equinox.git” is a read only mirror of the cvs repository. (http://wiki.eclipse.org/Git#Git_mirrors_of_CVS_repositories) -Andrew From: Kapukaranov, Borislav borislav.kapukara...@sap.com To: equinox-dev@eclipse.org equinox-dev@eclipse.org Date: 08/09/2011 11:07 AM Subject: [equinox-dev] equinox git repo Sent by: equinox-dev-boun...@eclipse.org Hi, Is “git://dev.eclipse.org/org.eclipse.equinox/org.eclipse.equinox.git” the correct git repo for equinox at the moment, meaning up-to-date, where-all-the-action-is, etc.? Also does it include also the migrated incubator projects? I noticed it’s larger than 2.03GB… and cloned for more than 2 hours, so I suspect I got the wrong one. If it actually is the correct repo, can’t it be optimized, e.g. separating the incubator, bundles, components, framework, etc. subfolders into separate repos? It’s a bit inconvenient to clone for 2+ hours just to get the source of org.eclipse.osgi. Thanks, Borislav___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Call every other week
We are now in our summer schedule which means a call every other week. The next call will take place Monday 11th. PaScaL ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Equinox tagged for the next Juno Integration build
The builds from June 21 or the N build from the 27th are all from HEAD (thus 3.8 / Juno). The webpage content has not yet been updated to reflect the reality. On 2011-06-28, at 7:49 AM, Kirchev, Lazar wrote: Hello, Where can I find the build artifacts? On http://download.eclipse.org/equinox/ only 3.7 build artifacts are available. Regards, Lazar From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: Tuesday, June 28, 2011 12:14 AM To: equinox-dev@eclipse.org Subject: [equinox-dev] Equinox tagged for the next Juno Integration build The map file has been updated for the following Bug changes: + Bug 350453. Incorrect usage of InputStream.available in ReliableFile (FIXED) The following projects have changed: org.eclipse.equinox.supplement org.eclipse.osgi.tests org.eclipse.osgi Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] p2 / pde tag
I've tagged p2 and PDE build (and its tests) because to react to some changes in the publisher. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Eclipse and Equinox 3.7 is now available
There is currently no plan to make anything avilable in a Maven repo. Which part are you interested in seeing available in a Maven repo? On 2011-06-27, at 6:13 PM, Jacek Laskowski wrote: On Wed, Jun 22, 2011 at 3:19 PM, Kim Moir kim_m...@ca.ibm.com wrote: The Eclipse and Equinox committers are happy to announce that Eclipse 3.7 is now available for download as part of the Indigo release. Hi, When will the release be available in Maven repo? Will it, right? Jacek -- Jacek Laskowski Java EE, functional languages and IBM WebSphere - http://blog.japila.pl Warszawa JUG conference = Confitura (formerly Javarsovia) :: http://confitura.pl ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Git repo and the incubator
If I understand everything correctly, the current proposal for the structure of git repos is to have one git repo per unix user group. In our case this means that we will have one equinox repo, one p2 repo, a few others and one incubator repo. As much as I understand the motivation behind this, I would like to discuss the dissolution of the incubator repo and instead see each relevant bit be moved to a more appropriate git repo. I think this will help showcase the other things we are working on and see that we are just not a framework. I know that this does not mesh with our way of segregating committers, but on the other hand I have a hard time imagining someone who is given commit rights on the incubator part of the repo to go and mess around in the rest of the code. wdyt? PaScaL ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] WiringAdmin vs PlatformAdmin
With the introduction of the WiringAdmin service, could someone shed some light on its relationship with equinox owns PlatformAdmin and especially the State aspect of that one. The reason I'm asking is that simpleconfigurator has dependencies on PlatformAdmin (see class StateResolverUtils) and I would like to know if it would make sense to change this to use WiringAdmin instead. Thx PaScaL ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Signing facility
Hey, Do you know if the signing ssl infrastructure provided as part of the fwk would be easily extractible as a separate bundle much like we do for supplement? Thx PaScaL ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Writing something into the config.ini file
If you want to make your example on the ML, I'm sure others would find it handy. On 2011-05-11, at 3:21 PM, Domenico Alessi wrote: Arg! Nevermind, caching effect. Worked like a charm. Thanks. Dom From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Domenico Alessi Sent: May-11-11 3:12 PM To: Equinox development mailing list Cc: P2 developer discussions Subject: Re: [equinox-dev] Writing something into the config.ini file Thanks Pascal. Ok, so before I put the plugin below into the dependencies, I saw the actions in the content.jar. Now that I have put in the include I no longer see the actions in my content.jar file. So nothing gets placed into my config.ini, but install passes. Thanks, Dom From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Pascal Rapicault Sent: May-11-11 2:40 PM To: Equinox development mailing list Cc: P2 developer discussions Subject: Re: [equinox-dev] Writing something into the config.ini file Make sure that the org.eclipse.equinox.p2.touchpoint.eclipse is in available. On 2011-05-11, at 2:33 PM, Domenico Alessi wrote: Hi Pascal, I get the following error at install time: An error occurred while configuring the installed items session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null -- [R]com.test.p2.feature.feature.group 1.0.0.201105111415, action=org.eclipse.equinox.internal.p2.engine.MissingAction). No action found for: setProgramProperty. No action found for: setProgramProperty. My p2.inf looks like this: instructions.configure=\ setProgramProperty(propName:testValue1,propValue:testValue2);\ Thanks in advance, Dom From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Pascal Rapicault Sent: May-11-11 1:36 PM To: Equinox development mailing list; P2 developer discussions Subject: Re: [equinox-dev] Writing something into the config.ini file This can be done using a touchpoint action (Provisioning Actions and Touchpoints) In this particular case: setProgramProperty, for example setProgramProperty(propName:equinox.use.ds, propValue:true); To get this added to your metadata you need to store that into a p2.inf file (Customizing metadata) On 2011-05-11, at 1:30 PM, Domenico Alessi wrote: Hi All, I a have quick question. I have a feature/plugin that I wish to install but I also want at installation time to put in a key/value pair into the config.ini. I see that install Handlers are discouraged. How can I accomplish this? BR, Dom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Writing something into the config.ini file
I heard there will great presentations and presenters :p On 2011-05-11, at 3:24 PM, Dahanne, Anthony wrote: You could even demo it during the EclipseDemoCamp in Montreal ! ;-) http://wiki.eclipse.org/index.php?title=Eclipse_DemoCamps_Indigo_2011/Montreal Just saying... Anthony De : equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] De la part de Pascal Rapicault Envoyé : 11 mai 2011 15:22 À : Equinox development mailing list Cc : P2 developer discussions Objet : Re: [equinox-dev] Writing something into the config.ini file If you want to make your example on the ML, I'm sure others would find it handy. On 2011-05-11, at 3:21 PM, Domenico Alessi wrote: Arg! Nevermind, caching effect. Worked like a charm. Thanks. Dom From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Domenico Alessi Sent: May-11-11 3:12 PM To: Equinox development mailing list Cc: P2 developer discussions Subject: Re: [equinox-dev] Writing something into the config.ini file Thanks Pascal. Ok, so before I put the plugin below into the dependencies, I saw the actions in the content.jar. Now that I have put in the include I no longer see the actions in my content.jar file. So nothing gets placed into my config.ini, but install passes. Thanks, Dom From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Pascal Rapicault Sent: May-11-11 2:40 PM To: Equinox development mailing list Cc: P2 developer discussions Subject: Re: [equinox-dev] Writing something into the config.ini file Make sure that the org.eclipse.equinox.p2.touchpoint.eclipse is in available. On 2011-05-11, at 2:33 PM, Domenico Alessi wrote: Hi Pascal, I get the following error at install time: An error occurred while configuring the installed items session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null -- [R]com.test.p2.feature.feature.group 1.0.0.201105111415, action=org.eclipse.equinox.internal.p2.engine.MissingAction). No action found for: setProgramProperty. No action found for: setProgramProperty. My p2.inf looks like this: instructions.configure=\ setProgramProperty(propName:testValue1,propValue:testValue2);\ Thanks in advance, Dom From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Pascal Rapicault Sent: May-11-11 1:36 PM To: Equinox development mailing list; P2 developer discussions Subject: Re: [equinox-dev] Writing something into the config.ini file This can be done using a touchpoint action (Provisioning Actions and Touchpoints) In this particular case: setProgramProperty, for example setProgramProperty(propName:equinox.use.ds, propValue:true); To get this added to your metadata you need to store that into a p2.inf file (Customizing metadata) On 2011-05-11, at 1:30 PM, Domenico Alessi wrote: Hi All, I a have quick question. I have a feature/plugin that I wish to install but I also want at installation time to put in a key/value pair into the config.ini. I see that install Handlers are discouraged. How can I accomplish this? BR, Dom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] (no subject)
Please ask this question on the virgo ML: https://dev.eclipse.org/mailman/listinfo/virgo-dev On 2011-04-23, at 11:58 AM, 段琦 wrote: Hi Did anyone use the Virgo?Today,I try to run the greenpages according to the related papers(http://www.eclipse.org/virgo/documentation/virgo-documentation-2.1.1.RELEASE/docs/virgo-getting-started/html/ch03s03.html).When I use run to start the H2 database server,the console report the Cannot find H2 jars in .m2 Maven repository. I think my Maven repository lose the *.h2.*.jar,so I install a related *h2.*.jar in the repository,but it still can't work.Dose anybody come cross this problem,could you help me? Very Thanks. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [p2-dev] Equinox/p2 meeting minutes posted
I just released and tagged. Thx everybody. On 2011-04-21, at 10:01 AM, Jeff McAffer wrote: Tom and I have looked at the new patch and agree it looks good. The bug report has been updated. As for the process stuff, you could have/should have/might have/... several things but that doesn't change the fact that we are 5 weeks past the API freeze and at the start of warmup builds for functional freeze looking to commit new function and API. There is a reason we have a rampdown process. It is not meant to block things but rather to give a chance for sober second thought and check that we are not doing something stupid in the heat of the crap I forgot to ... moment. In this case some really good feedback on the API came from several sources so the process seems to have done its job. Thanks to all. Jeff On 2011-04-20, at 10:42 PM, Pascal Rapicault wrote: 1) only if this means 3.7.1. 2) Not sure if this is possible since the classes are in a public package. 3) I think we are making an overly big deal of this whole thing. The API proposed has been reviewed by Dave and others a long time ago and it has not changed since then. The feedback from the last few days has only been focused on naming... which, as we know too well in Equinox, is a sign that there is no other issues. The other thing to remember is that should I had the chance to commit this API right after EclipseCon, the crappy names that I would have come up would have been carved in stone and we would not be here... I have attached a new patch to the bug report. On 2011-04-20, at 10:35 AM, Thomas Watson wrote: So here are the options as I see them. 1) postpone this new API until next release 2) propose the API as provisional (i.e. use x-internal etc) 3) work on the API as much as possible to gain confidence that it is API we can live with and support in future releases. 3) seems rather risky at this point in time. Is 2) an acceptable approach? Tom graycol.gifJeff McAffer ---04/20/2011 09:29:49 AM---If there is no objection I will release that during the week so we can actually work on the code together. I'm not a real fan o ecblank.gif From: ecblank.gif Jeff McAffer j...@eclipsesource.com ecblank.gif To: ecblank.gif Equinox development mailing list equinox-dev@eclipse.org ecblank.gif Cc: ecblank.gif P2 developer discussions p2-...@eclipse.org ecblank.gif Date: ecblank.gif 04/20/2011 09:29 AM ecblank.gif Subject:ecblank.gif Re: [equinox-dev] [p2-dev] Equinox/p2 meeting minutes posted If there is no objection I will release that during the week so we can actually work on the code together. I'm not a real fan of this approach in the last week of M7. If bogus API gets into M7 then we'll have a hell of a time removing/changing it. We almost always end up regretting those last minute pushes. For the code itself I don't care but releasing API that is not baked is less than optimal. Jeff On 2011-04-19, at 1:30 PM, Pascal Rapicault wrote: This issue has been discussed at the end of M6 with Tom and it has been agreed at the time that we will add this new API in M7 (I had not foreseen it happening so late). I just attached a new patch taking the feedback into account. The focus is on API since this is the most pressing issue for the rest of the week. The code needs to be polished. If there is no objection I will release that during the week so we can actually work on the code together. On 2011-04-19, at 9:27 AM, Jeff McAffer wrote: Darn. you are talking about https://bugs.eclipse.org/bugs/show_bug.cgi?id=337016? That's new API right? I took a look but am not sure what the final form is that you are thinking of. Susan had some comments and David as well. The original patch from you had a method getAgent() which seems suspect as it does effectively the ServiceHelper trick. Do you have any examples of this API in use. If you are going to look to release this please post a new patch with the proposed shape, some example use and mark for review. Ideally we could get John and/or DJ to review (I'll review as PMC guy). Please do not release until it has been reviewed. Jeff On 2011-04-18, at 5:22 PM, Pascal Rapicault wrote: Crap. Just a heads up that I stil need to release the new simplified API around the operations. I'll likely only get to that Friday. On 2011-04-18, at 3:21 PM, Thomas Watson wrote: http://wiki.eclipse.org/Equinox/Meeting_Minutes/20110418 As a reminder M7 is next week. After that we head into rampdown for M7. Please see http://eclipse.org/equinox/planning/freeze_plan_3.7.php for more details on the process for ramping down the release. Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [p2-dev] Equinox/p2 meeting minutes posted
The API has been ready since before eclipsecon. Dave and others reviewed it and it is good. What do you propose instead? We wait 3.7.1? On 2011-04-20, at 10:29 AM, Jeff McAffer wrote: If there is no objection I will release that during the week so we can actually work on the code together. I'm not a real fan of this approach in the last week of M7. If bogus API gets into M7 then we'll have a hell of a time removing/changing it. We almost always end up regretting those last minute pushes. For the code itself I don't care but releasing API that is not baked is less than optimal. Jeff On 2011-04-19, at 1:30 PM, Pascal Rapicault wrote: This issue has been discussed at the end of M6 with Tom and it has been agreed at the time that we will add this new API in M7 (I had not foreseen it happening so late). I just attached a new patch taking the feedback into account. The focus is on API since this is the most pressing issue for the rest of the week. The code needs to be polished. If there is no objection I will release that during the week so we can actually work on the code together. On 2011-04-19, at 9:27 AM, Jeff McAffer wrote: Darn. you are talking about https://bugs.eclipse.org/bugs/show_bug.cgi?id=337016? That's new API right? I took a look but am not sure what the final form is that you are thinking of. Susan had some comments and David as well. The original patch from you had a method getAgent() which seems suspect as it does effectively the ServiceHelper trick. Do you have any examples of this API in use. If you are going to look to release this please post a new patch with the proposed shape, some example use and mark for review. Ideally we could get John and/or DJ to review (I'll review as PMC guy). Please do not release until it has been reviewed. Jeff On 2011-04-18, at 5:22 PM, Pascal Rapicault wrote: Crap. Just a heads up that I stil need to release the new simplified API around the operations. I'll likely only get to that Friday. On 2011-04-18, at 3:21 PM, Thomas Watson wrote: http://wiki.eclipse.org/Equinox/Meeting_Minutes/20110418 As a reminder M7 is next week. After that we head into rampdown for M7. Please see http://eclipse.org/equinox/planning/freeze_plan_3.7.php for more details on the process for ramping down the release. Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ p2-dev mailing list p2-...@eclipse.org https://dev.eclipse.org/mailman/listinfo/p2-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ p2-dev mailing list p2-...@eclipse.org https://dev.eclipse.org/mailman/listinfo/p2-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [p2-dev] Equinox/p2 meeting minutes posted
There is only one discussion point. Do we want a new class versus a setter? Rather than focusing on the process, please review the API. On 2011-04-20, at 11:30 AM, Jeff McAffer wrote: We seem to still be discussing the API. You seem to want to put it in now (today) and sort it out later. I'd like the API to be more agreed to before putting it in to M7 given the lateness of the hour. Jeff On 2011-04-20, at 10:43 AM, Pascal Rapicault wrote: The API has been ready since before eclipsecon. Dave and others reviewed it and it is good. What do you propose instead? We wait 3.7.1? On 2011-04-20, at 10:29 AM, Jeff McAffer wrote: If there is no objection I will release that during the week so we can actually work on the code together. I'm not a real fan of this approach in the last week of M7. If bogus API gets into M7 then we'll have a hell of a time removing/changing it. We almost always end up regretting those last minute pushes. For the code itself I don't care but releasing API that is not baked is less than optimal. Jeff On 2011-04-19, at 1:30 PM, Pascal Rapicault wrote: This issue has been discussed at the end of M6 with Tom and it has been agreed at the time that we will add this new API in M7 (I had not foreseen it happening so late). I just attached a new patch taking the feedback into account. The focus is on API since this is the most pressing issue for the rest of the week. The code needs to be polished. If there is no objection I will release that during the week so we can actually work on the code together. On 2011-04-19, at 9:27 AM, Jeff McAffer wrote: Darn. you are talking about https://bugs.eclipse.org/bugs/show_bug.cgi?id=337016? That's new API right? I took a look but am not sure what the final form is that you are thinking of. Susan had some comments and David as well. The original patch from you had a method getAgent() which seems suspect as it does effectively the ServiceHelper trick. Do you have any examples of this API in use. If you are going to look to release this please post a new patch with the proposed shape, some example use and mark for review. Ideally we could get John and/or DJ to review (I'll review as PMC guy). Please do not release until it has been reviewed. Jeff On 2011-04-18, at 5:22 PM, Pascal Rapicault wrote: Crap. Just a heads up that I stil need to release the new simplified API around the operations. I'll likely only get to that Friday. On 2011-04-18, at 3:21 PM, Thomas Watson wrote: http://wiki.eclipse.org/Equinox/Meeting_Minutes/20110418 As a reminder M7 is next week. After that we head into rampdown for M7. Please see http://eclipse.org/equinox/planning/freeze_plan_3.7.php for more details on the process for ramping down the release. Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ p2-dev mailing list p2-...@eclipse.org https://dev.eclipse.org/mailman/listinfo/p2-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ p2-dev mailing list p2-...@eclipse.org https://dev.eclipse.org/mailman/listinfo/p2-dev ___ p2-dev mailing list p2-...@eclipse.org https://dev.eclipse.org/mailman/listinfo/p2-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [p2-dev] Equinox/p2 meeting minutes posted
1) only if this means 3.7.1. 2) Not sure if this is possible since the classes are in a public package. 3) I think we are making an overly big deal of this whole thing. The API proposed has been reviewed by Dave and others a long time ago and it has not changed since then. The feedback from the last few days has only been focused on naming... which, as we know too well in Equinox, is a sign that there is no other issues. The other thing to remember is that should I had the chance to commit this API right after EclipseCon, the crappy names that I would have come up would have been carved in stone and we would not be here... I have attached a new patch to the bug report. On 2011-04-20, at 10:35 AM, Thomas Watson wrote: So here are the options as I see them. 1) postpone this new API until next release 2) propose the API as provisional (i.e. use x-internal etc) 3) work on the API as much as possible to gain confidence that it is API we can live with and support in future releases. 3) seems rather risky at this point in time. Is 2) an acceptable approach? Tom graycol.gifJeff McAffer ---04/20/2011 09:29:49 AM---If there is no objection I will release that during the week so we can actually work on the code together. I'm not a real fan o ecblank.gif From: ecblank.gif Jeff McAffer j...@eclipsesource.com ecblank.gif To: ecblank.gif Equinox development mailing list equinox-dev@eclipse.org ecblank.gif Cc: ecblank.gif P2 developer discussions p2-...@eclipse.org ecblank.gif Date: ecblank.gif 04/20/2011 09:29 AM ecblank.gif Subject: ecblank.gif Re: [equinox-dev] [p2-dev] Equinox/p2 meeting minutes posted If there is no objection I will release that during the week so we can actually work on the code together. I'm not a real fan of this approach in the last week of M7. If bogus API gets into M7 then we'll have a hell of a time removing/changing it. We almost always end up regretting those last minute pushes. For the code itself I don't care but releasing API that is not baked is less than optimal. Jeff On 2011-04-19, at 1:30 PM, Pascal Rapicault wrote: This issue has been discussed at the end of M6 with Tom and it has been agreed at the time that we will add this new API in M7 (I had not foreseen it happening so late). I just attached a new patch taking the feedback into account. The focus is on API since this is the most pressing issue for the rest of the week. The code needs to be polished. If there is no objection I will release that during the week so we can actually work on the code together. On 2011-04-19, at 9:27 AM, Jeff McAffer wrote: Darn. you are talking about https://bugs.eclipse.org/bugs/show_bug.cgi?id=337016? That's new API right? I took a look but am not sure what the final form is that you are thinking of. Susan had some comments and David as well. The original patch from you had a method getAgent() which seems suspect as it does effectively the ServiceHelper trick. Do you have any examples of this API in use. If you are going to look to release this please post a new patch with the proposed shape, some example use and mark for review. Ideally we could get John and/or DJ to review (I'll review as PMC guy). Please do not release until it has been reviewed. Jeff On 2011-04-18, at 5:22 PM, Pascal Rapicault wrote: Crap. Just a heads up that I stil need to release the new simplified API around the operations. I'll likely only get to that Friday. On 2011-04-18, at 3:21 PM, Thomas Watson wrote: http://wiki.eclipse.org/Equinox/Meeting_Minutes/20110418 As a reminder M7 is next week. After that we head into rampdown for M7. Please see http://eclipse.org/equinox/planning/freeze_plan_3.7.php for more details on the process for ramping down the release. Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ p2-dev mailing list p2-...@eclipse.org https://dev.eclipse.org/mailman/listinfo/p2-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [p2-dev] Equinox/p2 meeting minutes posted
This issue has been discussed at the end of M6 with Tom and it has been agreed at the time that we will add this new API in M7 (I had not foreseen it happening so late). I just attached a new patch taking the feedback into account. The focus is on API since this is the most pressing issue for the rest of the week. The code needs to be polished. If there is no objection I will release that during the week so we can actually work on the code together. On 2011-04-19, at 9:27 AM, Jeff McAffer wrote: Darn. you are talking about https://bugs.eclipse.org/bugs/show_bug.cgi?id=337016? That's new API right? I took a look but am not sure what the final form is that you are thinking of. Susan had some comments and David as well. The original patch from you had a method getAgent() which seems suspect as it does effectively the ServiceHelper trick. Do you have any examples of this API in use. If you are going to look to release this please post a new patch with the proposed shape, some example use and mark for review. Ideally we could get John and/or DJ to review (I'll review as PMC guy). Please do not release until it has been reviewed. Jeff On 2011-04-18, at 5:22 PM, Pascal Rapicault wrote: Crap. Just a heads up that I stil need to release the new simplified API around the operations. I'll likely only get to that Friday. On 2011-04-18, at 3:21 PM, Thomas Watson wrote: http://wiki.eclipse.org/Equinox/Meeting_Minutes/20110418 As a reminder M7 is next week. After that we head into rampdown for M7. Please see http://eclipse.org/equinox/planning/freeze_plan_3.7.php for more details on the process for ramping down the release. Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ p2-dev mailing list p2-...@eclipse.org https://dev.eclipse.org/mailman/listinfo/p2-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] +1 for Borislav Kapukaranov on rt.equinox.bundles by Pascal Rapicault
Pascal Rapicault voted: +1 The more the merrier :) Voting summary: http://portal.eclipse.org/ ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] +1 for John W Ross on rt.equinox.bundles by Pascal Rapicault
Pascal Rapicault voted: +1 I like commenting on nominations :) Voting summary: http://portal.eclipse.org/ ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Events for instance location?
I have not looked at it myself, but I have been told that no service registration even was ever being sent. On 2011-02-18, at 11:49 AM, Thomas Watson wrote: We do register the instance location as a Location service with type=osgi.instance.area service property. Are you saying you do not see this service registered at all in your environment? Tom -equinox-dev-boun...@eclipse.org wrote: - To: Equinox development mailing list equinox-dev@eclipse.org From: Chris Aniszczyk caniszc...@gmail.com Sent by: equinox-dev-boun...@eclipse.org Date: 02/17/2011 01:38PM Subject: Re: [equinox-dev] Events for instance location? On Thu, Feb 17, 2011 at 1:32 PM, Pascal Rapicault pas...@sonatype.com wrote: For some reason I thought that the instance location was being registered as a service. However, I can't seem to find this. Did I dream that ? If I did, how can one know when the instance location is actually set? In PDE, we accomplish this by acquiring the org.osgi.service.datalocation.Location and then call isSet() on it... This is what happens when you try to launch on an already in use workspace and get that wonderful error... -- Cheers, Chris Aniszczyk http://aniszczyk.org +1 860 839 2465 ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Events for instance location?
For some reason I thought that the instance location was being registered as a service. However, I can't seem to find this. Did I dream that ? If I did, how can one know when the instance location is actually set? Thx PaScaL ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Equinox / p2 call cancelled
Due to the absence of a great number of people, this week p2 call is being cancelled. Talk to you next week, PaScaL ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] +1 for Brian de Alwis on rt.equinox.incubator by Pascal Rapicault
Pascal Rapicault voted: +1 +1 Voting summary: http://portal.eclipse.org/ ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] List of installable units or log - using p2 director to automate Subclipse, M2eclipse, and M2eclipse Extra for OpenMRS developers
[...] Somewhat oddly (to me) the relevant reference to the Update Manager API on Galileo: http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/api/org/eclipse/update/core/package-summary.html is marked as deprecated. I don't easily see a replacement API present, so, I am left to wonder, as I need to support Galileo in my implementation - am I missing something or is the Update Manager API indeed the best/only way to install features from a plug-in in Galileo? p2 has been around since 3.4 and it had a provisional API in 3.4 and 3.5. It is only since 3.6 that p2 has an official API. I definitely recommend staying out of update manager API and use the p2 provisional API instead. Though in different packages, the final APIs are really close to the provisional one and once you will have figured out how to make your installer work on 3.6, making it work in only a few package and method renames away. The other important point is that the metadata is compatible so you would not have to generate two sets of information. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] threadpool?
Don't you want to use the jobs API? On 2010-09-03, at 11:57 AM, Scott Lewis wrote: Hi Folks, Is there a threadpool impl available in Equinox somewhere? (non-internal packages of course). Thanks, Scott ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] How to compile within the terminal?
This tool is called tycho and is on the verge to move to eclipse. I've been using it recently and it is close to trivial to setup a build. You can find a good overall description from http://www.slideshare.net/kthoms/maven-3-tycho You can also find a relatively active user community on http://software.2206966.n2.nabble.com/Tycho-Users-f3053503.html HTH PaScaL On 2010-06-07, at 8:28 AM, Simone Gianni wrote: Hi Gabriel, I've never experimented with your case specifically, but I know Maven can compile and package Eclipse PDE plugin/OSGi bundles from command line. I've found an EclipseCon 2008 presentation by Carlos Sanchez ( search maven eclipse bundles on google), second and third part of the presentation deals with creating OSGi bundles with Maven and as a conseguence Eclipse PDE plugins. Hope this helps, Simone 2010/6/1 Gabriel Batistuta batistutagabrielf...@gmail.com It's not what I want. Actually, I'm able to do this with eclipse as your tutorial explains. Now, I want to do this in the terminal. It means that I want compile each bundle,or other think, in my terminal with a command line. Do you understand? Thank, Gab 2010/6/1 Wolfgang Werner wolfgang.wer...@gmail.com Gabriel, WRT your post on equinox-dev: I am not sure whether I understand you correctly, but if you want to build a headless (i.e. non-GUI) standalone OSGi based product, you may want to look at this tutorial: http://blog.wolfgang-werner.net/building-on-equinox-and-restlet-1/ Besides restlet integration, it describes all steps needed so build such a product, from bundle creation to the export of the final product. HTH, Wolfgang ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] API Addition
Done. On 2010-04-11, at 6:44 PM, Jeff McAffer wrote: Great. I did not recall this as one of the approved ones. Would be good to note that in the bug for consistency and transparency. Thanks for the info. Jeff On 2010-04-11, at 4:15 PM, Pascal Rapicault pas...@sonatype.com wrote: During last week team meeting, we went through all the API bugs to discuss as a team their relevance, impact, and get a verbal approval from the PMC thus streamlining the release of the API for all parties involved. This particular bug was part of this discussion, and it needs to be noted that it represents a loss of functionality over what we had in the past. On 2010-04-11, at 2:51 PM, Jeff McAffer wrote: I don't recall a API change proposal or approval for this. The bug cited does have the API keyword but no approvals AFAICT. Was that done somewhere else? Jeff On 2010-04-09, at 8:52 PM, Pascal Rapicault wrote: In order to address bug 303990 - metarequirement seems broken, I have had to add two new constants in the IProvisioningAgent INSTALLER_AGENT and INSTALLER_PROFILEID. This was a necessity because otherwise the director application was not able to install metarequirements. PaScaL___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] API Addition
In order to address bug 303990 - metarequirement seems broken, I have had to add two new constants in the IProvisioningAgent INSTALLER_AGENT and INSTALLER_PROFILEID. This was a necessity because otherwise the director application was not able to install metarequirements. PaScaL___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Fwd: p2 API changes
Begin forwarded message: From: Pascal Rapicault pas...@sonatype.com Date: April 8, 2010 2:54:36 PM EDT To: cross-project-issues-dev-requ...@eclipse.org, Equinox development mailing list equinox-dev@eclipse.org, P2 developer discussions p2-...@eclipse.org Subject: p2 API changes In an effort to clean things up a bit. p2 has released the following low impact changes: Bug 305334 - Added new methods on MetadataFactory to align with the terminology used in other parts of the API. == background == During 3.6, some p2 concepts got renamed however we had missed to rename some methods on the MetadataFactory class. this change introduces new methods matching the new terminology and deprecate the old one. After next week I build we will remove the deprecated methods from the MetadataFactory API. == impact == Low, because only very advanced p2 users would use these methods Bug 304538 - Marked IInstallableUnitPatch#getApplicabilityScope() with at @noreference == background == We did not had the time to review the implication of exposing this concept in the API. We are marking it @noreference because we will change this in the next release. == impact == null. Nobody refers to this method except the p2 planner. Bug 299506 - Marked IRequirementChange#equals() with @noreference ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Application scheduling
Does our implementation of the application model persist (across VM restarts) the application that have been scheduled? PaScaL___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Can't attend call today
I won't be able to attend today's call because of a conflicting meeting. PaScaL___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] FYI: OSGi services and extension registry
Neil just made this a way to bridge the extension registry and the services: http://github.com/njbartlett/Extensions2Services___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] +1 for Scott Lewis on rt.equinox.incubator
+1 +1 Voting summary: http://portal.eclipse.org/ ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Alternatives to OSGI
I have read about people using Android in residential gateways. It is of course at a much lower level since it is an OS. [equinox-dev] Alternatives to OSGI David Conde to: 'Equinox development mailing list' 09/02/2009 08:34 AM Sent by: equinox-dev-boun...@eclipse.org Please respond to Equinox development mailing list Hi, I am evaluating different alternatives to OSGI framework but I have not found anything which could face to OSGI at all, do you know another frameworks which could be used as Residencial Gateways different to OSGI? I have read something about Jigsaw but I think is more general purpose focused than OSGI, but I did not find anything more. Thank you in advance David___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: pic31702.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Question on Profiles / p2 and standalone Osgi
The result of the installation of an IU that contains a bundle should result in the bundle to be listed in the bundles.info in the configuration/org.eclipse.equinox.simpleconfigurator/bundles.info. To cause the system to re-consider this list of bundles, you need to grab the Configurator service (provided by the simpleconfigurator bundle) and call applyConfiguration(). This is how the apply changes dialog is implemented. | | From: | | ---| |Chase Wolfinger chase.wolfin...@gmail.com | ---| | | To:| | ---| |Equinox development mailing list equinox-dev@eclipse.org | ---| | | Cc:| | ---| |equinox-dev-boun...@eclipse.org | ---| | | Date: | | ---| |05/14/2009 11:07 PM | ---| | | Subject: | | ---| |Re: [equinox-dev] Question on Profiles / p2 and standalone Osgi | ---| Hi Pascal - I am currently running with the following VM arguments: -Declipse.p2.data.area=C:\p2agent\p2 -Declipse.p2.profile=ExampleProfile I have written a simple debug plugin that pulls the current SELF IProfile and it comes back ExampleProfile. I have then pulled the IU(s) and they all come back from the profile query. So it seems like the p2 framework is installed correctly. Once this is done is there a best practices to reconcile the currently running bundles with the profile IUs - similar to an apply changes? or is it better to iterate through the IUs and install the OSGI bundles directly ? On Thu, May 14, 2009 at 8:28 PM, Pascal Rapicault pascal_rapica...@ca.ibm.com wrote: Hi, The profile is not here to instruct p2 what should be installed in your system. Instead you need to think of it as the record of what has been installed. I think that the issue you are encountering is a tooling one where when you are starting an application from within Eclipse, no corresponding profile is created and as such any subsequent p2 operation can be problematic (https://bugs.eclipse.org/bugs/show_bug.cgi?id=250126). There is currently two work around: 1) You create a profile for your installation using the admin ui. When you start your application from within the IDE you set the vm arg eclipse.p2.data.area to point at the p2 folder that contains the profile you are running (e.g. -Declipse.p2.data.area=/Users/Pascal/Downloads/eclipse/p2/). You may also want to specify the ID of your profile by setting eclipse.p2.profile as a vm arg (e.g. eclipse.p2.profile=PlatformProfile) 2) You write a bundle that looks around in the running system, generates metadata representing it, and fake up an installation into a profile (you can find most of the code for generation in the publisher bundle). This bundle would be running in the application started. This is really a HACK and should not be used in real systems. I'm giving you this approach as a way for you to progress, but using this in a real product would result in not guaranteeing unicity of metadata, would not allow you to manage all the external files
Re: [equinox-dev] 3.6 target milestone and version created for Equinox
I was actually wondering if we should not use the train name instead (e.g. for 3.5. it would have been something like Galileo,GalileoM1, et...) | | From: | | -| |Thomas Watson tjwat...@us.ibm.com | -| | | To:| | -| |Equinox development mailing list equinox-dev@eclipse.org, p2-...@eclipse.org | -| | | Date: | | -| |04/20/2009 03:53 PM | -| | | Subject: | | -| |[equinox-dev] 3.6 target milestone and version created for Equinox | -| We are heading into the latest milestone before the release candidates of 3.5. I have create a new 3.6 target milestone and version in bugzilla for bugs that we want defer to the next release. Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] P2 and the transport layer
This was one of the goal of using ECF. I'm happy to see someone realizing this :-) We have not tried this ourselves, but we have been changing the implementation of the http transport without changing the p2 code so this should work (maybe some work needs to be done in ECF around error codes). Scott Lewis, ECF lead, is lurking here but you may want to contact the ECF community directly on ecf-...@eclipse.org HTH PaScaL | | From: | | ---| |J B moa...@gmail.com | ---| | | To:| | ---| |equinox-dev@eclipse.org | ---| | | Date: | | ---| |04/08/2009 12:47 PM | ---| | | Subject: | | ---| |[equinox-dev] P2 and the transport layer | ---| Can anyone provide me better details to the current state of the transport layer for P2? We need to support provisioning, but our only available transport layer will be JMS. If the P2 transport layer is based on ECF, I was hoping it might be possible to simply plugin a JMS transport and ride on top of that. Any thoughts? Thanks! Birch ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Re: 3.5M6 missing eclipse directory
PDE has support for n - 2 but has never guaranteed forward compatibility. You can always try to run the p2.repo2runnable task to make the repo in a format against which you can run. | | From: | | -| |Christian Campo christian.ca...@gmail.com | -| | | To:| | -| |Equinox development mailing list equinox-dev@eclipse.org | -| | | Date: | | -| |03/17/2009 04:15 AM | -| | | Subject: | | -| |Re: [equinox-dev] Re: 3.5M6 missing eclipse directory | -| So what do you do, if you use a 3.4 build process to build a 3.5 target ? which isnt so unusual 2009/3/16 Chris Aniszczyk z...@eclipsesource.com 2009/3/16 Christian Campo christian.ca...@gmail.com Some more stupid questions.:-) Ok so that .zip as I learned looks that way because it is p2-ized. No idea how to tell the PDE Build to use it, but that explains it at least. In 3.5M5, PDE Build added support to use p2 repos as a target: http://download.eclipse.org/eclipse/downloads/drops/S-3.5 M5-200902021535/eclipse-news-M5.html#PDE See the 'repoBaseLocation' and 'transformedRepoLocation' properties. Cheers, -- Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465 http://twitter.com/eclipsesource | http://twitter.com/caniszczyk ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev -- christian campo (gmail.com)___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Standard way to daemonize Equinox
system property | | From: | | -| |Jason van Zyl ja...@maven.org | -| | | To:| | -| |Equinox development mailing list equinox-dev@eclipse.org | -| | | Date: | | -| |03/14/2009 06:41 PM | -| | | Subject: | | -| |Re: [equinox-dev] Standard way to daemonize Equinox | -| On 14-Mar-09, at 2:47 PM, Pascal Rapicault wrote: It is complementary. - console and port will give unsecure remote access to the fwk. - ignoreApp will cause the fwk to not look for an application on startup and thus avoid an entry in the log - noExit will prevent the fwk to exit. My JSW entry now looks like: wrapper.app.parameter.1=org.eclipse.equinox.launcher.Main wrapper.app.parameter.2=-ignoreApp wrapper.app.parameter.3=-noExit But but the container is still exiting. I'm using eclipse-equinox-3.4.zip bundle. Is ignoreApp an option or a system property? graycol.gifJason van Zyl ---03/14/2009 04:19:56 PM---On 14-Mar-09, at 10:16 AM, Pascal Rapicault wrote: This seems reasonable. If you are not running a ecblank.gif ecblank.gif From: Jason van Zyl ja...@maven.org ecblank.gif ecblank.gif To: Equinox development mailing list equinox-dev@eclipse.org ecblank.gif ecblank.gif Date: 03/14/2009 04:19 PM ecblank.gif ecblank.gif Subject:Re: [equinox-dev] Standard way to daemonize Equinox On 14-Mar-09, at 10:16 AM, Pascal Rapicault wrote: This seems reasonable. If you are not running an application, you want to specify the system property eclipse.ignoreApp to true. You can find all the OSGi options at http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html That seems to be down. Is specifying this system property different then port listening trickery? PaScaL graycol.gifJason van Zyl ---03/14/2009 12:25:08 PM---Hi, After puttering around for a few minutes I found something for ecblank.gif ecblank.gif From: Jason van Zyl ja...@maven.org ecblank.gif ecblank.gif To: equinox-dev@eclipse.org ecblank.gif ecblank.gif
Re: [equinox-dev] Change log for Equinox versions?
We don't carry such a log. The easiest would be for you to run a query against all the bugs closed as fix in 3.5 (don't forget to include the milestones). For the framework, if I'm not wrong, it would be something like: https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advancedshort_desc_type=allwordssubstrshort_desc=classification=RTproduct=Equinoxcomponent=Frameworktarget_milestone=3.5target_milestone=3.5+M1target_milestone=3.5+M2target_milestone=3.5+M3target_milestone=3.5+M4target_milestone=3.5+M5target_milestone=3.5+M6target_milestone=3.5+M7target_milestone=3.5+RC1target_milestone=3.5+RC2target_milestone=3.5+RC3target_milestone=3.5+RC4long_desc_type=allwordssubstrlong_desc=bug_file_loc_type=allwordssubstrbug_file_loc=status_whiteboard_type=allwordssubstrstatus_whiteboard=keywords_type=allwordskeywords=bug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDresolution=FIXEDemailtype1=substringemail1=emailtype2=substringemail2=bugidtype=includebug_id=votes=chfieldfrom=chfieldto=Nowchfieldvalue=cmdtype=doitorder=Reuse+same+sort+as+last+timefield0-0-0=nooptype0-0-0=noopvalue0-0-0= HTH | | From: | | -| |Alin Dreghiciu adreghi...@gmail.com | -| | | To:| | -| |Equinox - General equinox-dev@eclipse.org | -| | | Date: | | -| |03/02/2009 06:59 PM | -| | | Subject: | | -| |[equinox-dev] Change log for Equinox versions? | -| Hi guys, I was looking for but I could not figure out a change log (what's new) for Equinox versions in general and Equinox 3.4.2 in particular. Can you guys point me to such a resource? -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. http://www.codedragons.com - New Energy for Projects - Great People working on Great Projects at Great Places ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Equinox P2 on Eclipse 3.3.0
I don't foresee any major problem in doing this, however again we have not tried this. As for generating metadata, take a look at http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_metadata_generator.html | | From: | | -| |Prodan Daniela daniela.pro...@gmail.com | -| | | To:| | -| |equinox-dev@eclipse.org | -| | | Date: | | -| |02/17/2009 01:24 PM | -| | | Subject: | | -| |[equinox-dev] Equinox P2 on Eclipse 3.3.0 | -| Hello, From this modified install you will have to generate metadata and then use the p2 director to create a brand new install. Is there a link where can I find more information about how I can do this? Is it possible that P2 will not be compatible with older versions of Eclipse( 3.4). Thank you, Daniela -- We have never tried that. You will need to take the following p2 plug-ins from 3.4 (org.eclipse.equinox.p2.*, org.eclipse.equinox.frameworkadmin*, org.eclipse.equinox.simpleconfigurator*) and also take the 3.4 copy of the former org.eclipse.update* plug-ins. From this modified install you will have to generate metadata and then use the p2 director to create a brand new install. HTH, PaScaL Inactive hide details for Prodan Daniela ---02/16/2009 12:33:38 PM---Hello, My name is Daniela Prodan and I am from Romania. I Prodan Daniela ---02 /16/2009 12:33:38 PM---Hello, My name is Daniela Prodan and I am from Romania. I have a question that is From: Prodan Daniela daniela.pro...@x To:equinox-...@xxx Date: 02/16/2009 12:33 PM Subject: [equinox-dev] Equinox P2 on eclipse 3.3.0 Hello, My name is Daniela Prodan and I am from Romania. I have a question that is related to the Equinox P2 update manager. Equinox P2 can be integrated in Eclipse 3.3.0 ? If it can, how can this be done? I suppose I should rebuild it with Eclipse SDK 3.3.0? Any information is useful. Thank you, Daniela Prodan ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Equinox self-diagnosis
See my comment on the bug. | | From: | | -| |Krzysztof Daniel krzysztof_dan...@pl.ibm.com | -| | | To:| | -| |equinox-dev@eclipse.org | -| | | Date: | | -| |02/04/2009 09:37 AM | -| | | Subject: | | -| |[equinox-dev] Equinox self-diagnosis | -| Hello everybody, I am working on bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=174515. [ErrorHandling] Plugins that can't load do not notify to the user. This bug is quite difficult as it is necessary to address end rcp users and also Eclipse developers. I'd like to introduce some kind of self-diagnosis mechanism, in which a feature could tell, that it could not be loaded successfully because one or more required plugins (or other features) are missing. For details please refer to the comment 27 in the bug. I need to know how can I get from Equinox list of installed and resolved plug-ins grouped by features? I mean something similar to Help-Installation Information-Installed Software, but with underlying plugins? Regards, Chris -- Christopher Daniel Technical Support Engineer Eclipse Support Center IBM Software Group ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] P2 modyfing - reducing GUI
Please send this question to the p2-dev ML, where more of the p2 developers are listening. Thx | | From: | | --| |rafal1...@poczta.onet.pl | --| | | To:| | --| |equinox-dev@eclipse.org | --| | | Date: | | --| |01/14/2009 10:47 AM | --| | | Subject: | | --| |[equinox-dev] P2 modyfing - reducing GUI | --| Hello Issue with provisioning system equinox.p2 reused in my RCP application: Is it posible to reduce functionality for Update system such as presented on linked site ( http://www.richclient2.eu/2007_07_03/updates-for-rcp-dummies-restricting-the-update-manager/ ) Where can i find a list of properties to set to reduce or modyfie (especialy reduce GUI to provide auto-Update without user control or withn minimal user integration) in plugin.properties or plugin_customization.ini 4example I've mada a change in imported plugin provisioningPrefPage = Install/Update TEST and in application it succesed the change in preferences page. In this way I would like to made some modyfication to adjust P2 update manager's Thanks for any advice ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] a future with futures
The code seems to be relatively well isolated, why not create a new bundle for it? | | From: | | -| |Scott Lewis sle...@eclipsesource.com | -| | | To:| | -| |Equinox development mailing list equinox-dev@eclipse.org | -| | | Date: | | -| |01/14/2009 07:17 PM | -| | | Subject: | | -| |[equinox-dev] a future with futures | -| On this E4 enhancement request: https://bugs.eclipse.org/bugs/show_bug.cgi?id=253777 there has been a long and fruitful discussion about supporting asynchronous programming (for E4 as well as other projects including ECF, p2, DSDP) by adding the concept of a 'future' to Equinox. Various designs have been proposed, and I think that there has been a good amount of convergence recently...i.e. see comment 121: https://bugs.eclipse.org/bugs/show_bug.cgi?id=253777#c121 for a recent summary. I would like to request that this contribution be considered for addition to Equinox for the Galileo release cycle. If there is more/other that I can do as a contributor please let me know. Scott ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] performance problems with Eclipse startup due to long DirectoryWatcher.poll() (25 minutes!)
This action has be happen in the startup thread because otherwise the bundles from the dropins folder will not be in your running instance... UM was doing the same except that it did not had to do the metadata generation. But it may be that most of p2 operations are currently slow for large installations Please open a bug with facts Also note that all p2 related communication should take place on the p2-dev ML. PaScaL | | From: | | -| |Jacek Pospychała jacek.pospych...@cs.put.poznan.pl | -| | | To:| | -| |Equinox development mailing list equinox-dev@eclipse.org | -| | | Date: | | -| |01/09/2009 10:34 AM | -| | | Subject: | | -| |Re: [equinox-dev] performance problems with Eclipse startup due to long DirectoryWatcher.poll() (25 minutes!) | -| Thanks Pascal and Simon. What concerns me is that this slow operation happens in p2.reconciler.dropins Activator.start(), actually stopping the startup of whole Eclipse app. My other problem is that this is not the only case. There are other, not yet clear or documented enough that cause slow startup - I'm trying to get stacktraces for them too. But it may be that most of p2 operations are currently slow for large installations. So assuming the the metadata write is slowing us so much, could it be realized as a separate thread, or moved out from Activator.start() sequence? Do you think it has any sense, or maybe there are other services that depend on the metadata written to disk? Jacek Pascal Rapicault pisze: Some bug fixes got made in 3.4.2, but the main problem is that p2 has to generate metadata on the fly which is a non trivial operation IO-wise. I would recommend you to generate p2 metadata for all of those 3000 bundles and install them properly using the p2 director. One bug report about performance of the reconciler is https://bugs.eclipse.org/bugs/show_bug.cgi?id=251561 Inactive hide details for Jacek Pospychała ---01/08/2009 11:19:42 AM---Hi I have an Eclipse 3.4.1 install (of ~3000 plug-ins),Jacek Pospychała ---01/08/2009 11:19:42 AM---Hi I have an Eclipse 3.4.1 install (of ~3000 plug-ins), that's starting for From: Jacek Pospychała jacek.pospych...@cs.put.poznan.pl To: equinox-dev@eclipse.org Date: 01/08/2009 11:19 AM Subject: [equinox-dev] performance problems with Eclipse startup due to long DirectoryWatcher.poll() (25 minutes!) Hi I have an Eclipse 3.4.1 install (of ~3000 plug-ins), that's starting for about 25minutes. Most of this time is spent in org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start() calling (indirectly) DirectoryWatcher.poll(). Looking at several coredumps collected during this startup time it seems that all threads wait() or sleep() and only Start Level Event Dispatcher is working. All the time this thread is writing some XML. (See it's stacktrace below) Is this expected behaviour? What XML is actually written? I also notice that p2 directory has about 600mb. I was looking for bugs with similar stack traces, but with no luck so far - should I open new? thanks Jacek stacktrace: 3XMTHREADINFO Start Level Event Dispatcher TID:0x4274C100, j9thread_t:0x0001BA70, state:CW, prio=5 3XMTHREADINFO1(native thread ID:0x890, native priority:0x5, native policy:UNKNOWN) 4XESTACKTRACE