You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Nathan Bubna <nb...@gmail.com> on 2008/07/07 20:42:47 UTC
velocity-site sucks
Ok, in a fit of procrastinating what i should really work on this
morning, i thought i'd try and do a quick update of the site to show
the Tools 2.0-beta1 release, and thus ensure i can update the site on
my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
Unfortunately, i can't build the site tools. It looks like the
velocity-site-news plugin is not keeping pace with plexus:
...
C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
symbol : class ReaderFactory
location: package org.codehaus.plexus.util
...
now, this was just a matter of telling the pom to use some older
version of plexus and in theory i shouldn't even need to have to site
stuff all working on my computer, but i feel better about checking
stuff in if i can try it locally. so, i tweaked the
velocity-site-news-plugin pom, got the site tools to all build and was
able to go to the site directory and run the site target successfully.
but then, the site:run target failed. frustrated i decided to go
ahead and check in my changes and just try building and deploying the
site from velocity.zones.apache.org. I followed the instructions and
all seemed to go well until the build_velocity_site.sh script failed
when trying to actually deploy the updated site:
[INFO] [site:deploy]
scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
Using private key: /export/home/velocity/.ssh/id_rsa
Executing command: /bin/bash -c 'ssh -i
/export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
nbubna@people.apache.org "mkdir -p /w
ww/velocity.apache.org/."'
Permission denied (publickey,keyboard-interactive).
scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnecting
scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code 255 - Permission denied (publickey,keyboard-interactive).
this is far from the first time i've seen this. in fact, i recall
spending much time fighting this same error in the past. i can't even
remember if i succeeded though. either way, i'm sick of the maven
site building headaches. what should be a fairly simple task has been
an ordeal *for YEARS now*! the current process is brittle, unwieldy
and worst of all, unmaintained. in contrast, there is the site
process for VelocityTools:
- uses DVSL (VTL-based, encourages DVSL maintenance)
- deploy process is just:
ant publish.docs
ssh <user>@people.apache.org
cd /www/velocity.apache.org/tools/devel (or release/<ver>)
unzip -o ../docs.zip
- and it works! no headaches!
it's simple, low-maintenance, and doesn't make me want to throw
things. granted, it may not have all the snazzy features Maven
provides, but we're barely taking advantage of them anyway. so,
consider this my warning that i intend to ditch this whole
velocity-site thing. if any of you think this is a bad idea, by all
means, please step up and maintain the velocity-site mess. i don't
think anything less than that will change my mind, and it's doubtful
whether even that would change it for long. i'm not sure when i'll
get to making the change; i've little doubt that it will be more work
than i imagine (especially figuring out what to do with those APT
files); and i'm sure it won't be fun. but consider this my notice
that i will no longer waste my time with this convoluted,
temperamental Maven-crazy velocity-site stuff.
p.s. help is welcome, and no one is allowed to complain about the lack
of site updates unless they help, one way or another. ;-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Nathan Bubna <nb...@gmail.com>.
i'm glad it at least works for you. thanks, Henning! so, the
download, news and index pages are updated for 1.6-beta1. i do still
need to figure out how we update the pages at
http://velocity.apache.org/engine/devel/ to reflect this latest. i've
no more time tonight though. anyone know offhand? if not, i'll
figure it out tomorrow, i guess.
once that's done, i'll send out the announcement of 1.6-beta1. i want
to wait for that updated change log, though, to show off all the
changes, not just a few.
On Mon, Sep 22, 2008 at 6:17 PM, Henning Schmiedehausen
<he...@apache.org> wrote:
> Hmm, I seem to do something wrong... :-)
>
> % slogin velocity.zones.apache.org
> Last login: Tue Sep 23 01:10:16 2008 from adsl-76-200-189
> Sun Microsystems Inc. SunOS 5.10 Generic January 2005
> bash-3.00$ newgrp velocity
> bash-3.00$ ~velocity/bin/build_velocity_site.sh > /tmp/logfile 2>&1
> bash-3.00$ tail -10 /tmp/logfile
>
> scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnecting
> scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 11 seconds
> [INFO] Finished at: Tue Sep 23 01:16:38 GMT+00:00 2008
> [INFO] Final Memory: 8M/66M
> [INFO] ------------------------------------------------------------------------
> bash-3.00$
>
> works for me. What errors exactly do you get? Maybe I have some env
> variables set differently from you.
>
> I could sudo to your account if you don't mind.
>
> Ciao
> Henning
>
>
> On Mon, 2008-09-22 at 17:26 -0700, Nathan Bubna wrote:
>> this still sucks... henning, do you have any time to help me with
>> this? even if you can just update the public site. the changes are
>> checked in, i just can't get
>>
>> newgrp velocity
>> /export/home/velocity/bin/build_velocity_site.sh
>>
>> to run for me on the zone.
>>
>> On Mon, Jul 7, 2008 at 11:42 AM, Nathan Bubna <nb...@gmail.com> wrote:
>> > Ok, in a fit of procrastinating what i should really work on this
>> > morning, i thought i'd try and do a quick update of the site to show
>> > the Tools 2.0-beta1 release, and thus ensure i can update the site on
>> > my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
>> > Unfortunately, i can't build the site tools. It looks like the
>> > velocity-site-news plugin is not keeping pace with plexus:
>> >
>> > ...
>> > C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
>> > io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
>> > symbol : class ReaderFactory
>> > location: package org.codehaus.plexus.util
>> > ...
>> >
>> > now, this was just a matter of telling the pom to use some older
>> > version of plexus and in theory i shouldn't even need to have to site
>> > stuff all working on my computer, but i feel better about checking
>> > stuff in if i can try it locally. so, i tweaked the
>> > velocity-site-news-plugin pom, got the site tools to all build and was
>> > able to go to the site directory and run the site target successfully.
>> > but then, the site:run target failed. frustrated i decided to go
>> > ahead and check in my changes and just try building and deploying the
>> > site from velocity.zones.apache.org. I followed the instructions and
>> > all seemed to go well until the build_velocity_site.sh script failed
>> > when trying to actually deploy the updated site:
>> >
>> > [INFO] [site:deploy]
>> > scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
>> > Using private key: /export/home/velocity/.ssh/id_rsa
>> > Executing command: /bin/bash -c 'ssh -i
>> > /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
>> > nbubna@people.apache.org "mkdir -p /w
>> > ww/velocity.apache.org/."'
>> >
>> > Permission denied (publickey,keyboard-interactive).
>> >
>> > scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnecting
>> > scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
>> > [INFO] ------------------------------------------------------------------------
>> > [ERROR] BUILD ERROR
>> > [INFO] ------------------------------------------------------------------------
>> > [INFO] Error uploading site
>> >
>> > Embedded error: Error performing commands for file transfer
>> > Exit code 255 - Permission denied (publickey,keyboard-interactive).
>> >
>> >
>> > this is far from the first time i've seen this. in fact, i recall
>> > spending much time fighting this same error in the past. i can't even
>> > remember if i succeeded though. either way, i'm sick of the maven
>> > site building headaches. what should be a fairly simple task has been
>> > an ordeal *for YEARS now*! the current process is brittle, unwieldy
>> > and worst of all, unmaintained. in contrast, there is the site
>> > process for VelocityTools:
>> >
>> > - uses DVSL (VTL-based, encourages DVSL maintenance)
>> > - deploy process is just:
>> > ant publish.docs
>> > ssh <user>@people.apache.org
>> > cd /www/velocity.apache.org/tools/devel (or release/<ver>)
>> > unzip -o ../docs.zip
>> > - and it works! no headaches!
>> >
>> > it's simple, low-maintenance, and doesn't make me want to throw
>> > things. granted, it may not have all the snazzy features Maven
>> > provides, but we're barely taking advantage of them anyway. so,
>> > consider this my warning that i intend to ditch this whole
>> > velocity-site thing. if any of you think this is a bad idea, by all
>> > means, please step up and maintain the velocity-site mess. i don't
>> > think anything less than that will change my mind, and it's doubtful
>> > whether even that would change it for long. i'm not sure when i'll
>> > get to making the change; i've little doubt that it will be more work
>> > than i imagine (especially figuring out what to do with those APT
>> > files); and i'm sure it won't be fun. but consider this my notice
>> > that i will no longer waste my time with this convoluted,
>> > temperamental Maven-crazy velocity-site stuff.
>> >
>> > p.s. help is welcome, and no one is allowed to complain about the lack
>> > of site updates unless they help, one way or another. ;-)
>> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Henning Schmiedehausen <he...@apache.org>.
Hmm, I seem to do something wrong... :-)
% slogin velocity.zones.apache.org
Last login: Tue Sep 23 01:10:16 2008 from adsl-76-200-189
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
bash-3.00$ newgrp velocity
bash-3.00$ ~velocity/bin/build_velocity_site.sh > /tmp/logfile 2>&1
bash-3.00$ tail -10 /tmp/logfile
scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnecting
scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11 seconds
[INFO] Finished at: Tue Sep 23 01:16:38 GMT+00:00 2008
[INFO] Final Memory: 8M/66M
[INFO] ------------------------------------------------------------------------
bash-3.00$
works for me. What errors exactly do you get? Maybe I have some env
variables set differently from you.
I could sudo to your account if you don't mind.
Ciao
Henning
On Mon, 2008-09-22 at 17:26 -0700, Nathan Bubna wrote:
> this still sucks... henning, do you have any time to help me with
> this? even if you can just update the public site. the changes are
> checked in, i just can't get
>
> newgrp velocity
> /export/home/velocity/bin/build_velocity_site.sh
>
> to run for me on the zone.
>
> On Mon, Jul 7, 2008 at 11:42 AM, Nathan Bubna <nb...@gmail.com> wrote:
> > Ok, in a fit of procrastinating what i should really work on this
> > morning, i thought i'd try and do a quick update of the site to show
> > the Tools 2.0-beta1 release, and thus ensure i can update the site on
> > my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
> > Unfortunately, i can't build the site tools. It looks like the
> > velocity-site-news plugin is not keeping pace with plexus:
> >
> > ...
> > C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
> > io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
> > symbol : class ReaderFactory
> > location: package org.codehaus.plexus.util
> > ...
> >
> > now, this was just a matter of telling the pom to use some older
> > version of plexus and in theory i shouldn't even need to have to site
> > stuff all working on my computer, but i feel better about checking
> > stuff in if i can try it locally. so, i tweaked the
> > velocity-site-news-plugin pom, got the site tools to all build and was
> > able to go to the site directory and run the site target successfully.
> > but then, the site:run target failed. frustrated i decided to go
> > ahead and check in my changes and just try building and deploying the
> > site from velocity.zones.apache.org. I followed the instructions and
> > all seemed to go well until the build_velocity_site.sh script failed
> > when trying to actually deploy the updated site:
> >
> > [INFO] [site:deploy]
> > scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
> > Using private key: /export/home/velocity/.ssh/id_rsa
> > Executing command: /bin/bash -c 'ssh -i
> > /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
> > nbubna@people.apache.org "mkdir -p /w
> > ww/velocity.apache.org/."'
> >
> > Permission denied (publickey,keyboard-interactive).
> >
> > scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnecting
> > scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
> > [INFO] ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO] ------------------------------------------------------------------------
> > [INFO] Error uploading site
> >
> > Embedded error: Error performing commands for file transfer
> > Exit code 255 - Permission denied (publickey,keyboard-interactive).
> >
> >
> > this is far from the first time i've seen this. in fact, i recall
> > spending much time fighting this same error in the past. i can't even
> > remember if i succeeded though. either way, i'm sick of the maven
> > site building headaches. what should be a fairly simple task has been
> > an ordeal *for YEARS now*! the current process is brittle, unwieldy
> > and worst of all, unmaintained. in contrast, there is the site
> > process for VelocityTools:
> >
> > - uses DVSL (VTL-based, encourages DVSL maintenance)
> > - deploy process is just:
> > ant publish.docs
> > ssh <user>@people.apache.org
> > cd /www/velocity.apache.org/tools/devel (or release/<ver>)
> > unzip -o ../docs.zip
> > - and it works! no headaches!
> >
> > it's simple, low-maintenance, and doesn't make me want to throw
> > things. granted, it may not have all the snazzy features Maven
> > provides, but we're barely taking advantage of them anyway. so,
> > consider this my warning that i intend to ditch this whole
> > velocity-site thing. if any of you think this is a bad idea, by all
> > means, please step up and maintain the velocity-site mess. i don't
> > think anything less than that will change my mind, and it's doubtful
> > whether even that would change it for long. i'm not sure when i'll
> > get to making the change; i've little doubt that it will be more work
> > than i imagine (especially figuring out what to do with those APT
> > files); and i'm sure it won't be fun. but consider this my notice
> > that i will no longer waste my time with this convoluted,
> > temperamental Maven-crazy velocity-site stuff.
> >
> > p.s. help is welcome, and no one is allowed to complain about the lack
> > of site updates unless they help, one way or another. ;-)
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Henning Schmiedehausen <he...@apache.org>.
Yep, taking a look now.
Ciao
Henning
On Mon, 2008-09-22 at 17:26 -0700, Nathan Bubna wrote:
> this still sucks... henning, do you have any time to help me with
> this? even if you can just update the public site. the changes are
> checked in, i just can't get
>
> newgrp velocity
> /export/home/velocity/bin/build_velocity_site.sh
>
> to run for me on the zone.
>
> On Mon, Jul 7, 2008 at 11:42 AM, Nathan Bubna <nb...@gmail.com> wrote:
> > Ok, in a fit of procrastinating what i should really work on this
> > morning, i thought i'd try and do a quick update of the site to show
> > the Tools 2.0-beta1 release, and thus ensure i can update the site on
> > my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
> > Unfortunately, i can't build the site tools. It looks like the
> > velocity-site-news plugin is not keeping pace with plexus:
> >
> > ...
> > C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
> > io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
> > symbol : class ReaderFactory
> > location: package org.codehaus.plexus.util
> > ...
> >
> > now, this was just a matter of telling the pom to use some older
> > version of plexus and in theory i shouldn't even need to have to site
> > stuff all working on my computer, but i feel better about checking
> > stuff in if i can try it locally. so, i tweaked the
> > velocity-site-news-plugin pom, got the site tools to all build and was
> > able to go to the site directory and run the site target successfully.
> > but then, the site:run target failed. frustrated i decided to go
> > ahead and check in my changes and just try building and deploying the
> > site from velocity.zones.apache.org. I followed the instructions and
> > all seemed to go well until the build_velocity_site.sh script failed
> > when trying to actually deploy the updated site:
> >
> > [INFO] [site:deploy]
> > scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
> > Using private key: /export/home/velocity/.ssh/id_rsa
> > Executing command: /bin/bash -c 'ssh -i
> > /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
> > nbubna@people.apache.org "mkdir -p /w
> > ww/velocity.apache.org/."'
> >
> > Permission denied (publickey,keyboard-interactive).
> >
> > scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnecting
> > scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
> > [INFO] ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO] ------------------------------------------------------------------------
> > [INFO] Error uploading site
> >
> > Embedded error: Error performing commands for file transfer
> > Exit code 255 - Permission denied (publickey,keyboard-interactive).
> >
> >
> > this is far from the first time i've seen this. in fact, i recall
> > spending much time fighting this same error in the past. i can't even
> > remember if i succeeded though. either way, i'm sick of the maven
> > site building headaches. what should be a fairly simple task has been
> > an ordeal *for YEARS now*! the current process is brittle, unwieldy
> > and worst of all, unmaintained. in contrast, there is the site
> > process for VelocityTools:
> >
> > - uses DVSL (VTL-based, encourages DVSL maintenance)
> > - deploy process is just:
> > ant publish.docs
> > ssh <user>@people.apache.org
> > cd /www/velocity.apache.org/tools/devel (or release/<ver>)
> > unzip -o ../docs.zip
> > - and it works! no headaches!
> >
> > it's simple, low-maintenance, and doesn't make me want to throw
> > things. granted, it may not have all the snazzy features Maven
> > provides, but we're barely taking advantage of them anyway. so,
> > consider this my warning that i intend to ditch this whole
> > velocity-site thing. if any of you think this is a bad idea, by all
> > means, please step up and maintain the velocity-site mess. i don't
> > think anything less than that will change my mind, and it's doubtful
> > whether even that would change it for long. i'm not sure when i'll
> > get to making the change; i've little doubt that it will be more work
> > than i imagine (especially figuring out what to do with those APT
> > files); and i'm sure it won't be fun. but consider this my notice
> > that i will no longer waste my time with this convoluted,
> > temperamental Maven-crazy velocity-site stuff.
> >
> > p.s. help is welcome, and no one is allowed to complain about the lack
> > of site updates unless they help, one way or another. ;-)
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Nathan Bubna <nb...@gmail.com>.
this still sucks... henning, do you have any time to help me with
this? even if you can just update the public site. the changes are
checked in, i just can't get
newgrp velocity
/export/home/velocity/bin/build_velocity_site.sh
to run for me on the zone.
On Mon, Jul 7, 2008 at 11:42 AM, Nathan Bubna <nb...@gmail.com> wrote:
> Ok, in a fit of procrastinating what i should really work on this
> morning, i thought i'd try and do a quick update of the site to show
> the Tools 2.0-beta1 release, and thus ensure i can update the site on
> my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
> Unfortunately, i can't build the site tools. It looks like the
> velocity-site-news plugin is not keeping pace with plexus:
>
> ...
> C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
> io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
> symbol : class ReaderFactory
> location: package org.codehaus.plexus.util
> ...
>
> now, this was just a matter of telling the pom to use some older
> version of plexus and in theory i shouldn't even need to have to site
> stuff all working on my computer, but i feel better about checking
> stuff in if i can try it locally. so, i tweaked the
> velocity-site-news-plugin pom, got the site tools to all build and was
> able to go to the site directory and run the site target successfully.
> but then, the site:run target failed. frustrated i decided to go
> ahead and check in my changes and just try building and deploying the
> site from velocity.zones.apache.org. I followed the instructions and
> all seemed to go well until the build_velocity_site.sh script failed
> when trying to actually deploy the updated site:
>
> [INFO] [site:deploy]
> scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
> Using private key: /export/home/velocity/.ssh/id_rsa
> Executing command: /bin/bash -c 'ssh -i
> /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
> nbubna@people.apache.org "mkdir -p /w
> ww/velocity.apache.org/."'
>
> Permission denied (publickey,keyboard-interactive).
>
> scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnecting
> scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Error uploading site
>
> Embedded error: Error performing commands for file transfer
> Exit code 255 - Permission denied (publickey,keyboard-interactive).
>
>
> this is far from the first time i've seen this. in fact, i recall
> spending much time fighting this same error in the past. i can't even
> remember if i succeeded though. either way, i'm sick of the maven
> site building headaches. what should be a fairly simple task has been
> an ordeal *for YEARS now*! the current process is brittle, unwieldy
> and worst of all, unmaintained. in contrast, there is the site
> process for VelocityTools:
>
> - uses DVSL (VTL-based, encourages DVSL maintenance)
> - deploy process is just:
> ant publish.docs
> ssh <user>@people.apache.org
> cd /www/velocity.apache.org/tools/devel (or release/<ver>)
> unzip -o ../docs.zip
> - and it works! no headaches!
>
> it's simple, low-maintenance, and doesn't make me want to throw
> things. granted, it may not have all the snazzy features Maven
> provides, but we're barely taking advantage of them anyway. so,
> consider this my warning that i intend to ditch this whole
> velocity-site thing. if any of you think this is a bad idea, by all
> means, please step up and maintain the velocity-site mess. i don't
> think anything less than that will change my mind, and it's doubtful
> whether even that would change it for long. i'm not sure when i'll
> get to making the change; i've little doubt that it will be more work
> than i imagine (especially figuring out what to do with those APT
> files); and i'm sure it won't be fun. but consider this my notice
> that i will no longer waste my time with this convoluted,
> temperamental Maven-crazy velocity-site stuff.
>
> p.s. help is welcome, and no one is allowed to complain about the lack
> of site updates unless they help, one way or another. ;-)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Nathan Bubna <nb...@gmail.com>.
On Mon, Jul 7, 2008 at 9:44 PM, Will Glass-Husain
<wg...@gmail.com> wrote:
> I'm pretty agnostic about this stuff, other than wanting something
> that works well and is reasonably easy to use when we need it.
sounds like you want something else too. :)
> Maybe the stuff that Henning customized is now in Maven core? It'd be
> nice if this could be a standard installation.
i wouldn't know, and i really only have so much attention/time i can
give to OSS. Maven is off my radar.
> WILL
>
> On Mon, Jul 7, 2008 at 4:19 PM, Nathan Bubna <nb...@gmail.com> wrote:
>> On Mon, Jul 7, 2008 at 1:39 PM, Paul Sundling <tk...@tkz.net> wrote:
>>> Sounds more like an ssh configuration problem. I bet it's been a long time
>>> since the last update.
>>
>> it probably is just an ssh config issue of some sort, but it's just
>> the symptom of the larger problem: dependence on a very customized
>> maven build that is so fragile it only "reliably" works from a custom,
>> specialized maven installation Henning setup on
>> velocity.zones.apache.org that must be invoked from a set of shells
>> scripts after a "newgrp velocity" command with ssh all properly
>> configured everywhere.
>>
>> it's a beast. and it makes me grumpy every time i try to use it.
>>
>>> I know general Maven pretty well, but I haven't done much advanced site
>>> stuff, mostly configuring reports. I'll try it locally sometime later in
>>> the week. Maven 2 keeps getting better, so one of my first questions would
>>> be what version are you using on the server?
>>
>> that would be quite welcome! i believe the maven build on
>> velocity.zones.apache.org is 2.0.6, but i also believe it is a custom
>> build, not the standard distribution. if you search the archives for
>> this list, you can probably learn a lot of things that would help.
>>
>>> Paul Sundling
>>>
>>> On Mon, 7 Jul 2008, Nathan Bubna wrote:
>>>
>>>> Ok, in a fit of procrastinating what i should really work on this
>>>> morning, i thought i'd try and do a quick update of the site to show
>>>> the Tools 2.0-beta1 release, and thus ensure i can update the site on
>>>> my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
>>>> Unfortunately, i can't build the site tools. It looks like the
>>>> velocity-site-news plugin is not keeping pace with plexus:
>>>>
>>>> ...
>>>>
>>>> C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
>>>> io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
>>>> symbol : class ReaderFactory
>>>> location: package org.codehaus.plexus.util
>>>> ...
>>>>
>>>> now, this was just a matter of telling the pom to use some older
>>>> version of plexus and in theory i shouldn't even need to have to site
>>>> stuff all working on my computer, but i feel better about checking
>>>> stuff in if i can try it locally. so, i tweaked the
>>>> velocity-site-news-plugin pom, got the site tools to all build and was
>>>> able to go to the site directory and run the site target successfully.
>>>> but then, the site:run target failed. frustrated i decided to go
>>>> ahead and check in my changes and just try building and deploying the
>>>> site from velocity.zones.apache.org. I followed the instructions and
>>>> all seemed to go well until the build_velocity_site.sh script failed
>>>> when trying to actually deploy the updated site:
>>>>
>>>> [INFO] [site:deploy]
>>>> scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
>>>> Using private key: /export/home/velocity/.ssh/id_rsa
>>>> Executing command: /bin/bash -c 'ssh -i
>>>> /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
>>>> nbubna@people.apache.org "mkdir -p /w
>>>> ww/velocity.apache.org/."'
>>>>
>>>> Permission denied (publickey,keyboard-interactive).
>>>>
>>>> scpexe://people.apache.org/www/velocity.apache.org - Session:
>>>> Disconnecting
>>>> scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [ERROR] BUILD ERROR
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Error uploading site
>>>>
>>>> Embedded error: Error performing commands for file transfer
>>>> Exit code 255 - Permission denied (publickey,keyboard-interactive).
>>>>
>>>>
>>>> this is far from the first time i've seen this. in fact, i recall
>>>> spending much time fighting this same error in the past. i can't even
>>>> remember if i succeeded though. either way, i'm sick of the maven
>>>> site building headaches. what should be a fairly simple task has been
>>>> an ordeal *for YEARS now*! the current process is brittle, unwieldy
>>>> and worst of all, unmaintained. in contrast, there is the site
>>>> process for VelocityTools:
>>>>
>>>> - uses DVSL (VTL-based, encourages DVSL maintenance)
>>>> - deploy process is just:
>>>> ant publish.docs
>>>> ssh <user>@people.apache.org
>>>> cd /www/velocity.apache.org/tools/devel (or release/<ver>)
>>>> unzip -o ../docs.zip
>>>> - and it works! no headaches!
>>>>
>>>> it's simple, low-maintenance, and doesn't make me want to throw
>>>> things. granted, it may not have all the snazzy features Maven
>>>> provides, but we're barely taking advantage of them anyway. so,
>>>> consider this my warning that i intend to ditch this whole
>>>> velocity-site thing. if any of you think this is a bad idea, by all
>>>> means, please step up and maintain the velocity-site mess. i don't
>>>> think anything less than that will change my mind, and it's doubtful
>>>> whether even that would change it for long. i'm not sure when i'll
>>>> get to making the change; i've little doubt that it will be more work
>>>> than i imagine (especially figuring out what to do with those APT
>>>> files); and i'm sure it won't be fun. but consider this my notice
>>>> that i will no longer waste my time with this convoluted,
>>>> temperamental Maven-crazy velocity-site stuff.
>>>>
>>>> p.s. help is welcome, and no one is allowed to complain about the lack
>>>> of site updates unless they help, one way or another. ;-)
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>> For additional commands, e-mail: dev-help@velocity.apache.org
>>
>>
>
>
>
> --
> Forio Business Simulations
>
> Will Glass-Husain
> wglass@forio.com
> www.forio.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Will Glass-Husain <wg...@gmail.com>.
I'm pretty agnostic about this stuff, other than wanting something
that works well and is reasonably easy to use when we need it.
Maybe the stuff that Henning customized is now in Maven core? It'd be
nice if this could be a standard installation.
WILL
On Mon, Jul 7, 2008 at 4:19 PM, Nathan Bubna <nb...@gmail.com> wrote:
> On Mon, Jul 7, 2008 at 1:39 PM, Paul Sundling <tk...@tkz.net> wrote:
>> Sounds more like an ssh configuration problem. I bet it's been a long time
>> since the last update.
>
> it probably is just an ssh config issue of some sort, but it's just
> the symptom of the larger problem: dependence on a very customized
> maven build that is so fragile it only "reliably" works from a custom,
> specialized maven installation Henning setup on
> velocity.zones.apache.org that must be invoked from a set of shells
> scripts after a "newgrp velocity" command with ssh all properly
> configured everywhere.
>
> it's a beast. and it makes me grumpy every time i try to use it.
>
>> I know general Maven pretty well, but I haven't done much advanced site
>> stuff, mostly configuring reports. I'll try it locally sometime later in
>> the week. Maven 2 keeps getting better, so one of my first questions would
>> be what version are you using on the server?
>
> that would be quite welcome! i believe the maven build on
> velocity.zones.apache.org is 2.0.6, but i also believe it is a custom
> build, not the standard distribution. if you search the archives for
> this list, you can probably learn a lot of things that would help.
>
>> Paul Sundling
>>
>> On Mon, 7 Jul 2008, Nathan Bubna wrote:
>>
>>> Ok, in a fit of procrastinating what i should really work on this
>>> morning, i thought i'd try and do a quick update of the site to show
>>> the Tools 2.0-beta1 release, and thus ensure i can update the site on
>>> my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
>>> Unfortunately, i can't build the site tools. It looks like the
>>> velocity-site-news plugin is not keeping pace with plexus:
>>>
>>> ...
>>>
>>> C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
>>> io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
>>> symbol : class ReaderFactory
>>> location: package org.codehaus.plexus.util
>>> ...
>>>
>>> now, this was just a matter of telling the pom to use some older
>>> version of plexus and in theory i shouldn't even need to have to site
>>> stuff all working on my computer, but i feel better about checking
>>> stuff in if i can try it locally. so, i tweaked the
>>> velocity-site-news-plugin pom, got the site tools to all build and was
>>> able to go to the site directory and run the site target successfully.
>>> but then, the site:run target failed. frustrated i decided to go
>>> ahead and check in my changes and just try building and deploying the
>>> site from velocity.zones.apache.org. I followed the instructions and
>>> all seemed to go well until the build_velocity_site.sh script failed
>>> when trying to actually deploy the updated site:
>>>
>>> [INFO] [site:deploy]
>>> scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
>>> Using private key: /export/home/velocity/.ssh/id_rsa
>>> Executing command: /bin/bash -c 'ssh -i
>>> /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
>>> nbubna@people.apache.org "mkdir -p /w
>>> ww/velocity.apache.org/."'
>>>
>>> Permission denied (publickey,keyboard-interactive).
>>>
>>> scpexe://people.apache.org/www/velocity.apache.org - Session:
>>> Disconnecting
>>> scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Error uploading site
>>>
>>> Embedded error: Error performing commands for file transfer
>>> Exit code 255 - Permission denied (publickey,keyboard-interactive).
>>>
>>>
>>> this is far from the first time i've seen this. in fact, i recall
>>> spending much time fighting this same error in the past. i can't even
>>> remember if i succeeded though. either way, i'm sick of the maven
>>> site building headaches. what should be a fairly simple task has been
>>> an ordeal *for YEARS now*! the current process is brittle, unwieldy
>>> and worst of all, unmaintained. in contrast, there is the site
>>> process for VelocityTools:
>>>
>>> - uses DVSL (VTL-based, encourages DVSL maintenance)
>>> - deploy process is just:
>>> ant publish.docs
>>> ssh <user>@people.apache.org
>>> cd /www/velocity.apache.org/tools/devel (or release/<ver>)
>>> unzip -o ../docs.zip
>>> - and it works! no headaches!
>>>
>>> it's simple, low-maintenance, and doesn't make me want to throw
>>> things. granted, it may not have all the snazzy features Maven
>>> provides, but we're barely taking advantage of them anyway. so,
>>> consider this my warning that i intend to ditch this whole
>>> velocity-site thing. if any of you think this is a bad idea, by all
>>> means, please step up and maintain the velocity-site mess. i don't
>>> think anything less than that will change my mind, and it's doubtful
>>> whether even that would change it for long. i'm not sure when i'll
>>> get to making the change; i've little doubt that it will be more work
>>> than i imagine (especially figuring out what to do with those APT
>>> files); and i'm sure it won't be fun. but consider this my notice
>>> that i will no longer waste my time with this convoluted,
>>> temperamental Maven-crazy velocity-site stuff.
>>>
>>> p.s. help is welcome, and no one is allowed to complain about the lack
>>> of site updates unless they help, one way or another. ;-)
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>> For additional commands, e-mail: dev-help@velocity.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Nathan Bubna <nb...@gmail.com>.
On Tue, Jul 8, 2008 at 10:15 AM, Paul Sundling <tk...@tkz.net> wrote:
> Yes It was velocitytools. I looked at the readme and here is an update on
> the patches mentioned in the readme:
>
> MNG-2874 : Fixed presumably in Maven 2.0.6 (2.0.9 is current version)
> MCHANGES-67: not sure I understand this one, but it sounds like wanted to
> use a mechanism other than list of developers in the pom.xml. Not resolved
> MCHANGES-66: fixed in version 2.0 of changes plugin (which is current
> version)
> DOXIA-91:Fixed in doxia 1.0-alpha-9
> DOXIA-78:fixed in 1.0-beta-1 (plugin has 70 of 72 issues resolved so should
> release soon, current version 1-0.alpha11)
>
> So most of the patches are fixed if using current versions.
Well, that's good.
> Having to locally install a deliverable seems like a bad call. General an
> internal repository is used to handle those use cases.
agreed.
> I would be shocked if apache didn't have their own proximity or continuum
> maven repository, given that maven itself is part of the apache project!
me too.
> It does sound brittle if you have to manually install deliverables in your
> local repository, apply custom patches...
>
> I don't think I'm going to be much help on that. You could always ask if
> someone on the maven project could help considering they are in ASF.
well, i appreciate the help so far. i still think i'm going to ditch
this. even if i got help and figured this out, we would still have
different site building methods for each velocity project. we need
some consistency here. i'm going to try and fix that, so i might as
well do it with the site building process in which i already have
expertise and familiarity.
> Paul Sundling
>
> On Tue, 8 Jul 2008, Nathan Bubna wrote:
>
>> On Mon, Jul 7, 2008 at 11:22 PM, Paul Sundling <tk...@tkz.net> wrote:
>>>
>>> Well there is probably not much I can do to help without access.
>>>
>>> When I run site:site locally I get an error complaining about config.xml
>>> and
>>> config.xml.xml having a conflict. I know Maven pretty well, but I
>>> haven't
>>> delved into custom site generation, just reports. So I'm not sure about
>>> troubleshooting it.
>>>
>>> Some notes on the maven configuration:
>>>
>>> Using build/classes and dist instead of the standard maven directories.
>>> I
>>> assume this is related to compatibility with some other system.
>>>
>>> I see mention of 3 jars, but Maven only built one overall jar. If
>>> breaking
>>> up things into separate jars, the standard maven approach is to split
>>> them
>>> into multiple sub-projects with a parent pom that is used to build them
>>> all
>>> together. it's relatively easy to setup, using a dependencyManagement
>>> section to keep versions consistent. The different deliverables can even
>>> have different dependencies. I wonder how things are done now. I
>>> wouldn't
>>> be suprised if there is some ant script being invoked in the shell
>>> scripts.
>>>
>>> Otherwise, the pom.xml looks pretty standard.
>>
>> Sounds like you're working with VelocityTools here. It's pretty
>> vanilla and doesn't do all that the Ant build does because Maven is
>> not the main build system. The only Velocity project where Maven is
>> king is the velocity-site stuff:
>>
>> http://svn.apache.org/repos/asf/velocity/site
>>
>> If you're up for it, you could take a look at that. I think the
>> README.txt describes the gist of what's going on in there. My
>> understanding is that you have to go to the site/tools dir and run the
>> install target there, then go to the site/site directory and run
>> site:site there. Or something like that.
>>
>>> Sorry I'm not much help.
>>>
>>> Paul Sundling
>>>
>>> On Mon, 7 Jul 2008, Nathan Bubna wrote:
>>>
>>>> On Mon, Jul 7, 2008 at 1:39 PM, Paul Sundling <tk...@tkz.net> wrote:
>>>>>
>>>>> Sounds more like an ssh configuration problem. I bet it's been a long
>>>>> time
>>>>> since the last update.
>>>>
>>>> it probably is just an ssh config issue of some sort, but it's just
>>>> the symptom of the larger problem: dependence on a very customized
>>>> maven build that is so fragile it only "reliably" works from a custom,
>>>> specialized maven installation Henning setup on
>>>> velocity.zones.apache.org that must be invoked from a set of shells
>>>> scripts after a "newgrp velocity" command with ssh all properly
>>>> configured everywhere.
>>>>
>>>> it's a beast. and it makes me grumpy every time i try to use it.
>>>>
>>>>> I know general Maven pretty well, but I haven't done much advanced site
>>>>> stuff, mostly configuring reports. I'll try it locally sometime later
>>>>> in
>>>>> the week. Maven 2 keeps getting better, so one of my first questions
>>>>> would
>>>>> be what version are you using on the server?
>>>>
>>>> that would be quite welcome! i believe the maven build on
>>>> velocity.zones.apache.org is 2.0.6, but i also believe it is a custom
>>>> build, not the standard distribution. if you search the archives for
>>>> this list, you can probably learn a lot of things that would help.
>>>>
>>>>> Paul Sundling
>>>>>
>>>>> On Mon, 7 Jul 2008, Nathan Bubna wrote:
>>>>>
>>>>>> Ok, in a fit of procrastinating what i should really work on this
>>>>>> morning, i thought i'd try and do a quick update of the site to show
>>>>>> the Tools 2.0-beta1 release, and thus ensure i can update the site on
>>>>>> my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
>>>>>> Unfortunately, i can't build the site tools. It looks like the
>>>>>> velocity-site-news plugin is not keeping pace with plexus:
>>>>>>
>>>>>> ...
>>>>>>
>>>>>>
>>>>>>
>>>>>> C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
>>>>>> io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
>>>>>> symbol : class ReaderFactory
>>>>>> location: package org.codehaus.plexus.util
>>>>>> ...
>>>>>>
>>>>>> now, this was just a matter of telling the pom to use some older
>>>>>> version of plexus and in theory i shouldn't even need to have to site
>>>>>> stuff all working on my computer, but i feel better about checking
>>>>>> stuff in if i can try it locally. so, i tweaked the
>>>>>> velocity-site-news-plugin pom, got the site tools to all build and was
>>>>>> able to go to the site directory and run the site target successfully.
>>>>>> but then, the site:run target failed. frustrated i decided to go
>>>>>> ahead and check in my changes and just try building and deploying the
>>>>>> site from velocity.zones.apache.org. I followed the instructions and
>>>>>> all seemed to go well until the build_velocity_site.sh script failed
>>>>>> when trying to actually deploy the updated site:
>>>>>>
>>>>>> [INFO] [site:deploy]
>>>>>> scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
>>>>>> Using private key: /export/home/velocity/.ssh/id_rsa
>>>>>> Executing command: /bin/bash -c 'ssh -i
>>>>>> /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
>>>>>> nbubna@people.apache.org "mkdir -p /w
>>>>>> ww/velocity.apache.org/."'
>>>>>>
>>>>>> Permission denied (publickey,keyboard-interactive).
>>>>>>
>>>>>> scpexe://people.apache.org/www/velocity.apache.org - Session:
>>>>>> Disconnecting
>>>>>> scpexe://people.apache.org/www/velocity.apache.org - Session:
>>>>>> Disconnected
>>>>>> [INFO]
>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>> [ERROR] BUILD ERROR
>>>>>> [INFO]
>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] Error uploading site
>>>>>>
>>>>>> Embedded error: Error performing commands for file transfer
>>>>>> Exit code 255 - Permission denied (publickey,keyboard-interactive).
>>>>>>
>>>>>>
>>>>>> this is far from the first time i've seen this. in fact, i recall
>>>>>> spending much time fighting this same error in the past. i can't even
>>>>>> remember if i succeeded though. either way, i'm sick of the maven
>>>>>> site building headaches. what should be a fairly simple task has been
>>>>>> an ordeal *for YEARS now*! the current process is brittle, unwieldy
>>>>>> and worst of all, unmaintained. in contrast, there is the site
>>>>>> process for VelocityTools:
>>>>>>
>>>>>> - uses DVSL (VTL-based, encourages DVSL maintenance)
>>>>>> - deploy process is just:
>>>>>> ant publish.docs
>>>>>> ssh <user>@people.apache.org
>>>>>> cd /www/velocity.apache.org/tools/devel (or release/<ver>)
>>>>>> unzip -o ../docs.zip
>>>>>> - and it works! no headaches!
>>>>>>
>>>>>> it's simple, low-maintenance, and doesn't make me want to throw
>>>>>> things. granted, it may not have all the snazzy features Maven
>>>>>> provides, but we're barely taking advantage of them anyway. so,
>>>>>> consider this my warning that i intend to ditch this whole
>>>>>> velocity-site thing. if any of you think this is a bad idea, by all
>>>>>> means, please step up and maintain the velocity-site mess. i don't
>>>>>> think anything less than that will change my mind, and it's doubtful
>>>>>> whether even that would change it for long. i'm not sure when i'll
>>>>>> get to making the change; i've little doubt that it will be more work
>>>>>> than i imagine (especially figuring out what to do with those APT
>>>>>> files); and i'm sure it won't be fun. but consider this my notice
>>>>>> that i will no longer waste my time with this convoluted,
>>>>>> temperamental Maven-crazy velocity-site stuff.
>>>>>>
>>>>>> p.s. help is welcome, and no one is allowed to complain about the lack
>>>>>> of site updates unless they help, one way or another. ;-)
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>>>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>> For additional commands, e-mail: dev-help@velocity.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Paul Sundling <tk...@tkz.net>.
Yes It was velocitytools. I looked at the readme and here is an update on
the patches mentioned in the readme:
MNG-2874 : Fixed presumably in Maven 2.0.6 (2.0.9 is current version)
MCHANGES-67: not sure I understand this one, but it sounds like wanted to
use a mechanism other than list of developers in the pom.xml. Not
resolved
MCHANGES-66: fixed in version 2.0 of changes plugin (which is current
version)
DOXIA-91:Fixed in doxia 1.0-alpha-9
DOXIA-78:fixed in 1.0-beta-1 (plugin has 70 of 72 issues resolved so
should release soon, current version 1-0.alpha11)
So most of the patches are fixed if using current versions.
Having to locally install a deliverable seems like a bad call. General an
internal repository is used to handle those use cases.
I would be shocked if apache didn't have their own
proximity or continuum maven repository, given that maven itself is part
of the apache project!
It does sound brittle if you have to manually install deliverables in your
local repository, apply custom patches...
I don't think I'm going to be much help on that. You could always ask if
someone on the maven project could help considering they are in ASF.
Paul Sundling
On Tue, 8 Jul 2008, Nathan Bubna wrote:
> On Mon, Jul 7, 2008 at 11:22 PM, Paul Sundling <tk...@tkz.net> wrote:
>> Well there is probably not much I can do to help without access.
>>
>> When I run site:site locally I get an error complaining about config.xml and
>> config.xml.xml having a conflict. I know Maven pretty well, but I haven't
>> delved into custom site generation, just reports. So I'm not sure about
>> troubleshooting it.
>>
>> Some notes on the maven configuration:
>>
>> Using build/classes and dist instead of the standard maven directories. I
>> assume this is related to compatibility with some other system.
>>
>> I see mention of 3 jars, but Maven only built one overall jar. If breaking
>> up things into separate jars, the standard maven approach is to split them
>> into multiple sub-projects with a parent pom that is used to build them all
>> together. it's relatively easy to setup, using a dependencyManagement
>> section to keep versions consistent. The different deliverables can even
>> have different dependencies. I wonder how things are done now. I wouldn't
>> be suprised if there is some ant script being invoked in the shell scripts.
>>
>> Otherwise, the pom.xml looks pretty standard.
>
> Sounds like you're working with VelocityTools here. It's pretty
> vanilla and doesn't do all that the Ant build does because Maven is
> not the main build system. The only Velocity project where Maven is
> king is the velocity-site stuff:
>
> http://svn.apache.org/repos/asf/velocity/site
>
> If you're up for it, you could take a look at that. I think the
> README.txt describes the gist of what's going on in there. My
> understanding is that you have to go to the site/tools dir and run the
> install target there, then go to the site/site directory and run
> site:site there. Or something like that.
>
>> Sorry I'm not much help.
>>
>> Paul Sundling
>>
>> On Mon, 7 Jul 2008, Nathan Bubna wrote:
>>
>>> On Mon, Jul 7, 2008 at 1:39 PM, Paul Sundling <tk...@tkz.net> wrote:
>>>>
>>>> Sounds more like an ssh configuration problem. I bet it's been a long
>>>> time
>>>> since the last update.
>>>
>>> it probably is just an ssh config issue of some sort, but it's just
>>> the symptom of the larger problem: dependence on a very customized
>>> maven build that is so fragile it only "reliably" works from a custom,
>>> specialized maven installation Henning setup on
>>> velocity.zones.apache.org that must be invoked from a set of shells
>>> scripts after a "newgrp velocity" command with ssh all properly
>>> configured everywhere.
>>>
>>> it's a beast. and it makes me grumpy every time i try to use it.
>>>
>>>> I know general Maven pretty well, but I haven't done much advanced site
>>>> stuff, mostly configuring reports. I'll try it locally sometime later in
>>>> the week. Maven 2 keeps getting better, so one of my first questions
>>>> would
>>>> be what version are you using on the server?
>>>
>>> that would be quite welcome! i believe the maven build on
>>> velocity.zones.apache.org is 2.0.6, but i also believe it is a custom
>>> build, not the standard distribution. if you search the archives for
>>> this list, you can probably learn a lot of things that would help.
>>>
>>>> Paul Sundling
>>>>
>>>> On Mon, 7 Jul 2008, Nathan Bubna wrote:
>>>>
>>>>> Ok, in a fit of procrastinating what i should really work on this
>>>>> morning, i thought i'd try and do a quick update of the site to show
>>>>> the Tools 2.0-beta1 release, and thus ensure i can update the site on
>>>>> my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
>>>>> Unfortunately, i can't build the site tools. It looks like the
>>>>> velocity-site-news plugin is not keeping pace with plexus:
>>>>>
>>>>> ...
>>>>>
>>>>>
>>>>> C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
>>>>> io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
>>>>> symbol : class ReaderFactory
>>>>> location: package org.codehaus.plexus.util
>>>>> ...
>>>>>
>>>>> now, this was just a matter of telling the pom to use some older
>>>>> version of plexus and in theory i shouldn't even need to have to site
>>>>> stuff all working on my computer, but i feel better about checking
>>>>> stuff in if i can try it locally. so, i tweaked the
>>>>> velocity-site-news-plugin pom, got the site tools to all build and was
>>>>> able to go to the site directory and run the site target successfully.
>>>>> but then, the site:run target failed. frustrated i decided to go
>>>>> ahead and check in my changes and just try building and deploying the
>>>>> site from velocity.zones.apache.org. I followed the instructions and
>>>>> all seemed to go well until the build_velocity_site.sh script failed
>>>>> when trying to actually deploy the updated site:
>>>>>
>>>>> [INFO] [site:deploy]
>>>>> scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
>>>>> Using private key: /export/home/velocity/.ssh/id_rsa
>>>>> Executing command: /bin/bash -c 'ssh -i
>>>>> /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
>>>>> nbubna@people.apache.org "mkdir -p /w
>>>>> ww/velocity.apache.org/."'
>>>>>
>>>>> Permission denied (publickey,keyboard-interactive).
>>>>>
>>>>> scpexe://people.apache.org/www/velocity.apache.org - Session:
>>>>> Disconnecting
>>>>> scpexe://people.apache.org/www/velocity.apache.org - Session:
>>>>> Disconnected
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [ERROR] BUILD ERROR
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] Error uploading site
>>>>>
>>>>> Embedded error: Error performing commands for file transfer
>>>>> Exit code 255 - Permission denied (publickey,keyboard-interactive).
>>>>>
>>>>>
>>>>> this is far from the first time i've seen this. in fact, i recall
>>>>> spending much time fighting this same error in the past. i can't even
>>>>> remember if i succeeded though. either way, i'm sick of the maven
>>>>> site building headaches. what should be a fairly simple task has been
>>>>> an ordeal *for YEARS now*! the current process is brittle, unwieldy
>>>>> and worst of all, unmaintained. in contrast, there is the site
>>>>> process for VelocityTools:
>>>>>
>>>>> - uses DVSL (VTL-based, encourages DVSL maintenance)
>>>>> - deploy process is just:
>>>>> ant publish.docs
>>>>> ssh <user>@people.apache.org
>>>>> cd /www/velocity.apache.org/tools/devel (or release/<ver>)
>>>>> unzip -o ../docs.zip
>>>>> - and it works! no headaches!
>>>>>
>>>>> it's simple, low-maintenance, and doesn't make me want to throw
>>>>> things. granted, it may not have all the snazzy features Maven
>>>>> provides, but we're barely taking advantage of them anyway. so,
>>>>> consider this my warning that i intend to ditch this whole
>>>>> velocity-site thing. if any of you think this is a bad idea, by all
>>>>> means, please step up and maintain the velocity-site mess. i don't
>>>>> think anything less than that will change my mind, and it's doubtful
>>>>> whether even that would change it for long. i'm not sure when i'll
>>>>> get to making the change; i've little doubt that it will be more work
>>>>> than i imagine (especially figuring out what to do with those APT
>>>>> files); and i'm sure it won't be fun. but consider this my notice
>>>>> that i will no longer waste my time with this convoluted,
>>>>> temperamental Maven-crazy velocity-site stuff.
>>>>>
>>>>> p.s. help is welcome, and no one is allowed to complain about the lack
>>>>> of site updates unless they help, one way or another. ;-)
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>> For additional commands, e-mail: dev-help@velocity.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Nathan Bubna <nb...@gmail.com>.
On Mon, Jul 7, 2008 at 11:22 PM, Paul Sundling <tk...@tkz.net> wrote:
> Well there is probably not much I can do to help without access.
>
> When I run site:site locally I get an error complaining about config.xml and
> config.xml.xml having a conflict. I know Maven pretty well, but I haven't
> delved into custom site generation, just reports. So I'm not sure about
> troubleshooting it.
>
> Some notes on the maven configuration:
>
> Using build/classes and dist instead of the standard maven directories. I
> assume this is related to compatibility with some other system.
>
> I see mention of 3 jars, but Maven only built one overall jar. If breaking
> up things into separate jars, the standard maven approach is to split them
> into multiple sub-projects with a parent pom that is used to build them all
> together. it's relatively easy to setup, using a dependencyManagement
> section to keep versions consistent. The different deliverables can even
> have different dependencies. I wonder how things are done now. I wouldn't
> be suprised if there is some ant script being invoked in the shell scripts.
>
> Otherwise, the pom.xml looks pretty standard.
Sounds like you're working with VelocityTools here. It's pretty
vanilla and doesn't do all that the Ant build does because Maven is
not the main build system. The only Velocity project where Maven is
king is the velocity-site stuff:
http://svn.apache.org/repos/asf/velocity/site
If you're up for it, you could take a look at that. I think the
README.txt describes the gist of what's going on in there. My
understanding is that you have to go to the site/tools dir and run the
install target there, then go to the site/site directory and run
site:site there. Or something like that.
> Sorry I'm not much help.
>
> Paul Sundling
>
> On Mon, 7 Jul 2008, Nathan Bubna wrote:
>
>> On Mon, Jul 7, 2008 at 1:39 PM, Paul Sundling <tk...@tkz.net> wrote:
>>>
>>> Sounds more like an ssh configuration problem. I bet it's been a long
>>> time
>>> since the last update.
>>
>> it probably is just an ssh config issue of some sort, but it's just
>> the symptom of the larger problem: dependence on a very customized
>> maven build that is so fragile it only "reliably" works from a custom,
>> specialized maven installation Henning setup on
>> velocity.zones.apache.org that must be invoked from a set of shells
>> scripts after a "newgrp velocity" command with ssh all properly
>> configured everywhere.
>>
>> it's a beast. and it makes me grumpy every time i try to use it.
>>
>>> I know general Maven pretty well, but I haven't done much advanced site
>>> stuff, mostly configuring reports. I'll try it locally sometime later in
>>> the week. Maven 2 keeps getting better, so one of my first questions
>>> would
>>> be what version are you using on the server?
>>
>> that would be quite welcome! i believe the maven build on
>> velocity.zones.apache.org is 2.0.6, but i also believe it is a custom
>> build, not the standard distribution. if you search the archives for
>> this list, you can probably learn a lot of things that would help.
>>
>>> Paul Sundling
>>>
>>> On Mon, 7 Jul 2008, Nathan Bubna wrote:
>>>
>>>> Ok, in a fit of procrastinating what i should really work on this
>>>> morning, i thought i'd try and do a quick update of the site to show
>>>> the Tools 2.0-beta1 release, and thus ensure i can update the site on
>>>> my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
>>>> Unfortunately, i can't build the site tools. It looks like the
>>>> velocity-site-news plugin is not keeping pace with plexus:
>>>>
>>>> ...
>>>>
>>>>
>>>> C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
>>>> io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
>>>> symbol : class ReaderFactory
>>>> location: package org.codehaus.plexus.util
>>>> ...
>>>>
>>>> now, this was just a matter of telling the pom to use some older
>>>> version of plexus and in theory i shouldn't even need to have to site
>>>> stuff all working on my computer, but i feel better about checking
>>>> stuff in if i can try it locally. so, i tweaked the
>>>> velocity-site-news-plugin pom, got the site tools to all build and was
>>>> able to go to the site directory and run the site target successfully.
>>>> but then, the site:run target failed. frustrated i decided to go
>>>> ahead and check in my changes and just try building and deploying the
>>>> site from velocity.zones.apache.org. I followed the instructions and
>>>> all seemed to go well until the build_velocity_site.sh script failed
>>>> when trying to actually deploy the updated site:
>>>>
>>>> [INFO] [site:deploy]
>>>> scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
>>>> Using private key: /export/home/velocity/.ssh/id_rsa
>>>> Executing command: /bin/bash -c 'ssh -i
>>>> /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
>>>> nbubna@people.apache.org "mkdir -p /w
>>>> ww/velocity.apache.org/."'
>>>>
>>>> Permission denied (publickey,keyboard-interactive).
>>>>
>>>> scpexe://people.apache.org/www/velocity.apache.org - Session:
>>>> Disconnecting
>>>> scpexe://people.apache.org/www/velocity.apache.org - Session:
>>>> Disconnected
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [ERROR] BUILD ERROR
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Error uploading site
>>>>
>>>> Embedded error: Error performing commands for file transfer
>>>> Exit code 255 - Permission denied (publickey,keyboard-interactive).
>>>>
>>>>
>>>> this is far from the first time i've seen this. in fact, i recall
>>>> spending much time fighting this same error in the past. i can't even
>>>> remember if i succeeded though. either way, i'm sick of the maven
>>>> site building headaches. what should be a fairly simple task has been
>>>> an ordeal *for YEARS now*! the current process is brittle, unwieldy
>>>> and worst of all, unmaintained. in contrast, there is the site
>>>> process for VelocityTools:
>>>>
>>>> - uses DVSL (VTL-based, encourages DVSL maintenance)
>>>> - deploy process is just:
>>>> ant publish.docs
>>>> ssh <user>@people.apache.org
>>>> cd /www/velocity.apache.org/tools/devel (or release/<ver>)
>>>> unzip -o ../docs.zip
>>>> - and it works! no headaches!
>>>>
>>>> it's simple, low-maintenance, and doesn't make me want to throw
>>>> things. granted, it may not have all the snazzy features Maven
>>>> provides, but we're barely taking advantage of them anyway. so,
>>>> consider this my warning that i intend to ditch this whole
>>>> velocity-site thing. if any of you think this is a bad idea, by all
>>>> means, please step up and maintain the velocity-site mess. i don't
>>>> think anything less than that will change my mind, and it's doubtful
>>>> whether even that would change it for long. i'm not sure when i'll
>>>> get to making the change; i've little doubt that it will be more work
>>>> than i imagine (especially figuring out what to do with those APT
>>>> files); and i'm sure it won't be fun. but consider this my notice
>>>> that i will no longer waste my time with this convoluted,
>>>> temperamental Maven-crazy velocity-site stuff.
>>>>
>>>> p.s. help is welcome, and no one is allowed to complain about the lack
>>>> of site updates unless they help, one way or another. ;-)
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>> For additional commands, e-mail: dev-help@velocity.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Paul Sundling <tk...@tkz.net>.
Well there is probably not much I can do to help without access.
When I run site:site locally I get an error complaining about config.xml
and config.xml.xml having a conflict. I know Maven pretty well, but I
haven't delved into custom site generation, just reports. So I'm not sure
about troubleshooting it.
Some notes on the maven configuration:
Using build/classes and dist instead of the standard maven directories. I
assume this is related to compatibility with some other system.
I see mention of 3 jars, but Maven only built one overall jar. If
breaking up things into separate jars, the standard maven approach is to
split them into multiple sub-projects with a parent pom that is used to
build them all together. it's relatively easy to setup, using a
dependencyManagement section to keep versions consistent. The different
deliverables can even have different dependencies. I wonder how things
are done now. I wouldn't be suprised if there is some ant script being
invoked in the shell scripts.
Otherwise, the pom.xml looks pretty standard.
Sorry I'm not much help.
Paul Sundling
On Mon, 7 Jul 2008, Nathan Bubna wrote:
> On Mon, Jul 7, 2008 at 1:39 PM, Paul Sundling <tk...@tkz.net> wrote:
>> Sounds more like an ssh configuration problem. I bet it's been a long time
>> since the last update.
>
> it probably is just an ssh config issue of some sort, but it's just
> the symptom of the larger problem: dependence on a very customized
> maven build that is so fragile it only "reliably" works from a custom,
> specialized maven installation Henning setup on
> velocity.zones.apache.org that must be invoked from a set of shells
> scripts after a "newgrp velocity" command with ssh all properly
> configured everywhere.
>
> it's a beast. and it makes me grumpy every time i try to use it.
>
>> I know general Maven pretty well, but I haven't done much advanced site
>> stuff, mostly configuring reports. I'll try it locally sometime later in
>> the week. Maven 2 keeps getting better, so one of my first questions would
>> be what version are you using on the server?
>
> that would be quite welcome! i believe the maven build on
> velocity.zones.apache.org is 2.0.6, but i also believe it is a custom
> build, not the standard distribution. if you search the archives for
> this list, you can probably learn a lot of things that would help.
>
>> Paul Sundling
>>
>> On Mon, 7 Jul 2008, Nathan Bubna wrote:
>>
>>> Ok, in a fit of procrastinating what i should really work on this
>>> morning, i thought i'd try and do a quick update of the site to show
>>> the Tools 2.0-beta1 release, and thus ensure i can update the site on
>>> my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
>>> Unfortunately, i can't build the site tools. It looks like the
>>> velocity-site-news plugin is not keeping pace with plexus:
>>>
>>> ...
>>>
>>> C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
>>> io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
>>> symbol : class ReaderFactory
>>> location: package org.codehaus.plexus.util
>>> ...
>>>
>>> now, this was just a matter of telling the pom to use some older
>>> version of plexus and in theory i shouldn't even need to have to site
>>> stuff all working on my computer, but i feel better about checking
>>> stuff in if i can try it locally. so, i tweaked the
>>> velocity-site-news-plugin pom, got the site tools to all build and was
>>> able to go to the site directory and run the site target successfully.
>>> but then, the site:run target failed. frustrated i decided to go
>>> ahead and check in my changes and just try building and deploying the
>>> site from velocity.zones.apache.org. I followed the instructions and
>>> all seemed to go well until the build_velocity_site.sh script failed
>>> when trying to actually deploy the updated site:
>>>
>>> [INFO] [site:deploy]
>>> scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
>>> Using private key: /export/home/velocity/.ssh/id_rsa
>>> Executing command: /bin/bash -c 'ssh -i
>>> /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
>>> nbubna@people.apache.org "mkdir -p /w
>>> ww/velocity.apache.org/."'
>>>
>>> Permission denied (publickey,keyboard-interactive).
>>>
>>> scpexe://people.apache.org/www/velocity.apache.org - Session:
>>> Disconnecting
>>> scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Error uploading site
>>>
>>> Embedded error: Error performing commands for file transfer
>>> Exit code 255 - Permission denied (publickey,keyboard-interactive).
>>>
>>>
>>> this is far from the first time i've seen this. in fact, i recall
>>> spending much time fighting this same error in the past. i can't even
>>> remember if i succeeded though. either way, i'm sick of the maven
>>> site building headaches. what should be a fairly simple task has been
>>> an ordeal *for YEARS now*! the current process is brittle, unwieldy
>>> and worst of all, unmaintained. in contrast, there is the site
>>> process for VelocityTools:
>>>
>>> - uses DVSL (VTL-based, encourages DVSL maintenance)
>>> - deploy process is just:
>>> ant publish.docs
>>> ssh <user>@people.apache.org
>>> cd /www/velocity.apache.org/tools/devel (or release/<ver>)
>>> unzip -o ../docs.zip
>>> - and it works! no headaches!
>>>
>>> it's simple, low-maintenance, and doesn't make me want to throw
>>> things. granted, it may not have all the snazzy features Maven
>>> provides, but we're barely taking advantage of them anyway. so,
>>> consider this my warning that i intend to ditch this whole
>>> velocity-site thing. if any of you think this is a bad idea, by all
>>> means, please step up and maintain the velocity-site mess. i don't
>>> think anything less than that will change my mind, and it's doubtful
>>> whether even that would change it for long. i'm not sure when i'll
>>> get to making the change; i've little doubt that it will be more work
>>> than i imagine (especially figuring out what to do with those APT
>>> files); and i'm sure it won't be fun. but consider this my notice
>>> that i will no longer waste my time with this convoluted,
>>> temperamental Maven-crazy velocity-site stuff.
>>>
>>> p.s. help is welcome, and no one is allowed to complain about the lack
>>> of site updates unless they help, one way or another. ;-)
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>> For additional commands, e-mail: dev-help@velocity.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Nathan Bubna <nb...@gmail.com>.
On Mon, Jul 7, 2008 at 1:39 PM, Paul Sundling <tk...@tkz.net> wrote:
> Sounds more like an ssh configuration problem. I bet it's been a long time
> since the last update.
it probably is just an ssh config issue of some sort, but it's just
the symptom of the larger problem: dependence on a very customized
maven build that is so fragile it only "reliably" works from a custom,
specialized maven installation Henning setup on
velocity.zones.apache.org that must be invoked from a set of shells
scripts after a "newgrp velocity" command with ssh all properly
configured everywhere.
it's a beast. and it makes me grumpy every time i try to use it.
> I know general Maven pretty well, but I haven't done much advanced site
> stuff, mostly configuring reports. I'll try it locally sometime later in
> the week. Maven 2 keeps getting better, so one of my first questions would
> be what version are you using on the server?
that would be quite welcome! i believe the maven build on
velocity.zones.apache.org is 2.0.6, but i also believe it is a custom
build, not the standard distribution. if you search the archives for
this list, you can probably learn a lot of things that would help.
> Paul Sundling
>
> On Mon, 7 Jul 2008, Nathan Bubna wrote:
>
>> Ok, in a fit of procrastinating what i should really work on this
>> morning, i thought i'd try and do a quick update of the site to show
>> the Tools 2.0-beta1 release, and thus ensure i can update the site on
>> my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
>> Unfortunately, i can't build the site tools. It looks like the
>> velocity-site-news plugin is not keeping pace with plexus:
>>
>> ...
>>
>> C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
>> io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
>> symbol : class ReaderFactory
>> location: package org.codehaus.plexus.util
>> ...
>>
>> now, this was just a matter of telling the pom to use some older
>> version of plexus and in theory i shouldn't even need to have to site
>> stuff all working on my computer, but i feel better about checking
>> stuff in if i can try it locally. so, i tweaked the
>> velocity-site-news-plugin pom, got the site tools to all build and was
>> able to go to the site directory and run the site target successfully.
>> but then, the site:run target failed. frustrated i decided to go
>> ahead and check in my changes and just try building and deploying the
>> site from velocity.zones.apache.org. I followed the instructions and
>> all seemed to go well until the build_velocity_site.sh script failed
>> when trying to actually deploy the updated site:
>>
>> [INFO] [site:deploy]
>> scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
>> Using private key: /export/home/velocity/.ssh/id_rsa
>> Executing command: /bin/bash -c 'ssh -i
>> /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
>> nbubna@people.apache.org "mkdir -p /w
>> ww/velocity.apache.org/."'
>>
>> Permission denied (publickey,keyboard-interactive).
>>
>> scpexe://people.apache.org/www/velocity.apache.org - Session:
>> Disconnecting
>> scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Error uploading site
>>
>> Embedded error: Error performing commands for file transfer
>> Exit code 255 - Permission denied (publickey,keyboard-interactive).
>>
>>
>> this is far from the first time i've seen this. in fact, i recall
>> spending much time fighting this same error in the past. i can't even
>> remember if i succeeded though. either way, i'm sick of the maven
>> site building headaches. what should be a fairly simple task has been
>> an ordeal *for YEARS now*! the current process is brittle, unwieldy
>> and worst of all, unmaintained. in contrast, there is the site
>> process for VelocityTools:
>>
>> - uses DVSL (VTL-based, encourages DVSL maintenance)
>> - deploy process is just:
>> ant publish.docs
>> ssh <user>@people.apache.org
>> cd /www/velocity.apache.org/tools/devel (or release/<ver>)
>> unzip -o ../docs.zip
>> - and it works! no headaches!
>>
>> it's simple, low-maintenance, and doesn't make me want to throw
>> things. granted, it may not have all the snazzy features Maven
>> provides, but we're barely taking advantage of them anyway. so,
>> consider this my warning that i intend to ditch this whole
>> velocity-site thing. if any of you think this is a bad idea, by all
>> means, please step up and maintain the velocity-site mess. i don't
>> think anything less than that will change my mind, and it's doubtful
>> whether even that would change it for long. i'm not sure when i'll
>> get to making the change; i've little doubt that it will be more work
>> than i imagine (especially figuring out what to do with those APT
>> files); and i'm sure it won't be fun. but consider this my notice
>> that i will no longer waste my time with this convoluted,
>> temperamental Maven-crazy velocity-site stuff.
>>
>> p.s. help is welcome, and no one is allowed to complain about the lack
>> of site updates unless they help, one way or another. ;-)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>> For additional commands, e-mail: dev-help@velocity.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: velocity-site sucks
Posted by Paul Sundling <tk...@tkz.net>.
Sounds more like an ssh configuration problem. I bet it's been a long
time since the last update.
I know general Maven pretty well, but I haven't done much advanced site
stuff, mostly configuring reports. I'll try it locally sometime later in
the week. Maven 2 keeps getting better, so one of my first questions
would be what version are you using on the server?
Paul Sundling
On Mon, 7 Jul 2008, Nathan Bubna wrote:
> Ok, in a fit of procrastinating what i should really work on this
> morning, i thought i'd try and do a quick update of the site to show
> the Tools 2.0-beta1 release, and thus ensure i can update the site on
> my new laptop, prior to finalizing (hopefully) the 2.0-beta2 release.
> Unfortunately, i can't build the site tools. It looks like the
> velocity-site-news plugin is not keeping pace with plexus:
>
> ...
> C:\java\apache\velocity\site\tools\velocity-site-news-plugin\target\generated-sources\modello\org\apache\velocity\site\news\model\
> io\xpp3\NewsXpp3Reader.java:[18,31] cannot find symbol
> symbol : class ReaderFactory
> location: package org.codehaus.plexus.util
> ...
>
> now, this was just a matter of telling the pom to use some older
> version of plexus and in theory i shouldn't even need to have to site
> stuff all working on my computer, but i feel better about checking
> stuff in if i can try it locally. so, i tweaked the
> velocity-site-news-plugin pom, got the site tools to all build and was
> able to go to the site directory and run the site target successfully.
> but then, the site:run target failed. frustrated i decided to go
> ahead and check in my changes and just try building and deploying the
> site from velocity.zones.apache.org. I followed the instructions and
> all seemed to go well until the build_velocity_site.sh script failed
> when trying to actually deploy the updated site:
>
> [INFO] [site:deploy]
> scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
> Using private key: /export/home/velocity/.ssh/id_rsa
> Executing command: /bin/bash -c 'ssh -i
> /export/home/velocity/.ssh/id_rsa -o "BatchMode yes"
> nbubna@people.apache.org "mkdir -p /w
> ww/velocity.apache.org/."'
>
> Permission denied (publickey,keyboard-interactive).
>
> scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnecting
> scpexe://people.apache.org/www/velocity.apache.org - Session: Disconnected
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Error uploading site
>
> Embedded error: Error performing commands for file transfer
> Exit code 255 - Permission denied (publickey,keyboard-interactive).
>
>
> this is far from the first time i've seen this. in fact, i recall
> spending much time fighting this same error in the past. i can't even
> remember if i succeeded though. either way, i'm sick of the maven
> site building headaches. what should be a fairly simple task has been
> an ordeal *for YEARS now*! the current process is brittle, unwieldy
> and worst of all, unmaintained. in contrast, there is the site
> process for VelocityTools:
>
> - uses DVSL (VTL-based, encourages DVSL maintenance)
> - deploy process is just:
> ant publish.docs
> ssh <user>@people.apache.org
> cd /www/velocity.apache.org/tools/devel (or release/<ver>)
> unzip -o ../docs.zip
> - and it works! no headaches!
>
> it's simple, low-maintenance, and doesn't make me want to throw
> things. granted, it may not have all the snazzy features Maven
> provides, but we're barely taking advantage of them anyway. so,
> consider this my warning that i intend to ditch this whole
> velocity-site thing. if any of you think this is a bad idea, by all
> means, please step up and maintain the velocity-site mess. i don't
> think anything less than that will change my mind, and it's doubtful
> whether even that would change it for long. i'm not sure when i'll
> get to making the change; i've little doubt that it will be more work
> than i imagine (especially figuring out what to do with those APT
> files); and i'm sure it won't be fun. but consider this my notice
> that i will no longer waste my time with this convoluted,
> temperamental Maven-crazy velocity-site stuff.
>
> p.s. help is welcome, and no one is allowed to complain about the lack
> of site updates unless they help, one way or another. ;-)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org