Re: No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?

>> $ echo $JAVA_HOME >> /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home ... >> $ mvn --version >> Apache Maven 3.0.4 (r1232337; 2012-01-17 19:44:56+1100) >> Maven home: /usr/share/maven >> Java version: 1.7.0_21, vendor: Oracle Corporation >> Java home: >> /Library/Java/JavaVirtualM

Re: No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?

On Mon, May 13, 2013 at 7:53 AM, Corin Lawson wrote: > $ echo $JAVA_HOME > /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home > Look at what that ends with. > $ mvn --version > Apache Maven 3.0.4 (r1232337; 2012-01-17 19:44:56+1100) > Maven home: /usr/share/maven > Java version: 1.

No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?

Hi, This seems like a pretty simple one and I'm hoping that I'll feel quite dim when I get answer... My environment: $ uname -srm Darwin 12.3.0 x86_64 $ $JAVA_HOME/bin/javac -version javac 1.7.0_21 javac: no source files Usage: javac where possible options include: -g

Re: mvn test shall run all tests

Andreas Gudian wrote: > You're right, what you would configure is in Ant-style notation. Here's > the deault config: > > > **/*Test*.java > **/*Test.java > **/*TestCase.java > IIRC, you *can* use regexp, i.e. such an expression should also work (not sure about the back slashes for the esca

Re: allowMajorUpdates for mvn versions:update-properties

I raised a JIRA: http://jira.codehaus.org/browse/MVERSIONS-220 -- View this message in context: http://maven.40175.n5.nabble.com/allowMajorUpdates-for-mvn-versions-update-properties-tp5754676p5756003.html Sent from the Maven - Users mailing list archive at Nabble.com.

Re: mvn test shall run all tests

Yes it uses ANT syntax but when writing out the answer I thought regex might be easier to understand... Then I changed my mind after sending ;-) On Monday, 13 May 2013, Jörg Schaible wrote: > Stephen Connolly wrote: > > > Surefire only runs the tests from classes that follow Surefire's naming > >

Re: mvn test shall run all tests

You're right, what you would configure is in Ant-style notation. Here's the deault config: **/*Test*.java **/*Test.java **/*TestCase.java 2013/5/13 Jörg Schaible > Stephen Connolly wrote: > > > Surefire only runs the tests from classes that follow Surefire's naming > > convention, i.e. f

Re: Maven-nar-plugin Issue

Hi swappy, It looks like you have maven-nar-plugin configured in your pluginManagement section, but not your plugins section. See this SO Q&A for an explanation of the difference: http://stackoverflow.com/questions/10483180/maven-what-is-pluginmanagement Regards, Curtis P.S. Since maven-nar-pl

[ANN] Maven Site Plugin 3.3 Released

The Apache Maven team is pleased to announce the release of the Maven Site Plugin, version 3.3 The Site Plugin is used to generate a site for the project. The generated site also includes the project's reports that were configured in the POM. http://maven.apache.org/plugins/maven-site-plugin/

Re: mvn test shall run all tests

Stephen Connolly wrote: > Surefire only runs the tests from classes that follow Surefire's naming > convention, i.e. file must match one of the following regexs > > Test.* > .*Test > .*TestCase Sure? I thought, it is using a wildcard notation by default (e.g. like Ant includes). - Jörg -

Re: mvn test shall run all tests

Be sure you know regex syntax before interpreting the regexes I provided On 13 May 2013 17:10, Stephen Connolly wrote: > Surefire only runs the tests from classes that follow Surefire's naming > convention, i.e. file must match one of the following regexs > > Test.* > .*Test > .*TestCase > > > O

Re: mvn test shall run all tests

Surefire only runs the tests from classes that follow Surefire's naming convention, i.e. file must match one of the following regexs Test.* .*Test .*TestCase On 13 May 2013 17:05, Sven Bauhan wrote: > Hi, > > I am new here with a question I could not a solution yet. > > I have about 6 test cla

mvn test shall run all tests

Hi, I am new here with a question I could not a solution yet. I have about 6 test classes to run some JUnit tests. When I call "mvn test" only the test of one class is executed. On the command line I can instruct maven to all tests by "mvn -Dtest='.*' test". But I don't know how I can create a

[maven compiler plugin] compilation failure with plexus eclipse compiler

Hello, There looks to be an issue with the plexus compiler plugin with the eclipse compiler configuration when using the switch statement with enums. Please, find details on following stackoverflow thread: http://stackoverflow.com/questions/16520888/maven-compilation-failure-when-switching-on-en

Re: Need help with POM configuration to combine jaxb2, jaxws, with dependencies and episode files

Thank you for the response. It seems like this is an issue that spans a few areas all involving maven in general, so I posted here and the plugin group. The plugin group only consists of 7 people so I was hoping I might hit someone here that could get me pointed in the right direction. Marc

Re: avoiding to write into user home

+1. I have done this. Caching cannot be disabled: it is what maven does. But you can control where the cache is stored. The final step is to invoke maven with: mvn -s /path/to/alternate/settings.xml With this command-line option and settings defined as noted by Stephen below, nothing will be

Re: avoiding to write into user home

The local repository cache is by default stored in ~/.m2/repository In the users or global settings this default can be changed to some other location. (See in http://maven.apache.org/settings.html#Simple_Values) Keep in mind that the cache is not concurrent safe, and is definitely not designed

avoiding to write into user home

i got this report http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/178529 user complaining about maven writing to home directory during compile. Is there any command line argument to prevent this (to turn off caching). - To un