Re: [cross-project-issues-dev] Layout and licenses
Frankly, that one was only on my just curious list. We have a long and distinguished list of fair exceptions. One of the things that I'm going to add into the new project management stuff is the ability to specify bundle names (and patterns) owned by a project. Wayne On 06/06/2012 09:23 AM, David M Williams wrote: I can help with the rephraseengine one ... your guess is correct, and its odd name has been documented before: https://bugs.eclipse.org/bugs/show_bug.cgi?id=330403 https://bugs.eclipse.org/bugs/show_bug.cgi?id=330403 (Of course, you can re-open the issue if you'd like ... but ... it seemed like one of those fair exceptions, to me). From: Wayne Beaton wa...@eclipse.org To: cross-project-issues-dev@eclipse.org, Date: 06/06/2012 09:17 AM Subject: [cross-project-issues-dev] Layout and licenses Sent by: cross-project-issues-dev-boun...@eclipse.org Hey folks. I'm going through the layout and licenses reports today. I've already opened a couple of bugs regarding missing about files and am just starting into the licenses. These issues need to be addressed before any reviews can be declared successful. Note that these are very basic requirements that are independent of participation in the simultaneous release. If you need help, please ask. There a Gemini JPA bundle in the repository. I'm also seeing a GEF3D bundle. Why? If these bundles are in the repository, shouldn't the owning projects be Juno particpants? Or did I miss a memo? org.eclipse.gemini.jpa_1.0.99.v20120225-1927.jar org.eclipse.gef3d_0.8.1.v20120528-0244.jar Who owns these bundles: org.eclipse.rephraserengine.core_8.0.0.201205300709.jar org.eclipse.rephraserengine.ui_8.0.0.201205300709.jar (I'll guess tools.ptp.photran based on the version number). Wayne -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Layout and licenses
I don't know anything about why gemini.jpa or gef3d are getting added to the repo, but this made me think about your question: If these bundles are in the repository, shouldn't the owning projects be Juno particpants? I don't know the correct answer, but it strikes me as odd that we allow non-eclipse third party dependencies to be added to the repo, but when it comes to a dependency on another project's bundles we force the other owning project to participate fully in the release. What if the project does not want to participate? What if there is an IP acceptable alternative (non-eclipse) project that could be used? Would we prefer the use of that non-eclipse third party technology over the eclipse one simple because the owning eclipse project does not want to participate in the Juno release? It seems to me that such cases should be treated as any other third party dependency and we should not force the owning project to participate in the release. Tom From: Wayne Beaton wa...@eclipse.org To: cross-project-issues-dev@eclipse.org, Date: 06/06/2012 08:17 AM Subject:[cross-project-issues-dev] Layout and licenses Hey folks. I'm going through the layout and licenses reports today. I've already opened a couple of bugs regarding missing about files and am just starting into the licenses. These issues need to be addressed before any reviews can be declared successful. Note that these are very basic requirements that are independent of participation in the simultaneous release. If you need help, please ask. There a Gemini JPA bundle in the repository. I'm also seeing a GEF3D bundle. Why? If these bundles are in the repository, shouldn't the owning projects be Juno particpants? Or did I miss a memo? org.eclipse.gemini.jpa_1.0.99.v20120225-1927.jar org.eclipse.gef3d_0.8.1.v20120528-0244.jar Who owns these bundles: org.eclipse.rephraserengine.core_8.0.0.201205300709.jar org.eclipse.rephraserengine.ui_8.0.0.201205300709.jar (I'll guess tools.ptp.photran based on the version number). Wayne -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev inline: graycol.gifinline: ecblank.gif___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Layout and licenses
Hi, Just to shed some lights into the issue. Gyrex requires Gemini JPA for its EclipseLink JPA integration. Gemini JPA does not provide a p2 repository. Thus, it's in the Gyrex repo which is part of Juno. Any ideas how to proceed? Migrating to some external library just because Gemini isn't participating in Juno seems wrong to me. -Gunnar Am 06.06.2012 15:48, schrieb Thomas Watson: I don't know anything about why gemini.jpa or gef3d are getting added to the repo, but this made me think about your question: If these bundles are in the repository, shouldn't the owning projects be Juno particpants? I don't know the correct answer, but it strikes me as odd that we allow non-eclipse third party dependencies to be added to the repo, but when it comes to a dependency on another project's bundles we force the other owning project to participate fully in the release. What if the project does not want to participate? What if there is an IP acceptable alternative (non-eclipse) project that could be used? Would we prefer the use of that non-eclipse third party technology over the eclipse one simple because the owning eclipse project does not want to participate in the Juno release? It seems to me that such cases should be treated as any other third party dependency and we should not force the owning project to participate in the release. Tom Inactive hide details for Wayne Beaton ---06/06/2012 08:17:55 AM---Hey folks. I'm going through the layout and licenses reportsWayne Beaton ---06/06/2012 08:17:55 AM---Hey folks. I'm going through the layout and licenses reports today. From: Wayne Beaton wa...@eclipse.org To: cross-project-issues-dev@eclipse.org, Date: 06/06/2012 08:17 AM Subject: [cross-project-issues-dev] Layout and licenses Hey folks. I'm going through the layout and licenses reports today. I've already opened a couple of bugs regarding missing about files and am just starting into the licenses. These issues need to be addressed before any reviews can be declared successful. Note that these are very basic requirements that are independent of participation in the simultaneous release. If you need help, please ask. There a Gemini JPA bundle in the repository. I'm also seeing a GEF3D bundle. Why? If these bundles are in the repository, shouldn't the owning projects be Juno particpants? Or did I miss a memo? org.eclipse.gemini.jpa_1.0.99.v20120225-1927.jar org.eclipse.gef3d_0.8.1.v20120528-0244.jar Who owns these bundles: org.eclipse.rephraserengine.core_8.0.0.201205300709.jar org.eclipse.rephraserengine.ui_8.0.0.201205300709.jar (I'll guess tools.ptp.photran based on the version number). Wayne -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore _Eclipse Projects_ http://www.eclipse.org/projects___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Layout and licenses
Hi Surely a release consists of on-train projects + Orbit, so if they're not on-train they should frozen be in Orbit. Regards Ed Willink On 06/06/2012 17:13, Gunnar Wagenknecht wrote: Hi, Just to shed some lights into the issue. Gyrex requires Gemini JPA for its EclipseLink JPA integration. Gemini JPA does not provide a p2 repository. Thus, it's in the Gyrex repo which is part of Juno. Any ideas how to proceed? Migrating to some external library just because Gemini isn't participating in Juno seems wrong to me. -Gunnar Am 06.06.2012 15:48, schrieb Thomas Watson: I don't know anything about why gemini.jpa or gef3d are getting added to the repo, but this made me think about your question: If these bundles are in the repository, shouldn't the owning projects be Juno particpants? I don't know the correct answer, but it strikes me as odd that we allow non-eclipse third party dependencies to be added to the repo, but when it comes to a dependency on another project's bundles we force the other owning project to participate fully in the release. What if the project does not want to participate? What if there is an IP acceptable alternative (non-eclipse) project that could be used? Would we prefer the use of that non-eclipse third party technology over the eclipse one simple because the owning eclipse project does not want to participate in the Juno release? It seems to me that such cases should be treated as any other third party dependency and we should not force the owning project to participate in the release. Tom Inactive hide details for Wayne Beaton ---06/06/2012 08:17:55 AM---Hey folks. I'm going through the layout and licenses reportsWayne Beaton ---06/06/2012 08:17:55 AM---Hey folks. I'm going through the layout and licenses reports today. From: Wayne Beatonwa...@eclipse.org To: cross-project-issues-dev@eclipse.org, Date: 06/06/2012 08:17 AM Subject: [cross-project-issues-dev] Layout and licenses Hey folks. I'm going through the layout and licenses reports today. I've already opened a couple of bugs regarding missing about files and am just starting into the licenses. These issues need to be addressed before any reviews can be declared successful. Note that these are very basic requirements that are independent of participation in the simultaneous release. If you need help, please ask. There a Gemini JPA bundle in the repository. I'm also seeing a GEF3D bundle. Why? If these bundles are in the repository, shouldn't the owning projects be Juno particpants? Or did I miss a memo? org.eclipse.gemini.jpa_1.0.99.v20120225-1927.jar org.eclipse.gef3d_0.8.1.v20120528-0244.jar Who owns these bundles: org.eclipse.rephraserengine.core_8.0.0.201205300709.jar org.eclipse.rephraserengine.ui_8.0.0.201205300709.jar (I'll guess tools.ptp.photran based on the version number). Wayne -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore _Eclipse Projects_ http://www.eclipse.org/projects___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev - No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2178 / Virus Database: 2433/5051 - Release Date: 06/06/12 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
