dash-dev http://dev.eclipse.org/mhonarc/lists/dash-dev/maillist.html dash-dev en-us Fri, 03 May 2013 16:31:04 GMT Fri, 03 May 2013 16:31:04 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) dash-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/dash-dev/maillist.html [dash-dev] Project meta data is out of date for technology.dash http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01373.html Wayne, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * The date for release "portal M3" is in the past, but the release is not... Wayne, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * The date for release "portal M3" is in the past, but the release is not marked as completed. If it is completed, it should be marked as completed; if it has been postponed, it should be given a new target date. * There is no next/future release of this project. All Eclipse projects must have a "next release" planned and scheduled. ]]> Fri, 05 Apr 2013 04:00:25 GMT http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01373.html emo@xxxxxxx (portal on behalf of emo) Re: [dash-dev] repo.eclipse.org maven instance testing http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01372.html I am going with limited knowledge of how Maven works, so please bear with me.

Our thoughts on limiting publishing to Hudson only is that Hudson provides us with a mechanism to provide a central set of credentials that are not exposed to the general public.  Just like signins.

If there is a way to allow multiple people to publish artifacts securely from various locations without having to store committer credentials in plaintext files, or giving everyone the keys to the entire repo, then I (and Thanh) are all ears.

Denis


On 02/23/2013 11:26 AM, Jesse McConnell wrote:

Why are you adding this restriction to maven usage while binaries built to be signed by the official Eclipse Foundation key can be built on whatever virus and compromised machines you wish to be uploaded and signed as official binaries?

cheers,
jesse


]]> Mon, 25 Feb 2013 14:12:36 GMT http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01372.html denis.roy@xxxxxxx (Denis Roy) Re: [dash-dev] repo.eclipse.org maven instance testing http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01371.html For reference to my previous comment, see Denis's comment here:Âhttps://bugs.eclipse.org/bugs/show_bug.cgi?id=354756#c26

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx


On Sat, Feb 23, 2013 at 10:26 AM, Jesse McConnell <jesse.mcconnell@xxxxxxxxx> wrote:

Why are you adding this restriction to maven usage while binaries built to be signed by the official Eclipse Foundation key can be built on whatever virus and compromised machines you wish to be uploaded and signed as official binaries?

cheers,
jesse

]]> Sat, 23 Feb 2013 16:27:49 GMT http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01371.html jesse.mcconnell@xxxxxxx (Jesse McConnell) Re: [dash-dev] repo.eclipse.org maven instance testing http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01370.html Why are you adding this restriction to maven usage while binaries built to be signed by the official Eclipse Foundation key can be built on whatever virus and compromised machines you wish to be uploaded and signed as official binaries? cheers,jesse
Why are you adding this restriction to maven usage while binaries built to be signed by the official Eclipse Foundation key can be built on whatever virus and compromised machines you wish to be uploaded and signed as official binaries?

cheers,
jesse
]]> Sat, 23 Feb 2013 16:26:22 GMT http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01370.html jesse.mcconnell@xxxxxxx (Jesse McConnell) Re: [dash-dev] repo.eclipse.org maven instance testing http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01369.html how could we deploy already existing releases ? Could we do that by deploying from build.eclipse.org ? No, when I discussed with Webmasters we decided that you need to use Hudson in order to deploy. If there's a different use case I'll have to discuss wi...
On 23/02/13 08:17 AM, Matthias Sohn wrote:
2013/2/23 Thanh Ha <thanh.ha@xxxxxxxxxxx>
Hi Everyone,

Per discussion in Bug 394792 [1] regarding credential security. We decided to limit deployment to the Eclipse Hudson instance which means if you want to deploy you will need to configure a Hudson job. I updated the wiki page with instructions on how I deployed the CBI maven plugins using Hudson [2]. If any Hudson experts know of better ways to configure the job please feel free to leave a suggestion.

[1] http://bugs.eclipse.org/394792
[2] http://wiki.eclipse.org/Services/Nexus#Deploying_artifacts_to_repo.eclipse.org

how could we deploy already existing releases ? Could we do that by deploying 

No, when I discussed with Webmasters we decided that you need to use Hudson in order to deploy. If there's a different use case I'll have to discuss with Webmasters again.

Are the already existing releases Maven repos? If so maybe I can copy them over if you point me to where they are.


Thanh
]]> Sat, 23 Feb 2013 14:29:51 GMT http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01369.html thanh.ha@xxxxxxx (Thanh Ha) Re: [dash-dev] repo.eclipse.org maven instance testing http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01368.html 2013/2/23 Thanh Ha &lt;thanh.ha@xxxxxxxxxxx&gt; how could we deploy already existing releases ? Could we do that by deploying&#xC2;from build.eclipse.org ?-- Matthias&#xC2; 2013/2/23 Thanh Ha <thanh.ha@xxxxxxxxxxx>
Hi Everyone,

Per discussion in Bug 394792 [1] regarding credential security. We decided to limit deployment to the Eclipse Hudson instance which means if you want to deploy you will need to configure a Hudson job. I updated the wiki page with instructions on how I deployed the CBI maven plugins using Hudson [2]. If any Hudson experts know of better ways to configure the job please feel free to leave a suggestion.

[1] http://bugs.eclipse.org/394792
[2] http://wiki.eclipse.org/Services/Nexus#Deploying_artifacts_to_repo.eclipse.org

