Re: [gemini-dev] Gemini Maven repo layout file permissions

["Kissner, Juergen" <juergen.kissner@xxxxxxx>]

Hi Glyn,

Thanks a lot for your investigations into the matter.

I managed to upload the DBAccess maven artifacts to /download.eclipse.org/gemini/mvn/. However, I was not able to do the git part (no shell access).

It looks as if the Blueprint artifacts have ended up in the wrong directory: mvn/org/org/eclipse/blueprint. That would correspond to a group ID org.org.eclipse.gemini.blueprint. 

Another question concerns the choice of the Blueprint group ID : As far as I can seem, yours would be org.eclipse.gemini.blueprint. That would not be consistent with other Gemini sub projects. I had suggested both options end of last year [1], [2]. The majority decided for the org.eclipse.gemini for the group ID [1]. Personally, I do not have strong preferences, but it would be nice to be consistent amongst the Gemini projects.

Juergen

[1] http://wiki.eclipse.org/Gemini/Meetings/Minutes_Dec_4_2012
[2] http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00815.html







-----Original Message-----
From: gemini-dev-bounces@xxxxxxxxxxx [mailto:gemini-dev-bounces@xxxxxxxxxxx] On Behalf Of Glyn Normington
Sent: Dienstag, 12. Februar 2013 13:34
To: gemini-dev@xxxxxxxxxxx
Subject: [gemini-dev] Gemini Maven repo layout file permissions

I am in the process of publishing a milestone of Gemini Blueprint and when I came to upload the Maven repo to the Gemini Maven repo (for the first time), I noticed that there were some issues.

Firstly, the git repository seemed out of date, so I deleted it and recreated it. But then I twigged that I am the owner of the git repository, so I changed the file permissions to give the group rt.gemini write access. We'll have to wait for someone else to try to commit to the repo before we know this has worked.

Secondly, the Maven repo layout looked wrong and its file permissions were non-uniform.

For instance, take the directory /home/data/httpd/download.eclipse.org/gemini/mvn/org/eclipse. I would expect to see just a gemini subdirectory (unless I don't understand Maven repo layout, which is equally likely!). Instead I found:

> ls -l
total 20
drwxr-xr-x 7 vgeorgieva common    4096 2012-07-21 09:08 gemini
drwxr-sr-x 4 mkeith     rt.gemini 4096 2012-11-15 15:20 org.eclipse.gemini.jpa
drwxr-sr-x 3 mkeith     rt.gemini 4096 2012-02-01 09:31 org.eclipse.gemini.jpa.samples
drwxrwxr-x 4 cfrost     common    4096 2012-12-07 06:20 org.eclipse.gemini.management
drwxr-xr-x 4 vgeorgieva common    4096 2012-11-26 12:52 org.eclipse.gemini.naming

with the following contents in gemini/

> ls -l gemini/
total 20
drwxr-xr-x 4 vgeorgieva common 4096 2012-12-20 15:48 org.eclipse.gemini.web
drwxr-xr-x 4 vgeorgieva common 4096 2012-12-20 15:48 org.eclipse.gemini.web.core
drwxr-xr-x 4 vgeorgieva common 4096 2012-12-20 15:49 org.eclipse.gemini.web.extender
drwxr-xr-x 4 vgeorgieva common 4096 2012-12-20 15:49 org.eclipse.gemini.web.test
drwxr-xr-x 4 vgeorgieva common 4096 2012-12-20 15:50 org.eclipse.gemini.web.tomcat

So I'm not sure that the whole Gemini Maven repo is usable as a Maven repo.

Regards,
Glyn
_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev