On 09.02.2013, 01:20:35 Dominique Pellé wrote:
Is the duplication in the directory name
.../LanguageTool-2.1-SNAPSHOT/LanguageTool-2.1-SNAPSHOT/... also
expected?
Not really expected, but it's what the plugin does by default.
About performance: does your workflow require making a lot of
Daniel Naber list2...@danielnaber.de wrote:
On 09.02.2013, 01:20:35 Dominique Pellé wrote:
Is the duplication in the directory name
.../LanguageTool-2.1-SNAPSHOT/LanguageTool-2.1-SNAPSHOT/... also
expected?
Not really expected, but it's what the plugin does by default.
About
On 09.02.2013, 10:58:25 Dominique Pellé wrote:
!-- modulelanguagetool-language-modules/en/module --
I forgot that we have a module language-all which is kind of a meta
module that pulls in all languages. So you should comment out non-relevant
languages also in the pom.xml of language-all.
On 09.02.2013, 10:58:25 Dominique Pellé wrote:
I only use the command line version of LanguageTool.
What you could also do is to skip languagetool-standalone and work directly
in languagetool-commandline. For this, maven-assembly-plugin needs to be
configured in the pom.xml of
Daniel Naber wrote:
There's now languagetool-commandline.jar. It would be nice to move all
libs
to a lib directory except the LT ones, but I'm not sure yet how that
works.
Thanks for that.
When running mvn clean package, I see 2 jar files created:
Richard Eckart de Castilho wrote:
Without having had a look at the build, I would expect at least two things
to cause:
1) Maven (like ant) is a Java application and it takes a moment to fire up
the JVM.
make is a native application. 2) The package goal always runs the full
packaging
Am 09.02.2013 um 01:50 schrieb Dominique Pellé dominique.pe...@gmail.com:
Richard Eckart de Castilho wrote:
Without having had a look at the build, I would expect at least two things to
cause:
1) Maven (like ant) is a Java application and it takes a moment to fire up
the JVM.
make is
Daniel Naber list2...@danielnaber.de wrote:
Hi everybody!
As planned, we have now switched the LT source to a module-based Maven
structure. This mail contains important information about what that means
for developers. Please read this carefully if you're affected.
*
2013/1/28 Mauro Condarelli mc5...@mclink.it
Sorry to disturb, people.
I've been using Eclipse previously.
Now I followed instructions for the maven repack.
Everything went ok, but I can't start the commandline:
mcon@vmrunner
:/srv/Store/Language/languagetool/languagetool-standalone/target$
What I do (in Windows) is to unzip this file:
.m2\repository\org\languagetool\languagetool-standalone\2.1-SNAPSHOT\languagetool-standalone-2.1-SNAPSHOT.zip
In the resulting folder you should have everything that is needed.
Regards,
Jaume Ortolà
2013/1/28 Mauro Condarelli mc5...@mclink.it
Mauro Condarelli mc5...@mclink.it wrote:
On 28/01/2013 09:51, Jaume Ortolà i Font wrote:
2013/1/28 Mauro Condarelli mc5...@mclink.it
Sorry to disturb, people.
I've been using Eclipse previously.
Now I followed instructions for the maven repack.
Everything went ok, but I can't start the
On 28.01.2013, 00:41:10 Mauro Condarelli wrote:
Everything went ok, but I can't start the commandline:
mcon@vmrunner:/srv/Store/Language/languagetool/languagetool-standalone/ta
rget$ java -cp languagetool-standalone-2.1-SNAPSHOT.jar
Could you please try again with the very latest version?
On 28.01.2013, 10:34:33 Mauro Condarelli wrote:
My .m2/repository directory contains a lot of libs (.jars .pom) deeply
nested, but nothing really about LanguageTool itself.
JARs will only be in ~/.m2/repository if you call mvn clean install. This
is useful as you then can compile and test
On 24/01/2013 21:27, Daniel Naber wrote:
On 24.01.2013, 13:15:38 Jaume Ortolà i Font wrote:
I can run the GUI with a file named now
languagetool-standalone-2.1-SNAPSHOT.jar, but I had to unzip it
previously. And I cannot find a command-line aplication like the
previous LanguageTool.jar.
2013/1/24 Daniel Naber list2...@danielnaber.de
You can use this for now (I just made an update, the class was still
missing):
java -cp languagetool-standalone-2.1-SNAPSHOT.jar
org.languagetool.commandline.Main
We can either add script files or configure Maven to create
another JAR for the
This can be useful for Eclipse users.
I installed these plugins:
m2e - Maven Integration for Eclipse
Subclipse (or other SVN plugin)
Maven SCM handler for Subclipse
Then in the SVN repository you can check out as a Maven project The
result is a duplicated structure like the one explaind by
As far as I am concerned, I think it is very technical.
I will work from the nightly builds.
On 24-01-13 13:15, Jaume Ortolà i Font wrote:
2013/1/23 Daniel Naber list2...@danielnaber.de
mailto:list2...@danielnaber.de
Don't hesitate to ask if you have questions.
Hi Daniel,
I miss an
Hi everybody!
As planned, we have now switched the LT source to a module-based Maven
structure. This mail contains important information about what that means
for developers. Please read this carefully if you're affected.
Who is affected?
Only people who use svn to access the very latest
Daniel Naber wrote:
7. If you find problems related to the switch, let me know. I know that not
everything is working 100% but we should be close. For example, some shell
scripts are missing / not working yet, and the *.oxt is still called *.zip
and too big.
Following web page has now a
Great news!
2. Make sure maven is installed. Type mvn -version on the command line.
If Maven returns its version and the version is = 3.0.2, everything is
okay. If not, follow the instructions on
http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html
(ignoring the
20 matches
Mail list logo
