On 10/08/2012 11:23 AM, Francesco Chicchiriccò wrote:
Hi,
I've just noticed an open staging repository on Nexus
(org.apache.cocoon-054) opened by Thorsten last Sep 11th.
Could it be removed?
Regards.
Sorry, did not read the mail the first time correctly and Javier just
pointed it out to me
On 10/10/2012 16:07, Thorsten Scherler wrote:
On 10/08/2012 11:23 AM, Francesco Chicchiriccò wrote:
Hi,
I've just noticed an open staging repository on Nexus
(org.apache.cocoon-054) opened by Thorsten last Sep 11th.
Could it be removed?
Regards.
Sorry, did not read the mail the first time
On 10/10/2012 04:10 PM, Francesco Chicchiriccò wrote:
On 10/10/2012 16:07, Thorsten Scherler wrote:
On 10/08/2012 11:23 AM, Francesco Chicchiriccò wrote:
Hi,
I've just noticed an open staging repository on Nexus
(org.apache.cocoon-054) opened by Thorsten last Sep 11th.
Could it be removed
Hi,
I've just noticed an open staging repository on Nexus
(org.apache.cocoon-054) opened by Thorsten last Sep 11th.
Could it be removed?
Regards.
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
repository/name
urlscpexe://people.apache.org/home/jheymans/public_html/cocoon-staging-repository/url
/repository
I guess that it isn't the best idea to use Jorg's home directory as staging
repository, is it? But what would be a better location for this on
people.apache.org
On 12/3/06, Reinhard Poetz [EMAIL PROTECTED] wrote:
...Some time ago somebody mentioned that the mv command is atomic. Is this
information correct?...
on a Linux or unixish system, mv uses the rename() system call which
is atomic (i.e. intermediate states are not visible), so
mv somefile
Reinhard Poetz wrote:
Currently we have following configuration in our root POM:
repository
idcocoon-staging-repo/id
namestaging release repository/name
urlscpexe://people.apache.org/home/jheymans/public_html/cocoon-staging-repository/url
/repository
I guess that it isn't the best
location of our sync repo as the
current solution /home/jheymans/public_html/cocoon-staging-repository is of
course just a temporary solution. This way we only have to deploy all the pom
artifacts just once again.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
that the cocoon-staging-repository is completly empty?
pwd
/x1/home/jheymans/public_html/cocoon-staging-repository
ls -lsa
total 4
2 drwxrwxrwx 2 jheymans jheymans 512 Aug 8 10:08 .
2 drwxrwxrwx 3 jheymans jheymans 512 Aug 8 10:08 ..
My understanding was that the staging repo is a mirror
Reinhard Poetz wrote:
I tried it and run into the problem[1] that when I refer to the already
released Cocoon parent artifact (org.apache.cocoon:cocoon:1), the old
value for the distribution repository is taken. Because of this I
accidently deployed the batik parent pom
Reinhard Poetz wrote:
My understanding was that the staging repo is a mirror of everything
under org/apache/cocoon and when we really want to release, we call a
script that copies our changes to the public sync repo or if we want to
roll back, we copy back the changes by copying the content
Jorg Heymans wrote:
Reinhard Poetz wrote:
My understanding was that the staging repo is a mirror of everything
under org/apache/cocoon and when we really want to release, we call a
script that copies our changes to the public sync repo or if we want to
roll back, we copy back the changes by
Jorg Heymans wrote:
...The only thing i'm still unsure about is how to do the sync between the
zone and people.a.o, rsync might not work too well given the metadata
that's involved
Note that, IMHO, you shouldn't rsync directly into the people.a.o
directories that are rsynced to the
Bertrand Delacretaz wrote:
I think the safe way is to first rsync from the zone to a temporary
location on people.a.o, which is on the same filesystem than the final
location, then do a move (mv), which is atomic, to the final location
on people.a.o.
-Bertrand (I'm not being paranoid, am
Jorg Heymans wrote:
Just agreed on this with Reinhard off-list, i'll make the required changes.
ok this is done now. I hope i got the permissions right (g+w and o+w on
all dirs involved, including my home dir).
Can someone please give it a spin ?
Regards
Jorg
Jorg Heymans wrote:
Jorg Heymans wrote:
Just agreed on this with Reinhard off-list, i'll make the required changes.
ok this is done now. I hope i got the permissions right (g+w and o+w on
all dirs involved, including my home dir).
Can someone please give it a spin ?
I'll give it a try
Reinhard Poetz wrote:
(i'll get started on setting up that staging repository now)
great, desperatly needed!
I've setup a staging repo on the zones,
http://cocoon.zones.apache.org/cocoon-staging-release-repository/. It's
configured in the root pom so any release:perform action
Jorg Heymans wrote:
I've setup a staging repo on the zones,
http://cocoon.zones.apache.org/cocoon-staging-release-repository/. It's
configured in the root pom so any release:perform action will be going
there instead of people.a.o.
The idea is that we can verify releases from there *before* we
Reinhard Poetz wrote:
The only thing i'm still unsure about is how to do the sync between the
zone and people.a.o, rsync might not work too well given the metadata
that's involved.
Why do you think so? As long there is no other process that manipulates
Cocoon artifacts in the Apache
19 matches
Mail list logo
