Upgraded to Maven 3 - now the clean goal deletes entire module directories?
Hi all! I just upgraded to Maven 3. Now, when I run mvn clean on a multi-module project it will delete each module entirely, rather than just the target directories contained within each module directory (which is how it used to work in Maven 2). Anyone have any idea what I might be doing wrong here? Cheers, - hugi // Hugi Thordarson // http://hugi.karlmenn.is/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Upgraded to Maven 3 - now the clean goal deletes entire module directories?
Greetings, On Sun, Jul 31, 2011 at 10:28 AM, Hugi Thordarson h...@karlmenn.is wrote: I just upgraded to Maven 3. Now, when I run mvn clean on a multi-module project it will delete each module entirely, rather than just the target directories contained within each module directory (which is how it used to work in Maven 2). Anyone have any idea what I might be doing wrong here? Maven output or it didn't happen. I simply do not believe this is what is happening unless you've somehow attached to clean phase an antrun execution to delete all your modules.. or you've put them under build.outputDirectory. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Upgraded to Maven 3 - now the clean goal deletes entire module directories?
Hi Jessie, You inspired me to do quick search for outputDirectory in all the POMs and I found this little bugger in all the projects' common parent pom: reporting outputDirectory / [ … ] /reporting Not sure what purpose it served - but once removed, the projects behave as expected in Maven 3 :). Thanks for the help! - hugi // Hugi Thordarson // http://hugi.karlmenn.is/ On 31.7.2011, at 14:38, Jesse Farinacci wrote: Greetings, On Sun, Jul 31, 2011 at 10:28 AM, Hugi Thordarson h...@karlmenn.is wrote: I just upgraded to Maven 3. Now, when I run mvn clean on a multi-module project it will delete each module entirely, rather than just the target directories contained within each module directory (which is how it used to work in Maven 2). Anyone have any idea what I might be doing wrong here? Maven output or it didn't happen. I simply do not believe this is what is happening unless you've somehow attached to clean phase an antrun execution to delete all your modules.. or you've put them under build.outputDirectory. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Upgraded to Maven 3 - now the clean goal deletes entire module directories?
Greetings, On Sun, Jul 31, 2011 at 10:53 AM, Hugi Thordarson h...@karlmenn.is wrote: You inspired me to do quick search for outputDirectory in all the POMs and I found this little bugger in all the projects' common parent pom: reporting outputDirectory / /reporting Not sure what purpose it served - but once removed, the projects behave as expected in Maven 3 :). Glad you figured it out. Having an empty outputDirectory must make it default to the modules working directory. Then your clean would convert the build into a digital Ouroboros of disaster. Maybe Maven 3, in its aim to better inform users about code smells, should warn users of this perilous condition. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Upgraded to Maven 3 - now the clean goal deletes entire module directories?
a digital Ouroboros of disaster -- that made my day. On Sun, Jul 31, 2011 at 11:03 AM, Jesse Farinacci jie...@gmail.com wrote: Greetings, On Sun, Jul 31, 2011 at 10:53 AM, Hugi Thordarson h...@karlmenn.is wrote: You inspired me to do quick search for outputDirectory in all the POMs and I found this little bugger in all the projects' common parent pom: reporting outputDirectory / /reporting Not sure what purpose it served - but once removed, the projects behave as expected in Maven 3 :). Glad you figured it out. Having an empty outputDirectory must make it default to the modules working directory. Then your clean would convert the build into a digital Ouroboros of disaster. Maybe Maven 3, in its aim to better inform users about code smells, should warn users of this perilous condition. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Upgraded to Maven 3 - now the clean goal deletes entire module directories?
Hi again, You inspired me to do quick search for outputDirectory in all the POMs and I found this little bugger in all the projects' common parent pom: reporting outputDirectory / /reporting Not sure what purpose it served - but once removed, the projects behave as expected in Maven 3 :). Glad you figured it out. Having an empty outputDirectory must make it default to the modules working directory. Then your clean would convert the build into a digital Ouroboros of disaster. Yes, that's what I figured (and confirmed by building some javadocs). Maybe Maven 3, in its aim to better inform users about code smells, should warn users of this perilous condition. Yes, that would be clever. Although Maven 3 is really just doing the right thing with a somewhat silly configuration :-). Thanks again, - hugi - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Upgraded to Maven 3 - now the clean goal deletes entire module directories?
If you file a jira ticket ([1]) suggesting this it could actually get implemented instead of just being a clever idea... /Anders [1] http://jira.codehaus.org/browse/MNG On Sun, Jul 31, 2011 at 17:16, Hugi Thordarson h...@karlmenn.is wrote: Hi again, You inspired me to do quick search for outputDirectory in all the POMs and I found this little bugger in all the projects' common parent pom: reporting outputDirectory / /reporting Not sure what purpose it served - but once removed, the projects behave as expected in Maven 3 :). Glad you figured it out. Having an empty outputDirectory must make it default to the modules working directory. Then your clean would convert the build into a digital Ouroboros of disaster. Yes, that's what I figured (and confirmed by building some javadocs). Maybe Maven 3, in its aim to better inform users about code smells, should warn users of this perilous condition. Yes, that would be clever. Although Maven 3 is really just doing the right thing with a somewhat silly configuration :-). Thanks again, - hugi - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Upgraded to Maven 3 - now the clean goal deletes entire module directories?
What!? You mean the developers don't pick up messages telepathically? :o) But really, I'm not sure if it's really that clever. It's a little like filing a ticket saying rm -rf ~ deletes my home directory. - hugi On 31.7.2011, at 18:42, Anders Hammar wrote: If you file a jira ticket ([1]) suggesting this it could actually get implemented instead of just being a clever idea... /Anders [1] http://jira.codehaus.org/browse/MNG On Sun, Jul 31, 2011 at 17:16, Hugi Thordarson h...@karlmenn.is wrote: Hi again, You inspired me to do quick search for outputDirectory in all the POMs and I found this little bugger in all the projects' common parent pom: reporting outputDirectory / /reporting Not sure what purpose it served - but once removed, the projects behave as expected in Maven 3 :). Glad you figured it out. Having an empty outputDirectory must make it default to the modules working directory. Then your clean would convert the build into a digital Ouroboros of disaster. Yes, that's what I figured (and confirmed by building some javadocs). Maybe Maven 3, in its aim to better inform users about code smells, should warn users of this perilous condition. Yes, that would be clever. Although Maven 3 is really just doing the right thing with a somewhat silly configuration :-). Thanks again, - hugi - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
latest snapshot not downloaded
Hello, Even with updatePolicy of always or -U, maven is not downloading the latest snapshot dependency from my http repository (artifactory). I can see that the maven-metadata*.xml files are being updated. Can anyone recommend the best way to debug the issue, in order to see exactly what is going on? Using -X doesn't really tell me why maven thinks the jar in my local repo is up to date. The filesystem timestamp of the jar in my local repo is older than the value in the maven-metadata*.xml on the server, so I would expect the jar to be downloaded again. Thanks! Brian
Re: Upgraded to Maven 3 - now the clean goal deletes entire module directories?
I was rather thinking of the warning that Maven could print to the console output about this kind of bad/strange pom declaration. (Although the reporting section isn't really touched by Maven 3 core I think but just the site plugin.) /Anders On Sun, Jul 31, 2011 at 20:50, Hugi Thordarson h...@karlmenn.is wrote: What!? You mean the developers don't pick up messages telepathically? :o) But really, I'm not sure if it's really that clever. It's a little like filing a ticket saying rm -rf ~ deletes my home directory. - hugi On 31.7.2011, at 18:42, Anders Hammar wrote: If you file a jira ticket ([1]) suggesting this it could actually get implemented instead of just being a clever idea... /Anders [1] http://jira.codehaus.org/browse/MNG On Sun, Jul 31, 2011 at 17:16, Hugi Thordarson h...@karlmenn.is wrote: Hi again, You inspired me to do quick search for outputDirectory in all the POMs and I found this little bugger in all the projects' common parent pom: reporting outputDirectory / /reporting Not sure what purpose it served - but once removed, the projects behave as expected in Maven 3 :). Glad you figured it out. Having an empty outputDirectory must make it default to the modules working directory. Then your clean would convert the build into a digital Ouroboros of disaster. Yes, that's what I figured (and confirmed by building some javadocs). Maybe Maven 3, in its aim to better inform users about code smells, should warn users of this perilous condition. Yes, that would be clever. Although Maven 3 is really just doing the right thing with a somewhat silly configuration :-). Thanks again, - hugi - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: latest snapshot not downloaded
Sorry, forgot to mention I'm using maven 3.0.3, on Mac. Brian On Sun, Jul 31, 2011 at 2:14 PM, Brian Parker onebrianpar...@gmail.comwrote: Hello, Even with updatePolicy of always or -U, maven is not downloading the latest snapshot dependency from my http repository (artifactory). I can see that the maven-metadata*.xml files are being updated. Can anyone recommend the best way to debug the issue, in order to see exactly what is going on? Using -X doesn't really tell me why maven thinks the jar in my local repo is up to date. The filesystem timestamp of the jar in my local repo is older than the value in the maven-metadata*.xml on the server, so I would expect the jar to be downloaded again. Thanks! Brian
Re: Upgraded to Maven 3 - now the clean goal deletes entire module directories?
http://jira.codehaus.org/browse/MNG-5144 On Sun, Jul 31, 2011 at 2:42 PM, Anders Hammar and...@hammar.net wrote: If you file a jira ticket ([1]) suggesting this it could actually get implemented instead of just being a clever idea... [1] http://jira.codehaus.org/browse/MNG -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Upgraded to Maven 3 - now the clean goal deletes entire module directories?
IMHO allowing the configuration outputDirectory/ just seems silly in itself and should probably throw a MojoException or something. If you REALLLY wanted that directory then you could use $baseDir or something. On 1/08/2011, at 3:16 AM, Hugi Thordarson wrote: Yes, that would be clever. Although Maven 3 is really just doing the right thing with a somewhat silly configuration :-).
Re: latest snapshot not downloaded
I believe that this is a known issue with a fix already committed for the next release. I don't personally know a work-around. On Sun, Jul 31, 2011 at 3:23 PM, Brian Parker onebrianpar...@gmail.com wrote: Sorry, forgot to mention I'm using maven 3.0.3, on Mac. Brian On Sun, Jul 31, 2011 at 2:14 PM, Brian Parker onebrianpar...@gmail.comwrote: Hello, Even with updatePolicy of always or -U, maven is not downloading the latest snapshot dependency from my http repository (artifactory). I can see that the maven-metadata*.xml files are being updated. Can anyone recommend the best way to debug the issue, in order to see exactly what is going on? Using -X doesn't really tell me why maven thinks the jar in my local repo is up to date. The filesystem timestamp of the jar in my local repo is older than the value in the maven-metadata*.xml on the server, so I would expect the jar to be downloaded again. Thanks! Brian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: latest snapshot not downloaded
This turned out to be an Artifactory configuration error with regard to Maven 3 and non unique snapshots. This page has a blurb about it: http://wiki.jfrog.org/confluence/display/RTF/Local+Repositories Thanks! Brian On Sun, Jul 31, 2011 at 2:23 PM, Brian Parker onebrianpar...@gmail.comwrote: Sorry, forgot to mention I'm using maven 3.0.3, on Mac. Brian On Sun, Jul 31, 2011 at 2:14 PM, Brian Parker onebrianpar...@gmail.comwrote: Hello, Even with updatePolicy of always or -U, maven is not downloading the latest snapshot dependency from my http repository (artifactory). I can see that the maven-metadata*.xml files are being updated. Can anyone recommend the best way to debug the issue, in order to see exactly what is going on? Using -X doesn't really tell me why maven thinks the jar in my local repo is up to date. The filesystem timestamp of the jar in my local repo is older than the value in the maven-metadata*.xml on the server, so I would expect the jar to be downloaded again. Thanks! Brian
There are no tests to run.
hi, my name is Tony , I'm from China. At present time,i do a small project named 52n-wps. the below is a part of my pom.xml .I guess the maven-surefire-plugins may have some problems. so i appreciate you could tell me what the problems is. thanks! plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.4.3/version configuration includes include**Test*.java/include /includes /configuration /plugin when i run the maven instal function of maven. Then I get : [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building 52north 52n-wps-commons 2.0-RC8-SNAPSHOT [INFO] [INFO] [INFO] --- maven-resources-plugin:2.3:resources (default-resources) @ 52n-wps-commons --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 0 resource [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 52n-wps-commons --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-resources-plugin:2.3:testResources (default-testResources) @ 52n-wps-commons --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory C:\Users\keen\workspace\52n-wps\52n-wps-commons\src\test\resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 52n-wps-commons --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.4.3:test (default-test) @ 52n-wps-commons --- [INFO] Surefire report directory: C:\Users\keen\workspace\52n-wps\52n-wps-commons\target\surefire-reports --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 52n-wps-commons --- [INFO] Building jar: C:\Users\keen\workspace\52n-wps\52n-wps-commons\target\52n-wps-commons-2.0-RC8-SNAPSHOT.jar [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 52n-wps-commons --- [INFO] Installing C:\Users\keen\workspace\52n-wps\52n-wps-commons\target\52n-wps-commons-2.0-RC8-SNAPSHOT.jar to C:\Users\keen\.m2\repository\org\n52\wps\52n-wps-commons\2.0-RC8-SNAPSHOT\52n-wps-commons-2.0-RC8-SNAPSHOT.jar [INFO] Installing C:\Users\keen\workspace\52n-wps\52n-wps-commons\pom.xml to C:\Users\keen\.m2\repository\org\n52\wps\52n-wps-commons\2.0-RC8-SNAPSHOT\52n-wps-commons-2.0-RC8-SNAPSHOT.pom [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 1.584s [INFO] Finished at: Sat Jul 30 20:50:36 CST 2011 [INFO] Final Memory: 4M/90M [INFO] -- View this message in context: http://maven.40175.n5.nabble.com/There-are-no-tests-to-run-tp4650980p4650980.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: There are no tests to run.
Hello, Check your test sources place (default is src/test/java) as I can read in the logs [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @52n-wps-commons --- [INFO] No sources to compile And use include**/*Test*.java/include (or none default are **/Test*.java, **/*Test.java, **/*TestCase.java) -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy 2011/7/31 tony liub...@gmail.com: hi, my name is Tony , I'm from China. At present time,i do a small project named 52n-wps. the below is a part of my pom.xml .I guess the maven-surefire-plugins may have some problems. so i appreciate you could tell me what the problems is. thanks! plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.4.3/version configuration includes include**Test*.java/include /includes /configuration /plugin when i run the maven instal function of maven. Then I get : [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building 52north 52n-wps-commons 2.0-RC8-SNAPSHOT [INFO] [INFO] [INFO] --- maven-resources-plugin:2.3:resources (default-resources) @ 52n-wps-commons --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 0 resource [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 52n-wps-commons --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-resources-plugin:2.3:testResources (default-testResources) @ 52n-wps-commons --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory C:\Users\keen\workspace\52n-wps\52n-wps-commons\src\test\resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 52n-wps-commons --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.4.3:test (default-test) @ 52n-wps-commons --- [INFO] Surefire report directory: C:\Users\keen\workspace\52n-wps\52n-wps-commons\target\surefire-reports --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 52n-wps-commons --- [INFO] Building jar: C:\Users\keen\workspace\52n-wps\52n-wps-commons\target\52n-wps-commons-2.0-RC8-SNAPSHOT.jar [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 52n-wps-commons --- [INFO] Installing C:\Users\keen\workspace\52n-wps\52n-wps-commons\target\52n-wps-commons-2.0-RC8-SNAPSHOT.jar to C:\Users\keen\.m2\repository\org\n52\wps\52n-wps-commons\2.0-RC8-SNAPSHOT\52n-wps-commons-2.0-RC8-SNAPSHOT.jar [INFO] Installing C:\Users\keen\workspace\52n-wps\52n-wps-commons\pom.xml to C:\Users\keen\.m2\repository\org\n52\wps\52n-wps-commons\2.0-RC8-SNAPSHOT\52n-wps-commons-2.0-RC8-SNAPSHOT.pom [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 1.584s [INFO] Finished at: Sat Jul 30 20:50:36 CST 2011 [INFO] Final Memory: 4M/90M [INFO] -- View this message in context: http://maven.40175.n5.nabble.com/There-are-no-tests-to-run-tp4650980p4650980.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Getting strange error in compilation
Anyone else seen this? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project seaglasslookandfeel: Compilation failure [ERROR] Failure executing javac, but could not parse the error: [ERROR] Fatal Error: Unable to find package java.lang in classpath or bootclasspath This is code that used to work. I'm running JDK 1.6.0_26 on Mac OS X 10.6.8 (Snow Leopard). This is Maven 3.0.3. -K - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting strange error in compilation
Okay, I see. Apple changed the location of classes.jar, which is what they call rt.jar in a recent release of Java, possibly update 26. -K On Jul 31, 2011, at 5:39 PM, Kathryn Huxtable wrote: Anyone else seen this? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project seaglasslookandfeel: Compilation failure [ERROR] Failure executing javac, but could not parse the error: [ERROR] Fatal Error: Unable to find package java.lang in classpath or bootclasspath This is code that used to work. I'm running JDK 1.6.0_26 on Mac OS X 10.6.8 (Snow Leopard). This is Maven 3.0.3. -K - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting strange error in compilation
On Mon, Aug 1, 2011 at 8:23 AM, Kathryn Huxtable kath...@kathrynhuxtable.org wrote: Okay, I see. Apple changed the location of classes.jar, which is what they call rt.jar in a recent release of Java, possibly update 26. How did you fix this then? Do we need to configure maven to understand this natively? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting strange error in compilation
I've been working on a Swing pluggable look feel, and was needing to include
rt.jar. I have a separate profile for the Mac. The relevant sections of my pom
look like:
...
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
configuration
source1.6/source
target1.6/target
compilerArguments
bootclasspath${java.home}/lib/rt.jar/bootclasspath
/compilerArguments
/configuration
/plugin
/plugins
...
profiles
profile
idmac/id
activation
os
familymac/family
/os
/activation
build
plugins
!-- Configure the compiler plugin to use JDK
1.6. --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
configuration
source1.6/source
target1.6/target
compilerArguments
bootclasspath${java.home}/bundle/Classes/classes.jar/bootclasspath
/compilerArguments
/configuration
/plugin
/plugins
/build
/profile
...
I think most artifacts don't need to include rt.jar, so I don't know what you'd
do. I suppose we can add the JDK version to the activation profile...
I don't think you folks need to do anything, but I was bewildered, and Google
wasn't much help, though I did eventually find a solution through a Google
search, just not the first several I tried.
-K
On Jul 31, 2011, at 6:27 PM, Barrie Treloar wrote:
On Mon, Aug 1, 2011 at 8:23 AM, Kathryn Huxtable
kath...@kathrynhuxtable.org wrote:
Okay, I see. Apple changed the location of classes.jar, which is what they
call rt.jar in a recent release of Java, possibly update 26.
How did you fix this then?
Do we need to configure maven to understand this natively?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting strange error in compilation
Actually, can I require that a profile be activated when both a jdk version
*and* an os family are selected, or is it always an or comparison? -K
On Jul 31, 2011, at 6:41 PM, Kathryn Huxtable wrote:
I've been working on a Swing pluggable look feel, and was needing to
include rt.jar. I have a separate profile for the Mac. The relevant sections
of my pom look like:
...
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
configuration
source1.6/source
target1.6/target
compilerArguments
bootclasspath${java.home}/lib/rt.jar/bootclasspath
/compilerArguments
/configuration
/plugin
/plugins
...
profiles
profile
idmac/id
activation
os
familymac/family
/os
/activation
build
plugins
!-- Configure the compiler plugin to use JDK
1.6. --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
configuration
source1.6/source
target1.6/target
compilerArguments
bootclasspath${java.home}/bundle/Classes/classes.jar/bootclasspath
/compilerArguments
/configuration
/plugin
/plugins
/build
/profile
...
I think most artifacts don't need to include rt.jar, so I don't know what
you'd do. I suppose we can add the JDK version to the activation profile...
I don't think you folks need to do anything, but I was bewildered, and Google
wasn't much help, though I did eventually find a solution through a Google
search, just not the first several I tried.
-K
On Jul 31, 2011, at 6:27 PM, Barrie Treloar wrote:
On Mon, Aug 1, 2011 at 8:23 AM, Kathryn Huxtable
kath...@kathrynhuxtable.org wrote:
Okay, I see. Apple changed the location of classes.jar, which is what they
call rt.jar in a recent release of Java, possibly update 26.
How did you fix this then?
Do we need to configure maven to understand this natively?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting strange error in compilation
I think the way for me to solve this is to use
fileexistsblah/exists/file in two different profiles checking for the
two different locations of classes.jar. If neither exists, we'll use the
default profile, which points to the Windows/Linux location.
I assume that when Oracle actually releases a Mac Java, they will use the
standard locations for these things rather than Apple's non-standard locations,
but it's just an assumption. I'm not counting on anything, including that
Oracle will even release a Mac Java. ;-)
-K
On Jul 31, 2011, at 6:44 PM, Kathryn Huxtable wrote:
Actually, can I require that a profile be activated when both a jdk version
*and* an os family are selected, or is it always an or comparison? -K
On Jul 31, 2011, at 6:41 PM, Kathryn Huxtable wrote:
I've been working on a Swing pluggable look feel, and was needing to
include rt.jar. I have a separate profile for the Mac. The relevant sections
of my pom look like:
...
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
configuration
source1.6/source
target1.6/target
compilerArguments
bootclasspath${java.home}/lib/rt.jar/bootclasspath
/compilerArguments
/configuration
/plugin
/plugins
...
profiles
profile
idmac/id
activation
os
familymac/family
/os
/activation
build
plugins
!-- Configure the compiler plugin to use JDK
1.6. --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
configuration
source1.6/source
target1.6/target
compilerArguments
bootclasspath${java.home}/bundle/Classes/classes.jar/bootclasspath
/compilerArguments
/configuration
/plugin
/plugins
/build
/profile
...
I think most artifacts don't need to include rt.jar, so I don't know what
you'd do. I suppose we can add the JDK version to the activation profile...
I don't think you folks need to do anything, but I was bewildered, and
Google wasn't much help, though I did eventually find a solution through a
Google search, just not the first several I tried.
-K
On Jul 31, 2011, at 6:27 PM, Barrie Treloar wrote:
On Mon, Aug 1, 2011 at 8:23 AM, Kathryn Huxtable
kath...@kathrynhuxtable.org wrote:
Okay, I see. Apple changed the location of classes.jar, which is what they
call rt.jar in a recent release of Java, possibly update 26.
How did you fix this then?
Do we need to configure maven to understand this natively?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting strange error in compilation
On Mon, Aug 1, 2011 at 9:14 AM, Kathryn Huxtable kath...@kathrynhuxtable.org wrote: Actually, can I require that a profile be activated when both a jdk version *and* an os family are selected, or is it always an or comparison? -K You know, I dont know. You might be better starting a separate thread to ask that question. My googling gets me contradictory answers. http://www.google.com/search?q=maven+profile+activation The POM reference docs (http://maven.apache.org/pom.html#Activation) * Activation occurs when one or more of the specified criteria have been met. When the first positive result is encountered, processing stops and the profile is marked as active. Introduction to Build Profiles (http://maven.apache.org/guides/introduction/introduction-to-profiles.html) * Doesn't have any examples that use multiple values within activation Maven: The Complete Reference Section 5.3. Profile Activation (http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html) * Activations can contain one of more selectors including JDK versions, Operating System parameters, files, and properties. A profile is activated when all activation criteria has been satisfied. So I suggest you try multiple and find out what happens. Then we need to create a JIRA to fix the documentation... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting strange error in compilation
What do you get from: find `/usr/libexec/java_home`/.. -name classes.jar -print ? I get: /Library/Java/JavaVirtualMachines/1.6.0_26-b03-384.jdk/Contents/Home/../Classes/classes.jar On Sun, Jul 31, 2011 at 7:55 PM, Barrie Treloar baerr...@gmail.com wrote: On Mon, Aug 1, 2011 at 9:14 AM, Kathryn Huxtable kath...@kathrynhuxtable.org wrote: Actually, can I require that a profile be activated when both a jdk version *and* an os family are selected, or is it always an or comparison? -K You know, I dont know. You might be better starting a separate thread to ask that question. My googling gets me contradictory answers. http://www.google.com/search?q=maven+profile+activation The POM reference docs (http://maven.apache.org/pom.html#Activation) * Activation occurs when one or more of the specified criteria have been met. When the first positive result is encountered, processing stops and the profile is marked as active. Introduction to Build Profiles (http://maven.apache.org/guides/introduction/introduction-to-profiles.html) * Doesn't have any examples that use multiple values within activation Maven: The Complete Reference Section 5.3. Profile Activation (http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html) * Activations can contain one of more selectors including JDK versions, Operating System parameters, files, and properties. A profile is activated when all activation criteria has been satisfied. So I suggest you try multiple and find out what happens. Then we need to create a JIRA to fix the documentation... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use the latest version from dependencies (not from all repository)
On 30/07/2011 7:16 AM, boraldo wrote: I don't need to make maven use A version that is inherited from C exactly. I want Maven to define the latest version automatically, without explicit definition. Not a good idea. You want a repeatable build with a specific version of A so you know what you are running. And I don't want to release new version of B only to fix it's A version. A:1.0 is suitable for B, so there's no need to change it. In real life I have a lot of artifacts. Some of them are stable and I don't want to update all them once new version of some middle artifact is changed. It is worth the effort to decide what version of things you are using. Having maven pick the latest version when you have not tested your software with that version is a recipe for long and painful debugging session that are surprises to everyone involved. We use 70+ third party libraries to build our application comprised of over 80 maven projects and every dependency is specified. We do not upgrade to a new version of anything unless everyone is aware of the change and someone reads the release notes to verify upward compatibility and tests the new version with our software. This makes individual developers confident that what they tested yesterday was only broken by what they did today not some random fix applied by a stranger to some library that they did not know was a dependency of a dependency. It takes an hour or so to plan a new release and every now and again a developer asks for a version upgrade in the middle of a development cycle which creates a min-project to verify that the new version does not break anything that we have done. That is a lot less than the time lost by a surprise update of a dependency by an Apache project or some other third party that breaks your code. There is a good reason why dependencies have versions. You may think that we are just too lazy to live on the edge but we have learned that it is better to plan than debug. Ron -- View this message in context: http://maven.40175.n5.nabble.com/How-to-use-the-latest-version-from-dependencies-not-from-all-repository-tp4642240p4649537.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: There are no tests to run.
Thanks for your reply, And now My question is I don't know what is my testSourceDirectory, http://maven.40175.n5.nabble.com/file/n4653638/QQ%E6%88%AA%E5%9B%BE20110801084048.png -- View this message in context: http://maven.40175.n5.nabble.com/There-are-no-tests-to-run-tp4650980p4653638.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: There are no tests to run.
On 31 July 2011 17:43, tony liub...@gmail.com wrote: Thanks for your reply, And now My question is I don't know what is my testSourceDirectory, http://maven.40175.n5.nabble.com/file/n4653638/QQ%E6%88%AA%E5%9B%BE20110801084048.png src/test/java which you do not appear to have. That would explain no tests being run. :-) Did you look at [1]? Make sure you follow the link to [2]. [1] http://maven.apache.org/guides/getting-started/index.html [2] http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting strange error in compilation
My test indicated that it's an and/or. -K On Jul 31, 2011, at 6:55 PM, Barrie Treloar wrote: On Mon, Aug 1, 2011 at 9:14 AM, Kathryn Huxtable kath...@kathrynhuxtable.org wrote: Actually, can I require that a profile be activated when both a jdk version *and* an os family are selected, or is it always an or comparison? -K You know, I dont know. You might be better starting a separate thread to ask that question. My googling gets me contradictory answers. http://www.google.com/search?q=maven+profile+activation The POM reference docs (http://maven.apache.org/pom.html#Activation) * Activation occurs when one or more of the specified criteria have been met. When the first positive result is encountered, processing stops and the profile is marked as active. Introduction to Build Profiles (http://maven.apache.org/guides/introduction/introduction-to-profiles.html) * Doesn't have any examples that use multiple values within activation Maven: The Complete Reference Section 5.3. Profile Activation (http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html) * Activations can contain one of more selectors including JDK versions, Operating System parameters, files, and properties. A profile is activated when all activation criteria has been satisfied. So I suggest you try multiple and find out what happens. Then we need to create a JIRA to fix the documentation... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting strange error in compilation
I get: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../Classes/classes.jar -K On Jul 31, 2011, at 7:22 PM, Benson Margulies wrote: What do you get from: find `/usr/libexec/java_home`/.. -name classes.jar -print ? I get: /Library/Java/JavaVirtualMachines/1.6.0_26-b03-384.jdk/Contents/Home/../Classes/classes.jar On Sun, Jul 31, 2011 at 7:55 PM, Barrie Treloar baerr...@gmail.com wrote: On Mon, Aug 1, 2011 at 9:14 AM, Kathryn Huxtable kath...@kathrynhuxtable.org wrote: Actually, can I require that a profile be activated when both a jdk version *and* an os family are selected, or is it always an or comparison? -K You know, I dont know. You might be better starting a separate thread to ask that question. My googling gets me contradictory answers. http://www.google.com/search?q=maven+profile+activation The POM reference docs (http://maven.apache.org/pom.html#Activation) * Activation occurs when one or more of the specified criteria have been met. When the first positive result is encountered, processing stops and the profile is marked as active. Introduction to Build Profiles (http://maven.apache.org/guides/introduction/introduction-to-profiles.html) * Doesn't have any examples that use multiple values within activation Maven: The Complete Reference Section 5.3. Profile Activation (http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html) * Activations can contain one of more selectors including JDK versions, Operating System parameters, files, and properties. A profile is activated when all activation criteria has been satisfied. So I suggest you try multiple and find out what happens. Then we need to create a JIRA to fix the documentation... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
