Re: Plugins not properly loading properties
tomcat:deploy could possibly fork a new process performing a maven build with the lifecycle (the docs should tell). I haven't used that plugin as I'm a Cargo addict...:-) /Anders On Mon, Sep 19, 2011 at 22:35, Maven User maven.2.u...@gmail.com wrote: BTW - this is totally not the behavior we're seeing with a tomcat:deploy. That seems to go through all the standard build lifecycle goals, then NOT pull in any dynamically loaded configuration... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Antwort: Re: Incorrect assembly created with Maven 3.0.3
Hi, Thorsten Heit wrote: ...snip ... But what puzzles me is that the archives created by Maven 2.2.1 and Maven 3.0.3 are different, and I don't see a reason why... ...snip... Hi there, Did you ever get anywhere with this? I'm seeing the same problem: Maven 3.0.3 adds batik-js-1.7.jar and omits serializer-2.7.1.jar. Though I am not positive, I believe this is the cause of an exception I see at runtime, the stack trace of which starts like this: java.lang.IllegalAccessError: org/apache/xml/serializer/ExtendedContentHandler at org.apache.xalan.transformer.TransformerImpl.createSerializationHandler (TransformerImpl.java:1233) ... I get a ClassNotFoundException at runtime. I don't know exactly which class, but it was one from the serializer jar... Unfortunately the only solution I have so far is to directly add a dependency to the serializer jar in the pom although no class in the project uses it - it is used transitively by xerces or xalan I guess... Regards Thorsten
Re: Re: Incorrect assembly created with Maven 3.0.3
Hi, Just a wild guess, do you have a dependencyManagament handling these artifacts where the scope is defined? I've seen different behavior between Maven 2.x and 3.0.x due to this (MJBOSSPACK-40 [1]). No, I haven't used dependency management. I simply referenced xerces and/or xalan (don't remember it exactly because I changed the project in the meantime...) Regards Thorsten
mvn dependency tree not working
While building a sub-project where I am trying to find the jar dependency showing up in compliation which i am not able to locate in code/pom. Tried command ;- mvn dependency:tree this doesnt show up the dependency tree this jar doesnt exist on nexus even, so i wanna see where is this defined in pom or dependency jar is calling it. error is Downloaded: http://IP:8081/nexus/content/groups/public-snapshots/abc/abc-web-utils/1.1-SNAPSHOT/maven-metadata.xml (351 B at 6.0 KB/sec) Downloading: http://IP:8081/nexus/content/groups/public/org/hibernate/ehcache/hibernate-core/3.3.1.GA/hibernate-core-3.3.1.GA.pom [WARNING] The POM for org.hibernate.ehcache:hibernate-core:jar:3.3.1.GA is missing, no dependency information available [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 6.065s [INFO] Finished at: Tue Sep 20 16:29:32 IST 2011 [INFO] Final Memory: 8M/1009M [INFO] [ERROR] Failed to execute goal on project com.abc.data.web: Could not resolve dependencies for project com.abc:com.abc.data.web:war:3.0.0.M1: Could not find artifact org.hibernate.ehcache:hibernate-core:jar:3.3.1.GA in abc (http://IP:8081/nexus/content/groups/public) - [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/DependencyResolutionException [kapila.narang@svn data-web]$ pwd /home/kapilacvs/data-3.0/data-web/data-web have made entry in pom also - plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.3/version /plugin maven version i am using is /usr/local/apache-maven-3.0/bin/mvn i have tried to run same command- mvn dependency:analyze-only on its parent pom its runs fine for other sub-projects. but give issue in this specific project. Doesn't give any dependency graph at all build gives build failure. was trying to understand what harm can these make expect cleaner code- [WARNING] Used undeclared dependencies found: [WARNING] Unused declared dependencies found: -- View this message in context: http://maven.40175.n5.nabble.com/mvn-dependency-tree-not-working-tp4822352p4822352.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugins not properly loading properties
Heh - yeah a quick look at the docs and it says: - Requires a Maven 2.0 project to be executed. - Since version: 1.0-alpha-2. - Invokes the execution of the lifecycle phase package prior to executing itself. There's no mention of forking and all the documentation around this plugin kinda stinks. Cargo is also a great option but one of the things we try to do is load property files from a jar and put the results into the reactor. I think this functionality is gone in maven 3 though On Tue, Sep 20, 2011 at 3:32 AM, Anders Hammar and...@hammar.net wrote: tomcat:deploy could possibly fork a new process performing a maven build with the lifecycle (the docs should tell). I haven't used that plugin as I'm a Cargo addict...:-) /Anders On Mon, Sep 19, 2011 at 22:35, Maven User maven.2.u...@gmail.com wrote: BTW - this is totally not the behavior we're seeing with a tomcat:deploy. That seems to go through all the standard build lifecycle goals, then NOT pull in any dynamically loaded configuration... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugins not properly loading properties
There has never been such native Maven support (i.e. in Maven core). /Anders On Tue, Sep 20, 2011 at 14:57, Maven User maven.2.u...@gmail.com wrote: Heh - yeah a quick look at the docs and it says: - Requires a Maven 2.0 project to be executed. - Since version: 1.0-alpha-2. - Invokes the execution of the lifecycle phase package prior to executing itself. There's no mention of forking and all the documentation around this plugin kinda stinks. Cargo is also a great option but one of the things we try to do is load property files from a jar and put the results into the reactor. I think this functionality is gone in maven 3 though On Tue, Sep 20, 2011 at 3:32 AM, Anders Hammar and...@hammar.net wrote: tomcat:deploy could possibly fork a new process performing a maven build with the lifecycle (the docs should tell). I haven't used that plugin as I'm a Cargo addict...:-) /Anders On Mon, Sep 19, 2011 at 22:35, Maven User maven.2.u...@gmail.com wrote: BTW - this is totally not the behavior we're seeing with a tomcat:deploy. That seems to go through all the standard build lifecycle goals, then NOT pull in any dynamically loaded configuration... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugins not properly loading properties
In 2.2.1, this worked flawlessly. In 3.X this (known) feature no longer works. http://www.mailinglistarchive.com/html/users@maven.apache.org/2011-01/msg00729.html Ok, I'm clear now :-) On Tue, Sep 20, 2011 at 9:13 AM, Anders Hammar and...@hammar.net wrote: There has never been such native Maven support (i.e. in Maven core). /Anders On Tue, Sep 20, 2011 at 14:57, Maven User maven.2.u...@gmail.com wrote: Heh - yeah a quick look at the docs and it says: - Requires a Maven 2.0 project to be executed. - Since version: 1.0-alpha-2. - Invokes the execution of the lifecycle phase package prior to executing itself. There's no mention of forking and all the documentation around this plugin kinda stinks. Cargo is also a great option but one of the things we try to do is load property files from a jar and put the results into the reactor. I think this functionality is gone in maven 3 though On Tue, Sep 20, 2011 at 3:32 AM, Anders Hammar and...@hammar.net wrote: tomcat:deploy could possibly fork a new process performing a maven build with the lifecycle (the docs should tell). I haven't used that plugin as I'm a Cargo addict...:-) /Anders On Mon, Sep 19, 2011 at 22:35, Maven User maven.2.u...@gmail.com wrote: BTW - this is totally not the behavior we're seeing with a tomcat:deploy. That seems to go through all the standard build lifecycle goals, then NOT pull in any dynamically loaded configuration... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugins not properly loading properties
That's something different. I said Maven 2 core doesn't have support for reading properties from a file. There might be plugins, but no such support in core. /Anders On Tue, Sep 20, 2011 at 15:20, Maven User maven.2.u...@gmail.com wrote: In 2.2.1, this worked flawlessly. In 3.X this (known) feature no longer works. http://www.mailinglistarchive.com/html/users@maven.apache.org/2011-01/msg00729.html Ok, I'm clear now :-) On Tue, Sep 20, 2011 at 9:13 AM, Anders Hammar and...@hammar.net wrote: There has never been such native Maven support (i.e. in Maven core). /Anders On Tue, Sep 20, 2011 at 14:57, Maven User maven.2.u...@gmail.com wrote: Heh - yeah a quick look at the docs and it says: - Requires a Maven 2.0 project to be executed. - Since version: 1.0-alpha-2. - Invokes the execution of the lifecycle phase package prior to executing itself. There's no mention of forking and all the documentation around this plugin kinda stinks. Cargo is also a great option but one of the things we try to do is load property files from a jar and put the results into the reactor. I think this functionality is gone in maven 3 though On Tue, Sep 20, 2011 at 3:32 AM, Anders Hammar and...@hammar.net wrote: tomcat:deploy could possibly fork a new process performing a maven build with the lifecycle (the docs should tell). I haven't used that plugin as I'm a Cargo addict...:-) /Anders On Mon, Sep 19, 2011 at 22:35, Maven User maven.2.u...@gmail.com wrote: BTW - this is totally not the behavior we're seeing with a tomcat:deploy. That seems to go through all the standard build lifecycle goals, then NOT pull in any dynamically loaded configuration... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven build with android API 11 failed, Cann't find symbol
Well you are sort of right. Let me clarify. 1. yes.. Google/Android does not publish to Maven Central (although imho they should) 2. the android4maven project, led by Robert Manning, and myself got the android jar and some others into Maven central. This is done off the Android Open Source Project and google allowed us to push into their namespace (this is the class skeleton stuff - the android jar in the SDK does not have any implementations) http://sourceforge.net/projects/android4maven/ 3. since Android 3.0 (api level 11) and beyond are not in AOSP these are not in central, same applies for the compatibility package, maps and others 4. My Maven Android SDK Deployer can install the android.jar, maps.jar and the compatibilty jar files into your local maven repo or into a local repository server so you can use it in a team easily. This allows you to develop with any API published in the SDK including Android 3.0 and up and the compatibility package https://github.com/mosabua/maven-android-sdk-deployer 5. All this and more is discussed on the Maven Android mailing list.. https://groups.google.com/forum/#!forum/maven-android-developers https://groups.google.com/forum/#%21forum/maven-android-developers Hope that clarifies things a bit. manfred On 11-09-19 07:53 AM, Guillaume Polet wrote: OK, I guess this is the main issue then. From what I understand: * Android guys do not publish their jars to a public Maven repo * If the version used in your dependencies matches the ones used by the Android team, then 2.2= API Level 8. If you want API Level 11, you need version 3.0 (http://developer.android.com/sdk/android-3.0.html) * There are some cool dudes who create jars with Class skeletons and empty method stubs to reproduce all the class names and method signatures so that you can compile your project. Unfortunately, the latests jars have not been created and/or published yet. * There is another guy (who just replied you) who has created a project just for the purpose of deploying the jars from the Android SDK to your local Maven repository: https://github.com/mosabua/maven-android-sdk-deployer. Read this for how to use this tool: https://github.com/mosabua/maven-android-sdk-deployer/blob/master/README.markdown Cheers, Guillaume Le 19/09/2011 16:23, darakok a écrit : I think you're right. My dependency references Android 2.2. dependency groupIdandroid/groupId artifactIdandroid/artifactId version2.2_r2/version scopeprovided/scope /dependency Thanks for your help. darakok -- View this message in context: http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4819154.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn dependency tree not working
Hi On 2011-09-20 14:30, kapila wrote: While building a sub-project where I am trying to find the jar dependency showing up in compliation which i am not able to locate in code/pom. Tried command ;- mvn dependency:tree this doesnt show up the dependency tree this jar doesnt exist on nexus even, so i wanna see where is this defined in pom or dependency jar is calling it. error is Downloaded: http://IP:8081/nexus/content/groups/public-snapshots/abc/abc-web-utils/1.1-SNAPSHOT/maven-metadata.xml (351 B at 6.0 KB/sec) Downloading: http://IP:8081/nexus/content/groups/public/org/hibernate/ehcache/hibernate-core/3.3.1.GA/hibernate-core-3.3.1.GA.pom [WARNING] The POM for org.hibernate.ehcache:hibernate-core:jar:3.3.1.GA is missing, no dependency information available The message above says that it cannot find org.hibernate.ehcache:hibernate-core:3.3.1.GA in your Nexus repository. Looking at what is available in the Central repository it looks like you have used the wrong groupId in your POM. It should be org.hibernate. The dependency can't do it's job if it cannot find all the dependencies for a given project. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 6.065s [INFO] Finished at: Tue Sep 20 16:29:32 IST 2011 [INFO] Final Memory: 8M/1009M [INFO] [ERROR] Failed to execute goal on project com.abc.data.web: Could not resolve dependencies for project com.abc:com.abc.data.web:war:3.0.0.M1: Could not find artifact org.hibernate.ehcache:hibernate-core:jar:3.3.1.GA in abc (http://IP:8081/nexus/content/groups/public) - [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/DependencyResolutionException [kapila.narang@svn data-web]$ pwd /home/kapilacvs/data-3.0/data-web/data-web have made entry in pom also - plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.3/version /plugin maven version i am using is /usr/local/apache-maven-3.0/bin/mvn i have tried to run same command- mvn dependency:analyze-only on its parent pom its runs fine for other sub-projects. but give issue in this specific project. Doesn't give any dependency graph at all build gives build failure. was trying to understand what harm can these make expect cleaner code- [WARNING] Used undeclared dependencies found: [WARNING] Unused declared dependencies found: -- View this message in context: http://maven.40175.n5.nabble.com/mvn-dependency-tree-not-working-tp4822352p4822352.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Not a valid plugin file: maven-taglib-plugin-1.4.2.jar
Hello all, I have been asked to drive a legacy build for the first time, and I am getting the error in the Subject above. It is a Maven 1.0 build and supposedly has been working for quite some time. The console output of the action that has the error is here: E:\foo\bar\snark\mainmaven -e jar:deploy Maven options are Maven options are -server -Xms400m -Xmx400m -XX:+UseConcMarkSweepGC -XX:+UseParNewGC __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 Attempting to download buildtool-main-SNAPSHOT.jar. org.apache.maven.MavenException: Not a valid plugin file: E:\foo\bar\snark\main\lib\maven-taglib\plugins\maven-taglib-plugin-1.4.2.jar at org.apache.maven.plugin.PluginManager.installPlugin(PluginManager.java:910) at org.apache.maven.plugin.PluginManager.installPlugin(PluginManager.java:862) at org.apache.maven.plugin.PluginManager.processDependencies(PluginManager.java:448) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:642) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:488) at org.apache.maven.cli.App.main(App.java:1239) 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:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) You have encountered an unknown error running Maven. Please help us to correct this problem by following these simple steps: - read the Maven FAQ at http://maven.apache.org/faq.html - run the same command again with the '-e' parameter, eg maven -e jar - search the maven-user archives for the error at http://nagoya.apache.org/eyebrowse/SummarizeList?listName=users@maven.apache.org - post the output of maven -e to JIRA at http://jira.codehaus.org/BrowseProject.jspa?id=10030 (you must sign up first) - run 'maven --info' and post the output as the environment to the bug above Total time: 2 seconds Finished at: Tue Sep 20 09:32:45 PDT 2011 E:\foo\bar\snark\main I am just getting started on this, but wanted to check with the group as to whether this is a common issue. I found several copies of maven-taglib-plugin-1.4.2.jar on the system in question and tried copying one into this location, but this produced the same error. Does anyone recall this issue when working with Maven 1.0? Thank you very muchjust for reading this novella. ;0) Christopher [cid:image001.png@01CAF080.AD65F1E0] Christopher Hahn The Dude SM Configuration Management RD Services, Hewlett-Packard Phone: 858-655-4096 Cell: 619-630-9791 ch...@hp.commailto:christopher.h...@hp.com Visit our SPE Portalhttp://teams5.sharepoint.hp.com/teams/SPE/default.aspx
Re: Not a valid plugin file: maven-taglib-plugin-1.4.2.jar
It is a Maven 1.0 build and supposedly has been working for quite some time. Does anyone recall this issue when working with Maven 1.0? No, but I haven't touched M1 in a very long time. You should seriously just spend an hour +/- converting it to work with Maven2 or M3 rather than debugging/fixing this old M1 build, IMO. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Not a valid plugin file: maven-taglib-plugin-1.4.2.jar
On 2011-09-20 21:31, Wayne Fay wrote: It is a Maven 1.0 build and supposedly has been working for quite some time. Does anyone recall this issue when working with Maven 1.0? No, but I haven't touched M1 in a very long time. You should seriously just spend an hour +/- converting it to work with Maven2 or M3 rather than debugging/fixing this old M1 build, IMO. I agree. You can get a jump start by using the convert goal of Maven One Plugin. It will convert most of your Maven 1 project.xml into a Maven 2 pom.xml. http://maven.apache.org/plugins/maven-one-plugin/ Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
