Re: [cross-project-issues-dev] [HIPP] Visibility of Hudson configuration for anonymous users
On 01/09/2014 12:00 PM, Mikaël Barbero mikael.barb...@gmail.com wrote: To be sure I understand, you mean that there is something like a private key in your job configuration? IMHO, I don't think it is safe to rely on Hudson privacy settings to protect such a thing. It's not a private key but a complete test suite. Neither the job configuration _nor_ workspace and console log must be publicly accessible. It's basically all or nothing depending on whether you have signed the NDA. M. ___ 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] Documentation on Gerrit at Eclipse
On 10/07/2013 03:30 PM, Lars Vogel wrote: Hi Wayne, not sure I follow your reasoning. Someone how want to contribute via Gerrit is a contributor IMHO. Why not add information about the Gerrit usage to http://www.eclipse.org/contribute/? Best regards, Lars 2013/10/7 Wayne Beaton wa...@eclipse.org The /contribute page is for contributors; linking to a page that describes how to set up Gerrit would be inappropriate. How about links to: http://wiki.eclipse.org/Development_Resources/Contributing_via_Git If the page needs more for Gerrit, then I recommend we augment it. WDYT? Wayne On 10/07/2013 08:04 AM, Lars Vogel wrote: +1 for adding a link to the Gerrit wiki from http://www.eclipse.org/contribute/ 2013/10/7 Mickael Istria mist...@redhat.com Hi Lars, all, That's indeed a clear documentation, it would make much sense to have something similar from the main Eclipse How to contribute pages. I just noticed that none of the pages linked from http://www.eclipse.org/contribute/ have a reference to Gerrit, which is for many project the recommended workflow. I guess it could directly contain a link to http://wiki.eclipse.org/Gerrit . WDYT? Can this discussion please be move to a bug? Thanks Markus ___ 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] Has Java 5 Platform support been discontinued?
On 09/04/2013 01:54 PM, Lars Vogel wrote: It looks to me that some org.eclipse.ui.* plug-ins require an BREE update in this case. I think a plug-in cannot require a lower Java version than a plug-in which it requires as dependency. SWT is a special case as it has no plug-in dependencies. For example org.eclipse.ui.view defined a BREE of J2SE-1.4. org.eclipse.ui defines a BREE of J2SE-1.3. But both depend on org.eclipse.core.runtime which currently defines J2SE-1.5 (should that be JavaSE-1.6 according to this discussion?). Why increase the BREE of bundle X if its dependency Y requires a higher BREE? One might chose to replace its dependency Y with one Y' that has a lower BREE. E.g. I might decide to replace the current org.eclipse.core.runtime bundle with an older version that still works with a lower BREE. M. ___ 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] Kepler is GO!
On 06/26/2013 03:53 PM, Tom Schindl wrote: Now this repo misses at least org.eclipse.ecf.provider.filetransfer.httpclient which was in the repo at this location at least until yesterday! For the record/future reference see https://bugs.eclipse.org/411737 M. ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
