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 "Creating a Project" part). As a Linux user, Maven should be
> provided by your distribution.
You can add a requirement for a minimum Maven version to the pom:
<prerequisites>
<maven>3.0.2</maven>
</prerequisites>
http://maven.apache.org/pom.html#Prerequisites
> 3. Check out the new code:
>
> svn co
> https://languagetool.svn.sourceforge.net/svnroot/languagetool/trunk/languagetool
You may find it more comfortable to reverse this and put "trunk" "tags" and
"branches" under languagetool:
https://languagetool.svn.sourceforge.net/svnroot/languagetool/languagetool/trunk
Probably the maven release plugin can detect the right location to create
release tags even with your current layout without further configuration, but
maybe not.
> Your IDE can probably import them all at once if you import the top
> "pom.xml"
In case of Eclipse and m2e, mind that the submodules will appear twice(!) in
the project explorer, once as project and then again as folders within the
project that resembles the top-level Maven folder. It causes some odd effects
like search finding files twice. You should get used to it after a while.
A recommendation for adding new modules in Eclipse:
1) open top-level POM
2) create module
3) close the project that was created for the module
4) delete the project from the project explorer (not from disk)
5) go to the top-level project and add the folder of the new module to SVN
6) revert .settings, .project, target, .classpath
7) add .settings, .project, target, .classpath to svn:ignore
8) commit the top-level project (the pom.xml and the module folder)
9) use Import->Existing Maven projects on the top-level project to add the
module back to the explorer
We found this was the best method to get Eclipse to recognize that the new
module is in SVN and it causes least confusion to Eclipse's workspace metadata.
> Instead of "ant test", now run "mvn clean test" before you commit a change.
> If you go to the sub-projects and type "mvn clean test" there, only that
> project will be tested. This is useful for the language modules, as only
> that language and its rules will be tested, which if quite fast. Be careful
> though, as the language module depends on the core module and you might get
> strange errors if the core module has changed and you haven't built **and
> installed** it yet. To install a module, use "mvn clean install". This will
> compile and test the module(s) and install the result (the *.jar files) in
> your local Maven repository (~/.m2/repository under Linux). When in doubt,
> run "mvn clean test" in the top directory.
If you use Eclipse and run the "test" goal within Eclipse, checking "resolve
workspace artifacts" in the run configuration should allow the tests to pick up
changes in the core module without doing an "install" before.
A good next step would be to add the Sonatype OSS pom as a parent pom to the
top-level languagetool pom and then try to create a release candidate.
Cheers,
-- Richard
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Languagetool-devel mailing list
Languagetool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/languagetool-devel
