[Lift] Re: Google search results
looks like google already removed all of the sub links which is kind of a bummer because it looks nice when you have those. On Mar 12, 5:41 pm, David Bernard david.bernard...@gmail.com wrote: It'll be done next week-end. On Thu, Mar 12, 2009 at 17:43, James Matlik james.mat...@gmail.com wrote: Why not have those links generate 301 redirects to the new site locations? It won't do much for people's existing bookmarks, but should allow search engines to update without the dead links. On Wed, Mar 11, 2009 at 6:50 PM, Timothy Perrett timo...@getintheloop.eu wrote: In short, no. We can't fix those results as they are generated by google not by our good selves. I belive this is because the wiki used to be on the lift TLD. Over time this will work itself out - appologies for any confussion this had caused. Cheers, Tim Sent from my iPhone On 11 Mar 2009, at 18:20, lmorroni la...@morroni.com wrote: Hello, I could not help but notice that the mini site map that gets returned on google when searching for lift framework has dead links. Can someone fix that? Larry --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Why does HelloWorld index.html contain a snippet rather than a complete XHTML page?
Why does HelloWorld index.html contain a snippet rather than a complete XHTML page? When I first saw the HelloWorld example I thought there must be a mistake, because the index.html file contains a snippet, while default.html contains what looked more like a complete XHTML page. Why doesn't lift initially reference a complete XHTML page and then pull in the snippet(s)? Is it to make it difficult/impossible for logic to creep into the view? Mal. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page?
Howdy, A Snippet is the bridge between the view and Scala code. In this example: lift:surround with=default at=content h2Welcome to your project!/h2 plift:HelloWorld.howdy //p /lift:surround The lift:HelloWorld.howdy / tag refers to the HelloWorld snippet which is is some Scala code in the HelloWorld class. Note the lift:surround tag. This surrounds its body with a template called default. The default.html file is located in the templates-hidden directory (it can be located elsewhere, but that's the convention). It has all the stuff in it like head and style and menus. This makes it possible to change the look of a large part of your site by changing the template rather than each page. Thanks, David On Fri, Mar 13, 2009 at 4:30 AM, mal3 malcolm.gor...@gmail.com wrote: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page? When I first saw the HelloWorld example I thought there must be a mistake, because the index.html file contains a snippet, while default.html contains what looked more like a complete XHTML page. Why doesn't lift initially reference a complete XHTML page and then pull in the snippet(s)? Is it to make it difficult/impossible for logic to creep into the view? Mal. -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Slash and burn
It would be advantageous for me, given the way I organize my sites, if requests for /page were served the same way as requests for /page/, or at least /page redirected to /page/. Is there an easy way to do this? Thanks, Chas. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Required goal not found: archetype:generate
No, its not a typo in the PDF. I just got it mixed up when typing the query. Erik On Mar 13, 1:50 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: Is that a typo in the PDF? If so, I'll fix it. Derek On Thu, Mar 12, 2009 at 2:36 PM, Alexander Kellett lypa...@gmail.comwrote: Few hours of playing with maven (multiple versions) and getting increasingly annoyed by it... and I suddenly revisited this part of the command: -DarchetypeGroupId:net.liftweb : should be =! Works just fine after that change :) Alex On Thu, Mar 12, 2009 at 6:34 PM, TylerWeir tyler.w...@gmail.com wrote: o, k. Since I'm getting the same error and I'm unsure why, try this on: mvn -e archetype:generate then you'll get a list mvn can make for you. lift-blank is # 32. You then fill bits and pieces yourself like this: Choose a number: (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/26/27/28/29/30/31/32/33/34/35/36/37/38/39/40/41/42) 16: : 32 [INFO] artifact net.liftweb:lift-archetype-blank: checking for updates from lift-archetype-blank-repo Define value for groupId: : ca.tylerweir Define value for artifactId: : HelloWorld Define value for version: 1.0-SNAPSHOT: : Define value for package: ca.tylerweir: : Give that a shot. On Mar 12, 1:20 pm, erik.fris...@googlemail.com erik.fris...@googlemail.com wrote: You are indeed right, my PDF was outdated. I have to admit though I have no clue how that happened, I downloaded it today. Anyway, I ran the following command: mvn archetype:generate -U \ -DarchetypeGroupId:net.liftweb \ -DarchetypeArtifactId=lift-archetype-blank \ -DarchetypeVersion=1.0 \ -DremoteRepositories=http://scala-tools.org/repo-releases\ -DgroupId=demo.helloworld \ -DartifactId=helloworld \ -Dversion=1.0-SNAPSHOT Now I get this error: The desired archetype does not exist (org.apache.maven.archetypes:lift- archetype-blank:1.0) Before I run the error I again deleted the .m2. Thanks for the help, got us a little closer to the solution. Is there something else I can try to get this to work? Erik P.S. If I ever get to see the BUILD SUCCESSFUL I will pop me a cold one and celebrate... On Mar 13, 4:09 am, TylerWeir tyler.w...@gmail.com wrote: Grab the PDF again, looks like you have the slightly older one with a version typo. Run this badboy: mvn archetype:generate -U \ -DarchetypeGroupId=net.liftweb \ -DarchetypeArtifactId=lift-archetype-blank \ -DarchetypeVersion=1.0 \ -DremoteRepositories=http://scala-tools.org/repo-releases\ -DgroupId=demo.helloworld \ -DartifactId=helloworld \ -Dversion=1.0-SNAPSHOT Ty On Mar 12, 1:00 pm, erik.fris...@googlemail.com erik.fris...@googlemail.com wrote: Hi again, I figured this one out. During some fixing I unwittingly overwrote my .bash_profile, reverting maven to the 2.0.6 version. I am running Leopard. I don't get this error anymoreyou guessed it, I get another. Now I get this: The desired archetype does not exist (org.apache.maven.archetypes:lift- archetype-blank:0.10) I can post the stacktrace if it is of help, I exclude it for now so this post remains somewhat readable. I am so desperately trying to get this working to play around with the framework, but so far this has been very depressing. I would greatly appreciate any hints or tips what might be going wrong. mvn --version prints out this: Maven version: 2.0.10 Java version: 1.5.0_16 OS name: mac os x version: 10.5.6 arch: i386 Family: unix --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Required goal not found: archetype:generate
On Fri, Mar 13, 2009 at 10:52 AM, erik.fris...@googlemail.com erik.fris...@googlemail.com wrote: No, its not a typo in the PDF. I just got it mixed up when typing the query. Just as a point of order, I'm glad that you stuck with the thread and didn't get too frustrated. I'm glad we could help get you to success. Thanks for sticking with Lift and I hope to see a Lift app that you build and I hope that you can lend a hand to the next person that's flumoxed by the Maven command line, whether it's a Maven challenge, a Lift documentation challenge, or a typing challenge. Thanks, David Erik On Mar 13, 1:50 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: Is that a typo in the PDF? If so, I'll fix it. Derek On Thu, Mar 12, 2009 at 2:36 PM, Alexander Kellett lypa...@gmail.com wrote: Few hours of playing with maven (multiple versions) and getting increasingly annoyed by it... and I suddenly revisited this part of the command: -DarchetypeGroupId:net.liftweb : should be =! Works just fine after that change :) Alex On Thu, Mar 12, 2009 at 6:34 PM, TylerWeir tyler.w...@gmail.com wrote: o, k. Since I'm getting the same error and I'm unsure why, try this on: mvn -e archetype:generate then you'll get a list mvn can make for you. lift-blank is # 32. You then fill bits and pieces yourself like this: Choose a number: (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/26/27/28/29/30/31/32/33/34/35/36/37/38/39/40/41/42) 16: : 32 [INFO] artifact net.liftweb:lift-archetype-blank: checking for updates from lift-archetype-blank-repo Define value for groupId: : ca.tylerweir Define value for artifactId: : HelloWorld Define value for version: 1.0-SNAPSHOT: : Define value for package: ca.tylerweir: : Give that a shot. On Mar 12, 1:20 pm, erik.fris...@googlemail.com erik.fris...@googlemail.com wrote: You are indeed right, my PDF was outdated. I have to admit though I have no clue how that happened, I downloaded it today. Anyway, I ran the following command: mvn archetype:generate -U \ -DarchetypeGroupId:net.liftweb \ -DarchetypeArtifactId=lift-archetype-blank \ -DarchetypeVersion=1.0 \ -DremoteRepositories=http://scala-tools.org/repo-releases\ -DgroupId=demo.helloworld \ -DartifactId=helloworld \ -Dversion=1.0-SNAPSHOT Now I get this error: The desired archetype does not exist (org.apache.maven.archetypes:lift- archetype-blank:1.0) Before I run the error I again deleted the .m2. Thanks for the help, got us a little closer to the solution. Is there something else I can try to get this to work? Erik P.S. If I ever get to see the BUILD SUCCESSFUL I will pop me a cold one and celebrate... On Mar 13, 4:09 am, TylerWeir tyler.w...@gmail.com wrote: Grab the PDF again, looks like you have the slightly older one with a version typo. Run this badboy: mvn archetype:generate -U \ -DarchetypeGroupId=net.liftweb \ -DarchetypeArtifactId=lift-archetype-blank \ -DarchetypeVersion=1.0 \ -DremoteRepositories=http://scala-tools.org/repo-releases\ -DgroupId=demo.helloworld \ -DartifactId=helloworld \ -Dversion=1.0-SNAPSHOT Ty On Mar 12, 1:00 pm, erik.fris...@googlemail.com erik.fris...@googlemail.com wrote: Hi again, I figured this one out. During some fixing I unwittingly overwrote my .bash_profile, reverting maven to the 2.0.6 version. I am running Leopard. I don't get this error anymoreyou guessed it, I get another. Now I get this: The desired archetype does not exist (org.apache.maven.archetypes:lift- archetype-blank:0.10) I can post the stacktrace if it is of help, I exclude it for now so this post remains somewhat readable. I am so desperately trying to get this working to play around with the framework, but so far this has been very depressing. I would greatly appreciate any hints or tips what might be going wrong. mvn --version prints out this: Maven version: 2.0.10 Java version: 1.5.0_16 OS name: mac os x version: 10.5.6 arch: i386 Family: unix -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Archetype Compile Problems
I tried it on a different computer now and everything worked perfectly. Now it's on me to find the differences. As there is no scala installed (no %scala_home% set) on the good one, am I wonder if the maven-scala-plugin uses its internal scala-compiler or relies on the system-wide one? Thanks for the help so far! On 8 Mrz., 23:58, johannes johannes.schu...@gmail.com wrote: Thank you very much, I'll try this tomorow and see what happens. I love the way of starting an embedded jetty as its usual in Wicket Demo WebApps, though, but I'll try everything reduced to get it working. Oh and yes, now i searched a littl bilt and found out about the moderation, sorry for posting twice-twice! On 8 Mrz., 21:33, David Bernard david.bernard...@gmail.com wrote: Hi, Have you try to force the version of jetty (and of the plugin to 6.1.14). RunWebApp class is only provide to help you run webapp for IDE/Editor (for test and debug). it's not required so you could remove it, if you don't need this feature. LiftConsole need the scala-compiler to run, if you don't use it, remove LiftConsole and the dependency (if you need it later, you'll copy them you a new project) The list is moderated (only against spam) = some delay. /davidB On Sun, Mar 8, 2009 at 18:35, johannes johannes.schu...@gmail.com wrote: Well I have 2.7.3 final installed on command line and used an newer version with the scala-eclipse-plugin, both gave me the same error. The pom has 2.7.3 as a property as it's ne 1.0 archetype... This must be something really simple if i look at the error msg..somehow it doesn't seem to include the scala-compiler.jar. Or is this dependency not used for regular compiling anyway? In the pom there's a commen for lift console..so this might be a hint that my scala installation is somehow messed up. Sorry for the confusing description but i got no clue where to start searching: does the default-scala-runtime compile the files or some internal compiler that is brought in by the maven plugin? On 8 Mrz., 13:11, TylerWeir tyler.w...@gmail.com wrote: Which version of scala do you have? Type scala -version on the commandline. If you're using Lift 1.0, you'll need scala 2.7.3. In your pom.xml file, look for scala.version. Tyler On Mar 8, 4:51 am, johannes johannes.schu...@gmail.com wrote: Hi all, I wanted to get started with lift this week, but after 4 nights of struggling with building one of the archetypes (e.g. the helloworld example) I don't know any further The error I get always is: [WARNING] Exception in thread main java.lang.NoClassDefFoundError: scala/tools/nsc/symtab/SymbolTable I first thought it was related to using eclipse, but the error also occurs using cli. I used the updated archetype definition found in a recent thread here. Any ideas on that? This doesn't seem like the bug in this file discussed in another thread here. I also tried multiple versions of jetty, though the problems seem to be related to the scala- compiler.jar. This jar is in the repository though Has anyone encountered a similar problem? Cheers, Johannes P.S.: Where did the first msg go?! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Slash and burn
Hmmm. I thought that this was what normally happened with most web servers (Jetty included). Are you using SiteMap, by any chance? What is the difference that you see between a response for /page and /page/ ? Derek On Fri, Mar 13, 2009 at 4:33 AM, Charles F. Munat c...@munat.com wrote: It would be advantageous for me, given the way I organize my sites, if requests for /page were served the same way as requests for /page/, or at least /page redirected to /page/. Is there an easy way to do this? Thanks, Chas. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Objections to merging jpa archetype?
Would anyone like to look at the jpaarchetype branch before I merge it? Derek --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Objections to merging jpa archetype?
Go for it. On Fri, Mar 13, 2009 at 3:09 PM, Derek Chen-Becker dchenbec...@gmail.comwrote: Would anyone like to look at the jpaarchetype branch before I merge it? Derek -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Objections to merging jpa archetype?
What version of Maven are you using? I'm getting the following errors: knuttyco...@knuttycombe-ubuntu:~/tmp$ mvn -DarchetypeCatalog=local archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for project - skipping [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): 1 Define value for groupId: : com.gaiam.gcsi Define value for artifactId: : jpa-lift Define value for version: 1.0-SNAPSHOT: : Define value for package: : com.gaiam.gcsi Confirm properties configuration: groupId: com.gaiam.gcsi artifactId: jpa-lift version: 1.0-SNAPSHOT package: com.gaiam.gcsi Y: : Y [INFO] [INFO] Using following parameters for creating OldArchetype: lift-jpa-archetype:0.11-SNAPSHOT [INFO] [INFO] Parameter: groupId, Value: com.gaiam.gcsi [INFO] Parameter: packageName, Value: com.gaiam.gcsi [INFO] Parameter: package, Value: com.gaiam.gcsi [INFO] Parameter: artifactId, Value: jpa-lift [INFO] Parameter: basedir, Value: /home/knuttycombe/tmp [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] * End of debug info from resources from generated POM *** [ERROR] ResourceManager : unable to find resource 'archetype-resources/webapp/src/main/webapp/templates-hidden/default.html' in any resource loader. [ERROR] Failed to generate project from the old archetype org.apache.maven.archetype.exception.ArchetypeGenerationFailure: Failed to generate project from the old archetype at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processOldArchetype(DefaultArchetypeGenerator.java:272) at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:145) at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:290) at org.apache.maven.archetype.DefaultArchetype.generateProjectFromArchetype(DefaultArchetype.java:75) at org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:185) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.archetype.old.ArchetypeTemplateProcessingException: Error merging velocity templates at
[Lift] Re: Objections to merging jpa archetype?
de...@rocky:/home/software/liftbook$ mvn -v Maven version: 2.0.9 Java version: 1.6.0_11 OS name: linux version: 2.6.27-11-generic arch: amd64 Family: unix This line in your output concerns me: [INFO] Using following parameters for creating OldArchetype:lift-jpa-archetype:0.11-SNAPSHOT The version in my archetype is 1.1-SNAPSHOT, so I wonder if you're getting an older version in your repo. Could you try nuking your .m2/repo and see if you still get the same error? Derek On Fri, Mar 13, 2009 at 9:38 AM, Kris Nuttycombe kris.nuttyco...@gmail.comwrote: What version of Maven are you using? I'm getting the following errors: knuttyco...@knuttycombe-ubuntu:~/tmp$ mvn -DarchetypeCatalog=local archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for project - skipping [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): 1 Define value for groupId: : com.gaiam.gcsi Define value for artifactId: : jpa-lift Define value for version: 1.0-SNAPSHOT: : Define value for package: : com.gaiam.gcsi Confirm properties configuration: groupId: com.gaiam.gcsi artifactId: jpa-lift version: 1.0-SNAPSHOT package: com.gaiam.gcsi Y: : Y [INFO] [INFO] Using following parameters for creating OldArchetype: lift-jpa-archetype:0.11-SNAPSHOT [INFO] [INFO] Parameter: groupId, Value: com.gaiam.gcsi [INFO] Parameter: packageName, Value: com.gaiam.gcsi [INFO] Parameter: package, Value: com.gaiam.gcsi [INFO] Parameter: artifactId, Value: jpa-lift [INFO] Parameter: basedir, Value: /home/knuttycombe/tmp [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] * End of debug info from resources from generated POM *** [ERROR] ResourceManager : unable to find resource 'archetype-resources/webapp/src/main/webapp/templates-hidden/default.html' in any resource loader. [ERROR] Failed to generate project from the old archetype org.apache.maven.archetype.exception.ArchetypeGenerationFailure: Failed to generate project from the old archetype at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processOldArchetype(DefaultArchetypeGenerator.java:272) at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:145) at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:290) at org.apache.maven.archetype.DefaultArchetype.generateProjectFromArchetype(DefaultArchetype.java:75) at org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:185) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[Lift] Re: Slash and burn
Derek, /page is parsed to List(page) and /page/ is parsed to List(page, index). Unfortunately, the rewrites are applied before the sitemap is in scope, so we can't consult the sitemap during rewrite, but I think there may be a way to write a DispatchPF to intercept List(xxx) and redirect to List(xxx, index) if that is a legal page. But, my editor will kill me if I don't get Chapter 5, draft 2 done, so I must stop yack shaving/helping people on this list and get back to work. :-) Thanks, David On Fri, Mar 13, 2009 at 2:27 PM, Derek Chen-Becker dchenbec...@gmail.comwrote: Hmmm. I thought that this was what normally happened with most web servers (Jetty included). Are you using SiteMap, by any chance? What is the difference that you see between a response for /page and /page/ ? Derek On Fri, Mar 13, 2009 at 4:33 AM, Charles F. Munat c...@munat.com wrote: It would be advantageous for me, given the way I organize my sites, if requests for /page were served the same way as requests for /page/, or at least /page redirected to /page/. Is there an easy way to do this? Thanks, Chas. -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Slash and burn
Within Lift, /page does what it says on the tin, whilst /page/ actually works out as: /page/index IMO, this is good. If you want them to be the same, I think you could either do a rewrite to the same content (if memory serves there is also a boolean option for defining if your using the slash or not?) I'm pretty sure it matters not of you are or are not using site map at this process is part of lifts request handling. Does that help? Cheers, Tim Sent from my iPhone On 13 Mar 2009, at 14:27, Derek Chen-Becker dchenbec...@gmail.com wrote: Hmmm. I thought that this was what normally happened with most web servers (Jetty included). Are you using SiteMap, by any chance? What is the difference that you see between a response for /page and / page/ ? Derek On Fri, Mar 13, 2009 at 4:33 AM, Charles F. Munat c...@munat.com wrote: It would be advantageous for me, given the way I organize my sites, if requests for /page were served the same way as requests for /page/, or at least /page redirected to /page/. Is there an easy way to do this? Thanks, Chas. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Objections to merging jpa archetype?
How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to the lift-archetype-jpa-basic pom.xml to get it to install: diff --git a/lift-archetype-jpa-basic/pom.xml b/lift-archetype-jpa-basic/pom.xml index 453e2b3..fc0cf8c 100644 --- a/lift-archetype-jpa-basic/pom.xml +++ b/lift-archetype-jpa-basic/pom.xml @@ -7,6 +7,7 @@ relativePath../pom.xml/relativePath /parent artifactIdlift-archetype-jpa-basic/artifactId + packagingmaven-archetype/packaging name${project.artifactId}/name descriptionArchetype - blank JPA project for Lift/description properties @@ -14,10 +15,18 @@ maven.test.skiptrue/maven.test.skip /properties build +extensions + extension +groupIdorg.apache.maven.archetype/groupId +artifactIdarchetype-packaging/artifactId +version2.0-alpha-4/version + /extension +/extensions plugins plugin artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4/version +extensionstrue/extensions configuration archetypeArtifactId${project.artifactId}/archetypeArtifactId archetypeGroupId${project.groupId}/archetypeGroupId After that, the archetype installed and I was able to generate it correctly. I have not yet tested the resulting application, though. Kris On Fri, Mar 13, 2009 at 9:46 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: de...@rocky:/home/software/liftbook$ mvn -v Maven version: 2.0.9 Java version: 1.6.0_11 OS name: linux version: 2.6.27-11-generic arch: amd64 Family: unix This line in your output concerns me: [INFO] Using following parameters for creating OldArchetype:lift-jpa-archetype:0.11-SNAPSHOT The version in my archetype is 1.1-SNAPSHOT, so I wonder if you're getting an older version in your repo. Could you try nuking your .m2/repo and see if you still get the same error? Derek On Fri, Mar 13, 2009 at 9:38 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: What version of Maven are you using? I'm getting the following errors: knuttyco...@knuttycombe-ubuntu:~/tmp$ mvn -DarchetypeCatalog=local archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO] task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for project - skipping [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): 1 Define value for groupId: : com.gaiam.gcsi Define value for artifactId: : jpa-lift Define value for version: 1.0-SNAPSHOT: : Define value for package: : com.gaiam.gcsi Confirm properties configuration: groupId: com.gaiam.gcsi artifactId: jpa-lift version: 1.0-SNAPSHOT package: com.gaiam.gcsi Y: : Y [INFO] [INFO] Using following parameters for creating OldArchetype: lift-jpa-archetype:0.11-SNAPSHOT [INFO] [INFO] Parameter: groupId, Value: com.gaiam.gcsi [INFO] Parameter: packageName, Value: com.gaiam.gcsi [INFO] Parameter: package, Value: com.gaiam.gcsi [INFO] Parameter: artifactId, Value: jpa-lift [INFO] Parameter: basedir, Value: /home/knuttycombe/tmp [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] * End of debug info from resources from generated POM *** [ERROR] ResourceManager : unable to find resource 'archetype-resources/webapp/src/main/webapp/templates-hidden/default.html' in any resource loader. [ERROR] Failed to generate project from the old archetype org.apache.maven.archetype.exception.ArchetypeGenerationFailure: Failed to generate project from the old archetype at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processOldArchetype(DefaultArchetypeGenerator.java:272) at
[Lift] corrections for lift book and starting with lift guide
My post didn't go through to the other group, and one issue is with the official starting with lift guide on the lift site anyway. In the lift book under section 1.3 -DarchetypeVersion=0.9 \ can be changed to 1.0 I ran the command from the book and maven downloaded scala 2.7.1 for some reason. I eventually deleted the helloword folder, my home/.m2 folder and started all over and scala 2.7.3 was finally downloaded correctly. Another issue is extra spaces after the backslash (\) at the end of lines. I copied the maven command from section 2.2 in the 'starting with lift' guide: http://liftweb.net/docs/getting_started/mod_master.html and maven barfed this out. It was because of the extra spaces at the ends of lines. Apparently only the HTML version of the book had the extra spaces, not the pdf. java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.AbstractStringBuilder.setLength(AbstractStringBuilder.java: 143) at java.lang.StringBuffer.setLength(StringBuffer.java:153) at org.apache.maven.cli.MavenCli$CLIManager.cleanArgs(MavenCli.java: 824) at org.apache.maven.cli.MavenCli$CLIManager.parse(MavenCli.java:777) at org.apache.maven.cli.MavenCli.main(MavenCli.java:103) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java: 315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java: 430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) ./newmaven.sh: line 3: -DarchetypeGroupId=net.liftweb: command not found ./newmaven.sh: line 4: -DarchetypeArtifactId=lift-archetype-basic: command not found ./newmaven.sh: line 5: -DarchetypeVersion=1.0: command not found ./newmaven.sh: line 6: -DremoteRepositories=http://scala-tools.org/repo-releases: No such file or directory ./newmaven.sh: line 7: -DgroupId=com.liftworkshop: command not found ./newmaven.sh: line 8: -DartifactId=todo: command not found ./newmaven.sh: line 9: -Dversion=0.1-SNAPSHOT: command not found java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.AbstractStringBuilder.setLength(AbstractStringBuilder.java: 143) at java.lang.StringBuffer.setLength(StringBuffer.java:153) at org.apache.maven.cli.MavenCli$CLIManager.cleanArgs(MavenCli.java: 824) at org.apache.maven.cli.MavenCli$CLIManager.parse(MavenCli.java:777) at org.apache.maven.cli.MavenCli.main(MavenCli.java:103) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java: 315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java: 430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) ./newmaven.sh: line 3: -DarchetypeGroupId=net.liftweb: command not found ./newmaven.sh: line 4: -DarchetypeArtifactId=lift-archetype-basic: command not found ./newmaven.sh: line 5: -DarchetypeVersion=1.0: command not found ./newmaven.sh: line 6: -DremoteRepositories=http://scala-tools.org/repo-releases: No such file or directory ./newmaven.sh: line 7: -DgroupId=com.liftworkshop: command not found ./newmaven.sh: line 8: -DartifactId=todo: command not found ./newmaven.sh: line 9: -Dversion=0.1-SNAPSHOT: command not found --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Objections to merging jpa archetype?
Ah, I think I missed that part of the POM. Let me fix that and commit the changes and then we can re-test. Thanks! Derek On Fri, Mar 13, 2009 at 11:11 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to the lift-archetype-jpa-basic pom.xml to get it to install: diff --git a/lift-archetype-jpa-basic/pom.xml b/lift-archetype-jpa-basic/pom.xml index 453e2b3..fc0cf8c 100644 --- a/lift-archetype-jpa-basic/pom.xml +++ b/lift-archetype-jpa-basic/pom.xml @@ -7,6 +7,7 @@ relativePath../pom.xml/relativePath /parent artifactIdlift-archetype-jpa-basic/artifactId + packagingmaven-archetype/packaging name${project.artifactId}/name descriptionArchetype - blank JPA project for Lift/description properties @@ -14,10 +15,18 @@ maven.test.skiptrue/maven.test.skip /properties build +extensions + extension +groupIdorg.apache.maven.archetype/groupId +artifactIdarchetype-packaging/artifactId +version2.0-alpha-4/version + /extension +/extensions plugins plugin artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4/version +extensionstrue/extensions configuration archetypeArtifactId${project.artifactId}/archetypeArtifactId archetypeGroupId${project.groupId}/archetypeGroupId After that, the archetype installed and I was able to generate it correctly. I have not yet tested the resulting application, though. Kris On Fri, Mar 13, 2009 at 9:46 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: de...@rocky:/home/software/liftbook$ mvn -v Maven version: 2.0.9 Java version: 1.6.0_11 OS name: linux version: 2.6.27-11-generic arch: amd64 Family: unix This line in your output concerns me: [INFO] Using following parameters for creating OldArchetype:lift-jpa-archetype:0.11-SNAPSHOT The version in my archetype is 1.1-SNAPSHOT, so I wonder if you're getting an older version in your repo. Could you try nuking your .m2/repo and see if you still get the same error? Derek On Fri, Mar 13, 2009 at 9:38 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: What version of Maven are you using? I'm getting the following errors: knuttyco...@knuttycombe-ubuntu:~/tmp$ mvn -DarchetypeCatalog=local archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for project - skipping [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): 1 Define value for groupId: : com.gaiam.gcsi Define value for artifactId: : jpa-lift Define value for version: 1.0-SNAPSHOT: : Define value for package: : com.gaiam.gcsi Confirm properties configuration: groupId: com.gaiam.gcsi artifactId: jpa-lift version: 1.0-SNAPSHOT package: com.gaiam.gcsi Y: : Y [INFO] [INFO] Using following parameters for creating OldArchetype: lift-jpa-archetype:0.11-SNAPSHOT [INFO] [INFO] Parameter: groupId, Value: com.gaiam.gcsi [INFO] Parameter: packageName, Value: com.gaiam.gcsi [INFO] Parameter: package, Value: com.gaiam.gcsi [INFO] Parameter: artifactId, Value: jpa-lift [INFO] Parameter: basedir, Value: /home/knuttycombe/tmp [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] * End of debug info from resources from generated POM *** [ERROR] ResourceManager : unable to find resource 'archetype-resources/webapp/src/main/webapp/templates-hidden/default.html' in any resource loader. [ERROR] Failed to generate project from the old archetype
[Lift] Re: Objections to merging jpa archetype?
Actually, I see that you did that against git. Can you commit your changes? Thanks, Derek On Fri, Mar 13, 2009 at 11:40 AM, Derek Chen-Becker dchenbec...@gmail.comwrote: Ah, I think I missed that part of the POM. Let me fix that and commit the changes and then we can re-test. Thanks! Derek On Fri, Mar 13, 2009 at 11:11 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to the lift-archetype-jpa-basic pom.xml to get it to install: diff --git a/lift-archetype-jpa-basic/pom.xml b/lift-archetype-jpa-basic/pom.xml index 453e2b3..fc0cf8c 100644 --- a/lift-archetype-jpa-basic/pom.xml +++ b/lift-archetype-jpa-basic/pom.xml @@ -7,6 +7,7 @@ relativePath../pom.xml/relativePath /parent artifactIdlift-archetype-jpa-basic/artifactId + packagingmaven-archetype/packaging name${project.artifactId}/name descriptionArchetype - blank JPA project for Lift/description properties @@ -14,10 +15,18 @@ maven.test.skiptrue/maven.test.skip /properties build +extensions + extension +groupIdorg.apache.maven.archetype/groupId +artifactIdarchetype-packaging/artifactId +version2.0-alpha-4/version + /extension +/extensions plugins plugin artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4/version +extensionstrue/extensions configuration archetypeArtifactId${project.artifactId}/archetypeArtifactId archetypeGroupId${project.groupId}/archetypeGroupId After that, the archetype installed and I was able to generate it correctly. I have not yet tested the resulting application, though. Kris On Fri, Mar 13, 2009 at 9:46 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: de...@rocky:/home/software/liftbook$ mvn -v Maven version: 2.0.9 Java version: 1.6.0_11 OS name: linux version: 2.6.27-11-generic arch: amd64 Family: unix This line in your output concerns me: [INFO] Using following parameters for creating OldArchetype:lift-jpa-archetype:0.11-SNAPSHOT The version in my archetype is 1.1-SNAPSHOT, so I wonder if you're getting an older version in your repo. Could you try nuking your .m2/repo and see if you still get the same error? Derek On Fri, Mar 13, 2009 at 9:38 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: What version of Maven are you using? I'm getting the following errors: knuttyco...@knuttycombe-ubuntu:~/tmp$ mvn -DarchetypeCatalog=local archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for project - skipping [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): 1 Define value for groupId: : com.gaiam.gcsi Define value for artifactId: : jpa-lift Define value for version: 1.0-SNAPSHOT: : Define value for package: : com.gaiam.gcsi Confirm properties configuration: groupId: com.gaiam.gcsi artifactId: jpa-lift version: 1.0-SNAPSHOT package: com.gaiam.gcsi Y: : Y [INFO] [INFO] Using following parameters for creating OldArchetype: lift-jpa-archetype:0.11-SNAPSHOT [INFO] [INFO] Parameter: groupId, Value: com.gaiam.gcsi [INFO] Parameter: packageName, Value: com.gaiam.gcsi [INFO] Parameter: package, Value: com.gaiam.gcsi [INFO] Parameter: artifactId, Value: jpa-lift [INFO] Parameter: basedir, Value: /home/knuttycombe/tmp [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] * End of debug info from resources from generated POM *** [ERROR] ResourceManager : unable to find resource
[Lift] Re: Slash and burn
I think I was confusing this with some other behavior of SiteMap, hence my question. I think it would be good to allow some really pre-processing of the URL. Would it useful to allow the user to control it, or do you think it would be better to just make it implicit? Something like LiftRules.pathRewrite.append { case List(parse) = List(parse, index) ... } I'm doing a lot of wand-waving there, but does that seem like a reasonable approach from the user side of things? Or maybe make a subclass of RewriteResponse that just tells Lift to modify the path but change nothing else? case class ModifiedPath (path : List[String]) extends RewriteResponse(...) Derek On Fri, Mar 13, 2009 at 10:51 AM, Timothy Perrett timo...@getintheloop.euwrote: Within Lift, /page does what it says on the tin, whilst /page/ actually works out as: /page/index IMO, this is good. If you want them to be the same, I think you could either do a rewrite to the same content (if memory serves there is also a boolean option for defining if your using the slash or not?) I'm pretty sure it matters not of you are or are not using site map at this process is part of lifts request handling. Does that help? Cheers, Tim Sent from my iPhone On 13 Mar 2009, at 14:27, Derek Chen-Becker dchenbec...@gmail.com wrote: Hmmm. I thought that this was what normally happened with most web servers (Jetty included). Are you using SiteMap, by any chance? What is the difference that you see between a response for /page and /page/ ? Derek On Fri, Mar 13, 2009 at 4:33 AM, Charles F. Munat c...@munat.com c...@munat.com wrote: It would be advantageous for me, given the way I organize my sites, if requests for /page were served the same way as requests for /page/, or at least /page redirected to /page/. Is there an easy way to do this? Thanks, Chas. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Objections to merging jpa archetype?
Done. On Fri, Mar 13, 2009 at 10:41 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Actually, I see that you did that against git. Can you commit your changes? Thanks, Derek On Fri, Mar 13, 2009 at 11:40 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Ah, I think I missed that part of the POM. Let me fix that and commit the changes and then we can re-test. Thanks! Derek On Fri, Mar 13, 2009 at 11:11 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to the lift-archetype-jpa-basic pom.xml to get it to install: diff --git a/lift-archetype-jpa-basic/pom.xml b/lift-archetype-jpa-basic/pom.xml index 453e2b3..fc0cf8c 100644 --- a/lift-archetype-jpa-basic/pom.xml +++ b/lift-archetype-jpa-basic/pom.xml @@ -7,6 +7,7 @@ relativePath../pom.xml/relativePath /parent artifactIdlift-archetype-jpa-basic/artifactId + packagingmaven-archetype/packaging name${project.artifactId}/name descriptionArchetype - blank JPA project for Lift/description properties @@ -14,10 +15,18 @@ maven.test.skiptrue/maven.test.skip /properties build + extensions + extension + groupIdorg.apache.maven.archetype/groupId + artifactIdarchetype-packaging/artifactId + version2.0-alpha-4/version + /extension + /extensions plugins plugin artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4/version + extensionstrue/extensions configuration archetypeArtifactId${project.artifactId}/archetypeArtifactId archetypeGroupId${project.groupId}/archetypeGroupId After that, the archetype installed and I was able to generate it correctly. I have not yet tested the resulting application, though. Kris On Fri, Mar 13, 2009 at 9:46 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: de...@rocky:/home/software/liftbook$ mvn -v Maven version: 2.0.9 Java version: 1.6.0_11 OS name: linux version: 2.6.27-11-generic arch: amd64 Family: unix This line in your output concerns me: [INFO] Using following parameters for creating OldArchetype:lift-jpa-archetype:0.11-SNAPSHOT The version in my archetype is 1.1-SNAPSHOT, so I wonder if you're getting an older version in your repo. Could you try nuking your .m2/repo and see if you still get the same error? Derek On Fri, Mar 13, 2009 at 9:38 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: What version of Maven are you using? I'm getting the following errors: knuttyco...@knuttycombe-ubuntu:~/tmp$ mvn -DarchetypeCatalog=local archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO] task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for project - skipping [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): 1 Define value for groupId: : com.gaiam.gcsi Define value for artifactId: : jpa-lift Define value for version: 1.0-SNAPSHOT: : Define value for package: : com.gaiam.gcsi Confirm properties configuration: groupId: com.gaiam.gcsi artifactId: jpa-lift version: 1.0-SNAPSHOT package: com.gaiam.gcsi Y: : Y [INFO] [INFO] Using following parameters for creating OldArchetype: lift-jpa-archetype:0.11-SNAPSHOT [INFO] [INFO] Parameter: groupId, Value: com.gaiam.gcsi [INFO] Parameter: packageName, Value: com.gaiam.gcsi [INFO] Parameter: package, Value: com.gaiam.gcsi [INFO] Parameter: artifactId, Value: jpa-lift [INFO] Parameter: basedir, Value: /home/knuttycombe/tmp [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] * End of debug info from resources from generated POM
[Lift] Re: Slash and burn
Im pretty sure you could just do this with the existing infrastructure (RewritePF and DispatchPF) For instance, if Chas doesnt mind having two seperate resources, then he can easily use RewritePF to get the same content at two resource locations. Alternatively, he could just use a 301 redirect response in a dispatch call to get the appropriate resource - I've posted code to one of his questions about that before If memory serves. I think that should all be cool? Cant think of a good reason why this wouldnt work anyway :-) Cheers, Tim On Mar 13, 4:57 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: I think I was confusing this with some other behavior of SiteMap, hence my question. I think it would be good to allow some really pre-processing of the URL. Would it useful to allow the user to control it, or do you think it would be better to just make it implicit? Something like LiftRules.pathRewrite.append { case List(parse) = List(parse, index) ... } I'm doing a lot of wand-waving there, but does that seem like a reasonable approach from the user side of things? Or maybe make a subclass of RewriteResponse that just tells Lift to modify the path but change nothing else? case class ModifiedPath (path : List[String]) extends RewriteResponse(...) Derek On Fri, Mar 13, 2009 at 10:51 AM, Timothy Perrett timo...@getintheloop.euwrote: Within Lift, /page does what it says on the tin, whilst /page/ actually works out as: /page/index IMO, this is good. If you want them to be the same, I think you could either do a rewrite to the same content (if memory serves there is also a boolean option for defining if your using the slash or not?) I'm pretty sure it matters not of you are or are not using site map at this process is part of lifts request handling. Does that help? Cheers, Tim Sent from my iPhone On 13 Mar 2009, at 14:27, Derek Chen-Becker dchenbec...@gmail.com wrote: Hmmm. I thought that this was what normally happened with most web servers (Jetty included). Are you using SiteMap, by any chance? What is the difference that you see between a response for /page and /page/ ? Derek On Fri, Mar 13, 2009 at 4:33 AM, Charles F. Munat c...@munat.com c...@munat.com wrote: It would be advantageous for me, given the way I organize my sites, if requests for /page were served the same way as requests for /page/, or at least /page redirected to /page/. Is there an easy way to do this? Thanks, Chas. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Objections to merging jpa archetype?
OK, I'll go ahead and merge with master. If I understand this whole process correctly, Hudson should build the new project and deploy it under snapshots on scala-tools.org. At that point we should be able to use the archetype:generate -DremoteRepository=http://scala-tools.org/repo-snapshotsto generate, correct? Derek On Fri, Mar 13, 2009 at 12:01 PM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: Done. On Fri, Mar 13, 2009 at 10:41 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Actually, I see that you did that against git. Can you commit your changes? Thanks, Derek On Fri, Mar 13, 2009 at 11:40 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Ah, I think I missed that part of the POM. Let me fix that and commit the changes and then we can re-test. Thanks! Derek On Fri, Mar 13, 2009 at 11:11 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to the lift-archetype-jpa-basic pom.xml to get it to install: diff --git a/lift-archetype-jpa-basic/pom.xml b/lift-archetype-jpa-basic/pom.xml index 453e2b3..fc0cf8c 100644 --- a/lift-archetype-jpa-basic/pom.xml +++ b/lift-archetype-jpa-basic/pom.xml @@ -7,6 +7,7 @@ relativePath../pom.xml/relativePath /parent artifactIdlift-archetype-jpa-basic/artifactId + packagingmaven-archetype/packaging name${project.artifactId}/name descriptionArchetype - blank JPA project for Lift/description properties @@ -14,10 +15,18 @@ maven.test.skiptrue/maven.test.skip /properties build +extensions + extension +groupIdorg.apache.maven.archetype/groupId +artifactIdarchetype-packaging/artifactId +version2.0-alpha-4/version + /extension +/extensions plugins plugin artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4/version +extensionstrue/extensions configuration archetypeArtifactId${project.artifactId}/archetypeArtifactId archetypeGroupId${project.groupId}/archetypeGroupId After that, the archetype installed and I was able to generate it correctly. I have not yet tested the resulting application, though. Kris On Fri, Mar 13, 2009 at 9:46 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: de...@rocky:/home/software/liftbook$ mvn -v Maven version: 2.0.9 Java version: 1.6.0_11 OS name: linux version: 2.6.27-11-generic arch: amd64 Family: unix This line in your output concerns me: [INFO] Using following parameters for creating OldArchetype:lift-jpa-archetype:0.11-SNAPSHOT The version in my archetype is 1.1-SNAPSHOT, so I wonder if you're getting an older version in your repo. Could you try nuking your .m2/repo and see if you still get the same error? Derek On Fri, Mar 13, 2009 at 9:38 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: What version of Maven are you using? I'm getting the following errors: knuttyco...@knuttycombe-ubuntu:~/tmp$ mvn -DarchetypeCatalog=local archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for project - skipping [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): 1 Define value for groupId: : com.gaiam.gcsi Define value for artifactId: : jpa-lift Define value for version: 1.0-SNAPSHOT: : Define value for package: : com.gaiam.gcsi Confirm properties configuration: groupId: com.gaiam.gcsi artifactId: jpa-lift version: 1.0-SNAPSHOT package: com.gaiam.gcsi Y: : Y [INFO] [INFO] Using following parameters for
[Lift] Re: Slash and burn
Well, treating a directory without a trailing slash (/path) as the directory + index (/path/index) is pretty standard behavior in web servers (Apache returns a 301 from the former to the latter), so I think something that requires less user intervention would be good. Perhaps at most we would want a boolean var on LiftRules to control the behavior. Derek On Fri, Mar 13, 2009 at 12:15 PM, Timothy Perrett timo...@getintheloop.euwrote: Im pretty sure you could just do this with the existing infrastructure (RewritePF and DispatchPF) For instance, if Chas doesnt mind having two seperate resources, then he can easily use RewritePF to get the same content at two resource locations. Alternatively, he could just use a 301 redirect response in a dispatch call to get the appropriate resource - I've posted code to one of his questions about that before If memory serves. I think that should all be cool? Cant think of a good reason why this wouldnt work anyway :-) Cheers, Tim On Mar 13, 4:57 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: I think I was confusing this with some other behavior of SiteMap, hence my question. I think it would be good to allow some really pre-processing of the URL. Would it useful to allow the user to control it, or do you think it would be better to just make it implicit? Something like LiftRules.pathRewrite.append { case List(parse) = List(parse, index) ... } I'm doing a lot of wand-waving there, but does that seem like a reasonable approach from the user side of things? Or maybe make a subclass of RewriteResponse that just tells Lift to modify the path but change nothing else? case class ModifiedPath (path : List[String]) extends RewriteResponse(...) Derek On Fri, Mar 13, 2009 at 10:51 AM, Timothy Perrett timo...@getintheloop.euwrote: Within Lift, /page does what it says on the tin, whilst /page/ actually works out as: /page/index IMO, this is good. If you want them to be the same, I think you could either do a rewrite to the same content (if memory serves there is also a boolean option for defining if your using the slash or not?) I'm pretty sure it matters not of you are or are not using site map at this process is part of lifts request handling. Does that help? Cheers, Tim Sent from my iPhone On 13 Mar 2009, at 14:27, Derek Chen-Becker dchenbec...@gmail.com wrote: Hmmm. I thought that this was what normally happened with most web servers (Jetty included). Are you using SiteMap, by any chance? What is the difference that you see between a response for /page and /page/ ? Derek On Fri, Mar 13, 2009 at 4:33 AM, Charles F. Munat c...@munat.com c...@munat.com wrote: It would be advantageous for me, given the way I organize my sites, if requests for /page were served the same way as requests for /page/, or at least /page redirected to /page/. Is there an easy way to do this? Thanks, Chas. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Objections to merging jpa archetype?
I actually haven't deployed an archetype onto a remote repository before, but it sounds right. Has ScalaJPA become publicly available on scala-tools yet? Kris On Fri, Mar 13, 2009 at 11:28 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: OK, I'll go ahead and merge with master. If I understand this whole process correctly, Hudson should build the new project and deploy it under snapshots on scala-tools.org. At that point we should be able to use the archetype:generate -DremoteRepository=http://scala-tools.org/repo-snapshots to generate, correct? Derek On Fri, Mar 13, 2009 at 12:01 PM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: Done. On Fri, Mar 13, 2009 at 10:41 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Actually, I see that you did that against git. Can you commit your changes? Thanks, Derek On Fri, Mar 13, 2009 at 11:40 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Ah, I think I missed that part of the POM. Let me fix that and commit the changes and then we can re-test. Thanks! Derek On Fri, Mar 13, 2009 at 11:11 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to the lift-archetype-jpa-basic pom.xml to get it to install: diff --git a/lift-archetype-jpa-basic/pom.xml b/lift-archetype-jpa-basic/pom.xml index 453e2b3..fc0cf8c 100644 --- a/lift-archetype-jpa-basic/pom.xml +++ b/lift-archetype-jpa-basic/pom.xml @@ -7,6 +7,7 @@ relativePath../pom.xml/relativePath /parent artifactIdlift-archetype-jpa-basic/artifactId + packagingmaven-archetype/packaging name${project.artifactId}/name descriptionArchetype - blank JPA project for Lift/description properties @@ -14,10 +15,18 @@ maven.test.skiptrue/maven.test.skip /properties build + extensions + extension + groupIdorg.apache.maven.archetype/groupId + artifactIdarchetype-packaging/artifactId + version2.0-alpha-4/version + /extension + /extensions plugins plugin artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4/version + extensionstrue/extensions configuration archetypeArtifactId${project.artifactId}/archetypeArtifactId archetypeGroupId${project.groupId}/archetypeGroupId After that, the archetype installed and I was able to generate it correctly. I have not yet tested the resulting application, though. Kris On Fri, Mar 13, 2009 at 9:46 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: de...@rocky:/home/software/liftbook$ mvn -v Maven version: 2.0.9 Java version: 1.6.0_11 OS name: linux version: 2.6.27-11-generic arch: amd64 Family: unix This line in your output concerns me: [INFO] Using following parameters for creating OldArchetype:lift-jpa-archetype:0.11-SNAPSHOT The version in my archetype is 1.1-SNAPSHOT, so I wonder if you're getting an older version in your repo. Could you try nuking your .m2/repo and see if you still get the same error? Derek On Fri, Mar 13, 2009 at 9:38 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: What version of Maven are you using? I'm getting the following errors: knuttyco...@knuttycombe-ubuntu:~/tmp$ mvn -DarchetypeCatalog=local archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO] task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for project - skipping [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): Choose archetype: 1: local - lift-jpa-archetype (lift-jpa-archetype) Choose a number: (1): 1 Define value for groupId: : com.gaiam.gcsi Define value for artifactId: : jpa-lift Define value for version: 1.0-SNAPSHOT: : Define value for package: : com.gaiam.gcsi Confirm properties
[Lift] Re: Objections to merging jpa archetype?
Darnit. It helps if I make the jpa archetype a module of the master lift project. Fixing now. Derek On Fri, Mar 13, 2009 at 12:52 PM, Derek Chen-Becker dchenbec...@gmail.comwrote: 1.0, baby! http://scala-tools.org/mvnsites/scalajpa/ I've been too busy to put up a nice blog entry on it, but it's on my todo list :( Derek On Fri, Mar 13, 2009 at 12:47 PM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: I actually haven't deployed an archetype onto a remote repository before, but it sounds right. Has ScalaJPA become publicly available on scala-tools yet? Kris On Fri, Mar 13, 2009 at 11:28 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: OK, I'll go ahead and merge with master. If I understand this whole process correctly, Hudson should build the new project and deploy it under snapshots on scala-tools.org. At that point we should be able to use the archetype:generate -DremoteRepository= http://scala-tools.org/repo-snapshots to generate, correct? Derek On Fri, Mar 13, 2009 at 12:01 PM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: Done. On Fri, Mar 13, 2009 at 10:41 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Actually, I see that you did that against git. Can you commit your changes? Thanks, Derek On Fri, Mar 13, 2009 at 11:40 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Ah, I think I missed that part of the POM. Let me fix that and commit the changes and then we can re-test. Thanks! Derek On Fri, Mar 13, 2009 at 11:11 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to the lift-archetype-jpa-basic pom.xml to get it to install: diff --git a/lift-archetype-jpa-basic/pom.xml b/lift-archetype-jpa-basic/pom.xml index 453e2b3..fc0cf8c 100644 --- a/lift-archetype-jpa-basic/pom.xml +++ b/lift-archetype-jpa-basic/pom.xml @@ -7,6 +7,7 @@ relativePath../pom.xml/relativePath /parent artifactIdlift-archetype-jpa-basic/artifactId + packagingmaven-archetype/packaging name${project.artifactId}/name descriptionArchetype - blank JPA project for Lift/description properties @@ -14,10 +15,18 @@ maven.test.skiptrue/maven.test.skip /properties build +extensions + extension +groupIdorg.apache.maven.archetype/groupId +artifactIdarchetype-packaging/artifactId +version2.0-alpha-4/version + /extension +/extensions plugins plugin artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4/version +extensionstrue/extensions configuration archetypeArtifactId${project.artifactId}/archetypeArtifactId archetypeGroupId${project.groupId}/archetypeGroupId After that, the archetype installed and I was able to generate it correctly. I have not yet tested the resulting application, though. Kris On Fri, Mar 13, 2009 at 9:46 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: de...@rocky:/home/software/liftbook$ mvn -v Maven version: 2.0.9 Java version: 1.6.0_11 OS name: linux version: 2.6.27-11-generic arch: amd64 Family: unix This line in your output concerns me: [INFO] Using following parameters for creating OldArchetype:lift-jpa-archetype:0.11-SNAPSHOT The version in my archetype is 1.1-SNAPSHOT, so I wonder if you're getting an older version in your repo. Could you try nuking your .m2/repo and see if you still get the same error? Derek On Fri, Mar 13, 2009 at 9:38 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: What version of Maven are you using? I'm getting the following errors: knuttyco...@knuttycombe-ubuntu:~/tmp$ mvn -DarchetypeCatalog=local archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for project - skipping [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:generate] [INFO]
[Lift] Re: Slash and burn
Hmmm, I see your point. Will have a noodle at the weekend and see what would be the best route. Cheers, Tim On 13/03/2009 17:45, Derek Chen-Becker dchenbec...@gmail.com wrote: Well, treating a directory without a trailing slash (/path) as the directory + index (/path/index) is pretty standard behavior in web servers (Apache returns a 301 from the former to the latter), so I think something that requires less user intervention would be good. Perhaps at most we would want a boolean var on LiftRules to control the behavior. Derek On Fri, Mar 13, 2009 at 12:15 PM, Timothy Perrett timo...@getintheloop.eu wrote: Im pretty sure you could just do this with the existing infrastructure (RewritePF and DispatchPF) For instance, if Chas doesnt mind having two seperate resources, then he can easily use RewritePF to get the same content at two resource locations. Alternatively, he could just use a 301 redirect response in a dispatch call to get the appropriate resource - I've posted code to one of his questions about that before If memory serves. I think that should all be cool? Cant think of a good reason why this wouldnt work anyway :-) Cheers, Tim On Mar 13, 4:57 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: I think I was confusing this with some other behavior of SiteMap, hence my question. I think it would be good to allow some really pre-processing of the URL. Would it useful to allow the user to control it, or do you think it would be better to just make it implicit? Something like LiftRules.pathRewrite.append { case List(parse) = List(parse, index) ... } I'm doing a lot of wand-waving there, but does that seem like a reasonable approach from the user side of things? Or maybe make a subclass of RewriteResponse that just tells Lift to modify the path but change nothing else? case class ModifiedPath (path : List[String]) extends RewriteResponse(...) Derek On Fri, Mar 13, 2009 at 10:51 AM, Timothy Perrett timo...@getintheloop.euwrote: Within Lift, /page does what it says on the tin, whilst /page/ actually works out as: /page/index IMO, this is good. If you want them to be the same, I think you could either do a rewrite to the same content (if memory serves there is also a boolean option for defining if your using the slash or not?) I'm pretty sure it matters not of you are or are not using site map at this process is part of lifts request handling. Does that help? Cheers, Tim Sent from my iPhone On 13 Mar 2009, at 14:27, Derek Chen-Becker dchenbec...@gmail.com wrote: Hmmm. I thought that this was what normally happened with most web servers (Jetty included). Are you using SiteMap, by any chance? What is the difference that you see between a response for /page and /page/ ? Derek On Fri, Mar 13, 2009 at 4:33 AM, Charles F. Munat c...@munat.com c...@munat.com wrote: It would be advantageous for me, given the way I organize my sites, if requests for /page were served the same way as requests for /page/, or at least /page redirected to /page/. Is there an easy way to do this? Thanks, Chas. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Objections to merging jpa archetype?
OK, it built and deployed. I just confirmed that you can create it with: mvn archetype:generate \ -DarchetypeRepository=http://scala-tools.org/repo-snapshots \ -DarchetypeGroupId=net.liftweb \ -DarchetypeArtifactId=lift-archetype-jpa-basic \ -DarchetypeVersion=1.1-SNAPSHOT Derek On Fri, Mar 13, 2009 at 12:54 PM, Derek Chen-Becker dchenbec...@gmail.comwrote: Darnit. It helps if I make the jpa archetype a module of the master lift project. Fixing now. Derek On Fri, Mar 13, 2009 at 12:52 PM, Derek Chen-Becker dchenbec...@gmail.com wrote: 1.0, baby! http://scala-tools.org/mvnsites/scalajpa/ I've been too busy to put up a nice blog entry on it, but it's on my todo list :( Derek On Fri, Mar 13, 2009 at 12:47 PM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: I actually haven't deployed an archetype onto a remote repository before, but it sounds right. Has ScalaJPA become publicly available on scala-tools yet? Kris On Fri, Mar 13, 2009 at 11:28 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: OK, I'll go ahead and merge with master. If I understand this whole process correctly, Hudson should build the new project and deploy it under snapshots on scala-tools.org. At that point we should be able to use the archetype:generate -DremoteRepository= http://scala-tools.org/repo-snapshots to generate, correct? Derek On Fri, Mar 13, 2009 at 12:01 PM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: Done. On Fri, Mar 13, 2009 at 10:41 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Actually, I see that you did that against git. Can you commit your changes? Thanks, Derek On Fri, Mar 13, 2009 at 11:40 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Ah, I think I missed that part of the POM. Let me fix that and commit the changes and then we can re-test. Thanks! Derek On Fri, Mar 13, 2009 at 11:11 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to the lift-archetype-jpa-basic pom.xml to get it to install: diff --git a/lift-archetype-jpa-basic/pom.xml b/lift-archetype-jpa-basic/pom.xml index 453e2b3..fc0cf8c 100644 --- a/lift-archetype-jpa-basic/pom.xml +++ b/lift-archetype-jpa-basic/pom.xml @@ -7,6 +7,7 @@ relativePath../pom.xml/relativePath /parent artifactIdlift-archetype-jpa-basic/artifactId + packagingmaven-archetype/packaging name${project.artifactId}/name descriptionArchetype - blank JPA project for Lift/description properties @@ -14,10 +15,18 @@ maven.test.skiptrue/maven.test.skip /properties build +extensions + extension +groupIdorg.apache.maven.archetype/groupId +artifactIdarchetype-packaging/artifactId +version2.0-alpha-4/version + /extension +/extensions plugins plugin artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4/version +extensionstrue/extensions configuration archetypeArtifactId${project.artifactId}/archetypeArtifactId archetypeGroupId${project.groupId}/archetypeGroupId After that, the archetype installed and I was able to generate it correctly. I have not yet tested the resulting application, though. Kris On Fri, Mar 13, 2009 at 9:46 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: de...@rocky:/home/software/liftbook$ mvn -v Maven version: 2.0.9 Java version: 1.6.0_11 OS name: linux version: 2.6.27-11-generic arch: amd64 Family: unix This line in your output concerns me: [INFO] Using following parameters for creating OldArchetype:lift-jpa-archetype:0.11-SNAPSHOT The version in my archetype is 1.1-SNAPSHOT, so I wonder if you're getting an older version in your repo. Could you try nuking your .m2/repo and see if you still get the same error? Derek On Fri, Mar 13, 2009 at 9:38 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: What version of Maven are you using? I'm getting the following errors: knuttyco...@knuttycombe-ubuntu:~/tmp$ mvn -DarchetypeCatalog=local archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for
[Lift] Re: Objections to merging jpa archetype?
Excellent! On Fri, Mar 13, 2009 at 12:55 PM, Derek Chen-Becker dchenbec...@gmail.com wrote: OK, it built and deployed. I just confirmed that you can create it with: mvn archetype:generate \ -DarchetypeRepository=http://scala-tools.org/repo-snapshots \ -DarchetypeGroupId=net.liftweb \ -DarchetypeArtifactId=lift-archetype-jpa-basic \ -DarchetypeVersion=1.1-SNAPSHOT Derek On Fri, Mar 13, 2009 at 12:54 PM, Derek Chen-Becker dchenbec...@gmail.com wrote: Darnit. It helps if I make the jpa archetype a module of the master lift project. Fixing now. Derek On Fri, Mar 13, 2009 at 12:52 PM, Derek Chen-Becker dchenbec...@gmail.com wrote: 1.0, baby! http://scala-tools.org/mvnsites/scalajpa/ I've been too busy to put up a nice blog entry on it, but it's on my todo list :( Derek On Fri, Mar 13, 2009 at 12:47 PM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: I actually haven't deployed an archetype onto a remote repository before, but it sounds right. Has ScalaJPA become publicly available on scala-tools yet? Kris On Fri, Mar 13, 2009 at 11:28 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: OK, I'll go ahead and merge with master. If I understand this whole process correctly, Hudson should build the new project and deploy it under snapshots on scala-tools.org. At that point we should be able to use the archetype:generate -DremoteRepository=http://scala-tools.org/repo-snapshots to generate, correct? Derek On Fri, Mar 13, 2009 at 12:01 PM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: Done. On Fri, Mar 13, 2009 at 10:41 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Actually, I see that you did that against git. Can you commit your changes? Thanks, Derek On Fri, Mar 13, 2009 at 11:40 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Ah, I think I missed that part of the POM. Let me fix that and commit the changes and then we can re-test. Thanks! Derek On Fri, Mar 13, 2009 at 11:11 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to the lift-archetype-jpa-basic pom.xml to get it to install: diff --git a/lift-archetype-jpa-basic/pom.xml b/lift-archetype-jpa-basic/pom.xml index 453e2b3..fc0cf8c 100644 --- a/lift-archetype-jpa-basic/pom.xml +++ b/lift-archetype-jpa-basic/pom.xml @@ -7,6 +7,7 @@ relativePath../pom.xml/relativePath /parent artifactIdlift-archetype-jpa-basic/artifactId + packagingmaven-archetype/packaging name${project.artifactId}/name descriptionArchetype - blank JPA project for Lift/description properties @@ -14,10 +15,18 @@ maven.test.skiptrue/maven.test.skip /properties build + extensions + extension + groupIdorg.apache.maven.archetype/groupId + artifactIdarchetype-packaging/artifactId + version2.0-alpha-4/version + /extension + /extensions plugins plugin artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4/version + extensionstrue/extensions configuration archetypeArtifactId${project.artifactId}/archetypeArtifactId archetypeGroupId${project.groupId}/archetypeGroupId After that, the archetype installed and I was able to generate it correctly. I have not yet tested the resulting application, though. Kris On Fri, Mar 13, 2009 at 9:46 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: de...@rocky:/home/software/liftbook$ mvn -v Maven version: 2.0.9 Java version: 1.6.0_11 OS name: linux version: 2.6.27-11-generic arch: amd64 Family: unix This line in your output concerns me: [INFO] Using following parameters for creating OldArchetype:lift-jpa-archetype:0.11-SNAPSHOT The version in my archetype is 1.1-SNAPSHOT, so I wonder if you're getting an older version in your repo. Could you try nuking your .m2/repo and see if you still get the same error? Derek On Fri, Mar 13, 2009 at 9:38 AM, Kris Nuttycombe kris.nuttyco...@gmail.com wrote: What version of Maven are you using? I'm getting the following errors: knuttyco...@knuttycombe-ubuntu:~/tmp$ mvn -DarchetypeCatalog=local archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO] task-segment: [archetype:generate] (aggregator-style) [INFO]
[Lift] Re: Slash and burn
Sorry, I've missed most of this discussion, but thank you for your responses. Hopefully, I'll be able to figure out what they mean after I get some coffee (I had a very late night working). I organize all my sites the same way. Names of items are expressed as directories. All pages are called index. So instead of this: /folks bob.html bill.html brent.html I have this: /folks /bob index.html /bill index.html /brent index.html One big advantage is that this works even if I later switch to a static HTML site, or a ruby site, or god-knows-what. And I can change index.html to index.php or index.xml or whatever and the URLs don't change. I learned this system ten years ago and it has served me very well. It seems that Lift used to serve /folks/ when /folks was called, but recently it stopped. It would be nice if it looked for a *file* with that name first, but then tried directories if no file was found. Is there a downside to that? Sorry about the subject line. Couldn't resist. Chas. Timothy Perrett wrote: Hmmm, I see your point. Will have a noodle at the weekend and see what would be the best route. Cheers, Tim On 13/03/2009 17:45, Derek Chen-Becker dchenbec...@gmail.com wrote: Well, treating a directory without a trailing slash (/path) as the directory + index (/path/index) is pretty standard behavior in web servers (Apache returns a 301 from the former to the latter), so I think something that requires less user intervention would be good. Perhaps at most we would want a boolean var on LiftRules to control the behavior. Derek On Fri, Mar 13, 2009 at 12:15 PM, Timothy Perrett timo...@getintheloop.eu wrote: Im pretty sure you could just do this with the existing infrastructure (RewritePF and DispatchPF) For instance, if Chas doesnt mind having two seperate resources, then he can easily use RewritePF to get the same content at two resource locations. Alternatively, he could just use a 301 redirect response in a dispatch call to get the appropriate resource - I've posted code to one of his questions about that before If memory serves. I think that should all be cool? Cant think of a good reason why this wouldnt work anyway :-) Cheers, Tim On Mar 13, 4:57 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: I think I was confusing this with some other behavior of SiteMap, hence my question. I think it would be good to allow some really pre-processing of the URL. Would it useful to allow the user to control it, or do you think it would be better to just make it implicit? Something like LiftRules.pathRewrite.append { case List(parse) = List(parse, index) ... } I'm doing a lot of wand-waving there, but does that seem like a reasonable approach from the user side of things? Or maybe make a subclass of RewriteResponse that just tells Lift to modify the path but change nothing else? case class ModifiedPath (path : List[String]) extends RewriteResponse(...) Derek On Fri, Mar 13, 2009 at 10:51 AM, Timothy Perrett timo...@getintheloop.euwrote timo...@getintheloop.euwrote: Within Lift, /page does what it says on the tin, whilst /page/ actually works out as: /page/index IMO, this is good. If you want them to be the same, I think you could either do a rewrite to the same content (if memory serves there is also a boolean option for defining if your using the slash or not?) I'm pretty sure it matters not of you are or are not using site map at this process is part of lifts request handling. Does that help? Cheers, Tim Sent from my iPhone On 13 Mar 2009, at 14:27, Derek Chen-Becker dchenbec...@gmail.com wrote: Hmmm. I thought that this was what normally happened with most web servers (Jetty included). Are you using SiteMap, by any chance? What is the difference that you see between a response for /page and /page/ ? Derek On Fri, Mar 13, 2009 at 4:33 AM, Charles F. Munat c...@munat.com c...@munat.com wrote: It would be advantageous for me, given the way I organize my sites, if requests for /page were served
[Lift] Re: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page?
Hi Mal, That aspect of the lift templating approach also warped my head for a while, having seen so many examples of the opposite approach (PHP, JSP, etc)... There is a certain part of me that still is unsettled about it, but I can see the advantages of it. Marc Ps. can the files such as index.html in the examples be full XML compliant documents? On 13/03/2009, at 3:30 PM, mal3 wrote: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page? When I first saw the HelloWorld example I thought there must be a mistake, because the index.html file contains a snippet, while default.html contains what looked more like a complete XHTML page. Why doesn't lift initially reference a complete XHTML page and then pull in the snippet(s)? Is it to make it difficult/impossible for logic to creep into the view? Mal. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Bookmarkable never-expiring dynamic pages
I think it may be helpful to use a guard: case RewriteRequest(path @ ParsePath(bios :: id :: _, _, _,_), _, _) if id != index = RewriteResponse( ParsePath(bio :: index :: Nil, , true, false), Map(id - id :: path.wholePath.drop(2) .zipWithIndex.map(p = (param+(p._2 + 1)) - p._1) :_* ) ) The RewriteResponse class (not companion object, as you're using here) also has a flag in the constructor to tell Lift to stop rewriting. Derek On Fri, Mar 13, 2009 at 5:34 PM, Charles F. Munat c...@munat.com wrote: I have a lot of sites that involve dynamically-generate pages. OK, all of them do. So let's say that I have a bios page where I link to a bunch of individual bios (for Sam, Sally, and Sue). If Sam is user #1 and Sally and Sue are #2 and #3 respectively, I want to get to their bios like this: /bios - Bio index page /bios/1 - Sam's bio /bios/2 - Sally's bio /bios/3 - Sue's bio Yes, I know about exposing database IDs. I don't care. But sometimes I do something like this: /bios /bios/sam_spade /bios/sally_struthers /bios/sue_me Where I generate the code from the users name using a regex. I actually like this better because it's more human readable, but generating the codes is a bitch (and names aren't always unique). So I get lazy and go back to numbers. Currently, I do this: case RewriteRequest(path @ ParsePath(bios :: id :: _, _, _,_), _, _) = RewriteResponse( ParsePath(bio :: index :: Nil, , true, false), Map(id - id :: path.wholePath.drop(2) .zipWithIndex.map(p = (param+(p._2 + 1)) - p._1) :_* ) ) Then I put the template for the bio page in /bio/index.html. The problem here is that I can't use /bio/index.html as the index page for the bios (choosing a template) because I get an infinite loop, which is why it redirects to /bio not /bios. I need it to *not* redirect when the id part is index. There is probably a drop dead simple way to do this, but my brain is fried after five all-nighters this week. Also, is this really the best way to implement the behavior I describe at the beginning of this email? And does everyone understand why I'm not using /bios/?F5177147114085ON=_ ? Chas. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page?
I think David could better answer this (I haven't looked at this part of the code for a while), but I think that anything outside of the lift:surround tag is tossed, so you could have a fully compliant XML file that will only have a portion used. Derek On Fri, Mar 13, 2009 at 5:40 PM, Marc Boschma marc+lift...@boschma.cxmarc%2blift...@boschma.cx wrote: Hi Mal, That aspect of the lift templating approach also warped my head for a while, having seen so many examples of the opposite approach (PHP, JSP, etc)... There is a certain part of me that still is unsettled about it, but I can see the advantages of it. Marc Ps. can the files such as index.html in the examples be full XML compliant documents? On 13/03/2009, at 3:30 PM, mal3 wrote: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page? When I first saw the HelloWorld example I thought there must be a mistake, because the index.html file contains a snippet, while default.html contains what looked more like a complete XHTML page. Why doesn't lift initially reference a complete XHTML page and then pull in the snippet(s)? Is it to make it difficult/impossible for logic to creep into the view? Mal. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Objections to merging jpa archetype?
OH HELL YEAH! THANKYOUTHANKYOUTHANKYOU. You rock. Chas. Derek Chen-Becker wrote: OK, it built and deployed. I just confirmed that you can create it with: mvn archetype:generate \ -DarchetypeRepository=http://scala-tools.org/repo-snapshots \ -DarchetypeGroupId=net.liftweb \ -DarchetypeArtifactId=lift-archetype-jpa-basic \ -DarchetypeVersion=1.1-SNAPSHOT Derek On Fri, Mar 13, 2009 at 12:54 PM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: Darnit. It helps if I make the jpa archetype a module of the master lift project. Fixing now. Derek On Fri, Mar 13, 2009 at 12:52 PM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: 1.0, baby! http://scala-tools.org/mvnsites/scalajpa/ I've been too busy to put up a nice blog entry on it, but it's on my todo list :( Derek On Fri, Mar 13, 2009 at 12:47 PM, Kris Nuttycombe kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com wrote: I actually haven't deployed an archetype onto a remote repository before, but it sounds right. Has ScalaJPA become publicly available on scala-tools yet? Kris On Fri, Mar 13, 2009 at 11:28 AM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: OK, I'll go ahead and merge with master. If I understand this whole process correctly, Hudson should build the new project and deploy it under snapshots on scala-tools.org http://scala-tools.org. At that point we should be able to use the archetype:generate -DremoteRepository=http://scala-tools.org/repo-snapshots to generate, correct? Derek On Fri, Mar 13, 2009 at 12:01 PM, Kris Nuttycombe kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com wrote: Done. On Fri, Mar 13, 2009 at 10:41 AM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: Actually, I see that you did that against git. Can you commit your changes? Thanks, Derek On Fri, Mar 13, 2009 at 11:40 AM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: Ah, I think I missed that part of the POM. Let me fix that and commit the changes and then we can re-test. Thanks! Derek On Fri, Mar 13, 2009 at 11:11 AM, Kris Nuttycombe kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com wrote: How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to the lift-archetype-jpa-basic pom.xml to get it to install: diff --git a/lift-archetype-jpa-basic/pom.xml b/lift-archetype-jpa-basic/pom.xml index 453e2b3..fc0cf8c 100644 --- a/lift-archetype-jpa-basic/pom.xml +++ b/lift-archetype-jpa-basic/pom.xml @@ -7,6 +7,7 @@ relativePath../pom.xml/relativePath /parent artifactIdlift-archetype-jpa-basic/artifactId + packagingmaven-archetype/packaging name${project.artifactId}/name descriptionArchetype - blank JPA project for Lift/description properties @@ -14,10 +15,18 @@ maven.test.skiptrue/maven.test.skip /properties build +extensions + extension +groupIdorg.apache.maven.archetype/groupId +artifactIdarchetype-packaging/artifactId +version2.0-alpha-4/version + /extension +/extensions plugins plugin artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4/version +extensionstrue/extensions configuration
[Lift] Re: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page?
Well, I just tested and this seems to not be the case :( On Fri, Mar 13, 2009 at 5:47 PM, Derek Chen-Becker dchenbec...@gmail.comwrote: I think David could better answer this (I haven't looked at this part of the code for a while), but I think that anything outside of the lift:surround tag is tossed, so you could have a fully compliant XML file that will only have a portion used. Derek On Fri, Mar 13, 2009 at 5:40 PM, Marc Boschma marc+lift...@boschma.cxmarc%2blift...@boschma.cx wrote: Hi Mal, That aspect of the lift templating approach also warped my head for a while, having seen so many examples of the opposite approach (PHP, JSP, etc)... There is a certain part of me that still is unsettled about it, but I can see the advantages of it. Marc Ps. can the files such as index.html in the examples be full XML compliant documents? On 13/03/2009, at 3:30 PM, mal3 wrote: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page? When I first saw the HelloWorld example I thought there must be a mistake, because the index.html file contains a snippet, while default.html contains what looked more like a complete XHTML page. Why doesn't lift initially reference a complete XHTML page and then pull in the snippet(s)? Is it to make it difficult/impossible for logic to creep into the view? Mal. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page?
Yes, if index.xhtml is a compliant XML (preferably XHTML) document, it will just be served up as-is. The lift:... / tags define transformations that are applied to your document before it is served up. --j On Fri, Mar 13, 2009 at 3:40 PM, Marc Boschma marc+lift...@boschma.cxmarc%2blift...@boschma.cx wrote: Hi Mal, That aspect of the lift templating approach also warped my head for a while, having seen so many examples of the opposite approach (PHP, JSP, etc)... There is a certain part of me that still is unsettled about it, but I can see the advantages of it. Marc Ps. can the files such as index.html in the examples be full XML compliant documents? On 13/03/2009, at 3:30 PM, mal3 wrote: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page? When I first saw the HelloWorld example I thought there must be a mistake, because the index.html file contains a snippet, while default.html contains what looked more like a complete XHTML page. Why doesn't lift initially reference a complete XHTML page and then pull in the snippet(s)? Is it to make it difficult/impossible for logic to creep into the view? Mal. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page?
I think I was confusing lift:ignore in there... On Fri, Mar 13, 2009 at 6:12 PM, Jorge Ortiz jorge.or...@gmail.com wrote: Yes, if index.xhtml is a compliant XML (preferably XHTML) document, it will just be served up as-is. The lift:... / tags define transformations that are applied to your document before it is served up. --j On Fri, Mar 13, 2009 at 3:40 PM, Marc Boschma marc+lift...@boschma.cxmarc%2blift...@boschma.cx wrote: Hi Mal, That aspect of the lift templating approach also warped my head for a while, having seen so many examples of the opposite approach (PHP, JSP, etc)... There is a certain part of me that still is unsettled about it, but I can see the advantages of it. Marc Ps. can the files such as index.html in the examples be full XML compliant documents? On 13/03/2009, at 3:30 PM, mal3 wrote: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page? When I first saw the HelloWorld example I thought there must be a mistake, because the index.html file contains a snippet, while default.html contains what looked more like a complete XHTML page. Why doesn't lift initially reference a complete XHTML page and then pull in the snippet(s)? Is it to make it difficult/impossible for logic to creep into the view? Mal. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Objections to merging jpa archetype?
Yeah... the minor things that made it work at all. :) And ScalaJPA And the whole exploration of Scala's interaction with JPA that you so thoroughly documented on the wiki, which gave me the confidence to use Lift in a major project in my company in the first place... Thank you Derek. You do rock. Kris On Fri, Mar 13, 2009 at 4:55 PM, Derek Chen-Becker dchenbec...@gmail.com wrote: Well, to give proper credit, Tyler and Kris both did a lot of initial work on the archetype and I just fixed a few minor things. Derek On Fri, Mar 13, 2009 at 5:49 PM, Charles F. Munat c...@munat.com wrote: OH HELL YEAH! THANKYOUTHANKYOUTHANKYOU. You rock. Chas. Derek Chen-Becker wrote: OK, it built and deployed. I just confirmed that you can create it with: mvn archetype:generate \ -DarchetypeRepository=http://scala-tools.org/repo-snapshots \ -DarchetypeGroupId=net.liftweb \ -DarchetypeArtifactId=lift-archetype-jpa-basic \ -DarchetypeVersion=1.1-SNAPSHOT Derek On Fri, Mar 13, 2009 at 12:54 PM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: Darnit. It helps if I make the jpa archetype a module of the master lift project. Fixing now. Derek On Fri, Mar 13, 2009 at 12:52 PM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: 1.0, baby! http://scala-tools.org/mvnsites/scalajpa/ I've been too busy to put up a nice blog entry on it, but it's on my todo list :( Derek On Fri, Mar 13, 2009 at 12:47 PM, Kris Nuttycombe kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com wrote: I actually haven't deployed an archetype onto a remote repository before, but it sounds right. Has ScalaJPA become publicly available on scala-tools yet? Kris On Fri, Mar 13, 2009 at 11:28 AM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: OK, I'll go ahead and merge with master. If I understand this whole process correctly, Hudson should build the new project and deploy it under snapshots on scala-tools.org http://scala-tools.org. At that point we should be able to use the archetype:generate -DremoteRepository=http://scala-tools.org/repo-snapshots to generate, correct? Derek On Fri, Mar 13, 2009 at 12:01 PM, Kris Nuttycombe kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com wrote: Done. On Fri, Mar 13, 2009 at 10:41 AM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: Actually, I see that you did that against git. Can you commit your changes? Thanks, Derek On Fri, Mar 13, 2009 at 11:40 AM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: Ah, I think I missed that part of the POM. Let me fix that and commit the changes and then we can re-test. Thanks! Derek On Fri, Mar 13, 2009 at 11:11 AM, Kris Nuttycombe kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com wrote: How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to the lift-archetype-jpa-basic pom.xml to get it to install: diff --git a/lift-archetype-jpa-basic/pom.xml b/lift-archetype-jpa-basic/pom.xml index 453e2b3..fc0cf8c 100644 --- a/lift-archetype-jpa-basic/pom.xml +++ b/lift-archetype-jpa-basic/pom.xml @@ -7,6 +7,7 @@ relativePath../pom.xml/relativePath /parent artifactIdlift-archetype-jpa-basic/artifactId + packagingmaven-archetype/packaging name${project.artifactId}/name descriptionArchetype - blank JPA project for Lift/description properties @@ -14,10 +15,18 @@
[Lift] Re: Objections to merging jpa archetype?
So the you is plural... Derek Chen-Becker wrote: Well, to give proper credit, Tyler and Kris both did a lot of initial work on the archetype and I just fixed a few minor things. Derek On Fri, Mar 13, 2009 at 5:49 PM, Charles F. Munat c...@munat.com mailto:c...@munat.com wrote: OH HELL YEAH! THANKYOUTHANKYOUTHANKYOU. You rock. Chas. Derek Chen-Becker wrote: OK, it built and deployed. I just confirmed that you can create it with: mvn archetype:generate \ -DarchetypeRepository=http://scala-tools.org/repo-snapshots \ -DarchetypeGroupId=net.liftweb \ -DarchetypeArtifactId=lift-archetype-jpa-basic \ -DarchetypeVersion=1.1-SNAPSHOT Derek On Fri, Mar 13, 2009 at 12:54 PM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com mailto:dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: Darnit. It helps if I make the jpa archetype a module of the master lift project. Fixing now. Derek On Fri, Mar 13, 2009 at 12:52 PM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com mailto:dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: 1.0, baby! http://scala-tools.org/mvnsites/scalajpa/ I've been too busy to put up a nice blog entry on it, but it's on my todo list :( Derek On Fri, Mar 13, 2009 at 12:47 PM, Kris Nuttycombe kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com wrote: I actually haven't deployed an archetype onto a remote repository before, but it sounds right. Has ScalaJPA become publicly available on scala-tools yet? Kris On Fri, Mar 13, 2009 at 11:28 AM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com mailto:dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: OK, I'll go ahead and merge with master. If I understand this whole process correctly, Hudson should build the new project and deploy it under snapshots on scala-tools.org http://scala-tools.org http://scala-tools.org. At that point we should be able to use the archetype:generate -DremoteRepository=http://scala-tools.org/repo-snapshots to generate, correct? Derek On Fri, Mar 13, 2009 at 12:01 PM, Kris Nuttycombe kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com wrote: Done. On Fri, Mar 13, 2009 at 10:41 AM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com mailto:dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: Actually, I see that you did that against git. Can you commit your changes? Thanks, Derek On Fri, Mar 13, 2009 at 11:40 AM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com mailto:dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: Ah, I think I missed that part of the POM. Let me fix that and commit the changes and then we can re-test. Thanks! Derek On Fri, Mar 13, 2009 at 11:11 AM, Kris Nuttycombe kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com mailto:kris.nuttyco...@gmail.com wrote: How are you installing the archetype as a plugin? After clearing out the repo and running an install of the plugin project, I'm not seeing it in my local archetype repository. I had to add this to
[Lift] Re: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page?
Maybe I'm not understanding the question, but it is perfectly possible to ignore the template and have index.html be anything you want. I have some pages that wrap the code with other templates (I use more than one, depending on the location on the site), and pages that stand alone. And I have pages that are generated entirely in the snippet. I also have URLS that respond with pure XML, some of which are generated in the snippet code, and others which are bound to a simple template in the webapp directory. Did I miss something? Chas. Derek Chen-Becker wrote: Well, I just tested and this seems to not be the case :( On Fri, Mar 13, 2009 at 5:47 PM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: I think David could better answer this (I haven't looked at this part of the code for a while), but I think that anything outside of the lift:surround tag is tossed, so you could have a fully compliant XML file that will only have a portion used. Derek On Fri, Mar 13, 2009 at 5:40 PM, Marc Boschma marc+lift...@boschma.cx mailto:marc%2blift...@boschma.cx wrote: Hi Mal, That aspect of the lift templating approach also warped my head for a while, having seen so many examples of the opposite approach (PHP, JSP, etc)... There is a certain part of me that still is unsettled about it, but I can see the advantages of it. Marc Ps. can the files such as index.html in the examples be full XML compliant documents? On 13/03/2009, at 3:30 PM, mal3 wrote: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page? When I first saw the HelloWorld example I thought there must be a mistake, because the index.html file contains a snippet, while default.html contains what looked more like a complete XHTML page. Why doesn't lift initially reference a complete XHTML page and then pull in the snippet(s)? Is it to make it difficult/impossible for logic to creep into the view? Mal. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Slash and burn
It seems that Lift used to serve /folks/ when /folks was called, but recently it stopped. It would be nice if it looked for a *file* with that name first, but then tried directories if no file was found. Is there a downside to that? Im afraid your mistaken about it previously having different behavior - its always behaved in the same way it does now :-) As per mine and Derek's convo above, there is rational for needing the trailing slash, and perhaps it should be a configurable option in LiftRules. Off the top of my head, i'm not sure how deeply rooted the current behavior is. Anywho, i'll have a dig around this weekend and see what the options are. Cheers, Tim --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page?
Maybe I'm misunderstanding the question, too. I thought he meant having a fully valid XHTML page for a template, but re-reading it he says XML-compliant. Marc, could you clarify what you mean with an example? Thanks, Derek On Fri, Mar 13, 2009 at 6:37 PM, Charles F. Munat c...@munat.com wrote: Maybe I'm not understanding the question, but it is perfectly possible to ignore the template and have index.html be anything you want. I have some pages that wrap the code with other templates (I use more than one, depending on the location on the site), and pages that stand alone. And I have pages that are generated entirely in the snippet. I also have URLS that respond with pure XML, some of which are generated in the snippet code, and others which are bound to a simple template in the webapp directory. Did I miss something? Chas. Derek Chen-Becker wrote: Well, I just tested and this seems to not be the case :( On Fri, Mar 13, 2009 at 5:47 PM, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: I think David could better answer this (I haven't looked at this part of the code for a while), but I think that anything outside of the lift:surround tag is tossed, so you could have a fully compliant XML file that will only have a portion used. Derek On Fri, Mar 13, 2009 at 5:40 PM, Marc Boschma marc+lift...@boschma.cx marc%2blift...@boschma.cx mailto: marc%2blift...@boschma.cx marc%252blift...@boschma.cx wrote: Hi Mal, That aspect of the lift templating approach also warped my head for a while, having seen so many examples of the opposite approach (PHP, JSP, etc)... There is a certain part of me that still is unsettled about it, but I can see the advantages of it. Marc Ps. can the files such as index.html in the examples be full XML compliant documents? On 13/03/2009, at 3:30 PM, mal3 wrote: Why does HelloWorld index.html contain a snippet rather than a complete XHTML page? When I first saw the HelloWorld example I thought there must be a mistake, because the index.html file contains a snippet, while default.html contains what looked more like a complete XHTML page. Why doesn't lift initially reference a complete XHTML page and then pull in the snippet(s)? Is it to make it difficult/impossible for logic to creep into the view? Mal. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---