Re: Javascript support
Hi Minto, Minto van der Sluis wrote: Hi Manos, JavascriptDependencyFilter is a nice feature and a technical showcase, but I would not allow a feature like that to be activated in projects I control. With this feature I have no absolute control over my deliverables. As far as I can tell there is no garantee that 2 installations are exactly identical. Can you please clarify that or provide an example? I don't get it :-) It even introduces a runtime dependency on the maven repository which might not be available on all occasions. Not at all. The filter only pulls js files from JARs already within the WAR classpath. Cheers, Manos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Javascript support
Hi Manos, It seems I misunderstood the functionality. I thought .js files were pulled from outside the delivered EAR/WAR file straight from the maven repository. In this case the part you didn't get does not apply anymore. The same counts for my objections. Regards, Minto -Oorspronkelijk bericht- Van: Manos Batsis [mailto:manos_li...@geekologue.com] Verzonden: dinsdag 22 september 2009 11:18 Aan: Maven Users List Onderwerp: Re: Javascript support Hi Minto, Minto van der Sluis wrote: Hi Manos, JavascriptDependencyFilter is a nice feature and a technical showcase, but I would not allow a feature like that to be activated in projects I control. With this feature I have no absolute control over my deliverables. As far as I can tell there is no garantee that 2 installations are exactly identical. Can you please clarify that or provide an example? I don't get it :-) It even introduces a runtime dependency on the maven repository which might not be available on all occasions. Not at all. The filter only pulls js files from JARs already within the WAR classpath. Cheers, Manos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org =DISCLAIMER De informatie in deze e-mail is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de geadresseerde bent, wordt u er hierbij op gewezen, dat u geen recht heeft kennis te nemen van de rest van deze e-mail, deze te gebruiken, te kopieren of te verstrekken aan andere personen dan de geadresseerde. Indien u deze e-mail abusievelijk hebt ontvangen, brengt u dan alstublieft de afzender op de hoogte, waarbij u bij deze gevraagd wordt het originele bericht te vernietigen. Politie Amsterdam-Amstelland is niet verantwoordelijk voor de inhoud van deze e-mail en wijst iedere aansprakelijkheid af voor en/of in verband met alle gevolgen en/of schade van een onjuiste of onvolledige verzending ervan. Tenzij uitdrukkelijk het tegendeel blijkt, kunnen aan dit bericht geen rechten worden ontleend. Het gebruik van Internet e-mail brengt zekere risico?s met zich mee. Daarom wordt iedere aansprakelijkheid voor het gebruik van dit medium door de Politie Amsterdam-Amstelland van de hand gewezen. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
Sluis, M. van der (Minto) wrote: It seems I misunderstood the functionality. I thought .js files were pulled from outside the delivered EAR/WAR file straight from the maven repository. Truth is I need to make this clearer in the documentation. To provide an example, suppose you wanted to include the sarissa javascript library as a dependency in the WAR and make it available automatically to HTTP clients: dependency groupIdgr.abiss.mvn.plugins/groupId artifactIdmaven-jstools-plugin/artifactId /dependency dependency groupIdgr.abiss.js/groupId artifactIdsarissa/artifactId /dependency The sarissa script is then available by default (the URL pattern is configurable) as http://domain.tld/lib/js/gr/abiss/js/sarissa/sarissa.js hth, Manos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
PS. Nicolas, 19 open issues in Jira, so there is some community feedback for your project. Half of them are Harlan Iverson todo list (also committer in this project) Some may get fixed quickly, but few of them has patch attached. By feedback I suggested mailing list activity on user or d...@mojo.codehaus.org I'd be pleased to work more one this project if I got more time ... Nicolas
Re: Javascript support
I've used GWT w/ maven. -Dave On Mon, Sep 21, 2009 at 6:26 AM, Minto van der Sluis mi...@multimach.comwrote: Hi Folks, What's the best way to handle javascript using Maven? I have searched the ML archive but it seems all projects have sort of died I have looked at javascript-maven-pluging [1]. But: - svn activity is near to none for the last year. - sources and web-site seem to be out of sync. - site contains a few dead links () - dedicated mailing list archive seem to have disappeared Jstools plugin does not seems to be in a much better shape. - last svn activity is 19 months ago. - less functionality than javascript-maven-plugin Same goes for the maven-js-plugin [3] : - functionality limited to compression - the still some very limited svn activity, Is there a better way to work with javascript files, or have I been spoiled by the maven java functionality? Regards, Minto 'misl' van der Sluis [1] http://mojo.codehaus.org/javascript-maven-tools [2] http://www.dev.abiss.gr/mvn-jstools [3] http://ossi.mobilvox.com/maven-js-plugin BTW is not my intention to insult anyone. I really do appreciate all effort people have put into this, but my impression is javascript support has been scattered and it seems sort of aborted or at least neglected :-( - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
I created the javascript-maven-pluging two years agoI didn't work on it anymore for a while as I don't use it @work and have no more time left to work on it Patch are welcome if you'd like to support improve it ;) 2009/9/21 Minto van der Sluis mi...@multimach.com Hi Folks, What's the best way to handle javascript using Maven? I have searched the ML archive but it seems all projects have sort of died I have looked at javascript-maven-pluging [1]. But: - svn activity is near to none for the last year. - sources and web-site seem to be out of sync. - site contains a few dead links () - dedicated mailing list archive seem to have disappeared Jstools plugin does not seems to be in a much better shape. - last svn activity is 19 months ago. - less functionality than javascript-maven-plugin Same goes for the maven-js-plugin [3] : - functionality limited to compression - the still some very limited svn activity, Is there a better way to work with javascript files, or have I been spoiled by the maven java functionality? Regards, Minto 'misl' van der Sluis [1] http://mojo.codehaus.org/javascript-maven-tools [2] http://www.dev.abiss.gr/mvn-jstools [3] http://ossi.mobilvox.com/maven-js-plugin BTW is not my intention to insult anyone. I really do appreciate all effort people have put into this, but my impression is javascript support has been scattered and it seems sort of aborted or at least neglected :-( - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
Minto van der Sluis wrote: What's the best way to handle javascript using Maven? I have searched the ML archive but it seems all projects have sort of died I have looked at javascript-maven-pluging [1]. But: - svn activity is near to none for the last year. - sources and web-site seem to be out of sync. - site contains a few dead links () - dedicated mailing list archive seem to have disappeared Jstools plugin does not seems to be in a much better shape. - last svn activity is 19 months ago. - less functionality than javascript-maven-plugin Same goes for the maven-js-plugin [3] : - functionality limited to compression - the still some very limited svn activity, None of the above projects are dead AFAIK. None of them tries to provide everything plus the kitchen sink but they work. People use them together since their overlap is rather minimal. IMHO, their development is under hibernation due to luck of interest/suggestions/involvement from plugin users. hth, Manos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
Same feedback from me. I got few users requesting status for the plugin (as you do) and no contribution / proposal / support request in the plugin Seems there is few maven user to build JS apps. None of the above projects are dead AFAIK. None of them tries to provide everything plus the kitchen sink but they work. People use them together since their overlap is rather minimal. IMHO, their development is under hibernation due to luck of interest/suggestions/involvement from plugin users. hth, Manos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
Same for me with the maven-js-plugin. We have in the works more features to implement but, I have much less time than I did when I started on it. Also, there hasn't been much requested as has been mentioned so anything we have come up for new features has just been the result of brainstorming instead of requested features. Adam On Mon, Sep 21, 2009 at 10:32 AM, nicolas de loof nicolas.del...@gmail.com wrote: Same feedback from me. I got few users requesting status for the plugin (as you do) and no contribution / proposal / support request in the plugin Seems there is few maven user to build JS apps. None of the above projects are dead AFAIK. None of them tries to provide everything plus the kitchen sink but they work. People use them together since their overlap is rather minimal. IMHO, their development is under hibernation due to luck of interest/suggestions/involvement from plugin users. hth, Manos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
Oeps, it seems I stepped on some to toes, sorry guys ... and that I am spoiled ;-) A different look gives the following results: javascript-maven-plugin 19 open issues/ total unknown (to me) mailing list: (archive can't be found) commiters: 4 (olamy,ndeloof,bentman,trygvis) # commits in 2009: 16 (svn log | grep 2009- | wc -l) maven jstools plugin: Bugs http://sourceforge.net/tracker/?atid=994821group_id=205730func=browse - 1 open/2 total Feature Requests http://sourceforge.net/tracker/?atid=994824group_id=205730func=browse - 1 open/1 total Patches http://sourceforge.net/tracker/?atid=994823group_id=205730func=browse - 0 open/0 total Support Requests http://sourceforge.net/tracker/?atid=994822group_id=205730func=browse - 0 open/0 total mailing list (users): 6 messages over 2 years commiters: not sure, my guess is only 1 (mbatsis) # commits in 2009: 0? (I have no cvs client) maven-js-plugin Bugs http://sourceforge.net/tracker/?atid=972557group_id=200202func=browse - 0 open/2 total Feature Requests http://sourceforge.net/tracker/?atid=972560group_id=200202func=browse - 0 open/4 total Patches http://sourceforge.net/tracker/?atid=972559group_id=200202func=browse - 0 open/0 total Support Requests http://sourceforge.net/tracker/?atid=972558group_id=200202func=browse - 0 open/1 total mailing list (dev): 14 messages over 3 years commiters: 1 (mvaaltemus) # commits in 2009: 9 (svn log | grep 2009- | wc -l) With these figures javascript-maven-plugin seems the most active one to me. A quick comparison of features gives: javascript-maven maven-jstools maven-js js packaging x x - dep. mgntcompile-time runtime - compress x - x jsunitx - - jsdoc x x - jslintx x - reporting x x - Is this a proper feature comparison? Lack of users has IMHO multiple causes: 1) Javascript source management is an afterthough on many project. They include it as resources in their WAR project. (I've seen the mess ;-) 2) The road for javascript dependency management is not as clear as for java. 3) Lack of javascript dependencies in the maven repositories (search for javascript gives 9-16 results [1], [2] and [3]) Regards, Minto 'misl' van der Sluis [1] http://search.mvnsearch.org/query.action?cat=jarq=javascript [2] http://javarepo.xoocode.org/search?q=javascript [3] http://mvnrepository.com/search.html?query=javascript PS. David, GWT is not an option for existing javascript files is it? PS. Nicolas, 19 open issues in Jira, so there is some community feedback for your project. Minto van der Sluis schreef: Hi Folks, What's the best way to handle javascript using Maven? I have searched the ML archive but it seems all projects have sort of died I have looked at javascript-maven-pluging [1]. But: - svn activity is near to none for the last year. - sources and web-site seem to be out of sync. - site contains a few dead links () - dedicated mailing list archive seem to have disappeared Jstools plugin does not seems to be in a much better shape. - last svn activity is 19 months ago. - less functionality than javascript-maven-plugin Same goes for the maven-js-plugin [3] : - functionality limited to compression - the still some very limited svn activity, Is there a better way to work with javascript files, or have I been spoiled by the maven java functionality? Regards, Minto 'misl' van der Sluis [1] http://mojo.codehaus.org/javascript-maven-tools [2] http://www.dev.abiss.gr/mvn-jstools [3] http://ossi.mobilvox.com/maven-js-plugin BTW is not my intention to insult anyone. I really do appreciate all effort people have put into this, but my impression is javascript support has been scattered and it seems sort of aborted or at least neglected :-( - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
Minto van der Sluis wrote: Oeps, it seems I stepped on some to toes, sorry guys ... and that I am spoiled ;-) Aren't we all ;-) Lack of users has IMHO multiple causes: 1) Javascript source management is an afterthough on many project. They include it as resources in their WAR project. (I've seen the mess ;-) 2) The road for javascript dependency management is not as clear as for java. Bingo. jstools is not only a maven plugin; it is also used as a classpath-like mechanism for resolving js resources at runtime (i.e. when processing an HTTP request) within WAR projects. In short, one can build a JS project with Maven as described in js-packaging [1], in which case the project artifact is a JAR. A WAR project can pool that jar as usual by adding it in the dependencies section within the POM. The jstools should also be added as a dependency to the WAR, making the JavascriptDependencyFilter [2] available to the web application. The filter is responsible for resolving js or other static resources and produce proper responses to HTTP requests. In other words jstools provides runtime dep management (for war projects) and relies on maven conventions for build time. [1] http://dev.abiss.gr/mvn-jstools/js-packaging.html [2] http://dev.abiss.gr/mvn-jstools/apidocs/gr/abiss/mvn/plugins/jstools/web/JavascriptDependencyFilter.html hth, Manos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
I don't think GWT can manage existing JS files. GWT could be used for new dev and the rest as a static resource which could be used by GWT if desired. On Mon, Sep 21, 2009 at 9:26 AM, Minto van der Sluis mi...@multimach.comwrote: Oeps, it seems I stepped on some to toes, sorry guys ... and that I am spoiled ;-) A different look gives the following results: javascript-maven-plugin 19 open issues/ total unknown (to me) mailing list: (archive can't be found) commiters: 4 (olamy,ndeloof,bentman,trygvis) # commits in 2009: 16 (svn log | grep 2009- | wc -l) maven jstools plugin: Bugs http://sourceforge.net/tracker/?atid=994821group_id=205730func=browse - 1 open/2 total Feature Requests http://sourceforge.net/tracker/?atid=994824group_id=205730func=browse - 1 open/1 total Patches http://sourceforge.net/tracker/?atid=994823group_id=205730func=browse - 0 open/0 total Support Requests http://sourceforge.net/tracker/?atid=994822group_id=205730func=browse - 0 open/0 total mailing list (users): 6 messages over 2 years commiters: not sure, my guess is only 1 (mbatsis) # commits in 2009: 0? (I have no cvs client) maven-js-plugin Bugs http://sourceforge.net/tracker/?atid=972557group_id=200202func=browse - 0 open/2 total Feature Requests http://sourceforge.net/tracker/?atid=972560group_id=200202func=browse - 0 open/4 total Patches http://sourceforge.net/tracker/?atid=972559group_id=200202func=browse - 0 open/0 total Support Requests http://sourceforge.net/tracker/?atid=972558group_id=200202func=browse - 0 open/1 total mailing list (dev): 14 messages over 3 years commiters: 1 (mvaaltemus) # commits in 2009: 9 (svn log | grep 2009- | wc -l) With these figures javascript-maven-plugin seems the most active one to me. A quick comparison of features gives: javascript-maven maven-jstools maven-js js packaging x x - dep. mgntcompile-time runtime - compress x - x jsunitx - - jsdoc x x - jslintx x - reporting x x - Is this a proper feature comparison? Lack of users has IMHO multiple causes: 1) Javascript source management is an afterthough on many project. They include it as resources in their WAR project. (I've seen the mess ;-) 2) The road for javascript dependency management is not as clear as for java. 3) Lack of javascript dependencies in the maven repositories (search for javascript gives 9-16 results [1], [2] and [3]) Regards, Minto 'misl' van der Sluis [1] http://search.mvnsearch.org/query.action?cat=jarq=javascript [2] http://javarepo.xoocode.org/search?q=javascript [3] http://mvnrepository.com/search.html?query=javascript PS. David, GWT is not an option for existing javascript files is it? PS. Nicolas, 19 open issues in Jira, so there is some community feedback for your project. Minto van der Sluis schreef: Hi Folks, What's the best way to handle javascript using Maven? I have searched the ML archive but it seems all projects have sort of died I have looked at javascript-maven-pluging [1]. But: - svn activity is near to none for the last year. - sources and web-site seem to be out of sync. - site contains a few dead links () - dedicated mailing list archive seem to have disappeared Jstools plugin does not seems to be in a much better shape. - last svn activity is 19 months ago. - less functionality than javascript-maven-plugin Same goes for the maven-js-plugin [3] : - functionality limited to compression - the still some very limited svn activity, Is there a better way to work with javascript files, or have I been spoiled by the maven java functionality? Regards, Minto 'misl' van der Sluis [1] http://mojo.codehaus.org/javascript-maven-tools [2] http://www.dev.abiss.gr/mvn-jstools [3] http://ossi.mobilvox.com/maven-js-plugin BTW is not my intention to insult anyone. I really do appreciate all effort people have put into this, but my impression is javascript support has been scattered and it seems sort of aborted or at least neglected :-( - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
Hi Martin, I am not looking for a particular javascript library, I am looking for a kind of dependency management as there exists for java projects. Both javascript-maven-plugin as maven-jstools-plugin seem to be capable of doing that. On my current project I inherited a javascript mess where 3rd party dependencies are copied somewhere into src/main/resources or src/main/webapp/js. It's even worse, some js files have both 3rd party and custom code. So it's hard to see what's custom and what's 3rd party. To bring order into that chaos I was hoping for a maven javascript plugin to help out. Regards, Minto 'misl' van der Sluis Martin Gainty schreef: The Javascript Library du jour (for any supported framework) changes with the political climate 2 years ago everyone used Dojo last year everyone converted all their Dojo code to Flex this year its JQuery personally i dont put Dojo on my resume anymore as someone would say thats OLD! so if you fork a branch to develop JQuery scripts (and you notice someone sawing the branch you're on) Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 21 Sep 2009 06:33:37 -0600 Subject: Re: Javascript support From: dhoff...@gmail.com To: users@maven.apache.org I've used GWT w/ maven. -Dave On Mon, Sep 21, 2009 at 6:26 AM, Minto van der Sluis mi...@multimach.comwrote: Hi Folks, What's the best way to handle javascript using Maven? I have searched the ML archive but it seems all projects have sort of died I have looked at javascript-maven-pluging [1]. But: - svn activity is near to none for the last year. - sources and web-site seem to be out of sync. - site contains a few dead links () - dedicated mailing list archive seem to have disappeared Jstools plugin does not seems to be in a much better shape. - last svn activity is 19 months ago. - less functionality than javascript-maven-plugin Same goes for the maven-js-plugin [3] : - functionality limited to compression - the still some very limited svn activity, Is there a better way to work with javascript files, or have I been spoiled by the maven java functionality? Regards, Minto 'misl' van der Sluis [1] http://mojo.codehaus.org/javascript-maven-tools [2] http://www.dev.abiss.gr/mvn-jstools [3] http://ossi.mobilvox.com/maven-js-plugin BTW is not my intention to insult anyone. I really do appreciate all effort people have put into this, but my impression is javascript support has been scattered and it seems sort of aborted or at least neglected :-( - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Hotmail: Free, trusted and rich email service. Get it now. http://clk.atdmt.com/GBL/go/171222984/direct/01/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
Hi Manos, JavascriptDependencyFilter is a nice feature and a technical showcase, but I would not allow a feature like that to be activated in projects I control. With this feature I have no absolute control over my deliverables. As far as I can tell there is no garantee that 2 installations are exactly identical. It even introduces a runtime dependency on the maven repository which might not be available on all occasions. Regards, Minto 'misl' van der Sluis Manos Batsis schreef: Minto van der Sluis wrote: Oeps, it seems I stepped on some to toes, sorry guys ... and that I am spoiled ;-) Aren't we all ;-) Lack of users has IMHO multiple causes: 1) Javascript source management is an afterthough on many project. They include it as resources in their WAR project. (I've seen the mess ;-) 2) The road for javascript dependency management is not as clear as for java. Bingo. jstools is not only a maven plugin; it is also used as a classpath-like mechanism for resolving js resources at runtime (i.e. when processing an HTTP request) within WAR projects. In short, one can build a JS project with Maven as described in js-packaging [1], in which case the project artifact is a JAR. A WAR project can pool that jar as usual by adding it in the dependencies section within the POM. The jstools should also be added as a dependency to the WAR, making the JavascriptDependencyFilter [2] available to the web application. The filter is responsible for resolving js or other static resources and produce proper responses to HTTP requests. In other words jstools provides runtime dep management (for war projects) and relies on maven conventions for build time. [1] http://dev.abiss.gr/mvn-jstools/js-packaging.html [2] http://dev.abiss.gr/mvn-jstools/apidocs/gr/abiss/mvn/plugins/jstools/web/JavascriptDependencyFilter.html hth, Manos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javascript support
Declare your js source directory at plugin level : plugin artifactIdjavascript-maven-plugin/artifact configuration sourceDirectorymy/source/directory/sourceDirectory /configuration Maybe the plugin should use the project.sourceDirectory as the compile goal is only relevant in a pure javascript project... Nico. 2008/2/27, Adrian Herscu [EMAIL PROTECTED]: 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 sourceDirectorymy/source/directory/sourceDirectory 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 [EMAIL PROTECTED]: Harlan, thanks for your fast reply. It works! However, I am not sure what the goalwar-package/goal 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 [EMAIL PROTECTED] 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:
Re: Javascript support
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 sourceDirectorymy/source/directory/sourceDirectory 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 [EMAIL PROTECTED]: Harlan, thanks for your fast reply. It works! However, I am not sure what the goalwar-package/goal 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] (http://webdav.wirexn.net/snapshots), central (http://repo1.maven.org/maven2), wirexn.net (http://webdav.wirexn.net/repository) TIA, Adrian. nicolas de loof wrote:
Re: Javascript support
Harlan, thanks for your fast reply. It works! However, I am not sure what the goalwar-package/goal 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] (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 [EMAIL PROTECTED]: 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Javascript support
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: [EMAIL PROTECTED] (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 [EMAIL PROTECTED]: 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Javascript support
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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] (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 [EMAIL PROTECTED]: 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Javascript support
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 [EMAIL PROTECTED]: 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Javascript support
Insitu wrote: 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. Is there something you need beyond a jslint report for syntax errors/best practices in general? You can get a jslint report from jstools see [1] for an example. Nicolas' javascript plugin over at codehaus also offers jslint checking. If you need something else, I'm sure all js plugin authors would be interested to hear it. Personally, I have received very little feedback on the jstools plugin. I intent to add jsunit and ecmaunit support but have not figured out a really convenient way to do so from the user's point of view yet. Regarding plugin merging, I personally think that me and Nicolas or the people over at mobilvox have developed our plugins having somewhat different viewpoints or actual problems to solve. This is actually great, since the whole Maven+JS thing (or java+JS, or webapp+js or whatever) is not mature/clear enough for anyone to come up with the right solution that does everything plus the kitchensink. Besides, M2 users can mix and match as they like in a POM. [1] http://dev.abiss.gr/mvn-jstools/usage.html Cheers, Manos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Javascript support
Manos Batsis [EMAIL PROTECTED] writes: Is there something you need beyond a jslint report for syntax errors/best practices in general? You can get a jslint report from jstools see [1] for an example. Nicolas' javascript plugin over at codehaus also offers jslint checking. Thanks for your answers (yours and Nicolas): - JSlint reports are not really useful and it seems that the parser used is quite old, isn't it ? I need to parse javascript 1.7 or 1.8 (eg. what's used in Mozilla) and jslint reports false negative with such code - I use personally jsunit, with integration in surefire: I can generate something that is understandable by surefire plugin which generates a nice output report for my unit tests. To do this, you need to hack a bit jsunit, I have provided some code I think in the past but could not remind how/when/where. - What I was thinking about is something along the following: read all js files with rhino to have an approximate compile phase that would check obvious errors that otherwise go unnoticed in javascript (eg. undefined variables/functions, incorrect spellings...) - I would like to have a xpi package type. I plan to work on something soon, but if someone already did it... - I don't know how to handle dependencies really. I would like to use them like in java,so that declared dependencies in the pom are available both at compile and runtime. That could imply doing some magic with unpacking/classpath to run unit tests. best regards, -- Arnaud Bailly, PhD OQube - Software Engineering http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
