You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repository@apache.org by Reinhard Poetz <re...@apache.org> on 2006/08/03 15:33:45 UTC
Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
The Cocoon project has released a couple of artifacts to
m2-ibiblio-rsync-repository on people.apache.org. We kindly ask you to sync this
with the ibiblio repository.
Thanks!
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Carlos Sanchez <ca...@apache.org>.
done, will be there in 4 hours
On 8/3/06, Reinhard Poetz <re...@apache.org> wrote:
>
> The Cocoon project has released a couple of artifacts to
> m2-ibiblio-rsync-repository on people.apache.org. We kindly ask you to sync this
> with the ibiblio repository.
>
> Thanks!
>
> --
> Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
>
> {Software Engineering, Open Source, Web Applications, Apache Cocoon}
>
> web(log): http://www.poetz.cc
> --------------------------------------------------------------------
>
>
>
>
>
> ___________________________________________________________
> Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Staging Repository
Posted by Jorg Heymans <jh...@domek.be>.
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 (org.apache.cocoon:batik:1) to
> the official Apache sync repo.
>
Yes you should've deployed our new root pom first and waited for the
sync to maven central before deploying any child blocks.
> Any ideas how to override the distribution repository from command line
> or do we really have to deploy all our pom artifacts just to propagate
> the new location?
mmm interesting problem... deploying a new root pom potentially triggers
a cascade of module pom deployments. We could get around this by making
all poms extend the root pom directly, instead of passing via their
parent module poms. This would work if we don't intend to use the module
poms for anything else but to aggregate the module components.
I'll need to think about this.
Jorg
Re: Staging Repository
Posted by Reinhard Poetz <re...@apache.org>.
Reinhard Poetz wrote:
> 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 tommorrow and let you know whether it works for me.
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 (org.apache.cocoon:batik:1) to the official Apache sync repo.
Any ideas how to override the distribution repository from command line or do we
really have to deploy all our pom artifacts just to propagate the new location?
If there is no way we should find the final 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
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: Staging Repository
Posted by Reinhard Poetz <re...@apache.org>.
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 tommorrow and let you know whether it works for me.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: Staging Repository
Posted by Reinhard Poetz <re...@apache.org>.
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 copying the content of the sync
>> repo over our staging repo (we should be able to do this on specific
>> paths, but that's a detail).
>>
>
> this would work, even though my understanding was that staging->release
> repo is a one way process. You deploy to staging and after verification
> you _move_ the files simply to release. If you get it wrong, just zap
> staging and try again. I just talked with jdcasey on #maven about this,
> he said that we should be ok with overwriting metadata.xml as the
> <versions> element in there is only used for snapshot resolution.
> Release artifacts are looked up directly.
ahh, ok. Then there is no need to for keeping our staging repo in sync with the
public sync repo.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Staging Repository
Posted by Jorg Heymans <jh...@domek.be>.
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 of the sync
> repo over our staging repo (we should be able to do this on specific
> paths, but that's a detail).
>
this would work, even though my understanding was that staging->release
repo is a one way process. You deploy to staging and after verification
you _move_ the files simply to release. If you get it wrong, just zap
staging and try again. I just talked with jdcasey on #maven about this,
he said that we should be ok with overwriting metadata.xml as the
<versions> element in there is only used for snapshot resolution.
Release artifacts are looked up directly.
> Have you already written the necessary scripts?
nope.
Jorg
Re: Staging Repository
Posted by Reinhard Poetz <re...@apache.org>.
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 ?
Is it on purpose 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 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 of the sync repo over our staging repo
(we should be able to do this on specific paths, but that's a detail).
Have you already written the necessary scripts?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: Staging Repository
Posted by Jorg Heymans <jh...@domek.be>.
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
Re: Staging Repository
Posted by Jorg Heymans <jh...@domek.be>.
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 I?)
not at all :)
Just agreed on this with Reinhard off-list, i'll make the required changes.
Jorg
Re: Re: Staging Repository
Posted by Bertrand Delacretaz <bd...@apache.org>.
> 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 final repositories: if you do this
and a sync is happening from people.a.o to the final destination at
the same time, you might end up with an incomplete set of files at the
final destination (hope I'm being clear ;-)
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 I?)
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Reinhard Poetz <re...@apache.org>.
Jorg Heymans wrote:
> On 8/5/06 3:11 PM, in article C0FA658D.33E0%jh@domek.be, "Jorg Heymans"
> <jh...@domek.be> wrote:
>
>> Actually, no. I forgot the -s settings.xml when doing mvn cocoon:deploy
>> jetty6:run
>>
>> Now I get java.lang.NoClassDefFoundError:
>> org/apache/avalon/framework/CascadingRuntimeException
>>
>> It seems that some avalon jars are missing , I'll have a look.
>>
>
> Right I got it working now.
>
> It turned out that during archetype build, svn.a.o was not available as a
> repository. The avalon and excalibur poms are still located there so we need
> to have that repo available during build if we want to pick up the
> dependencies transitively.
Why don't we get some build failure?
> There are two solutions, either make the pom.xml in the archetype (the one
> that the user ends up with) extend the cocoon root pom, or put svn.a.o in a
> repositories section in that same pom. It doesn't really matter for the
> moment, so just to get it working I declared the repo in pom.xml - this way
> the user still has the option of inheriting from his own poms should he wish
> to do so.
> I've rereleased the archetype as 1.0.0-M2.
thanks! I wonder if whether naming our releases "milestones" makes much sense
considering this case ... I have to say that I'm not perfectly happy with it. Do
we have better alternatives?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Jorg Heymans <jh...@domek.be>.
Reinhard Poetz wrote:
>
> I've released 1.0.0-M3 now. Can somebody please check if I did it right?
>
looks good to me.
Jorg
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Jorg Heymans <jh...@domek.be>.
Reinhard Poetz wrote:
>
> I've released 1.0.0-M3 now. Can somebody please check if I did it right?
>
i'll have a look tonight.
> thanks! I wonder if whether naming our releases "milestones" makes much sense
> considering this case ... I have to say that I'm not perfectly happy with it. Do
> we have better alternatives?
milestones come before release candidates, i'ld say the terminology is
OK here (even though we're mainly using the milestones to practice our
maven build skills)
> I haven't set back /src/main/resources/archetype-resources/pom.xml so
> that it points to snapshots again. I think that it doesn't make much
> sense to point to snapshots in an archetype. Or does somebody have the
> need to create Cocoon projects that are based on snapshots?
the archetype should only depend on stable releases yes.
Jorg
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Reinhard Poetz <re...@apache.org>.
Reinhard Poetz wrote:
> Jorg Heymans wrote:
>> I've rereleased the archetype as 1.0.0-M2.
>
> Unfortunatly the archetype creates a pom with SNAPSHOT dependencies.
> This has to be fixed with another release. We really need a staging
> repository ...
>
I've released 1.0.0-M3 now. Can somebody please check if I did it right?
I haven't set back /src/main/resources/archetype-resources/pom.xml so that it
points to snapshots again. I think that it doesn't make much sense to point to
snapshots in an archetype. Or does somebody have the need to create Cocoon
projects that are based on snapshots?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Reinhard Poetz <re...@apache.org>.
Carsten Ziegeler wrote:
> Our getting started guide states
> "You need to build the trunk of Cocoon in order to get your local
> repositories filled with the necessary artifacts."
>
> I guess we can remove this as m1 is released to the repos, right?
yes
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Carsten Ziegeler <cz...@apache.org>.
Our getting started guide states
"You need to build the trunk of Cocoon in order to get your local
repositories filled with the necessary artifacts."
I guess we can remove this as m1 is released to the repos, right?
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: Staging Repository
Posted by Jorg Heymans <jh...@domek.be>.
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 m2-sync repo *directly* and circumvents
> the staging repo, I don't see any problems.
OK i see now, it will work if nobody circumvents the staging repo.
> How can we trigger the sync from cocoon.zones.apache.org given that we
> shouldn't/mustn't store private ssh keys on this potentially unsecure
> machine? Wouldn't it be a better option to have our staging repo on
> people.apache.org too?
i didn't know the zone is potentially unsecure. If we are allowed to
create people.a.o/repo/cocoon-staging-release-repository then that's ok
as well (and probably easier to access for all).
Jorg
Re: Staging Repository
Posted by Reinhard Poetz <re...@apache.org>.
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 sync to
> people.a.o and give the green to repository@a.o to upload to maven central.
>
> 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 m2-sync repo *directly* and circumvents the staging
repo, I don't see any problems.
How can we trigger the sync from cocoon.zones.apache.org given that we
shouldn't/mustn't store private ssh keys on this potentially unsecure machine?
Wouldn't it be a better option to have our staging repo on people.apache.org too?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Staging Repository (was Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository)
Posted by Jorg Heymans <jh...@domek.be>.
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 will be going
there instead of people.a.o.
The idea is that we can verify releases from there *before* we sync to
people.a.o and give the green to repository@a.o to upload to maven central.
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.
Jorg
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Reinhard Poetz <re...@apache.org>.
Jorg Heymans wrote:
> Reinhard Poetz wrote:
>> Jorg Heymans wrote:
>>> I've rereleased the archetype as 1.0.0-M2.
>> Unfortunatly the archetype creates a pom with SNAPSHOT dependencies.
>> This has to be fixed with another release. We really need a staging
>> repository ...
>>
>
> woops sorry about that :-(
don't worry
> (i'll get started on setting up that staging repository now)
great, desperatly needed!
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Jorg Heymans <jh...@domek.be>.
Reinhard Poetz wrote:
> Jorg Heymans wrote:
>> I've rereleased the archetype as 1.0.0-M2.
>
> Unfortunatly the archetype creates a pom with SNAPSHOT dependencies.
> This has to be fixed with another release. We really need a staging
> repository ...
>
woops sorry about that :-(
(i'll get started on setting up that staging repository now)
Jorg
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Reinhard Poetz <re...@apache.org>.
Jorg Heymans wrote:
> I've rereleased the archetype as 1.0.0-M2.
Unfortunatly the archetype creates a pom with SNAPSHOT dependencies. This has to
be fixed with another release. We really need a staging repository ...
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Jorg Heymans <jh...@domek.be>.
On 8/5/06 3:11 PM, in article C0FA658D.33E0%jh@domek.be, "Jorg Heymans"
<jh...@domek.be> wrote:
> Actually, no. I forgot the -s settings.xml when doing mvn cocoon:deploy
> jetty6:run
>
> Now I get java.lang.NoClassDefFoundError:
> org/apache/avalon/framework/CascadingRuntimeException
>
> It seems that some avalon jars are missing , I'll have a look.
>
Right I got it working now.
It turned out that during archetype build, svn.a.o was not available as a
repository. The avalon and excalibur poms are still located there so we need
to have that repo available during build if we want to pick up the
dependencies transitively.
There are two solutions, either make the pom.xml in the archetype (the one
that the user ends up with) extend the cocoon root pom, or put svn.a.o in a
repositories section in that same pom. It doesn't really matter for the
moment, so just to get it working I declared the repo in pom.xml - this way
the user still has the option of inheriting from his own poms should he wish
to do so.
I've rereleased the archetype as 1.0.0-M2.
Jorg
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Jorg Heymans <jh...@domek.be>.
On 8/5/06 2:07 PM, in article C0FA56BF.33D8%jh@domek.be, "Jorg Heymans"
<jh...@domek.be> wrote:
>> That's really great news! Did you test with an empty local repo?
>>
>
> Yep.
>
Actually, no. I forgot the -s settings.xml when doing mvn cocoon:deploy
jetty6:run
Now I get java.lang.NoClassDefFoundError:
org/apache/avalon/framework/CascadingRuntimeException
It seems that some avalon jars are missing , I'll have a look.
Jorg
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Jorg Heymans <jh...@domek.be>.
On 8/5/06 1:15 PM, in article 44D47DBC.9040103@apache.org, "Reinhard Poetz"
<re...@apache.org> wrote:
>> I get this as output for http://localhost:8888/blocks/myBlock/ :
>> com.mycompany:myBlock This is a message coming from a Spring bean.
>>
> That's really great news! Did you test with an empty local repo?
>
Yep.
>> Be aware though that the rsync from ibiblio to mirrors.dotsrc.org went
>> somehow wrong, compare [1] and [2]. For now I've disabled my mirror settings
>> and only tested from maven central , and given above results I'ld say it
>> works pretty well :)
>>
> good catch! I will have a look if there are more differences between ibiblio
> and mirrors.dotsrc.org.
You'ld expect subsequent rsyncs between central and its mirrors to pick this
up though - but somehow it doesn't, wierd.
Jorg
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Reinhard Poetz <re...@apache.org>.
Jorg Heymans wrote:
> On 8/5/06 10:40 AM, in article 44D4598B.5000703@apache.org, "Reinhard Poetz"
> <re...@apache.org> wrote:
>
>> Unfortunatly this comes for the M1 release too late because I fear that we
>> have some problems with the dependency resolution of at least one of our
>> released artifacts. I tested the block-archtetype and if I want to run the
>> created block after a cocoon:deploy, libraries are missing and the servlet
>> container stops with a ClassNotFoundException. If I do the same with the
>> M2-SNAPSHOT version of the block-archetype everything seems to be okay
>> although nothing has changed since the release.
>>
>
> I get this as output for http://localhost:8888/blocks/myBlock/ :
> com.mycompany:myBlock This is a message coming from a Spring bean.
That's really great news! Did you test with an empty local repo?
>> Could somebody try cocoon.zones.apache.org/daisy/documentation/g1/1159.html
>> and report back whether it works? Please don't use your usual local repository
>> but point to a new location in your Maven settings.xml so that there can't be
>> any side effects (I can't try it myself again as I only have a GPRS connection
>> over the weekend.)
>
> Be aware though that the rsync from ibiblio to mirrors.dotsrc.org went
> somehow wrong, compare [1] and [2]. For now I've disabled my mirror settings
> and only tested from maven central , and given above results I'ld say it
> works pretty well :)
good catch! I will have a look if there are more differences between ibiblio and
mirrors.dotsrc.org.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Jorg Heymans <jh...@domek.be>.
On 8/5/06 10:40 AM, in article 44D4598B.5000703@apache.org, "Reinhard Poetz"
<re...@apache.org> wrote:
> Unfortunatly this comes for the M1 release too late because I fear that we
> have some problems with the dependency resolution of at least one of our
> released artifacts. I tested the block-archtetype and if I want to run the
> created block after a cocoon:deploy, libraries are missing and the servlet
> container stops with a ClassNotFoundException. If I do the same with the
> M2-SNAPSHOT version of the block-archetype everything seems to be okay
> although nothing has changed since the release.
>
I get this as output for http://localhost:8888/blocks/myBlock/ :
com.mycompany:myBlock This is a message coming from a Spring bean.
> Could somebody try cocoon.zones.apache.org/daisy/documentation/g1/1159.html
> and report back whether it works? Please don't use your usual local repository
> but point to a new location in your Maven settings.xml so that there can't be
> any side effects (I can't try it myself again as I only have a GPRS connection
> over the weekend.)
Be aware though that the rsync from ibiblio to mirrors.dotsrc.org went
somehow wrong, compare [1] and [2]. For now I've disabled my mirror settings
and only tested from maven central , and given above results I'ld say it
works pretty well :)
Regards
Jorg
[1]
http://www.ibiblio.org/maven2/org/apache/cocoon/cocoon-22-archetype-block/1.
0.0-M1/
[2]
http://mirrors.dotsrc.org/maven2/org/apache/cocoon/cocoon-22-archetype-block
/1.0.0-M1/
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Reinhard Poetz <re...@apache.org>.
Jorg Heymans wrote:
> <re...@apache.org> wrote:
>> yes, that's IMO the way to go. Could some shell script guru set up the
>> necessary shell scripts for the sync process? What we need is two scripts on
>> people.apache.org:
>>
>> m2repo-to-private.sh [sub-directory]: Using this script you can set back a
>> particular module, e.g. cocoon-core: "m2repo-to-private.sh
>> org/apache/cocoon/cocoon-core"
>>
>> private-to-m2repo.sh: Using this script we sync our private repo with the
>> official m2 sync repository. After running this script we can ping
>> repository@apache to do the sync with the ibiblio repo.
>>
>> The only thing left is that we should make our private repository available
>> via http so that we can try out our releases locally.
>>
>
> What about the maven metadata.xml ? Isn't that one updated with each
> release?
AFAIU yes
> We should make sure that there is no risk of breaking something
> when we start playing with this ourselves. I'll ask for a second opinion on
> #maven. (but if you ask me, they should be the ones providing a more
> granular sync service in the first place)
yes, that would be even a better option. The only important point for me is that
we need the possibility to test our release before it is really published.
Unfortunatly this comes for the M1 release too late because I fear that we have
some problems with the dependency resolution of at least one of our released
artifacts.
I tested the block-archtetype and if I want to run the created block after a
cocoon:deploy, libraries are missing and the servlet container stops with a
ClassNotFoundException.
If I do the same with the M2-SNAPSHOT version of the block-archetype everything
seems to be okay although nothing has changed since the release.
Could somebody try cocoon.zones.apache.org/daisy/documentation/g1/1159.html and
report back whether it works? Please don't use your usual local repository but
point to a new location in your Maven settings.xml so that there can't be any
side effects (I can't try it myself again as I only have a GPRS connection over
the weekend.)
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Jorg Heymans <jh...@domek.be>.
On 8/4/06 8:08 PM, in article 44D38D12.8090705@apache.org, "Reinhard Poetz"
<re...@apache.org> wrote:
> Bertrand Delacretaz wrote:
>
>> Also, if a sync happens while you're uploading stuff, a half-finished release
>> will be published.
>>
>> This looks exactly like the mysterious build problems that Carsten and I were
>> chasing at ApacheCon, where he had different versions of some artifacts (from
>> another project, not Cocoon) than me in his maven cache, with the same
>> version numbers.
>>
>> I know little about how this all works, but maybe it would make sense to use
>> a staging area, outside of the synced directories, to create the release? And
>> move it to the "sync zone" when it's ready and checked.
>>
> yes, that's IMO the way to go. Could some shell script guru set up the
> necessary shell scripts for the sync process? What we need is two scripts on
> people.apache.org:
>
> m2repo-to-private.sh [sub-directory]: Using this script you can set back a
> particular module, e.g. cocoon-core: "m2repo-to-private.sh
> org/apache/cocoon/cocoon-core"
>
> private-to-m2repo.sh: Using this script we sync our private repo with the
> official m2 sync repository. After running this script we can ping
> repository@apache to do the sync with the ibiblio repo.
>
> The only thing left is that we should make our private repository available
> via http so that we can try out our releases locally.
>
What about the maven metadata.xml ? Isn't that one updated with each
release? We should make sure that there is no risk of breaking something
when we start playing with this ourselves. I'll ask for a second opinion on
#maven. (but if you ask me, they should be the ones providing a more
granular sync service in the first place)
Jorg
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Reinhard Poetz <re...@apache.org>.
Bertrand Delacretaz wrote:
> On 8/3/06, Jorg Heymans <jh...@domek.be> wrote:
>
>> ...It was just confirmed to me on repo@ that indeed the whole
>> m2-ibiblio-rsync-repository directory is synced for each synchronisation
>> request. So be aware of this, if you make a mistake during the release
>> and
>> you're unlucky (ie you just uploaded before the rsync kicked in) then
>> those
>> bad artifacts are on maven central and you'll have to re-release with new
>> version increment...
>
> Also, if a sync happens while you're uploading stuff, a half-finished
> release will be published.
>
> This looks exactly like the mysterious build problems that Carsten and
> I were chasing at ApacheCon, where he had different versions of some
> artifacts (from another project, not Cocoon) than me in his maven
> cache, with the same version numbers.
>
> I know little about how this all works, but maybe it would make sense
> to use a staging area, outside of the synced directories, to create
> the release? And move it to the "sync zone" when it's ready and
> checked.
yes, that's IMO the way to go. Could some shell script guru set up the necessary
shell scripts for the sync process? What we need is two scripts on
people.apache.org:
m2repo-to-private.sh [sub-directory]: Using this script you can set back a
particular module, e.g. cocoon-core:
"m2repo-to-private.sh org/apache/cocoon/cocoon-core"
private-to-m2repo.sh: Using this script we sync our private repo with the
official m2 sync repository. After running this script we can ping
repository@apache to do the sync with the ibiblio repo.
The only thing left is that we should make our private repository available via
http so that we can try out our releases locally.
WDOT?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 8/3/06, Jorg Heymans <jh...@domek.be> wrote:
> ...It was just confirmed to me on repo@ that indeed the whole
> m2-ibiblio-rsync-repository directory is synced for each synchronisation
> request. So be aware of this, if you make a mistake during the release and
> you're unlucky (ie you just uploaded before the rsync kicked in) then those
> bad artifacts are on maven central and you'll have to re-release with new
> version increment...
Also, if a sync happens while you're uploading stuff, a half-finished
release will be published.
This looks exactly like the mysterious build problems that Carsten and
I were chasing at ApacheCon, where he had different versions of some
artifacts (from another project, not Cocoon) than me in his maven
cache, with the same version numbers.
I know little about how this all works, but maybe it would make sense
to use a staging area, outside of the synced directories, to create
the release? And move it to the "sync zone" when it's ready and
checked.
-Bertrand
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Jorg Heymans <jh...@domek.be>.
On 8/3/06 3:37 PM, in article 44D1FC0F.2050205@apache.org, "Reinhard Poetz"
<re...@apache.org> wrote:
> Reinhard Poetz wrote:
>
>> The Cocoon project has released a couple of artifacts to
>> m2-ibiblio-rsync-repository on people.apache.org. We kindly ask you to sync
>> this with the ibiblio repository.
>>
>> Thanks!
>>
> Because of another sync request the artifacts that Jorg and I released last
> week have already been synced. Hence nothing speak against syncing the blocks
> released today.
It was just confirmed to me on repo@ that indeed the whole
m2-ibiblio-rsync-repository directory is synced for each synchronisation
request. So be aware of this, if you make a mistake during the release and
you're unlucky (ie you just uploaded before the rsync kicked in) then those
bad artifacts are on maven central and you'll have to re-release with new
version increment.
Jorg
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Brett Porter <br...@gmail.com>.
On 07/08/06, Wendy Smoak <ws...@gmail.com> wrote:
> We need a release staging repository. And then we need a reliable way
> to "promote" artifacts from staging to ibiblio-rsync, so that the
> repository metadata is correct.
I most definitely agree.
I am still interested in finding out "what goes wrong" though, as I'd
rather not have to leave it up to testers to find these sorts of
problems, even if it is first staged.
Cheers,
Brett
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Reinhard Poetz <re...@apache.org>.
Wendy Smoak wrote:
> On 8/6/06, Brett Porter <br...@gmail.com> wrote:
>
>> This isn't a matter of agreeing or disagreeing. If you put something
>> into the sync repository, it is the same as putting it into /dist/.
>> You've said "we've released these files, push them out to the world".
>>
>> It's becoming all too frequent that stuff gets pushed there and then
>> done again when a problem is noticed. I would like to see us
>> cataloguing the reasons this occurs and doing whatever we can to avoid
>> it in future.
>
> We need a release staging repository. And then we need a reliable way
> to "promote" artifacts from staging to ibiblio-rsync, so that the
> repository metadata is correct.
>
> I can't see how any project with a reasonably complex build could
> release straight to the rsynced repo. And definitely not the ones
> (like Struts) that use a test build stage, where a version is tagged
> and built, then voted on later. It's nice if everything works
> perfectly the first time, but all you have to do is forget to enable a
> profile, or have a connection drop, and you have to re-build.
>
> What do you think?
I agree here. We (the Cocoon community) came to the same conclusions.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Wendy Smoak <ws...@gmail.com>.
On 8/6/06, Brett Porter <br...@gmail.com> wrote:
> This isn't a matter of agreeing or disagreeing. If you put something
> into the sync repository, it is the same as putting it into /dist/.
> You've said "we've released these files, push them out to the world".
>
> It's becoming all too frequent that stuff gets pushed there and then
> done again when a problem is noticed. I would like to see us
> cataloguing the reasons this occurs and doing whatever we can to avoid
> it in future.
We need a release staging repository. And then we need a reliable way
to "promote" artifacts from staging to ibiblio-rsync, so that the
repository metadata is correct.
I can't see how any project with a reasonably complex build could
release straight to the rsynced repo. And definitely not the ones
(like Struts) that use a test build stage, where a version is tagged
and built, then voted on later. It's nice if everything works
perfectly the first time, but all you have to do is forget to enable a
profile, or have a connection drop, and you have to re-build.
What do you think?
--
Wendy
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Brett Porter <br...@gmail.com>.
On 05/08/06, Jorg Heymans <jh...@apache.org> wrote:
> > There's no guarantee of when it will be synced and I dont have the
> > time to sync different pieces so the right option is as you say
> > increase the version number and release again.
> > I don't think this is any different than other release processes.
> >
>
> I don't agree with above, but if that's how it is then so be it.
This isn't a matter of agreeing or disagreeing. If you put something
into the sync repository, it is the same as putting it into /dist/.
You've said "we've released these files, push them out to the world".
It's becoming all too frequent that stuff gets pushed there and then
done again when a problem is noticed. I would like to see us
cataloguing the reasons this occurs and doing whatever we can to avoid
it in future.
- Brett
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Carlos Sanchez <ca...@apache.org>.
On 8/5/06, Jorg Heymans <jh...@apache.org> wrote:
>
> On 8/3/06 9:41 PM, "Carlos Sanchez" <ca...@apache.org> wrote:
>
> > There's no guarantee of when it will be synced and I dont have the
> > time to sync different pieces so the right option is as you say
> > increase the version number and release again.
> > I don't think this is any different than other release processes.
> >
>
> I don't agree with above, but if that's how it is then so be it.
>
>
> On a different note, comparing
> http://mirrors.dotsrc.org/maven2/org/apache/cocoon/cocoon-22-archetype-block
> /1.0.0-M1/ with
> http://www.ibiblio.org/maven2/org/apache/cocoon/cocoon-22-archetype-block/1.
> 0.0-M1/ , it seems that something went wrong with the mirror
> synchronisation. Any ideas on how to bring the dotsrc mirror up to date ?
>
no idea, they mirror from ibiblio
>
> Jorg
>
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Jorg Heymans <jh...@apache.org>.
On 8/3/06 9:41 PM, "Carlos Sanchez" <ca...@apache.org> wrote:
> There's no guarantee of when it will be synced and I dont have the
> time to sync different pieces so the right option is as you say
> increase the version number and release again.
> I don't think this is any different than other release processes.
>
I don't agree with above, but if that's how it is then so be it.
On a different note, comparing
http://mirrors.dotsrc.org/maven2/org/apache/cocoon/cocoon-22-archetype-block
/1.0.0-M1/ with
http://www.ibiblio.org/maven2/org/apache/cocoon/cocoon-22-archetype-block/1.
0.0-M1/ , it seems that something went wrong with the mirror
synchronisation. Any ideas on how to bring the dotsrc mirror up to date ?
Jorg
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Carlos Sanchez <ca...@apache.org>.
There's no guarantee of when it will be synced and I dont have the
time to sync different pieces so the right option is as you say
increase the version number and release again.
I don't think this is any different than other release processes.
On 8/3/06, Jorg Heymans <jh...@domek.be> wrote:
>
>
>
> On 8/3/06 3:37 PM, in article 44D1FC0F.2050205@apache.org, "Reinhard Poetz"
> <re...@apache.org> wrote:
>
> >> The Cocoon project has released a couple of artifacts to
> >> m2-ibiblio-rsync-repository on people.apache.org. We kindly ask you to sync
> >> this with the ibiblio repository.
>
> > Because of another sync request the artifacts that Jorg and I released last
> > week have already been synced. Hence nothing speak against syncing the blocks
> > released today.
>
>
> Woosh !!
>
> Carlos, is the complete apache m2-release-repository sync'ed upon each
> synchronisation request? Wouldn't a more prudent approach be to sync only
> the requested project, or even artifact? Is this technically doable?
>
> Here's why for example: during the release process on Monday evening I
> realized I had made a mistake and removed some of the produced artifacts in
> m2-ibiblio-sync-repository in order to redo the release.
> Now had the full sync occurred before I removed them then we would've been
> in trouble, and the only correct thing then to do would've been to increment
> the version number, release again and deal with the hassle of users
> downloading the bad artifacts and asking why it's not working ...
>
> Thoughts?
>
> Jorg
>
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Jorg Heymans <jh...@domek.be>.
On 8/3/06 3:37 PM, in article 44D1FC0F.2050205@apache.org, "Reinhard Poetz"
<re...@apache.org> wrote:
>> The Cocoon project has released a couple of artifacts to
>> m2-ibiblio-rsync-repository on people.apache.org. We kindly ask you to sync
>> this with the ibiblio repository.
> Because of another sync request the artifacts that Jorg and I released last
> week have already been synced. Hence nothing speak against syncing the blocks
> released today.
Woosh !!
Carlos, is the complete apache m2-release-repository sync'ed upon each
synchronisation request? Wouldn't a more prudent approach be to sync only
the requested project, or even artifact? Is this technically doable?
Here's why for example: during the release process on Monday evening I
realized I had made a mistake and removed some of the produced artifacts in
m2-ibiblio-sync-repository in order to redo the release.
Now had the full sync occurred before I removed them then we would've been
in trouble, and the only correct thing then to do would've been to increment
the version number, release again and deal with the hassle of users
downloading the bad artifacts and asking why it's not working ...
Thoughts?
Jorg
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Reinhard Poetz <re...@apache.org>.
Reinhard Poetz wrote:
>
> The Cocoon project has released a couple of artifacts to
> m2-ibiblio-rsync-repository on people.apache.org. We kindly ask you to
> sync this with the ibiblio repository.
>
> Thanks!
Because of another sync request the artifacts that Jorg and I released last week
have already been synced. Hence nothing speak against syncing the blocks
released today.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository
Posted by Carlos Sanchez <ca...@apache.org>.
done, will be there in 4 hours
On 8/3/06, Reinhard Poetz <re...@apache.org> wrote:
>
> The Cocoon project has released a couple of artifacts to
> m2-ibiblio-rsync-repository on people.apache.org. We kindly ask you to sync this
> with the ibiblio repository.
>
> Thanks!
>
> --
> Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
>
> {Software Engineering, Open Source, Web Applications, Apache Cocoon}
>
> web(log): http://www.poetz.cc
> --------------------------------------------------------------------
>
>
>
>
>
> ___________________________________________________________
> Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride