Don't know if anyone responded, but you may need to add the maven  
snapshot repository to your pom as well.

Sent from my iPhone

On Apr 3, 2009, at 2:36 PM, DavidV <[email protected]> wrote:

>
> I added the dependency to my pom.xml exactly as you suggested and I'm
> getting this error:
>
> Downloading: 
> http://scala-tools.org/repo-releases/net/liftweb/lift-widgets/1.1-S
> NAPSHOT/lift-widgets-1.1-SNAPSHOT.jar
> [INFO]
> --- 
> ---------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> --- 
> ---------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) net.liftweb:lift-widgets:jar:1.1-SNAPSHOT
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>      mvn install:install-file -DgroupId=net.liftweb -DartifactId=lift-
> widgets -
> Dversion=1.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the
> file there:
>
>      mvn deploy:deploy-file -DgroupId=net.liftweb -DartifactId=lift-
> widgets -Dv
> ersion=1.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -
> Drepositor
> yId=[id]
>
>  Path to dependency:
>        1) testLift:testLift:war:1.0
>        2) net.liftweb:lift-widgets:jar:1.1-SNAPSHOT
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
>  testLift:testLift:war:1.0
>
> from the specified remote repositories:
>  scala-tools.org (http://scala-tools.org/repo-releases),
>  central (http://repo1.maven.org/maven2)
>
>
> I changed the dependency version to 1.0 because I followed the scala-
> tools.org link (http://scala-tools.org/repo-releases) and noticed that
> there wasn't a 1.1-SNAPSHOT version in net\liftweb\lift-widgets.
> Maven then compiled the project, but my menu still isn't showing up as
> I would like it to.  I haven't changed my template.
>
> On Apr 2, 11:07 pm, Derek Chen-Becker <[email protected]> wrote:
>> Do you have lift-widgets module as a dependency in your pom.xml?
>>
>>     <dependency>
>>       <groupId>net.liftweb</groupId>
>>       <artifactId>lift-widgets</artifactId>
>>       <version>1.1-SNAPSHOT</version>
>>     </dependency>
>>
>> That's needed to get the dropdown widget code.
>>
>> Derek
>>
>> On Thu, Apr 2, 2009 at 3:13 PM, DavidV <[email protected]>  
>> wrote:
>>
>>> I posted this yesterday but I haven't seen it appear yet...sorry  
>>> if it
>>> is here twice.
>>
>>> I downloaded the scripts separately because I didn't know how to
>>> update my repository/library to include the MenuWidget class and the
>>> appropriate .js and .css files.  I tried running "mvn install" on my
>>> webapp, but it didn't download those new files.
>>> I fixed the problem with my .css file so it compiles now, however  
>>> I'm
>>> still not getting the nice stylish superfish navbar.  Instead, I'm
>>> getting a vertical bulleted list of links to my different pages.  I
>>> think it's a problem with my template.  Here are the relevant
>>> sections:
>>
>>> <html xmlns="http://www.w3.org/1999/xhtml"; xmlns:lift="http://
>>> liftweb.net/">
>>>  <head>
>>>    <meta http-equiv="content-type" content="text/html;
>>> charset=UTF-8" />
>>>    <meta name="description" content="" />
>>>    <meta name="keywords" content="" />
>>
>>>    <title>My WebApp <lift:Menu.title /> </title>
>>>    <lift:StyleSheet.entryForm />
>>>    <lift:StyleSheet.fancyType />
>>>    <script id="jquery" src="/classpath/jquery.js" type="text/
>>> javascript"/>
>>>    <script id="json" src="/classpath/json.js" type="text/ 
>>> javascript"/
>>
>>>        </head>
>>>        <body>
>>
>>>    <div class="container">
>>>      <div style="text-align: center">
>>>      <br/>
>>>        <h1 class="alt">
>>>          Welcome to My WebApp </h1>
>>>     </div>
>>>      <hr/>
>>
>>>     <div>
>>>        <lift:MyMenu.render />
>>>           <div>
>>>               <lift:Msgs/>
>>>               <hr class="space" />
>>>          </div>
>>>      </div>
>>
>>> MyMenu is the snippet that contains the render method, which looks
>>> like this:
>>
>>>  def render(xhtml: NodeSeq): NodeSeq = {
>>>    MenuWidget(MenuStyle.NAVBAR)
>>>  }
>>
>>> Does anyone see what might be wrong here?
>>
>>> Thanks,
>>> David
>>
>>> On Apr 1, 11:04 am, "marius d." <[email protected]> wrote:
>>>> Is there a reason why you downloaded he scripts separately? ... the
>>>> superfish dependencies are offered by the widget. Please see the  
>>>> lift-
>>>> widgets project and the test applicaiton from there.
>>
>>>> Br's,
>>>> Marius
>>
>>>> On Mar 31, 11:48 pm, DavidV <[email protected]> wrote:
>>
>>>>> I would like to use this newMenuWidget, so I got the source code  
>>>>> from
>>>>> GitHub and put it into my application as a snippet.  I also  
>>>>> downloaded
>>>>> all of the necessary superfish .css and .js files from the  
>>>>> superfish
>>>>> website and put those in local sub-directories of the "src/main/
>>>>> webapp" folder.  When I try to compile the code in maven,  
>>>>> however, I
>>>>> get the following error.
>>
>>>>> C:\Source\trunk\eclipse\testLift>mvn clean jetty:run
>>>>> [INFO] Scanning for projects...
>>>>> [INFO] Searching repository for plugin with prefix: 'jetty'.
>>>>> [INFO]
>>
>>> --- 
>>> --- 
>>> ------------------------------------------------------------------
>>>>> [INFO] Building testLift
>>>>> [INFO]    task-segment: [clean, jetty:run]
>>>>> [INFO]
>>
>>> --- 
>>> --- 
>>> ------------------------------------------------------------------
>>>>> [INFO] [clean:clean]
>>>>> [INFO] Deleting directory C:\Source\trunk\eclipse\testLift\target
>>>>> [INFO] Preparing jetty:run
>>>>> [INFO] [resources:resources]
>>>>> [INFO] Using default encoding to copy filtered resources.
>>>>> [INFO] [yuicompressor:compress {execution: default}]
>>>>> [INFO] jquery.hoverIntent.js (4637b) -> jquery.hoverIntent.js  
>>>>> (0b)[0%]
>>>>> [INFO] superfish.js (3837b) -> superfish.js (0b)[0%]
>>>>> [INFO] entryform.css (11417b) -> entryform.css (10202b)[89%]
>>>>> [INFO] print.css (1341b) -> print.css (821b)[61%]
>>>>> [INFO]
>>
>>> --- 
>>> --- 
>>> ------------------------------------------------------------------
>>>>> [ERROR] FATAL ERROR
>>>>> [INFO]
>>
>>> --- 
>>> --- 
>>> ------------------------------------------------------------------
>>>>> [INFO] Illegal group reference
>>>>> [INFO]
>>
>>> --- 
>>> --- 
>>> ------------------------------------------------------------------
>>>>> [INFO] Trace
>>>>> java.lang.IllegalArgumentException: Illegal group reference
>>>>>         at  
>>>>> java.util.regex.Matcher.appendReplacement(Matcher.java:713)
>>>>>         at  
>>>>> com.yahoo.platform.yui.compressor.CssCompressor.compress
>>>>> (CssCompresso
>>>>> r.java:78)
>>>>>         at
>>>>> net. 
>>>>> sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCom
>>>>> pressorMojo.java:182)
>>>>>         at net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir
>>>>> (MojoSupport.j
>>>>> ava:151)
>>>>>         at net.sf.alchim.mojo.yuicompressor.MojoSupport.execute
>>>>> (MojoSupport.java
>>>>> :105)
>>>>>         at  
>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo
>>>>> (DefaultPlugi
>>>>> nManager.java:451)
>>>>>         at
>>>>> org. 
>>>>> apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>>>> ultLifecycleExecutor.java:558)
>>>>>         at
>>>>> org. 
>>>>> apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>>>>> fecycle(DefaultLifecycleExecutor.java:499)
>>>>>         at
>>>>> org. 
>>>>> apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecy
>>>>> cle(DefaultLifecycleExecutor.java:924)
>>>>>         at
>>>>> org. 
>>>>> apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(Def
>>>>> aultLifecycleExecutor.java:767)
>>>>>         at
>>>>> org. 
>>>>> apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>>>> ultLifecycleExecutor.java:529)
>>>>>         at
>>>>> org. 
>>>>> apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
>>>>> Goal(DefaultLifecycleExecutor.java:512)
>>>>>         at
>>>>> org. 
>>>>> apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>>>>> ltLifecycleExecutor.java:482)
>>>>>         at
>>>>> org. 
>>>>> apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>>>>> dleFailures(DefaultLifecycleExecutor.java:330)
>>>>>         at
>>>>> org. 
>>>>> apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>>>>> ts(DefaultLifecycleExecutor.java:291)
>>>>>         at  
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
>>>>> (DefaultLi
>>>>> fecycleExecutor.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
>>>>> (DelegatingMethodAcces
>>>>> sorImpl.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)
>>>>> [INFO]
>>
>>> --- 
>>> --- 
>>> ------------------------------------------------------------------
>>>>> [INFO] Total time: 5 seconds
>>>>> [INFO] Finished at: Tue Mar 31 17:38:35 EDT 2009
>>>>> [INFO] Final Memory: 17M/30M
>>>>> [INFO]
>>
>>> --- 
>>> --- 
>>> ------------------------------------------------------------------
>>
>>>>> Any ideas on how to prevent/fix this?  Do I need to modify  
>>>>> my .pom?
>>
>>>>> Thanks,
>>>>> David
>>
>>>>> On Mar 23, 12:18 pm, "marius d." <[email protected]> wrote:
>>
>>>>>> Cool ... if you tested it and theMenuWidget, from my  
>>>>>> perspective it
>>>>>> is good to go into master. And it's really great that you added  
>>>>>> the
>>>>>> ScalaDocs !!!
>>
>>>>>> Br's,
>>>>>> Marius
>>
>>>>>> On Mar 23, 6:07 pm, Derek Chen-Becker <[email protected]>  
>>>>>> wrote:
>>
>>>>>>> OK, I've pushed the new code on the wip-dcb-dropdown branch. I  
>>>>>>> made
>>> some
>>>>>>> minor mods to the builtin Menu snippet (and changes to the Menu
>>> widget to
>>>>>>> match):
>>
>>>>>>>     1. Added an "expandAll" attribute that renders the entire
>>> SiteMap.
>>>>>>>     2. Added a new "top" prefix to the builder snippet to  
>>>>>>> allow for
>>>>>>>        attributes on the top-level menu UL element.
>>>>>>>     3. Added API documentation to the Menu class.
>>
>>>>>>> For some reason, the branch isn't showing up on github. I did a
>>
>>>>>>> git push origin wip-dcb-dropdown
>>
>>>>>>> And it says it's up-to-date, but I'm not seeing it on github.
>>
>>>>>>> Derek
>>
>>>>>>> On Sat, Mar 21, 2009 at 3:04 PM, Charles F. Munat  
>>>>>>> <[email protected]>
>>> wrote:
>>
>>>>>>>> +1
>>
>>>>>>>> I am understanding exactly what you have in mind and think  
>>>>>>>> it's a
>>> great
>>>>>>>> idea. I wrote some kludgy code months ago (I knew zero about
>>> Scala back
>>>>>>>> then -- now I know *infinity* times more! :-) to do pretty much
>>> the same
>>>>>>>> thing, and I ended up completely rewriting the Menu snippet  
>>>>>>>> to my
>>> own
>>>>>>>> needs. More flexibility == good, I think.
>>
>>>>>>>> Chas.
>>
>>>>>>>> (For anyone a little slow on the uptake this fine Saturday,
>>> please note
>>>>>>>> that anything times zero is still zero.)
>>
>>>>>>>> Derek Chen-Becker wrote:
>>>>>>>>> I think I'm not being very clear. I'm going to modify the
>>> builtin Menu
>>>>>>>>> snippet, not SiteMap. In my view, SiteMap should not be
>>> concerned with
>>>>>>>>> how it's rendered, but the builtin snippet surely should be
>>
>> ...
>>
>> read more ยป
>
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to