tomcat6:list - minimum requirements to run
Hi all, I have some difficulty to understand how to use the plugin below to do a simple $ mvn tomcat6:list pluginManagement plugins plugin groupIdorg.apache.tomcat.maven/groupId artifactIdtomcat6-maven-plugin/artifactId version2.1/version /plugin plugin groupIdorg.apache.tomcat.maven/groupId artifactIdtomcat7-maven-plugin/artifactId version2.1/version /plugin /plugins /pluginManagement I have integrated this plugin into my main pom.xml of the multi modul project svnkit, of which svnkit-dav has a war file on board/generated. Not an executable war file (what is that?) but just a war to be deployed to a running tomcat AS. As a starter, and not involfing any war file, I like just to know under which circumstances I can use $ mvn tomcat6:list Josef - I have read the documentation and I am not clear what to do to get an embedded tomcat OR how to use it.
AW: Is there any generic Maven code generator?
A code generator needs input. Hence some generic formal language is used to specify the input to the genric code generator? UML? Visualization of a generic language could mean - speak UML, UML is a reality today. UML modells can says much more then 1000 words? Hence I opt for better integration of modelling tools with maven. Also roundtrip engineering is a must. Enterprise Architect (EA) is able to generate code from UML and other diagrams for many target compiler and it helps you to have code, modell and documentation in sync. And EA can be feed with code and generates your diagramms. A task which only ends when the modells become to complex. Maven is much about geting and nailing dependent components together. If maven finds the dependecies, a tool like EA could use input to draw i.e. the component diagram, maybe a maven plugin can pave the way for EA. Other whise, in my mind, there are far too many tools around and I get to often the feeling that each time a problem developes, folk starts to seek a tool to avoid some brain work. So if one knows in which aspects maven poms could be used toward EA to get ceratin artiacs visualized for better understanding, that would be almost a very good step into proper direction. Josef -Ursprüngliche Nachricht- Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] Gesendet: Mittwoch, 27. Februar 2013 12:31 An: users@maven.apache.org Betreff: Is there any generic Maven code generator? I just posted this to Stackoverflow, but after posting I realized, that I should have come here first :-( I am currently working on a project, that makes intense usage of code generation for various purposes. One generator generates SQL scripts from jpa entities. Another generates DTOs from pojos, another generates the JPA2.0 meta model, jet another generates some xml and schema files based on Java classes ... each generator works completely different needs to be configured differently. My question now is ... is there any generic maven code generator plugin out there with the following attributes: * Creates a pojo model of a Java class (Names, Properties, Annotation, Methods ...) * Uses templates for defining the output that uses the pojo model to generate any output. * Allows me to specify multiple templates for one class * Allows me to generate code and resources * Allows me to generate a base class to target/generated-sources and a dummy implementation to src/main/java which simply extends the base class (If the dummy class in src/main/java exists, nothing happens, if it doesn't it generates such a dummy class. This code is checked in to the SCM and allows extending the generated classes manually) I am using the Flexmojos GraniteDS plugin for generating my ActionScript model code, but it's pretty specialized for that particular purpose. I think such a generic generator would make things a lot easier ... is there something like that available out there, or do I have to start implementing it myself? Chris - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Git Repositories
Unfortunately the link below does not show anything to read in English ... Josef -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Donnerstag, 21. Februar 2013 15:54 An: Maven Users List Betreff: Re: Git Repositories You would imaging somewhere like: http://docs.codehaus.org/display/MAVENUSER/Maven+Best+Practice+Guide But documentation of best practices is something we are weak on... We are great at telling people what isn't best practice... not so great at documenting that stuff ;-) A wise user would add a child page to that wiki page, and perhaps remove the placeholder text! (Given that the linked page is the *user* contributed wiki) On 21 February 2013 14:47, Eric Kolotyluk eric.koloty...@gmail.com wrote: OK, I think I've got it. The answer depends more on what artifacts will always have the same version number, than how many artifacts there are. In a nutshell, one repository for the entire multi-module project is best, where all the artifacts keep their versions in sync with the parent pom. But, if you have to support artifacts with versions out of sync, then the out of sync versions need their own repositories. More work to manage, but sometimes necessary. Thanks for the clarification. Where would I find these kinds of best practices written down? Cheers, Eric On 2013-02-21 1:25 AM, Stephen Connolly wrote: One git repository for everything that is always released together and has the same version number. If there are some sub-modules that have a different lifecycle, they should be in a separate git repository. That may force you to split the other modules you thought were always released as one into two other git repositories. Lather, rince, repeat On 21 February 2013 07:16, Eric Kolotyluk eric.koloty...@gmail.com wrote: I'm a git newbie and I was wondering if there are any best practices around using maven with git people could point me to? For example, if I have a project with several artifacts/modules net.kolotyluk.coolapp - client.jar - common.jar - service.jar is it better to create a single repository net.kolotyluk.coolapp for the project, or several repositories such as net.kolotyluk.coolapp.client net.kolotyluk.coolapp.common and net.kolotyluk.coolapp.service for each artifact? Cheers, Eric --** --**- To unsubscribe, e-mail: users-unsubscribe@maven.**apac**he.orghttp://apache.org users-unsubscribe@**maven.apache.orgusers-unsubscribe@maven.apache .org For additional commands, e-mail: users-h...@maven.apache.org --**--**-- --- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.or g 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
AW: maven jax-ws and jdk7. help please
I fully support that! I had a nightmare with Axis2-1.6.2 and JDK1.6.0_30 when it comes to use jax-ws and jaxb with ALLOWED ANNOTATIONS; Axis-1.6.2 has a jax-ws interface which knows about 4 args to some annotations, so the compiler had absolute no problem. But then JDK 1.6.0_30 RT.jar has only an implementation for 3 args to be set on a annotation class, hence calling through the interface the 4 arg to be set, returnd a class not found exception. The cure was to endorse from JDK 1.7 into JDK1.6.0_30/jre/lib/endorsed the proper jar files; This works now for us very well for Vista and OpenVMS Josef -Ursprüngliche Nachricht- Von: Jörg Schaible [mailto:joerg.schai...@scalaris.com] Gesendet: Montag, 28. Januar 2013 10:37 An: users@maven.apache.org Betreff: Re: maven jax-ws and jdk7. help please laudio.info wrote: Thanks I have seen that, using the same java code and the same configuration, the problem appears if i use the jdk7. Using the jdk there is not problem The jaxws plugin does not respect the compiler settings for source/target. On top of it, the exception has additional info since JDK 7, so any code that uses reflection to map an exception class to something else, will be affected by the different Java runtime. AFAICS JAXB is such a tool. Nothing of this has to do with Maven directly though. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: building from latest trunk
Hi Thomas thanks for the support. your svn commands below work to some degree! bash$ jsvn info http://github.com/apache/maven-3/trunk 0: /DKA3/java_60/bin/java 1: -Dsun.io.useCanonCaches=false 2: -Djava.util.logging.config.file=/DKA3/stadelma/svnkit-1.3.5.7406/logging.properties 3: -cp 4: /DKA3/stadelma/svnkit-1.3.5.7406/svnkit.jar:/DKA3/stadelma/svnkit-1.3.5.7406/svnkit-cli.jar:/DKA3/stadelma/svnkit-1.3.5.7406/tril ead.jar:/DKA3/stadelma/svnkit-1.3.5.7406/jna.jar:/DKA3/stadelma/svnkit-1.3.5.7406/sqljet.1.0.4.jar:/DKA3/stadelma/svnkit-1.3.5.7406/ antlr-runtime-3.1.3.jar 5: org.tmatesoft.svn.cli.svn.SVN 6: info 7: http://github.com/apache/maven-3/trunk svn: Repository moved permanently to '/apache/maven-3/trunk'; please relocate svn: OPTIONS request failed on '/apache/maven-3/trunk' so this fails with http:// bash$ jsvn info https//github.com/apache/maven-3/trunk 0: /DKA3/java_60/bin/java 1: -Dsun.io.useCanonCaches=false 2: -Djava.util.logging.config.file=/DKA3/stadelma/svnkit-1.3.5.7406/logging.properties 3: -cp 4: /DKA3/stadelma/svnkit-1.3.5.7406/svnkit.jar:/DKA3/stadelma/svnkit-1.3.5.7406/svnkit-cli.jar:/DKA3/stadelma/svnkit-1.3.5.7406/tril ead.jar:/DKA3/stadelma/svnkit-1.3.5.7406/jna.jar:/DKA3/stadelma/svnkit-1.3.5.7406/sqljet.1.0.4.jar:/DKA3/stadelma/svnkit-1.3.5.7406/ antlr-runtime-3.1.3.jar 5: org.tmatesoft.svn.cli.svn.SVN 6: info 7: https://github.com/apache/maven-3/trunk Path: trunk URL: https://github.com/apache/maven-3/trunk Repository Root: https://github.com/apache/maven-3 Repository UUID: 5bc8a53d-41ec-bbf6-b094-ce57b7db7bff Revision: 9404 Node Kind: directory Last Changed Author: no.author Last Changed Rev: 9312 Last Changed Date: 2003-09-01 18:05:50 +0200 (Mon, 01 Sep 2003) so this works with https:// bash$ jsvn co https://github.com/apache/maven-3/trunk 0: /DKA3/java_60/bin/java 1: -Dsun.io.useCanonCaches=false 2: -Djava.util.logging.config.file=/DKA3/stadelma/svnkit-1.3.5.7406/logging.properties 3: -cp 4: /DKA3/stadelma/svnkit-1.3.5.7406/svnkit.jar:/DKA3/stadelma/svnkit-1.3.5.7406/svnkit-cli.jar:/DKA3/stadelma/svnkit-1.3.5.7406/tril ead.jar:/DKA3/stadelma/svnkit-1.3.5.7406/jna.jar:/DKA3/stadelma/svnkit-1.3.5.7406/sqljet.1.0.4.jar:/DKA3/stadelma/svnkit-1.3.5.7406/ antlr-runtime-3.1.3.jar 5: org.tmatesoft.svn.cli.svn.SVN 6: co 7: https://github.com/apache/maven-3/trunk Atrunk/.gitattributes Atrunk/.gitignore Atrunk/README.bootstrap.txt Atrunk/README.md Atrunk/README.txt ... ... after 10 minutes of downloading, at ... ... Atrunk/maven-core/src/site/apt/scripting-support/marmalade-support.apt Atrunk/maven-core/src/site/resources Atrunk/maven-core/src/site/resources/design A trunk/maven-core/src/site/resources/design/2.1-lifecycle-refactor-class-diagram.png svn: SSL peer shut down incorrectly svn: REPORT request failed on '/apache/maven-3/!svn/vcc/default' bash$ so this fails with https - but succeeded yesterday for an jsvn up with http, through our firewall. It started to work very nicely on openvms using jsvn (as we have no svn (c/c++ compiled version on OpenVMS we use jsvn)). Migrating also means to me bash$ rm -rf trunk/ deleting all old sources and only then does bash$ jsvn co https://github.com/apache-maven-3/trunk work. and BTW: it does only work for the https but not for the http protocol. Is this by intention of the administrator? So as long as I can jsvn co/up this git repo using jsvn from OpenVMS through the https protocol is all fine for me. BUT svn: SSL peer shutdown incorrectly kicks me out of the loop. Is it my JSVN-Client or the https://github.com Repository-Server which fails or the FW in between? what makes my jsvn fail after thousand of files are downloaded using jsvn co https://...? Josef -Ursprüngliche Nachricht- Von: Thomas Broyer [mailto:t.bro...@gmail.com] Gesendet: Montag, 7. Januar 2013 16:38 An: Maven Users List Betreff: Re: building from latest trunk On Mon, Jan 7, 2013 at 4:20 PM, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Does that mean that I can still use jsvn to update my maven trunk sources but this time just from a different (git-hub)repository found under a different url? AIUI, yes. if yes: what is the correct svn checkout command to use? Try svn co https://github.com/apache/maven-3/trunk; and if it doesn't work, then try the 2-step svn co --depth empty https://github.com/apache/maven-3; then svn up trunk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: building from latest trunk
Thomas I take TortoiseGit on Windows Vista to clone from maven-3/trunk/ but it seams that none of the git supported protocols are supported there. Or do I something wrong, even when I have used TortoiseGit for clonig a few times very well.? --- 1. attempt using https --- git.exe clone --recursive --progress -v git clone https://github.com/apache/maven-3/trunk; E:\hub\maven-3\trunk Cloning into 'E:\hub\maven-3\trunk'... fatal: I don't handle protocol 'git clone https' git did not exit cleanly (exit code 128) (234 ms @ 08.01.2013 12:06:37) --- 2. attempt using http --- git.exe clone --progress -v git clone http://github.com/apache/maven-3/trunk; E:\hub\maven-3\trunk Cloning into 'E:\hub\maven-3\trunk'... fatal: I don't handle protocol 'git clone http' git did not exit cleanly (exit code 128) (1591 ms @ 08.01.2013 12:08:01) --- 3. attempt using https --- git.exe clone --progress -v git clone git://github.com/apache/maven-3/trunk E:\hub\maven-3\trunk Cloning into 'E:\hub\maven-3\trunk'... fatal: I don't handle protocol 'git clone git' git did not exit cleanly (exit code 128) (359 ms @ 08.01.2013 12:08:46) over all using bash$ jsvn --depth infinity https://github.com/apache/maven-3/trunk/apache-maven apache-maven on a one by one basis succeeded, but checking out the whole maven-3/trunk/ at once always fails. Doing the same using jsvn to a axis2 svn repository for the whole axis2 trunk succeeded without any problem. Difference: axis2 jsvn uses http while maven-3 used https. Can that make a difference or is the github.com server shaky or do I run into a limit setup server side or client side at the fire wall? (see my previous e-mail for that) Please: Would potentially somebody explain what works up-to-day with this github.com repository in regard to apache/maven/trunk and what does not work? Josef -Ursprüngliche Nachricht- Von: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch] Gesendet: Dienstag, 8. Januar 2013 10:45 An: Maven Users List Betreff: AW: building from latest trunk Hi Thomas thanks for the support. your svn commands below work to some degree! bash$ jsvn info http://github.com/apache/maven-3/trunk 0: /DKA3/java_60/bin/java 1: -Dsun.io.useCanonCaches=false 2: -Djava.util.logging.config.file=/DKA3/stadelma/svnkit-1.3.5.7406/logging.properties 3: -cp 4: /DKA3/stadelma/svnkit-1.3.5.7406/svnkit.jar:/DKA3/stadelma/svnkit-1.3.5.7406/svnkit-cli.jar:/DKA3/stadelma/svnkit-1.3.5.7406/tril ead.jar:/DKA3/stadelma/svnkit-1.3.5.7406/jna.jar:/DKA3/stadelma/svnkit-1.3.5.7406/sqljet.1.0.4.jar:/DKA3/stadelma/svnkit-1.3.5.7406/ antlr-runtime-3.1.3.jar 5: org.tmatesoft.svn.cli.svn.SVN 6: info 7: http://github.com/apache/maven-3/trunk svn: Repository moved permanently to '/apache/maven-3/trunk'; please relocate svn: OPTIONS request failed on '/apache/maven-3/trunk' so this fails with http:// bash$ jsvn info https//github.com/apache/maven-3/trunk 0: /DKA3/java_60/bin/java 1: -Dsun.io.useCanonCaches=false 2: -Djava.util.logging.config.file=/DKA3/stadelma/svnkit-1.3.5.7406/logging.properties 3: -cp 4: /DKA3/stadelma/svnkit-1.3.5.7406/svnkit.jar:/DKA3/stadelma/svnkit-1.3.5.7406/svnkit-cli.jar:/DKA3/stadelma/svnkit-1.3.5.7406/tril ead.jar:/DKA3/stadelma/svnkit-1.3.5.7406/jna.jar:/DKA3/stadelma/svnkit-1.3.5.7406/sqljet.1.0.4.jar:/DKA3/stadelma/svnkit-1.3.5.7406/ antlr-runtime-3.1.3.jar 5: org.tmatesoft.svn.cli.svn.SVN 6: info 7: https://github.com/apache/maven-3/trunk Path: trunk URL: https://github.com/apache/maven-3/trunk Repository Root: https://github.com/apache/maven-3 Repository UUID: 5bc8a53d-41ec-bbf6-b094-ce57b7db7bff Revision: 9404 Node Kind: directory Last Changed Author: no.author Last Changed Rev: 9312 Last Changed Date: 2003-09-01 18:05:50 +0200 (Mon, 01 Sep 2003) so this works with https:// bash$ jsvn co https://github.com/apache/maven-3/trunk 0: /DKA3/java_60/bin/java 1: -Dsun.io.useCanonCaches=false 2: -Djava.util.logging.config.file=/DKA3/stadelma/svnkit-1.3.5.7406/logging.properties 3: -cp 4: /DKA3/stadelma/svnkit-1.3.5.7406/svnkit.jar:/DKA3/stadelma/svnkit-1.3.5.7406/svnkit-cli.jar:/DKA3/stadelma/svnkit-1.3.5.7406/tril ead.jar:/DKA3/stadelma/svnkit-1.3.5.7406/jna.jar:/DKA3/stadelma/svnkit-1.3.5.7406/sqljet.1.0.4.jar:/DKA3/stadelma/svnkit-1.3.5.7406/ antlr-runtime-3.1.3.jar 5: org.tmatesoft.svn.cli.svn.SVN 6: co 7: https://github.com/apache/maven-3/trunk Atrunk/.gitattributes Atrunk/.gitignore Atrunk/README.bootstrap.txt Atrunk/README.md Atrunk/README.txt ... ... after 10 minutes of downloading, at ... ... Atrunk/maven-core/src/site/apt/scripting-support/marmalade-support.apt Atrunk/maven-core/src/site/resources Atrunk/maven-core/src/site/resources/design A trunk/maven-core/src/site/resources/design/2.1-lifecycle-refactor-class-diagram.png svn: SSL peer shut down incorrectly svn: REPORT request failed on '/apache/maven-3/!svn/vcc/default' bash$ so this fails with https - but succeeded yesterday
AW: building from latest trunk
Very much thanks Thomas, But when I use the git://... protocol I cannot pass our fire wall because I think it is not forseen by git to pass credentials to a proxy server when the git protocol is used. within my .gitconfig I have set a http.proxy as http://c770817:mypasw...@proxyserver.com:8080 still missing the http.auth.preference=Basic attribute which stops our proxy server from negotiating but enforces it to start a basic authentication session with username and password. That works for http://... to many git-repo-server. So git://.. is not passing credentials to proxy server http:/.. passing proxy credentials is not supported at your side of the pond https://.. works but I was kicked out many times from ssl peer and have to jsvn co in junks, one directory after one directory of the trunk. This is very annoying. Josef -Ursprüngliche Nachricht- Von: Thomas Broyer [mailto:t.bro...@gmail.com] Gesendet: Dienstag, 8. Januar 2013 12:29 An: Maven Users List Betreff: Re: building from latest trunk On Tue, Jan 8, 2013 at 12:16 PM, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Thomas I take TortoiseGit on Windows Vista to clone from maven-3/trunk/ but it seams that none of the git supported protocols are supported there. No, the Git repo is at https://github.com/apache/maven-3.git But if you're using Git, then you can use the repo from Apache: git://git.apache.org/maven-3.git See http://git.apache.org/ (search for maven-3 on the page) and https://github.com/apache/maven-3 (clone URLs are given at the top of the page) -- Thomas Broyer /tɔ.ma.bʁwa.je/ - 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
AW: building from latest trunk
thank you very much Kristian that explains many thing. BTW: do you know if with git.exe the proxy credentials can be passed using the git://... protocol. This just a general question. So far from egit/jgit forum nothing to a simple question. Josef -Ursprüngliche Nachricht- Von: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] Im Auftrag von Kristian Rosenvold Gesendet: Dienstag, 8. Januar 2013 12:34 An: Maven Users List Betreff: Re: building from latest trunk We are re-arranging the mirroring layout on github, and the current git repos on github seem to be in a state of flux. Hopefully this smoothens out soon. I would recommend using https://git-wip-us.apache.org/repos/asf/maven.git until they shape up. This is the authorative master repo as well ! Kristian 2013/1/8 Thomas Broyer t.bro...@gmail.com: On Tue, Jan 8, 2013 at 12:16 PM, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Thomas I take TortoiseGit on Windows Vista to clone from maven-3/trunk/ but it seams that none of the git supported protocols are supported there. No, the Git repo is at https://github.com/apache/maven-3.git But if you're using Git, then you can use the repo from Apache: git://git.apache.org/maven-3.git See http://git.apache.org/ (search for maven-3 on the page) and https://github.com/apache/maven-3 (clone URLs are given at the top of the page) -- Thomas Broyer /tɔ.ma.bʁwa.je/ - 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
AW: building from latest trunk
This morning I finished updating my sources from the https://github.com/apache/maven-3/trunk repository. version 9404 is checked out. I have then rebuilt bash$ mvn clean install on OpenVMS with all success. The files mvn and mvnDebug mentioned below where also not included in the tar.gz but they are provided in the sources. This files are required with each unix release in the tar.gz file. And we need it on OpenVMS as maven runs under bash$ a Unix shell. Any idea why this files are not delivered any longer? or is this now a platform dependent issue? i.e. if OpenVMS do not include them??? Josef -Ursprüngliche Nachricht- Von: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch] Gesendet: Montag, 7. Januar 2013 14:47 An: Maven Users List Betreff: building from latest trunk Hi, I did openVMS bash$ svn co trunk bash$ mvn clean install bash$ all the build steps indicates SUCCESS; lets do a cd and inspect bash$ cd /dka3/.m2/repository/org/apache/maven/apache-maven/3.1-SNAPSHOT bash$ ls -l total 10205 -rwxr-x--- 1 STADELMA 129 5206734 Jan 7 12:12 apache-maven-3.1-SNAPSHOT-bin.tar.gz -rwxr-x--- 1 STADELMA 129 5234859 Jan 7 12:12 apache-maven-3.1-SNAPSHOT-bin.zip -rwxr-x--- 1 STADELMA 129 1113 Jan 7 12:12 apache-maven-3.1-SNAPSHOT-site.xml -rwxr-x--- 1 STADELMA 129 5569 Jan 7 12:12 apache-maven-3.1-SNAPSHOT.pom -rwxr-x--- 1 STADELMA 129 316 Jan 7 12:12 maven-metadata-local.xml openVMS copy apache-maven-3.1-SNAPSHOT-bin.tar.gz sys$login: apache-maven-3.1-SNAPSHOT-bin.tar.gz openVMS set def sys$login openVMSbash bash$ gnutar -vzxf apache-maven-3.1-SNAPSHOT-bin.tar.gz and I get the just built maven-3.1-snapshot installed BUT Now I am facing one problem I've never seen before. *** bash$ cd $HOME/apache-maven-3.1-SNAPSHOT bash$ ls -l total 13 -rwxr-x--- 1 STADELMA 129 230 Jan 7 12:12 m2.conf -rwxr-x--- 1 STADELMA 129 6152 Jan 7 12:12 mvn.bat -rwxr-x--- 1 STADELMA 129 6306 Jan 7 12:12 mvnDebug.bat I am facing the following problem! why was mvn and mvnDebug (the shell files) not packaged into my target *tar.gz file? lets look at the sources openVMS set def DKA3:[SW-PROJEKTE.asf.maven.maven-3.trunk.apache-maven.src.bin] bash$ ls -l total 31 drwxr-x--- 1 STADELMA 129 512 Oct 30 16:27 _svn -rwxr-x--- 1 STADELMA 129 222 Oct 30 16:27 m2.conf -rwxr-x--- 1 STADELMA 129 5807 Jan 7 11:28 mvn -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvn.bat -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvnDebug -rwxr-x--- 1 STADELMA 129 6106 Jan 7 11:28 mvnDebug.bat -rwxr-x--- 1 STADELMA 129 6115 Jan 7 11:28 mvnyjp bash$ all there, just not packaged with my tar.gz and maybe .zip file any hints welcome Josef - 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
building from latest trunk
Hi, I did openVMS bash$ svn co trunk bash$ mvn clean install bash$ all the build steps indicates SUCCESS; lets do a cd and inspect bash$ cd /dka3/.m2/repository/org/apache/maven/apache-maven/3.1-SNAPSHOT bash$ ls -l total 10205 -rwxr-x--- 1 STADELMA 129 5206734 Jan 7 12:12 apache-maven-3.1-SNAPSHOT-bin.tar.gz -rwxr-x--- 1 STADELMA 129 5234859 Jan 7 12:12 apache-maven-3.1-SNAPSHOT-bin.zip -rwxr-x--- 1 STADELMA 129 1113 Jan 7 12:12 apache-maven-3.1-SNAPSHOT-site.xml -rwxr-x--- 1 STADELMA 129 5569 Jan 7 12:12 apache-maven-3.1-SNAPSHOT.pom -rwxr-x--- 1 STADELMA 129 316 Jan 7 12:12 maven-metadata-local.xml openVMS copy apache-maven-3.1-SNAPSHOT-bin.tar.gz sys$login: apache-maven-3.1-SNAPSHOT-bin.tar.gz openVMS set def sys$login openVMSbash bash$ gnutar -vzxf apache-maven-3.1-SNAPSHOT-bin.tar.gz and I get the just built maven-3.1-snapshot installed BUT Now I am facing one problem I've never seen before. *** bash$ cd $HOME/apache-maven-3.1-SNAPSHOT bash$ ls -l total 13 -rwxr-x--- 1 STADELMA 129 230 Jan 7 12:12 m2.conf -rwxr-x--- 1 STADELMA 129 6152 Jan 7 12:12 mvn.bat -rwxr-x--- 1 STADELMA 129 6306 Jan 7 12:12 mvnDebug.bat I am facing the following problem! why was mvn and mvnDebug (the shell files) not packaged into my target *tar.gz file? lets look at the sources openVMS set def DKA3:[SW-PROJEKTE.asf.maven.maven-3.trunk.apache-maven.src.bin] bash$ ls -l total 31 drwxr-x--- 1 STADELMA 129 512 Oct 30 16:27 _svn -rwxr-x--- 1 STADELMA 129 222 Oct 30 16:27 m2.conf -rwxr-x--- 1 STADELMA 129 5807 Jan 7 11:28 mvn -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvn.bat -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvnDebug -rwxr-x--- 1 STADELMA 129 6106 Jan 7 11:28 mvnDebug.bat -rwxr-x--- 1 STADELMA 129 6115 Jan 7 11:28 mvnyjp bash$ all there, just not packaged with my tar.gz and maybe .zip file any hints welcome Josef - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: building from latest trunk
Thanks Steven, I assumed that! BUT are you saying that $ svn up does no longer work ... AND For me there is to say I do not have a git for OpenVMS yet, hence this circumstances will complicate my src update cycles, unless someone knows about a OpenVMS port of GIT! Are you further saying that maven trunk sources are no longer making it into the svn repo? in this case - reading at http://maven.apache.org/guides/development/guide-building-m2.html indicates that as alternative one can still use svn co but this has no value if this repo is not updated by developers. For my problem as work around ... I just copied the 2 missing files mvn and mvnDebug from the kit into m2_home/bin and then did OpenVMS bash bash$ mvn -version Apache Maven 3.1-SNAPSHOT (rNON-CANONICAL_2013-01-07_12-07_STADELMA; 2013-01-07 12:07:04+0100) Maven home: /dka3/stadelma/apache-maven-3.1 Java version: 1.6.0, vendor: Hewlett-Packard Company Java home: /DKA3/java_60/JRE Default locale: en, platform encoding: ISO8859-1 OS name: openvms, version: v8.4, arch: ia64, family: openvms bash$ But I don't know why the maven build did not package this two files into my tar.gz or zip file. Josef -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Montag, 7. Januar 2013 14:56 An: Maven Users List Betreff: Re: building from latest trunk Not an answer for you but an FYI: Maven trunk has moved to git On 7 January 2013 13:47, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Hi, I did openVMS bash$ svn co trunk bash$ mvn clean install bash$ all the build steps indicates SUCCESS; lets do a cd and inspect bash$ cd /dka3/.m2/repository/org/apache/maven/apache-maven/3.1-SNAPSHOT bash$ ls -l total 10205 -rwxr-x--- 1 STADELMA 129 5206734 Jan 7 12:12 apache-maven-3.1-SNAPSHOT-bin.tar.gz -rwxr-x--- 1 STADELMA 129 5234859 Jan 7 12:12 apache-maven-3.1-SNAPSHOT-bin.zip -rwxr-x--- 1 STADELMA 129 1113 Jan 7 12:12 apache-maven-3.1-SNAPSHOT-site.xml -rwxr-x--- 1 STADELMA 129 5569 Jan 7 12:12 apache-maven-3.1-SNAPSHOT.pom -rwxr-x--- 1 STADELMA 129 316 Jan 7 12:12 maven-metadata-local.xml openVMS copy apache-maven-3.1-SNAPSHOT-bin.tar.gz sys$login: apache-maven-3.1-SNAPSHOT-bin.tar.gz openVMS set def sys$login openVMSbash bash$ gnutar -vzxf apache-maven-3.1-SNAPSHOT-bin.tar.gz and I get the just built maven-3.1-snapshot installed BUT Now I am facing one problem I've never seen before. *** bash$ cd $HOME/apache-maven-3.1-SNAPSHOT bash$ ls -l total 13 -rwxr-x--- 1 STADELMA 129 230 Jan 7 12:12 m2.conf -rwxr-x--- 1 STADELMA 129 6152 Jan 7 12:12 mvn.bat -rwxr-x--- 1 STADELMA 129 6306 Jan 7 12:12 mvnDebug.bat I am facing the following problem! why was mvn and mvnDebug (the shell files) not packaged into my target *tar.gz file? lets look at the sources openVMS set def DKA3:[SW-PROJEKTE.asf.maven.maven-3.trunk.apache-maven.src.bin] bash$ ls -l total 31 drwxr-x--- 1 STADELMA 129 512 Oct 30 16:27 _svn -rwxr-x--- 1 STADELMA 129 222 Oct 30 16:27 m2.conf -rwxr-x--- 1 STADELMA 129 5807 Jan 7 11:28 mvn -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvn.bat -rwxr-x--- 1 STADELMA 129 5955 Jan 7 11:28 mvnDebug -rwxr-x--- 1 STADELMA 129 6106 Jan 7 11:28 mvnDebug.bat -rwxr-x--- 1 STADELMA 129 6115 Jan 7 11:28 mvnyjp bash$ all there, just not packaged with my tar.gz and maybe .zip file any hints welcome Josef - 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
AW: building from latest trunk
Does that mean that I can still use jsvn to update my maven trunk sources but this time just from a different (git-hub)repository found under a different url? if yes: what is the correct svn checkout command to use? Thanks Josef -Ursprüngliche Nachricht- Von: Thomas Broyer [mailto:t.bro...@gmail.com] Gesendet: Montag, 7. Januar 2013 15:52 An: Maven Users List Betreff: Re: building from latest trunk On Mon, Jan 7, 2013 at 3:32 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Those docs are in the process of being rewitten... they are sadly not what they should be. AFAIK you will need GIT to get the latest core distribution... If you dont need latest, you can get the release tarballs... And there is always the ability to get a .zip of the core source though some magic via github GitHub also exposes every repo as SVN: https://github.com/blog/1178-collaborating-on-github-with-subversion - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Why does mvn compiile using java 1.3?
I don't love that as a default! because there are OS which do not yet have up-to-date Open JDK 7 or JDK 8. And we do not have influence to the company not delivering as they should, years after promising that Java is what we need for future OpenVMS developments. Or has someone knowledge when HP releases a Open JDK 7.0? And yes, we know, changing a platform with 25 to 30 year old business algorithms written in PASCAL, today integrated with Java to form part of a larger web-service server on OpenVMS is not so easy. Legacy code has value too, not only legacy data! Josef -Ursprüngliche Nachricht- Von: Mark Derricutt [mailto:m...@talios.com] Gesendet: Mittwoch, 28. November 2012 19:36 An: Maven Users List Betreff: Re: Why does mvn compiile using java 1.3? Now that Oracle are controlling Java on OSX we can no longer blame Apple - I'd love to see the default become Java 7 now. And if one needs to lock down to the older versions, lock them down. On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote: Good to know that Maven is now only 8 years behind. I blame Apple. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: MissingProjectException
I toke the NetBeans 7.2 / tool / option / java / maven / and I had to browsed to E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin The I tried a clean build from NetBeans and I got -- cd E:\Users\C770817\SW-PROJEKTE\SpezplaService; JAVA_HOME=C:\\Program Files\\Java\\jdk1.6.0_30 M2_HOME=E:\\Users\\C770817\\SW-UMGEBUNG\\apache-maven-3.1\\bin mvn.bat clean install ERROR: M2_HOME is set to an invalid directory. M2_HOME = E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin Please set the M2_HOME variable in your environment to match the location of the Maven installation maybe not with an older NetBeans version browsing to and setting in the select window to E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin\.. selects actually E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1 which is correct - hence it works. --- But E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin is a no go for NetBeans 7.2 and results in the error shown above. So far my NetBeans 7.2 setup for maven. the same error happens when I take the control panel and set the env.variable M2_HOME to E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin So for you to work Set MAVEN_HOME or M2_HOME to E:\Apps\Dev\NetBeans7\NetBeans7.2.1\java\maven but not E:\Apps\Dev\NetBeans7\NetBeans7.2.1\java\maven\bin or vice versa, (even the 2 dots may make it potentially work go up one level to be correct) and have a greater chance . . . it will all work :-) if not tell me and I try it myself with this setups. NetBeans 7.2 allows only to brows for the maven location, and it takes out the last dir when it is followed by hacked in \.. while older NetBeans give you access and allows to enter what you want. Josef -Ursprüngliche Nachricht- Von: Froggerbin [mailto:frogger...@gmail.com] Gesendet: Donnerstag, 29. November 2012 15:58 An: 'Maven Users List' Betreff: RE: MissingProjectException Yes, I knew that NetBeans had its own Maven on board. My external as well as internal maven work nicely through Windows commandline, but not through NetBeans. That's the whole problem. From commandline here follow the internal maven and external maven installations: NetBeans onboard internal Maven: C:\mvn -version Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: E:\Apps\Dev\NetBeans7\NetBeans7.2.1\java\maven\bin\.. Java version: 1.7.0_07, vendor: Oracle Corporation Java home: E:\Apps (x86)\Dev\Java\jdk7u7\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7, version: 6.1, arch: x86, family: windows External Maven (extracted zip): E:\Apps (x86)\Dev\apachemaven\apache-maven-3.0.4\binmvn -version Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: E:\Apps (x86)\Dev\apachemaven\apache-maven-3.0.4\bin\.. Java version: 1.7.0_07, vendor: Oracle Corporation Java home: E:\Apps (x86)\Dev\Java\jdk7u7\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7, version: 6.1, arch: x86, family: windows I tried using both the internal Maven and the external maven in NetBeans through the options you said (options-java-maven) but it still doesn't work. -Original Message- From: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch] Sent: woensdag 28 november 2012 9:55 To: Maven Users List Subject: AW: MissingProjectException Hi Do you know that NetBeans has its own maven on board? C:\Program Files\NetBeans 7.2\java\maven\bin Your EXTERNAL maven - pointed to by MAVEN_HOME or M2_HOME might work nicely, i.e. USE $ mvn -version as a always first to check and tell us a bit more about what you have. In order to use this external maven with NetBeans, at NetBeans goto /tools /options /tab to JAVA /tab to MAVEN and enter the path to the root of your external maven i.e. or the same as you have in M2_HOME but not as a multi part path, only as a single path is allowed there E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.0.5 If you already toke notice of that, or know that, then you are on a good way. Josef -Ursprüngliche Nachricht- Von: Froggerbin [mailto:frogger...@gmail.com] Gesendet: Mittwoch, 28. November 2012 00:03 An: 'Maven Users List'; rwhee...@artifact-software.com Betreff: RE: MissingProjectException To me it simply looks like the character is being escaped with \ on both sides: \ sample \ I figure NetBeans did this because the path contains spaces, therefor if the are escaped, then the \ have to be escaped as well, hence the double \. That is simply supposed to be mvn.bat that resides in the Maven installation directory. In that case it's an external Maven. Internal or external, I tried both and the problem remained. -Original Message- From: Ron Wheeler [mailto:rwhee...@artifact-software.com] Sent: dinsdag 27 november 2012 23:59 To: users@maven.apache.org Subject: Re: MissingProjectException On 27/11/2012 4:07 PM, Froggerbin
AW: AW: MissingProjectException
That is what I say, definitely not, I have tested it, and it produces the error shown in .-2 Josef -Ursprüngliche Nachricht- Von: Ron Wheeler [mailto:rwhee...@artifact-software.com] Gesendet: Donnerstag, 29. November 2012 18:29 An: users@maven.apache.org Betreff: Re: AW: MissingProjectException I don't think M2_HOME should have the \bin at the end. On 29/11/2012 12:18 PM, Stadelmann Josef wrote: I toke the NetBeans 7.2 / tool / option / java / maven / and I had to browsed to E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin The I tried a clean build from NetBeans and I got -- cd E:\Users\C770817\SW-PROJEKTE\SpezplaService; JAVA_HOME=C:\\Program Files\\Java\\jdk1.6.0_30 M2_HOME=E:\\Users\\C770817\\SW-UMGEBUNG\\apache-maven-3.1\\bin mvn.bat clean install ERROR: M2_HOME is set to an invalid directory. M2_HOME = E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin Please set the M2_HOME variable in your environment to match the location of the Maven installation maybe not with an older NetBeans version browsing to and setting in the select window to E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin\.. selects actually E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1 which is correct - hence it works. --- But E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin is a no go for NetBeans 7.2 and results in the error shown above. So far my NetBeans 7.2 setup for maven. the same error happens when I take the control panel and set the env.variable M2_HOME to E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin So for you to work Set MAVEN_HOME or M2_HOME to E:\Apps\Dev\NetBeans7\NetBeans7.2.1\java\maven but not E:\Apps\Dev\NetBeans7\NetBeans7.2.1\java\maven\bin or vice versa, (even the 2 dots may make it potentially work go up one level to be correct) and have a greater chance . . . it will all work :-) if not tell me and I try it myself with this setups. NetBeans 7.2 allows only to brows for the maven location, and it takes out the last dir when it is followed by hacked in \.. while older NetBeans give you access and allows to enter what you want. Josef -Ursprüngliche Nachricht- Von: Froggerbin [mailto:frogger...@gmail.com] Gesendet: Donnerstag, 29. November 2012 15:58 An: 'Maven Users List' Betreff: RE: MissingProjectException Yes, I knew that NetBeans had its own Maven on board. My external as well as internal maven work nicely through Windows commandline, but not through NetBeans. That's the whole problem. From commandline here follow the internal maven and external maven installations: NetBeans onboard internal Maven: C:\mvn -version Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: E:\Apps\Dev\NetBeans7\NetBeans7.2.1\java\maven\bin\.. Java version: 1.7.0_07, vendor: Oracle Corporation Java home: E:\Apps (x86)\Dev\Java\jdk7u7\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7, version: 6.1, arch: x86, family: windows External Maven (extracted zip): E:\Apps (x86)\Dev\apachemaven\apache-maven-3.0.4\binmvn -version Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: E:\Apps (x86)\Dev\apachemaven\apache-maven-3.0.4\bin\.. Java version: 1.7.0_07, vendor: Oracle Corporation Java home: E:\Apps (x86)\Dev\Java\jdk7u7\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7, version: 6.1, arch: x86, family: windows I tried using both the internal Maven and the external maven in NetBeans through the options you said (options-java-maven) but it still doesn't work. -Original Message- From: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch] Sent: woensdag 28 november 2012 9:55 To: Maven Users List Subject: AW: MissingProjectException Hi Do you know that NetBeans has its own maven on board? C:\Program Files\NetBeans 7.2\java\maven\bin Your EXTERNAL maven - pointed to by MAVEN_HOME or M2_HOME might work nicely, i.e. USE $ mvn -version as a always first to check and tell us a bit more about what you have. In order to use this external maven with NetBeans, at NetBeans goto /tools /options /tab to JAVA /tab to MAVEN and enter the path to the root of your external maven i.e. or the same as you have in M2_HOME but not as a multi part path, only as a single path is allowed there E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.0.5 If you already toke notice of that, or know that, then you are on a good way. Josef -Ursprüngliche Nachricht- Von: Froggerbin [mailto:frogger...@gmail.com] Gesendet: Mittwoch, 28. November 2012 00:03 An: 'Maven Users List'; rwhee...@artifact-software.com Betreff: RE: MissingProjectException To me it simply looks like the character is being escaped with \ on both sides: \ sample \ I figure NetBeans did this because the path contains spaces, therefor
AW: MissingProjectException
Hi Do you know that NetBeans has its own maven on board? C:\Program Files\NetBeans 7.2\java\maven\bin Your EXTERNAL maven - pointed to by MAVEN_HOME or M2_HOME might work nicely, i.e. USE $ mvn -version as a always first to check and tell us a bit more about what you have. In order to use this external maven with NetBeans, at NetBeans goto /tools /options /tab to JAVA /tab to MAVEN and enter the path to the root of your external maven i.e. or the same as you have in M2_HOME but not as a multi part path, only as a single path is allowed there E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.0.5 If you already toke notice of that, or know that, then you are on a good way. Josef -Ursprüngliche Nachricht- Von: Froggerbin [mailto:frogger...@gmail.com] Gesendet: Mittwoch, 28. November 2012 00:03 An: 'Maven Users List'; rwhee...@artifact-software.com Betreff: RE: MissingProjectException To me it simply looks like the character is being escaped with \ on both sides: \ sample \ I figure NetBeans did this because the path contains spaces, therefor if the are escaped, then the \ have to be escaped as well, hence the double \. That is simply supposed to be mvn.bat that resides in the Maven installation directory. In that case it's an external Maven. Internal or external, I tried both and the problem remained. -Original Message- From: Ron Wheeler [mailto:rwhee...@artifact-software.com] Sent: dinsdag 27 november 2012 23:59 To: users@maven.apache.org Subject: Re: MissingProjectException On 27/11/2012 4:07 PM, Froggerbin wrote: \E:\\Apps (x86)\\Dev\\apachemaven\\apache-maven-3.0.4\\bin\\mvn.bat\ This looks very odd and I am not sure how any normal parser is going to deal with this. What is it supposed to be? Ron -- 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 - 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
mvn build 3.1-snapshot failes when building core
my svn trunk update has Completed: At revision: 1405720 using maven 3.0.5-snapshot to build maven 3.1-snapshot it always fails when building the CORE any ideas welcome ! or shall I file a JIRA ? Josef cd E:\asf\maven\maven-3\trunk; JAVA_HOME=C:\\Program Files\\Java\\jdk1.6.0_30 M2_HOME=E:\\Users\\C770817\\SW-UMGEBUNG\\apache-maven-3.0.5 E:\\Users\\C770817\\SW-UMGEBUNG\\apache-maven-3.0.5\\bin\\mvn.bat clean install Scanning for projects... Reactor Build Order: Apache Maven Maven Model Maven Artifact Maven Plugin API Maven Model Builder Maven Settings Maven Settings Builder Maven Repository Metadata Model Maven Aether Provider Maven Core Maven Compat Maven Embedder Maven Distribution Building Apache Maven 3.1-SNAPSHOT [clean:clean] Deleting E:\asf\maven\maven-3\trunk\target [remote-resources:process] [animal-sniffer:check] Checking unresolved references to org.codehaus.mojo.signature:java15:1.0 [site:attach-descriptor] [install:install] Installing E:\asf\maven\maven-3\trunk\pom.xml to E:\Users\C770817\.m2\repository\org\apache\maven\maven\3.1-SNAPSHOT\mave n-3.1-SNAPSHOT.pom Installing E:\asf\maven\maven-3\trunk\target\maven-3.1-SNAPSHOT-site.xml to E:\Users\C770817\.m2\repository\org\apache\maven\maven\3.1-SNAPSHOT\mave n-3.1-SNAPSHOT-site.xml Building Maven Model 3.1-SNAPSHOT [clean:clean] Deleting E:\asf\maven\maven-3\trunk\maven-model\target [modello:java] outputDirectory: E:\asf\maven\maven-3\trunk\maven-model\target\generated-sources\modello Working on model: src/main/mdo/maven.mdo Generating current version: 4.0.0 [modello:xpp3-reader] outputDirectory: E:\asf\maven\maven-3\trunk\maven-model\target\generated-sources\modello Working on model: src/main/mdo/maven.mdo Generating current version: 4.0.0 [modello:xpp3-extended-reader] outputDirectory: E:\asf\maven\maven-3\trunk\maven-model\target\generated-sources\modello Working on model: src/main/mdo/maven.mdo Generating current version: 4.0.0 [modello:xpp3-writer] outputDirectory: E:\asf\maven\maven-3\trunk\maven-model\target\generated-sources\modello Working on model: src/main/mdo/maven.mdo Generating current version: 4.0.0 [remote-resources:process] [resources:resources] [debug] execute contextualize Using 'UTF-8' encoding to copy filtered resources. skip non existing resourceDirectory E:\asf\maven\maven-3\trunk\maven-model\src\main\resources Copying 3 resources [compiler:compile] Compiling 50 source files to E:\asf\maven\maven-3\trunk\maven-model\target\classes [animal-sniffer:check] Checking unresolved references to org.codehaus.mojo.signature:java15:1.0 [resources:testResources] [debug] execute contextualize Using 'UTF-8' encoding to copy filtered resources. skip non existing resourceDirectory E:\asf\maven\maven-3\trunk\maven-model\src\test\resources Copying 3 resources [compiler:testCompile] Compiling 37 source files to E:\asf\maven\maven-3\trunk\maven-model\target\test-classes [surefire:test] Surefire report directory: E:\asf\maven\maven-3\trunk\maven-model\target\surefire-reports --- T E S T S --- Running org.apache.maven.model.ActivationFileTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Running org.apache.maven.model.ActivationOSTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec Running org.apache.maven.model.ActivationPropertyTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.apache.maven.model.ActivationTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.apache.maven.model.BuildTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.apache.maven.model.CiManagementTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.apache.maven.model.ContributorTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.apache.maven.model.DependencyManagementTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.apache.maven.model.DependencyTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.apache.maven.model.DeploymentRepositoryTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.apache.maven.model.DeveloperTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running
[maven-3/trunk] bootstrap-build failing
How can I cure best the problems shown below? it occurs during a
bootstrap-build of maven-3/trunk on my Vista System.
(see red lines, which are of interesst to me).
I have successfully build from sources SLF4J é all. Where does this
bootstrap-build.xml expect this files now?
where do I have to copy the SLF4J-*.jars and maybe others to make the
maven-3/trunk build.xml (bootstrap-build) happy?
Has the final error shown below, (which makes the bootstrap-build fail?) to do
with the absence of SLF4J-*.jar's or what does it indicate?
This on a Windows Vista System
Josef
ant -f E:\\asf\\maven\\maven-3\\trunk all
clean-bootstrap:
initTaskDefs:
Building Apache Maven ...
isMavenHomeSet:
init:
maven.home = E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1
maven.repo.local = /E:/Users/C770817/.m2/repository
distributionId = apache-maven
distributionName = Apache Maven
distributionDirectory = apache-maven
prompt-maven-home-exists:
pull:
Copying 1 file to E:\asf\maven\maven-3\trunk
Deleting: E:\asf\maven\maven-3\trunk\dependencies.xml
generate-sources:
Created dir: E:\asf\maven\maven-3\trunk\bootstrap\target
Created dir: E:\asf\maven\maven-3\trunk\bootstrap\target\generated-sources
Generating sources for maven-model/src/main/mdo/maven.mdo
Generating sources for maven-plugin-api/src/main/mdo/lifecycle.mdo
Generating sources for maven-model-builder/src/main/mdo/profiles.mdo
Generating sources for maven-settings/src/main/mdo/settings.mdo
Generating sources for maven-core/src/main/mdo/toolchains.mdo
Generating sources for maven-repository-metadata/src/main/mdo/metadata.mdo
Generating sources for maven-compat/src/main/mdo/profiles.mdo
Generating sources for maven-compat/src/main/mdo/paramdoc.mdo
compile-boot:
Created dir: E:\asf\maven\maven-3\trunk\bootstrap\target\classes
Compiling 719 source files to
E:\asf\maven\maven-3\trunk\bootstrap\target\classes
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Copying 1 file to E:\asf\maven\maven-3\trunk\bootstrap\target\classes
process-classes:
Using plexus version 1.5.5
SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
[INFO] Discovered 129 component descriptors(s)
maven-compile:
SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
null 3.1-SNAPSHOT
${distributionShortName} home: unknown maven home
Java version: 1.6.0_30, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_30\jre
Default locale: de_CH, platform encoding: Cp1252
OS name: windows vista, version: 6.0, arch: x86, family: windows[debug]
execute contextualize
[debug] execute contextualize
---
T E S T S
---
Running org.apache.maven.model.ActivationFileTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running org.apache.maven.model.ActivationOSTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.ActivationPropertyTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.ActivationTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.BuildTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running org.apache.maven.model.CiManagementTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.ContributorTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.DependencyManagementTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.DependencyTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.DeploymentRepositoryTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.DeveloperTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.DistributionManagementTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.ExclusionTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.ExtensionTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.IssueManagementTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.LicenseTest
Tests
AW: [maven-3/trunk] bootstrap-build failing
What does that mean?
are you saying that maven developers will not fix the bootstrap-build problem
shown below or
are you saying that This mailing list strips HTML I have delivered
insufficient information?
I am confused about your answer, sorry!
Josef
-Ursprüngliche Nachricht-
Von: Benson Margulies [mailto:bimargul...@gmail.com]
Gesendet: Donnerstag, 1. November 2012 11:39
An: Maven Users List
Betreff: Re: [maven-3/trunk] bootstrap-build failing
On Thu, Nov 1, 2012 at 6:29 AM, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
How can I cure best the problems shown below? it occurs during a
bootstrap-build of maven-3/trunk on my Vista System.
(see red lines, which are of interesst to me).
We can't. This mailing list strips HTML.
I have successfully build from sources SLF4J é all. Where does this
bootstrap-build.xml expect this files now?
where do I have to copy the SLF4J-*.jars and maybe others to make the
maven-3/trunk build.xml (bootstrap-build) happy?
Has the final error shown below, (which makes the bootstrap-build fail?) to
do with the absence of SLF4J-*.jar's or what does it indicate?
This on a Windows Vista System
Josef
ant -f E:\\asf\\maven\\maven-3\\trunk all
clean-bootstrap:
initTaskDefs:
Building Apache Maven ...
isMavenHomeSet:
init:
maven.home = E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1
maven.repo.local = /E:/Users/C770817/.m2/repository distributionId =
apache-maven distributionName = Apache Maven distributionDirectory =
apache-maven
prompt-maven-home-exists:
pull:
Copying 1 file to E:\asf\maven\maven-3\trunk
Deleting: E:\asf\maven\maven-3\trunk\dependencies.xml
generate-sources:
Created dir: E:\asf\maven\maven-3\trunk\bootstrap\target
Created dir:
E:\asf\maven\maven-3\trunk\bootstrap\target\generated-sources
Generating sources for maven-model/src/main/mdo/maven.mdo
Generating sources for maven-plugin-api/src/main/mdo/lifecycle.mdo
Generating sources for maven-model-builder/src/main/mdo/profiles.mdo
Generating sources for maven-settings/src/main/mdo/settings.mdo
Generating sources for maven-core/src/main/mdo/toolchains.mdo
Generating sources for
maven-repository-metadata/src/main/mdo/metadata.mdo
Generating sources for maven-compat/src/main/mdo/profiles.mdo
Generating sources for maven-compat/src/main/mdo/paramdoc.mdo
compile-boot:
Created dir: E:\asf\maven\maven-3\trunk\bootstrap\target\classes
Compiling 719 source files to
E:\asf\maven\maven-3\trunk\bootstrap\target\classes
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Copying 1 file to E:\asf\maven\maven-3\trunk\bootstrap\target\classes
process-classes:
Using plexus version 1.5.5
SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
[INFO] Discovered 129 component descriptors(s)
maven-compile:
SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
null 3.1-SNAPSHOT
${distributionShortName} home: unknown maven home Java version:
1.6.0_30, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_30\jre Default locale:
de_CH, platform encoding: Cp1252 OS name: windows vista, version:
6.0, arch: x86, family: windows[debug] execute contextualize
[debug] execute contextualize
---
T E S T S
---
Running org.apache.maven.model.ActivationFileTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016
sec Running org.apache.maven.model.ActivationOSTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.ActivationPropertyTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.ActivationTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.BuildTest Tests run: 4, Failures: 0,
Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Running
org.apache.maven.model.CiManagementTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.ContributorTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.DependencyManagementTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.DependencyTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.model.DeploymentRepositoryTest
Tests
AW: [maven-3/trunk] bootstrap-build failing
, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.203 sec Running org.apache.maven.model.inheritance.DefaultInheritanceAssemblerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.671 sec Running org.apache.maven.model.interpolation.StringSearchModelInterpolatorTest Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.593 sec Running org.apache.maven.model.path.DefaultUrlNormalizerTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.apache.maven.model.profile.activation.JdkVersionProfileActivatorTest Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec Running org.apache.maven.model.profile.activation.PropertyProfileActivatorTest Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.11 sec Running org.apache.maven.model.validation.DefaultModelValidatorTest Tests run: 43, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.967 sec Results : Tests run: 94, Failures: 0, Errors: 0, Skipped: 0 [debug] execute contextualize [debug] execute contextualize --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [debug] execute contextualize [debug] execute contextualize --- T E S T S --- Running org.apache.maven.settings.building.DefaultSettingsBuilderFactoryTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.109 sec Running org.apache.maven.settings.validation.DefaultSettingsValidatorTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Results : Tests run: 7, Failures: 0, Errors: 0, Skipped: 0 [debug] execute contextualize [debug] execute contextualize --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [debug] execute contextualize [debug] execute contextualize --- T E S T S --- Running org.apache.maven.repository.internal.DefaultServiceLocatorTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.187 sec Running org.apache.maven.repository.internal.DefaultVersionResolverTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.764 sec Running org.apache.maven.repository.internal.RepositorySystemTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.281 sec Results : Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 E:\asf\maven\maven-3\trunk\build.xml:250: Java returned: 1 BUILD FAILED (total time: 1 minute 21 seconds) -Ursprüngliche Nachricht- Von: Graham Leggett [mailto:minf...@sharp.fm] Gesendet: Donnerstag, 1. November 2012 11:58 An: Maven Users List Betreff: Re: [maven-3/trunk] bootstrap-build failing On 01 Nov 2012, at 12:43 PM, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: What does that mean? are you saying that maven developers will not fix the bootstrap-build problem shown below or are you saying that This mailing list strips HTML I have delivered insufficient information? You have delivered insufficient information. HTML mail provides for different fonts and different colours, while plain text mail doesn't. HTML mail also provides a layout headache for makers of mailing list archiving software, and introduces all sorts of security headaches too, and so standard practise for many mailing lists is to take into account the text-only version of your email only. To see what your email looks like in the archives, see below: http://mail-archives.apache.org/mod_mbox/maven-users/201211.mbox/%3CC76B3518F981E0468383F7E091A595B88EFBE0%40c005815.chres1.doleni.net%3E As you can see, no red colour, so we have no idea what lines you are referring to. Regards, Graham -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: [maven-3/trunk] bootstrap-build failing
Hi Anders If you don't have maven installed on your PC (System) one way to start is to use a ant bootstrap-build. In the past this was running nicely. Now with the latest trunk sources ant -f- build.xml does not run at all to completion. I am using JDK 1.6 and ANT-1.8.1 or ANT-1.8.2 on a Windows Vista System. If the bootstrap-build is no longer of any needs, as it is assumed that everyone has now a previous version of maven-2.2.1 installed (i.e.), then we should remove the build.xml and the README.bootstrap.txt file from the trunk. That would be a clean indicator that build.xml / bootstrap-builds, are no longer supported. Thanks for any thoughts / hints into either a bootstrap-build or non-bootstrap-build world. Josef -Ursprüngliche Nachricht- Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag von Anders Hammar Gesendet: Donnerstag, 1. November 2012 12:11 An: Maven Users List Betreff: Re: [maven-3/trunk] bootstrap-build failing While you're at it: Give us info on what version of Ant you're using as well what JDK version. If you want to speed things up, you could try a different Ant version. (I don't know which Ant version is preferred though as I always build with Maven.) The slf4j error is most likely safe to ignore. That has to do about the logging and just says it's defaulting to the no-op impl. /Anders On Thu, Nov 1, 2012 at 11:58 AM, Graham Leggett minf...@sharp.fm wrote: On 01 Nov 2012, at 12:43 PM, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: What does that mean? are you saying that maven developers will not fix the bootstrap-build problem shown below or are you saying that This mailing list strips HTML I have delivered insufficient information? You have delivered insufficient information. HTML mail provides for different fonts and different colours, while plain text mail doesn't. HTML mail also provides a layout headache for makers of mailing list archiving software, and introduces all sorts of security headaches too, and so standard practise for many mailing lists is to take into account the text-only version of your email only. To see what your email looks like in the archives, see below: http://mail-archives.apache.org/mod_mbox/maven-users/201211.mbox/%3CC7 6B3518F981E0468383F7E091A595B88EFBE0%40c005815.chres1.doleni.net%3E As you can see, no red colour, so we have no idea what lines you are referring to. Regards, Graham -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: [maven-3/trunk] bootstrap-build failing
OK Stuart, at my Vista System, it fails. Just downloaded and installed ant 1.8.4 $ java -version java version 1.6.0_30 Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) Client VM (build 20.5-b03, mixed mode) C770817@C036357 /e/asf/maven/maven-3/trunk $ ant -version Apache Ant(TM) version 1.8.4 compiled on May 22 2012 $ ant -d -f build.xml ... BUILD FAILED E:\asf\maven\maven-3\trunk\build.xml:250: Java returned: 1 at org.apache.tools.ant.taskdefs.Java.execute(Java.java:111) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:392) at org.apache.tools.ant.Target.performTasks(Target.java:413) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) at org.apache.tools.ant.Project.executeTarget(Project.java:1368) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.Main.runBuild(Main.java:809) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Total time: 2 minutes 7 seconds E:\asf\maven\maven-3\trunk So I have no clue why this ant bootstrap-build fails on my Vista System which is a clean as many other systems used to develop code. The line build.xml(250) is where ...MavenCLI class gets invoked/forked by a java command. I have no clue why 1 is returned to/by Java. OK - we sit behind a firewall , if that makes a difference? Josef -Ursprüngliche Nachricht- Von: Stuart McCulloch [mailto:mccu...@gmail.com] Gesendet: Donnerstag, 1. November 2012 14:52 An: Maven Users List Betreff: Re: [maven-3/trunk] bootstrap-build failing On 1 November 2012 10:29, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: How can I cure best the problems shown below? it occurs during a bootstrap-build of maven-3/trunk on my Vista System. (see red lines, which are of interesst to me). I have successfully build from sources SLF4J é all. Where does this bootstrap-build.xml expect this files now? where do I have to copy the SLF4J-*.jars and maybe others to make the maven-3/trunk build.xml (bootstrap-build) happy? SLF4J should be downloaded by the [artifact:dependencies] task, just like all the other bootstrap dependencies - you shouldn't need to build it yourself. Has the final error shown below, (which makes the bootstrap-build fail?) to do with the absence of SLF4J-*.jar's or what does it indicate? The SLF4J messages about 'Failed to load class' and 'Defaulting to no-operation' are informational and should not fail the build. It means that it couldn't find a backend implementation (the current build does not specify a particular backend on purpose) so it's telling you about this in case you had meant to choose a backend but forgot: http://www.slf4j.org/codes.html#StaticLoggerBinder The final error just says that Java returned 1 on exit, but doesn't say why - you could try running ant -d -f build.xml to see if that gives more information about the failure at the end. FWIW, I just tried the bootstrap build on a clean system (OSX, Java 1.6.0_37, Ant 1.8.4) and it built without errors - note that I still saw the SLF4J messages, but those are expected at the moment This on a Windows Vista System Josef ant -f E:\\asf\\maven\\maven-3\\trunk all clean-bootstrap: initTaskDefs: Building Apache Maven ... isMavenHomeSet: init: maven.home = E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1 maven.repo.local = /E:/Users/C770817/.m2/repository distributionId = apache-maven distributionName = Apache Maven distributionDirectory = apache-maven prompt-maven-home-exists: pull: Copying 1 file to E:\asf\maven\maven-3\trunk Deleting: E:\asf\maven\maven-3\trunk\dependencies.xml generate-sources: Created dir: E:\asf\maven\maven-3\trunk\bootstrap\target Created dir: E:\asf\maven\maven-3\trunk\bootstrap\target\generated-sources Generating sources for maven-model/src/main/mdo/maven.mdo Generating sources for maven-plugin-api/src/main/mdo/lifecycle.mdo Generating sources for maven-model-builder/src/main/mdo/profiles.mdo Generating sources for maven-settings/src/main/mdo/settings.mdo Generating sources for maven-core/src/main/mdo/toolchains.mdo Generating sources for maven
AW: AW: [maven-3/trunk] bootstrap-build failing
Will close the guess, and bootstrap-build from my home system tomorrow not sitting behind a firewall using proxy info to reach out to central! Josef -Ursprüngliche Nachricht- Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag von Anders Hammar Gesendet: Donnerstag, 1. November 2012 17:23 An: Maven Users List Betreff: Re: AW: [maven-3/trunk] bootstrap-build failing I'm guessing there's a missing proxy configuration here. /Anders On Thu, Nov 1, 2012 at 4:42 PM, Stuart McCulloch mccu...@gmail.com wrote: On 1 Nov 2012, at 15:06, Stadelmann Josef wrote: OK Stuart, at my Vista System, it fails. Just downloaded and installed ant 1.8.4 $ java -version java version 1.6.0_30 Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) Client VM (build 20.5-b03, mixed mode) C770817@C036357 /e/asf/maven/maven-3/trunk $ ant -version Apache Ant(TM) version 1.8.4 compiled on May 22 2012 $ ant -d -f build.xml ... BUILD FAILED E:\asf\maven\maven-3\trunk\build.xml:250: Java returned: 1 at org.apache.tools.ant.taskdefs.Java.execute(Java.java:111) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j ava:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess orImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java :106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:392) at org.apache.tools.ant.Target.performTasks(Target.java:413) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) at org.apache.tools.ant.Project.executeTarget(Project.java:1368) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExec utor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.Main.runBuild(Main.java:809) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Total time: 2 minutes 7 seconds E:\asf\maven\maven-3\trunk So I have no clue why this ant bootstrap-build fails on my Vista System which is a clean as many other systems used to develop code. The line build.xml(250) is where ...MavenCLI class gets invoked/forked by a java command. I have no clue why 1 is returned to/by Java. Line 250 in build.xml is where it forks the JVM - if you capture the output from running ant -d -f build.xml and look for maven-compile: then it should show the actual command it forks (ie. the one that returns error code 1). You could copy that command and all its arguments (ie. java -classpath ...snip... org.apache.maven.cli.MavenCli ...etc...) and try it from the command-line to see if there's an error message that's not getting passed on. Perhaps also add '-X' after 'org.apache.maven.cli.MavenCli' to enable full debug output. OK - we sit behind a firewall , if that makes a difference? The bootstrap build should use your local settings.xml just like Maven, so as long this is configured with any proxy needed to access Maven Central then it should be fine. Josef -Ursprüngliche Nachricht- Von: Stuart McCulloch [mailto:mccu...@gmail.com] Gesendet: Donnerstag, 1. November 2012 14:52 An: Maven Users List Betreff: Re: [maven-3/trunk] bootstrap-build failing On 1 November 2012 10:29, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: How can I cure best the problems shown below? it occurs during a bootstrap-build of maven-3/trunk on my Vista System. (see red lines, which are of interesst to me). I have successfully build from sources SLF4J é all. Where does this bootstrap-build.xml expect this files now? where do I have to copy the SLF4J-*.jars and maybe others to make the maven-3/trunk build.xml (bootstrap-build) happy? SLF4J should be downloaded by the [artifact:dependencies] task, just like all the other bootstrap dependencies - you shouldn't need to build it yourself. Has the final error shown below, (which makes the bootstrap-build fail?) to do with the absence of SLF4J-*.jar's or what does it indicate? The SLF4J messages about 'Failed to load class' and 'Defaulting to no-operation' are informational and should not fail the build. It means that it couldn't find a backend implementation (the current build does not specify a particular backend on purpose) so it's telling you about this in case you had meant to choose a backend but forgot: http
AW: [mvn-3.0.5] troubles with Generating Plugin Management report --- maven-project-info-reports-plugin:2.4
Wayne I have done that very carefully yesterday. For me all was Ok but as you can see it failed. I deleted me repo several times and was unable to build error free. This morning I moved my project to a different directiory tree but on the same disk. Then I've rerun maven from the same account to build the project ... all was excellent working. So now, I don’t have explanation why the POM's should have an issue, but maybe there is a protection or left rubbish problem somewhere, i.e. maven attempting to build into a local place or the like. I am confused, but it runs OK now. Thank you very much for your help and don’t bother with me when I send in such stack traces. Josef -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Montag, 9. Juli 2012 18:52 An: Maven Users List Betreff: Re: [mvn-3.0.5] troubles with Generating Plugin Management report --- maven-project-info-reports-plugin:2.4 Downloaded: http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent ral/org/codehaus/mojo/clirr-maven-plugin/2.3/clirr-maven-plugin-2.3.pom (8 KB at 41.1 KB/sec) Downloaded: http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent ral/org/codehaus/mojo/mojo-parent/27/mojo-parent-27.pom (27 KB at 175.4 KB/sec) [INFO] Could not build project for: clirr-maven-plugin:1 problem was encountered while building the effective model for org.codehaus.mojo:clirr-maven-plugin:2.3 [FATAL] Non-resolvable parent POM for org.codehaus.mojo:mojo-parent:27: Could not find artifact org.codehaus:codehaus-parent:pom:3 @ org.codehaus.mojo:mojo-parent:27 for project org.codehaus.mojo:clirr-maven-plugin:2.3 for project org.codehaus.mojo:clirr-maven-plugin:2.3 org.apache.maven.project.InvalidProjectModelException: 1 problem was encountered while building the effective model for org.codehaus.mojo:clirr-maven-plugin:2.3 [FATAL] Non-resolvable parent POM for org.codehaus.mojo:mojo-parent:27: Could not find artifact org.codehaus:codehaus-parent:pom:3 @ org.codehaus.mojo:mojo-parent:27 for project org.codehaus.mojo:clirr-maven-plugin:2.3 for project org.codehaus.mojo:clirr-maven-plugin:2.3 This error suggests the pom files for clirr-maven-plugin:2.3 and maybe mojo-parent:27 and codehaus-parent in your repo might have issues. Look at those poms in particular. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[mvn-3.0.5] troubles with Generating Plugin Management report --- maven-project-info-reports-plugin:2.4
How can I make it work? 1. The Warning bothers me ... 2. deleted in my repository all in subdirectory mojo from org.codehaus (so all org.codehaus.mojo artifacts need to be refreshed from external repo or maven central or 3. However that does not work 4. But I have checked the various pom's and cant find the gulty one. 5. So what could be the reason for the FATAL errors below, because as you can see artifacs are downloaded if missing 6. what else can I cleanup in my local repo? 7. what does this mean: [INFO] Could not build project for: clirr-maven-plugin:1 8. is there a relation to org.apache.maven.project.InvalidProjectModelException: 1 9. can it be that bandRepositories now strikes back? Josef [INFO] [INFO] --- maven-site-plugin:3.0:site (default) @ SpezplaService --- [INFO] configuring report plugin org.apache.maven.plugins:maven-project-info-reports-plugin:2.4 [INFO] Parent project loaded from repository: com.axa.ch.spezpla:Spezpla-Parent:pom:1.0 [WARNING] Unable to find a URL to the parent project. The parent menu will NOT be added. [INFO] Relativizing decoration links with respect to project URL: http://integ2.ch.winterthur.com/Wiki/index.php/SpezplaService [INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0 skin. [INFO] Generating About report--- maven-project-info-reports-plugin:2.4 [INFO] Generating Project Summary report--- maven-project-info-reports-plugin:2.4 [INFO] Generating Project License report--- maven-project-info-reports-plugin:2.4 [INFO] Generating Project Team report--- maven-project-info-reports-plugin:2.4 [INFO] Generating Source Repository report--- maven-project-info-reports-plugin:2.4 [INFO] Generating Issue Tracking report--- maven-project-info-reports-plugin:2.4 [INFO] Generating Mailing Lists report--- maven-project-info-reports-plugin:2.4 [INFO] Generating Dependencies report--- maven-project-info-reports-plugin:2.4 [INFO] Generating Continuous Integration report--- maven-project-info-reports-plugin:2.4 [INFO] Generating Plugin Management report--- maven-project-info-reports-plugin:2.4 Downloading: http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent ral/org/codehaus/mojo/clirr-maven-plugin/2.3/clirr-maven-plugin-2.3.pom Downloaded: http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent ral/org/codehaus/mojo/clirr-maven-plugin/2.3/clirr-maven-plugin-2.3.pom (8 KB at 41.1 KB/sec) Downloading: http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent ral/org/codehaus/mojo/mojo-parent/27/mojo-parent-27.pom Downloaded: http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent ral/org/codehaus/mojo/mojo-parent/27/mojo-parent-27.pom (27 KB at 175.4 KB/sec) [INFO] Could not build project for: clirr-maven-plugin:1 problem was encountered while building the effective model for org.codehaus.mojo:clirr-maven-plugin:2.3 [FATAL] Non-resolvable parent POM for org.codehaus.mojo:mojo-parent:27: Could not find artifact org.codehaus:codehaus-parent:pom:3 @ org.codehaus.mojo:mojo-parent:27 for project org.codehaus.mojo:clirr-maven-plugin:2.3 for project org.codehaus.mojo:clirr-maven-plugin:2.3 org.apache.maven.project.InvalidProjectModelException: 1 problem was encountered while building the effective model for org.codehaus.mojo:clirr-maven-plugin:2.3 [FATAL] Non-resolvable parent POM for org.codehaus.mojo:mojo-parent:27: Could not find artifact org.codehaus:codehaus-parent:pom:3 @ org.codehaus.mojo:mojo-parent:27 for project org.codehaus.mojo:clirr-maven-plugin:2.3 for project org.codehaus.mojo:clirr-maven-plugin:2.3 at org.apache.maven.project.DefaultMavenProjectBuilder.transformError(Defau ltMavenProjectBuilder.java:174) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:221) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:232) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:239) at org.apache.maven.report.projectinfo.PluginManagementReport$PluginManagem entRenderer.renderSectionPluginManagement(PluginManagementReport.java:20 3) at org.apache.maven.report.projectinfo.PluginManagementReport$PluginManagem entRenderer.renderBody(PluginManagementReport.java:166) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMa venReportRenderer.java:79) at org.apache.maven.report.projectinfo.PluginManagementReport.executeReport (PluginManagementReport.java:80) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRep ort.java:190) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Repo rtDocumentRenderer.java:219) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Def
AW: AW: [mvn] bad artifacs returned
Wayne the answer is simple; look at http://search.maven.org/remotecontent?filepath=org/opensaml/opensaml/2.2.3/opensaml-2.2.3.pom and see how opensaml's dependency on xalan is defined. That is to say if I get you right ::: if I have a dependency on opensaml I need to exclude in my project the transitive dependency to xalan in the dependency to opensaml? Josef -Ursprüngliche Nachricht- Von: Ron Wheeler [mailto:rwhee...@artifact-software.com] Gesendet: Mittwoch, 4. Juli 2012 17:36 An: users@maven.apache.org Betreff: Re: AW: [mvn] bad artifacs returned It appears you have a bad dependency definition. Only you can fix it. The right one is dependency groupIdxalan/groupId artifactIdxalan/artifactId version2.7.1/version /dependency It appears that you have dependency groupIdorg.apache.xalan/groupId artifactIdxalan/artifactId version2.7.1/version /dependency No one knows how you got this included in your effective POM but it is wrong. Excluding all the repos in the world will not fix your problem. Ron On 04/07/2012 10:46 AM, Stadelmann Josef wrote: that is what I want to tell you that you will not find any artifacy at -Ursprüngliche Nachricht- Von: Olivier Lamy [mailto:ol...@apache.org] Gesendet: Mittwoch, 4. Juli 2012 16:37 An: Maven Users List Betreff: Re: [mvn] bad artifacs returned AFAIK xalan has the groupId:artifactId xalan:xalan see http://repo.maven.apache.org/maven2/xalan/xalan/ Maybe you declare the repository http://shibboleth.internet2.edu/downloads/maven2 in your pom (or in a project you are using) 2012/7/4 Stadelmann Josef josef.stadelm...@axa-winterthur.ch: what is returned to an depencey invoked artifact download if the link to the artifact does not hit a .pom or the .jar wanted but is redirected by the receiving repository server to a basic html page explaing the user that artifacts have been moved? i.e. currently for /org/apache/xalan/xalan/2.7.1/xalan-2.7.1.jar /org/opensaml/openws/1.2.2/openws-1.2.2.jar; jargs/jargs/1.0/jargs-1.0.jar i.e. beeing requested to download from Downloading: http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.p om but is then redirected to Downloading: http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/ 2.7.1/xalan-2.7.1.pom where it ends in the nirvana as this EP is redirected http://shibboleth.internet2.edu/ explaing that stuuf has been moved. Josef -- 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: AW: [mvn] bad artifacs returned
Wayne,
the rampart-project.pom has the following.
!-- Other Rampart Dependencies --
dependency
groupIdorg.apache.ws.security/groupId
artifactIdwss4j/artifactId
version${wss4j.version}/version
exclusions
!-- We exclude xalan:xalan as a transitive dependency, but
include
org.apache.xalan:xalan as a direct dependency. This avoids
conflicts with the dependencies of org.opensaml:opensaml
(which uses org.apache.xalan:xalan). --
to say is this is only true for opensaml-2.3.3 but not for opensaml-2.5.1
exclusion
artifactIdxalan/artifactId
groupIdxalan/groupId
/exclusion
/exclusions
/dependency
dependency
groupIdorg.apache.xalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
Josef
-Ursprüngliche Nachricht-
Von: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch]
Gesendet: Donnerstag, 5. Juli 2012 10:08
An: Maven Users List; rwhee...@artifact-software.com
Betreff: AW: AW: [mvn] bad artifacs returned
Wayne
the answer is simple; look at
http://search.maven.org/remotecontent?filepath=org/opensaml/opensaml/2.2.3/opensaml-2.2.3.pom
and see how opensaml's dependency on xalan is defined.
That is to say if I get you right :::
if I have a dependency on opensaml I need to exclude in my project the
transitive dependency to xalan in the dependency to opensaml?
Josef
-Ursprüngliche Nachricht-
Von: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Gesendet: Mittwoch, 4. Juli 2012 17:36
An: users@maven.apache.org
Betreff: Re: AW: [mvn] bad artifacs returned
It appears you have a bad dependency definition.
Only you can fix it.
The right one is
dependency
groupIdxalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
It appears that you have
dependency
groupIdorg.apache.xalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
No one knows how you got this included in your effective POM but it is
wrong.
Excluding all the repos in the world will not fix your problem.
Ron
On 04/07/2012 10:46 AM, Stadelmann Josef wrote:
that is what I want to tell you that you will not find any artifacy at
-Ursprüngliche Nachricht-
Von: Olivier Lamy [mailto:ol...@apache.org]
Gesendet: Mittwoch, 4. Juli 2012 16:37
An: Maven Users List
Betreff: Re: [mvn] bad artifacs returned
AFAIK xalan has the groupId:artifactId xalan:xalan see
http://repo.maven.apache.org/maven2/xalan/xalan/
Maybe you declare the repository
http://shibboleth.internet2.edu/downloads/maven2 in your pom (or in a
project you are using)
2012/7/4 Stadelmann Josef josef.stadelm...@axa-winterthur.ch:
what is returned to an depencey invoked artifact download
if the link to the artifact does not hit a .pom or the .jar wanted
but is redirected by the receiving repository server to a basic
html page explaing the user that artifacts have been moved?
i.e. currently for
/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.jar
/org/opensaml/openws/1.2.2/openws-1.2.2.jar;
jargs/jargs/1.0/jargs-1.0.jar
i.e. beeing requested to download from
Downloading:
http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.p
om
but is then redirected to
Downloading:
http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/
2.7.1/xalan-2.7.1.pom
where it ends in the nirvana as this EP is redirected
http://shibboleth.internet2.edu/ explaing that stuuf has been moved.
Josef
--
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
-
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
AW: [mvn-3] jar files causing problems
Wayne 100%-nail-hit! how did you know that xalan-2.7.1.jar xalan-2.7.1.pom and other stuff . . . when downloaded as maven-artifact from the repository, comes down with such a bunch of HTML rubbish in it? Who deposits xalan-2.7.1.jar é all? Before I deleted the mirrors in my settings.xml, there was local company repository mirror defined. This mirror acts as proxy. And it provided me the same rubbish. So I removed this mirror. So the rubbish is located somehow central and I wonder if I am the only one having this types of troubles. Below my settings.xml Josef ?xml version=1.0 encoding=ISO-8859-1? settings localRepository/dka3/stadelma/.m2/repository/localRepository proxies proxy activetrue/active protocolhttp/protocol hostproxyserver.ch/host port8080/port usernameC770817/username passwordorbxorbx/password nonProxyHosts*.wgrintra.net/nonProxyHosts iddefault/id /proxy /proxies mirrors /mirrors /settings I am going to move now, from my local PC m2/repository, the failing artifacts into the OpenVMS m2/repository. -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Dienstag, 3. Juli 2012 18:28 An: Maven Users List Betreff: Re: [mvn-3] jar files causing problems [WARNING] The POM for org.apache.xalan:xalan:jar:2.7.1 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details Cat the jar file or open it in vi etc. I bet you see an HTTP 503 or a 404 or something other HTML in there instead of the proper binary jar bits. Most likely you have a problem in your settings.xml. Ideally you should set up a proper local Maven Repository Manager (Nexus, Archiva, Artifactory, etc) and leverage it for your jar access. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: [mvn-3] jar files causing problems
Ok Wayne or anybody else we have a corporate repository acting as a proxy to central ! fine - this safes you a lot bandwidth and us time. But what shall I do if I get same rubbish from our repository as well as from central when I ask for pom / jar? for an artifact? I just cleared out my m2/repository and have all downloaded for a small axis2 project from our repository at axa-winterthur. As xalan jars and pom's and others are in error, just rubbish HTML in it, I expected our axa-winterthur repository is bad; Hence I took out from settings.xml the mirror to our repository. Sso I work without any mirror at the moment. But bad luck, our repository is really just a mirror of central and contains the same rubbish for xalan-2.7.1.pom and jar - HTML in a POM and in the jar's while my $ mvn install takes place I observer the following [INFO] [INFO] Building SpezplaService 1.6.1 [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml Downloaded: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml (614 B at 2.2 KB/sec) Downloading: http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom Downloading: http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom [WARNING] Checksum validation failed, expected !DOCTYPE but is 2b52583a26dc455eebec16f29ab9480344f2c5a4 for http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom [WARNING] Checksum validation failed, expected !DOCTYPE but is 2b52583a26dc455eebec16f29ab9480344f2c5a4 for http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom let's take 1 by 1 Downloading: http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom taking this URL into the browser brings you to the shibboleth site and it seems that the expected repository has been relocated to somewhere else. I think, maven cannot handle this bad redirection but sucks up the HTML rubbish instead from this site for the artifacts wanted. What I do not understand is, why xalan-* and a few other artifacts must come down from http://shibboleth.internet2.edu/downloads/maven2/org/apache/ Where can I prevent this? can I? can I black-list proactively the mirrorurlhttp://shibboleth.internet2.edu/downloads/maven2 ? can someone more fluent with that confirm or explain me what happens? any help welcome Josef -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Dienstag, 3. Juli 2012 18:28 An: Maven Users List Betreff: Re: [mvn-3] jar files causing problems [WARNING] The POM for org.apache.xalan:xalan:jar:2.7.1 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details Cat the jar file or open it in vi etc. I bet you see an HTTP 503 or a 404 or something other HTML in there instead of the proper binary jar bits. Most likely you have a problem in your settings.xml. Ideally you should set up a proper local Maven Repository Manager (Nexus, Archiva, Artifactory, etc) and leverage it for your jar access. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[mvn] bad artifacs returned
what is returned to an depencey invoked artifact download if the link to the artifact does not hit a .pom or the .jar wanted but is redirected by the receiving repository server to a basic html page explaing the user that artifacts have been moved? i.e. currently for /org/apache/xalan/xalan/2.7.1/xalan-2.7.1.jar /org/opensaml/openws/1.2.2/openws-1.2.2.jar; jargs/jargs/1.0/jargs-1.0.jar i.e. beeing requested to download from Downloading: http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.p om but is then redirected to Downloading: http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/ 2.7.1/xalan-2.7.1.pom where it ends in the nirvana as this EP is redirected http://shibboleth.internet2.edu/ explaing that stuuf has been moved. Josef
AW: [mvn] bad artifacs returned
To answer part of my question:
if a project has a dependency on xalan, and somehow maven-magic the artifact is
said to be at
http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom
however, there, a redirect happens, and the pom or the jar just ends in the
following content/page
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html xmlns=http://www.w3.org/1999/xhtml;
head
meta http-equiv=Content-Type content=text/html; charset=UTF-8 /
titleInternet2 Shibboleth Project has moved/title
style type=text/css
h3, h4 {margin-bottom:0;}
h3+p {margin-top:0;}
. . .
in fact content of any jar or pom or sha downloaded is the html page explaining
the user that
*** Internet2 Shibboleth Project has moved ***
what is wrong ?
who has to act ?
this for the xalan and maybe many other artifacts expected to be found at the
http://shibboleth.internet2.edu/downloads/maven2 repository server
Josef
-Ursprüngliche Nachricht-
Von: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch]
Gesendet: Mittwoch, 4. Juli 2012 16:28
An: Maven Users List
Betreff: [mvn] bad artifacs returned
what is returned to an depencey invoked artifact download
if the link to the artifact does not hit a .pom or the .jar wanted
but is redirected by the receiving repository server to a basic
html page explaing the user that artifacts have been moved?
i.e. currently for
/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.jar
/org/opensaml/openws/1.2.2/openws-1.2.2.jar;
jargs/jargs/1.0/jargs-1.0.jar
i.e. beeing requested to download from
Downloading:
http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom
but is then redirected to
Downloading:
http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom
where it ends in the nirvana as this EP is redirected
http://shibboleth.internet2.edu/ explaing that stuff has been moved.
Josef
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
AW: [mvn] bad artifacs returned
that is what I want to tell you that you will not find any artifacy at -Ursprüngliche Nachricht- Von: Olivier Lamy [mailto:ol...@apache.org] Gesendet: Mittwoch, 4. Juli 2012 16:37 An: Maven Users List Betreff: Re: [mvn] bad artifacs returned AFAIK xalan has the groupId:artifactId xalan:xalan see http://repo.maven.apache.org/maven2/xalan/xalan/ Maybe you declare the repository http://shibboleth.internet2.edu/downloads/maven2 in your pom (or in a project you are using) 2012/7/4 Stadelmann Josef josef.stadelm...@axa-winterthur.ch: what is returned to an depencey invoked artifact download if the link to the artifact does not hit a .pom or the .jar wanted but is redirected by the receiving repository server to a basic html page explaing the user that artifacts have been moved? i.e. currently for /org/apache/xalan/xalan/2.7.1/xalan-2.7.1.jar /org/opensaml/openws/1.2.2/openws-1.2.2.jar; jargs/jargs/1.0/jargs-1.0.jar i.e. beeing requested to download from Downloading: http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.p om but is then redirected to Downloading: http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/ 2.7.1/xalan-2.7.1.pom where it ends in the nirvana as this EP is redirected http://shibboleth.internet2.edu/ explaing that stuuf has been moved. Josef -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - 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
AW: AW: [mvn] bad artifacs returned
Ron I would not say that - because I just found out that the artifact org/apache/rampart/rampart-project/1.6.2/rampart-project-1.6.1.pom has the following snippet in it. AND My project so far depends on this artifact and it comes from apache ! Now I will check if I can make it without this artifact. rampart-project-1.6.1.pom and rampart-1.6.2 as well repositories repository releases enabledtrue/enabled updatePolicyalways/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicywarn/checksumPolicy /snapshots idopen-saml/id nameOpenSAML/name urlhttp://shibboleth.internet2.edu/downloads/maven2//url /repository /repositories But the trouble makers are not at apache ! they are at EDU shibboleth which moved the artifact repository potentially without telling axis2/rampart folk what they did. what can maven do when a request for an artifact is re-directed into nirvana? Josef -Ursprüngliche Nachricht- Von: Ron Wheeler [mailto:rwhee...@artifact-software.com] Gesendet: Mittwoch, 4. Juli 2012 17:36 An: users@maven.apache.org Betreff: Re: AW: [mvn] bad artifacs returned It appears you have a bad dependency definition. Only you can fix it. The right one is dependency groupIdxalan/groupId artifactIdxalan/artifactId version2.7.1/version /dependency It appears that you have dependency groupIdorg.apache.xalan/groupId artifactIdxalan/artifactId version2.7.1/version /dependency No one knows how you got this included in your effective POM but it is wrong. Excluding all the repos in the world will not fix your problem. Ron On 04/07/2012 10:46 AM, Stadelmann Josef wrote: that is what I want to tell you that you will not find any artifacy at -Ursprüngliche Nachricht- Von: Olivier Lamy [mailto:ol...@apache.org] Gesendet: Mittwoch, 4. Juli 2012 16:37 An: Maven Users List Betreff: Re: [mvn] bad artifacs returned AFAIK xalan has the groupId:artifactId xalan:xalan see http://repo.maven.apache.org/maven2/xalan/xalan/ Maybe you declare the repository http://shibboleth.internet2.edu/downloads/maven2 in your pom (or in a project you are using) 2012/7/4 Stadelmann Josef josef.stadelm...@axa-winterthur.ch: what is returned to an depencey invoked artifact download if the link to the artifact does not hit a .pom or the .jar wanted but is redirected by the receiving repository server to a basic html page explaing the user that artifacts have been moved? i.e. currently for /org/apache/xalan/xalan/2.7.1/xalan-2.7.1.jar /org/opensaml/openws/1.2.2/openws-1.2.2.jar; jargs/jargs/1.0/jargs-1.0.jar i.e. beeing requested to download from Downloading: http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.p om but is then redirected to Downloading: http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/ 2.7.1/xalan-2.7.1.pom where it ends in the nirvana as this EP is redirected http://shibboleth.internet2.edu/ explaing that stuuf has been moved. Josef -- 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: AW: [mvn] bad artifacs returned
And opensaml-2.2.3.pom has a reference as well repositories repository idshibboleth.internet2.edu/id nameInternet2/name layoutdefault/layout urlhttp://shibboleth.internet2.edu/downloads/maven2/url snapshots enabledfalse/enabled /snapshots /repository /repositories Just to become aware that this url is outdated and leads to troubles with maven when used in a download. Don't ask me about the mystery when this will happen. Josef -Ursprüngliche Nachricht- Von: Ron Wheeler [mailto:rwhee...@artifact-software.com] Gesendet: Mittwoch, 4. Juli 2012 17:36 An: users@maven.apache.org Betreff: Re: AW: [mvn] bad artifacs returned It appears you have a bad dependency definition. Only you can fix it. The right one is dependency groupIdxalan/groupId artifactIdxalan/artifactId version2.7.1/version /dependency It appears that you have dependency groupIdorg.apache.xalan/groupId artifactIdxalan/artifactId version2.7.1/version /dependency No one knows how you got this included in your effective POM but it is wrong. Excluding all the repos in the world will not fix your problem. Ron On 04/07/2012 10:46 AM, Stadelmann Josef wrote: that is what I want to tell you that you will not find any artifacy at -Ursprüngliche Nachricht- Von: Olivier Lamy [mailto:ol...@apache.org] Gesendet: Mittwoch, 4. Juli 2012 16:37 An: Maven Users List Betreff: Re: [mvn] bad artifacs returned AFAIK xalan has the groupId:artifactId xalan:xalan see http://repo.maven.apache.org/maven2/xalan/xalan/ Maybe you declare the repository http://shibboleth.internet2.edu/downloads/maven2 in your pom (or in a project you are using) 2012/7/4 Stadelmann Josef josef.stadelm...@axa-winterthur.ch: what is returned to an depencey invoked artifact download if the link to the artifact does not hit a .pom or the .jar wanted but is redirected by the receiving repository server to a basic html page explaing the user that artifacts have been moved? i.e. currently for /org/apache/xalan/xalan/2.7.1/xalan-2.7.1.jar /org/opensaml/openws/1.2.2/openws-1.2.2.jar; jargs/jargs/1.0/jargs-1.0.jar i.e. beeing requested to download from Downloading: http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.p om but is then redirected to Downloading: http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/ 2.7.1/xalan-2.7.1.pom where it ends in the nirvana as this EP is redirected http://shibboleth.internet2.edu/ explaing that stuuf has been moved. Josef -- 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[maven-2.2.1] on building axis2 ./tags/v1.6.1/modules/kernel fails
Dear all,
Since a few days I have on my OpenVMS system this failure when I build
Axis2-1.6.1 using
$ mvn -P java150 -Dtest=false install
I suspect an XML Reader which is not behaving well on OpenVMS (coming
down recently)
OR
From where shall this remote manifest come? And why does the reader say
they a re empty?
Any chance to test this
org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:3005)
I am not building trunk sources but ./tags/v1.6.1 of axis2 and they
build perfect on Windows.
Few weeks ago I did not have problems to build the axis2-kernel on
OpenVMS but now I have.
And adding -fail-never to the mvn command shows at the end that many
modules have the same problem.
But axis2-kernel ist just the first one having problems with this remote
resource manifests and this reader.
Any hints clues welcome
Josef
[INFO]
[INFO] Building Apache Axis2 - Kernel
[INFO]task-segment: [install]
[INFO]
[INFO] [remote-resources:process {execution: default}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error finding remote resources manifests
Embedded error: input contained no data
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error finding
remote resources manifests
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:180)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error finding
remote resources manifests
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.proc
essResourceBundles(ProcessRemoteResourcesMojo.java:1204)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.exec
ute(ProcessRemoteResourcesMojo.java:519)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:694)
... 17 more
Caused by: java.io.EOFException: input contained no data
at
org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:3005)
at
org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3048)
at
org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:142
2)
at
org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1407)
at
org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1105)
at
org.apache.maven.plugin.resources.remote.io.xpp3.RemoteResourcesBundleXp
p3Reader.read(RemoteResourcesBundleXpp3Reader.java:929)
at
org.apache.maven.plugin.resources.remote.io.xpp3.RemoteResourcesBundleXp
p3Reader.read(RemoteResourcesBundleXpp3Reader.java:858)
at
org.apache.maven.plugin.resources.remote.io.xpp3.RemoteResourcesBundleXp
p3Reader.read(RemoteResourcesBundleXpp3Reader.java:872)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.proc
essResourceBundles(ProcessRemoteResourcesMojo.java:1086)
... 20 more
[INFO]
[INFO] Total time: 19 seconds
[INFO] Finished at: Wed Nov 16
AW: [maven-2.2.1] on building axis2 ./tags/v1.6.1/modules/kernel fails
Wayne thank you to get me to the right direction. please take note it Is not my own source I am attempting to build. It is the official released axis2-1.6.1 src reelase which I toke down by $ jsvn co /asf/axis/axis2/java/core/tags/v1.6.1 v1.6.1 AND hence this pom.xml there is the master of all. That is to say, because I expect some source corruption, I deleted yesterday all under /asf/axis/axis2/java/core/tags/v1.6.1 and I toke down a fresh copy from http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.6.1 Unfortunately I got the same failure. axis2-kernel the first one showing up not able to pass a $ mvn install Now - which Manifests do I need to check? If they belong to sources code then catching down sources all again should cure the problem. Is that correct? Josef I can redo a build on a Windows System and check that a $ä mvn -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Mittwoch, 16. November 2011 14:47 An: Maven Users List Betreff: [maven-2.2.1] on building axis2 ./tags/v1.6.1/modules/kernel fails I suspect an XML Reader which is not behaving well on OpenVMS (coming down recently) This isn't the issue. From where shall this remote manifest come? And why does the reader say they a re empty? They might not exist or they might actually be empty. Any chance to test this org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:3005) This isn't the issue. Few weeks ago I did not have problems to build the axis2-kernel on OpenVMS but now I have. What else has changed in the meantime related to this build? Bear in mind the remote resources plugin reaches out over the network to download stuff so things may have changed without you even knowing it. Caused by: org.apache.maven.plugin.MojoExecutionException: Error finding remote resources manifests ... Caused by: java.io.EOFException: input contained no data Seems like Maven cannot find some required manifest file(s) for remote resources plugin. Fix that problem and you should be good to go. Check the project pom files to find usage of remote resources plugin to see what file(s) it is trying to grab during the build. Or ask the Axis2 folks about it. Wayne This was not failing at all few weeks ago. If the build now fails it is as you said, something in the net has changed. I will re-build axis2-1.6.1 on Windows Vista from /asf/axis/axis2/java/core/tags/v1.6.1 and report. But what if Windows Vista can build but my maven on OpenVMS can't build from the same sources and fails building axis2-kernel ? any more clues are welcome. Josef -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Mittwoch, 16. November 2011 14:47 An: Maven Users List Betreff: [maven-2.2.1] on building axis2 ./tags/v1.6.1/modules/kernel fails I suspect an XML Reader which is not behaving well on OpenVMS (coming down recently) This isn't the issue. From where shall this remote manifest come? And why does the reader say they a re empty? They might not exist or they might actually be empty. Any chance to test this org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:3005) This isn't the issue. Few weeks ago I did not have problems to build the axis2-kernel on OpenVMS but now I have. What else has changed in the meantime related to this build? Bear in mind the remote resources plugin reaches out over the network to download stuff so things may have changed without you even knowing it. Caused by: org.apache.maven.plugin.MojoExecutionException: Error finding remote resources manifests ... Caused by: java.io.EOFException: input contained no data Seems like Maven cannot find some required manifest file(s) for remote resources plugin. Fix that problem and you should be good to go. Check the project pom files to find usage of remote resources plugin to see what file(s) it is trying to grab during the build. Or ask the Axis2 folks about it. Wayne
[maven-2.2.1] how to turn-off Visiting non-standard Signature object
using maven to build my small project. [site:site] Parent project loaded from repository: org.apache:apache:pom:10 Downloading: http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent ral/org/apache/apache/10/apache-10-site_en.xml Unable to find resource 'org.apache:apache:xml:site_en:10' in repository central (http://repo1.maven.org/maven2) Downloading: http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent ral/org/apache/apache/10/apache-10-site.xml Unable to find resource 'org.apache:apache:xml:site:10' in repository central (http://repo1.maven.org/maven2) Relativizing decoration links with respect to project URL: http://maven.apache.org Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0 skin. Generating Distribution Management report--- Maven Project Info Reports Plugin 2.4 Generating About report--- Maven Project Info Reports Plugin 2.4 Generating Dependencies report--- Maven Project Info Reports Plugin 2.4 Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object Visiting non-standard Signature object . . . . many more to follow How can I turn this off? I know sombody has asked this question already, unfortunately I cant find the response or a hint to the error message in the mail archives. Josef
AW: [maven-2.2.1] on building axis2 ./tags/v1.6.1/modules/kernel fails
Sorry Wayne,
I forgot to write that I have re-posted / commented this to the axis2-users
list.
But if error messages would be a bit more helpful i.e. telling the expected
path and filename either local or remote, many problem would even NOT hit your
desk.
Thank you anyway
Josef
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:wayne...@gmail.com]
Gesendet: Mittwoch, 16. November 2011 17:45
An: Maven Users List
Betreff: Re: [maven-2.2.1] on building axis2 ./tags/v1.6.1/modules/kernel fails
please take note it Is not my own source I am attempting to build. It is the
official released axis2-1.6.1 src reelase which I toke down by
$ jsvn co /asf/axis/axis2/java/core/tags/v1.6.1 v1.6.1
As stated previously on emails of this topic, the Maven Users list
cannot be expected to be experts on all software being built around
the world with the Maven tool. You truly must ask these questions on
the Axis2 Developer (or User) list first and then as a last resort
come to us for help. Surely the Axis2 Developers have a better
understanding of their own build, right?
Unfortunately I got the same failure. axis2-kernel the first one showing up
not
able to pass a $ mvn install
Now - which Manifests do I need to check? If they belong to sources code
then catching down sources all again should cure the problem. Is that correct?
I checked the pom for axis2-kernel and it has a plugin section as follows:
plugin
artifactIdmaven-remote-resources-plugin/artifactId
executions
execution
goals
goalprocess/goal
/goals
configuration
resourceBundles
resourceBundleorg.apache.axis2:axis2-resource-bundle:${project.version}/resourceBundle
/resourceBundles
/configuration
/execution
/executions
/plugin
That led me to the pom for axis2-resource-bundle which shows:
plugin
artifactIdmaven-remote-resources-plugin/artifactId
executions
execution
goals
goalbundle/goal
/goals
/execution
/executions
/plugin
So then I went and looked at the MRRP plugin documentation (aka RTFM):
http://maven.apache.org/plugins/maven-remote-resources-plugin/
This tells me the following:
remote-resources:bundle creates the resource bundle manifest required
by the remote resource bundle processing. The manifest file,
$basedir/target/classes/META-INF/maven/remote-resources.xml, is
created from the contents of the src/main/resources directory.
So now we go back full circle to your error message:
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
finding remote resources manifests
...
Caused by: java.io.EOFException: input contained no data
This suggests to me that the axis2-resource-bundle artifact that you
have built in OpenVMS does not, for whatever reason, contain the
remote-resources.xml manifest file which is required for MRRP to
properly utilize the artifact. Or perhaps the artifact at that
coordinate does not even exist, I'm unsure which is correct.
You should find the axis2-resource-bundle artifact in your local repo
cache, open it up (unzip it) and look for a file named
META-INF/maven/remote-resource.xml inside. If that file does not exist
or is empty, that would seem to be your problem.
In all likelihood, there is something in the Java coding of MRRP which
is incompatible with your OpenVMS system (not really a surprise). You
should pull down the source code of MRRP and analyze it. If you find
and fix a defect, please donate your patch back to the Maven JIRA so
it can be included in a future release of MRRP.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
AW: Problems with MAVEN's-ANT on OpenVMS
Hi Wayne
Thank you Wayne for this excellent Analysis. If a routine belonging to the file
system returns something badly,
there is a little chance to influence by a logical JAVA$FILENAME_CONTROL which
can be set to so many values
used to control filename encodings, particular how to deal with dot's in file
names.
Josef
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:wayne...@gmail.com]
Gesendet: Donnerstag, 20. Oktober 2011 23:51
An: Maven Users List
Betreff: Re: Problems with MAVEN's-ANT on OpenVMS
With knowing the details about our environment
would you expect that Lucene written in clean Java
is not operating on such a platform?
Without a comprehensive analysis of the source code for Lucene (and
potentially, some or all of its dependencies) it is impossible to say
anything conclusive about how well it may operate on OpenVMS or any
other operating system except for those explicitly supported (and
tested) by the dev team. Java isn't truly write-once run-anywhere,
despite such claims ~10-15 years back.
I looked at your stacktrace and the problem seemed to be related to a
NumberFormatException thrown by java.lang.Long.parseLong() that is not
being caught and handled by Lucene:
Caused by: java.lang.NumberFormatException: For input string: 1.
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Long.parseLong(Long.java:419)
at
org.apache.lucene.index.SegmentInfos.generationFromSegmentsFileName(SegmentInfos.java:199)
I found a Lucene JIRA issue that is loosely related:
https://issues.apache.org/jira/browse/LUCENE-3008
Looks like line 211 in trunk is the issue (was line 199 in the stacktrace):
http://svn.apache.org/viewvc/lucene/dev/trunk/lucene/src/java/org/apache/lucene/index/SegmentInfos.java?view=markup
The source code is:
return Long.parseLong(fileName.substring(1+IndexFileNames.SEGMENTS.length()),
Character.MAX_RADIX);
A quick look at the Java API shows:
http://download.oracle.com/javase/1,5.0/docs/api/java/lang/Long.html#parseLong(java.lang.String,%20int)
An exception of type NumberFormatException is thrown if any of the
following situations occurs:
* Any character of the string is not a digit of the specified
radix, except that the first character may be a minus sign '-'
('\u002d') provided that the string is longer than length 1.
The decimal character in the string 1. is not valid in the radix
defined by Character.MAX_RADIX. So, you'll need to figure out where
that filename of 1. is coming from -- either OpenVMS or Lucene --
and somehow get rid of the decimal in the filename. Or just rename
that file from 1. to simply 1 in your filesystem.
Without access to an OpenVMS system and having no real understanding
of Lucene's internals, I can't really look into it any more at this
point. You probably need to email the Lucene Users list and ask if
anyone has successfully gotten it to run on OpenVMS (I'm guessing not)
and get things patched up before you can make more progress with
getting Nexus running on it. Or take the more reasonable approach and
simply install Nexus on a Windows box in your office. ;-)
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
AW: Problems with MAVEN's-ANT on OpenVMS
Thank you Benson pointing me into the right direction. Was an oversight on my site, that yet another product got involved. Lucene So I have to download yet another hopefully open source project and build it on OpenVMS We attempted to run the Sonatype nexus war on our Apache Tomcat/5.5.26 AS on top of JVM Version 1.6.0-2.p1 from Hewlett-Packard Company on OpenVMS 8.4 patched to latest level in a ia64 OS Architecture environment to get your right With knowing the details about our environment would you expect that Lucene written in clean Java is not operating on such a platform? -Ursprüngliche Nachricht- Von: Benson Margulies [mailto:bimargul...@gmail.com] Gesendet: Donnerstag, 13. Oktober 2011 14:58 An: Maven Users List Betreff: Re: Problems with MAVEN's-ANT on OpenVMS Just to put the cork in this, the backtrace at the end proves that Apache Lucene doesn't work in your OpenVMS environment. Words cannot express my lack of surprise. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: default auth for settings.xml
This is very clean clear statement! Please make maven pointing this out to the user to use a repo if it is so wasteful. I am by far not an expert of maven or repositories, but I agree with you, it gets much more simple as all proxy connections and all connections to external servers can be handled at one point, the repository in the role of a proxy So far I did not manage to make nexus reach out through our firewall because I do not know how to pass such a thing as -Dhttp.auth.preference=Basic to our proxy server on a attempt to take central into service. (Sorry a nexus issue) Josef -Ursprüngliche Nachricht- Von: Ron Wheeler [mailto:rwhee...@artifact-software.com] Gesendet: Donnerstag, 13. Oktober 2011 20:24 An: users@maven.apache.org Betreff: Re: default auth for settings.xml On 13/10/2011 2:06 PM, Tommy Chheng wrote: Do you have Nexus or another repo installed? If not, do that first. That will fix your settings.xml problem in a much more sensible way and make your whole life a lot easier. Using Maven without a repo is a horribly wasteful thing to do. Ron Hi, I have a few servers in the settings.xml where the username/password is the same for all server ids. is there a way to set a default username/password so i don't have to add a new server xml block every time? 26server 27idscala-tools.org/id 28usernamet/username 29passwordXXX/password 30/server 31server 32idsweble/id 33usernamet/username 34passwordXXX/password 35/server 36/servers -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
AW: How to install MAVEN on Windows 7
But if windows claims as in this case that the command is not known, then the PATH does not know the .exe, .com or .bat making the command and maven has ./bin/mvn.bat hence you have to add (as one points out previously %M2_HOME%\bin; to the PATH and there best to the SYSTEM not the USER Josef -Ursprüngliche Nachricht- Von: Eric Kolotyluk [mailto:eric.koloty...@gmail.com] Gesendet: Freitag, 14. Oktober 2011 18:58 An: users@maven.apache.org Betreff: Re: How to install MAVEN on Windows 7 I use Maven on several Windows 7 systems and have had no real problems after setting up the environment variables properly. Other than that, Maven is just like any other Java application. In particular make sure maven\bin is on your Path or Path2 environment variables. Do you know how to set those in Windows? Cheers, Eric Cheers, Eric On 2011-10-13 7:23 PM, Wayne Fay wrote: What environment variables do I modify for Windows 7? The system does not recognize the mvn -version command. What directions did you follow? What commands did you execute? I am aware of nothing special about installing on Win7. I think you simply skipped/missed a step or two in the documentation. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: How does Maven use timestamps?
I am havening a very similar thing which I would say fosters what you say. I know I have a somehow unsupported maven as I runs to some degree on OpenVMS But, I would be glad how experts explain the following: $ cd /dka3/sw-projekte/asf.axis/axis2/java/core/tags/v1.6.0 $ mvn clean install fails for module/codegen in the surefire test $ mvn clean install --projects module/maven runs perfect I guess, as I am not a maven expert, that in the first mvn case the reactor gets engaged and it set-up/delivers/passes/invokes something different whereas in the second case the reactor is bypassed and the command reaches the executor on duty very straight. Josef -Ursprüngliche Nachricht- Von: Dieter Van de Walle [mailto:dieter.vandewa...@newtec.eu] Gesendet: Freitag, 14. Oktober 2011 09:30 An: users@maven.apache.org Betreff: How does Maven use timestamps? Hello, For a while now, I have noticed sporadic problems when using Maven. For example: a maven build results in errors on a project. If I then check out the project into another directory, the project builds without any problems. The content of both directories is identical. I use 'mvn clean install' . More in general: if I have problems like these, a touch of all files in the project seems to resolve them. Therefore it seems to me that the file properties seems to be the cause. I'm suspecting timestamps, because a touch always magically solves these problems. However I don't understand why this could make a difference? If I run a 'mvn clean' or just manually remove the target directory, everything should be rebuilt, and timestamps shouldn't matter right? However this seems to be the case. I get the impression some files are sometimes skipped for compilation by maven, causing errors. Another thing that could also be a factor is that I am using GIT to manage the project files in the faulty directory. However I don't really see how this could influence the build ... Does this ring a bell with anyone? Can anyone point me in the right direction on solving this issue? Maven version info below. Best regards, Dieter Van de Walle -- Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /opt/apache-maven-3.0.3 Java version: 1.6.0_26, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre Default locale: nl_BE, platform encoding: UTF-8 OS name: linux, version: 2.6.38-11-generic-pae, arch: i386, family: unix Discover our world of Innovation and Product leadership - bePART, Engineered for partner value Meet us @ www.newtec.eu/events *** e-mail confidentiality footer *** This message and any attachments thereto are confidential. They may also be privileged or otherwise protected by work product immunity or other legal rules. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore is in no way liable for any errors or omissions in the content of this message, which may arise as a result of e-mail transmission. If verification is required, please request a hard copy.
AW: Problems with MAVEN's-ANT on OpenVMS
Hi Wayne my comment ++ below -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Dienstag, 11. Oktober 2011 19:36 An: Maven Users List Betreff: Re: Problems with MAVEN's-ANT on OpenVMS Question: Given mavens settings.xml has the proxy info's does maven tell ant about this proxy information? If yes, where in code and how? I don't know. I would expect the answer is in the maven-antrun-plugin source code, and having just glanced at it now, I don't see any specific location where such proxy information is handed off to Ant (but it may be happening despite not seeing it obviously stated via system properties or something): http://svn.apache.org/viewvc/maven/plugins/tags/maven-antrun-plugin-1.6/src/main/java/org/apache/maven/plugin/antrun/AntRunMojo.java?view=markup If you determine that proxy information is not being passed to Ant, and you patch this code to pass proxy info to Ant, please contribute it back via JIRA for the benefit of other users. ++ will do so I should also mention the setproxy Ant task which may be an easier route to a solution for you: http://ant.apache.org/manual/Tasks/setproxy.html ++ this works but needs to be added to pom's with an ant section and build.xml's. And it works! So we just look for a more central not project dependent solution Question: how does maven get best informed about the preferred authentication schemas to be used by the proxy server i.e. -Dhttp.auth.preference=Basic as described by the ORACLE documentation for JAVA and at many other places. There appears to be an open JIRA related to this specifically: http://jira.codehaus.org/browse/MNG-3049 ++ OK - still unclear for me if this is a application, like ant or maven issue, or a JAVA/JDK/JVM problem; hence not clear, hence not fixed. Question: If ant is first and picks up proxy info and works would you expect for maven that ant tells maven about proxy info to be used? I don't understand this question. Can you please try again, and perhaps explain things more? ++ sometimes inside an ant target maven gets called by a mvn . . . task/macro ; in this context, ANT already knows about the proxy info. But how is this information passed to maven now? If maven retrieves proxy setting from MAVEN_OPTS environment variable under any circumstances, then fine, if not, how is this passed to maven from a ant section in a pom? So the question may be allowed: does maven pick-up MAVEN_OPTS proxy information when called from within a ANT task? BTW: I took the latest sources of nexus down to my Vista PC. Tried to build it as I do with maven and axis2 and it failed! Why do you insist on building everything from sources? ++ because on OpenVMS sometimes one can just not refer to documents which are written for windows and Linux users. ++ because debugging and walking through code even at maven or ant or axis2 has brought many insight into what is not documented. i.e. the axis2 time-out-constant for a servicegroupId was just not seconds as said in a axis2.xml and documented but milliseconds, and since we know this from debugging the rest was a sniff. The rest of us use the binaries directly with no complaints. As Stephen already stated, you should just pull down the Nexus binary and run it on Windows, then point your OpenVMS Maven at it. ++ that has been done meanwhile; ++ further to that, there was a maven team established at our company some two years ago, but long time, we could not use Sonatype Nexus as a proxy or repository as it was just not working well enough. Meanwhile it works and I have tried again and changed only the m2.url in a ANT library.properties files and had a great better experience. This has fix my proxy issues; but there are others out in the crowd depending on proxy setups working well. Also if Ant with the get needs to access any other files outside a nice nexus proxy server, it still needs a working proxy infrastructure. BTW: Then I took the latest binary version of a nexus-webapp.war down to my OpenVMS, I untared it on OpenVMS as we do with Axis2 or maven. It fails during startup on Tomcat and Java 6.0. Many things get up as one can see in tomcat logs attached as text file; but it fails. I am not surprised that Nexus fails to load on OpenVMS. I bet you are the first person (in the world, perhaps) to attempt such a thing. Feel free to communicate that log to Sonatype directly and they may be able to work with you to fix their code so it runs properly -- the Maven Users list is not the right place for such complaints/discussion. ++ Sorry and I agree 100% (was just an example) I did look at the log and it has a NFE for input string 1. which seems to be the root problem: Caused by: java.lang.NumberFormatException: For input string: 1. at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Long.parseLong(Long.java:419) at
AW: Problems with MAVEN's-ANT on OpenVMS
Thank you Barrie, thank you Wayne for your excellent articles. Now there is hope to get maven and ant build axis2 and maven and our own stuff on OpenVMS. The issues we are faced with are so many fold: And to complicate things even more. We sit behind firewalls and maven and ant with a get task to build i.e.Axis2, needs to be set with proper proxy info including http.auth.preference=Basic, not supported straight by Ant or maven but needs to go as a hint to our Microsoft proxy server to not start negotiating authentication schemas unable to be handled by the client calling. We have a working ant version of Ant, that is to say, by a bash shell script we launch our own AntClassLoader which creates an Authenticator to pass username and password and then calls the real AntLoader;;; BTW: Username and Password for the proxy server is never picked up by default from JAVA args as said in documents at various places. We have investigated Ant code for that. It is picked up by ant code only if you pass the --diagnostics switch to Ant and makes people think that all is fine, but in reality for a get task Ant does not pick proxy info under normal operation. This circumstance alone has made us work for some days. Also to be honest to Ant, it might be a Java JVM or java.net problem. Which org has to deal with such issues? Which org should fix it once for ever? Or who has to deal with such issues? The Ant-, or Maven-, or Java- or any of the mayn thousand jar-developers. We like to setup JAVA Arguments like -Dhttp.proxy.User=name -Dhttp.proxy.Password=xxx. So all is fine if we pass this as Ant arguments from inside a build.xml. BUT we do not like to change the ant build.xml files for each product like axis2 or maven. And we do not like to modify each maven pom for the same reason. We prefer a more central place. This is the case for maven with its settings.xml (except http.auth.preference=Basic is not foreseen by maven). It is always the same: what is used where and when and under which circumstances ?! Question: Given mavens settings.xml has the proxy info's does maven tell ant about this proxy information? If yes, where in code and how? Question: how does maven get best informed about the preferred authentication schemas to be used by the proxy server i.e. -Dhttp.auth.preference=Basic as described by the ORACLE documentation for JAVA and at many other places. Question: If ant is first and picks up and works would you expect for maven that ant tells maven about proxy info to be used? BTW: thanks for the pointers to the books. BTW: I took the latest sources of nexus down to my Vista PC. Tried to build it as I do with maven and axis2 and it failed! BTW: Then I took the latest binary version of a nexus-webapp.war down to my OpenVMS, I untared it on OpenVMS as we do with Axis2 or maven. It fails during startup on Tomcat and Java 6.0. Many things get up as one can see in tomcat logs attached as text file; but it fails. I did so because Wayne Fay said to work with nexus simplifies much of this repository and cache management. And I beleave you. And I like the idea very much and was reading a lot about nexus and repositories immediately. But in reality we have now one more product on OpenVMS which we need to make work first; where ever the problem is. Is it JAVA from HP? or any of the jar files issuing a shell script? or the use of exported environment variable of which bash under OpenVMS does not know anything by default? It is a tedious process to make such complex environments work; Josef -Ursprüngliche Nachricht- Von: Barrie Treloar [mailto:baerr...@gmail.com] Gesendet: Mittwoch, 5. Oktober 2011 00:45 An: Maven Users List Betreff: Re: Problems with MAVEN's-ANT on OpenVMS On Wed, Oct 5, 2011 at 3:43 AM, Wayne Fay wayne...@gmail.com wrote: May I ask you a favor and lead me to a document describing how we can make maven using our own ant 1.7.1, as we had changes in ANT 1.7.1 specifically for OpenVMS, those catching logical, and generating a temporary file where all the many hundred arguments being passed today to JAVA / JVM are stored in. I already told you what to do but here are the complete steps: Plus, did you try google? http://www.google.com/search?q=maven+ant+plugin+change+version+of+ant Some of the steps that Wayne has kindly outlined are not particular to your problem. They are the knowledge you need to run Maven effectively at your company. I highly recommend that you read the freely available books at http://maven.apache.org/articles.html We can't wave a magic wand for you to grasp some of the more important and complicated concepts. Your going to have to help us by helping yourself first. Additionally, if you think these steps are important and not well documented, I invite you to document them for the benefit of others. As a user you should have access to http://docs.codehaus.org/display/MAVENUSER/Home But I think the best
AW: Problems with MAVEN's-ANT on OpenVMS
Hello Wayne
Thank you.
Wayne, I understand by far not all in maven , who does?
But thanks for the reply, it clears a bit of the clouds.
May I ask you a favor and lead me to a document describing how we can make
maven using our own ant 1.7.1,
as we had changes in ANT 1.7.1 specifically for OpenVMS, those catching
logical, and generating a temporary
file where all the many hundred arguments being passed today to JAVA / JVM are
stored in.
can we make maven use our ant by changing pom.xml or better have a more global
approach/setup such as in a settings.xml?
We need maven to execute our own ant 1.7.1 for now as this is the only way we
can pass 100+ arguments to JAVA/JVM on OpenVMS
The current version of ANT, which maven-2.2.1 uses by default, is not doing
this right for OpenVMS.
And hence we run into the error shown in the trace below, which is from a
AntSetup.xml calling the real build-wsdls.xml for test purpose.
It is even not executing correct just when just asked to execute an ordinary
bash shell ls command.
And to be positive: We would not take this challenge and work and work just to
get maven build maven and axis2 if we would not love maven!
But with openvms it is sometimes a night mare.
And it is a nightmare if maven developers use Unix scripts when they could use
JAVA statements for the same.
Today we have maven build 6/7 of apache-maven-2.2.1 from the bootstrap, and we
have maven-2.2.1 build axis2-1.6.0 to about 70%
And we see the day when we have a working environment on OpenVMS as many of you
have on Linux and Solaris and Windows;
And we are not from HP owning OpenVMS but are just ordinary customers counting
on open source communities!
And we do not yet have a nexus e all repository manager!
This will end in a next port to OpenVMS !!!
So we need to keep it simple and know how to deploy our own ANT into what you
call mavens cache.
Josef.Stadelmann@
Axa-winterthur.ch
[INFO] Executing tasks
[echo] Building WSDLs...
Overriding previous definition of reference to maven.dependency.classpath
[echo] Running on OpenVMS
[echo] Inside
/dka3/sw-projekte/asf/axis/axis2/java/core/tags/v1.6.0/modules/codegen/AntSetup.xml.
ANT Version = ${antversion}
not-CustomAnt:
CustomAnt:
[echo] Executing /bin/sh -c 'export ANT_OPTS=-Dhttp.auth.preference=Basic
-Dhttp.proxyHost=bcproxyserver.ch.winterthur.com -Dh
ttp.proxyPort=8080 -Dhttp.proxyUser=C770817 -Dhttp.proxyPassword=orbxorbx; ls
-l'
[exec] %DCL-W-NOCOMD, no command on line - reenter with alphabetic first
character
[exec] %DCL-W-NOCOMD, no command on line - reenter with alphabetic first
character
[exec] Result: 229552
all:
[INFO] Executed tasks
[INFO] [resources:copy-resources {execution: copy-templates}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 7 resources
[INFO] Copying 1 resource
[INFO] Copying 1 resource
[INFO] Copying 1 resource
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] Copying 10 resources
[INFO] Copying 2 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 4 source files to
/dka3/sw-projekte/asf/axis/axis2/java/core/tags/v1.6.0/modules/codegen/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory:
/dka3/sw-projekte/asf/axis/axis2/java/core/tags/v1.6.0/modules/codegen/target/surefire-reports
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There are test failures.
Please refer to
/dka3/sw-projekte/asf/axis/axis2/java/core/tags/v1.6.0/modules/codegen/target/surefire-reports
for the individual te
st results.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 40 seconds
[INFO] Finished at: Tue Oct 04 18:30:21 CEST 2011
[INFO] Final Memory: 25M/618M
[INFO]
bash$
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:wayne...@gmail.com]
Gesendet: Montag, 3. Oktober 2011 16:31
An: Maven Users List
Betreff: Re: Problems with MAVEN's-ANT on OpenVMS
I was never expecting that maven is using it's own ANT !
Its not using its own Ant. It simply does not use the Ant that you
previously installed but rather uses the Ant jars directly from its
cache.
Now with maven it just did not work and the reason why is: Maven uses it's
own ANT lib files !!!
I was not expecting that maven reinvents the wheel.
It doesn't. This is a failure of
Problems with MAVEN's-ANT on OpenVMS
Dear maven community,
I was never expecting that maven is using it's own ANT !
We are facing problems with ANT_171 on OpenVMS;
ANT 1.7.1 was unable to do a GET properly when located behind a firewall !
For that to reach out to the world it is said on many places / document that
one can
set the following JVM switches to pass / reach out through a Firewall
And now it comes:
For ANT one is told to use
-Dhttp.proxyHost=myproxy
-Dhttp.proxyPort=8080
-Dhttp.proxyUser=Sepp
-Dhttp.proxyPassword=mypassword
And different so one cannot use a common variable for booth
For MAVEN one is told to use
-Dhttp.proxyhost=myproxy
-Dhttp.proxyport=8080
-Dhttp.proxyuser=Sepp
-Dhttp.proxypassword=mypassword
ANT does not take http.proxyUser and http.proxyPassword into account!
For that to correct we added an Authenticator to our AntClassLoader.class ANT,
reading http.proxyUser and http.proxyPassword from the system environment and
setting up the Authenticator.
So we wrote our own AntClassLoader.class which creates an Authenticator and
then calls the AntLauncher.class from the installed ANT version.
AND it works and standard ANT_171 was able to execute GET's to remote files
through the firewall without a need to justify al and every build.xml
Now with maven it just did not work and the reason why is: Maven uses it's own
ANT lib files !!!
I was not expecting that maven reinvents the wheel.
So then - be it as it is --- how can we enforce maven to use a particular
installed ANT version and not use the maven-internal ANT ?
And how can we debug ANT when called from maven. Maven has a mvnDebug.bat and
we can make a antDebug.bat but this would imply that ANT is not forked somehow
but called via a command.
Josef
And by text below, this gets fostered by Philippe which helps me a lot to make
maven install Axis2 on OpenVMS
-Ursprüngliche Nachricht-
Von: Philippe Vouters [mailto:philippe.vout...@laposte.net]
Gesendet: Donnerstag, 29. September 2011 16:36
An: Stadelmann Josef
Betreff: Shit !!!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josef,
Maven downloads its own 1.8.1 Ant code to execute this attached pom.xml ant
tasks.
I shall have to find out a way Maven uses my own ant-1.7.1 jars. This is still
in the goal of Maven/Ant Axis-2 build.
First I shall try to modify the pom.xml so that it invokes ant to execute a
build.xml as suggested as best in the plexus code extract you sent me.
Philippe
bash$ export M2_HOME=$HOME/apache-maven-2.2.1 bash$ mvn install ...
Downloading:
http://repo1.maven.org/maven2/org/apache/ant/ant-nodeps/1.8.1/ant-nodeps-1.8.1.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/ant/ant-parent/1.8.1/ant-parent-1.8.1.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/ant/ant/1.8.1/ant-1.8.1.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/ant/ant-launcher/1.8.1/ant-launcher-1.8.1.pom
Downloading:
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar
Downloading:
http://repo1.maven.org/maven2/org/apache/ant/ant-nodeps/1.8.1/ant-nodeps-1.8.1.jar
Downloading:
http://repo1.maven.org/maven2/org/apache/ant/ant/1.8.1/ant-1.8.1.jar
Downloading:
http://repo1.maven.org/maven2/org/apache/ant/ant-launcher/1.8.1/ant-launcher-1.8.1.jar
...
[INFO] [antrun:run {execution: compile}] [INFO] Executing tasks
main:
[echo] compile classpath: /PHV/PHV/target/classes
[echo] runtime classpath: /PHV/PHV/target/classes
[echo] test classpath:
/PHV/PHV/target/test-classes:/PHV/PHV/target/clas
ses
[echo] plugin classpath:
/PHV/PHV/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar:/PHV/PHV/.m2/repository/org/apache/ant/ant-
nodeps/1.8.1/ant-nodeps-1.8.1.jar:/PHV/PHV/.m2/repository/org/apache/ant/ant/1.8
.1/ant-1.8.1.jar:/PHV/PHV/.m2/repository/org/apache/ant/ant-launcher/1.8.1/ant-l
auncher-1.8.1.jar:/PHV/PHV/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar
...
bash$ env
TERM=vt100-80
ANT_HOME=/PHV/PHV/ANT_171
HOSTTYPE=ia64
PATH=/PHV/PHV/apache-maven-2.2.1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/
usr/bin:/sbin:/bin:.
HOME=/PHV/PHV
SHELL=bash
USER=PHV
JAVA_HOME=/java_kit/jre
M2_HOME=/PHV/PHV/apache-maven-2.2.1
OSTYPE=VMS
SHLVL=1
_=/bin/env
bash$ alias
alias l.='ls -d .* --color=auto'
alias ll='ls -l --color=auto'
alias ls='ls --color=auto'
alias vi='vim'
- --
Philippe Vouters (Fontainebleau/France)
URL: http://vouters.dyndns.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6EgkwACgkQsUYBDUbOpdqlXQCfS15I85FqbNOWVzNlAcT+qPVX
swAAn2LkwBLcMNZoXKddrvb8wtZqF7i5
=J8k2
-END PGP SIGNATURE-
project
modelVersion4.0.0/modelVersion
artifactIdmy-test-app/artifactId
groupIdmy-test-group/groupId
version1.0-SNAPSHOT
AW: hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:1018) FAILS on OpenVMS
In other words, dear maven-community,
the check is platform dependent working or failing,
hence useless in a OpenVMS or Windows 7 environment, and maybe others too!
But Java is code once run everywhere, isn't it?
Josef
Von: Lucas Persson [mailto:lucas.pers...@oracle.com]
Gesendet: Dienstag, 28. Juni 2011 09:32
An: Maven Users List
Betreff: Re:
hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:1018) FAILS
on OpenVMS
Hi
I have notice that the below check fails on windows 7 if the file you copy is a
windows symlink (not a shortcut).
The length on a symlink is not the lenght of the file which the symlink points
to so the check will always fail.
I think this check is kind of useless. Sure one should get IOException if the
copy fails?
/Lucas
On 06/27/2011 09:23 PM, Hervé BOUTEMY wrote:
after the source,
if ( source.length() != destination.length() )
{
final String message = Failed to copy full contents from +
source + to + destination;
throw new IOException( message );
}
did you try to write a unit test?
Regards,
Hervé
Le lundi 27 juin 2011, Stadelmann Josef a écrit :
I reported what I see some time agoe.
What ever I do with maven-2.2.1 and co
It fails when it has no reason to fail.
The greate thing is to say; when ever this copy full content error or
any similarcopy full content errors occur, the copy took place perfect
and diff doesn't show any diffs.
So why is plexus in error at that point and as a consequence lets maven
look old and BUILD fail?
-Dfile.encoding= ISO-8859-1 has no impact and fails as well at the same
position (just for info)
Otherwhise when I see how much of maven-2.2.1 works with OpenVMS, it
would be very promising if not this little tiny bits would play such a
fatal bad role.
Why does this guy do so badly
hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:1018)
Josef
IA64mvn -e install
0: DKB3:[JAVA$150.BIN]JAVA$JAVA.EXE;1
1: -Dclassworlds.conf=/dkb3/apache-maven-2_2_1/bin/m2.conf
2: -Duser.home=/dkb3/stadelma
3: -Dmaven.home=/dkb3/apache-maven-2_2_1
4: -Dhttp.auth.preference=Basic
5: -Dfile.encoding=UTF-8
6: org.codehaus.classworlds.Launcher
7: -e
8: install
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] Building SVNKit
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/dkb3/sw-projekte/asf/svnkit/tags/1_3_3/src/main/resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/dkb3/sw-projekte/asf/svnkit/tags/1_3_3/src/test/resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[INFO] [surefire:test {execution: default-test}]
[INFO] No tests to run.
[INFO] [jar:jar {execution: default-jar}]
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/dkb3/sw-projekte/asf/svnkit/tags/1_3_3/target/svnkit-1.3.3.jar to
/dkb3/stadelma/.m2/repository/org/tmatesoft/svn
kit/svnkit/1.3.3/svnkit-1.3.3.jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error installing artifact's metadata: Error installing metadata:
Error copying POM to the local repository.
Failed to copy full contents from
/dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml to
/dkb3/stadelma/.m2/repository/org/tmatesoft/svn
kit/svnkit/1.3.3/svnkit-1.3.3.pom
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error installing
hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:1018) FAILS on OpenVMS
I reported what I see some time agoe.
What ever I do with maven-2.2.1 and co
It fails when it has no reason to fail.
The greate thing is to say; when ever this copy full content error or
any similarcopy full content errors occur, the copy took place perfect
and diff doesn't show any diffs.
So why is plexus in error at that point and as a consequence lets maven
look old and BUILD fail?
-Dfile.encoding= ISO-8859-1 has no impact and fails as well at the same
position (just for info)
Otherwhise when I see how much of maven-2.2.1 works with OpenVMS, it
would be very promising if not this little tiny bits would play such a
fatal bad role.
Why does this guy do so badly
hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:1018)
Josef
IA64mvn -e install
0: DKB3:[JAVA$150.BIN]JAVA$JAVA.EXE;1
1: -Dclassworlds.conf=/dkb3/apache-maven-2_2_1/bin/m2.conf
2: -Duser.home=/dkb3/stadelma
3: -Dmaven.home=/dkb3/apache-maven-2_2_1
4: -Dhttp.auth.preference=Basic
5: -Dfile.encoding=UTF-8
6: org.codehaus.classworlds.Launcher
7: -e
8: install
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] Building SVNKit
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/dkb3/sw-projekte/asf/svnkit/tags/1_3_3/src/main/resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/dkb3/sw-projekte/asf/svnkit/tags/1_3_3/src/test/resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[INFO] [surefire:test {execution: default-test}]
[INFO] No tests to run.
[INFO] [jar:jar {execution: default-jar}]
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/dkb3/sw-projekte/asf/svnkit/tags/1_3_3/target/svnkit-1.3.3.jar to
/dkb3/stadelma/.m2/repository/org/tmatesoft/svn
kit/svnkit/1.3.3/svnkit-1.3.3.jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error installing artifact's metadata: Error installing metadata:
Error copying POM to the local repository.
Failed to copy full contents from
/dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml to
/dkb3/stadelma/.m2/repository/org/tmatesoft/svn
kit/svnkit/1.3.3/svnkit-1.3.3.pom
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error installing
artifact's metadata: Error installing metadata: Error copyi
ng POM to the local repository.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:180)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
installing artifact's metadata: Error installing metadata: Error co
pying POM to the local repository.
at
SVN can not revert - VISTA can not copy it
If I would be a maven developer I would make this path a bit more longer to really see others go into problems as well as I do on my Vista PC; Error restoring text for 'E:\asf\maven\maven-3\nb_trunk\maven-embedder\src\test\error-reporting-p rojects\ext-plugin-artifact-missing\local-repo\org\apache\maven\errortes t\ext-plugin-artifact-missing-maven-plugin\1\ext-plugin-artifact-missing -maven-plugin-1.pom' AIt looks to me as this was never said long ago by many other developers. :-( I toke maven down using SVN checkout to a trunk, then I tried to just copy it to a different directory and VISTA faild because the path is just too long. Josef :-(
AW: Hello World? And More
Hello Team My problem goes into the same direction, hence no new thread; When I first saw this archetype:generate , I was about to try it immediately. ON PC ON OpenVMS I am using on the PC, maven 2.2.1 and my observations are: I get 41 options to chose from offered; I use 15 and well it works; initially with some downloads 15, is OK and GENERATES a Project mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=com.mycompany.app -DartifactId=my-app-15 mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=com.mycompany.app -DartifactId=my-app-1 . . . . Choose a number: (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/26/27/28/29/30/31/32/33/34/35/36/37/38/39/40/41) 15: : 1 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The defined artifact is not an archetype mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=com.mycompany.app -DartifactId=my-app-1 . . . Choose a number: (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/26/27/28/29/30/31/32/33/34/35/36/37/38/39/40/41) 15: : 6 [INFO] artifact org.appfuse.archetypes:appfuse-modular-jsf: checking for updates from central Downloading: http://repo1.maven.org/maven2/org/appfuse/archetypes/appfuse-modular-jsf/2.1.0-M2/appfuse-modular-jsf-2.1.0-M2.jar [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The defined artifact is not an archetype In any unselected case it downloads first and fails So numbers used are : 1 to 9 FAILS; 10 to 17 is Ok and GENERATES, 18 FAILS, 19 is OK; 20 FAILS --- Choose a number: (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/26/27/28/29/30/31/32/33/34/35/36/37/38/39/40/41) 15: : 20 [INFO] artifact org.apache.maven.archetypes:softeu-archetype-seam: checking for updates from softeu-archetype-seam-repo [INFO] artifact org.apache.maven.archetypes:softeu-archetype-seam: checking for updates from central [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The desired archetype does not exist (org.apache.maven.archetypes:softeu-archetype-seam:RELEASE) 21 FAILS Choose a number: (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/26/27/28/29/30/31/32/33/34/35/36/37/38/39/40/41) 15: : 21 [INFO] artifact org.apache.maven.archetypes:softeu-archetype-seam-simple: checking for updates from softeu-archetype-seam-simple-repo [INFO] artifact org.apache.maven.archetypes:softeu-archetype-seam-simple: checking for updates from central [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The desired archetype does not exist (org.apache.maven.archetypes:softeu-archetype-seam-simple:RELEASE) . . . End of my test on PC Guess someone has a little bit of work to do ! Or how shall I go on ??? And oooh yes; On OpenVMS the offerings are much greater (guess they come from remote), and they give me from the remote catalog 377 options to chose from I have some parameter passing problems on OpenVMS but the default option perfectly generates a quick-start-project Thank you Josef Von: Hahn, Christopher (SAN DIEGO) [mailto:christopher.h...@hp.com] Gesendet: Mittwoch, 23. März 2011 19:40 An: Maven Users List Betreff: Hello World? ??? What can make Hello World fail: == D:\tempmvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=com.mycompany.app -DartifactId=my-app D:\tempset MAVEN_OPTS=-Xmx1024m -Xms128m [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file: Connection refused: connect [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e
AW: subversion vs maven
I would consider this as either a) bad dependencies or b) bad dependency management And I woul NOT and never ever expect that from a modern build system like maven. Josef -Ursprüngliche Nachricht- Von: Jeff [mailto:predato...@gmail.com] Gesendet: Mittwoch, 16. Februar 2011 18:28 An: Maven Users List; cika...@gmail.com Betreff: Re: subversion vs maven Maybe this question will expose my ignorance, but I thought most build systems only build the things that have changed unless you do a clean each time or are starting from a fresh checkout as opposed to doing an svn update and then running the build. Being new to Maven myself, there could there be an option in the POM that might be forcing a full build each time? I would think that as long as you aren't specifying clean in your build kickoff process or otherwise forcing a full biuld, you should only be getting the incremental build, no? Am I off in my understanding? On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis cika...@gmail.comwrote: Yes, However it does a full build which takes ~30-40 minutes. But I want to build only specific projects and their dependents. Regards Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent
AW: Error on mvn clean
What OS? Did the directory attribute get somehow to read only for the process intending to do the delte? Some OS can not delete the directory if the directory is not empty first! Josef -Ursprüngliche Nachricht- Von: Kenneth Litwak [mailto:klit...@apu.edu] Gesendet: Freitag, 4. Februar 2011 22:52 An: Maven Users List Betreff: Error on mvn clean I'm getting an error on clean. Failed to delete directory: c:\javaprojects\javaapp\SpringWeb\target Reason: unable to delete directory c:\javaprojects\javaapp\SpringWeb\target Maven made the directory and I can see it. Why is the clean failing? - 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
AW: Brand new to Maven, first build, didn't go well.
And you need -Dhttp.auth.preference=Basic in case your firewall is from MS and knows NTLM and Basic authentication schemas; It would be so nice from maven if maven's settings.xml could express this as well ! all in one place :-) Got old unless I got that far and from OpenVMS through the firewall. Not required from a PC wich does NTLM by default. Josef -Ursprüngliche Nachricht- Von: Wendy Smoak [mailto:wsm...@gmail.com] Gesendet: Donnerstag, 3. Februar 2011 16:34 An: Maven Users List; Amy Betreff: Re: Brand new to Maven, first build, didn't go well. On Thu, Feb 3, 2011 at 10:28 AM, Amy o627m...@yahoo.com wrote: I will add that I'm at work and behind a firewall. I believe there is also a proxy through which all of my HTTP requests go. Here is some information about configuring Maven to go through your http proxy: http://maven.apache.org/guides/mini/guide-proxies.html Are the developers in your organization already using Maven? If so, they should have an internal Maven repository that you can build against -- ask them for advice on what to put in your settings.xml file. -- Wendy - 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
AW: AW: org.codehaus.modello.ModelloCli fails parsing maven.mdo on OpenVMS
That is what I think as well. In this case I would need to know
Looking at the xml below, its clearly the generate-sources target
which fails and in that the line with java fork=fork ... which
gets executed and fails in turn parsing the model file .mdo.
How does the class org.codehaus.modello.ModelloCli select which parser
to use and how can I check that the proper parser is used?
How can I enforce that this class uses a different parser?
Josef
target name=generate-sources depends=pull description=generates Java
sources from Modello mdo model files
mkdir dir=bootstrap/target/
mkdir dir=bootstrap/target/generated-sources/
macrodef name=modello-single-mode
attribute name=file/
attribute name=mode/
attribute name=version/
sequential
java fork=fork classname=org.codehaus.modello.ModelloCli
failonerror=true
classpath refid=modello.pathid/
arg file=@{file}/ !-- model file --
arg value=@{mode}/ !-- output type --
arg file=bootstrap/target/generated-sources/ !-- output
directory --
arg value=@{version}/ !-- model version --
arg value=false/ !-- package with version --
arg value=true/ !-- use Java 5 --
arg value=UTF-8/ !-- encoding --
/java
/sequential
/macrodef
macrodef name=modello
attribute name=file/
attribute name=version default=1.0.0/
sequential
echo taskname=modello message=Generating sources for @{file}/
modello-single-mode file=@{file} version=@{version} mode=java/
modello-single-mode file=@{file} version=@{version}
mode=xpp3-reader/
modello-single-mode file=@{file} version=@{version}
mode=xpp3-writer/
/sequential
/macrodef
modello file=maven-model/src/main/mdo/maven.mdo version=4.0.0/
modello file=maven-plugin-descriptor/src/main/mdo/lifecycle.mdo/
modello file=maven-plugin-registry/plugin-registry.mdo/
modello
file=maven-plugin-parameter-documenter/src/main/mdo/paramdoc.mdo/
modello file=maven-profile/src/main/mdo/profiles.mdo/
modello file=maven-settings/src/main/mdo/settings.mdo/
modello file=maven-repository-metadata/src/main/mdo/metadata.mdo/
modello file=maven-toolchain/src/main/mdo/toolchains.mdo/
/target
-Ursprüngliche Nachricht-
Von: Kristian Rosenvold [mailto:kristian.rosenv...@gmail.com]
Gesendet: Mittwoch, 19. Januar 2011 08:30
An: Maven Users List
Betreff: Re: AW: org.codehaus.modello.ModelloCli fails parsing maven.mdo on
OpenVMS
Den 18.01.2011 17:16, skrev Stadelmann Josef:
Maybe you have another advise for me.
From the general smell of it I would suspect this is somehow related to
your xml parsers/versions or some kind of inappropriate
version mix. I know this is probably not too helpful
Kristian
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
org.codehaus.modello.ModelloCli fails parsing maven.mdo on OpenVMS
I am about to build apache-maven-2.2.1 on OpenVMS using either ant 1.7
or ant 1.6.5 from the NetBeans IDE 6.5.1
Just substituted M2_HOME by MVN_HOME for convenient.
I managed that ant get could download the artifacts from central
repository straigth into OpenVMS; for that to work, for that to pass my
firewall, I added the follwing logical to OpenVMS.
$ define/process -Dhttp.authpreference=Basic
-Dhttp.proxyhost=myprocx.com -Dhttp.proxyport=8080
-Dhttp.proxyuser=mydomainusername -Dhttp.proxypassword=mydoaminpassword
So the only thing one can not do with setproxy in ant is to give a
AuthenticationSchema preference, but as we access via http we can use it
like from maven, and since there is no more needs for any setproxy in
the build.xml file.
After doing so the pull target of the bootstrap-build.xml was working
properly and all dependent artifacts are now downloaded straigth into
the OpenVMS maven repository;
hence I did the next command line
$ ant -v -Dmaven.home=/dkb3/stadelma/apache-maven-2_2_1 -f
bootstrap-build.xml generate-sources
And that gives me an error which you migth be able to give me a bit
advise. See to verbos output (few overides deleted)
I toke out java fork=fork from bootstratp-build.xml setting up the
macrodef for modello, but no effect; so I changed this back.
I checked out by an editor that maven.mdo file for proper formats; BUT
I can't see anything wrong with it; also the same files build perfect on
the windows system, just not on openVMS.
Could it be a parser problem?
If yes is there a way to exchange the parser for the source generating
step ?
Josef
Apache Ant version 1.6.5 compiled on July 14 2006
Buildfile:
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/boo
tstrap-build.xml
Detected Java version: 1.5 in: /ide$java_root/jre
Detected OS: OpenVMS
parsing buildfile
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/boo
tstrap-build.xml with URI =
file:///INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_
2_1/bootstrap-build.xml
Project base dir set to:
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1
Build sequence for target(s) `generate-sources' is [initTaskDefs,
isMavenHomeSet, initLocalRepo, init, read-poms, pull, generate-sources]
Complete build sequence is [initTaskDefs, isMavenHomeSet, initLocalRepo,
init, read-poms, pull, generate-sources, clean-bootstrap, compile-boot,
maven-compile, maven-assembly, extract-assembly, all, its-setup,
its-win32, its-unix, run-its, with-its, set-temp-maven-home, ]
initTaskDefs:
Loading
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/pom
.xml
parsing buildfile
jar:file:/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-
2_2_1/maven-ant-tasks-2.0.8.jar!/org/apache/maven/artifact/ant/antlib.xm
l with URI =
jar:file:/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-
2_2_1/maven-ant-tasks-2.0.8.jar!/org/apache/maven/artifact/ant/antlib.xm
l
isMavenHomeSet:
Loading Environment env.
Property ${env.MVN_HOME} has not been set
Using Maven home at: /dkb3/stadelma/apache-maven-2_2_1
initLocalRepo:
Using the local repository at: /dkb3/stadelma/.m2/repository
init:
Loading
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/pom
.xml
maven.home = /dkb3/stadelma/apache-maven-2_2_1
maven.assembly =
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/apa
che-maven/target/apache-maven-2.2.1-bin.zip
read-poms:
Copying 1 file to
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1
Copying
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/pom
.xml to
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/dep
endencies.xml
Replacing in
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/dep
endencies.xml: !--start-- -- !--
Replacing in
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/dep
endencies.xml: !--end-- -- --
Loading Maven settings file: /dkb3/stadelma/.m2/settings.xml
Using remote repositories:
- id=central, url=http://repo.exist.com/maven2, releases=enabled,
snapshots=disabled, proxy=bcproxyserver.ch.winterthur.com
Deleting:
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/dep
endencies.xml
Loading Maven settings file: /dkb3/stadelma/.m2/settings.xml
pull:
Loading Maven settings file: /dkb3/stadelma/.m2/settings.xml
Maven Ant Tasks version: 2.0.8
Using local repository: /dkb3/stadelma/.m2/repository
Resolving dependencies...
Using remote repositories:
- id=apache.snapshots, url=http://repository.apache.org/snapshots,
releases=disabled, snapshots=enabled,
proxy=bcproxyserver.ch.winterthur.com
- id=central, url=http://repo.exist.com/maven2, releases=enabled,
snapshots=disabled, proxy=bcproxyserver.ch.winterthur.com
org.apache.maven:maven:pom:2.2.1 (selected)
commons-cli:commons-cli:jar:1.2:compile (selected)
org.apache.maven.doxia:doxia-sink-api:jar:1.1:compile (selected)
AW: org.codehaus.modello.ModelloCli fails parsing maven.mdo on OpenVMS
I am using NetBeans IDE with distributed NetBeans Plugin from HP to connect to OpenVMS That way I can say that any .mdo file is an ASCII file to be sent/received by the FTP File cabinet to/from openVMS. So over all I have avery convenient way to put or get files to from my OpenVMS FTP File cabinet. And I just did a get from server and then applied a local PC based Build of the target generate-sources and all went OK. I doubble checkk with the EDT on OpenVMS and it seams a plain vanilla XML file. Because NetBeans said the file type is unknown I assigned it a Mime type of (application/xml) I took NetBeans and I applied an xml check and an xml validation and all went Ok. I went online to connect via FTP to my OpenVMS system and I did put file to server I toke my plain old OpenVMS EDT and I could edit it without any troubles. and I marked line 79 with EDT and went down to line 103 with EDT and the look all the same in OpenVMS EDIT EDT and in NetBeans, guess there is a parser problem maybe with encoding as in OpenVMS we normally use ISO-8895-1 not UTF-8. We can say it is the same content. And you want beleave it ... after I toke out the content of the first 4 description /description In particular the CDATA sections but left descriptionTest /description the parsing went well over maven.mdo (all 3 gen-sets), lifecycle.mdo (all 3 gen sets), but failed again for the plugin-registry.mdo with the java gen set. Maybe you have another advise for me. Josef ... classes class rootElement=true xml.tagName=project nameModel/name superClassModelBase/superClass description ![CDATA[ The codelt;projectgt;/code element is the root of the descriptor. The following table lists all of the possible child elements. ]] /description version3.0.0+/version fields . this is line 79 in OpenVMS EDT !-- == -- !-- Model Version -- !-- == -- field namepomVersion/name version3.0.0/version requiredtrue/required typeString/type description ![CDATA[ Declares to which version of project descriptor this POM conforms. The only valid value is code3/code. ]] /description /field field namemodelVersion/name version4.0.0/version requiredtrue/required descriptionDeclares to which version of project descriptor this POM conforms./description typeString/type /field .and this is line 103 in openVMS EDT and the same is shown in NetBeans IDE Editor !-- == -- !-- Parent Model -- !-- == -- -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Dienstag, 18. Januar 2011 16:10 An: Maven Users List Betreff: Re: org.codehaus.modello.ModelloCli fails parsing maven.mdo on OpenVMS Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name /field must match start tag name fields from line 79 (position: TEXT seen .../field /field... @103:33) Did you check around line 79, the /field and /fields etc? Are you certain this is exactly the same file that is processed with no errors on Windows with zero edits or modifications, the same revision number, etc? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: why does maven use /bin/sh -c ls -1lna /djb3/... just to get a file attribute?
Thank you all for helping me. You are right I seem to be the only one using maven on OpenVMS. Still ramping up; I've never built maven on OpenVMS due to some JSVN catch down problem and a HP JAVA JVM crash. Next development server running OpenVMS will bring me back a 100% patched OS and a stable running JVM; then I can catch down sources using jsvn (svnkit) more easy. Then allows me building maven using thze ant bootstrap and/or bump it all up to most recent maven versions as I did so many times on my VISTA PC. The results seen on OpenVMS are very very promising for ANT, JSVN and MAVEN; integration among platforms is all for me. NetBeans IDE with distributed NetBeans from HP allows me to have local PC based projects as well as remote projects running/debugging on OpenVMS. Aim : have a fast reliable development environment both VISTA PC with Visual Studio 2010, WCF 3.5, VB.NET, C#.NET AND NetBeans e all based toward my Apache Axis2/J+C Servers on OPenVMS integrating via HP WSIT our very large Spezpla OpenVMS Legacy Server with its Oracle 10g DB. To deliver a bit more insigth to the current problem I am faced with - here the log - part - with the error and the -e and -X switch set. [INFO] No tests to run. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ sqljet --- [DEBUG] org.apache.maven.plugins:maven-jar-plugin:jar:2.3.1: [DEBUG]org.apache.maven:maven-plugin-api:jar:2.0.6:compile [DEBUG]org.apache.maven:maven-project:jar:2.0.6:compile [DEBUG] org.apache.maven:maven-settings:jar:2.0.6:compile [DEBUG] org.apache.maven:maven-profile:jar:2.0.6:compile [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.6:compile [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0.6:compile [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0.6:compile [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile [DEBUG] junit:junit:jar:3.8.1:compile [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:compile [DEBUG]org.apache.maven:maven-model:jar:2.0.6:runtime [DEBUG]org.apache.maven:maven-artifact:jar:2.0.6:compile [DEBUG]org.apache.maven:maven-archiver:jar:2.4.1:compile [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.13:compile [DEBUG]org.codehaus.plexus:plexus-archiver:jar:1.0:compile [DEBUG] org.codehaus.plexus:plexus-io:jar:1.0:compile [DEBUG]commons-lang:commons-lang:jar:2.1:compile [DEBUG]org.codehaus.plexus:plexus-utils:jar:2.0.5:compile [DEBUG] Created new class realm pluginorg.apache.maven.plugins:maven-jar-plugin:2.3.1 [DEBUG] Populating class realm pluginorg.apache.maven.plugins:maven-jar-plugin:2.3.1 [DEBUG] Included: org.apache.maven.plugins:maven-jar-plugin:jar:2.3.1 [DEBUG] Included: junit:junit:jar:3.8.1 [DEBUG] Included: org.apache.maven:maven-archiver:jar:2.4.1 [DEBUG] Included: org.codehaus.plexus:plexus-interpolation:jar:1.13 [DEBUG] Included: org.codehaus.plexus:plexus-archiver:jar:1.0 [DEBUG] Included: org.codehaus.plexus:plexus-io:jar:1.0 [DEBUG] Included: commons-lang:commons-lang:jar:2.1 [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:2.0.5 [DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6 [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.6 [DEBUG] Excluded: org.apache.maven:maven-settings:jar:2.0.6 [DEBUG] Excluded: org.apache.maven:maven-profile:jar:2.0.6 [DEBUG] Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6 [DEBUG] Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6 [DEBUG] Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6 [DEBUG] Excluded: org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1 [DEBUG] Excluded: classworlds:classworlds:jar:1.1-alpha-2 [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.6 [DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.0.6 [DEBUG] Configuring mojo org.apache.maven.plugins:maven-jar-plugin:2.3.1:jar from plugin realm ClassRealm[pluginorg.apache.maven.pl ugins:maven-jar-plugin:2.3.1, parent: ClassRealm[maven.api, parent: null]] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-jar-plugin:2.3.1:jar' with basic configurator -- [DEBUG] (f) classesDirectory = /dkb3/sw-projekte/asf/sqljet/trunk/target/classes [DEBUG] (f) defaultManifestFile = /dkb3/sw-projekte/asf/sqljet/trunk/target/classes/META-INF/MANIFEST.MF [DEBUG] (f) finalName = sqljet-1.1.0 [DEBUG] (f) forceCreation = false [DEBUG] (f) outputDirectory = /dkb3/sw-projekte/asf/sqljet/trunk/target [DEBUG] (f) project = MavenProject: org.tmatesoft.sqljet:sqljet:1.1.0 @ /dkb3/sw-projekte/asf/sqljet/trunk/pom.xml [DEBUG] (f) useDefaultManifestFile = false [DEBUG] -- end configuration -- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] [INFO] BUILD FAILURE [INFO]
why does maven use /bin/sh -c ls -1lna /djb3/... just to get a file attribute?
On OpenVMS, with JDK 1.5, and maven 3.0 I can download now perfectly forcing basic authentication toward our proxy server. But as downloading artefacts from repositories works now perfect, I want to do bigger steps. i.e. building the svnkit so here we go IA64mvn -Dhttp.auth.preference=Basic --version Apache Maven 3.0 (r1036088; 2010-11-23 18:19:59+0100) Java version: 1.5.0 Java home: /dkb3/java$150/jre Default locale: en, platform encoding: ISO8859-1 OS name: openvms version: v8.3-1h1 arch: ia64 Family: openvms IA64 IA64 set default dkb3:[sw-projekte.asf.svnkit.tags.1_3_3] IA64 IA64mvn -Dhttp.auth.preference=Basic clean install [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building SVNKit 1.3.3 [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ svnkit --- [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ svnkit --- [WARNING] Using platform encoding (ISO8859-1 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ svnkit --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ svnkit --- [WARNING] Using platform encoding (ISO8859-1 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ svnkit --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.5:test (default-test) @ svnkit --- [INFO] No tests to run. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ svnkit --- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 6.099s [INFO] Finished at: Thu Jan 13 14:05:34 CET 2011 [INFO] Final Memory: 4M/62M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:2.3.1:jar (default-jar) on project svnkit: Error assembling JAR: Failed to read filesystem attributes for: /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlad /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml': Error while executing process. Child creation error: no such file or directory - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException IA64dir :-( How can java catch file system attributes better? Why do we use a Unix shell command to create a child prozess (sub-process in openvms) by Java just to catch a file system attribute? Creating child processes is an overkill and slows down maven and other SW when used. This claim is placed - because not every operating system has by default - a Unix command shell - to create a child process - to execute a directory command - just to get a file system attribute! But it seems that on my OpenVMS with default DCL command language, the maven version 3 under java and a JVM attempts to place a command which should create a child process just to execute a ls command used to retrieve a file attribute. I call it a style break, we should not do it from Java and not assume Unix or the like shells avail, or we are at risk that over time fewer system will support what maven attempts to do. Josef.Stadelmann @axa-winterthur.ch
AW: Maven failing due to javac path issue -- Windows
Please note:
A JRE never has developer tools like compilers or generators and the like.
Nothing to develop something.
That's why JAVA_HOME as environment variable must point to a SDK-root with
javac.exe in it and not to a JRE-root.
And second:
JAVA_HOME is an environment variable AND is sometimes intentionally be used to
overwrite the java system property $(java.home)
BUT This is a no go too in WINDOWS as the java system property ${java.home}
points always to a JRE-root even when set explicit. There is no override.
Hence using ${java.home} to catch a javac.exe (compiler) is a no-go too.
With this in mind Per-Henrik's request is very valid.
Josef
Von: Enrique Gaona [mailto:ega...@us.ibm.com]
Gesendet: Mittwoch, 8. September 2010 03:05
An: Maven Users List
Cc: users@maven.apache.org
Betreff: RE: Maven failing due to javac path issue -- Windows
Apologies for not responding right away, had to deal with another fire:-)
Per-Henrik's request:
C:\Documents and Settings\Administratorjavac -version
javac 1.6.0-internal
I just resolved the problem by adding a maven-compiler-plugin to the project's
pom.xml and that resolved the issue. Thanks everyone for your input, very much
appreciate all the help.
Cheers,
Enrique
Inactive hide details for Martin Gainty ---09/07/2010 07:23:10
PM---$JDK_HOME/bin/javac.exeMartin Gainty ---09/07/2010 07:23:10
PM---$JDK_HOME/bin/javac.exe
Martin Gainty mgai...@hotmail.com
09/07/2010 07:22 PM
Please respond to
Maven Users List users@maven.apache.org
To
users@maven.apache.org
cc
Subject
RE: Maven failing due to javac path issue -- Windows
$JDK_HOME/bin/javac.exe
$JRE_HOME/bin/java.exe
Martin
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
To: users@maven.apache.org
From: joerg.schai...@gmx.de
Subject: Re: Maven failing due to javac path issue -- Windows
Date: Tue, 7 Sep 2010 23:11:21 +0200
Anders Hammar wrote:
I believe that the Java home path given by mvn -version on a Windows
platform points at the jre, not the jdk. Possibly someone on Windows could
confirm this?
This is normal (also on Linux). I am also curious on java -version though
...
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
AW: Maven failing due to javac path issue -- Windows
I just found a bigger better explanation from an unknown autor you migth have
to care when using JAVA and a Windows System
Josef
JAVA_HOME vs java.home
What's the difference between JAVA_HOME and java.home? JAVA_HOME is the JDK
install directory, e.g., C:\jdk5. It's meant to be set as an environment
variable and referenced in Windows batch files or Unix scripts. I always have
it in my Windows Control Panel and .tcsh files, along with other common
environment variables. Some Java applications use the name jdk.home for this
purpose, which I think is a better name. But JAVA_HOME has been used since the
beginning and is now a convention.
java.home is the JRE install directory, e.g., C:\jdk5\jre, or C:\Program
Files\Java\jre1.5.0_06. Unlike JAVA_HOME, I never seen java.home as an
environment variable. java.home is a build-in Java system property, whose value
is the JRE install directory. Since all Java system properties are also exposed
as Ant build properties, you can also use ${java.home} in build files.
Would jre.home be a better name? Maybe, but I don't think Sun will change it.
Therefore, java.home is always there inside JVM, whereas JAVA_HOME exists
mainly in your shell environment and you may pass it to JVM as a system
property. Why do we still need JAVA_HOME? Well, there are good reasons:
* You can add $JAVA_HOME/bin to the beginning of your PATH, to make sure
you always invoke the right java program. On Windows, java.exe is duplicated in
several places, for instance %JAVA_HOME%\bin\java.exe,
$JAVA_HOME\jre\bin\java.exe, and %SystemRoot%\system32\java.exe. Without have
$JAVA_HOME/bin at the beginning of the PATH, a java command will always resolve
to %SystemRoot%\system32\java.exe, which may not be what you want. The same
problem can also exist in Linux/Solaris.
* Some Java application runtime needs to use tools/libraries only
available in JDK. For example, web containers need tools.jar in JDK to compile
JSP pages, and ejb containers also need to invoke javac/rmic tools in JDK. So
the build-in system property java.home is not sufficient.
-Ursprüngliche Nachricht-
Von: Enrique Gaona [mailto:ega...@us.ibm.com]
Gesendet: Dienstag, 7. September 2010 18:26
An: Maven Users List
Betreff: Maven failing due to javac path issue -- Windows
Hi,
I'm trying to build a project on Windows (believe me, this is not my first
choice) and its failing because Maven can't find javac. The error message
being returned Failure executing javac, but could not parse the error:
The system cannot find the path specified. Looking at the debug
output, I see this, [DEBUG] (f) executable = null/bin/javac. Is there a
way to rectify this problem, given the fact JAVA_HOME, M2_HOME, and PATH
variables have been set correctly? Thanks.
Output from the variables:
C:\RTC-data\workspaceecho %JAVA_HOME%
C:\IBM\ibm-java-sdk-60-win-i386\sdk
C:\RTC-data\workspaceecho %M2_HOME%
C:\apache-maven-2.2\apache-maven-2.2.1
C:\RTC-data\workspaceecho %PATH%
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files
\IBM\Infoprint Select;C:\Notes;C:\Program Files\XLView;C:\lotus
\compnent;C:\Utilities;C:\Program Files\Common Files\Lenovo;C:\pr
ogram files\ibm\personal communications\;C:\Program Files\IBM\Trace
Facility\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\ThinkPad
\ConnectUtilities;C:\Program Files\IBM\RationalSDLC\common;C:\ap
ache-maven-2.2\apache-maven-2.2.1\bin;C:\IBM\ibm-java-sdk-60-win-i386\sdk
\bin
Build output error:
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
The system cannot find the path specified.
[INFO]
[DEBUG] Trace
org.apache.maven.BuildFailureException: Compilation failure
Failure executing javac, but could not parse the error:
The system cannot find the path specified.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:715)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at
WG: catch 22s building Maven-2.2.1 with NetBeans 5.5.1 using distributet NetBeans from HP
_
Von: Stadelmann Josef
Gesendet: Donnerstag, 2. September 2010 15:15
An: 'Maven Users List'; 'Distributed NetBeans for OpenVMS';
'nbus...@netbeans.org'
Betreff: catch 22s building Maven-2.2.1 with NetBeans 5.5.1 using
distributet NetBeans from HP
I have a very nice catch 22 situation
Porting maven-2.2.1 to OpenVMS using NetBeans 5.5.1 and distributet
NetBeans from HP;
I build it first in VISTA SP1, using a DOS Windows running as
administrator. The build works perfect.
But building maven-2.2.1 using NetBeans 5.5. 1 with distributet NetBeans
from HP is a mess.
I get the following errors, (not running as administrator)
clean-bootstrap:
Deleting directory C:\asf\maven\maven-2\tags\maven-2.2.1\bootstrap
initTaskDefs:
isMavenHomeSet:
Using Maven home at: C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1
initLocalRepo:
Using the local repository at: C:\Users\C770817\.m2\repository
init:
maven.home = C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1
maven.assembly =
C:\asf\maven\maven-2\tags\maven-2.2.1\apache-maven\target\apache-maven-2
.2.1-bin.zip
read-poms:
Copying 1 file to C:\asf\maven\maven-2\tags\maven-2.2.1
Deleting: C:\asf\maven\maven-2\tags\maven-2.2.1\dependencies.xml
pull:
generate-sources:
Created dir: C:\asf\maven\maven-2\tags\maven-2.2.1\bootstrap\target
Created dir:
C:\asf\maven\maven-2\tags\maven-2.2.1\bootstrap\target\generated-sources
Generating sources for maven-model/src/main/mdo/maven.mdo
C:\asf\maven\maven-2\tags\maven-2.2.1\build.xml:147: The following error
occurred while executing this line:
C:\asf\maven\maven-2\tags\maven-2.2.1\build.xml:141: The following error
occurred while executing this line:
C:\asf\maven\maven-2\tags\maven-2.2.1\build.xml:123:
java.lang.SecurityException
BUILD FAILED (total time: 1 minute 5 seconds)
Why a security exception, how can I avoid it?
Then starting NetBeans 5.5.1 using RUN AS ADMINISTRATOR to hopefully
prevent the security exception
Is a no go too and results results in a crash and leaves two processes
on the system during startup of NB
Java.lang.NoClassDefFoundError:
org/netbenas/modules/project/ui/OpenProjectList
At
org.netbeans.modules.distributed.remotefs.MyURLMapperProxy.searchFS(Unkn
own Source)
At
org.netbeans.modules.distributed.remotefs.MyURLMapperProxy.MOUNTfs(Unkno
wn Source)
At
org.netbeans.modules.distributed.remotefs.MyURLMapperProxy.GETfILEOBJECT
S(Unknown Source)
At
org.OPENIDE.FILESYSTEM.urlmAPPER.FINDfILEoBJECT(urlmAPPER.Java:196))
.
Why does Modello demand privileges to generate code using this target
during a maven-2.2.1 boot-strat-build
target name=generate-sources depends=pull description=generates
Java sources from Modello mdo model files
mkdir dir=bootstrap/target/
mkdir dir=bootstrap/target/generated-sources/
macrodef name=modello-single-mode
attribute name=file/
attribute name=mode/
attribute name=version/
sequential
123 java fork=fork classname=org.codehaus.modello.ModelloCli
failonerror=true
classpath refid=modello.pathid/
arg file=@{file}/ !-- model file --
arg value=@{mode}/ !-- output type --
arg file=bootstrap/target/generated-sources/ !-- output
directory --
arg value=@{version}/ !-- model version --
arg value=false/ !-- package with version --
arg value=true/ !-- use Java 5 --
arg value=UTF-8/ !-- encoding --
/java
/sequential
/macrodef
macrodef name=modello
attribute name=file/
attribute name=version default=1.0.0/
sequential
echo taskname=modello message=Generating sources for
@{file}/
141 modello-single-mode file=@{file} version=@{version}
mode=java/
modello-single-mode file=@{file} version=@{version}
mode=xpp3-reader/
modello-single-mode file=@{file} version=@{version}
mode=xpp3-writer/
/sequential
/macrodef
147 modello file=maven-model/src/main/mdo/maven.mdo version=4.0.0/
modello file=maven-plugin-descriptor/src/main/mdo/lifecycle.mdo/
modello file=maven-plugin-registry/plugin-registry.mdo/
modello
file=maven-plugin-parameter-documenter/src/main/mdo/paramdoc.mdo/
modello file=maven-profile/src/main/mdo/profiles.mdo/
modello file=maven-settings/src/main/mdo/settings.mdo/
modello
file=maven-repository-metadata/src/main/mdo/metadata.mdo/
modello file=maven-toolchain/src/main/mdo/toolchains.mdo/
/target
I am open for any kind of hints, and I can't use maven 3 because we have
projects which are not yet mavenized for version3 of maven.
Also, I wan't to debug maven-2.2.1 to see if and how proxy
authentication works using the BASIC authentication scheme
on HP OpenVMS with JDK 5.0 e all.
And yes;
using a higher version of NetBeans leaves renders my netbeans project
files in a way that I can't open it thereafter in NetBeans 5.5.1
Beautifull dependencies :-)
Josef - with catch 22's
AW: maven-1.1 build-bootstrap fails with OpenVMS
We are using a feature with Axis2-1.2 which is called scope=soapsession That is to say, we have a state-full web service realized and interfaced with Microsoft WCF 3.5 Clients. State-full web services with long lasting user sessions is a thing which makes every bode I've meet so far cry. Hence I never got real help on that issues when I need it, hence I have built axis2-1.2 in the past from scratch myself just to be able to single step through the engine code to master this features; sorry but we use long lasting session because our legacy server code some 120'000 line of OpenVMS Pascal code is as it is. And yes: all is running fine. But since some few weeks my destroy() method is no longer called when the user session breaks. Axis2-1.2 needs at a max maven-1.1 for building. I do it routinely at home not sitting behind a fire wall proxy demanding username and password and domain name to reach out for artifacts; but here in the AXA company I can't reach out for artifacts unless this NTLM authentication is properly supported. Also: WHO OF YOU MAVEN GUYS CAN TELL ME how to best approach? 1. Does Axis2-1.5 and greater support scope=soapsession correctly; I've read somewhere that this is not any longer the case; Unfortunately I lost my pointer to this information, hence I can't ask the author. And again; this feature seems to be so exotic but is there, that nobody helps me. 2. WHO OF YOU MAVEN DEVELOPERS can tell me that maven-2.2.1 and above used to build Axis2-1.5 and above can reach through proxies using username password and domain name and is able to deal with NTLM authentication correctly? If this does not run on maven-1.1 why should it run on maven-2 and maven-3? I will certainly go any build maven-2.2.1 and port it to OpenVMS and hope that it can reach through proxy protected networks to get artifacts downloaded. Josef -Ursprüngliche Nachricht- Von: Kathryn Huxtable [mailto:kath...@kathrynhuxtable.org] Gesendet: Dienstag, 24. August 2010 19:14 An: Maven Users List Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS Egads, is anyone still using Maven 1? If so, why? -K On Aug 24, 2010, at 11:40 AM, Wayne Fay wrote: Wasting time? How do I force BASIC authentication using maven-1.1 either with maven-1.1 or maybe I can do it outside maven-1.1-code through a Let me be more plain... you are WASTING YOUR TIME trying to fix Maven1. Perhaps you understand me better now? Find the simplest thing that could possibly work -- just download the artifacts into the proper spot in your local filesystem -- and get on with the more important things, which is apparently debugging your problems Axis. Wayne - 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
AW: maven-1.1 build-bootstrap fails with OpenVMS
Stephen I agree with some of your points, But please tell me how authentication with a proxy server is handled in maven-2 or maven-3? If authentication toward a proxy server is handled the same way as in maven-1 then there is at least one pile left in maven-2 or maven-3 :-), But given there are no such piles left; how then is authentication handled in maven-2 or maven-3? Most important for me: Can I force maven-2 or maven-3 to use only BASIC authentication (user name AND password) but not NTLM or DIGEST toward a proxy server to reach out for artifact downloading, this because I run from OpenVMS, which might be not as good as Linux or Windows is in dealing with NTLM Authentication. Josef -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Montag, 30. August 2010 12:45 An: Maven Users List Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS There was a MAJOR refactoring between Maven 1.x and Maven 2.x If a project is built using Maven 1.x you have no hope to build it with Maven 2.x unless you convert the build process yourself (or unless somebody else has converted it for you) Maven 1.x development pretty much ceased at least 4-5 years ago I think you are out of luck unless you can use a Maven Repository Manager (e.g. Nexus) to proxy the requests for you -Stephen P.S. Stephen has never done any development work with Maven 1.x. Stephen thinks Maven 1.x is a stinking pile of excrement... which makes an excellent fertiliser from which the roses that are Maven 2.x and Maven 3.x have grown ;-) On 30 August 2010 09:56, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: We are using a feature with Axis2-1.2 which is called scope=soapsession That is to say, we have a state-full web service realized and interfaced with Microsoft WCF 3.5 Clients. State-full web services with long lasting user sessions is a thing which makes every bode I've meet so far cry. Hence I never got real help on that issues when I need it, hence I have built axis2-1.2 in the past from scratch myself just to be able to single step through the engine code to master this features; sorry but we use long lasting session because our legacy server code some 120'000 line of OpenVMS Pascal code is as it is. And yes: all is running fine. But since some few weeks my destroy() method is no longer called when the user session breaks. Axis2-1.2 needs at a max maven-1.1 for building. I do it routinely at home not sitting behind a fire wall proxy demanding username and password and domain name to reach out for artifacts; but here in the AXA company I can't reach out for artifacts unless this NTLM authentication is properly supported. Also: WHO OF YOU MAVEN GUYS CAN TELL ME how to best approach? 1. Does Axis2-1.5 and greater support scope=soapsession correctly; I've read somewhere that this is not any longer the case; Unfortunately I lost my pointer to this information, hence I can't ask the author. And again; this feature seems to be so exotic but is there, that nobody helps me. 2. WHO OF YOU MAVEN DEVELOPERS can tell me that maven-2.2.1 and above used to build Axis2-1.5 and above can reach through proxies using username password and domain name and is able to deal with NTLM authentication correctly? If this does not run on maven-1.1 why should it run on maven-2 and maven-3? I will certainly go any build maven-2.2.1 and port it to OpenVMS and hope that it can reach through proxy protected networks to get artifacts downloaded. Josef -Ursprüngliche Nachricht- Von: Kathryn Huxtable [mailto:kath...@kathrynhuxtable.org] Gesendet: Dienstag, 24. August 2010 19:14 An: Maven Users List Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS Egads, is anyone still using Maven 1? If so, why? -K On Aug 24, 2010, at 11:40 AM, Wayne Fay wrote: Wasting time? How do I force BASIC authentication using maven-1.1 either with maven-1.1 or maybe I can do it outside maven-1.1-code through a Let me be more plain... you are WASTING YOUR TIME trying to fix Maven1. Perhaps you understand me better now? Find the simplest thing that could possibly work -- just download the artifacts into the proper spot in your local filesystem -- and get on with the more important things, which is apparently debugging your problems Axis. Wayne - 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
AW: maven-1.1 build-bootstrap fails with OpenVMS
Anders Thanks for the info, I went through that already, A DN it is formaven2 and maven3 However as you can read as well .. just below the box on tghe mentioned page/like http://maven.apache.org/guides/mini/guide-proxies.html Please note that currently NTLM proxies are not supported as they have not been tested. You may be able to use the relevant system properties on JDK 1.4+ to make this work. ++ would be nice to know how? So what java system properties do I have to set to make JDK work and force to use only BASIC authentication? Josef -Ursprüngliche Nachricht- Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag von Anders Hammar Gesendet: Montag, 30. August 2010 14:46 An: Maven Users List Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS http://maven.apache.org/guides/mini/guide-proxies.html /Anders On Mon, Aug 30, 2010 at 14:34, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Stephen I agree with some of your points, But please tell me how authentication with a proxy server is handled in maven-2 or maven-3? If authentication toward a proxy server is handled the same way as in maven-1 then there is at least one pile left in maven-2 or maven-3 :-), But given there are no such piles left; how then is authentication handled in maven-2 or maven-3? Most important for me: Can I force maven-2 or maven-3 to use only BASIC authentication (user name AND password) but not NTLM or DIGEST toward a proxy server to reach out for artifact downloading, this because I run from OpenVMS, which might be not as good as Linux or Windows is in dealing with NTLM Authentication. Josef -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Montag, 30. August 2010 12:45 An: Maven Users List Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS There was a MAJOR refactoring between Maven 1.x and Maven 2.x If a project is built using Maven 1.x you have no hope to build it with Maven 2.x unless you convert the build process yourself (or unless somebody else has converted it for you) Maven 1.x development pretty much ceased at least 4-5 years ago I think you are out of luck unless you can use a Maven Repository Manager (e.g. Nexus) to proxy the requests for you -Stephen P.S. Stephen has never done any development work with Maven 1.x. Stephen thinks Maven 1.x is a stinking pile of excrement... which makes an excellent fertiliser from which the roses that are Maven 2.x and Maven 3.x have grown ;-) On 30 August 2010 09:56, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: We are using a feature with Axis2-1.2 which is called scope=soapsession That is to say, we have a state-full web service realized and interfaced with Microsoft WCF 3.5 Clients. State-full web services with long lasting user sessions is a thing which makes every bode I've meet so far cry. Hence I never got real help on that issues when I need it, hence I have built axis2-1.2 in the past from scratch myself just to be able to single step through the engine code to master this features; sorry but we use long lasting session because our legacy server code some 120'000 line of OpenVMS Pascal code is as it is. And yes: all is running fine. But since some few weeks my destroy() method is no longer called when the user session breaks. Axis2-1.2 needs at a max maven-1.1 for building. I do it routinely at home not sitting behind a fire wall proxy demanding username and password and domain name to reach out for artifacts; but here in the AXA company I can't reach out for artifacts unless this NTLM authentication is properly supported. Also: WHO OF YOU MAVEN GUYS CAN TELL ME how to best approach? 1. Does Axis2-1.5 and greater support scope=soapsession correctly; I've read somewhere that this is not any longer the case; Unfortunately I lost my pointer to this information, hence I can't ask the author. And again; this feature seems to be so exotic but is there, that nobody helps me. 2. WHO OF YOU MAVEN DEVELOPERS can tell me that maven-2.2.1 and above used to build Axis2-1.5 and above can reach through proxies using username password and domain name and is able to deal with NTLM authentication correctly? If this does not run on maven-1.1 why should it run on maven-2 and maven-3? I will certainly go any build maven-2.2.1 and port it to OpenVMS and hope that it can reach through proxy protected networks to get artifacts downloaded. Josef -Ursprüngliche Nachricht- Von: Kathryn Huxtable [mailto:kath...@kathrynhuxtable.org] Gesendet: Dienstag, 24. August 2010 19:14 An: Maven Users List Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS Egads, is anyone still using Maven 1? If so, why? -K On Aug 24, 2010, at 11:40 AM, Wayne Fay wrote: Wasting time
AW: maven-1.1 build-bootstrap fails with OpenVMS
It would be very fine if BASIC Authentication would be enforced by default when
one opens an URLConnection in OpenVMS and other platforms. But that is not the
case. Instead it goes into some kind of NTLM conversation and fails in OpenVMS
on JDK 5.0 (that can be seen when I run Ethereal)
I have found the sources below on the web: And I like to see now how it is
going for BASIC Authentication on my OpenVMS machine. So far when I try to
debug I can see the code called in rt.jar from sun. I can see code because
src.zip is in the source class path. But as the rt.jar was not complied with
the -g option I can't see any argument values but bunches of asynchronity when
doing single steping; Hence I cannot see the argument values passed so deep in
code from the java system properties into critical rt.jar routines used to open
an connection with the proper authorization and proxy data, called.
How would you go from there to see argument values passed if arguments belong
to sun rt.jar code not complied with the -g option; I can only see argument
values in my own short code. Do I get somewhere an rt.jar which was compiled
with the -g option or do I have to make that myself a project?
/*
* TestJDKNTLM.java
*
* Created on 30. August 2010, 15:19
*
*/
package axawl.spezpla.jdkntlmauth;
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import java.net.URL;
import java.net.URLConnection;
/**
*
* @author C770817
*/
public class TestJDKNTLM {
private void execute() throws IOException {
#1System.setProperty(proxySet, true);
#2System.setProperty(http.proxyHost, bcproxy.ch.winterthur.com);
#3System.setProperty(http.proxyPort, 8080);
#4System.setProperty(http.proxyUser, C770817);
#5System.setProperty(http.proxyPassword, mydomainpassword);
#6System.setProperty(http.auth.ntlm.domain, ourdomain);
URL url = new URL(http://www.ks-net.ch;);
URLConnection conn = url.openConnection();
conn.setAllowUserInteraction(true);
BufferedReader reader = new BufferedReader(new
InputStreamReader(conn.getInputStream()));
int read = 0;
String body = null;
do {
body = reader.readLine();
System.out.println(body);
} while (body != null);
}
/**
* @param args the command line arguments
*/
public static void main(String[] args) throws IOException {
new TestJDKNTLM().execute();
}
}
Commenting #1 above out shows no effect on Vista and on OpenVMS
Commenting #4, #5, #6 out has no effect on Vista and on OpenVMS
Commenting #2 and/or #3 out shows an effect on OpenVMS and VISTA
I have removed all properties from files like build.properties;
So ANT and JAVA does not know this properties unless code makes em known.
Effe4ct: on VISTA NTLM takes place and all works due to NTLM works, on OpenVMS
I get 407 errors and al fails!
That is to say: NTLM authentication still works because the magic stuff is at
the sun corner for VISTA and fails short for the OpenVMS part, but is done in
the JDK itself with little to no effect doing such things here in code.
But what is going on there, that remains the big question?
To make it worse - stepping through remote code at OpenVMS shows asynchronity
at the rt.jar level; some lines are hit as they should and some are not. That
means the sources and or JDK versions used on VISTA and Open VMS are the same
but not really! JDK's and/or sources of JDK 1.5 may vary in minor ways, making
it hard to debug using a modern IDE like NetBeans and remote debugging. Guess I
have to use stone time jdb on OpenVMS to not be enforced to remote debugging
and asynchronity when doing single stepping.
So far the nice properties;
On OpenVMS I can conclude: That BASIC authentication does not work if the proxy
server asks for NTLM and BASIC because the client side code at OpenVMS does not
know how to handle it. And this magic belongs to rt.jar (so far quality and
portability among platforms and testing).
Josef
-Ursprüngliche Nachricht-
Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag
von Anders Hammar
Gesendet: Montag, 30. August 2010 15:30
An: Maven Users List
Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS
AFAIK, basic auth is what is used out-of-the-box. If you want something
else, then you need some configuration. So you should be fine.
/Anders
On Mon, Aug 30, 2010 at 15:15, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
Anders
Thanks for the info, I went through that already, A DN it is formaven2 and
maven3
However as you can read as well .. just below the box on tghe mentioned
page/like
http://maven.apache.org/guides/mini/guide-proxies.html
Please note that currently NTLM proxies are not supported as they have not
been tested.
You may be able to use
maven-1.1 build-bootstrap fails with OpenVMS
I have successfully built maven-1.1 from .\maven\maven-1\trunks\core on
my Vista PC / Java 1.5 from DOS and from NetBeans 5.5.1
Using maven-1.1 I have successfully built axis2-1.2; and thats why I
need maven also on a OpenVMS Integrity Server from HP;
There - Axis2-1.2 - is up and running there; but I need to compile/debug
axis2-1.2 to figure/detect out undocumented behaviour.
i.e. - why my destroy() method is no longer called in
scope=soapsession
So I like to complement our development environment on OpenVMS with
maven-1.1 first and then subseqeuntl upgrade tomaven 2 and
Maven 3 when done with maven 1.1
However
IA64 ant -f build-bootstrap.xml
Fails on OpenVMS but runs on the Vista PC
IA64ant -f build-bootstrap.xml
Buildfile: build-bootstrap.xml
check-maven-home:
check-maven-home-local-default:
check-maven-home-local:
check-maven-repo-local:
check-properties:
check-env:
[echo] maven.home = /dkb3/apache-maven-1.1
env:
[echo] maven.home = /dkb3/apache-maven-1.1
[echo] maven.home.local = /dkb3/stadelma/.maven
[echo] maven.repo.local = /dkb3/stadelma/.maven/repository
[echo]
[echo]
[echo] +--
[echo]
[echo] | WARNING WARNING WARNING WARNING WARNING WARNING WARNING
[echo]
[echo] |
[echo]
. . . .
[echo] |
[echo]
[echo] | WARNING WARNING WARNING WARNING WARNING WARNING WARNING
[echo]
[echo] +--
clean-maven-home:
[delete] Deleting directory /dkb3/apache-maven-1.1/bin
[mkdir] Created dir: /dkb3/apache-maven-1.1/bin
[delete] Deleting directory /dkb3/apache-maven-1.1/lib
[mkdir] Created dir: /dkb3/apache-maven-1.1/lib
[delete] Deleting directory /dkb3/apache-maven-1.1/plugins
[mkdir] Created dir: /dkb3/apache-maven-1.1/plugins
maven-phase-1:
[delete] Deleting directory
/dkb3/sw-projekte/asf/maven/maven-1/trunks/core/bootstrap
[mkdir] Created dir:
/dkb3/sw-projekte/asf/maven/maven-1/trunks/core/bootstrap/bootstrap-clas
ses
[javac] Compiling 6 source files to
/dkb3/sw-projekte/asf/maven/maven-1/trunks/core/bootstrap/bootstrap-clas
ses
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[echo]
[echo]
[echo] |
[echo]
[echo] | LOADING BOOTSTRAP TASKDEF...
[echo]
[echo] |
[echo]
[echo]
[echo] |
[echo]
[echo] | RUNNING BOOTSTRAP TASK...
[echo]
[echo] |
[mkdir] Created dir:
/dkb3/sw-projekte/asf/maven/maven-1/trunks/core/bootstrap/bin
[bootstrap] Using the following for your maven.repo.local:
/dkb3/stadelma/.maven/repository
[bootstrap] Using the following for your local repository:
/dkb3/stadelma/.maven/repository
[bootstrap] Using the following for your remote repositories:
[http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.m
aven.org/maven/]
[bootstrap] Downloading
http://people.apache.org/repo/m1-snapshot-repository/maven/jars/dom4j-1.
7-20060614.jar
[bootstrap] Error retrieving artifact from
[http://people.apache.org/repo/m1-snapshot-repository/maven/jars/dom4j-1
.7-20060614.jar]:
java.io.IOException: Not authorized by proxy.
[bootstrap] Downloading
http://repo1.maven.org/maven/maven/jars/dom4j-1.7-20060614.jar
[bootstrap] Error retrieving artifact from
[http://repo1.maven.org/maven/maven/jars/dom4j-1.7-20060614.jar]:
java.io.IOException: No
t authorized by proxy.
BUILD FAILED
/dkb3/sw-projekte/asf/maven/maven-1/trunks/core/build-bootstrap.xml:180:
Failed to download dependency
Total time: 11 seconds
IA64
IA64ty sys$login:build.properties
# - Proxy setup -
user.home=/dkb3/stadelma
#
# - Default Base Path for Dependent Packages -
# Replace this path with the directory path where
# dependencies binaries should be downloaded.
#base.path=C:\\Users\\C770817\\.maven\\base.path
base.path=/dkb3/stadelma/.maven/base.path
#
#--- maven specific
#
maven.proxy.host=bcproxyserver.ch.winterthur.com
maven.proxy.port=8080
maven.proxy.username=C770817
maven.proxy.password=Sep10orbx
maven.proxy.ntlm.host=C007368
maven.proxy.ntlm.domain=CH.WINTERTHUR.COM
maven.proxy.use=on
maven.repo.local=${user.home}/.maven/repository
maven.home=/dkb3/apache-maven-1.1
env.MAVEN_HOME=${maven.home}
IA64
Note: our proxy server as identified accepts both NTLM and then BASIC
authentication
I have successfully pass this infomation and checked using some logging
via the build.properties file as shown.
The thing is that all items are accepted except
maven.proxy.ntlm.domain=CH.WINTERTHUR.COM
When I look at Ethereal, a network protocol analyzer I observer the
following:
ON VISTA
The build-bootstrap uses NTLM authentication because NTLM is presented
first by the proxy-server.
It does not use basic authntication for downloading artefacts as shown.
ON INTEG1 (OVMS)
The build-bootstrap uses NTLM authentication because NTLM is
AW: maven-1.1 build-bootstrap fails with OpenVMS
Wayne, Wasting time? It seems to me that I am not the only one having problems with Authentication. In particular with NTLM Authentication, or forcing an Authentication Schema. Therefore again;: How do I force BASIC authentication using maven-1.1 either with maven-1.1 or maybe I can do it outside maven-1.1-code through a system property. java is full of it but I am not the expert on Authentication else I would dive down in Java JDK code to see what missing bits and bytes I can feed via a system property just tell the Authenticator or the like that we want to go with BASIC authentication. I am not the only one which has problems to force an Authentication schema. Forcing one or the other Authentication is a long lasting burner in the web. While I can certainly download artifacts for the maven build-bootstrap, how do I do it best to not get? But then maven-1.1 uses further downloads for plugins and just all what is still not mavenized for maven-2 etc. i.e. axis2-1.2 etc. etc. shall I download all this artifacts as well by hand? If our companies maven repository would not just keep artifacts for maven 2 and 3 but for maven 1 as well, then I would not be here asking silly questions and waste others time. Josef -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Dienstag, 24. August 2010 16:11 An: Maven Users List Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS HOW CAN I FORCE THAT BASIC ATHENTICATION IS USED but NEVER NTLM This would solve my problem Why are you wasting your time with this? Just download the artifacts (jar files etc) yourself and copy it to the proper Maven1 local repo cache structure. I haven't used M1 in a long time so I will admit that I forget how all that works, but it is not required that Maven itself download all artifacts, simply that they are available to be used during the build. And/or use a Maven Repo Manager that is M1-compatible. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: maven-1.1 build-bootstrap fails with OpenVMS
Wayne Or keep it more simple, maybe you understand me then. What would you say if subversion, would not work just because it is unable to authenticate properly with your proxy server? Would that tool be useful for you? Not saying what artifacts you need or intend to download with it in the future. Maven is in this sense like subversion. It hast to download missing artifacts whenever it detects at unforeseen times that an artifact has to be downloaded. This automatic dependency management AND download capability makes maven what it is: MAVEN - I love it. Josef -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Dienstag, 24. August 2010 16:11 An: Maven Users List Betreff: Re: maven-1.1 build-bootstrap fails with OpenVMS HOW CAN I FORCE THAT BASIC ATHENTICATION IS USED but NEVER NTLM This would solve my problem Why are you wasting your time with this? Just download the artifacts (jar files etc) yourself and copy it to the proper Maven1 local repo cache structure. I haven't used M1 in a long time so I will admit that I forget how all that works, but it is not required that Maven itself download all artifacts, simply that they are available to be used during the build. And/or use a Maven Repo Manager that is M1-compatible. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
WG: jelly plugin /artifact plugin
-Ursprüngliche Nachricht- Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 12. September 2006 09:55 An: Stadelmann Josef Betreff: Re: jelly plugin /artifact plugin I don't use maven 1 since a very long time. You can send your mail on maven users list users@maven.apache.org Emmanuel Stadelmann Josef a écrit : Hi Michal, Hi Emmanuel On OpenVMS, uisng BASH, JAVA 142, on the way to build AXIS2 I can successfully build i.e. the Data Binding module of Axis2. But at the /dsa5/axis2/src dierectory level, on the way to atain the multiproject goal all runs fine until this first installing comes. Do I have a mix up of versions? Im using BASH$ /dsa5/apache/maven/bin/maven (calling a .sh fle) without any more arguments and without any modifications to the .sh file launching maven AXIS2 demands on MAVEN 1.0.2 as per documentation. Very thankfule for a hint Josef Stadelmann working on Alpha OpenVMS - BASH - JAVA 142 bash$ /dsa5/apache/maven/bin/maven __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 build:start: jar: multiproject:install: multiproject:projects-init: [echo] Gathering project list Starting the reactor... Our processing order: Apache Axis 2.0 - Common Apache Axis 2.0 - Java2WSDL Apache Axis 2.0 - Core Apache Axis 2.0 - Data Binding Apache Axis 2.0 - Addressing Apache Axis 2.0 - Code Generation Apache Axis 2.0 - JiBX Data Binding Apache Axis 2.0 - Samples + | Gathering project list Apache Axis 2.0 - Common | Memory: 7M/10M + + | Gathering project list Apache Axis 2.0 - Java2WSDL | Memory: 7M/10M + + | Gathering project list Apache Axis 2.0 - Core | Memory: 7M/10M + + | Gathering project list Apache Axis 2.0 - Data Binding | Memory: 7M/10M + + | Gathering project list Apache Axis 2.0 - Addressing | Memory: 7M/10M + + | Gathering project list Apache Axis 2.0 - Code Generation | Memory: 7M/10M + + | Gathering project list Apache Axis 2.0 - JiBX Data Binding | Memory: 7M/10M + + | Gathering project list Apache Axis 2.0 - Samples | Memory: 7M/10M + Starting the reactor... Our processing order: Apache Axis 2.0 - Common Apache Axis 2.0 - Java2WSDL Apache Axis 2.0 - Core Apache Axis 2.0 - Data Binding Apache Axis 2.0 - Addressing Apache Axis 2.0 - Code Generation Apache Axis 2.0 - JiBX Data Binding Apache Axis 2.0 - Samples + | Executing multiproject:install-callback Apache Axis 2.0 - Common | Memory: 7M/10M + multiproject:goal: build:start: multiproject:install-callback: [echo] Running jar:install for Apache Axis 2.0 - Common java:prepare-filesystem: java:compile: [echo] Compiling to /dsa5/axis2/src/modules/common/target/classes [echo] == NOTE: Targetting JVM 1.4, classes will not run on earlier JVMs == [javac] Compiling 14 source files to /dsa5/axis2/src/modules/common/target/classes java:jar-resources: Copying 1 file to /dsa5/axis2/src/modules/common/target/classes test:prepare-filesystem: [mkdir] Created dir: /dsa5/axis2/src/modules/common/target/test-classes [mkdir] Created dir: /dsa5/axis2/src/modules/common/target/test-reports test:test-resources: test:compile: [echo] No test source files to compile. test:test: [echo] No tests to run. jar:jar: [jar] Building jar: /dsa5/axis2/src/modules/common/target/axis2-common-1.0.jar jar:install: [echo] Installing... Uploading to axis2/jars/axis2-common-1.0.jar: (42K) BUILD FAILED File.. /dsa5/stadelma/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly Element... maven:reactor Line.. 217 Column -1 Unable to obtain goal [multiproject:install-callback] -- /dsa5/stadelma/.maven/cache/maven-artifact-plugin-1.5.2/plugin.jelly :62:-1: artifact:artifact-install Error getting the project as a string Total time: 4 minutes 2 seconds Finished at: Tue Sep 12 08:37:22 MEST 2006 - To unsubscribe, e-mail: [EMAIL
