You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Insitu <ab...@oqube.com> on 2008/02/18 12:11:35 UTC
Javascript support
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
Re: Javascript support
Posted by Insitu <ab...@oqube.com>.
Manos Batsis <ma...@geekologue.com> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Javascript support
Posted by Manos Batsis <ma...@geekologue.com>.
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Javascript support
Posted by nicolas de loof <ni...@apache.org>.
Declare your js source directory at plugin level :
<plugin>
<artifactId>javascript-maven-plugin</artifact>
<configuration>
<sourceDirectory>my/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 <bm...@fastmail.fm>:
>
> 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 <sourceDirectory>my/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 <bm...@fastmail.fm>:
> >> Harlan, thanks for your fast reply. It works!
> >> However, I am not sure what the <goal>war-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 <bm...@fastmail.fm>
> >> 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 <ab...@oqube.com>:
> >>>>>> 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
>
>
Re: Javascript support
Posted by Adrian Herscu <bm...@fastmail.fm>.
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 <sourceDirectory>my/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 <bm...@fastmail.fm>:
>> Harlan, thanks for your fast reply. It works!
>> However, I am not sure what the <goal>war-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 <bm...@fastmail.fm>
>> 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 <ab...@oqube.com>:
>>>>>> 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
Re: Javascript support
Posted by nicolas de loof <ni...@apache.org>.
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 <bm...@fastmail.fm>:
>
> Harlan, thanks for your fast reply. It works!
> However, I am not sure what the <goal>war-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 <bm...@fastmail.fm>
> 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 <ab...@oqube.com>:
> >>>> 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
>
>
Re: Javascript support
Posted by Adrian Herscu <bm...@fastmail.fm>.
Harlan, thanks for your fast reply. It works!
However, I am not sure what the <goal>war-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 <bm...@fastmail.fm> 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 <ab...@oqube.com>:
>>>> 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
Re: Javascript support
Posted by Harlan Iverson <h....@gmail.com>.
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 <bm...@fastmail.fm> 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 <ab...@oqube.com>:
> >> 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
>
>
Re: Javascript support
Posted by Adrian Herscu <bm...@fastmail.fm>.
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 <ab...@oqube.com>:
>> 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
Re: Javascript support
Posted by nicolas de loof <ni...@apache.org>.
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 <ab...@oqube.com>:
>
> 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
>
>