how could we deploy already existing releases ? Could we do that by deployingÂ

--
MatthiasÂ
]]> Sat, 23 Feb 2013 13:17:10 GMT http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01368.html matthias.sohn@xxxxxxx (Matthias Sohn) Re: [dash-dev] repo.eclipse.org maven instance testing http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01367.html Hi Everyone, Per discussion in Bug 394792 [1] regarding credential security. We decided to limit deployment to the Eclipse Hudson instance which means if you want to deploy you will need to configure a Hudson job. I updated the wiki page with instructions ... Hi Everyone,
Per discussion in Bug 394792 [1] regarding credential security. We decided to limit deployment to the Eclipse Hudson instance which means if you want to deploy you will need to configure a Hudson job. I updated the wiki page with instructions on how I deployed the CBI maven plugins using Hudson [2]. If any Hudson experts know of better ways to configure the job please feel free to leave a suggestion.

[1] http://bugs.eclipse.org/394792
[2] http://wiki.eclipse.org/Services/Nexus#Deploying_artifacts_to_repo.eclipse.org

Thanh

]]> Sat, 23 Feb 2013 00:53:24 GMT http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01367.html thanh.ha@xxxxxxx (Thanh Ha) Re: [dash-dev] repo.eclipse.org maven instance testing http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01366.html Hi Everyone, Some big changes I need to make today. Using &quot;eclipse&quot; and &quot;eclipse-snapshots&quot; was not a good idea as aggregate groups of the entire repo after all. It conflicts with the &quot;Eclipse Project&quot; space so we need to change this to give &quot;eclipsequot; ... Hi Everyone,
Some big changes I need to make today. Using "eclipse" and "eclipse-snapshots" was not a good idea as aggregate groups of the entire repo after all. It conflicts with the "Eclipse Project" space so we need to change this to give "eclipse" back to the "Eclipse Project".

The new proposal is that we will use more generically named groups:

all repo releases: https://repo.eclipse.org/content/groups/releases
all repo snapshots: https://repo.eclipse.org/content/groups/snapshots


The eclipse group will now be given to the "Eclipse Project".

eclipse (group): https://repo.eclipse.org/content/groups/eclipse/
eclipse-releases: https://repo.eclipse.org/content/repositories/eclipse-releases/
eclipse-snapshots: https://repo.eclipse.org/content/repositories/eclipse-snapshots/


If you've been using these URLs in your projects you will need to change them.

Sorry for the inconvenience,


Thanh

]]> Thu, 21 Feb 2013 15:13:15 GMT http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01366.html thanh.ha@xxxxxxx (Thanh Ha) Re: [dash-dev] repo.eclipse.org maven instance testing http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01365.html That makes good sense. I am +1 for this change. +1 to keep release and snapshot repositories strictly separated I think mixing snapshot and release repositories doesn't make sense -- Matthias _______________________________________________ dash-dev mai...
Hi Everyone,

repo.eclipse.org has been modified with the suggested changes.

releases only: https://repo.eclipse.org/content/groups/eclipse/
snapshots only: https://repo.eclipse.org/content/groups/eclipse-snapshots/


A scheduled task has also been configured to cleanup snapshots older than 30-days on a weekly basis.


Thanh


On 19/02/2013 6:25 PM, Matthias Sohn wrote:
2013/2/20 Thanh Ha <thanh.ha@xxxxxxxxxxx>
On 19/02/13 06:05 PM, Alex Blewitt wrote:
You should also have a group which is 'only releases' and 'only snapshots'. In fact, I'd argue that the main 'eclipse' one only contain releases and have 'eclipse-snapshots' as a separate one, because there's rarely a good reason to mix both releases and snapshots in the same repository.

That makes good sense. I am +1 for this change.

+1 to keep release and snapshot repositories strictly separated
 
Would it be good to have a mixed one also maybe "eclipse-all" which aggregates the 2 groups for those who want both?

I think mixing snapshot and release repositories doesn't make sense 

--
Matthias


_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev

]]> Wed, 20 Feb 2013 02:20:16 GMT http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01365.html thanh.ha@xxxxxxx (Thanh Ha) Re: [dash-dev] repo.eclipse.org maven instance testing http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01364.html I'm not sure what you mean by retention time. Can you explain this setting? Is it the "Not Found Cache TTL"? Usually old snapshot builds (e.g. older than 1 month) are purged in order to limit disk consumption of the Nexus server. -- Matthias ____________...
Thanks Matthias,

That helps. I was able to find the setting for this as well. I think 1 month (30 days) is reasonable, I will set it to 30 days unless anyone has any objections.


Thanh


On 19/02/13 06:28 PM, Matthias Sohn wrote:
2013/2/19 Thanh Ha <thanh.ha@xxxxxxxxxxx>
Hi Matthias,
On 19/02/13 04:23 PM, Matthias Sohn wrote:
What's the retention time for snapshot repositories ?
I'm not sure what you mean by retention time. Can you explain this setting? Is it the "Not Found Cache TTL"? 

Usually old snapshot builds (e.g. older than 1 month) are purged in order to limit
disk consumption of the Nexus server.

--
Matthias


_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev

]]> Tue, 19 Feb 2013 23:32:41 GMT http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01364.html thanh.ha@xxxxxxx (Thanh Ha)