On Tue, Jul 8, 2008 at 10:15 AM, Paul Sundling <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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" >>>>>> [EMAIL PROTECTED] "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: [EMAIL PROTECTED] >>>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>>> >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
