Return-Path: Delivered-To: apmail-maven-users-archive@www.apache.org Received: (qmail 17588 invoked from network); 27 Feb 2008 13:22:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Feb 2008 13:22:16 -0000 Received: (qmail 47657 invoked by uid 500); 27 Feb 2008 13:22:03 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 47579 invoked by uid 500); 27 Feb 2008 13:22:03 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 47567 invoked by uid 99); 27 Feb 2008 13:22:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 05:22:03 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gcjtmu-turbine-maven-user-846@m.gmane.org designates 80.91.229.2 as permitted sender) Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 13:21:25 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JUMDz-0000vC-Vw for users@maven.apache.org; Wed, 27 Feb 2008 13:21:32 +0000 Received: from 87.70.143.34 ([87.70.143.34]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Feb 2008 13:21:31 +0000 Received: from bmf1972 by 87.70.143.34 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Feb 2008 13:21:31 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: users@maven.apache.org From: Adrian Herscu Subject: Re: Javascript support Date: Wed, 27 Feb 2008 15:21:21 +0200 Lines: 206 Message-ID: References: <87zltytt7c.fsf@oqube.oqube.com> <4c39e3030802180321n25f5abf8rfd4fab696a0bf18f@mail.gmail.com> <25097ca30802251058m3e4620e2xc44991ecb75d933a@mail.gmail.com> <4c39e3030802260427y70452704x681f4b172f2afc0a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 87.70.143.34 User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) In-Reply-To: <4c39e3030802260427y70452704x681f4b172f2afc0a@mail.gmail.com> Sender: news X-Virus-Checked: Checked by ClamAV on apache.org Hi Nicolas, How do I specify a different source directory? I have looked into the sources and found this: http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools/javascript-maven-plugin/src/main/java/org/codehaus/mojo/javascript/CompileMojo.java Tried the my/source/directory under the build section and got this: [INFO] ------------------------------------------------------------------------ [INFO] basedir C:\documents\pm\project-trunks\wirexn\sandbox\extjs-client-sample \src\main\javascript does not exist [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.IllegalStateException: basedir C:\documents\pm\project-trunks\wirexn\s andbox\extjs-client-sample\src\main\javascript does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java: 542) at org.codehaus.mojo.javascript.CompileMojo.execute(CompileMojo.java:130 ) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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) Adrian. nicolas de loof wrote: > The war-package process source scripts and place them in the packaging > folder used by the war plugin to create the exploded war, before archivaing > a .war. > > Nico > > 2008/2/26, Adrian Herscu : >> Harlan, thanks for your fast reply. It works! >> However, I am not sure what the war-package does (as in the >> example here: >> >> http://mojo.codehaus.org/javascript-maven-tools/guide-webapp-development.html >> ) >> >> Adrian. >> >> >> >> Harlan Iverson wrote: >>> The javascript plugin is currently sandboxed, so following these >>> instructions should make it available: >>> >>> http://mojo.codehaus.org/using-sandbox-plugins.html >>> >>> The other option is to download the source and run mvn install locally. >> The >>> location in the plugin's maven site is wrong, it is here: >>> >>> http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools/ >>> >>> You'll need to check out the top level, as the plugin depends on other >>> modules. >>> >>> Good luck. >>> Harlan >>> >>> >>> On Mon, Feb 25, 2008 at 12:40 PM, Adrian Herscu >> wrote: >>>> Hi all, >>>> >>>> In which repository is this plugin hosted? >>>> I am getting: >>>> >>>> Missing: >>>> ---------- >>>> 1) >>>> >>>> >> org.codehaus.mojo.javascript:javascript-maven-plugin:jar:1.0-alpha-1-SNAPSHOT >>>> >>>> Try downloading the file manually from the project website. >>>> >>>> Then, install it using the command: >>>> mvn install:install-file -DgroupId=org.codehaus.mojo.javascript >>>> -Dartifact >>>> Id=javascript-maven-plugin \ >>>> -Dversion=1.0-alpha-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=org.codehaus.mojo.javascript >>>> -DartifactId=j >>>> avascript-maven-plugin \ >>>> -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar >>>> -Dfile=/path/to/file \ >>>> -Durl=[url] -DrepositoryId=[id] >>>> >>>> Path to dependency: >>>> 1) >>>> org.wirexn.sandbox.extjs:extjs-client-sample:javascript:1.0-alpha-1-S >>>> NAPSHOT >>>> 2) >>>> org.codehaus.mojo.javascript:javascript-maven-plugin:jar:1.0-alpha-1- >>>> SNAPSHOT >>>> >>>> ---------- >>>> 1 required artifact is missing. >>>> >>>> for artifact: >>>> >>>> >>>> >> org.wirexn.sandbox.extjs:extjs-client-sample:javascript:1.0-alpha-1-SNAPSHOT >>>> from the specified remote repositories: >>>> snapshots@wirexn.net (http://webdav.wirexn.net/snapshots), >>>> central (http://repo1.maven.org/maven2), >>>> wirexn.net (http://webdav.wirexn.net/repository) >>>> >>>> >>>> TIA, >>>> Adrian. >>>> >>>> nicolas de loof wrote: >>>>> You can look at the jslint report that will check for some structural >>>> rules >>>>> ( >>>>> >> http://mojo.codehaus.org/javascript-maven-tools/javascript-report-maven-plugin/index.html >>>>> ) >>>>> >>>>> Not sure, but syntactic errors should be detected also. >>>>> >>>>> 2008/2/18, Insitu : >>>>>> Hello, >>>>>> I would like to know what is the current status/plans of the various >>>>>> javascript handling plugins out there. Few months ago there has been >>>>>> some discussions on this topic and some talks about merging >>>>>> projects. I am currently using jstools plugin, with jsunit for test >>>>>> execution, and would like to know if someone has done work on >>>>>> "verifying" or "compiling" the javascript, using eg. Rhino or other >>>>>> parser to ensure syntactic correctness of javascript. >>>>>> >>>>>> Regards, >>>>>> -- >>>>>> Arnaud Bailly, PhD >>>>>> OQube - Software Engineering >>>>>> http://www.oqube.com >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org >>>>>> For additional commands, e-mail: users-help@maven.apache.org >>>>>> >>>>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org >>>> For additional commands, e-mail: users-help@maven.apache.org >>>> >>>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org >> For additional commands, e-mail: users-help@maven.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org