Re: war plugin incompatibility
I think that I have fixed this problem by adding the following stanza to the maven war plugin descriptor: false On 11/9/23 2:46 PM, Rick Hillegas wrote: I am trying to install a Derby release into my local maven repository. The world has changed underneath me in the last year and a half since I published the last Derby release. The Derby maven-based publication poms can be found under https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/ The Derby publication poms don't do much. They just sign the Derby artifacts and copy them into the repository. No jars or wars are actually built by the publication poms. That happens elsewhere. On my first attempt, I used the maven version I used a year and a half ago: 3.8.6. One of the Derby artifacts is a war file and its associated publication pom contained this plugin stanza: org.apache.maven.plugins maven-war-plugin 2.1.1 When I executed a top level mvn clean install the command failed with the following error: [WARNING] Error injecting: org.apache.maven.plugin.war.WarMojo com.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Error injecting constructor, java.lang.ExceptionInInitializerError: Cannot access defaults field of Properties at org.apache.maven.plugin.war.WarMojo.(Unknown Source) while locating org.apache.maven.plugin.war.WarMojo followed at the end by [ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on project derbywar: Execution default-war of goal org.apache.maven.plugins:maven-war-plugin:2.1.1:war failed: Unable to load the mojo 'war' in the plugin 'org.apache.maven.plugins:maven-war-plugin:2.1.1' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Cannot access defaults field of Properties So I upgraded maven to version 3.9.5 and I upgraded the war plugin stanza to specify maven plugin version 3.3.1. Now "mvn clean install" raises the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:3.3.1:war (default-war) on project derbywar: Error assembling WAR: webxml attribute is required (or pre-existing WEB-INF/web.xml if executing in update mode) -> [Help 1] Since all I am doing is signing jars and wars, I don't think that a web.xml file should be required. I would appreciate your advice for how to get over this speedbump. Thanks, -Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
war plugin incompatibility
I am trying to install a Derby release into my local maven repository. The world has changed underneath me in the last year and a half since I published the last Derby release. The Derby maven-based publication poms can be found under https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/ The Derby publication poms don't do much. They just sign the Derby artifacts and copy them into the repository. No jars or wars are actually built by the publication poms. That happens elsewhere. On my first attempt, I used the maven version I used a year and a half ago: 3.8.6. One of the Derby artifacts is a war file and its associated publication pom contained this plugin stanza: org.apache.maven.plugins maven-war-plugin 2.1.1 When I executed a top level mvn clean install the command failed with the following error: [WARNING] Error injecting: org.apache.maven.plugin.war.WarMojo com.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Error injecting constructor, java.lang.ExceptionInInitializerError: Cannot access defaults field of Properties at org.apache.maven.plugin.war.WarMojo.(Unknown Source) while locating org.apache.maven.plugin.war.WarMojo followed at the end by [ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on project derbywar: Execution default-war of goal org.apache.maven.plugins:maven-war-plugin:2.1.1:war failed: Unable to load the mojo 'war' in the plugin 'org.apache.maven.plugins:maven-war-plugin:2.1.1' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Cannot access defaults field of Properties So I upgraded maven to version 3.9.5 and I upgraded the war plugin stanza to specify maven plugin version 3.3.1. Now "mvn clean install" raises the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:3.3.1:war (default-war) on project derbywar: Error assembling WAR: webxml attribute is required (or pre-existing WEB-INF/web.xml if executing in update mode) -> [Help 1] Since all I am doing is signing jars and wars, I don't think that a web.xml file should be required. I would appreciate your advice for how to get over this speedbump. Thanks, -Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: peer not authenticated error
INFRA advised me to upgrade to maven 3.8.6. That did not fix the problem. It then occurred to me to follow the terminal advice from the failed upload: [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :derbyLocale_ko_KR Even though there were no errors to correct, I issued that command. The upload continued without further errors. I verified that the artifacts were all uploaded to the Nexus staging repository. Thanks to everyone who helped me puzzle through this, -Rick On 6/14/22 6:51 AM, Rick Hillegas wrote: Thanks for looking at the pom, Slawomir. As part of the publication process, we run a program which replaces all of those ALPHA_VERSION tokens with the actual release id (in this case, 10.16.1.1). On 6/14/22 1:19 AM, Slawomir Jaranowski wrote: Hi, In your project I see: derby-project ALPHA_VERSION Please try to change project version to SNAPSHOT (all modules), eg 10.16.0-SNAPSHOT , you can use mvn versions:set -DnewVersion=10.16.0-SNAPSHOT and than try mvn deploy Please note that you can not override release version. wt., 14 cze 2022 o 10:00 Tamás Cservenák napisał(a): Howdy, So is the "peer not authenticated" error still sporadically happening? Qs: - can you use some LTS java instead of 18? (17 or 11?) - could you execute the build with -e (or -X but this will give you a LOT of logs) and paste the stack trace? - you sure you are directly accessing repo.a.o, no proxy or whatever in between your maven process and repo.a.o? HTH T On Tue, Jun 14, 2022 at 12:10 AM Rick Hillegas wrote: Thanks, Tamas. On your advice, I updated the top level pom to refer to version 26 of the parent apache pom. This caused the maven-antrun-plugin to object that a major upgrade had obsoleted the element. I was advised to change to . I did that too. However, I am still seeing "peer not authenticated" messages. On 6/13/22 11:15 AM, Tamás Cservenák wrote: Howdy, Well, sadly I see that svn tag is in place, but the very first observation I have is that due to ancient parent Apache POM version 10, you use ancient plugins despite the latest Maven being used. Please try to upgrade parent to current one (current version is 26). So in here https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/pom.xml make project/parent/version = 26 Parent version 10 you use is from 2011 hence you use plugins that are 11 years old or older, made for Maven2, and I really have no idea what kind of bug(s) may be hit here... Note: ASF parent 10 says java level is 1.4... so this may need some alignment as well... Also, why Java 18? Is it needed or is it just handy? (I'd go with some LTS rather) Other than that, given the sporadic nature of the error, I really can't say more, maybe some misbehaving proxy in between maven process and repo.apache.org? HTH Tamas On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas wrote: I need advice about how to move past a "peer not authenticated" error. I am trying to stage some 20 jars and corresponding poms via the following command: mvn -Dgpg.passphrase="my secret passphrase" clean deploy I am able to upload most of the artifacts, but the command eventually fails with a "peer not authenticated" error. The artifact which incurs this error is not consistent. I have tried this from two different locations (Palm Springs and San Francisco). But I can't get to the end of the upload without a "peer not authenticated" error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): transfer failed for https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc : peer not authenticated -> [Help 1] Here is my environment: maven 3.8.5 OpenJDK Runtime Environment 18.9 (build 11+28) Based on some advice I found on the internet, I tried adding the following stanza to my top level pom: ... org.apache.maven.plugins maven-deploy-plugin 3 That does not fix the problem. Any help you can give me would be appreciated. Thanks, Rick - 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: peer not authenticated error
Thanks for looking at the pom, Slawomir. As part of the publication process, we run a program which replaces all of those ALPHA_VERSION tokens with the actual release id (in this case, 10.16.1.1). On 6/14/22 1:19 AM, Slawomir Jaranowski wrote: Hi, In your project I see: derby-project ALPHA_VERSION Please try to change project version to SNAPSHOT (all modules), eg 10.16.0-SNAPSHOT , you can use mvn versions:set -DnewVersion=10.16.0-SNAPSHOT and than try mvn deploy Please note that you can not override release version. wt., 14 cze 2022 o 10:00 Tamás Cservenák napisał(a): Howdy, So is the "peer not authenticated" error still sporadically happening? Qs: - can you use some LTS java instead of 18? (17 or 11?) - could you execute the build with -e (or -X but this will give you a LOT of logs) and paste the stack trace? - you sure you are directly accessing repo.a.o, no proxy or whatever in between your maven process and repo.a.o? HTH T On Tue, Jun 14, 2022 at 12:10 AM Rick Hillegas wrote: Thanks, Tamas. On your advice, I updated the top level pom to refer to version 26 of the parent apache pom. This caused the maven-antrun-plugin to object that a major upgrade had obsoleted the element. I was advised to change to . I did that too. However, I am still seeing "peer not authenticated" messages. On 6/13/22 11:15 AM, Tamás Cservenák wrote: Howdy, Well, sadly I see that svn tag is in place, but the very first observation I have is that due to ancient parent Apache POM version 10, you use ancient plugins despite the latest Maven being used. Please try to upgrade parent to current one (current version is 26). So in here https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/pom.xml make project/parent/version = 26 Parent version 10 you use is from 2011 hence you use plugins that are 11 years old or older, made for Maven2, and I really have no idea what kind of bug(s) may be hit here... Note: ASF parent 10 says java level is 1.4... so this may need some alignment as well... Also, why Java 18? Is it needed or is it just handy? (I'd go with some LTS rather) Other than that, given the sporadic nature of the error, I really can't say more, maybe some misbehaving proxy in between maven process and repo.apache.org? HTH Tamas On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas I need advice about how to move past a "peer not authenticated" error. I am trying to stage some 20 jars and corresponding poms via the following command: mvn -Dgpg.passphrase="my secret passphrase" clean deploy I am able to upload most of the artifacts, but the command eventually fails with a "peer not authenticated" error. The artifact which incurs this error is not consistent. I have tried this from two different locations (Palm Springs and San Francisco). But I can't get to the end of the upload without a "peer not authenticated" error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): transfer failed for https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc : peer not authenticated -> [Help 1] Here is my environment: maven 3.8.5 OpenJDK Runtime Environment 18.9 (build 11+28) Based on some advice I found on the internet, I tried adding the following stanza to my top level pom: ... org.apache.maven.plugins maven-deploy-plugin 3 That does not fix the problem. Any help you can give me would be appreciated. Thanks, Rick - 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: peer not authenticated error
Thanks for the additional advice, Tamas. Infra is going to restart the service on the Nexus end. See https://issues.apache.org/jira/browse/INFRA-23348 Maybe that will fix the problem. I'm sorry for sowing confusion about the Java version. I am using the GA release of Java 11. Here is the full output of java -version: openjdk version "11" 2018-09-25 OpenJDK Runtime Environment 18.9 (build 11+28) OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode) I haven't set up any proxies on my end. Thanks, -Rick On 6/14/22 12:59 AM, Tamás Cservenák wrote: Howdy, So is the "peer not authenticated" error still sporadically happening? Qs: - can you use some LTS java instead of 18? (17 or 11?) - could you execute the build with -e (or -X but this will give you a LOT of logs) and paste the stack trace? - you sure you are directly accessing repo.a.o, no proxy or whatever in between your maven process and repo.a.o? HTH T On Tue, Jun 14, 2022 at 12:10 AM Rick Hillegas wrote: Thanks, Tamas. On your advice, I updated the top level pom to refer to version 26 of the parent apache pom. This caused the maven-antrun-plugin to object that a major upgrade had obsoleted the element. I was advised to change to . I did that too. However, I am still seeing "peer not authenticated" messages. On 6/13/22 11:15 AM, Tamás Cservenák wrote: Howdy, Well, sadly I see that svn tag is in place, but the very first observation I have is that due to ancient parent Apache POM version 10, you use ancient plugins despite the latest Maven being used. Please try to upgrade parent to current one (current version is 26). So in here https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/pom.xml make project/parent/version = 26 Parent version 10 you use is from 2011 hence you use plugins that are 11 years old or older, made for Maven2, and I really have no idea what kind of bug(s) may be hit here... Note: ASF parent 10 says java level is 1.4... so this may need some alignment as well... Also, why Java 18? Is it needed or is it just handy? (I'd go with some LTS rather) Other than that, given the sporadic nature of the error, I really can't say more, maybe some misbehaving proxy in between maven process and repo.apache.org? HTH Tamas On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas wrote: I need advice about how to move past a "peer not authenticated" error. I am trying to stage some 20 jars and corresponding poms via the following command: mvn -Dgpg.passphrase="my secret passphrase" clean deploy I am able to upload most of the artifacts, but the command eventually fails with a "peer not authenticated" error. The artifact which incurs this error is not consistent. I have tried this from two different locations (Palm Springs and San Francisco). But I can't get to the end of the upload without a "peer not authenticated" error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): transfer failed for https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc : peer not authenticated -> [Help 1] Here is my environment: maven 3.8.5 OpenJDK Runtime Environment 18.9 (build 11+28) Based on some advice I found on the internet, I tried adding the following stanza to my top level pom: ... org.apache.maven.plugins maven-deploy-plugin 3 That does not fix the problem. Any help you can give me would be appreciated. Thanks, Rick - 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: peer not authenticated error
Thanks, Tamas. On your advice, I updated the top level pom to refer to version 26 of the parent apache pom. This caused the maven-antrun-plugin to object that a major upgrade had obsoleted the element. I was advised to change to . I did that too. However, I am still seeing "peer not authenticated" messages. On 6/13/22 11:15 AM, Tamás Cservenák wrote: Howdy, Well, sadly I see that svn tag is in place, but the very first observation I have is that due to ancient parent Apache POM version 10, you use ancient plugins despite the latest Maven being used. Please try to upgrade parent to current one (current version is 26). So in here https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/pom.xml make project/parent/version = 26 Parent version 10 you use is from 2011 hence you use plugins that are 11 years old or older, made for Maven2, and I really have no idea what kind of bug(s) may be hit here... Note: ASF parent 10 says java level is 1.4... so this may need some alignment as well... Also, why Java 18? Is it needed or is it just handy? (I'd go with some LTS rather) Other than that, given the sporadic nature of the error, I really can't say more, maybe some misbehaving proxy in between maven process and repo.apache.org? HTH Tamas On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas wrote: I need advice about how to move past a "peer not authenticated" error. I am trying to stage some 20 jars and corresponding poms via the following command: mvn -Dgpg.passphrase="my secret passphrase" clean deploy I am able to upload most of the artifacts, but the command eventually fails with a "peer not authenticated" error. The artifact which incurs this error is not consistent. I have tried this from two different locations (Palm Springs and San Francisco). But I can't get to the end of the upload without a "peer not authenticated" error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): transfer failed for https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc: peer not authenticated -> [Help 1] Here is my environment: maven 3.8.5 OpenJDK Runtime Environment 18.9 (build 11+28) Based on some advice I found on the internet, I tried adding the following stanza to my top level pom: ... org.apache.maven.plugins maven-deploy-plugin 3 That does not fix the problem. Any help you can give me would be appreciated. Thanks, Rick - 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
peer not authenticated error
I need advice about how to move past a "peer not authenticated" error. I am trying to stage some 20 jars and corresponding poms via the following command: mvn -Dgpg.passphrase="my secret passphrase" clean deploy I am able to upload most of the artifacts, but the command eventually fails with a "peer not authenticated" error. The artifact which incurs this error is not consistent. I have tried this from two different locations (Palm Springs and San Francisco). But I can't get to the end of the upload without a "peer not authenticated" error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): transfer failed for https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc: peer not authenticated -> [Help 1] Here is my environment: maven 3.8.5 OpenJDK Runtime Environment 18.9 (build 11+28) Based on some advice I found on the internet, I tried adding the following stanza to my top level pom: ... org.apache.maven.plugins maven-deploy-plugin 3 That does not fix the problem. Any help you can give me would be appreciated. Thanks, Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: problem using maven to gpg-sign artifacts
Thanks, Karl. Upgrading to the latest version of Maven and the gpg plugin did the trick. I am still getting peer authentication errors on some uploads, but I suspect that is a server problem and not a maven issue. Much appreciated. On 6/10/22 10:30 AM, Karl Heinz Marbaise wrote: On 10.06.22 19:26, Karl Heinz Marbaise wrote: Hi Rick, On 10.06.22 17:55, Rick Hillegas wrote: I am having trouble signing maven artifacts. The details of the problem are described at https://issues.apache.org/jira/browse/INFRA-23348. The maven error message is terse. No additional useful information comes back when I run the maven command with -e and -X switches. I haven't found any useful information on the web. My environment is as follows: Mac OSX 11.2.3 Apache Maven 3.5.0 gpg (GnuPG) 2.3.6 (libgcrypt 1.10.1) openjdk version "11" 2018-09-25 This is the command which fails... mvn -Dgpg.passphrase="blah blah blah my passphrase" clean deploy ...and this is the error message I see: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.3:sign (sign-artifacts) on project derby-project: Exit code: 2 -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.3:sign (sign-artifacts) on project derby-project: Exit code: 2 I would appreciate any advice you can give me about how to debug this problem. Ah furthermore what I missed I strongly recommend to upgrade the Maven version as well Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
problem using maven to gpg-sign artifacts
I am having trouble signing maven artifacts. The details of the problem are described at https://issues.apache.org/jira/browse/INFRA-23348. The maven error message is terse. No additional useful information comes back when I run the maven command with -e and -X switches. I haven't found any useful information on the web. My environment is as follows: Mac OSX 11.2.3 Apache Maven 3.5.0 gpg (GnuPG) 2.3.6 (libgcrypt 1.10.1) openjdk version "11" 2018-09-25 This is the command which fails... mvn -Dgpg.passphrase="blah blah blah my passphrase" clean deploy ...and this is the error message I see: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.3:sign (sign-artifacts) on project derby-project: Exit code: 2 -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.3:sign (sign-artifacts) on project derby-project: Exit code: 2 I would appreciate any advice you can give me about how to debug this problem. Thanks, -Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Clarification on an end-version/end-date for maven plugins' support of JDK 1.7
Thanks for the help and input Tamas and Ben! Yes, I wasn't demanding or expecting anything, just was curious if there was some broader "plan", but it sounds like it's up to the individual maintainers, which is fine. We too were hoping that our operations folks would get all the web application servers upgraded to Java 8 last year, which apparently didn't "quite" happen - thus I'm still supporting a few servers running [very ancient] versions of Java 1.7. I'll probably have a fun meeting with my bosses soon and perhaps I too can just say that no longer will any of the libraries I build be Java 1.7 compatible, so if one of those clients needs it, they can get their server upgraded or "too bad" - man that'd be great! Cheers, Rick E-mail: hant...@gmail.com Twitter: rack88 <http://www.twitter.com/rack88> On Tue, Jun 8, 2021 at 12:31 PM Benjamin Marwell wrote: > Just FYI, > > IBM, Zulu, Oracle and Microsoft are giving extended support to paying > customers until the 2030s. I guess maven plugins will stay on 1.8 for quite > a while, but that's just a guess. > At least most libraries haven't moved to Java 11 yet (and afaik won't move > to Java 11 in the near future). > > There is no extended support available for Java 7 from most vendors (maybe > Zulu?), and due to updates to the TLS stack, Java 1.7 has become quite > unusable. I doubt that there is a good reason to support Java 1.7 now. > Updating to Java 8 shouldn't be a big issue and will get you quite some > performance gains. > > HTH > Ben > > > > > On Tue, 8 Jun 2021, 08:28 Tamás Cservenák, wrote: > > > Howdy, > > > > Let me state several things in advance first: > > - ASF Maven project (the project) is an open source project maintained by > > volunteers in their spare time. > > - We (as a project) do not provide any kind of "support" or any of that > > stuff. > > > > That said, Java 7 is EOLd in 2015, while Java 8 is EOLd in 2019, and yes, > > we try to move to supported (read: freely available) Java versions. > > > > Hence, if you are stuck on Java 7, your best option is really to "lock > > down" your plugin versions as well, and accept the fact that you are > stuck > > on your tooling as well. > > > > We, as a Java project, have upstream dependencies, and time is pressing > us > > also, as more and more projects move to Java 8 (if not to Java 11), that > in > > the same way prevents us from consuming the latest dependencies, hence, > the > > whole "flock" (ecosystem) has to follow the moving target. > > > > So, while there is no "general guideline" (aside that Maven CLI 3.x is > Java > > 7, Maven 4.x CLI will be Java 8, etc), due to large ecosystem (plugins in > > ASF and outside) and plugin version numbers being "unbounded" (are per > > plugins, not really bounded to Maven CLI), we try our best when we switch > > plugin from Java 7 to something higher; it usually means minor or major > > version update (so will not happen in a "patch release"), and pretty much > > always will be present in release notes, just like it is in case of > > maven-javadoc-plugin: > > https://maven.apache.org/plugins/maven-javadoc-plugin/jira-report.html > > > > So, it is up to you to search thru release notes, and figure out which > > plugin requires which version of Java. > > > > HTH > > Tamas > > > > > > On Tue, Jun 8, 2021 at 6:43 AM Rick Hanton wrote: > > > > > Hi folks, > > > > > > Just wondering if someone can point me to any documentation about one > of > > > the following things: > > > > > > 1) Is there a high level direction among apache projects and > particularly > > > apache maven plugin projects to no longer build using the version 1.7 > > JDK? > > > I'm seeing similar changes to move away from Java 7 as I poke through > > some > > > projects like Surefire and maven-javadoc-plugin's latest > builds/releases. > > > This is creating some chaos for my company, where we typically use the > > > maven-release plugin via the command-line, but rarely specify versions > of > > > the plugins it is dependent upon in our pom.xml files (allowing maven > to > > do > > > its normal process of using the latest+greatest release version(s)). I > > > presume other developers that still have code building with JDK 1.7 > will > > be > > > in the same boat where their builds start failing with errors like the > > one > > >
Clarification on an end-version/end-date for maven plugins' support of JDK 1.7
pain for us since these releases with JDK 1.8 class files started appearing in May. Thanks, Rick <https://about.me/rickhanton?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb> Rick Hanton about.me/rickhanton <https://about.me/rickhanton?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb> E-mail: hant...@gmail.com Twitter: rack88 <http://www.twitter.com/rack88> Cell: 651-747-5864
Re: Please officially support RELEASE and LATEST
Curtis, For what it's worth, I completely agree. This is a broken part of Maven that we've learned to work around because of a theoretical benefit. I can agree with needing to specify a version or version range for other dependencies, but for my code in non-Prod environments -- I want LATEST. Always. I looked into this about three(?) years ago and it looked a bit like a religious battle, so I just declared defeat. I think there was a ticket created that was closed "Won't Fix". We have Nexus rebuild it's metadata for the affected repositories and this adjusts the LATEST tag. I started coding an optional parameter for Maven to be used locally and I think the code's 90% there, but I had a series of problems using Maven to build Maven and had to do other work and never got back to it. On 04/24/2017 11:58 AM, Curtis Rueden wrote: I would like to argue for the inclusion / restoration / continued support of the RELEASE and LATEST tags. Really? No one else cares enough to respond? I am very often running into use cases where the easiest solution seems to be LATEST and/or RELEASE. I have to manage a large Bill of Materials POM and I need to know things like "which components have new releases available" and "which components have SNAPSHOT builds since the last release." How do other people answer these questions without custom tooling, and without using LATEST or RELEASE tags? Regards, Curtis -- Curtis Rueden LOCI software architect - https://loci.wisc.edu/software ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden On Thu, Apr 13, 2017 at 10:51 AM, Curtis Rueden wrote: Hi Maven developers, I would like to argue for the inclusion / restoration / continued support of the RELEASE and LATEST tags. Reasons: 1) There are many valid use cases for them. For example, my script jrun [1] uses RELEASE right now to make it easier to launch a Maven GAV. Launching e.g. the Jython REPL is as easy as "jrun org.python:jython-standalone" from the CLI. But this relies on RELEASE working. I know that Maven is traditionally viewed as primarily a build-time tool, but it is also extremely useful for synthesizing runtime environments, and IMHO underutilized in this regard. 2) For LATEST, you can achieve basically the same behavior using a version range like [0,). There is no other way (that I know of) to achieve what the RELEASE tag does. 3) The argument that they harm reproducibility is totally valid. But so do SNAPSHOTs, and so do version ranges. And those have not been deprecated. So why are RELEASE and LATEST eschewed so heavily? Orthogonally: I think it would be awesome to warn about irreproducible builds, be they from SNAPSHOTs, version ranges, or these special keywords. People need to know when their builds are vulnerable. But there should probably also be a property to disable this warning, for the cases when the developer intentionally wants/needs to use them, and knows what they are doing. If the issue is just that no ones has time to work on e.g. MNG-6206, I could try to make some time for it—I feel strongly enough about this issue. Thanks for any insight, workarounds, counterarguments, agreement. (Especially if you agree: please speak up, so the core Maven devs know I'm not just an outlier here!) Regards, Curtis [1] https://github.com/ctrueden/jrun -- Curtis Rueden LOCI software architect - https://loci.wisc.edu/software ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden -- Rick Huff, Principal Software Engineer Identity and Access Management Team ITS Applications, The University of Texas at Austin
Re: Can not understand why maven is ALWAYS choosing a 3rd repo BEFORE my nexus one?
It actually pulls the correct artifacts from the 3rd party repos just fine (the one you see called ZK in my settings.) There are a bunch of them in there and the upgrade them quite frequently so I'd prefer to not have to manually add them, especially since their repos work just fine. The annoying part is that I see it trying to access some of our internal ones from there. That's the confusing part. It eventually does pull from the correct nexus repo for our internal dependencies but why do I see it try to access that 3rd party repo first? Is there no way to enforce an order that it will check repositories? (When I google for this issue it's confusing... some mention that the settings.xml reverses the order, but I've tried using different orders in there.) On Fri, May 8, 2015 at 4:02 PM, Ron Wheeler wrote: > Is it possible that Maven is having the same trouble as Nexus and can not > get into the repo and just moves on to the next one since it has no idea > about which dependency is going to be found in the repo and maybe the next > one will work better and get it everything that it needs. > > It would not make sense to wait forever on a repo that will not talk to > Maven. > > Can you download the artifact manually and add it to your repo and move on. > > Ron > > > > On 08/05/2015 3:40 PM, Rick R wrote: > >> I mention that at the end of the above email... for some reason I'm having >> trouble proxing this one ZK repository that requires a username and >> password (which I've added in the nexus auth settings.) I think the error >> Nexus mentioned was "remote access not allowed" or something to that >> effect. >> >> On Fri, May 8, 2015 at 3:03 PM, Ron Wheeler < >> rwhee...@artifact-software.com> >> wrote: >> >> Why not have your repo proxy the extra ones so everyone's settings.xml >>> points to your repo and its is up to the repo manager to set up the >>> permitted repo. >>> >>> Ron >>> >>> >>> On 08/05/2015 2:39 PM, Rick R wrote: >>> >>> I'm trying to figure out why Maven is choosing a 3rd party repo defined >>>> in >>>> my settings xml BEFORE trying to search in our internal Nexus repo. >>>> >>>> My settings xml has the following profile which is set as the active >>>> one. >>>> >>>> >>>> >>>> ncs-main >>>> >>>> >>>> >>>> ZK EE >>>> https://maven.zkoss.org/repo/zk/ee >>>> >>>> >>>> >>>> zk repository >>>> http://mavensync.zkoss.org/maven2 >>>> >>>> >>>> >>>> nexus.repo.all >>>> >>>> http://dayrhencvp011.enterprisenet.org:8080/nexus/content/groups/public/ >>>> >>>> >>>> true >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> My project's pom does not have any repositories specified. I tried >>>> messing >>>> with the order of the repositories above (flipping them around different >>>> ways) but it always seems to go after one of the ZK ones first: >>>> >>>> >>>> Downloading: >>>> >>>> >>>> http://dayrhencvp011.enterprisenet.org:8080/nexus/content/groups/public/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml >>>> >>>> Downloading: >>>> >>>> >>>> http://mavensync.zkoss.org/maven2/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml >>>> >>>> Downloading: >>>> >>>> >>>> https://maven.zkoss.org/repo/zk/ee/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml >>>> >>>> Downloaded: >>>> >>>> >>>> http://dayrhencvp011.enterprisenet.org:8080/nexus/content/groups/public/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml >>>> (769 B at 2.5 KB/sec) >>>> >>>> [WARNING] Could not transfer metadata >>>> com.ncs:ncs-data-domain:1.12-SNAPSHOT/maven-metadata.xml from/to ZK EE ( >>>> https://maven.zkoss.org/repo/zk/ee): Connection to >>>> https://maven.zkoss.org >>>> refused >>>> >>>> [WARNING] Failure to transfer >>>> com.ncs:ncs-data-domain
Re: Can not understand why maven is ALWAYS choosing a 3rd repo BEFORE my nexus one?
I mention that at the end of the above email... for some reason I'm having trouble proxing this one ZK repository that requires a username and password (which I've added in the nexus auth settings.) I think the error Nexus mentioned was "remote access not allowed" or something to that effect. On Fri, May 8, 2015 at 3:03 PM, Ron Wheeler wrote: > Why not have your repo proxy the extra ones so everyone's settings.xml > points to your repo and its is up to the repo manager to set up the > permitted repo. > > Ron > > > On 08/05/2015 2:39 PM, Rick R wrote: > >> I'm trying to figure out why Maven is choosing a 3rd party repo defined in >> my settings xml BEFORE trying to search in our internal Nexus repo. >> >> My settings xml has the following profile which is set as the active one. >> >> >> >>ncs-main >> >> >> >> ZK EE >> https://maven.zkoss.org/repo/zk/ee >> >> >> >> zk repository >> http://mavensync.zkoss.org/maven2 >> >> >> >> nexus.repo.all >> >> http://dayrhencvp011.enterprisenet.org:8080/nexus/content/groups/public/ >> >> >>true >> >> >> >> >> >> >> >> My project's pom does not have any repositories specified. I tried messing >> with the order of the repositories above (flipping them around different >> ways) but it always seems to go after one of the ZK ones first: >> >> >> Downloading: >> >> http://dayrhencvp011.enterprisenet.org:8080/nexus/content/groups/public/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml >> >> Downloading: >> >> http://mavensync.zkoss.org/maven2/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml >> >> Downloading: >> >> https://maven.zkoss.org/repo/zk/ee/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml >> >> Downloaded: >> >> http://dayrhencvp011.enterprisenet.org:8080/nexus/content/groups/public/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml >> (769 B at 2.5 KB/sec) >> >> [WARNING] Could not transfer metadata >> com.ncs:ncs-data-domain:1.12-SNAPSHOT/maven-metadata.xml from/to ZK EE ( >> https://maven.zkoss.org/repo/zk/ee): Connection to >> https://maven.zkoss.org >> refused >> >> [WARNING] Failure to transfer >> com.ncs:ncs-data-domain:1.12-SNAPSHOT/maven-metadata.xml from >> https://maven.zkoss.org/repo/zk/ee was cached in the local repository, >> resolution will not be reattempted until the update interval of ZK EE has >> elapsed or updates are forced. Original error: Could not transfer metadata >> com.ncs:ncs-data-domain:1.12-SNAPSHOT/maven-metadata.xml from/to ZK EE ( >> https://maven.zkoss.org/repo/zk/ee): Connection to >> https://maven.zkoss.org >> refused >> >> Of course it found ncs-data-domain in the 3rd attempt above (form nexus) >> but why does it always try the maven ones first? >> >> Even when I switch the order around it's trying zk-ee FIRST. >> >> Very frustrating and can't find any documentation on it. >> >> >> (Note, if you're wondering why I didn't put this 3rd party repo in Nexus, >> I >> tried but it was complaining about unable to work with it.. forgot the >> exact error.. it has to be authenticated with a username and password and >> I >> tried adding that to nexus as well, but was having trouble so I left the >> definition in my settings.xml) >> >> > > -- > Ron Wheeler > President > Artifact Software Inc > email: rwhee...@artifact-software.com > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Rick R
Can not understand why maven is ALWAYS choosing a 3rd repo BEFORE my nexus one?
I'm trying to figure out why Maven is choosing a 3rd party repo defined in my settings xml BEFORE trying to search in our internal Nexus repo. My settings xml has the following profile which is set as the active one. ncs-main ZK EE https://maven.zkoss.org/repo/zk/ee zk repository http://mavensync.zkoss.org/maven2 nexus.repo.all http://dayrhencvp011.enterprisenet.org:8080/nexus/content/groups/public/ true My project's pom does not have any repositories specified. I tried messing with the order of the repositories above (flipping them around different ways) but it always seems to go after one of the ZK ones first: Downloading: http://dayrhencvp011.enterprisenet.org:8080/nexus/content/groups/public/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml Downloading: http://mavensync.zkoss.org/maven2/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml Downloading: https://maven.zkoss.org/repo/zk/ee/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml Downloaded: http://dayrhencvp011.enterprisenet.org:8080/nexus/content/groups/public/com/ncs/ncs-data-domain/1.12-SNAPSHOT/maven-metadata.xml (769 B at 2.5 KB/sec) [WARNING] Could not transfer metadata com.ncs:ncs-data-domain:1.12-SNAPSHOT/maven-metadata.xml from/to ZK EE ( https://maven.zkoss.org/repo/zk/ee): Connection to https://maven.zkoss.org refused [WARNING] Failure to transfer com.ncs:ncs-data-domain:1.12-SNAPSHOT/maven-metadata.xml from https://maven.zkoss.org/repo/zk/ee was cached in the local repository, resolution will not be reattempted until the update interval of ZK EE has elapsed or updates are forced. Original error: Could not transfer metadata com.ncs:ncs-data-domain:1.12-SNAPSHOT/maven-metadata.xml from/to ZK EE ( https://maven.zkoss.org/repo/zk/ee): Connection to https://maven.zkoss.org refused Of course it found ncs-data-domain in the 3rd attempt above (form nexus) but why does it always try the maven ones first? Even when I switch the order around it's trying zk-ee FIRST. Very frustrating and can't find any documentation on it. (Note, if you're wondering why I didn't put this 3rd party repo in Nexus, I tried but it was complaining about unable to work with it.. forgot the exact error.. it has to be authenticated with a username and password and I tried adding that to nexus as well, but was having trouble so I left the definition in my settings.xml) -- Rick R
Re: Anyone know how to use the ant task scopes?
On Dec 17, 2012, at 4:18 , Stephen Connolly wrote: > that is maven Ant tasks. > > > The scope element is used when you have specified "scopes" attr in > *however* it is really only of use when you have a > pomRefId as there is no other way to reference a different set of scopes. > > So the way you would do this is create a with all the > dependencies, e.g. > https://github.com/apache/cassandra/blob/trunk/build.xml#L319 and then use > the scopes element to select the scopes you want. I have not done that > here: https://github.com/apache/cassandra/blob/trunk/build.xml#L517 but > that is for political reasons, where c* didn't want test scoped > dependencies in their non-test "pom"s Thanks, Stephen. I'll see if I can figure it out, but thanks for pointing me at the :pom element. And thanks for pointing me at Cassandra. A friend at a very large company just told me they're using Cassandra, but thought was commercial. Now I see it isn't :-) -- Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Anyone know how to use the ant task scopes?
On Dec 17, 2012, at 3:59 , Martin Gainty wrote:
> Rick depends on where you place declaration in your build.xml global
> declaration with http://ant.apache.org/manual/Tasks/property.html
> target-local override with
> http://ant.apache.org/manual/Tasks/local.html
> is this what you're looking for?
Sorry, I didn't repeat my original issue here. I'm hoping to have one
entry with each dependency having appropriate scope
("compile", "provided", "test"), and then refer to the class path and file list
generated by that from each of my various targets
(compile, build, test). So, I want to adjust the "useScope" attribute
accordingly, but since it's part of the element, I
don't see a way to do that.
Are you saying I should put a ${} property in there that can be adjusted inside
each target, and that will, in turn, adjust the generated class path and file
list?
--
Rick
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Anyone know how to use the ant task scopes?
On Dec 16, 2012, at 18:06 , Benson Margulies wrote: > You'll have to be a lot more specific. With the antrun plugin? With > something else? I've posted a couple times with my specific query, but no replies to it. I set it up a long time ago, so I didn't know there was more than one way to use the maven plugin in ant. In my ~/.ant/lib I have maven-ant-tasks-2.1.3.jar. Here's what I have in my build.xml: ... http://mirrors.ibiblio.org/maven2"/> ... ... etc. I don't know if that's antrun or something else. -- Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Anyone know how to use the ant task scopes?
Anyone at all? -- Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Help with ant task?
On Dec 10, 2012, at 12:03 , Martin Gainty wrote: > Short Answer: HERE (and ant-users) is latest version of ANT installed..IMHO > skip ivy..all of your namespace mapping can be accomplished in Maven > http://ant.apache.org/bindownload.cgi > get maven-antrun-plugin from here (IMHO install it to local repo) > http://mvnrepository.com/artifact/org.apache.maven.plugins/maven-antrun-plugin > take a gander at these examples for executing ANT Tasks with > maven-antrun-plugin here > http://docs.codehaus.org/display/MAVENUSER/Antrun+Plugin > pingback if you need anything Thanks, Martin. I posted a question a few days ago but got no response. My trouble is not so much with running the maven ant task, that works fine (I use it to fetch dependencies and build class paths). What I'd like to do is make use of the "useScope" attribute, which doesn't seem useful to me, at least the way I understand its use. Ideally, I'd be able to specify each dependency with its required scope, then outside of that tag, refer to it with different useScope values. But as it is, it seems useless, because it can only be specified once per dependencies tag. Can someone elaborate on how it's supposed to be used? Thanks! -- Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Help with ant task?
Hi. Where does one go for help with the ant task? -- Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
useScope in ant build script
Despite reading and re-reading the docs, and googling, for the past half-hour, I can't see how useScope or scopes is useful in the maven ant task unless I use a separate POM file. If I list all my dependencies directly in my ant build script, there appears to be no way to reference one dependency set with multiple different scopes. For example, I have: ... I have a compile target in ant that uses this as the classpath. But I'd like my test target to also use it as a classpath. The problem is that in the test target, I need some of my "provided"-scope dependencies to be included, so I want to use it as a useScope="test" set of dependencies. But because this can only be specified with the dependencies artifact once, there's no way to use it. That seems to make the feature rather useless. Am I just completely missing the usage? How can I avoid completely copying the entire dependency set? Thanks, -- Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Overriding distributionManagement Repositories
Oh! Great, looks like that was added quite a while ago, I've never seen it. Thanks Nick On 6/23/11 11:05 AM, "Nick Stolwijk" wrote: > You could create a profile in your settings.xml which is always active > and sets the property altDeploymentRepository[2] to your new value. > > [1] http://maven.apache.org/settings.html#Active_Profiles > [2] > http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#altDeploy > mentRepository > > Hth, > > Nick Stolwijk > ~Senior Java Developer~ > > iPROFS > Wagenweg 208 > 2012 NM Haarlem > T +31 23 547 6369 > F +31 23 547 6370 > I www.iprofs.nl > > > > On Thu, Jun 23, 2011 at 3:44 PM, Rick Mangi wrote: >> Hello Maven Users, >> >> I'm trying to migrate my users to a new nexus repository on a different >> domain. I'm trying to avoid having to tell all of the developers to change >> their distributionManagement/repository and /snapshotRepository values in >> their pom files or to upgrade to new parent poms all at once. They can do it >> over time, but we support hundreds of developers on many projects. >> >> I can't seem to find a way to override these values in settings.xml. I can >> easily change where the users fetch artifacts from, but not where they >> deploy or release to. (btw - most of my users are still using maven 2). >> >> Thanks for any advice you may have. >> >> Rick >> >> >> >> >> - >> 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
Overriding distributionManagement Repositories
Hello Maven Users, I'm trying to migrate my users to a new nexus repository on a different domain. I'm trying to avoid having to tell all of the developers to change their distributionManagement/repository and /snapshotRepository values in their pom files or to upgrade to new parent poms all at once. They can do it over time, but we support hundreds of developers on many projects. I can't seem to find a way to override these values in settings.xml. I can easily change where the users fetch artifacts from, but not where they deploy or release to. (btw - most of my users are still using maven 2). Thanks for any advice you may have. Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How access classes from war dependency?
On May 5, 2011, at 2:44 PM, sipungora wrote:
> I've done this, as you've explained me here. But I have one problem yet. If
> I save data in jar object from 1-st war for the 2-nd war, the 2-nd war
> cannot acces they. My object is the singleton.
>
> 1 protected static Controller controller;
> 2
> 3 public static Controller getInstance() {
> 4 if(controller == null) {
> 5 controller = new Controller();
> 6 }
> 7 return controller;
> 8 }
>
> If I debug 1-st war and then 2-nd one, I see that 2-nd war also goes into
> row 5. So both wars works with different objects.
> Can you explain me how can I solve this?
I don't think you can do this. I think each war is in its own class loader;
effectively each web application is in its own space. There may be ways to
configure your app server to share information between wars, but frankly the
whole concept smells of bad design.
--
Rick Genter
rgen...@interactions.net
***
This e-mail and any of its attachments may contain Interactions Corporation
proprietary information, which is privileged, confidential, or subject to
copyright belonging to the Interactions Corporation. This e-mail is intended
solely for the use of the individual or entity to which it is addressed. If you
are not the intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this e-mail is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify the sender
immediately and permanently delete the original and any copy of this e-mail and
any printout. Thank You.
***
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Dynamically generating class names with archetype
On Apr 19, 2011, at 3:05 PM, Ryan Connolly wrote: > Hi have you defined these properties in an archetype descriptor? > > http://maven.apache.org/guides/mini/guide-creating-archetypes.html According to the documentation at: http://maven.apache.org/archetype/archetype-common/archetype.html the only elements supported by are , , , , , and . Where would I put the definitions of those properties? -- Rick Genter rgen...@interactions.net *** This e-mail and any of its attachments may contain Interactions Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Interactions Corporation. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. *** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Dynamically generating class names with archetype
I'm building an archetype for generating Maven projects for our custom
application framework. Everything is working but the generated project always
has the same class names and annotations. I would like to be able to
dynamically specify those names/annotations.
For example, I can specify my Java file
(src/main/resources/archetype-resources/src/main/java/ClientApp.java) like this:
package ${packageName};
// imports go here...
@OurAnnotation(client="Client", application="ClientApp",
version="1.0.0-SNAPSHOT")
public class ClientApp extends OurBaseClass {
...
}
but what I'd like to do is something like this:
package ${packageName};
// imports go here...
@OurAnnotation(client="${client}", application="${clientApp}",
version="${clientAppVersion}")
public class ${clientApp} extends OurBaseClass {
...
}
I tried the above and using:
mvn archetype:generate -DarchetypeGroupId=... -DarchetypeArtifactId=...
-DarchetypeVersion=... -Dclient=Acme -DclientApp=HelloWorld6
-DclientAppVersion=1.0.0-SNAPSHOT -DgroupId=net.interactions.example
-Dversion=0.0.1-SNAPSHOT -DartifactId=hello-world-6
my generated ClientApp.java file had the correct package name
(net.interactions.example), but none of the other substitutions were performed.
Also, I'd need the generated file itself to have the correct name
(${clientApp}.java). I'd have preferred that the generated file be named
"HelloWorld6.java" and have the content:
package net.interactions.example;
// imports go here...
@OurAnnotation(client="Acme", application="HelloWorld6",
version="0.0.1-SNAPSHOT")
public class HelloWorld6 extends OurBaseClass {
...
}
Is what I want to do possible?
--
Rick Genter
rgen...@interactions.net
***
This e-mail and any of its attachments may contain Interactions Corporation
proprietary information, which is privileged, confidential, or subject to
copyright belonging to the Interactions Corporation. This e-mail is intended
solely for the use of the individual or entity to which it is addressed. If you
are not the intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this e-mail is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify the sender
immediately and permanently delete the original and any copy of this e-mail and
any printout. Thank You.
***
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Test phase for a command line tool (resend)
Note: I sent this on Friday (2011-03-18) but saw no response, so am resending on the chance that it somehow got lost in transit. Caveat: I am new to Maven. I've read the online documentation but haven't found a good source of sample POMs other than for very basic configurations. I have a POM that builds a command-line tool. I figured out how to use the assembly plugin to build a self-contained jar, but now I need to be able to run a series of test cases using that jar and a custom shell script to invoke it. I have several questions: 1) Where do I put my custom shell script in the hierarchy? I've put the source into src/main/bin for now. 2) For testing I'd like to copy the shell script and self-contained jar (jar-with-dependencies) to a test directory (similar to test-classes) and run the jar from there. How do I do that? 3) The command-line tool analyzes compiled Java code from a jar and builds an XML file from the analysis. What I'd like to do for my test cases is compile a bunch of different tests into different jars, then for each jar run the tool over it, generating an XML file, and do a diff on the XML file against expected output. How do I do that? 3a) Alternatively I could write a test application that used Runtime.exec() to run the tool for each test case, then read in the resulting XML files using an XML parser and made a bunch of assertions about each file, but frankly I'd rather avoid writing the extra code. If I need to, however, how would I do that? I don't necessarily need the actual POMs written for me; pointers to more complete samples doing similar tasks would be fine. Thanks in advance. -- Rick Genter rgen...@interactions.net *** This e-mail and any of its attachments may contain Interactions Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Interactions Corporation. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. *** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Test phase for a command line tool
Caveat: I am new to Maven. I've read the online documentation but haven't found a good source of sample POMs other than for very basic configurations. I have a POM that builds a command-line tool. I figured out how to use the assembly plugin to build a self-contained jar, but now I need to be able to run a series of test cases using that jar and a custom shell script to invoke it. I have several questions: 1) Where do I put my custom shell script in the hierarchy? I've put the source into src/main/bin for now. 2) For testing I'd like to copy the shell script and self-contained jar (jar-with-dependencies) to a test directory (similar to test-classes) and run the jar from there. How do I do that? 3) The command-line tool analyzes compiled Java code from a jar and builds an XML file from the analysis. What I'd like to do for my test cases is compile a bunch of different tests into different jars, then for each jar run the tool over it, generating an XML file, and do a diff on the XML file against expected output. How do I do that? 3a) Alternatively I could write a test application that used Runtime.exec() to run the tool for each test case, then read in the resulting XML files using an XML parser and made a bunch of assertions about each file, but frankly I'd rather avoid writing the extra code. If I need to, however, how would I do that? I don't necessarily need the actual POMs written for me; pointers to more complete samples doing similar tasks would be fine. Thanks in advance. -- Rick Genter rgen...@interactions.net *** This e-mail and any of its attachments may contain Interactions Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Interactions Corporation. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. *** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Fortify and Maven
You can get it from the fortify website. You may need to talk to a support tech for the exact location. -Original Message- From: ginni [mailto:gi...@aero.org] Sent: Thursday, November 11, 2010 2:40 PM To: users@maven.apache.org Subject: RE: Fortify and Maven I would love to. Where can I find it? -- View this message in context: http://maven.40175.n5.nabble.com/Fortify-and-Maven-tp118623p3261165.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 - The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Fortify and Maven
Ginni, Can you use the maven-sca-plugin-2.6 with your version of the server ? If so the plugin is documented pretty well and you can use maven instead of ant. -Original Message- From: ginni [mailto:gi...@aero.org] Sent: Thursday, November 11, 2010 12:45 PM To: users@maven.apache.org Subject: Re: Fortify and Maven Hi All, I am new to Maven and new to Fortify. We have Fortify v5.2 (pre-360) and I need to generate whatever Fortify needs to run the build (ant build) for this multi-module project. Any guidance on how I can do that? Thanks!! Ginni -- View this message in context: http://maven.40175.n5.nabble.com/Fortify-and-Maven-tp118623p3260957.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 - The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven is a swamp
I think that's the main point. Nobody thinks XML is wonderful to read or write, but it's easily read by any tools, languages and by humans. XML is a standard, like it or not. It's a glue. Glue is good. Glue lets the logic be language neutral and portable. On 10/15/10 6:40 PM, "Ron Wheeler" wrote: > > Who cares what language Maven uses? > There are IDEs with editors that eliminate the need to look at XML. > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven is a swamp
Flexible and elegant aren't necessarily the same thing... Any language that prides itself on its ability to be obfuscated can't be elegant ;-) That said, I do love it. As far as Maven goes, the elegance of maven is that it does 90% of what you need it to do with very little or no effort and the other 10% can be done without much hassle. On 10/13/10 10:48 AM, "Kathryn Huxtable" wrote: > It does. The rest of the language is rather ugly, though. -K > > On Oct 13, 2010, at 9:07 AM, Rick Mangi wrote: > >> I just enjoyed the bit about perl having elegant and concise data structures >> :-) >> >> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven is a swamp
I just enjoyed the bit about perl having elegant and concise data structures
:-)
On 10/13/10 9:57 AM, "chemit" wrote:
> Le Wed, 13 Oct 2010 08:58:27 -0400,
> Ron Wheeler a écrit :
>
>> Doing the wrong thing and not using an IDE with a POM editor is not
>> a good recipe for a smooth development cycle.
>> I will admit to occasionally editing XML but that is for extreme
>> cases while you are getting set up..
>>
> euh wrong person :)
>
> You should have respond to previous mail, ... I love maven and all the
> xml stuff (arch to su much in facts.) I was just responding to the guy
> Kenneth which seems to be pretty angry with Maven and xml ;)
>
>
>> If you don't like XML:
>> 1) Get your development workflow Mavenized
>> 2) Get a Maven Repo set up
>> 3) Restructure your projects to fit the way Maven works
>> 3) Use an IDE that supports Maven with a proper human oriented editor
>> - Eclipse STS is very good at this.
>>
>> Then you will have no need of XML editing and no need to screw around
>> with command line Maven or custom plug-ins or custom goals.
>> You will not spend a lot of time in this forum moaning about the
>> unfairness of life and the difficulty of using Maven.
>>
>> Once you start using Maven properly, it is a very high level tool for
>> building Java applications such as:
>> Java WebServices
>> Java Servlets
>> Java Portlets
>> Java Standalone applications
>>
>> If you are building something else, my comments may not be relevant.
>>
>>
>> Ron
>>
>>
>>
>> On 13/10/2010 2:47 AM, chemit wrote:
>>> Le Tue, 12 Oct 2010 19:35:46 -0500,
>>> Kenneth McDonald a écrit :
>>>
Yes, I realize this is flamebait, but after trying to puzzle out
the following maven plugin:
maven-antrun-plugin
1.6
deploy
deploy-gh-pages
run
>>> location=""/>
>>> dir="${gh-pages-dir}">
>>> dir="${gh-pages-dir}">
I simply can't resist. Whoever in their right mind decided software
developers to think that requiring other developers to write config
files in XML was a proper decision?
Python, Ruby, and (yes even Perl) have had had much more elegant
and concise ways of managing complex data structures for years
now. And there's a reason JSON has become so popular--primarily
because XML is not, and was never intended to be, a format for
developers to write specifications in.
>>> First of all using the ant plugin is against "Best pratices", so
>>> for me and from this point, why critisize something when you are
>>> doing it the wrong way ?
>>>
Let's take a look at the most obvious of the problems in the above:
>>> location=""/>
>>> dir="${gh-pages-dir}">
>>> dir="${gh-pages-dir}">
Now, I'm still very new to maven, but it strikes me that what the
above is saying is (in Pythonic code, but feel free to convert to
your own):
import git
gh-pages-dir = ""
git(dir=gh-pages-dir, "add .")
git(dir=gh-pages-dir, "commit")
git(dir=gh-pages-dir, "push origin gh-pages")
I'm sure there are errors in the translation--but I'm equally sure
that if these errors were corrected, they would not substantially
alter the ratio of XML to Pythonic code. Ruby and even Perl would
do just as well.
>>> but if it is so simple as you say, you should be able to write your
>>> simply code without any doubt...
>>>
So here's a challenge to the (very intelligent) folks at apache.
Open your minds to the fact that XML is not only the Final
Solution, but isn't even close to the best solution, and start
producing some products that are configurable without an entire
manual in front of oneself. I realize that arriving at an optimal
solution is not really possible, but XML is so suboptimal as to
beggar belief.
I am just so sick of using crappy "solutions" (read: XML) layered
over top of what could be good solutions.
>>> Yes crappy is
Re: Why all these errors with mvn site:site concerning https://maven-repository.dev.java.net/nonav/repository
On Tue, Jul 27, 2010 at 4:34 PM, Brian Fox wrote: > one of the reports in there hits all repos known to the build. There's > a bug against it. > Is there a known work around in the meantime? > > On Tue, Jul 27, 2010 at 2:29 PM, Rick R wrote: > > I keep getting all these errors about > > https://maven-repository.dev.java.net/nonav/repository. I tried googling > > about it but the responses are confusing. > > (I'm using maven 2.2.1 and 2.1.1 of the site plugin) > > > > tons more. > > [ERROR] Unable to determine if resource > > org.springframework:spring-context-support:jar:2.5.5:compile exists in > > https://maven-repository.dev.java.net/nonav/repository > > [ERROR] Unable to determine if resource > > org.springframework:spring-core:jar:2.5.5:compile exists in > > https://maven-repository.dev.java.net/nonav/repository > > [ERROR] Unable to determine if resource > > org.springframework:spring-jms:jar:2.5.5:compile exists in > > https://maven-repository.dev.java.net/nonav/repository > > [ERROR] Unable to determine if resource > > org.springframework:spring-tx:jar:2.5.5:compile exists in > > https://maven-repository.dev.java.net/nonav/repository > > [ERROR] Unable to determine if resource > > org.springframework:spring-web:jar:2.5.5:compile exists in > > https://maven-repository.dev.java.net/nonav/repository > > [ERROR] Unable to determine if resource oro:oro:jar:2.0.8:compile exists > in > > https://maven-repository.dev.java.net/nonav/repository > > [ERROR] Unable to determine if resource rhino:js:jar:1.7R1:compile exists > in > > https://maven-repository.dev.java.net/nonav/repository > > [ERROR] Unable to determine if resource > taglibs:standard:jar:1.1.2:compile > > exists in https://maven-repository.dev.java.net/nonav/repository > > [ERROR] Unable to determine if resource tomcat:jsp-api:jar:5.5.23:test > > exists in https://maven-repository.dev.java.net/nonav/repository > > [ERROR] Unable to determine if resource wsdl4j:wsdl4j:jar:1.6.2:compile > > exists in https://maven-repository.dev.java.net/nonav/repository > > [ERROR] Unable to determine if resource xom:xom:jar:1.0:compile exists in > > https://maven-repository.dev.java.net/nonav/repository > > [ERROR] Unable to determine if resource xpp3:xpp3_min:jar:1.1.4c:compile > > exists in https://maven-repository.dev.java.net/nonav/repository > > > > > > -- > > Rick R > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Rick R
Why all these errors with mvn site:site concerning https://maven-repository.dev.java.net/nonav/repository
I keep getting all these errors about https://maven-repository.dev.java.net/nonav/repository. I tried googling about it but the responses are confusing. (I'm using maven 2.2.1 and 2.1.1 of the site plugin) tons more. [ERROR] Unable to determine if resource org.springframework:spring-context-support:jar:2.5.5:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource org.springframework:spring-core:jar:2.5.5:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource org.springframework:spring-jms:jar:2.5.5:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource org.springframework:spring-tx:jar:2.5.5:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource org.springframework:spring-web:jar:2.5.5:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource oro:oro:jar:2.0.8:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource rhino:js:jar:1.7R1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource taglibs:standard:jar:1.1.2:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource tomcat:jsp-api:jar:5.5.23:test exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource wsdl4j:wsdl4j:jar:1.6.2:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource xom:xom:jar:1.0:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource xpp3:xpp3_min:jar:1.1.4c:compile exists in https://maven-repository.dev.java.net/nonav/repository -- Rick R
release plugin issue
I've configured the release plugin in my build. I'm using a flat directory structure like: Aggregator Common Ejb Web When I do a release:prepare from the aggregator directory everything seems to work however the aggregator/... is the only path labeled. Also, when I do a release:perform from the aggregator directory it fails looking for the sibling directories in the aggregator/target/sibling. Maven identifies aggregator/target/checkout as the working directory. Is this because of the directory structure I'm using ? Does the release-plugin only work with a hierarchical dir? Is there a way around this or do I need to change the dir structure I'm using ? Thanks - The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer.
RE: maven release plugin not updating sub-module dependencies
Aleksey,
Thank you for the advice. That looks like it will work much better than what I
was doing.
Rick
-Original Message-
From: Aleksey Didik [mailto:di...@magenta-technology.ru]
Sent: Thursday, July 08, 2010 9:13 AM
To: Maven Users List
Subject: Re: maven release plugin not updating sub-module dependencies
Rick, see comments below.
> I thought it would update the sibling modules based on the modules included
> in the parent pom. It updates the sibling dependencies when it changes the
> tagged version just not the next version.
Look like I've not clear understood release process with sibling
dependencies. If it updates when it changes the tagged version, but not
updates next version, it looks like an issue...
> So you're saying move the sibling dependencies to the dependencyManagement
> and use ${project.version}, or just use ${project.version} in the sibling
> poms instead of using the X.X-SNAPSHOT version ??
By the way, I use ${project.version}- way in all
my projects and it's fully cover all necessities.
If you will use ${project.version} instead of using X.X-SNAPSHOT
version, it could make some troubles, because ${project.version}
property for current pom (module) is this module version. And if you
associate dependency version with current module version/ it could be
not good.
I use this way:
*parent pom.xml:*
1.0-SNAPSHOT
/
a-module
b-module
...
a-module
${project.version}
/
*b-module pom.xml:*
/
...
a-module
/
In this variant I'm using the same version for all modules in my project
and all sibling modules depends on each other by project version of
parent module.
Release plugin update only module version, not dependency versions. All
dependency versions will be updated automatically by using
dependencyManagement section and ${project.version} property.
It's usable in most projects, than have no necessity to have different
versions of project modules.
In this case also usable to set
/true/ in release plugin
configuration.
It help you to input release and next version only for parent module,
sibling modules will use the same version.
Hope this help,
Aleksey.
-
The information in this message may be proprietary and/or
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your
computer.
RE: maven release plugin not updating sub-module dependencies
Aleksey,
I thought it would update the sibling modules based on the modules included in
the parent pom. It updates the sibling dependencies when it changes the tagged
version just not the next version.
So you're saying move the sibling dependencies to the dependencyManagement and
use ${project.version}, or just use ${project.version} in the sibling poms
instead of using the X.X-SNAPSHOT version ??
Thanks for your response
Rick
-Original Message-
From: Aleksey Didik [mailto:di...@magenta-technology.ru]
Sent: Thursday, July 08, 2010 8:12 AM
To: Maven Users List
Subject: Re: maven release plugin not updating sub-module dependencies
Hello Rick.
In this case release will not change dependencies versions, because
maven have no difference between external artifact and module artifact.
My suggestion is to use ${project.version} and
for cross module dependencies.
hth,
Aleksey Didik.
08.07.2010 17:59, DeGrande, Rick пишет:
> No, I was thinking about doing that, but I have the dependencies in the
> sibling poms. I'm not using the ${project.version} in these poms. I just
> have the SNAPSHOT version specified on the sibling dependencies.
>
>
> Thanks
> Rick
>
> -Original Message-
> From: Aleksey Didik [mailto:di...@magenta-technology.ru]
> Sent: Thursday, July 08, 2010 1:14 AM
> To: Maven Users List
> Subject: Re: maven release plugin not updating sub-module dependencies
>
>
>Hello, Rick.
> Please, clarify, how do you define submodule dependency?
> Do you use section in parent pom with
> ${project.version} property?
>
> Best regards,
> Aleksey Didik.
>
>
> 08.07.2010 2:34, DeGrande, Rick пишет:
>> I have a multi--module configuration. the directory structure is:
>>
>> aggregate
>> ejb
>> war
>>
>> The war file includes the ejb as a dependency. When I do a
>> release:prepare -DdryRun maven generates the pom.xml.tag correctly but
>> it doesn't update the sub module dependencies in the pom.xml.next. How
>> do I get it to update the sub-module dependencies ?
>>
>>
>>
>> thanks
>>
>>
>>
>>
>> -
>> The information in this message may be proprietary and/or
>> confidential, and protected from disclosure. If the reader of this
>> message is not the intended recipient, or an employee or agent
>> responsible for delivering this message to the intended recipient,
>> you are hereby notified that any dissemination, distribution or
>> copying of this communication is strictly prohibited. If you have
>> received this communication in error, please notify First Data
>> immediately by replying to this message and deleting it from your
>> computer.
>
> -
> 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: maven release plugin not updating sub-module dependencies
No, I was thinking about doing that, but I have the dependencies in the sibling
poms. I'm not using the ${project.version} in these poms. I just have the
SNAPSHOT version specified on the sibling dependencies.
Thanks
Rick
-Original Message-
From: Aleksey Didik [mailto:di...@magenta-technology.ru]
Sent: Thursday, July 08, 2010 1:14 AM
To: Maven Users List
Subject: Re: maven release plugin not updating sub-module dependencies
Hello, Rick.
Please, clarify, how do you define submodule dependency?
Do you use section in parent pom with
${project.version} property?
Best regards,
Aleksey Didik.
08.07.2010 2:34, DeGrande, Rick пишет:
> I have a multi--module configuration. the directory structure is:
>
> aggregate
> ejb
> war
>
> The war file includes the ejb as a dependency. When I do a
> release:prepare -DdryRun maven generates the pom.xml.tag correctly but
> it doesn't update the sub module dependencies in the pom.xml.next. How
> do I get it to update the sub-module dependencies ?
>
>
>
> thanks
>
>
>
>
> -
> The information in this message may be proprietary and/or
> confidential, and protected from disclosure. If the reader of this
> message is not the intended recipient, or an employee or agent
> responsible for delivering this message to the intended recipient,
> you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have
> received this communication in error, please notify First Data
> immediately by replying to this message and deleting it from your
> computer.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven release plugin not updating sub-module dependencies
I have a multi--module configuration. the directory structure is: aggregate ejb war The war file includes the ejb as a dependency. When I do a release:prepare -DdryRun maven generates the pom.xml.tag correctly but it doesn't update the sub module dependencies in the pom.xml.next. How do I get it to update the sub-module dependencies ? thanks - The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer.
Best Practices Question: Teams working on different modules / SCM, etc
I've been trying to read up on best practices with Maven in a team environment where different groups are working on different but related modules. Been reading over chp7 of 'Better Builds With Maven' but still have some questions. To keep it simple for sake of discussion... war project depends on jarA, jarA depends jarB. Three different teams are working on those three separate modules. For this current project we have not set up a continuous integration server yet. (We're still on CVS here for source control management but I know another team using CruiseControl for continuous builds so at some point we'll use that as well.) We are using Artificatory for our local internal repository. Right now since the project is still very young we're just declaring the version number as 1.0-SNAPSHOT. Ultimately all that we care about building to the dev server is the webapp (war) project. We started out for a while having the various jar projects do a 'mvn deploy' when they were ready to deploy their jars, the problem with that is how does jarB know that he's not going to break jarA who depends on jarB if he does a deploy? jarA team can be happily going along coding against a local repository version of jarB that allows him to not break. Lets say jarA doesn't do a deploy, but now a dev build of the war project needs to take place - it ends up pulling in the new jarB snapshot which causes things to break. How is that kind of thing best avoided (other than forcing down locked version numbers?) How do you make sure you can always get a good build of a dev war that is dependent on various interrelated modules? Typically we've done this the harder way and not relied on teams using mvn deploy - and instead we would require teams to tag their code with a DEV tag (since we still want to allow people to check in code that compiles but isn't DEV server ready yet.) On the server we then go through and do a cvs update from the DEV tag for all the modules and build them which makes sure we get a decent build or catch any problems. I'm guessing this is where a continuous integration build system would help? ( I assume it can do the same thing and build from a tag and build in the correct order? ) I'm just wondering what the best practice is in making sure you can 1) allow developers to always be checking in code (that compiles, but could break another person depending on it) and 2) easily get a quick dev build of the main project (war) to a server? Next probably somewhat naive question, but in regard to increasing a version number, I take the best practice is when some sub-module feels its ready for a new version number, they simply update their pom version number (remove the -SNAPSHOT) and check in their pom and possibly do a mvn deploy. Then they go back with maybe a 1.1.1-SNAPSHOT declared for their project so they can continue to work on the next release with snapshots? I take it then they just communicate with the other teams that a new version or snapshot version is ready. So to sum up what I 'think' is the way day-to-day operations run for teams 1) team works on their code with 1.0-SNAPSHOT version number 2) before checking in any code, run mvn clean install with the -U flag to get any new dependent snap shot versions 3) assuming code builds, it can be checked in 4) when happy with code as stable enough for others to use, tag it to DEV, do mvn deploy There is something still really wrong with the above though. It doesn't allow someone to ALWAYS be able to make a good dev build, but I guess that's the drawback to using snapshots. Any suggestions and articles on the best way to handle a combination of doing source control management and maven for multiple module projects would be appreciated.
Re: toughest time trying to get a jsp filtered.. any help much appreciated
[SOLVED] not sure how because I've modified too many things since I came back to looking at this issue. On Sat, May 22, 2010 at 7:15 AM, Martin Gainty wrote: > > > you're probably want to consider a templating language such as FTL/VM.. > i'll borrow this test-include from FreeMarker > Well in this case I really don't. That would require just one more external file to manage. In this simple case all I wanted to do is make sure that a version number declared as a dependency in my web app's pom (for a swf file) was actually used a version number I could use in one of my jsps. I only wanted to make this change in one place when the version number changed. Since the pom obviously needed to know this version number for sure, it made sense to me to just have a way to access it from the pom file. Thanks for everyone's patience. I'm sure it was something really stupid I was doing since this original description on using the maven-war webResoures task is working just fine now: http://fogit.blogspot.com/2009/07/web-resources-filtering-with-maven-2.html
Re: toughest time trying to get a jsp filtered.. any help much appreciated
On Fri, May 21, 2010 at 11:53 PM, Rick R wrote:
>
>
> On Fri, May 21, 2010 at 9:44 PM, Wayne Fay wrote:
>
>> >
>> > FOO/foo.bar>
>> >
>>
>> If this is literally cut and paste from your pom.xml file, the problem
>> should be pretty obvious. If you changed it and accidentally deleted
>> the <, that's another story.
>>
>
>
> Ha sorry. no it wasn't cut and paste:) I see the mistake above. I had
> several properties and then pasted them here and just screwed up making it
> more generic. Thanks though.
>
I also ended up getting around the problem (in a flex/java app) by
utilizing the flex mojos copy-flex-resources goal of the plugin.
However, I still would be curious why I wasn't have it filter correctly for
the jsp. The plugin section was copy and paste:
org.apache.maven.
plugins
maven-war-plugin
2.0.2
src/main/webapp
**/*.jsp
true
The relevant property I was trying to replace.. copy and paste:
1.0-SNAPSHOT
and then from a snippet in the index.jsp
"src", "integrated-media-swf-${swf.version}.swf"
Re: toughest time trying to get a jsp filtered.. any help much appreciated
On Fri, May 21, 2010 at 9:44 PM, Wayne Fay wrote: > > > > FOO/foo.bar> > > > > If this is literally cut and paste from your pom.xml file, the problem > should be pretty obvious. If you changed it and accidentally deleted > the <, that's another story. > Ha sorry. no it wasn't cut and paste:) I see the mistake above. I had several properties and then pasted them here and just screwed up making it more generic. Thanks though.
toughest time trying to get a jsp filtered.. any help much appreciated
I'd like to have a jsp in the root of src/main/webapps filtered and the var
replaced with a property in the war's pom.
In my pom I have:
FOO/foo.bar>
org.apache.maven.plugins
maven-war-plugin
2.0.2
src/main/webapp
**/*.jsp
true
I have an index.jsp with
${foo.bar} defined in it.
When I run mvn clean install, I never see this var replaced in the index.jsp
in the exploded dir in target.
Any ideas what I'm doing wrong?
I found this article online and it looks like I'm doing everything
correctly.
http://fogit.blogspot.com/2009/07/web-resources-filtering-with-maven-2.html
The difference in that article is he has his jsp's in a pages dir, and mine
are right out in the root (some are also under WEB-INF/jsp but the one I
want filtered is in the root of the webapp.)
Re: release plugin: Create new SNAPSHOT from release tag?
Check out the 1.0 tag and run mvn release:branch http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html See the note about branching from a tag. On 4/30/10 7:08 AM, "Kalpak Gadre" wrote: > Past discussion which happened on similar question, > > http://www.mail-archive.com/users@maven.apache.org/msg108587.html > > Kalpak > > >> Hi, >> Using release:prepare, release:perform I successfully created a tag in svn. >> I now have to fix some bugs so I thought I should create a new branch from >> the svn tag. Is this the way to go? >> >> So I created from 1.0-SNAPSHOT the svn tag 1.0 and have the working copy >> 2.0-SNAPSHOT. To fix a bug i the old release I want to create the branch >> 1.1-SNAPSHOT from the version 1.0. >> >> How can I do this? It is a multi module project and I'd rather not fix all >> versions by hand... >> >> Cheers, >> >> Jan >> > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: artifacts built from alternate scm branches
That's exactly how we manage the version #s for branches. We use the convention that the leading number comes from the source of the branch (usually the trunk), then we add a meaningful identifier for the branch, and finally a branch version that can be incremented by the release process - 6.0.0-mybranch-2.1-SNAPSHOT See - http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-p om-syntax.html#pom-relationships-sect-version-build-numbers Rick On 4/16/10 9:23 AM, "Stephen Connolly" wrote: > who said version numbers have to be numbers! > > 6.0.0-mybranch-SNAPSHOT > 6.0.0-yourbranch-SNAPSHOT, > > etc > > On 16 April 2010 13:09, Nicola Musatti wrote: > >> Stephen Connolly wrote: >> >>> different branches should have different version numbers >>> >> This would be reasonable if I only issued maintenance releases from my >> branches. In my case however branches evolve independently and I'd rather >> not assign them arbitrary version numbers. >> >> Cheers, >> Nicola Musatti >> >> On 16 April 2010 11:12, Nicola Musatti >> nicola.musa...@objectway.it>> wrote: >>> >>>Hallo, >>>I have different branches of the same project that are being >>>developed in parallel, to cater for customer customizations. Is >>>there a standard way to identify the resulting artifacts? At first >>>I thought of giving each a different classifier, but I'm under the >>>impression that this is not what classifiers are meant for, as >>>I've only seen them used to identify build variants obtained from >>>the same set of sources. >>> >>>Thanks, >>>Nicola Musatti >>> >>>- >>>To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>><mailto:users-unsubscr...@maven.apache.org> >>> >>>For additional commands, e-mail: users-h...@maven.apache.org >>><mailto: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: Multi Modules / Multi SCM urls?
Resending this question... Anyone have an idea? On 4/13/10 11:37 AM, "Rick Mangi" wrote: > Hi, > > Does anybody know if there's existing mojo to allow individual modules in a > multi-module project to point to different SCM urls? So instead of having > the entire project living in a single subversion tree it you could use > something like scm:bootstrap to check out dependent modules from various > locations but have the dependencies linked in the maven reactor? > > Thanks, > > Rick > > > > > > - > 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
Multi Modules / Multi SCM urls?
Hi, Does anybody know if there's existing mojo to allow individual modules in a multi-module project to point to different SCM urls? So instead of having the entire project living in a single subversion tree it you could use something like scm:bootstrap to check out dependent modules from various locations but have the dependencies linked in the maven reactor? Thanks, Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Can I control the number string by which the SNAPSHOT keyword is replaced at the time of deployment to snapshot repository?
Henika, That timestamp is crucial to Maven as it determines which snapshot build of an artifact is the latest, you really shouldn't touch it. Rick On 4/12/10 7:45 AM, "Henika Tekwani" wrote: > > Hi, > > As we know that when we deploy an artifact to a snapshot repository the > SNAPSHOT keyword in the artifact version, say 9.5.0-SNAPSHOT, is replaced by > a timestamp number (e.g., my-app-9.5.0-20100412.084615-1.jar). In this case > SNAPSHOT is replaced by ³20100412.084615² which is an automatically > generated timestamp number. > > I wanted to know that is there any way by which I can control the number > string by which the SNAPSHOT keyword is replaced at the time of deployment, > i.e., instead of this automatically generated timestamp number can I supply > some other uniquely generated number string (e.g., 20100412.1.234071) at the > time of deployment such that the SNAPSHOT keyword is replaced by my uniquely > generated number string. > > Thanks & Regards, > -Henika - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Had to remove a plugin dir from local repo, why? [was Re: what does it mean with this error when trying to run mvn eclipse:eclipse (Cannot find mojo descriptor for: 'eclipse:eclipse' - Treating as n
I changed the subject since I think this is now more of a general local repository question. On Wed, Feb 3, 2010 at 2:08 PM, Anders Hammar wrote: > Regarding why Maven tries to use 2.8-SNAPSHOT and isn't successful I'm > somewhat puzzled. You didn't post the full error output, so I can't say for > sure. Also, I need to know more about your Artifactory setup to spot the > problem. > Ok, this is really weird, how could one's existing local repository affect things? I was going to post a long email of things I've tried but the bottom line is that when I went in to my local repository and deleted: org/apache/maven/plugins/maven-eclipse-plugin/ The, 'mvn eclipse:eclipse' command worked just fine - the plugin downloaded fine ( I was trying this off a simple archetype jar project not using the artifactory repo.) I knew something had to be up since when I backed up (moved my repository to repo.bak) and then ran mvn eclipse:eclipse the eclipse plugin worked just fine. As soon as I put my old repo back I got the failure error shown at the end of this post. So now my question is: why in the world would my local repository affect this? Did I have some kind of corrupt version of the plugin? Here was the error I WAS getting BEFORE I manually removed the maven-eclipse-plugin dir from my repo [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-eclipse-plugin -Dversion=2.8-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-eclipse-plugin -Dversion=2.8-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.8-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.8-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2)
Re: what does it mean with this error when trying to run mvn eclipse:eclipse (Cannot find mojo descriptor for: 'eclipse:eclipse' - Treating as non-aggregator.)
On Wed, Feb 3, 2010 at 3:49 AM, Anders Hammar wrote: > Ok, first I would like to point you at some Maven books. They are great to > get the basics: > http://books.sonatype.com > Yes I need to read that more thoroughly. I did look through it once and tried to refer to even in this case, but it was one of those things where I didn't even really know where to look since wasn't sure of the exact cause. > Try this on the command line: > mvn org.apache.maven.plugins:maven-eclipse-plugin:2.7:eclipse > > Perfect! Yes that worked! > By adding the > following xml section to your project, you configure Maven to use v2.7 of > the plugin (but only when executed for this project or a project that > inherits from this): > > > > >org.apache.maven.plugins >maven-eclipse-plugin >2.7 > > > > > > Perfect also! (This is now what I've added to my project's pom so this issue doesn't keep happening.) > The schema for pom.xml is found here: > http://maven.apache.org/maven-v4_0_0.xsd > > Ok thanks. Although even looking at that schema it makes it difficult for me as a newb to look at and say "ok from that schema create the pluginManagement definition as you did above. *So the only last question I have 'Where did things go wrong in my attempt to use mvn eclipse:eclipse?' Even if I run just a simple archetype jar (no dependency on my company repo) and then run mvn eclipse:eclipse without declaring the version like you mentioned I'll get the issue, so I guess it's something wrong with the eclipse 2.8 snapshot not being in the public repo? I would think that if I went to the maven eclipse plugin info http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html that it would mention the help you gave me (declaring the version in my pom or settings) since I would think others would run into the same issues as myself (or else I guess everyone is just more up-to-speed and instantly knows what to do.:) > As a last point I would like you to talk to your local Maven people as > well. > They know > your local environment and should be able to help you. I can't solve > problems in your local environment. > Ha, I know you can't. But the guy setting the local repo up was newb also. We're trying to push for maven to be used here so learning on the fly. Thanks again for your help. I did learn a LOT through this whole ordeal.
Re: what does it mean with this error when trying to run mvn eclipse:eclipse (Cannot find mojo descriptor for: 'eclipse:eclipse' - Treating as non-aggregator.)
On Tue, Feb 2, 2010 at 2:43 PM, Anders Hammar wrote: > > Also, try what I suggested about specifying the version of the plugin to v > 2.7. > Ok I totally suck at Maven :) I'm trying to figure out how the heck you figure out how to declare the above and where you figure out the pom syntax for the eclipse plugin to declare the version? I looked out here http://mvnrepository.com/artifact/maven/maven-eclipse-plugin (I normally go to the above repo look up to determine the pom dependencies I want to add.) Obviously it is using 2.8 since after the mvn eclipse:eclipse error I end up seeing: Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-eclipse-plugin -Dversion=2.8-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.8-SNAPSHOT >From the above I assume I can build the pom dependency and change it to 2.7 like you mentioned, but somewhere I must be able to find that pom declaration in a repo online somewhere? Just trying to learn the process of where I find these things?
Re: what does it mean with this error when trying to run mvn eclipse:eclipse (Cannot find mojo descriptor for: 'eclipse:eclipse' - Treating as non-aggregator.)
On Tue, Feb 2, 2010 at 1:56 AM, Anders Hammar wrote: > I'm quite sure you must have reconfigured something since last time it > worked. The plugin exists in central, and for some reason your build isn't > looking there. > > Run > mvn help:effective-pom > and find the section and paste it in a reply. > > false central http://internalcompanyURL:8081/artifactory/plugins-releases false snapshots http://internalcompanyURL:8081/artifactory/plugins-snapshots codehaus-plugins http://dist.codehaus.org/ legacy Maybe something's screwed up with the internal artifactory repo? Thanks so much for the help. Also, you might want to consider locking the version of the plugin being > used. You do that in the pluginManagement section. Currently I think you > don't have a version specified, so Maven will try to get the latest > (2.8-SNAPSHOT). That may cause issues when a new version is available, > which > isn't backwardscompatible for some reason. Or possibly you do have the > version set to 2.8-SNAPSHOT? You can see that as well in the effective pom. > http://maven.apache.org/pom.html#Plugin_Management > (In this case you only need to specify groupId, artifactId, and version. > The > latest released version is 2.7, which exists in central.) > > /Anders > > On Mon, Feb 1, 2010 at 22:32, Rick R wrote: > > > running mvn eclipse:eclipse used to work.. now I'm getting... > > > > [INFO] Unable to find resource > > 'org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.8-SNAPSHOT' > > in > > repository codehaus-plugins (http://dist.codehaus.org/) > > [INFO] Cannot find mojo descriptor for: 'eclipse:eclipse' - Treating as > > non-aggregator. > > > > I'm new to maven and stumped by what is going on? > > > > -- > > Rick R > > > -- Rick R
what does it mean with this error when trying to run mvn eclipse:eclipse (Cannot find mojo descriptor for: 'eclipse:eclipse' - Treating as non-aggregator.)
running mvn eclipse:eclipse used to work.. now I'm getting... [INFO] Unable to find resource 'org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.8-SNAPSHOT' in repository codehaus-plugins (http://dist.codehaus.org/) [INFO] Cannot find mojo descriptor for: 'eclipse:eclipse' - Treating as non-aggregator. I'm new to maven and stumped by what is going on? -- Rick R
Tomcat plugin doesn't seem to be using build final name for context (seems to always use artifactId)
I'm confused here. The docs
http://mojo.codehaus.org/tomcat-maven-plugin/usage.html state that the
default context is
Context path of /${project.build.finalName} if no explicit one is given.
In my war pom I have:
dataselector-web
but I later have
dataselector
The war builds fine to the name "dataselector.war" and I can manually
deploy it just fine, yet when I try to use the tomcat plugin it tries
to deploy to the context dataselector-web which is the artificatId and
not the finalName.
What did I do wrong? I don't mind declaring the name in the tomcat
module config but all the examples I see show a hardcoded path for the
context. I dont' want to to hardcode that context path (eg
/Users/rick/tomcat/webapps/dataselector )
--
Rick R
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
SOLVED I guess. Re: What happens to cause a build to not work after blowing out your repo - how to force so things are always checked locally?
After more googling I found this discussion http://www.yeap.de/blog2.0/archives/183-Upgrading-flex-mojos-2.0.0-to-flexmojos-maven-plugin-3.x.htmlwhere others had the same issue. Apparently jdom is needed in your maven lib if a certain dependency relies on it. Something with plexus was bitching about it but no idea what that was about. Seems really bad though that someone would have to manually add that jar to the maven lib so I'd like to get the root cause of thatissue at some point. Apparently in the older maven projects it was part of the uber-jar? I need a drink now for all the time wasted on this today:) I had tried adding a dependency to the pom for the jdom jar (actually that was one of the first things I did), but that didn't help. I wouldn't have thought that it was needed in the actual lib dir. (Now a crazier question though is why would my old repo have worked though without adding this jar? I'm too tired to try to figure that one out.) On Fri, Dec 11, 2009 at 7:51 PM, Rick R wrote: > > > On Fri, Dec 11, 2009 at 6:37 PM, Rick R wrote: > >> >> Now to add to the confusion, not sure it's the firewall at all ... on the >> Mac and Windows machine both behind company firewall...the Mac now gives the >> errors like: >> >> >> [INFO] >> >> [ERROR] BUILD ERROR >> [INFO] >> >> [INFO] Failed to resolve artifact. >> >> Missing: >> -- >> 1) com.adobe.flex:compiler:pom:3.2.0.3958 >> Path to dependency: >> 1) >> org.sonatype.flexmojos:flexmojos-maven-plugin:maven-plugin:3.4.2 >> 2) com.adobe.flex:compiler:pom:3.2.0.3958 >> >> >> > For what it's worth I got past my recent errors by changing the repository > http://repository.sonatype.org/content/groups/public/ > > Now the project that I provided earlier that was zipped up builds, but I > still have the issue in my current project related to the below. But I'll > work now on debugging better since the archetype works it must be something > conflicting in my code causing an issue. Still really odd my old repo works > with the same code base though. That part has me really stumped. > > > [WARNING] Not defined if locales should be merged or not > [WARNING] Unable to find license.jar on classpath. Check wiki for > instructions about how to add it: >https://docs.sonatype.org/display/FLEXMOJOS/FAQ#FAQ-1.3 > [FATAL ERROR] org.sonatype.flexmojos.compiler.LibraryMojo#execute() caused > a linkage error (java.lang.NoClassDefFoundError) and may be out-of-date. > Check the realms: > [FATAL ERROR] Plugin realm = > app0.child-container[org.sonatype.flexmojos:flexmojos-maven-plugin:3.4.2] > > urls[93] = > file:/Users/rick/.m2/repository/org/apache/maven/shared/maven-plugin-testing-harness/1.1/maven-plugin-testing-harness-1.1.jar > > [FATAL ERROR] Container realm = plexus.core > urls[0] = file:/Users/rick/java/maven/lib/maven-2.2.1-uber.jar > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] org/jdom/input/SAXBuilder > org.jdom.input.SAXBuilder > [INFO] > > [INFO] Trace > java.lang.NoClassDefFoundError: org/jdom/input/SAXBuilder > at > org.sonatype.flexmojos.utilities.FDKConfigResolver.getConfig(FDKConfigResolver.java:95) > > -- Rick R
Re: What happens to cause a build to not work after blowing out your repo - how to force so things are always checked locally?
On Fri, Dec 11, 2009 at 6:37 PM, Rick R wrote: > > Now to add to the confusion, not sure it's the firewall at all ... on the > Mac and Windows machine both behind company firewall...the Mac now gives the > errors like: > > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > > Missing: > -- > 1) com.adobe.flex:compiler:pom:3.2.0.3958 > Path to dependency: > 1) org.sonatype.flexmojos:flexmojos-maven-plugin:maven-plugin:3.4.2 > 2) com.adobe.flex:compiler:pom:3.2.0.3958 > > > For what it's worth I got past my recent errors by changing the repository http://repository.sonatype.org/content/groups/public/ Now the project that I provided earlier that was zipped up builds, but I still have the issue in my current project related to the below. But I'll work now on debugging better since the archetype works it must be something conflicting in my code causing an issue. Still really odd my old repo works with the same code base though. That part has me really stumped. [WARNING] Not defined if locales should be merged or not [WARNING] Unable to find license.jar on classpath. Check wiki for instructions about how to add it: https://docs.sonatype.org/display/FLEXMOJOS/FAQ#FAQ-1.3 [FATAL ERROR] org.sonatype.flexmojos.compiler.LibraryMojo#execute() caused a linkage error (java.lang.NoClassDefFoundError) and may be out-of-date. Check the realms: [FATAL ERROR] Plugin realm = app0.child-container[org.sonatype.flexmojos:flexmojos-maven-plugin:3.4.2] urls[93] = file:/Users/rick/.m2/repository/org/apache/maven/shared/maven-plugin-testing-harness/1.1/maven-plugin-testing-harness-1.1.jar [FATAL ERROR] Container realm = plexus.core urls[0] = file:/Users/rick/java/maven/lib/maven-2.2.1-uber.jar [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org/jdom/input/SAXBuilder org.jdom.input.SAXBuilder [INFO] [INFO] Trace java.lang.NoClassDefFoundError: org/jdom/input/SAXBuilder at org.sonatype.flexmojos.utilities.FDKConfigResolver.getConfig(FDKConfigResolver.java:95)
Re: What happens to cause a build to not work after blowing out your repo - how to force so things are always checked locally?
On Fri, Dec 11, 2009 at 6:27 PM, Rick R wrote: > > On Fri, Dec 11, 2009 at 5:22 PM, Wayne Fay wrote: > >> > runs just fine when going against my OLD repo. With a fresh EMPTY repo >> I'll >> > end up with the following: >> > >> > >> app0.child-container[org.sonatype.flexmojos:flexmojos-maven-plugin:3.4.2] >> >> What version of the flexmojos-maven-plugin is used in your successful >> build, against the old repo? Use -X for debug mode if you're not sure. >> >> > > > My old repo only has 3.4.2 plugin so isn't that all it can run against? > > But here is the really weird thing (and I'm wondering if it is some issue > being behind the work firewall?) > Now to add to the confusion, not sure it's the firewall at all ... on the Mac and Windows machine both behind company firewall...the Mac now gives the errors like: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) com.adobe.flex:compiler:pom:3.2.0.3958 Path to dependency: 1) org.sonatype.flexmojos:flexmojos-maven-plugin:maven-plugin:3.4.2 2) com.adobe.flex:compiler:pom:3.2.0.3958 Yet on Windows it's the same thing as I saw on the home linux box (not behind a firewall): [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) com.adobe.flex.framework:flex-framework:pom:3.2.0.3958 Path to dependency: 1) net.reumann:swc:swc:1.0-SNAPSHOT 2) com.adobe.flex.framework:flex-framework:pom:3.2.0.3958 -- 1 required artifact is missing. for artifact: net.reumann:swc:swc:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2)
Re: What happens to cause a build to not work after blowing out your repo - how to force so things are always checked locally?
On Fri, Dec 11, 2009 at 5:22 PM, Wayne Fay wrote: > > runs just fine when going against my OLD repo. With a fresh EMPTY repo > I'll > > end up with the following: > > > > app0.child-container[org.sonatype.flexmojos:flexmojos-maven-plugin:3.4.2] > > What version of the flexmojos-maven-plugin is used in your successful > build, against the old repo? Use -X for debug mode if you're not sure. > > My old repo only has 3.4.2 plugin so isn't that all it can run against? But here is the really weird thing (and I'm wondering if it is some issue being behind the work firewall?) I took that same test project that I posted and used it from a linux box not behind the company firewall (with a completely fresh repo as well) and I end up with the following error instead: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) com.adobe.flex.framework:flex-framework:pom:3.2.0.3958 Path to dependency: 1) net.reumann:swc:swc:1.0-SNAPSHOT 2) com.adobe.flex.framework:flex-framework:pom:3.2.0.3958 -- 1 required artifact is missing. for artifact: net.reumann:swc:swc:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) AND NOW back on the mac machine, when running that test fresh again I now notice these kinds of messages which don't look good: Downloading: http://repo1.maven.org/maven2/org/graniteds/granite-generator-share/2.0.0.GA/granite-generator-share-2.0.0.GA.pom [INFO] Unable to find resource 'org.graniteds:granite-generator-share:pom: 2.0.0.GA' in repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/org/sonatype/flexmojos/flexmojos-generator-constraints/3.4.2/flexmojos-generator-constraints-3.4.2.pom Downloading: http://repo1.maven.org/maven2/com/adobe/flex/compiler/3.2.0.3958/compiler-3.2.0.3958.pom [INFO] Unable to find resource 'com.adobe.flex:compiler:pom:3.2.0.3958' in repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/com/adobe/flex/compiler/3.2.0.3958/compiler-3.2.0.3958.pom [INFO] Unable to find resource 'com.adobe.flex:compiler:pom:3.2.0.3958' in repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/com/adobe/flex/compiler/asdoc/3.2.0.3958/asdoc-3.2.0.3958.pom [INFO] Unable to find resource 'com.adobe.flex.compiler:asdoc:pom:3.2.0.3958' in repository central ( http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/com/adobe/flex/compiler/asdoc/3.2.0.3958/asdoc-3.2.0.3958.pom [INFO] Unable to find resource 'com.adobe.flex.compiler:asdoc:pom:3.2.0.3958' in repository central ( http://repo1.maven.org/maven2) and the error is completely DIFFERENT now: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) com.adobe.flex:compiler:pom:3.2.0.3958 Path to dependency: 1) org.sonatype.flexmojos:flexmojos-maven-plugin:maven-plugin:3.4.2 2) com.adobe.flex:compiler:pom:3.2.0.3958 ... and 5 others missing as well I'm going nuts:)
Re: What happens to cause a build to not work after blowing out your repo - how to force so things are always checked locally?
On Fri, Dec 11, 2009 at 2:25 PM, Wayne Fay wrote:
>
> I think there's an extremely good chance you do not have your plugin
> versions locked down in your pom files with
> [1.2.3].
>
I'm pretty sure my small project hasn't changed version numbers of plugins
so I'm completely stumped. For example, here is a created archetype if
someone wants to run mvn clean install in the root (it's small, it'll break
when trying to do the unit test for flash without the plugin but i don't
care about that, if you got to that point you got passed the error I'm
seeing.) http://dl.dropbox.com/u/86998/flex-project.zip
This is what is odd, is that project above which I just made from the
following archetype cmd
mvn archetype:generate -DarchetypeRepository=
http://repository.sonatype.org/content/groups/flexgroup-DarchetypeGroupId=org.sonatype.flexmojos
-DarchetypeArtifactId=flexmojos-archetypes-modular-webapp
-DarchetypeVersion=3.4.1 (as described in the 3rd archetype here
http://flexmojos.sonatype.org/getting-started.html )
runs just fine when going against my OLD repo. With a fresh EMPTY repo I'll
end up with the following:
~/projects/flex-project $ mvn clean install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - net.reumann:flex-project:pom:1.0-SNAPSHOT
[INFO] swc Library
[INFO] swf Application
[INFO] Unnamed - net.reumann:war:war:1.0-SNAPSHOT
[WARNING] POM for 'classworlds:classworlds:pom:1.1:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for 'jaxen:jaxen:pom:1.1:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[INFO]
[INFO] Building Unnamed - net.reumann:flex-project:pom:1.0-SNAPSHOT
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /Users/rick/projects/flex-project/pom.xml to
/Users/rick/.m2/repository/net/reumann/flex-project/1.0-SNAPSHOT/flex-project-1.0-SNAPSHOT.pom
[INFO]
[INFO] Building swc Library
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory /Users/rick/projects/flex-project/swc/target
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (MacRoman actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/Users/rick/projects/flex-project/swc/src/main/resources
[INFO] [flexmojos:compile-swc {execution: default-compile-swc}]
[INFO] Flexmojos 3.4.2 - Apache License (NO WARRANTY) - See COPYRIGHT file
[WARNING] Not defined if locales should be merged or not
[WARNING] Unable to find license.jar on classpath. Check wiki for
instructions about how to add it:
https://docs.sonatype.org/display/FLEXMOJOS/FAQ#FAQ-1.3
[FATAL ERROR] org.sonatype.flexmojos.compiler.LibraryMojo#execute() caused a
linkage error (java.lang.NoClassDefFoundError) and may be out-of-date. Check
the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.sonatype.flexmojos:flexmojos-maven-plugin:3.4.2]
urls[0] =
file:/Users/rick/.m2/repository/org/sonatype/flexmojos/flexmojos-maven-plugin/3.4.2/flexmojos-maven-plugin-3.4.2.jar
urls[1] =
file:/Users/rick/.m2/repository/org/sonatype/flexmojos/flexmojos-generator-api/3.4.2/flexmojos-generator-api-3.4.2.jar
urls[2]..etc etc
urls[3]
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/Users/rick/java/maven/lib/maven-2.2.1-uber.jar
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] org/jdom/input/SAXBuilder
org.jdom.input.SAXBuilder
[INFO]
[INFO] Trace
java.lang.NoClassDefFoundError: org/jdom/input/SAXBuilder
at
org.sonatype.flexmojos.utilities.FDKConfigResolver.getConfig(FDKConfigResolver.java:95)
What happens to cause a build to not work after blowing out your repo - how to force so things are always checked locally?
Hopefully I describe this situation correctly, because I'm constantly getting burned on it at work it seems and the non-maven co-workers always end up going "sheesh this stuff seems to happen all the time with maven." Here's a situation: I run an archetype command to create a project setup (happens in this case to be a flex archetype.) My first mvn install command works perfect and I go along my way building the start of my app. As I'm building I'm often doing mvn clean install along the way and things are going just fine. Now I have a co-worker check out the project a few weeks later. He runs mvn clean install and boom an issue (in this case it was: [INFO] Trace java.lang.NoClassDefFoundError: org/jdom/input/SAXBuilder at org.sonatype.flexmojos.utilities.FDKConfigResolver.getConfig(FDKConfigResolver.java:95) at org.sonatype.flexmojos.utilities.FDKConfigResolver.getFontManagers(FDKConfigResolver.java:118) ) ) So I'm pissed because it was fine for me locally. I then go and backup my local repo and try the mvn clean install... bam. blows up with the same error. So my question is: 1) How do I prevent this from happening? In other words, when I do a 'mvn clean install' I don't want to check an enormous dependency graph, but I'd certainly like to know that the jars needed to build my project or to run it are REALLY there in the repo and not just in my local repo. Shouldn't there be a way to enforce this? My app might only require (as an example) 5 runtime jars and maybe 10 compile time jars - that should be easy to check. 2) What happens that causes my initial build to work but then later not work if I start with a cleaned out local repository? Does it mean some dependency repository got borked somehow? (Again, it would sure be nice to know about this when building locally.. I'd prefer knowing there is a real issue that happened and force me to run mvn in offline mode if need be. I'd prefer that over doing a checkin and telling someone to go ahead and build the project and have it fail on them.) Thanks for any help in understanding the situation.
Re: Problem with mvn site:run and javadocs
Done. Thanks Lukas. On 10/21/09 3:42 AM, "Lukas Theussl" wrote: > > Please attach your findings here: > > http://jira.codehaus.org/browse/MSITE-220 > > Cheers, > -Lukas > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Problem with mvn site:run and javadocs
Hello, I'm encountering a strange problem with the generation of my javadocs report in the maven site plugin. If I run mvn javadoc:javadoc it generates the javadocs, but when I run mvn site:run and browse to the javadocs report I see the following in the console: /Users/mangir/work/kids-web-core/src/main/java/com/nickonline/web/filter/rew rite/DefaultRewriteHandler.java:18: cannot find symbol symbol : variable LogFactory location: class com.nickonline.web.filter.rewrite.DefaultRewriteHandler protected static final Log log = LogFactory ^ java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast to com.sun.javadoc.AnnotationTypeDoc And in the browser I get a bunch of messages similar to the following: HTTP ERROR: 500 Error rendering Maven report: Exit code: 1 - /Users/mangir/work/kids-web-core/src/main/java/com/nickonline/ir/BaseIR.java :7: package net.sf.ehcache does not exist import net.sf.ehcache.CacheManager; ^ /Users/mangir/work/kids-web-core/src/main/java/com/nickonline/ir/BaseIR.java :18: cannot find symbol symbol : class CacheManager location: interface com.nickonline.ir.BaseIR public void setCacheManager(CacheManager cacheManager); ^ /Users/mangir/work/kids-web-core/src/main/java/com/nickonline/ir/BaseIR.java :19: cannot find symbol symbol : class CacheManager location: interface com.nickonline.ir.BaseIR public CacheManager getCacheManager(); ^ /Users/mangir/work/kids-web-core/src/main/java/com/nickonline/ir/BaseIRImpl. java:3: package net.sf.ehcache does not exist import net.sf.ehcache.CacheManager; ^ /Users/mangir/work/kids-web-core/src/main/java/com/nickonline/ir/BaseIRImpl. java:5: package org.apache.commons.logging does not exist import org.apache.commons.logging.Log; ^ /Users/mangir/work/kids-web-core/src/main/java/com/nickonline/ir/BaseIRImpl. java:6: package org.apache.commons.logging does not exist import org.apache.commons.logging.LogFactory; ^ I'm pretty stumped on this. If I run - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Best practice - for multiple config files per environment
I know this must be a common question, and I've been googling for the best practice for using a different configuration file (say a different hibernate.cfg.xml file) for different profiles (based on a profile, local, itr, etc.) Normally I rely on a single file that is filtered based on a different filter file (prepended by the profile environment name), however the files now might be drastically different for a local build (where I define properties for a datasource) and a production build which will have different properties in the file for locating a datasource, so just using in place substitution isn't the best (I'd prefer a way to copy a completely different config file based on the profile being run.) Basically how to you include different property/xml files for your different builds (using profiles) -- Rick R
Simple question I think - how can I default to local repo if connection to internal repository is down?
I've googled this and tried to search the archives but it's hard to get a direct hit. We are using an internal repository but if for some reason that repository goes down, isn't there a way the maven build can still proceed using the files in the user's local repository (assuming of course the pom hasn't changes and dependencies since they last were connected.) Right now, if that internal repository is down, the builds will not work. My repository definitions look like this (I know there is debate about where to put the repository info, but I like it in the project's parent pom instead of on the user's machine.): central http://company-repo-IP:8081/artifactory/repo false snapshots http://company-repo-IP:8081/artifactory/repo false maven2-repository.dev.java.net Java.net Repository for Maven http://download.java.net/maven/2/ default maven2-repository.dev.java.net Java.net Repository for Maven http://download.java.net/maven/2/ default jboss.net repo Java.net Repository for Maven http://repository.jboss.org/maven2 default central http://company-repo-IP:8081/artifactory/plugins-releases false snapshots http://company-repo-IP:8081/artifactory/plugins-snapshots false - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to get cobertura tasks to run on "mvn install" ?
On Mon, Dec 22, 2008 at 9:43 AM, Stephen Connolly wrote: > Now for my standard disclaimer: > > "RUN THE DAMN TESTS TWICE!" > > I have seen: > > 1, Tests that fail when run without coverage but pass when run with > coverage. > 2. Tests that pass when run without coverage but fail when run with > coverage. Stephen, I actually saw your post come up stating the same thing while searching for "how I make sure cobertura only runs the tests once" in this thread here http://www.nabble.com/cobertura-%2B-surefire-config-td16281994.html I understand what you are saying about being sure that they are run twice (once before instrumentation), but for general use during the course of the day I'd still like to shorten the cycle by only having the tests run one time. You mention to use a profile to accomplish this, and I'm trying different things to no avail. If I disable the surefire plugin in my plugin the tests never run, so I'm confused what to do? I'm confused on how I'm supposed to set up the profile to only run the test suite once after instrumentation? I was trying a profile like below which I thought might work. I thought maybe cobertura would still force the tests to run even with the surefire plugin was set to skip, but in this scenario I get no tests run. If I remove the surefire plugin from the profile, I'll end up with the tests run twice. Thanks for any help. coverage org.codehaus.mojo cobertura-maven-plugin test cobertura org.apache.maven.plugins maven-surefire-plugin 2.4.2 true - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to get cobertura tasks to run on "mvn install" ?
Actually, hold on, the main reason it wasn't working was because I was an iidiot!! blah. Look how I had the execution code inside the configuration code! DOH! Thanks though for your patience. One of those cases where explaining what I was doing to someone pointed me to my error. On Mon, Dec 22, 2008 at 9:43 AM, Stephen Connolly wrote: > "clean" is the only phase on the clean lifecycle. > > you want a phase on the build lifecycle... > > Also, you want a phase after the tests have been compiled, and probably > after the tests have ran (to ensure you measure the coverage of working > tests... coverage of broken tests is usually meaningless, as you are > executing unplanned paths) > > Now for my standard disclaimer: > > "RUN THE DAMN TESTS TWICE!" > > I have seen: > > 1, Tests that fail when run without coverage but pass when run with > coverage. > 2. Tests that pass when run without coverage but fail when run with > coverage. > > I have seen both 1 & 2 far more often that you think. > > In *MOST* cases of #1 and in about half the cases of #2 this has been > because the developer did not understand the code optimizations that the JVM > is allowed to make. In every one of these cases, switching to another valid > JVM implementation has reproduced the issue. > > In the other half of the cases of #2 this has been because they are > performance tests... and they would be expected to fail when coverage has > instrumented the code. > > Do you have more than one thread? Run the tests twice. > > -Stephen > > 2008/12/22 Rick > >> On Mon, Dec 22, 2008 at 4:04 AM, Stephen Connolly >> wrote: >> > >> > The Sonatype book is good, and available free online and there are other >> > good tutorials. A 3-4 hours quick skim is most definitely not a waste of >> > your time. >> >> Actually I did read the sontatype book. I reread the chapter on "the >> build lifecycle" and it sounds like (following what is described in >> section 10.1) if I added the phase 'clean' and goal 'cobertura' that >> it should run the cobertura goal when the mvn clean phase is reached? >> Yes I don't see this happening. I even tried different phases. >> >> Under the plugin section under build I have (other plugins removed for >> clarity) >> >> >> >> >> >>org.codehaus.mojo >>cobertura-maven-plugin >> >> >> >> >> com/foo/ondp/**/*Test.class >> >> >> >> >>clean >> >> >> cobertura >> >> >> >> >> >> >> >> >> >> If I manually run mvn cobertura:cobertura it runs fine. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > -- Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to get cobertura tasks to run on "mvn install" ?
On Mon, Dec 22, 2008 at 4:04 AM, Stephen Connolly wrote: > > The Sonatype book is good, and available free online and there are other > good tutorials. A 3-4 hours quick skim is most definitely not a waste of > your time. Actually I did read the sontatype book. I reread the chapter on "the build lifecycle" and it sounds like (following what is described in section 10.1) if I added the phase 'clean' and goal 'cobertura' that it should run the cobertura goal when the mvn clean phase is reached? Yes I don't see this happening. I even tried different phases. Under the plugin section under build I have (other plugins removed for clarity) org.codehaus.mojo cobertura-maven-plugin com/foo/ondp/**/*Test.class clean cobertura If I manually run mvn cobertura:cobertura it runs fine. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
how to get cobertura tasks to run on "mvn install" ?
This is newbie I know, but I don't see how I get my cobertura:cobertura task (or maybe cobertura:check) to always run when I do a build with "mvn clean install." I might change it later, but for now I'd like the text coverage cobertura task to always run. I don't get what is causing the mvn tests to run when i do mvn install but not the cobertura tasks? -- Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Cobertura? what is ignore used for in maven, I don't see it mentioned...
The maven cobertura plugin page http://mojo.codehaus.org/cobertura-maven-plugin/usage.html has an example like: org.codehaus.mojo cobertura-maven-plugin com.example.boringcode.* com/example/dullcode/**/*.class com/example/**/*Test.class ... what is "ignore" used for? What's the difference between ignore and exclude? I don't see the concept of ignore mentioned at all on the cobertura site so I'm guessing it's a maven thing? -- Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[OT-ish] testing EJB3 components? ( embedded jboss? )
I'm really having a heck of time figuring out how to EASILY test my EJB3 components with Maven2/TestNG. I'm using the @EJB annotations to inject EJBs into my Stateless session beans and it works fine in my deployed ear to JBoss5. What I want to do is to test some of these EJB3s. Some of them call other stateless session beans so it's a bit difficult from a pure pojo approach since the whole context needs to be set up so the EJB3 injection can take place. I briefly looked at EJB3Unit and I thought it look overly complicated (but maybe I should continue to pursue that?). Using an embedded jboss instance looked pretty easy, but the problem is this... what I'll need to do is have my ejb jars deployed to my embedded jboss deploy directory as part of my project. How do I tell testing in maven2 to build jars to a deploy directory and not just target? Thanks for any help. -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
A couple mvn site questions..?
1) I have a project structure with a parent pom and several modules beneath it. When I run mvn site from the root (the parent pom dir) it generates the site index.html file but if I try to click on any of the module links the URLs are wrong. They try to go to /path/project/target/site/module/index.html when it needs to go to /path/project/module/target/site/index.html What's the best way to fix this? 2) I can't seem to get the surefire-plugin report link to show up in any of the main site menus. For example in my ejb-jar module pom.xml I have: org.apache.maven.plugins maven-surefire-report-plugin 2.4.2 src/test/config/testng.xml When site runs the surefire-reports.html file is created, but it's not listed as a link in the index.html file, as shown in the diagram in the docs: http://maven.apache.org/plugins/maven-surefire-report-plugin/usage.html Is there something I need to do to get it show up as a link as shown in the image? Thanks -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would really appreciate some feedback on this Maven2-EJB3/JPA example that I've posted, to make it better
I On Tue, Oct 14, 2008 at 2:35 PM, Martin Gainty <[EMAIL PROTECTED]> wrote: > would be nice if we could start at the top of Pikes Peak to look down on the > Spring vs EJB debate > Spring promotes the use of Factories and EJB doesnt Well, the both use DI to inject things, so maybe I'm missing that value of the Factories to which you speak. > Spring works well with all ORM methodologies including Hibernate and iBatis Yes, that is Spring's awesome strength... super flexible. +1 for Spring there, and I've been the biggest supporter of iBATIS for years (still am.) However, if your company is decided on using ORM and you are going to use JPA, whatever is underneath doesn't matter 'too' much - hibernate/toplink,etc. I don't see it a big deal using JBoss or Glassfish in that case and just 'go'. > EJB supports implementation of Local vs Remote access for stateful and > stateless beans > latest version of EJB supports Annotations to implement interfaces > more salient points? Yea, that's what is nice now, is setting up any kind of EJB is super easy. Also, if you are using a JEE container you get some other things out of the box like JMS as well without having to use third party jars to handle things. > > with regards to MVC who wins and for what reasons? Not sure what you mean there.. you mean MVC in regard to web apps? In that case, you can use anything you want. (I haven't used Seam and it seems overly complicated. I prefer simple Stripes for my web front ends. ) > is this as simple as EJB is good ? > and Spring is bad ? I don't think it's an either/or. I think they are BOTH good. However, here's my personal preference at this stage... (and this can change next week:) - if I need a simple CRUD app that is all self contained and isn't going to be a corporate behemoth...I'd use Rails. If it's going to be a large corporate application I currently lean towards JEE (EJB3). In my short endeavor with Spring/JPA/Tomcat, I found setting up Spring to work with JPA and Tomcat to be a pain. .. .had issues with the load time weaving and looking at the docs and googling on the setup for Tomcat was confusing. Plus I had to start looking over a Spring book - all for what gain? The only main benefit I found was that it was easier to test my Spring pojos. With Spring/Tomcat, I also had to start importing all kinds of different jars into my application lib and tomcat lib (aspectj jars, spring jars, etc.) Overall it was just more of a pain to me getting started. Again, I'm by no means against a Spring/JPA/Tomcat or Resin solution. I just disagree that things are now easier' with Spring vs using JEE5 (granted this used to not be the case. For those bashing JEE and EJB3 (not saying you are) do take a look at even the simple example I posted. Look at how little configuration there is. I'm not saying learning the spring setup is super hard... but I (and others) have had issues trying to get it to work with Tomcat. Sure it can work, but I was up and running in less time with EJB3 on JBoss (and I had the same experience with Glassfish also.) And yes, I am aware there will be some container specific files I'll need to modify (ie pool sizes, etc. But I don't find that too big a deal.. even on Tomcat or Resin there are files you could tweak.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would really appreciate some feedback on this Maven2-EJB3/JPA example that I've posted, to make it better
On Tue, Oct 14, 2008 at 1:00 PM, Rusty Wright <[EMAIL PROTECTED]> wrote: > I guess what I'm asking is, what's the difference between EJB3 and JPA? For > example, if I want to use JPA I could use Hibernate and Tomcat and use only > the JPA annotations. When you say EJB3 does that mean that you're using JPA > in a J2EE app server, or is there more to it than that? You are correct. However if you are going to do like you say and "Use JPA with Hibernate and Tomcat" you will also STILL need some sort of container to manage things which is where Spring comes in. You'll also want Spring to manage transactions (which you get for free with EJB3, etc) I don't want to start a whole Spring vs EJB3 war, but suffice it to say I found the setup much easier with EJB3. You can follow some of the 'war' so to speak if you look at some of the comments in this blog post http://java.dzone.com/articles/the-cost-springsource-enterpri Both a Spring/JPA/Hibernate solution and an EJB3/JPA/Hibernate solution will work and they both have some pros and cons. (For those catching this post out of context it started with some comments I was requesting in the maven setup for this tutorial I posted: http://www.learntechnology.net/content/ejb/maven-ejb3.jsp Any helpful changes are welcome, thanks.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would really appreciate some feedback on this Maven2-EJB3/JPA example that I've posted, to make it better
On Mon, Oct 13, 2008 at 6:26 PM, Rusty Wright <[EMAIL PROTECTED]> wrote: > I was wondering if you need to use JBoss? Couldn't you do it as a war > instead of an ear? Mine is an EJB3 example. (For a decent spring/jpa example, look at appfuse) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Would really appreciate some feedback on this Maven2-EJB3/JPA example that I've posted, to make it better
Thanks to those on this list helping me start to get a handle on Maven. I made my first attempt at a decent simple lesson that can work as an EJB3/JPA skeleton app that builds with Maven2. (There are some things out there but many of them are a bit outdated, or else they cover too much, or too little. I tried to get the core basics down in this demo that I wish I had when starting out.) I'd appreciate if some of you could at least look over the pom.xml files that you see posted: http://learntechnology.net/content/ejb/maven-ejb3.jsp I'm not sure I'm using provided and optional correctly (although the generate ear seems to look ok to me.) I'm obviously still a maven newb so any recommendations I'll kindly take to get it fixed up. Thanks -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[OT somewhat] commit modules separately or all under one project?
In a typical JEE project I have a parent module that my children all inherit from. My modules look like: parent ear ejb web jar My debate is how to best put this into version control? Do most of you commit the parent directory that holds all the submodules as 'one project' or do some of you like to commit each module separately? I'm leaning towards just checking in the whole parent directory as one project, since the modules are all so closely related. Although the jar file (Which is mostly util stuff can really be stand alone I suppose and in theory the ejb module could be used by another web project, but that's extremely unlikely. ) -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Best practice? Where to put app-server specific files (log4j.xml, datsource xml files, jboss-service.xml , etc.)
Thanks everyone. You all make good points. Typically, with our ant builds, we have a special task called "setup_jboss" that will deploy certain jboss specific files (after doing some substitutions - ie datsource setup for a dev db, etc.). It's obviously not run all the time, so I guess I could keep the seem thing within maven (just haven't used the ant tasks from within maven yet, but will look into that. On Mon, Oct 6, 2008 at 10:13 PM, Edelson, Justin < [EMAIL PROTECTED]> wrote: > We treat these JBoss configuration files as artifacts outside of the main > deployable (read: EAR file). The vast majority of our JBoss sites use the > same base server configuration, which includes the jboss-service.xml and > other files. jboss-service.xml uses system property placeholders for > environmental-specific bits. The system properties are defined in a separate > file and loaded into JBoss with the -P option. Each instance has its own > log4j.xml file and datasource xml files, but AFAIK, these could use property > placeholders as well if necessary. We version control all of these files > (obviously), but outside of the main application. > > The goal of this architecture was, as Bob says below, to use the same build > between dev, QA, and prod (although in reality, dev is usually a SNAPSHOT > build from CI) and to simplify new site creation by reusing the same base > server configuration. > > For more application-specific (vs. container-specific) stage-based > configuration, we use a combination of system properties (-Dstage=qa) and a > customized version of Spring internals. > > Justin Edelson > VP, Platform Engineering > MTV Networks Digital > > > > From: Bob Aiello [mailto:[EMAIL PROTECTED] > Sent: Mon 10/6/2008 9:00 PM > To: Maven Users List > Subject: Re: Best practice? Where to put app-server specific files > (log4j.xml, datsource xml files, jboss-service.xml , etc.) > > > > I believe that most people use the Ant plugin Assembly to parse the dev, > qa, > prod > environment files. I would suggest that you create them all during the > build. I have > seen some people put in the environment during the build and parse the > files > just for > that environment. This meant that they had to rebuild for dev, QA and Prod > (very > bad practice!). From a compliance point of view you do want your QA build > to be the same as the build that you promote into production (obviously you > have a deployment script to change over the environment files). > > What does everyone else do? > > Bob Aiello > Editor in Chief > CM Crossroads > www.cmcrossroads.com > http://www.linkedin.com/in/BobAiello > > > - Original Message - > From: "Rick" <[EMAIL PROTECTED]> > To: "Maven Users List" > Sent: Monday, October 06, 2008 6:25 PM > Subject: Best practice? Where to put app-server specific files (log4j.xml, > datsource xml files, jboss-service.xml , etc.) > > > > I'm working on a typical JEE application that will be deployed to JBoss. > > (JBoss5 if it matters.) Things are going. I have a pretty standard setup: > > > > Parent Module > > EJB-JAR Module > > JAR Module > > WEB Module > > EAR Module > > > > > > Currently, however, I'm manually having to deal with certain files that I > > need in JBoss: > > * datasource.xml files > > * jboss-service.xml > > * log4j.xml files > > There will probably be some others as well. > > > > What is the best way to deal with these files? Is the best practice to > > create a directory in the parent module or ear module and just create > some > > custom ant task to move them around where they need to go? I couldn't > find > > much about a jboss maven plugin to help with these tasks, so I'm assuming > > hooking in regular old ant is the way to go? > > > > I'll also want to have certain variables in those files replaced with > > variables from a profile (dev, test, prod) depending on what profile I'm > > running. I'll look into that as well, since I'm sure there are some docs > > on > > it, but are the any issues to be aware of since I'm guessing these aren't > > standard files that I'm dealing with so is using the replacement > > mechanism > > more difficult? > > > > Thanks > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- Rick
Best practice? Where to put app-server specific files (log4j.xml, datsource xml files, jboss-service.xml , etc.)
I'm working on a typical JEE application that will be deployed to JBoss. (JBoss5 if it matters.) Things are going. I have a pretty standard setup: Parent Module EJB-JAR Module JAR Module WEB Module EAR Module Currently, however, I'm manually having to deal with certain files that I need in JBoss: * datasource.xml files * jboss-service.xml * log4j.xml files There will probably be some others as well. What is the best way to deal with these files? Is the best practice to create a directory in the parent module or ear module and just create some custom ant task to move them around where they need to go? I couldn't find much about a jboss maven plugin to help with these tasks, so I'm assuming hooking in regular old ant is the way to go? I'll also want to have certain variables in those files replaced with variables from a profile (dev, test, prod) depending on what profile I'm running. I'll look into that as well, since I'm sure there are some docs on it, but are the any issues to be aware of since I'm guessing these aren't standard files that I'm dealing with so is using the replacement mechanism more difficult? Thanks
Ant task always tries to download one of my indirect dependencies
Every time I build my project using ant and the maven ant task, it tries to download a dependency: [artifact:dependencies] Downloading: org/hibernate/hibernate-commons- annotations/3.1.0.GA/hibernate-commons-annotations-3.1.0.GA.pom from main.repository This does not seem to exist. A newer version does exist, but the build process still seems to try to get this one. Since the task runs for all targets, even targets that don't need any dependencies, it slows down my workflow. How can I track down which of my direct dependencies is responsible? I've tried the verbose and debug output from ant, but I don't know how to interpret it. TIA, -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: no main or test directories created when using webapp archetype?
On Sun, Sep 28, 2008 at 5:11 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > The archetype is encouraging the best practice of putting the Java > code in a separate module. > > If you need the directories, you can create them. If this is > something you need often, you can create your own archetype. Ok interesting. Thanks Wendy. I didn't think of creating a separate module for the web-related java classes. Is this a common practice? I agree in separation of concerns, but that might be a bit much. In other words a servlet isn't going to be any good stand-alone (outside of the concept of web project) so it makes sense for me to have all that in a 'web module.' (Now if Eclipse supported multi-modules better I wouldn't' mind as much. I wish there was a way I could have a project in eclipse represented by the parent pom and then have all the sub modules beneath it. Back when I used IDEA, I think this was possible. Does NetBeans maybe support this?) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: no main or test directories created when using webapp archetype?
I should clarify.. 'main' is created.. just no java directory (or test) is created even when I provide the package declaration with -DpackageName=com.foobar On Sun, Sep 28, 2008 at 4:55 PM, Rick <[EMAIL PROTECTED]> wrote: > I'm confused... when I run the maven webapp archetype I only end up > with "resources" and "webapp" directories created.. no java/src/main > or java/src/test ? Shouldn't it make those directories for me? > > I tested with the archetype as shown here on the maven2 site: > > http://maven.apache.org/guides/mini/guide-webapp.html > > -- > Rick > -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
no main or test directories created when using webapp archetype?
I'm confused... when I run the maven webapp archetype I only end up with "resources" and "webapp" directories created.. no java/src/main or java/src/test ? Shouldn't it make those directories for me? I tested with the archetype as shown here on the maven2 site: http://maven.apache.org/guides/mini/guide-webapp.html -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using spring How to share jpa applicationContext.xml file with main src and test source?
I'm using the spring PetClinic as an example application to follow. I
have things building and working in maven2, but I'm having an issue
with the junit tests.
I'd like to be able to share one of my application-context.xml files
that is in my src/main/resources directory without having to keep it
in two places.
The application example I'm using for testing needs to call
AbstractJpaTests which requires one to override the getConfigPaths.
The problem is how do I get a handle outside of the test-classes in
which the tests are being run?
//the files below exist in my tests-classes directory, but I'd also
like to use the one in my standard classes directory as well.
// the / slash only seems to bring me to the base of my test-classes directory
@Override
protected String[] getConfigPaths() {
return new String[] {
"/applicationContext-jpa.xml",
"/applicationContext-entityManager.xml"
};
}
}
I've even tried adding an extra entry in my pom.xml for to use the
main resources as well but it didn't seem to help:
src/main/resources
**/*.xml
src/test/resources
**/*.xml
--
Rick
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbie: understanding how teams deal with version numbers on dependencies (Best practices)?
This isn't in reply to Stephen directly since so many people have made good points.. so thanks. I guess I'm still wonder what most people practice (or maybe not most but what's considered 'good'), in regard to the following situation... Project B will be putting out a new release based on features in Project A that Project B depends on. Project A works on their jar, runs some tests, runs things the best they can locally and then needs to have it deployed as part of the web app (Project B) so that some others in the company can look at it and examine the features etc. Later that day it's realized Project A jar needs to be modified again. So again a new version needs to go out to Project B in dev. This cycle sometimes happens quite rapidly towards the end of the development cycle. My question is "Are these quick releases typically release versions or snapshots?" To me, they seem to be snapshots, but I suppose in theory they could be considered releases with minor bug/enhancement features. It would be somewhat nice during this rapid development cycle that the version declaration in Project B would have to keep being changed. It seems like a decent(?) approach (possibly alluded to by what I've been piecing together in this thread), is that during this "busy dev time" it would be ok to change Project B's pom dependency on Project A to something like SNAPSHOT or latest release. THEN, after things settle down abit, someone makes the cool to clamp down on the dev version number dependency on Project B. I think this might be a safe approach during the time period when Project B is getting close to being 'ready' for its release to Test based on the work done by Project A. Like others have pointed out, it would then be a bad idea (I agree) to just leave the dev version of Project B to depend on snapshot of Project A. Thanks again for all the good comments so far. On Sun, Sep 14, 2008 at 10:07 AM, Stephen Connolly <[EMAIL PROTECTED]> wrote: > You might want to either have a look at the versions-maven-plugin or > consider version ranges. > > With the versions-maven-plugin you can update a property that locks down the > version you use automatically, which can be helpful in controlling when you > get an update in your dependency. > > If you just always want the latest, you can use version ranges. > > If you make it a rule to never deploy -SNAPSHOT artifacts you can then limit > the exposure to the bleeding edge by the very separation of developers. > > i.e. > > If I am working on A & B and I do an mvn install of A 1.0.5-SNAPSHOT and B > depends on A. > > versions-maven-plugin can be configured to see the 1.0.5-SNAPSHOT on my > machine and thus I can see both dev versions. > > You are only working on B, so you will only see 1.0.4 until 1.0.5 is > released. > > The same can be achieved with version ranges but I'm never quite sure how > ranges work with -SNAPSHOT's being the latest i.e. is [1.0.0,) going to > include 1.0.5-SNAPSHOT? > > -Stephen > > On Sun, Sep 14, 2008 at 2:41 PM, sverhagen <[EMAIL PROTECTED]> wrote: > >> >> >> Graham Leggett wrote: >> > >> > But by doing this, project B is saying "we accept that project A may >> > break at any time, and we accept this". >> > >> > ... >> > >> > There is no "right" answer as to when this should happen, this is up to >> > the development team. But it is down to a binary choice: be on the >> > snapshot bleeding edge and access changes quickly and accept that it >> > will break randomly and without warning, or depend on a release, and you >> > get stability and controlled change. >> > >> >> Our single organisational project has a large number of modules. While >> adding single features (during Agile sprints) we change stuff in multiple >> such modules. >> Having a snapshot dependency from A on B when making corresponding changes >> between the two, for a single feature, some would argue this to be true >> Continuous Integration (thus: a good thing). >> In our environment we're for the moment happy with that. B and A are >> released shortly after each other (in that order), no problem. >> In our environment the real problems occur when A has a dependency on C as >> well, and A and C are both involved in another, concurrent feature as well. >> We've not yet found a very satisfying procedure for that one... anyone? ;-) >> -- >> View this message in context: >> http://www.nabble.com/newbie%3A-understanding-how-teams-deal-with-version-numbers-on-dependencies-%28Best-practices%29--tp19473528p19480432.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbie: understanding how teams deal with version numbers on dependencies (Best practices)?
On Sat, Sep 13, 2008 at 4:39 PM, Graham Leggett <[EMAIL PROTECTED]> wrote: > In other words, use the maven-release-plugin to publish formal releases of > code, and make sure that project A never depends on a snapshot of project B > if you can possibly avoid it. Use proper version numbers. Here's what I'm confused at though. Project A builds a jar. It needs to be used in Project B. Ideally of course Project A should be tested in Project B locally, but in reality (unfortunately) the dev environment often becomes a more 'real' test. Typically the developers of Project A will have access to Project B, so can't they just set up the dev profile of Project B, to use the latest stable version? This way they won't have to constantly be changing the profile for Project B.. or is that a bad practice? Assuming some time goes by while they do more 'real life' stuff in dev and they like how things are. They could then change the version of the dependency of Project A to a set number and then check that updated pom/profile into version control. Are they any documents out there that explain some of these common best practices in company environments? The two books I mentioned 'touch' upon it but don't see give a lot of detail. Understanding this 'process' of how things should be done to me seems critical to have nailed down (even if there are different ways to do it, I'd like to be aware of the typical scenarios corporations use.) Thanks to all for the replies so far. -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven best practice for multi module projects and version control
I'm a bit confused on the best practice for working with maven projects within a version control system. For example assuming we have a company repository setup and we are working on EJB project (ear) with your standard components (war and a few jars). Do people typically set up a FooBar ear project and check that into version control including the parent pom.xml and sub modules as part of a FooBar project? Or is better to just check in the parent ear pom as part of a FooBar project that has nothing in it but the parent pom.xml, and then checkin all the modules separately into version control? Typically (using ant) I'd create an ear project and include the modules that are 'tightly tied' to this project, but move out other projects that can obviously be shared easily amongst other projects. I assume the seem logic would apply to maven2 projects? Just want to make sure I'm not missing a best practice before I get too deep down the maven2 path here. Thanks, -- Rick
Re: Simple question - but totally frustrated - best way to define internal repo - but easily not use this repo when not at work?
I'm still confused on why it wouldn't be a good idea to simply put the company repository info in a parent pom that all company projects would use? This seems a lot cleaner and easier to setup and maintain... 1) If it's in a parent pom and you need to change repository urls someone can update the parent pom and everyone should have it. If a settings.xml file is used and anything needs to change in it (internal repo urls), you have to contact every developer and tell them to change their settings.xml file to reflect the new changes. 2) avoids having to set up any of the things mentioned so far in this thread. (The simple 'mvn install' on their project will work without any other modifiications or activation profiles being set.) Of course the user will have to first checkout the inital parent project from version control, but this seems easier than having your team work with a settings.xml file. I'm new though, so maybe I'm missing a serious drawback to this approach? On Fri, Jun 6, 2008 at 4:24 AM, Timothy Reilly <[EMAIL PROTECTED]> wrote: > > Rick, > > A couple of other options > If you automatically map a drive when you connect to your company lan > you could activate the acme-company profile with a file activation. > > Or as Wayne says use your mvn script. > > For example on windows create %HOMEDRIVE%%HOMEPATH%\mavenrc_pre.bat file > to do something like: > > maven_pre.bat > > call ping -n 1 -w 400 my_pdc_hostname > if ERRORLEVEL > 0 GOTO end > MAVEN_CMD_LINE_ARGS="%MAVEN_CMD_LINE_ARGS% -Dcom.acme.onthenetwork=true > " > :end > > Then use property profile activators com.acme.onthenetwork and > !com.acme.onthenetwork > > ----- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Rick
Re: Simple question - but totally frustrated - best way to define internal repo - but easily not use this repo when not at work?
I'm still a bit confused though... can't I define my repository in a parent.pom ? Why isn't this the preferred approach? Would seem to make sense to me - users check out a parent project from cvs. Run mvn install, put the parent pom in their repo. All new projects use this parent pom definition where the company's internal repo is definied. Wouldn't this be easier? On Thu, Jun 5, 2008 at 11:43 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > The easiest would be to simply rename settings.xml to settings.x when > you get home. This assumes that you don't have any special settings > for your projects. But this would disable the artifactory repo. Or if > you're on an operating system with symbolic links, you could adjust > the link to settings.xml when you change locations. > > Another approach would involve creating copies of mvn.bat and > settings.xml and calling mvn-copy when you're home. You would also set > mvn-copy.bat up to append -s /path/to/settings-copy.xml to all calls > to mvn. > > Wayne > > On Thu, Jun 5, 2008 at 10:06 PM, Rick <[EMAIL PROTECTED]> wrote: > > I'm totally confused and could use some help... > > > > I have an internal company repo setup fine. Currently, following the > > artifcatory docs, I defined this repo in my mavenhome/conf/settings.xml > file > > such as: > > > > > >acme-company > > > > > >central > >http://urlip:8081/artifactory/repo > > > >false > > > > > > > > > > I can then set this profile to be active in the settings.xml file as well > > and all works fine. > > > > The problem is when I'm at home using this laptop I don't want to use > this > > profile! I just want plain jane vanilla iblio repo. > > > > I'm confused how to set up things to get what I want - projects using our > > company parent pom using the repositories as defined above, and any other > > projects to not use the profile as above. > > > > What I was 'thinking' I could so is just set up the repository definition > in > > my parent proejct pom.. but that didn't seem to work at all. To me this > > makes the most sense as users wouldn't even have to define anything in > their > > settings.xml file. I see no examples of this however and can't seem to > get > > ti to work. Assuming I keep this profile definition in my (and > unfortunately > > the whole team's local settings.xml file) how do I set up parent company > > profile to use it? If I keep it "alawys active" then it's always active > even > > when I'm not at work which seems to be a pain. > > > > Even if this kind of info shouldn't be in a parent pom, and should be in > the > > settings.xml file, how do I then easily set things up so that I can do > "mvn > > install" when I'm not at work and have it NOT try to connect to the > > acme-company profile? I'd prefer not to have a pass in a profile argument > on > > the command line, but I suppose if I have to, I'll do it. > > > > I'm thinking this is a common situation so I must be totally doing > something > > wrong, > > > > -- > > Rick > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Rick
Re: Simple question - but totally frustrated - best way to define internal repo - but easily not use this repo when not at work?
On Thu, Jun 5, 2008 at 11:43 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > Or if you're on an operating system with symbolic links, you could adjust > the link to settings.xml when you change locations. > Ok, thanks. I can do the above. -- Rick
Simple question - but totally frustrated - best way to define internal repo - but easily not use this repo when not at work?
I'm totally confused and could use some help... I have an internal company repo setup fine. Currently, following the artifcatory docs, I defined this repo in my mavenhome/conf/settings.xml file such as: acme-company central http://urlip:8081/artifactory/repo false I can then set this profile to be active in the settings.xml file as well and all works fine. The problem is when I'm at home using this laptop I don't want to use this profile! I just want plain jane vanilla iblio repo. I'm confused how to set up things to get what I want - projects using our company parent pom using the repositories as defined above, and any other projects to not use the profile as above. What I was 'thinking' I could so is just set up the repository definition in my parent proejct pom.. but that didn't seem to work at all. To me this makes the most sense as users wouldn't even have to define anything in their settings.xml file. I see no examples of this however and can't seem to get ti to work. Assuming I keep this profile definition in my (and unfortunately the whole team's local settings.xml file) how do I set up parent company profile to use it? If I keep it "alawys active" then it's always active even when I'm not at work which seems to be a pain. Even if this kind of info shouldn't be in a parent pom, and should be in the settings.xml file, how do I then easily set things up so that I can do "mvn install" when I'm not at work and have it NOT try to connect to the acme-company profile? I'd prefer not to have a pass in a profile argument on the command line, but I suppose if I have to, I'll do it. I'm thinking this is a common situation so I must be totally doing something wrong, -- Rick
Re: jboss maven ear support documentation (as mentioned on the ear plugin page)?
Thanks wayne. They also have some other properties that are Jboss specific. It would just be nice to see some examples, although I can probably figure it out from the brief list they give (shown below.) Just seems like at some point they had examples since the docs mention: "You can take a look at the examples for more information on the JBoss support." Not sure which example they are referring to though. The EAR plugin can generate the jboss-app.xml automatically. To do so, the 'jboss' element must be configured and takes the following child elements: * version: the targeted JBoss version to use, 3.2, 4 or 4.2 (the default is 4). * security-domain: the JNDI name of the security manager (JBoss 4 only) * unauthenticated-principal: the unauthenticated principal (JBoss 4 only) * loader-repository: the name of the UnifiedLoaderRepository MBean to use for the ear to provide ear level scoping of classes deployed in the ear * jmx-name: the object name of the ear mbean. * module-order: specify the order in which the modules specified in the application.xml file gets loaded (JBoss 4.2 only) * data-sources: specify the desired data source(s) to add into the jboss-app.xml, usage is as follows: On Sun, May 18, 2008 at 11:58 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > I didn't write the documentation of the EAR module so I can't be > certain, but I would assume this is a reference to the sarModule and > harModule sections in the Configuration/EAR Modules page: > http://maven.apache.org/plugins/maven-ear-plugin/modules.html#sarModule > http://maven.apache.org/plugins/maven-ear-plugin/modules.html#harModule > > Wayne > > On Sun, May 18, 2008 at 10:02 PM, Rick <[EMAIL PROTECTED]> wrote: >> At the bottom of this page >> http://maven.apache.org/plugins/maven-ear-plugin/usage.html >> it mentions >> >> "Hibernate archives (HAR) and Service archives (SAR) will be >> recognized automatically and added the the jboss-app.xml file. >> You can take a look at the examples for more information on the JBoss >> support." >> >> I'm weary of googling. Can someone point me to where these "examples" >> are "on the JBoss support." >> >> TIA >> >> -- >> Rick >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jboss maven ear support documentation (as mentioned on the ear plugin page)?
At the bottom of this page http://maven.apache.org/plugins/maven-ear-plugin/usage.html it mentions "Hibernate archives (HAR) and Service archives (SAR) will be recognized automatically and added the the jboss-app.xml file. You can take a look at the examples for more information on the JBoss support." I'm weary of googling. Can someone point me to where these "examples" are "on the JBoss support." TIA -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: artifactory and snapshots vs releases
On Sat, May 10, 2008 at 1:19 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Fri, May 9, 2008 at 7:30 AM, Rick <[EMAIL PROTECTED]> wrote: > >> Another hopefully quick one... The better builds guide mentions about >> filenames being used with timestamps appended etc, but yet whenever I >> do mvn deploy, I never see that timestamp either in my local m2 repo >> or in my corporate rep snapshots dir, It only ever has the version as >> I've declared in the pom version for the project. > > What is an example of a version number you're using? > > If your version number ends in -SNAPSHOT, and you haven't set > uniqueVersion=false in distributionManagement, then you should see > timestamped files in the remote snapshotRepository after you deploy. me == moron (mostly:) I 'think' everything is ok. I stated a major falsehood above.. in my local repo things are fine - I apologize I don't know what I was looking at to assume it wasn't working there (maybe I was an idiot and since I was working with Artificatory all day I just quickly saw 1.0-SNAPSHOT and assumed it was a file and not dir to traverse - regardless, I was an idiot there.) However, it is Artificatory I was really confused, since In Artificatory I'll only see something like "1.0-SNAPSHOT.jar" listed.. but in the maven-metadata.xml you will see the versioning change when you deploy new ones. I'm assuming that's behaving as normal? (I know this isn't an Artificatory list, but was just curious.) I did see this in their FAQ: Why do you strongly recommend against deploying unique snapshots? Because doing so normally promotes an unmanageable build environment. In practice, unique snapshots are never tracked for the real changes they carry: the snapshot's final name is not human deterministic and its "meaning" is normally obscure to developers since, by itself, it has no relation to the source it has been compiled against. Moreover, many times snapshots in a multi-module environment are dependent on other snapshots, so you would have to reconstruct by hand a cryptic dependency chain just to get back to a version you believe is stable. Often, the identification process of such a version is, by itself, obscure and is based on common inputs such as "yesterday before lunchtime everything worked" Therefore, it is highly preferable to use non-unique snapshots in development and, when needing, go back to a stable non-snapshot version by reconstructing one from a specific revision/tag in the VCS, where the meaning of the artifact can be easily tracked. It is advised to have the artifact itself embed the revision/tag (as part of its name or internally) for clear and visible revision tracking. -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
any ideas what I did wrong that was fixed by me deleting stuff from local repo?
Ok, I've been going crazy wondering why my parent pom that I checked
into my organization's repo (using Artifactory) wasn't working
correctly when I tried to use it one of my projects using the parent
directive in my project's pom. I kept getting an error about not
having "pom" declared as the package type so I changed in the parent
pom to use "pom" as the package type. However, when I kept trying to
use mvn {anything} in my project I tried all kinds of things wondering
what was going wrong since when I created a foobar project using a
similar construct it was working fine. On a whim I then decided to
blow out my directory in m2 and then everything was fine when I did
mvn deploy.
--
Rick
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: artifactory and snapshots vs releases
On Thu, May 8, 2008 at 11:56 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Thu, May 8, 2008 at 8:45 PM, Rick <[EMAIL PROTECTED]> wrote: > > If you have both a and a , Maven will > choose based on whether the version number ends in -SNAPSHOT. Magic. > :) See > http://maven.apache.org/ref/2.0.9/maven-model/maven.html#class_distributionManagement Thanks again Wendy. Another hopefully quick one... The better builds guide mentions about filenames being used with timestamps appended etc, but yet whenever I do mvn deploy, I never see that timestamp either in my local m2 repo or in my corporate rep snapshots dir, It only ever has the version as I've declared in the pom version for the project. I never see filenames being created as described below, so I'm wondering if I have things set up incorrectly: You'll see that it is treated differently than when it was installed in the local repository. The filename that is used is similar to proficio-api-1.0-20060211.131114-1.jar. In this case, the version used is the time that it was deployed (in the UTC timezone) and the build number. If you were to deploy again, the time stamp would change and the build number would increment to 2. This technique allows you to continue using the latest version by declaring a dependency on 1.0- SNAPSHOT, or to lock down a stable version by declaring the dependency version to be the specific equivalent such as 1.0-20060211.131114-1. While this is not usually the case, locking the version in this way may be important if there are recent changes to the repository that need to be ignored temporarily. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
artifactory and snapshots vs releases
Sorry if this is covered somewhere but I've been looking at "better builds with maven" guide, the website, and the Artifactory website but I'm a bit confused on a few things (since chapter 7 is a bit confusing.) Currently my internal repository is set up using Artifactory and it has a "libs-snapshots" and "lib-releases" - what do I need to do to setup my deploys so that I can also deploy release versions to the repo and not just snaphots. Obviously I assume I first label the version number in the POM or is that something handled automatically?, then what is the best practice to toggle between the two - snapshot builds to the repo vs releases? Maybe I'm just not setting things up correctly. Currently I have this defined in my project's pom.xml: I have in my project pom: snapshots dav:http://internalURL:8081/artifactory/libs-snapshots and the webdav wagon definition is set and the deploy works for snaphots when I type "mvn deploy" (I also declared my username and password for 'snapshots' in my m2_home/conf/settings.xml - not sure if that's the best place?) Anyway if I want to deploy a release it seems like I have to change the id name to "internal" and of course change the url from libs-snapshots to libs-releases. There must be a better way to do this whichI'm assuming involves the release plugin somehow? But in chapter 7 of the better builds guide it doesn't really mention about releasing to the a releases directory in Artificatory (which I wouldn't expect it to since the guide is generic, but I'm confused what to do.) Also, is it standard to put that distributionManagement definition in the project pom.xml? I would think that would be something you'd share amongst all your projects so maybe it should go somewhere in my .m2 settings? Lastly, just out of curiosity why aren't these plugins like the maven-compile and release part of the archetype or at least stubbed out in the generation from the archetype? Seems like they'd almost always be used? Thanks again for the help. -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: site is very confusing for beginners - how to get list of archetypes - link on faq is broken
Awesome. thanks guys. On Thu, May 8, 2008 at 10:12 AM, Chad La Joie <[EMAIL PROTECTED]> wrote: > You might want to start here: > > http://www.sonatype.com/book/ > > I tried learning Maven from the website as well and found it nearly > impossible. I don't use the site as anything more than a reference manual > for plugin options. > > > > Rick wrote: > > > I'm really struggling with the way the maven2 site is organized. > > > > I'm on the getting started guide > > http://maven.apache.org/guides/getting-started/index.html > > > > I get to the point where it mentions "How do I make my first Maven > > project" and it talks about Archetypes. I figured I'd like to see what > > archetypes I can use since the one it shows seems to make a jar (and > > I'm curious about ears and wars as well.) So I lick on the link right > > there in the description "Introduction to Archetypes" and I'm brought > > to this page which says very little. > > > http://maven.apache.org/guides/introduction/introduction-to-archetypes.html > > > > So I figured I'll browse the site and try to find out how I can find a > > list of archetypes. Now where would you go on the site to find this? > > I'd think this would be important information? > > > > I've been looking everywhere. I shouldn't have to go to a FAQ for this > > important information, but more on that later. So I'm not going to the > > FAQ and searching all the menu items. By accident I happen to look at > > plugins and I noticed an "archetype" plugin so I click on that and get > > some decent info but still no explanation of what archetypes are > > available. > > > > Eventually I give up and figure I'll browse the FAQ. There happens to > > be a link "How do I get a list of archetypes" but when I click on it I > > get a 404 > http://svn.apache.org/viewvc/maven/archetype/trunk/maven-archetypes > > > > A frustrating start for me. I hope it gets better. > > > > > > -- > SWITCH > Serving Swiss Universities > -- > Chad La Joie, Software Engineer, Security > Werdstrasse 2, P.O. Box, 8021 Zürich, Switzerland > phone +41 44 268 15 75, fax +41 44 268 15 68 > [EMAIL PROTECTED], http://www.switch.ch > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
