[
http://jira.codehaus.org/browse/MAVENUPLOAD-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115246
]
Manos Batsis commented on MAVENUPLOAD-1806:
-------------------------------------------
Two out of three scripts rsync ok. After several hours sarissa in not in repo1
yet.
Checked out the committed scripts, you have correctly modified the GROUP_DIR in
two of them (thanks!). However, in gr.abiss.js.sarissa.sh [1] The line:
GROUP_DIR=gr/abiss/js/sarissa/
should be
GROUP_DIR=gr/abiss/js/
as sarissa is the artifactId, I think that's why it does not rsync properly.
[1]
http://svn.apache.org/viewvc/maven/archiva/tools/trunk/maven-meeper/src/bin/synchronize/m2-sync/conf/gr.abiss.js.sarissa.sh?content-type=text%2Fplain&view=co
Thanks,
Manos
> rsync request: gr.abiss
> ------------------------
>
> Key: MAVENUPLOAD-1806
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1806
> Project: maven-upload-requests
> Issue Type: Bug
> Reporter: Manos Batsis
> Assignee: Carlos Sanchez
> Attachments: gr.abiss.js.sarissa.sh, gr.abiss.md4j.sh,
> gr.abiss.mvn.plugins.maven-jstools-plugin.sh, gr.abiss.sh
>
>
> Hello,
> This is an rsync request. You can verify I'm (Manos Batsis) a team member in
> all projects of dev.abiss.gr by checking out the m2 team report for each
> project (I'm also a co-fouder of Abiss.gr), for example [1]. Our releases
> repo is at [2] and our OS project list at [3]. Anyway, have not done this
> before so tried to work out a basic, non-ssh version of the script
> (attached), hope it works :-)
> [1] http://dev.abiss.gr/md4j/team-list.html
> [2] http://dev.abiss.gr/m2repo/releases
> [3] http://dev.abiss.gr
> Thanks,
> Manos
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
