Type in documentation on "Dependency scope"?

retrieved through an explicit dependency B with scope 'provided' (3rd row). Shouldn't this stay 'runtime', because if B didn't need compile access to C, then the module A depending on B will normally not

[M2] cyclic dependency M2 'plugins' trunk between checkstyle and javadoc plugin.

at: Mon Nov 06 11:09:37 CET 2006 [INFO] Final Memory: 3M/6M [INFO] FATAL ERROR: Unable to configure the Maven application For more information, run with the -e flag Rerunning 'mvn' with the options '-X' or '-e' didn't show more inf

Re: [M1] can't build M1 trunk because maven-model 3.0.2-20061008.232644 not found.

or: org/apache/maven/project/io/xpp3/MavenXpp3Reader at org.apache.maven.project.Project.(Project.java:133) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:193) ... 21 more It seems some classes were removed from maven-model-3.0.2 which are still needed in the maven-artifact-plugin. Regards, D

[M1] can't build M1 trunk because maven-model 3.0.2-20061008.232644 not found.

lable. Regards, Davy Toch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Is TestNG support in M2 2.0.4 already stable?

ailable in http://www.ibiblio.org/maven2. Regards, Davy Toch Davy Toch wrote: Hi, I was just wondering whether TestNG support in M2 is already stable and can be used as a viable replacement of JUnit? I already tried using TestNG in M2 but I had different problems (tests not being run, ClassCastEx

Is TestNG support in M2 2.0.4 already stable?

detail, I just have this simple question : is M2 2.0.4 already supposed to fully support TestNG or is it recommended to wait until M2 2.0.5 or higher? Regards and thanks, Davy Toch - To unsubscribe, e-mail: [EMAIL PROTECTED] For

Re: jelly: How to get a reference to an environment variable?

Hi, Different solutions: ... JAVA_HOME : ${env.JAVA_HOME} ... Maven variables : ${context.getVariables()} Maven JRE : ${context.getVariable("java.home")} Maven JAVA_HOME : ${context.getVariable("env.JAVA_HOME")} ... Re

Re: [m2] antlib and typedef - feel like a noob

Hi, There's a bug in the documentation. Instead of you should have Regards, Davy Toch On Tuesday 27 September 2005 15:37, Darren Hartford wrote: > name="NewDepTest" > default="get-deps" > basedir="." >

Problem with marmalade plugin tutorial as described on M2 site.

I've just started experimenting with M2, so perhaps I forgot a configuration somewhere in M2 that is obvious for the M2 guru's out there :-). Regards, Davy Toch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiproject: dependency not triggered

comp1. So make sure the artifact created by project/comp1 is already available in the local/central repository!. In order to build all components, you should do: $cd project/master; maven %multiproject_goal_name% Regards, Davy Toch IT-Consultant Steria SA/NV [EMAIL PROTECTED] wrote: I

Re: Multiproject: dependency not triggered

roject.xml and maven.xml out of toplevel, what would be the behaviour of multiproject:install in rh/ folder? Or are you suggesting that toplevel build must commence from rh/apps? Again, thanks! Rk x77309 On Thu, 15 Sep 2005, Davy Toch wrote: Hi, Your project structure has the following pr

Re: Multiproject: dependency not triggered

cts. If I move the project.xml and maven.xml out of toplevel, what would be the behaviour of multiproject:install in rh/ folder? Or are you suggesting that toplevel build must commence from rh/apps? Again, thanks! Rk x77309 On Thu, 15 Sep 2005, Davy Toch wrote: Hi, Your project structure has t

Re: Multiproject: dependency not triggered

py rh/maven.xml to rh/app/maven.xml but remove the multiproject part should be removed in the latter. Also : http://jira.codehaus.org/browse/MPMULTIPROJECT-55 (unfortunately I didn't get any feedback on this from the Maven guru's :-( ). Regards, Davy Toch IT-Consultant Steria SA/NV

Re: problem in building project with subprojects when using Maven 1.1-beta1

2 solutions: - Upgrade maven-artifact-plugin to latest version - Use Maven-1.1-beta2 instead (recommended). Don't forget to modify MAVEN_HOME and PATH to point to maven-1.1-beta2 afterwards. Marco Mistroni wrote: hello all, i have a project which contains a subproject in this structure J

Re: [M1.1] SAXParserFactoryImpl could not be instantiated

Solution: - point MAVEN_HOME to maven-1.1-beta2 - modify PATH to point the 'bin' folder of Maven 1.1 beta 2 Remark : if you do the first, but not the second, then you'll get the error you indicated. What is confusing however, is that you see '1.1-beta-2' in the Maven logo, despite the fact tha

Re: [m1] Keeping plugins up to date

ean up update-script.cmd and you're ready to update the plugins. Regards, Davy Toch Milos Kleint wrote: if you want to be sure that evenryone builds with the same version of the plugin, add the plugin as a dependency of the project. Regards Milos Kleint On 8/2/05, Grant Ingersoll <[EM