RE: how to convert unique snaphot into non-unique snaphot on downloading from nexus
Could you explain what you mean by Unique and non-Unique? From: sahil_tech [sahilaggarwal1...@gmail.com] Sent: Friday, October 25, 2013 8:55 AM To: users@maven.apache.org Subject: Re: how to convert unique snaphot into non-unique snaphot on downloading from nexus Can somebody please check the issue posted above and provide a fix if possible. I am completely stuck due to this and management now wants me to revert the mvn deploy to mvn install. -- View this message in context: http://maven.40175.n5.nabble.com/how-to-convert-unique-snaphot-into-non-unique-snaphot-on-downloading-from-nexus-tp5773312p5773827.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven build not populating with arabic characters in jasper reports
It seems that when your reports are built from within eclipse your Arabic font is in your classpath and when built with Maven, it isn't. Use iReport to export the font as an extension, manually install the generated jar file onto your repository (or upload it to your repository manager if you are using one such as Nexus), and use it as a dependency. Let us know if this helped. From: sarmahdi [sarma...@hotmail.com] Sent: Saturday, April 20, 2013 2:11 AM To: users@maven.apache.org Subject: Maven build not populating with arabic characters in jasper reports Hello All,I tried searching for this issue and i couldn't find anything. When i build my application with eclipse my jasper reports are coming correctly in English and Arabic. When i build it through maven, my English reports are coming correctly but my Arabic reports are generated but with no Arabic. Some of the labels are coming as in English but some are not even there they are just empty. The data that is supposed to come in numbers is also not showing. I cant say that don't have fonts or something as the same reports work when i build it through eclipse and generate an ear file through that. but when maven does the ear file they don't work in Arabic.What am I missing here. Hows is maven related to this anyways.Any help will be appreciate.ThanksSyed. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-build-not-populating-with-arabic-characters-in-jasper-reports-tp5754151.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: Dependency entry changes runtime
I posted this in Weblogic's forum and waited. But nothing useful came out of it. If I restart WLS (without having the dependency tag in POM file), the problem goes away... This is the post in Weblogic's forum: https://forums.oracle.com/forums/thread.jspa?threadID=2413507&tstart=0 -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: July-11-12 3:14 PM To: Maven Users List Subject: Re: Dependency entry changes runtime > Now that I think again, the problem is not that the class is not > found. The error says "java.lang.IllegalArgumentException: Object: > com.xxx.entities.XyzEntity@3a18c1 is not a known entity type" which is > coming from EclipseLink in WebLogic. > > But I wonder why making a trivial change (as it seems) in POM file > should make this behave differently. I gotta be an issue in JPA. So out of > this list's scope. I think there must be some additional difference(s) between the "working" and "not working" state that you have simply not found -- but not necessarily in the Jar files you are producing now, perhaps in some other piece/component. If you sort it out, come back and give us more details, if for no reason other than to benefit future Google searchers who run into similar problems with EclipseLink. 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
RE: Dependency entry changes runtime
Thanks mate. Still Identical MANIFEST(!) and when I compared the JARs with a tool (BeyondCompare) I could only see one difference which is maven directory under META-INF directory. Now that I think again, the problem is not that the class is not found. The error says "java.lang.IllegalArgumentException: Object: com.xxx.entities.XyzEntity@3a18c1 is not a known entity type" which is coming from EclipseLink in WebLogic. But I wonder why making a trivial change (as it seems) in POM file should make this behave differently. I gotta be an issue in JPA. So out of this list's scope. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: July-11-12 12:33 PM To: Maven Users List Subject: Re: Dependency entry changes runtime OK so back up. First, leave the dependency out of A and run "mvn clean package". Set that jar file aside (rename it and move it out of target or clean will remove it.) Now add the dependency and run "mvn clean package". Set that jar file aside like you did before. Now use some tool to unzip both and compare the contents. Surely there is a difference you simply have not accounted for yet. Wayne On Wed, Jul 11, 2012 at 1:34 PM, Amir Gheibi wrote: > Here is A's Manifest entry which as I mentioned, is identical in both > scenarios. > > Manifest-Version: 1.0 > Built-By: bm03043 > Build-Jdk: 1.6.0_18 > Created-By: Apache Maven 3.0.4 > Archiver-Version: Plexus Archiver > Extension-List: entities > entities-Extension-Name: com.xxx.entities > > -Original Message- > From: Wayne Fay [mailto:wayne...@gmail.com] > Sent: July-11-12 11:13 AM > To: Maven Users List > Subject: Re: Dependency entry changes runtime > >> Runtime environment is a "Weblogic 10.3.3" in which "B" is registered as an >> Optional Package (Library) and there is an extension entry in A's MANIFEST >> that refers to it (that's how A finds B in runtime). >> >> I compared A's JAR file in both scenarios and I don't see any difference >> whatsoever except the POM file within the Maven directory, which as far as I >> understand, doesn't have any effect on runtime. >> >> Why would the dependency entry change runtime behavior? > > Didn't you already answer your own question? The answer is the > MANIFEST entry. If you check, the MANIFEST entry will (should) only > appear when the dependency is added with runtime scope. > > 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
RE: Dependency entry changes runtime
Here is A's Manifest entry which as I mentioned, is identical in both scenarios. Manifest-Version: 1.0 Built-By: bm03043 Build-Jdk: 1.6.0_18 Created-By: Apache Maven 3.0.4 Archiver-Version: Plexus Archiver Extension-List: entities entities-Extension-Name: com.xxx.entities -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: July-11-12 11:13 AM To: Maven Users List Subject: Re: Dependency entry changes runtime > Runtime environment is a "Weblogic 10.3.3" in which "B" is registered as an > Optional Package (Library) and there is an extension entry in A's MANIFEST > that refers to it (that's how A finds B in runtime). > > I compared A's JAR file in both scenarios and I don't see any difference > whatsoever except the POM file within the Maven directory, which as far as I > understand, doesn't have any effect on runtime. > > Why would the dependency entry change runtime behavior? Didn't you already answer your own question? The answer is the MANIFEST entry. If you check, the MANIFEST entry will (should) only appear when the dependency is added with runtime scope. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Dependency entry changes runtime
The dependency is added with "provided" scope and MANIFEST is identical in both scenarios. That MANIFEST entry that I mentioned is required for weblogic to make the connection between A and B. -Original Message- From: Wayne Fay Sent: July-11-12 11:13 AM To: Maven Users List Subject: Re: Dependency entry changes runtime > Runtime environment is a "Weblogic 10.3.3" in which "B" is registered as an > Optional Package (Library) and there is an extension entry in A's MANIFEST > that refers to it (that's how A finds B in runtime). > > I compared A's JAR file in both scenarios and I don't see any difference > whatsoever except the POM file within the Maven directory, which as far as I > understand, doesn't have any effect on runtime. > > Why would the dependency entry change runtime behavior? Didn't you already answer your own question? The answer is the MANIFEST entry. If you check, the MANIFEST entry will (should) only appear when the dependency is added with runtime scope. 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
Dependency entry changes runtime
Hi,
I have a project in which a module, say "A", has a runtime dependency (not
required during compile) to another module ("B").
Without explicitly adding the dependency to A's POM file it compiles
(everything is passed to A as "object"). But during runtime it won't find "B".
Even though it exists. But if I add the dependency tag to A's POM file (with
"provided" scope) and compile again, it'll find "B" during runtime.
Runtime environment is a "Weblogic 10.3.3" in which "B" is registered as an
Optional Package (Library) and there is an extension entry in A's MANIFEST that
refers to it (that's how A finds B in runtime).
I compared A's JAR file in both scenarios and I don't see any difference
whatsoever except the POM file within the Maven directory, which as far as I
understand, doesn't have any effect on runtime.
Why would the dependency entry change runtime behavior?
Thanks,
Amir
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: maven release plugin uses "git add" instead of svn commit
I guess Maven "conventionally" uses Git. This is what I have in my parent POM. Change connections to point to your SVN's trunk or release branch. scm:git:ssh://git@x/usr/local/git_repos/projectXYZ.git scm:git:ssh://git@x/usr/local/git_repos/projectXYZ.git HEAD -Original Message- From: nivea Sent: July-10-12 1:02 PM Subject: maven release plugin uses "git add" instead of svn commit In the parent pom.xml I have specified the scm url that points to the svn location. How do I force release plugin to use svn as the scm and not git. My configuration for release plugin: org.apache.maven.plugins maven-release-plugin 2.3.2 forked-path -Prelease false javasvn com.google.code.maven-scm-provider-svnjava maven-scm-provider-svnjava 2.0.3 -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-uses-git-add-instead-of-svn-commit-tp5713686.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven-ear-plugin - How to manipulate Manifest.MF of webModule and ejbModule?
I'm not sure about different behaviors. But I would normally get the JAR and
WAR plugins to edit respected modules' MANIFEST files.
-Original Message-
From: Mauricio
Sent: July-09-12 12:55 PM
Subject: maven-ear-plugin - How to manipulate Manifest.MF of webModule and
ejbModule?
Hello,
I have a multimodule maven project with the following structure:
| app (parent)
-- pom.xml
-- app-ear
-- pom.xml
-- app-ejb
-- src
-- pom.xml
-- app-web
-- src
-- pom.xml
|
This is my *app/pom.xml* (parent project) where I put all my application
dependencies:
|
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
com.mycompany
app
0.0.1-SNAPSHOT
pom
app
http://maven.apache.org
app-ejb
app-web
app-ear
javax.ejb
ejb-api
3.0
provided
javaee
javaee-api
5
provided
org.glassfish
javax.faces
2.0.9
provided
org.richfaces.ui
richfaces-components-ui
org.richfaces.core
richfaces-core-impl
org.richfaces
richfaces-bom
4.2.0.Final
import
pom
org.apache.maven.plugins
maven-compiler-plugin
2.4
1.6
1.6
|
This is my *app-ejb/pom.xml*:
|
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
app
com.mycompany
0.0.1-SNAPSHOT
app-ejb
ejb
org.apache.maven.plugins
maven-ejb-plugin
2.3
3.0
|
This is my *app-web/pom.xml*:
|
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
app
com.mycompany
0.0.1-SNAPSHOT
app-web
war
${project.groupId}
app-ejb
${project.version}
provided
app-web
org.apache.maven.plugins
maven-war-plugin
2.2
|
And finally this is my *app-ear/pom.xml* where I have the detais about how
generate my app.ear file:
|
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
app
com.mycompany
0.0.1-SNAPSHOT
app-ear
ear
${project.groupId}
app-ejb
ejb
${project.version}
provided
${project.groupId}
app-web
war
${project.version}
provided
app
maven-ear-plugin
2.7
5
war
lib
true
com.mycompany
app-web
app-web.war
/app
com.mycompany
app-ejb
app-ejb.jar
org.glassfish
javax.faces
org.richfaces.core
richfaces-core-api
org.richfaces.core
richfaces-core-impl
org.richfaces.ui
deploy with WebLogic-Maven-Plugin for development purposes
Hi everyone, We are using Maven 3 along with Nexus Pro to build applications and manage artifacts. Developers in the team don't have permission to deploy anything (SNAPSHOT or RELEASE) to Nexus, but only download. A CI server has been setup for that purpose. CI server builds SNAPSHOTs when developers commit something to SCM repo. CI server builds RELEASEs on-demand. We've created deployment projects that aggregate RELEASED jar files into ear files to be deployed on application and web servers. Each developer has a local Weblogic server and I'd like to use weblogic-maven-plugin (from Oracle, not from Codehaus) so they don't have to do the packaging and deployment to their local Weblogic server manually. I want them to be able to invoke the plugin's goals to install/update jar files (project's modules and their dependencies) on their weblogic and debug locally. My question is how to set it up. Once at the parent project level (would it take care of dependency jar files)? Or separately for each module within the project? There is also a problem of shared libraries. When packaged in an ear file (in "lib" directory by default), shared libraries' classes are visible to all modules within the ear file. When deployed separately, they have to be deployed as Optional Packages. Could I do that with this plugin? Thanks, Amir
RE: compile plugin
Run "whereis java" ("where java" in Windows) to find out how many java
executable you might have in PATH and which one is listed first. That's where
I'd start.
-Original Message-
From: chad.da...@emc.com [mailto:chad.da...@emc.com]
Sent: June-25-12 9:45 AM
To: users@maven.apache.org
Subject: compile plugin
I've got multiple jdk's installed. I'm trying to force maven to use my java 7.
I invoke mvn with a JAVA_HOME value that points to my desired jdk, but then
the compile plugin complains about 1.7 not being a valid source setting . . .
seems like the JAVA_HOME doesn't control the execution of the compile plugin .
. .
Ideas?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Getting Error in Maven
>From the output it can be seen Apache Maven 3.0.4 (r1232337; 2012-01-17 14:14:56+0530) . vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0\jre ... That is, Maven's using "C:\Program Files\Java\jdk1.7.0\jre" as your JAVA_HOME which instead should be your JDK folder -Original Message- From: debashish mukherjee [mailto:deba...@gmail.com] Sent: March-30-12 6:39 AM To: users@maven.apache.org Subject: Getting Error in Maven Hi, I am using maven 3.0.4 on my windows 7 machine, while running mvn jetty:run, I am facing these errors, please provide with some solution. Apache Maven 3.0.4 (r1232337; 2012-01-17 14:14:56+0530) Maven home: D:\softwares\apache-maven-3.0.4 Java version: 1.7.0, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from D:\softwares\apache-maven-3.0.4\conf\settings.xml [DEBUG] Reading user settings from C:\Users\deb\.m2\settings.xml [DEBUG] Using local repository at C:\Users\deb\.m2\repository [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for C:\Users\deb\.m2\repository [INFO] Scanning for projects... [DEBUG] Extension realms for project com.mycompany:myproject:war:1.0-SNAPSHOT: (none) [DEBUG] Looking up lifecyle mappings for packaging war from ClassRealm[plexus.core, parent: null] [DEBUG] Resolving plugin prefix jetty from [org.apache.maven.plugins, org.codehaus.mojo] [DEBUG] Resolved plugin prefix jetty to org.mortbay.jetty:maven-jetty-plugin from POM com.mycompany:myproject:war:1.0-SNAPSHOT [DEBUG] === REACTOR BUILD PLAN [DEBUG] Project: com.mycompany:myproject:war:1.0-SNAPSHOT [DEBUG] Tasks: [jetty:run] [DEBUG] Style: Regular [DEBUG] === [INFO] [INFO] [INFO] Building AppFuse Struts 2 Application 1.0-SNAPSHOT [INFO] [DEBUG] Resolving plugin prefix jetty from [org.apache.maven.plugins, org.codehaus.mojo] [DEBUG] Resolved plugin prefix jetty to org.mortbay.jetty:maven-jetty-plugin from POM com.mycompany:myproject:war:1.0-SNAPSHOT [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] [DEBUG] === PROJECT BUILD PLAN [DEBUG] Project: com.mycompany:myproject:1.0-SNAPSHOT [DEBUG] Dependencies (collect): [] [DEBUG] Dependencies (resolve): [runtime] [DEBUG] Repositories (dependencies): [appfuse-snapshots ( http://oss.sonatype.org/content/repositories/appfuse-snapshots, snapshots), central (http://repo.maven.apache.org/maven2, releases)] [DEBUG] Repositories (plugins) : [appfuse-snapshots ( http://oss.sonatype.org/content/repositories/appfuse-snapshots, snapshots), central (http://repo.maven.apache.org/maven2, releases)] [DEBUG] --- init fork of com.mycompany:myproject:1.0-SNAPSHOT for org.mortbay.jetty:maven-jetty-plugin:6.1.26:run (default-cli) --- [DEBUG] Dependencies (collect): [] [DEBUG] Dependencies (resolve): [compile, test] [DEBUG] --- [DEBUG] Goal: org.codehaus.mojo:native2ascii-maven-p
RE: Running surefire:test goal uses wrong resource file
Found the answer. Both persistence config files were using same persistence unit. From: Amir Gheibi Sent: March-29-12 3:57 PM To: Maven Users List (users@maven.apache.org) Subject: Running surefire:test goal uses wrong resource file Using Maven 3.0.4 with a flat project structure: |--Parent | | pom.xml | |--Module | | pom.xml | I use JPA for persistence and my unit test code uses different persistence configuration file than the main source. I use an in-memory derby database for unit tests and the actual source uses an Oracle database. However, running "mvn clean test" updates the oracle database. It seems surefire's test goal uses the wrong resource file. Persistence.xml used by unit tests which is located under "Module/src/test/resources/META-INF" http://java.sun.com/xml/ns/persistence"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd<http://java.sun.com/xml/ns/persistence%20http:/java.sun.com/xml/ns/persistence/persistence_2_0.xsd>" version="2.0"> org.eclipse.persistence.jpa.PersistenceProvider com.domain.someProject.SomeEntity Persistence.xml used by main source which is located under "Module/src/main/resources/META-INF" http://java.sun.com/xml/ns/persistence"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd<http://java.sun.com/xml/ns/persistence%20http:/java.sun.com/xml/ns/persistence/persistence_2_0.xsd>" version="2.0"> org.eclipse.persistence.jpa.PersistenceProvider com.domain.someProject.SomeEntity Would appreciate any input. - Amir
Running surefire:test goal uses wrong resource file
Using Maven 3.0.4 with a flat project structure: |--Parent | | pom.xml | |--Module | | pom.xml | I use JPA for persistence and my unit test code uses different persistence configuration file than the main source. I use an in-memory derby database for unit tests and the actual source uses an Oracle database. However, running "mvn clean test" updates the oracle database. It seems surefire's test goal uses the wrong resource file. Persistence.xml used by unit tests which is located under "Module/src/test/resources/META-INF" http://java.sun.com/xml/ns/persistence"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"; version="2.0"> org.eclipse.persistence.jpa.PersistenceProvider com.domain.someProject.SomeEntity Persistence.xml used by main source which is located under "Module/src/main/resources/META-INF" http://java.sun.com/xml/ns/persistence"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"; version="2.0"> org.eclipse.persistence.jpa.PersistenceProvider com.domain.someProject.SomeEntity Would appreciate any input. - Amir
RE: Dependency resolution problem
Wouldn't "-x" option give debug information from which the actual problem can be found and resolved? -Original Message- From: Niranjan Rao [mailto:nhr...@gmail.com] Sent: March-19-12 1:31 PM To: Maven Users List Subject: Dependency resolution problem After banging my head for half an hour, I finally figured what was wrong. I was trying to use org.xerial:sqlite-jdbc version 3.7.2 on maven 3. This jar is part of central repository and I was able to to see when I went to local nexus mirror. However maven was not "seeing" it. Any time I tried compilation, I was getting error about unable to resolve dependencies. It turned out that this artifact is dependent upon some other artifacts which come from xerial.org repository. If maven had told me about the actual missing dependencies, it would have been much easier. Was there any switch that I could have used to the name of actual missing dependency? During my tries maven only complained about dependency that was in my pom and not the transitive dependencies. I managed to fix it by adding xerial mirror to my nexus, but this can be baffling problem as error message was misleading. Regards, Niranjan - 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: Which is the BEST Approach to define Global POM.XML
Got it. Thanks. -Original Message- From: Eric Kolotyluk [mailto:eric.koloty...@gmail.com] Sent: March-14-12 2:57 PM To: Amir Gheibi Cc: Maven Users List Subject: Re: Which is the BEST Approach to define Global POM.XML Amir, my Project POM has more modules inside (platform.Java & platform.NET), and they in turn are packaging type "POM" because there are more modules in those, that typically are types like "JAR" so my structure looks like Corporate POM +-- Project POM 1 +--+-- Platform POM 1.1 +--+--+-- Artifact POM 1.1.1 +--+--+-- Artifact POM 1.1.2 +--+-- Platform POM 1.2 +--+--+-- Artifact POM 1.2.1 +--+--+-- Artifact POM 1.2.2 The Project and Platform POM are just there for structural reasons. For example if I want I can do a clean and deploy in the Project POM directory and everything gets built, tested and deployed, or I work on more specific pieces. Cheers, Eric On 2012-03-14 2:34 PM, Amir Gheibi wrote: > Hi Eric, > > I was wondering why your project POM's packaging type is "POM". If I > understand correctly, with "POM" packaging type you'd only get 3 default > goals bound to their phases (I read it here: > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Built-in_Lifecycle_Bindings). > > Thanks, > Amir > > -Original Message- > From: Eric Kolotyluk [mailto:eric.koloty...@gmail.com] > Sent: March-14-12 2:22 PM > To: users@maven.apache.org > Subject: Re: Which is the BEST Approach to define Global POM.XML > > What I do is have a top-level POM like (see below), and then I have my > top level project POMs reference that (see further below). This may > not be the best example, as I am still in the process of building the > infrastructure, but > > 1. I put the Parent POM in its own place in source control and I > manually deploy it with Maven when I make changes. > 2. You need to do this before creating any Project POMs that reference > it because they should reference it via Maven and not the file > system - if you work in a large company you will soon discover why. > 3. There is of course a bootstrapping issue because now the project > POMs need to know how to find your Repository Manager, which is why > I include that information in the top level (Corporate) POM so > people can use it as a reference. > 4. As you may gather I am using Sonatype's Nexus as a Repository Manager. > 5. We are still developing our corporate repository infrastructure so > the content of the Corporate POM will evolve over time as our > corporate governance and policies are better codified. > > Does that help? > > xmlns="http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd";> > > 4.0.0 > com > my-company > 0.0.1-SNAPSHOT > pom > My Company Corporate POM > Corporate Project Object Module for standard conventions > and rules. 10069959 > Eric Kolotyluk eric.koloty...@gmail.com > My Company Ltd. Vancouver > PDTSoftware Architect > Software Developer > My Company > > http://sonatype:8081/nexus/content/groups/public dUrl> > > false > nexus > My Company Release Repository > http://sonatype:8081/nexus/content/repositories/releases > default > > > nexus > My Company Snapshot Repository > http://sonatype:8081/nexus/content/repositories/snapshots > default > > > > > > > > always > > info.collide.mvn > Collide > http://sonatype:8081/nexus/content/repositories/info.collide.mvn/ > > > > thirdparty > 3rd party > http://sonatype:8081/nexus/content/repositories/thirdparty/ > > > > > > > > > > > > UTF-8 > > > > - - - - - - - > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd";> > 4.0.0 > > com > my-company > 0.0.1-SNAPSHOT > > com.my-company > intersystem > 0.0.2-SNAPSHOT > pom > My Company Intersystem > Service layer for collaborative, distributed applications > and services My Company > Intersystem > https://collaborate.my-company.com/sites/SoftwareStandardsAndGuid > elines/Intersystem/default.aspx > repo > > > > > 10069959 > Eric Kolotyluk > eric.koloty...@gmail.com > My Company Vancouver > PDT Software Architect Software > Developer Intersystem Architect >My
RE: Which is the BEST Approach to define Global POM.XML
Hi Eric, I was wondering why your project POM's packaging type is "POM". If I understand correctly, with "POM" packaging type you'd only get 3 default goals bound to their phases (I read it here: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Built-in_Lifecycle_Bindings). Thanks, Amir -Original Message- From: Eric Kolotyluk [mailto:eric.koloty...@gmail.com] Sent: March-14-12 2:22 PM To: users@maven.apache.org Subject: Re: Which is the BEST Approach to define Global POM.XML What I do is have a top-level POM like (see below), and then I have my top level project POMs reference that (see further below). This may not be the best example, as I am still in the process of building the infrastructure, but 1. I put the Parent POM in its own place in source control and I manually deploy it with Maven when I make changes. 2. You need to do this before creating any Project POMs that reference it because they should reference it via Maven and not the file system - if you work in a large company you will soon discover why. 3. There is of course a bootstrapping issue because now the project POMs need to know how to find your Repository Manager, which is why I include that information in the top level (Corporate) POM so people can use it as a reference. 4. As you may gather I am using Sonatype's Nexus as a Repository Manager. 5. We are still developing our corporate repository infrastructure so the content of the Corporate POM will evolve over time as our corporate governance and policies are better codified. Does that help? http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 com my-company 0.0.1-SNAPSHOT pom My Company Corporate POM Corporate Project Object Module for standard conventions and rules. 10069959 Eric Kolotyluk eric.koloty...@gmail.com My Company Ltd. Vancouver PDT Software Architect Software Developer My Company http://sonatype:8081/nexus/content/groups/public false nexus My Company Release Repository http://sonatype:8081/nexus/content/repositories/releases default nexus My Company Snapshot Repository http://sonatype:8081/nexus/content/repositories/snapshots default always info.collide.mvn Collide http://sonatype:8081/nexus/content/repositories/info.collide.mvn/ thirdparty 3rd party http://sonatype:8081/nexus/content/repositories/thirdparty/ UTF-8 - - - - - - - http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 com my-company 0.0.1-SNAPSHOT com.my-company intersystem 0.0.2-SNAPSHOT pom My Company Intersystem Service layer for collaborative, distributed applications and services My Company Intersystem https://collaborate.my-company.com/sites/SoftwareStandardsAndGuidelines/Intersystem/default.aspx repo 10069959 Eric Kolotyluk eric.koloty...@gmail.com My Company Vancouver PDT Software Architect Software Developer Intersystem Architect My Company http://sonatype:8081/nexus/content/groups/public false nexus My Company Release Repository http://sonatype:8081/nexus/content/repositories/releases default nexus My Company Snapshot Repository http://sonatype:8081/nexus/content/repositories/snapshots default always info.collide.mvn Collide http://sonatype:8081/nexus/content/repositories/info.collide.mvn/ thirdparty 3rd party http://sonatype:8081/nexus/content/repositories/thirdparty/ 0.8.6.0 UTF-8 platform.Java platform.NET On 2012-03-14 1:29 PM, Daivish Shah wrote: > Hi Maven Team, > > I am trying to find out what is the best way to define company > specific GLOBAL POM.XML. Which each team can inherit it in EACH Projects. > > Can some one provide me guideline on that ? Is that going to be > profile or just simple POM.XML ? And how to inherit that. Please > provide me guideline to implement it. As this is very critical before > we implement all projects with MAVEN. > > Thanks, > Daivish. > - 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
