How is version:display-plugin-updates determine the super-pom version (wrongly?)
Hello, when I create a minimal POM* and expand it with maven 3.2.1 then I see an entry in the resulting effective pom: plugin artifactIdmaven-surefire-plugin/artifactId version2.12.4/version executions execution iddefault-test/id phasetest/phase goals goaltest/goal /goals /execution /executions /plugin (and no plugin management enty). When I run the version:display-plugin-updates on the same pom, it will print: [DEBUG] [org.apache.maven.plugins:maven-surefire-plugin].version=null [DEBUG] [org.apache.maven.plugins:maven-surefire-plugin].artifactVersion=2.4.2 [DEBUG] [org.apache.maven.plugins:maven-surefire-plugin].effectiveVersion=2.17 [DEBUG] [org.apache.maven.plugins:maven-surefire-plugin].specified=false [DEBUG] [org.apache.maven.plugins:maven-surefire-plugin].superPom.version=2.12.4 [WARNING] The following plugins do not have their version specified: ... [WARNING] maven-surefire-plugin .. (from super-pom) 2.17 I have no idea why it tells me that the super-pom defines 2.17, is this the expected behavior? In the debug output the versions look better. Greetings Bernd PS: I tested it with the following pom, settings file, empty local repo and commands: pom.xml: project 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; modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdpom-test/artifactId version0.1-SNAPSHOT/version /project empty.xml: settings xmlns=http://maven.apache.org/SETTINGS/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd; localRepositoryC:\Users\USER\.m2\default-repository/localRepository /settings $ mvn -s empty.xml versions:display-plugin-updates $ mvn -s empty.xml help:effective-pom pom-effective.xml - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
executing command maven site - getting error for _en.xml on my super-pom project
Hi Team, I am getting following Exception, I don't understand why it's all of sudden looking for *super-pom-1.0.0.0-site_en.xml*http://mavenrepo.mitchell.com/repo/com/mitchell/maven/apd/super-pom/1.0.0.0/super-pom-1.0.0.0-site_en.xml from Artifactory. When i execute MAVEN SITE command. super-pom project is my super project for all of the project. Is anybody has idea why it's looking for specific internationalization file from the repository ? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project sample-assignment-root-pom: SiteToolException: The site descriptor cannot be resolved from the repository: ArtifactResolutionException: Unable to locate site descriptor: Could not transfer artifact com.mitchell.maven.sample:super-pom:xml:site_en:1.0.0.0 from/to company-central (http://mavenrepo.company.com/repohttp://mavenrepo.mitchell.com/repo): Access denied to: http://mavenrepo.company.com/repo/com/mitchell/maven/apd/super-pom/1.0.0.0/* super-pom-1.0.0.0-site_en.xml*http://mavenrepo.mitchell.com/repo/com/mitchell/maven/apd/super-pom/1.0.0.0/super-pom-1.0.0.0-site_en.xml [ERROR] com.mitchell.maven.sample:super-pom:xml:1.0.0.0 Thanks, Daivish.
Re: Quick question on Super POM plugin management usage
Don't call this a super pom! It's a parent (pom). There is only ONE Super-POM and it's part of Maven Core. Calling some other artifact a super-pom will only confuse people. /Anders On Thu, Mar 29, 2012 at 02:47, Daivish Shah daivish.s...@gmail.com wrote: Hi, I am trying to use the super POM in my all of the project and seems like PluginManagement doesn't work like this way. Super-Pom Project pom.xml build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.8.1/version /plugin /plugins /pluginManagement /build Using Super POM in my other project as followed. pom.xml parent groupIdcom.super/groupId artifactIdsuper-pom/artifactId version0.0.1-SNAPSHOT/version /parent build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin /plugins /build When i try to use like this way compiler throws me WARNING/ERROR message and looks like i have to apply VERSION ID again when i use any of the plugin which is listed in my super POM Project. Which doesn't make sense to declare PLUGIN things in my SUPER POM Project. Any idea what's going on here ? Is that the way MAVEN designed or i am doing something wrong here ? Thanks, daivish. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Quick question on Super POM plugin management usage
Hi, I am trying to use the super POM in my all of the project and seems like PluginManagement doesn't work like this way. Super-Pom Project pom.xml build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.8.1/version /plugin /plugins /pluginManagement /build Using Super POM in my other project as followed. pom.xml parent groupIdcom.super/groupId artifactIdsuper-pom/artifactId version0.0.1-SNAPSHOT/version /parent build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin /plugins /build When i try to use like this way compiler throws me WARNING/ERROR message and looks like i have to apply VERSION ID again when i use any of the plugin which is listed in my super POM Project. Which doesn't make sense to declare PLUGIN things in my SUPER POM Project. Any idea what's going on here ? Is that the way MAVEN designed or i am doing something wrong here ? Thanks, daivish.
Re: Quick question on Super POM plugin management usage
On Thu, Mar 29, 2012 at 11:17 AM, Daivish Shah daivish.s...@gmail.com wrote: Hi, I am trying to use the super POM in my all of the project and seems like PluginManagement doesn't work like this way. Super-Pom Project pom.xml build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.8.1/version /plugin /plugins /pluginManagement /build Using Super POM in my other project as followed. pom.xml parent groupIdcom.super/groupId artifactIdsuper-pom/artifactId version0.0.1-SNAPSHOT/version /parent build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin /plugins /build When i try to use like this way compiler throws me WARNING/ERROR message and looks like i have to apply VERSION ID again when i use any of the plugin which is listed in my super POM Project. Which doesn't make sense to declare PLUGIN things in my SUPER POM Project. Any idea what's going on here ? Is that the way MAVEN designed or i am doing something wrong here ? Thanks, daivish. javadoc is a reporting plugin. You will probably need to *duplicate* the information in the reporting section. See http://jira.codehaus.org/browse/MSITE-443 for more details. I think you can leave out the version from the pluginManagement section. It may depend on whether you ever want to run javadoc directly, which is normally not what you want, you want to run all the reporting stuff via mvn site - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Super pom / enforcer issues?
Comments inline. Regards, /James 2009/12/9 Nord, James jn...@nds.com: I'm having a really strange error in Maven 2.2.1 and the enforcer plugin. Basically it appears as though the super pom is missing version definitions for the following even though they should be present according to the web documentation (and performing a help:effective-pom shows them listed in the pluginManagement section): * maven-clean-plugin * maven-deploy-plugin * maven-install-plugin * maven-site-plugin Anyone any ideas what's happening? If I read your mail correctly then you're thinking the Enforcer plugin should not complain about missing versions if those versions are provided by the super pom. Correct. But think about it, if you upgrade to a newer Maven version then you could get a different super pom and as such your build is not reproducible. But the build is reproducible - you made an invalid assumption. In our builds we record the Maven version used to do the build so if we want to reproduce it we use exactly the same maven version on exactly the same platform with exactly the same JDK. I don't expect any maven version to give exactly the same results as a different version. You should explicitly list the versions of everything you use. Don't depend on the super pom to do it for you. The Enforcer plugin is just doing what you asked it to do. From the documentation: The Super POM is Maven's default POM. All POMs extend the Super POM unless explicitly set This rule enforces that all plugins have a version defined, either in the plugin or pluginManagement section of the pom or a parent pom. The combination of the two says to me that my POM implicitly has the Super POM as its parent, and hence *does* have the versions defined. My take on the Enforcer plugin is to make builds reproducible given the same environment at a latter date. Changing Maven version (or JDK!) changes the environment and is out of scope IMHO. This is especially the case if you explicitly limit the version of Maven and JDK (and OS!) used in the enforcer rules, and setting these does make sure your build is reproducible. ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. An NDS Group Limited company. www.nds.com
Re: Super pom / enforcer issues?
My take on the Enforcer plugin is to make builds reproducible given the same environment at a latter date. Changing Maven version (or JDK!) changes the environment and is out of scope IMHO. This is especially the case if you explicitly limit the version of Maven and JDK (and OS!) used in the enforcer rules, and setting these does make sure your build is reproducible. Sounds like you want Enforcer to work like: if version of plugin not in this pom, or a parent etc and maven version locked down and jdk version is locked down and maven super pom specifies version of this plugin then do not fail You can certainly hack the code yourself or file a JIRA to make it work like you expect with a configurable flag to turn that feature on/off. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Super pom / enforcer issues?
Hi all,
I'm having a really strange error in Maven 2.2.1 and the enforcer plugin.
Basically it appears as though the super pom is missing version definitions for
the following even though they should be present according to the web
documentation (and performing a help:effective-pom shows them listed in the
pluginManagement section):
* maven-clean-plugin
* maven-deploy-plugin
* maven-install-plugin
* maven-site-plugin
Anyone any ideas what's happening?
mvn validate
[INFO] Scanning for projects...
[INFO]
[INFO] Building example
[INFO]task-segment: [validate]
[INFO]
[INFO] [enforcer:enforce {execution: enforce-rules}]
[INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for
updates from central
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequirePluginVersions
failed with message:
Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are not
allowed )
org.apache.maven.plugins:maven-clean-plugin.The version currently in use is
2.3
org.apache.maven.plugins:maven-deploy-plugin. The version currently in use is
2.4
org.apache.maven.plugins:maven-install-plugin. The version currently in use is
2.3
org.apache.maven.plugins:maven-site-plugin. The version currently in use is
2.0.1
Found plugins without fixed release version defined. Build is not reproducible.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Some Enforcer rules have failed. Look above for specific messages
explaining why the rule failed.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Wed Dec 09 18:09:15 GMT 2009
[INFO] Final Memory: 6M/254M
[INFO]
mvn --version
Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
Java version: 1.6.0_16
Java home: C:\Java\jdk1.6.0_16\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: windows xp version: 5.1 arch: x86 Family: windows
-- begin pom.xml -
?xml version=1.0 encoding=UTF-8?
project 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/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdexample/groupId
artifactIdmyPom/artifactId
version0.0.1-SNAPSHOT/version
packagingpom/packaging
nameexample/name
build
plugins
plugin
artifactIdmaven-enforcer-plugin/artifactId
version1.0-beta-1/version
executions
execution
idenforce-rules/id
goals
goalenforce/goal
/goals
phasevalidate/phase
configuration
rules
requireMavenVersion
version2.2.1/version
/requireMavenVersion
requirePluginVersions
messageFound plugins without fixed release version defined. Build is not
reproducible./message
/requirePluginVersions
/rules
/configuration
/execution
/executions
/plugin
/plugins
/build
/project
-- end pom.xml -
**
This message is confidential and intended only for the addressee. If you have
received this message in error, please immediately notify the
postmas...@nds.com and delete it from your system as well as any copies. The
content of e-mails as well as traffic data may be monitored by NDS for
employment and security
Re: Super pom / enforcer issues?
2009/12/9 Nord, James jn...@nds.com: I'm having a really strange error in Maven 2.2.1 and the enforcer plugin. Basically it appears as though the super pom is missing version definitions for the following even though they should be present according to the web documentation (and performing a help:effective-pom shows them listed in the pluginManagement section): * maven-clean-plugin * maven-deploy-plugin * maven-install-plugin * maven-site-plugin Anyone any ideas what's happening? If I read your mail correctly then you're thinking the Enforcer plugin should not complain about missing versions if those versions are provided by the super pom. But think about it, if you upgrade to a newer Maven version then you could get a different super pom and as such your build is not reproducible. You should explicitly list the versions of everything you use. Don't depend on the super pom to do it for you. The Enforcer plugin is just doing what you asked it to do. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin version in SUPER POM simply ignored, with trivial pom.xml
Right, it looks like help:describe -Dplugin=resources will download and show the latest version of a plugin, regarless of what version the project/pom actually specifies. In which case this FAQ entry is VERY wrong, and should be update ASAP to save people trouble: http://maven.apache.org/general.html#plugin-version Besides the FAQ being wrong this is problematic because the help displayed may or may not be relevant for the plugin version used in project. Here is the closes bug I found: http://jira.codehaus.org/browse/MPH-53 -- View this message in context: http://old.nabble.com/Plugin-version-in-SUPER-POM-simply-ignored%2C-with-trivial-pom.xml-tp26661071p26674107.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: Plugin version in SUPER POM simply ignored, with trivial pom.xml
Go by help effective pom not describe, it looks hokey to me. Is 2.4.1 the latest? Maybe that's what is being reported. --Brian (mobile) On Dec 5, 2009, at 10:07 PM, kdwinkler keithdwink...@gmail.com wrote: Help even reports version 2.4.1 for the below pom: project ... build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.3/version /plugin /plugins /pluginManagement /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.3/version /plugin /plugins /reporting /project -- View this message in context: http://old.nabble.com/Plugin-version-in-SUPER-POM-simply-ignored%2C-with-trivial-pom.xml-tp26661071p26662106.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
Plugin version in SUPER POM simply ignored, with trivial pom.xml
maven-resources-plugin resolves to version 2.4.1 despite 2.3 being specified in the super pom. My entire pom is this: project ... modelVersion4.0.0/modelVersion groupIdcom.redshiftsoft/groupId artifactIdredshift-pom/artifactId packagingpom/packaging version1.0.0-SNAPSHOT/version /project mvn help:describe -Dplugin=resources Reports version 2.4.1 HOWEVER, mvn help:effective-pom shows version 2.3 for this plugin. And that is indeed the version in the super pom. Is this a known bug? Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) Java version: 1.6.0_16 Java home: C:\Program Files\Java\jdk1.6.0_16\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7 version: 6.1 arch: x86 Family: windows -- View this message in context: http://old.nabble.com/Plugin-version-in-SUPER-POM-simply-ignored%2C-with-trivial-pom.xml-tp26661071p26661071.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: Plugin version in SUPER POM simply ignored, with trivial pom.xml
Keith, Know that plugins and reportings are SEPARATE configurations. A version specified in one section does not affect the other. If this is your situation, declare the version under both tags. Paul On Sat, Dec 5, 2009 at 6:49 PM, kdwinkler keithdwink...@gmail.com wrote: maven-resources-plugin resolves to version 2.4.1 despite 2.3 being specified in the super pom. My entire pom is this: project ... modelVersion4.0.0/modelVersion groupIdcom.redshiftsoft/groupId artifactIdredshift-pom/artifactId packagingpom/packaging version1.0.0-SNAPSHOT/version /project mvn help:describe -Dplugin=resources Reports version 2.4.1 HOWEVER, mvn help:effective-pom shows version 2.3 for this plugin. And that is indeed the version in the super pom. Is this a known bug? Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) Java version: 1.6.0_16 Java home: C:\Program Files\Java\jdk1.6.0_16\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7 version: 6.1 arch: x86 Family: windows -- View this message in context: http://old.nabble.com/Plugin-version-in-SUPER-POM-simply-ignored%2C-with-trivial-pom.xml-tp26661071p26661071.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: Plugin version in SUPER POM simply ignored, with trivial pom.xml
plugins and reportings are SEPARATE configurations. Which version is reported by mvn help:describe -Dplugin=? Anyway, if I change my simple pom to this (note this is a brand new project, this pom.xml is the only thing in the directory, there is no parent pom--other than super--I have not modified the maven install or any settings file): project... modelVersion4.0.0/modelVersion groupIdcom.redshiftsoft/groupId artifactIdredshift-pom/artifactId packagingpom/packaging version1.0.0/version reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.3/version /plugin /plugins /reporting /project mvn help:describe -Dplugin=resources I still get: Name: Maven Resources Plugin Description: The Resources Plugin handles the copying of project resources to the output directory. There are two different kinds of resources: main resources and test resources. The difference is that the main resources are the resources associated to the main source code while the test resources are associated to the test source code. Thus, this allows the separation of resources for the main source code and its unit tests. Group Id: org.apache.maven.plugins Artifact Id: maven-resources-plugin Version: 2.4.1 Goal Prefix: resources Paul Benedict-2 wrote: Keith, Know that plugins and reportings are SEPARATE configurations. A version specified in one section does not affect the other. If this is your situation, declare the version under both tags. Paul -- View this message in context: http://old.nabble.com/Plugin-version-in-SUPER-POM-simply-ignored%2C-with-trivial-pom.xml-tp26661071p26661657.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: Plugin version in SUPER POM simply ignored, with trivial pom.xml
Keith, Which version is reported by mvn help:describe -Dplugin=? My guess is that it is from plugins, not reports Paul - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin version in SUPER POM simply ignored, with trivial pom.xml
Help even reports version 2.4.1 for the below pom: project ... build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.3/version /plugin /plugins /pluginManagement /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.3/version /plugin /plugins /reporting /project -- View this message in context: http://old.nabble.com/Plugin-version-in-SUPER-POM-simply-ignored%2C-with-trivial-pom.xml-tp26661071p26662106.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: Maven Enforcer Plugin, default versions (from Super POM) not taken into account
This is absolutely intentional. The best practice is for you to
control your own versions. Yes the super pom introduces a bit of
stability, but at the cost of complacency. If you rely on the defaults
in the super pom it means in a year when you build with a different
version of maven, you have a whole different set of plugins along with
it. That's probably not what you want. It also means when you upgrade
maven core, you drag along potentially a bunch of new plugins and if
something breaks, how can you tell why?
On Thu, Nov 5, 2009 at 1:28 AM, Rebholz Paul paul.rebh...@six-group.com wrote:
Hi
We are setting up an enterprise-wide parent pom in which we lock down
plugin versions. For the Maven 'inherent' set of core plugins, we want
to fallback on the super pom declared versions, but seem to run into a
problem with the enforcer not taking into account those defaults. We are
using the newest final maven version 2.2.1.
The error message we end up with is the following:
...
[INFO] [enforcer:enforce {execution: enforce}]
[WARNING] Rule 1:
org.apache.maven.plugins.enforcer.RequirePluginVersions failed with
message:
Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are not
allowed )
org.apache.maven.plugins:maven-resources-plugin. The version
currently in use is 2.3
org.apache.maven.plugins:maven-surefire-plugin. The version
currently in use is 2.4.3
org.apache.maven.plugins:maven-jar-plugin. The version currently in
use is 2.2
...
Any tips on how to save us from having to duplicate version information
for the core plugins in the enterprise-wide parent pom ?
Regards, Paul
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. If you receive this message in
error, please notify the sender urgently and then immediately delete the
message and any copies of it from your system. Please also immediately
destroy any hardcopies of the message.
The sender's company reserves the right to monitor all e-mail communications
through their networks.
-
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
Super pom properties in child pom
Say I've got a super pom with a defined SCM section like so:
scm
connectionscm:git:git://server/repos/${artifactId}.git/connection
/scm
Well in the child pom, it's taking the super pom's name and appending /
child pom's name.
Like so:
scm
connectionscm:git:git://server/repos/Super/Child.git/connection
/scm
That's not what I wanted it to do, I need it to just have Child.git without
the super/ stuff
How do I ensure that happens?
Thanks,
David
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Super pom properties in child pom
On Fri, 05 Jun 2009 14:12:50 -0500, dkowis dko...@shlrm.org wrote:
Say I've got a super pom with a defined SCM section like so:
scm
connectionscm:git:git://server/repos/${artifactId}.git/connection
/scm
Well in the child pom, it's taking the super pom's name and appending /
child pom's name.
Like so:
scm
connectionscm:git:git://server/repos/Super/Child.git/connection
/scm
That's not what I wanted it to do, I need it to just have Child.git
without
the super/ stuff
How do I ensure that happens?
Actually it's still stranger than that:
I have a configured url in the scm section
urlhttp://server/gitweb/gitweb.cgi/repos/${artifactId}/url
This should show up in the generated site (when running mvn site) as:
http://server/gitweb/gitweb.cgi/repos/Child
But it's showing up as:
http://server/gitweb/gitweb.cgi/repos/Child/Super/Child
What is going on? I didn't specify anything else after the URL, why is
appending things for me?
Thanks,
David
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Using super pom
I have the following file structure: /Deep6MasterPOM pom.xml /Foundation pom.xml I have a local maven repository in ~woo/.m2/repository, of course. I'm trying to put a few common things into the Deep6MasterPOM like the JDepends plugin for later components of the entire Deep6 build to use. Right now, I have the Deep6MasterPOM/pom.xml as -- project 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/maven-v4_0_0.xsd modelVersion4.0.0/modelVersion groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId packagingpom/packaging modules module../Foundation/module /modules version0.0.1-SNAPSHOT/version nameDeep6MasterPOM/name urlhttp://maven.apache.org/url descriptionThis project provides a Super POM with the JDepend plugin specified/description inceptionYearFeb-20-2009/inceptionYear issueManagement systemMantis/system urlhttp://localhost/~woo/mantis/url /issueManagement developers developer idwoo/id nameJohn Wooten/name emailjwoo...@shoulderscorp.com/email organizationShouldersCorp/organization organizationUrlhttp://www.shoulderscorp.com/organizationUrl timezoneEST/timezone roles roleArchitect/Lead-Developer/role /roles /developer /developers scm connectionscm:svn:svn+ssh://woo37...@www.areteq.com/Deep6/ connection tagDeep6Master/tag urlhttp://localhost/url /scm organization nameShouldersCorp./name urlhttp://www.shoulderscorp.com/url /organization !-- repositories /repositories -- dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies reporting plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdjdepend-maven-plugin/artifactId /plugin /plugins /reporting /project -- and the /Foundation/pom.xml as project 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/maven-v4_0_0.xsd parent groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId version1/version relativePath../Deep6MasterPOM/pom.xml/relativePath /parent modelVersion4.0.0/modelVersion artifactIdFoundation/artifactId nameFoundation/name version0.0.1-SNAPSHOT/version descriptionThe base classes for all AreteQ projects/description repositories !-- repository idlocal/id nameLocal Repository Switchboard/name layoutdefault/layout urlfile://Users/woo//url snapshots enabledfalse/enabled /snapshots /repository -- /repositories /project --- My intent is to have the mvn site:site for Foundation use the super pom (i.e. parent ) and incorporate that into the child pom, so that the JDepends works there as well as other things I'll have in common. 1) Should I be creating a pom in Deep6MasterPOM/pom.xml? Apparently when Foundation tries to run, it looks in the maven remote repository for my pom file for Deep6MasterPOM? --- url = http://repo1.maven.org/maven2 Downloading: http://repo1.maven.org/maven2/com/areteq/Deep6MasterPOM/1/Deep6MasterPOM-1.pom [ERROR] Failed to resolve parent-POM from repository. Parent POM Information: Group-Id: com.areteq Artifact-Id: Deep6MasterPOM Version: 1 Local Repository: /Users/woo/.m2/repository Remote Repositories: central - http://repo1.maven.org/maven2 Reason: Unable to download the artifact from any repository com.areteq:Deep6MasterPOM:pom:1 from the specified remote repositories: central (http://repo1.maven.org/maven2) Project Id: [inherited]:Foundation:jar:0.0.1-SNAPSHOT From file: /Users/woo/Development/workspaces/Qworkspace/Foundation/ pom.xml [INFO] [INFO] For more information, run with the -e flag [INFO] [INFO] + Ignoring build failures How do I make it keep my stuff local, and use the master only for the jars, etc. that it needs? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using super pom
On Sat, Feb 21, 2009 at 6:48 AM, John Wooten jwoo...@shoulderscorp.com wrote: I have the following file structure: /Deep6MasterPOM pom.xml /Foundation pom.xml I have a local maven repository in ~woo/.m2/repository, of course. I'm trying to put a few common things into the Deep6MasterPOM like the JDepends plugin for later components of the entire Deep6 build to use. Right now, I have the Deep6MasterPOM/pom.xml as -- project 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/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId packagingpom/packaging modules module../Foundation/module /modules I would not expect to see modules in a master pom. Typically you have an organization-wide master pom that sets defaults at a high level. It has a separate release cycle, and no modules. version0.0.1-SNAPSHOT/version So the version of Deep6MasterPOM is 0.0.1-SNAPSHOT... and the /Foundation/pom.xml as ... parent groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId version1/version relativePath../Deep6MasterPOM/pom.xml/relativePath /parent ...but you're trying to use version 1, which probably hasn't been released yet. How do I make it keep my stuff local, and use the master only for the jars, etc. that it needs? Use 'mvn install' to put it in your local repository, and use the correct version number. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using super pom
Thanks, I think the problem is not understand the life cycle of a maven build and how these things relate. So, as I understand it, you create a master pom, no modules, but default information. Then mvn install it to put it into a repository. It should be a pop package, though. Then in the child pom refer to the same release number as 0.0.1- SNAPSHOT in this case? On Feb 21, 2009, at 10:13 AM, Wendy Smoak wrote: On Sat, Feb 21, 2009 at 6:48 AM, John Wooten jwoo...@shoulderscorp.com wrote: I have the following file structure: /Deep6MasterPOM pom.xml /Foundation pom.xml I have a local maven repository in ~woo/.m2/repository, of course. I'm trying to put a few common things into the Deep6MasterPOM like the JDepends plugin for later components of the entire Deep6 build to use. Right now, I have the Deep6MasterPOM/pom.xml as -- project 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/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId packagingpom/packaging modules module../Foundation/module /modules I would not expect to see modules in a master pom. Typically you have an organization-wide master pom that sets defaults at a high level. It has a separate release cycle, and no modules. version0.0.1-SNAPSHOT/version So the version of Deep6MasterPOM is 0.0.1-SNAPSHOT... and the /Foundation/pom.xml as ... parent groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId version1/version relativePath../Deep6MasterPOM/pom.xml/relativePath /parent ...but you're trying to use version 1, which probably hasn't been released yet. How do I make it keep my stuff local, and use the master only for the jars, etc. that it needs? Use 'mvn install' to put it in your local repository, and use the correct version number. -- 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
Re: Using super pom
John, go to sonatype.com and look at their book; http://www.sonatype.com/documentation/books I was able to figure it out from that and they're good at exhorting you to use best practices. Another good online book is http://www.exist.com/better-build-maven John Wooten wrote: Thanks, I think the problem is not understand the life cycle of a maven build and how these things relate. So, as I understand it, you create a master pom, no modules, but default information. Then mvn install it to put it into a repository. It should be a pop package, though. Then in the child pom refer to the same release number as 0.0.1-SNAPSHOT in this case? On Feb 21, 2009, at 10:13 AM, Wendy Smoak wrote: On Sat, Feb 21, 2009 at 6:48 AM, John Wooten jwoo...@shoulderscorp.com wrote: I have the following file structure: /Deep6MasterPOM pom.xml /Foundation pom.xml I have a local maven repository in ~woo/.m2/repository, of course. I'm trying to put a few common things into the Deep6MasterPOM like the JDepends plugin for later components of the entire Deep6 build to use. Right now, I have the Deep6MasterPOM/pom.xml as -- project 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/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId packagingpom/packaging modules module../Foundation/module /modules I would not expect to see modules in a master pom. Typically you have an organization-wide master pom that sets defaults at a high level. It has a separate release cycle, and no modules. version0.0.1-SNAPSHOT/version So the version of Deep6MasterPOM is 0.0.1-SNAPSHOT... and the /Foundation/pom.xml as ... parent groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId version1/version relativePath../Deep6MasterPOM/pom.xml/relativePath /parent ...but you're trying to use version 1, which probably hasn't been released yet. How do I make it keep my stuff local, and use the master only for the jars, etc. that it needs? Use 'mvn install' to put it in your local repository, and use the correct version number. -- 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using super pom
Thanks, I'm getting those printed out so I can read a bit more leisurely. I finally copied the pom.xml to the directory above the various eclipse projects and it seems to find them now. I keep getting errors now about some of the tools ( plugins ) not finding VM software, and not being able to unzip some file that I didn't even know I had. On Feb 21, 2009, at 1:12 PM, Rusty Wright wrote: John, go to sonatype.com and look at their book; http://www.sonatype.com/documentation/books I was able to figure it out from that and they're good at exhorting you to use best practices. Another good online book is http://www.exist.com/better-build-maven John Wooten wrote: Thanks, I think the problem is not understand the life cycle of a maven build and how these things relate. So, as I understand it, you create a master pom, no modules, but default information. Then mvn install it to put it into a repository. It should be a pop package, though. Then in the child pom refer to the same release number as 0.0.1- SNAPSHOT in this case? On Feb 21, 2009, at 10:13 AM, Wendy Smoak wrote: On Sat, Feb 21, 2009 at 6:48 AM, John Wooten jwoo...@shoulderscorp.com wrote: I have the following file structure: /Deep6MasterPOM pom.xml /Foundation pom.xml I have a local maven repository in ~woo/.m2/repository, of course. I'm trying to put a few common things into the Deep6MasterPOM like the JDepends plugin for later components of the entire Deep6 build to use. Right now, I have the Deep6MasterPOM/pom.xml as -- project 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/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId packagingpom/packaging modules module../Foundation/module /modules I would not expect to see modules in a master pom. Typically you have an organization-wide master pom that sets defaults at a high level. It has a separate release cycle, and no modules. version0.0.1-SNAPSHOT/version So the version of Deep6MasterPOM is 0.0.1-SNAPSHOT... and the /Foundation/pom.xml as ... parent groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId version1/version relativePath../Deep6MasterPOM/pom.xml/relativePath /parent ...but you're trying to use version 1, which probably hasn't been released yet. How do I make it keep my stuff local, and use the master only for the jars, etc. that it needs? Use 'mvn install' to put it in your local repository, and use the correct version number. -- 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 - 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: Using super pom
Oh, BTW, when I do a maven clean, it removes the target/classes folder. That is where maven is supposed to compile the classes. Do I have to separately compile within Eclipse, or can maven do the compile also? On Feb 21, 2009, at 1:12 PM, Rusty Wright wrote: John, go to sonatype.com and look at their book; http://www.sonatype.com/documentation/books I was able to figure it out from that and they're good at exhorting you to use best practices. Another good online book is http://www.exist.com/better-build-maven John Wooten wrote: Thanks, I think the problem is not understand the life cycle of a maven build and how these things relate. So, as I understand it, you create a master pom, no modules, but default information. Then mvn install it to put it into a repository. It should be a pop package, though. Then in the child pom refer to the same release number as 0.0.1- SNAPSHOT in this case? On Feb 21, 2009, at 10:13 AM, Wendy Smoak wrote: On Sat, Feb 21, 2009 at 6:48 AM, John Wooten jwoo...@shoulderscorp.com wrote: I have the following file structure: /Deep6MasterPOM pom.xml /Foundation pom.xml I have a local maven repository in ~woo/.m2/repository, of course. I'm trying to put a few common things into the Deep6MasterPOM like the JDepends plugin for later components of the entire Deep6 build to use. Right now, I have the Deep6MasterPOM/pom.xml as -- project 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/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId packagingpom/packaging modules module../Foundation/module /modules I would not expect to see modules in a master pom. Typically you have an organization-wide master pom that sets defaults at a high level. It has a separate release cycle, and no modules. version0.0.1-SNAPSHOT/version So the version of Deep6MasterPOM is 0.0.1-SNAPSHOT... and the /Foundation/pom.xml as ... parent groupIdcom.areteq/groupId artifactIdDeep6MasterPOM/artifactId version1/version relativePath../Deep6MasterPOM/pom.xml/relativePath /parent ...but you're trying to use version 1, which probably hasn't been released yet. How do I make it keep my stuff local, and use the master only for the jars, etc. that it needs? Use 'mvn install' to put it in your local repository, and use the correct version number. -- 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 - 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
Super POM PlugIn Configuration / Multimodule Setup
Hi,
i have a multimodule setup...
Now i have the following question:
I use a plugin (maven-license-plugin) in my parent pom and do the
configuration of it there as well. The configuration of it are in a
folder of this parent module
Parent
+--- Module A
+--- Module B
+--- config-files
Based on the deriving of the parent POM every module now does the
license check, but within the modules the modules complains about not
finding the configuration files, so i have added into the
sub modules an configuration with referencing the configuration-files
via things like this:
${basedir}/../config-files to have only a single set of configuration
files for the plugin
Does exist there an more elegant way to do this ?
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM PlugIn Configuration / Multimodule Setup
Hi,
You could find a multimodule configuration for resources files (xml, txt
...) in the checkstyle plugin documentation.
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
This tips is to create a new maven module (jar) that will contains all your
resources needed by your plugin configuration.
And some plugin could check the classpath to retrieve resources.
Guillaume Boucherie
2008/9/17 Karl Heinz Marbaise [EMAIL PROTECTED]
Hi,
i have a multimodule setup...
Now i have the following question:
I use a plugin (maven-license-plugin) in my parent pom and do the
configuration of it there as well. The configuration of it are in a
folder of this parent module
Parent
+--- Module A
+--- Module B
+--- config-files
Based on the deriving of the parent POM every module now does the
license check, but within the modules the modules complains about not
finding the configuration files, so i have added into the
sub modules an configuration with referencing the configuration-files
via things like this:
${basedir}/../config-files to have only a single set of configuration
files for the plugin
Does exist there an more elegant way to do this ?
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven2: How to activate super pom profile to use it in child project?
Hi all,
I would like to activate profile which is placed in super pom for using
it in child project.
The reason:
I would like to use common properties but depends on profile in many
child projects.
Sample situation:
- super pom:
project ...
groupIdmyGroupId/groupId
artifactIdsuperLevel/artifactId
packagingpom/packaging
...
profiles
profile
idmainDevProperties/id
properties
filterFilePath/sample/filter.file/filterFilePath
/properties
/profile
/profiles
/project
- project pom
project ...
groupIdmyGroupId/groupId
artifactIdproject1/artifactId
...
parent
groupIdmyGroupId/groupId
artifactIdsuperLevel/artifactId
/parent
...
profiles
profile
idenv-dev/id
build
filters
filter${filterFilePath}/filter
/filters
/build
/profile
/profiles
/project
Command run on super pom level:
mvn process-resources -P mainDevProperties,env-dev
Error:
Error loading property file '...\${filterFilePath}'
Command run on super pom level:
mvn help:active-profiles -P mainDevProperties,env-dev
Result:
Active Profiles for Project 'myGroupId:superLevel:pom:...':
The following profiles are active:
- mainDevProperties (source: pom)
Active Profiles for Project 'myGroupId:project1:war:...':
The following profiles are active:
- env-dev (source: pom)
How to activate profile mainDevProperties for project project1.
Please help me with this issue.
Regards,
sapo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding maven-compiler-plugin to super POM
Hi guys, thanks for the replies. I read up on parent/child POMs and now understand what I was doing (or wasn't in this case). So maybe I'll modify my intitial question, is there anyway to configure my environment (Mac OS X) to tell Maven I always want JDK 1.5? It'd be nice if it inferred this from my JAVA_HOME setting. Or is it just an accepted practice that every Maven project must be explicitly set to JDK 1.5 via the maven-compiler-plugin? Thanks again. mikeottinger wrote: Hello, I'm trying to come up with a way such that new maven projects I create are ready to use JDK 1.5 by inheritance from a super POM. I'm having no luck, hence this post. I'm new to maven (thanks to this forum for telling me maven defaults to jdk 1.3) so super POMs are a little unfamiliar to me, from searching this forum I'm told that creating a pom.xml in the parent directory of my project somehow does the trick. I created one, added the plugin for maven-compiler-plugin, ran mvn install, but I still get jdk compiling errors. Does anyone have any suggestions in setting a jdk level globally for my environment? Are super POMs even the way to go? I tend to create a lot of little projects for prototyping and having to tell Maven I want jdk 1.5 for each of them is annoying. Thanks in advance! -- View this message in context: http://www.nabble.com/Adding-maven-compiler-plugin-to-super-POM-tp16851994s177p16897186.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Adding maven-compiler-plugin to super POM
Hello, I'm trying to come up with a way such that new maven projects I create are ready to use JDK 1.5 by inheritance from a super POM. I'm having no luck, hence this post. I'm new to maven (thanks to this forum for telling me maven defaults to jdk 1.3) so super POMs are a little unfamiliar to me, from searching this forum I'm told that creating a pom.xml in the parent directory of my project somehow does the trick. I created one, added the plugin for maven-compiler-plugin, ran mvn install, but I still get jdk compiling errors. Does anyone have any suggestions in setting a jdk level globally for my environment? Are super POMs even the way to go? I tend to create a lot of little projects for prototyping and having to tell Maven I want jdk 1.5 for each of them is annoying. Thanks in advance! -- View this message in context: http://www.nabble.com/Adding-maven-compiler-plugin-to-super-POM-tp16851994s177p16851994.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Adding maven-compiler-plugin to super POM
In your pom.xml file add the following: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin /plugins /build Thanks, Daniel King Vurv The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to the message and deleting it from your computer. Thank you. -Original Message- From: mikeottinger [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 4:06 PM To: users@maven.apache.org Subject: Adding maven-compiler-plugin to super POM Hello, I'm trying to come up with a way such that new maven projects I create are ready to use JDK 1.5 by inheritance from a super POM. I'm having no luck, hence this post. I'm new to maven (thanks to this forum for telling me maven defaults to jdk 1.3) so super POMs are a little unfamiliar to me, from searching this forum I'm told that creating a pom.xml in the parent directory of my project somehow does the trick. I created one, added the plugin for maven-compiler-plugin, ran mvn install, but I still get jdk compiling errors. Does anyone have any suggestions in setting a jdk level globally for my environment? Are super POMs even the way to go? I tend to create a lot of little projects for prototyping and having to tell Maven I want jdk 1.5 for each of them is annoying. Thanks in advance! -- View this message in context: http://www.nabble.com/Adding-maven-compiler-plugin-to-super-POM-tp168519 94s177p16851994.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Adding maven-compiler-plugin to super POM
You need to specify this pom as a parent element in your child pom...simply adding it in the parent directory doesn't magically do it for you ;-) Also, super-pom is normally reserved to mean the pom included in the maven core...the true super pom. A more appropriate term is a corporate pom for a corp wide setup, or just a parent pom. -Original Message- From: mikeottinger [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 4:06 PM To: users@maven.apache.org Subject: Adding maven-compiler-plugin to super POM Hello, I'm trying to come up with a way such that new maven projects I create are ready to use JDK 1.5 by inheritance from a super POM. I'm having no luck, hence this post. I'm new to maven (thanks to this forum for telling me maven defaults to jdk 1.3) so super POMs are a little unfamiliar to me, from searching this forum I'm told that creating a pom.xml in the parent directory of my project somehow does the trick. I created one, added the plugin for maven-compiler-plugin, ran mvn install, but I still get jdk compiling errors. Does anyone have any suggestions in setting a jdk level globally for my environment? Are super POMs even the way to go? I tend to create a lot of little projects for prototyping and having to tell Maven I want jdk 1.5 for each of them is annoying. Thanks in advance! -- View this message in context: http://www.nabble.com/Adding-maven-compiler-plugin-to-super-POM-tp168519 94s177p16851994.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can sub pom have different version than super pom
Dear Colleagues, I have two separate projects base and extension. Each project is really a multi-project inheritance hierarchy. Finally extension pom is a sub pom of base pom. The pom inheritance is as follows: base base-sub1 base-sub2 extension extension-sub1 extension-sub2 Since base and pom are separately released projects they need to be version independent of each other. For example it should be possible for version 2.0 of base be the parent pom of version 1.0 of extension. I recently discovered that this may not be possible. It seems that if I give extension pom a version it applies the same version to parent during build even though parent was give a separate and explicit version: project modelVersion4.0.0/modelVersion parent groupIdbase/groupId artifactIdbase/artifactId version2.0/version /parent groupIdderived/groupId artifactIdderived/artifactId version1.0/version ... /project It appears that building above pom causes version 1.0 of base to be used instead of 2.0. What am I doing wrong? -- Regards, Farrukh Najmi Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can sub pom have different version than super pom
If this is not possible then whats is the best way to avoid duplication of conetnt between base.pom and extension.pom? Also please see a typo fix inline below... Farrukh Najmi wrote: Dear Colleagues, I have two separate projects base and extension. Each project is really a multi-project inheritance hierarchy. Finally extension pom is a sub pom of base pom. The pom inheritance is as follows: base base-sub1 base-sub2 extension extension-sub1 extension-sub2 Since base and pom are separately released projects they need to be version independent of each other. For example it should be possible for version 2.0 of base be the parent pom of version 1.0 of extension. I recently discovered that this may not be possible. It seems that if I give extension pom a version it applies the same version to parent during build even though parent was give a separate and explicit version: project modelVersion4.0.0/modelVersion parent groupIdbase/groupId artifactIdbase/artifactId version2.0/version /parent groupIdderived/groupId artifactIdderived/artifactId version1.0/version ... /project Oops above should have read: project modelVersion4.0.0/modelVersion parent groupIdbase/groupId artifactIdbase/artifactId version2.0/version /parent groupIdextension/groupId artifactIdextension/artifactId version1.0/version ... /project It appears that building above pom causes version 1.0 of base to be used instead of 2.0. What am I doing wrong? -- Regards, Farrukh Najmi Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can sub pom have different version than super pom
Here is what learned about my problem:
* It is certainly possible to have a child pom (extension) have a
different version that its parent pom (base) - (good!)
* My problem was due to use of variable ${pom.parent.version} within
dependencyManagement section. Apparently the variable gets
resolved in the child poms of extension and not where is is
defined. This was causing incorrect version to be picked up
The fix was to hard-code the version in dependencyManagement section of
extension.pom to be same as the pom.parent.version in extension.pom.
Thanks.
Farrukh Najmi wrote:
If this is not possible then whats is the best way to avoid
duplication of conetnt between base.pom and extension.pom?
Also please see a typo fix inline below...
Farrukh Najmi wrote:
Dear Colleagues,
I have two separate projects base and extension.
Each project is really a multi-project inheritance hierarchy.
Finally extension pom is a sub pom of base pom.
The pom inheritance is as follows:
base
base-sub1
base-sub2
extension
extension-sub1
extension-sub2
Since base and pom are separately released projects they need to be
version independent of each other.
For example it should be possible for version 2.0 of base be the
parent pom of version 1.0 of extension.
I recently discovered that this may not be possible. It seems that if
I give extension pom a version it applies the same
version to parent during build even though parent was give a separate
and explicit version:
project
modelVersion4.0.0/modelVersion
parent
groupIdbase/groupId
artifactIdbase/artifactId
version2.0/version
/parent
groupIdderived/groupId
artifactIdderived/artifactId
version1.0/version
...
/project
Oops above should have read:
project
modelVersion4.0.0/modelVersion
parent
groupIdbase/groupId
artifactIdbase/artifactId
version2.0/version
/parent
groupIdextension/groupId
artifactIdextension/artifactId
version1.0/version
...
/project
It appears that building above pom causes version 1.0 of base to be
used instead of 2.0.
What am I doing wrong?
--
Regards,
Farrukh Najmi
Web: http://www.wellfleetsoftware.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Super POM location
I think the super-pom is the name for the concept of default settings and there is no actual super pom. The normal solution for your problem would be to create a corporate/company pom and let all projects add it as their parent. Hth, Nick S. -Original Message- From: Marcelo Alcantara [mailto:[EMAIL PROTECTED] Sent: Fri 2/15/2008 17:26 To: users@maven.apache.org Subject: Super POM location Hi, I searched a lot in the Internet but could not find this answer. Where is the super pom located? I have configurations that are for all projects that I wanted to setup in it. Thanks in advance. -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823
Super POM location
Hi, I searched a lot in the Internet but could not find this answer. Where is the super pom located? I have configurations that are for all projects that I wanted to setup in it. Thanks in advance. -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823
Re: Super POM location
actually, it does exist. if you look in the maven uber jar it's under org.apache.maven.project On Fri, Feb 15, 2008 at 10:30 AM, [EMAIL PROTECTED] wrote: I think the super-pom is the name for the concept of default settings and there is no actual super pom. The normal solution for your problem would be to create a corporate/company pom and let all projects add it as their parent. Hth, Nick S. -Original Message- From: Marcelo Alcantara [mailto:[EMAIL PROTECTED] Sent: Fri 2/15/2008 17:26 To: users@maven.apache.org Subject: Super POM location Hi, I searched a lot in the Internet but could not find this answer. Where is the super pom located? I have configurations that are for all projects that I wanted to setup in it. Thanks in advance. -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823 -- Gregory Kick http://kickstyle.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Super POM location
Ok, I've found it, it is under: https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml Hth, Nick S. -Original Message- From: Gregory Kick [mailto:[EMAIL PROTECTED] Sent: Fri 2/15/2008 17:35 To: Maven Users List Subject: Re: Super POM location actually, it does exist. if you look in the maven uber jar it's under org.apache.maven.project On Fri, Feb 15, 2008 at 10:30 AM, [EMAIL PROTECTED] wrote: I think the super-pom is the name for the concept of default settings and there is no actual super pom. The normal solution for your problem would be to create a corporate/company pom and let all projects add it as their parent. Hth, Nick S. -Original Message- From: Marcelo Alcantara [mailto:[EMAIL PROTECTED] Sent: Fri 2/15/2008 17:26 To: users@maven.apache.org Subject: Super POM location Hi, I searched a lot in the Internet but could not find this answer. Where is the super pom located? I have configurations that are for all projects that I wanted to setup in it. Thanks in advance. -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823 -- Gregory Kick http://kickstyle.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM location
Ok! Thanks everybody for the promply respose! Regards, Marcelo On Fri, Feb 15, 2008 at 3:05 PM, Wayne Fay [EMAIL PROTECTED] wrote: As already mentioned, there is a super pom (in the Maven jar itself), but you shoudn't be editing it. Instead you should make a top level corporate pom and have all projects inherit from it (set as parent). Wayne On 2/15/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Ok, I've found it, it is under: https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml Hth, Nick S. -Original Message- From: Gregory Kick [mailto:[EMAIL PROTECTED] Sent: Fri 2/15/2008 17:35 To: Maven Users List Subject: Re: Super POM location actually, it does exist. if you look in the maven uber jar it's under org.apache.maven.project On Fri, Feb 15, 2008 at 10:30 AM, [EMAIL PROTECTED] wrote: I think the super-pom is the name for the concept of default settings and there is no actual super pom. The normal solution for your problem would be to create a corporate/company pom and let all projects add it as their parent. Hth, Nick S. -Original Message- From: Marcelo Alcantara [mailto:[EMAIL PROTECTED] Sent: Fri 2/15/2008 17:26 To: users@maven.apache.org Subject: Super POM location Hi, I searched a lot in the Internet but could not find this answer. Where is the super pom located? I have configurations that are for all projects that I wanted to setup in it. Thanks in advance. -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823 -- Gregory Kick http://kickstyle.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823
Re: Super POM location
example? Thanks M- - Original Message - From: Marcelo Alcantara [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Friday, February 15, 2008 3:24 PM Subject: Re: Super POM location Ok! Thanks everybody for the promply respose! Regards, Marcelo On Fri, Feb 15, 2008 at 3:05 PM, Wayne Fay [EMAIL PROTECTED] wrote: As already mentioned, there is a super pom (in the Maven jar itself), but you shoudn't be editing it. Instead you should make a top level corporate pom and have all projects inherit from it (set as parent). Wayne On 2/15/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Ok, I've found it, it is under: https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven -project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml Hth, Nick S. -Original Message- From: Gregory Kick [mailto:[EMAIL PROTECTED] Sent: Fri 2/15/2008 17:35 To: Maven Users List Subject: Re: Super POM location actually, it does exist. if you look in the maven uber jar it's under org.apache.maven.project On Fri, Feb 15, 2008 at 10:30 AM, [EMAIL PROTECTED] wrote: I think the super-pom is the name for the concept of default settings and there is no actual super pom. The normal solution for your problem would be to create a corporate/company pom and let all projects add it as their parent. Hth, Nick S. -Original Message- From: Marcelo Alcantara [mailto:[EMAIL PROTECTED] Sent: Fri 2/15/2008 17:26 To: users@maven.apache.org Subject: Super POM location Hi, I searched a lot in the Internet but could not find this answer. Where is the super pom located? I have configurations that are for all projects that I wanted to setup in it. Thanks in advance. -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823 -- Gregory Kick http://kickstyle.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM location
As already mentioned, there is a super pom (in the Maven jar itself), but you shoudn't be editing it. Instead you should make a top level corporate pom and have all projects inherit from it (set as parent). Wayne On 2/15/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Ok, I've found it, it is under: https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml Hth, Nick S. -Original Message- From: Gregory Kick [mailto:[EMAIL PROTECTED] Sent: Fri 2/15/2008 17:35 To: Maven Users List Subject: Re: Super POM location actually, it does exist. if you look in the maven uber jar it's under org.apache.maven.project On Fri, Feb 15, 2008 at 10:30 AM, [EMAIL PROTECTED] wrote: I think the super-pom is the name for the concept of default settings and there is no actual super pom. The normal solution for your problem would be to create a corporate/company pom and let all projects add it as their parent. Hth, Nick S. -Original Message- From: Marcelo Alcantara [mailto:[EMAIL PROTECTED] Sent: Fri 2/15/2008 17:26 To: users@maven.apache.org Subject: Super POM location Hi, I searched a lot in the Internet but could not find this answer. Where is the super pom located? I have configurations that are for all projects that I wanted to setup in it. Thanks in advance. -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823 -- Gregory Kick http://kickstyle.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FATAL ERROR on release:prepare with a super-pom
Hi folks, I'm trying to do a mv nrelease:prepare from a super-pom that have a lsit of proyects i want to release to the same version.. All was runing fine,asking the new version, the SCM TAG ..but just after this i have a FATAL ERROR : java.lang.ArrayIndexOutOfBoundsException: 37 at ...shared.release.phase.RewritePomsForReleasePhase.TranslateUrlPath(RewritePomForReleasePhase.java:249) If any one know this issue, reply quickly please, i need do the release this morning. Thanks a lot to all for all. Have a nice day and nice holydays!! -- View this message in context: http://www.nabble.com/FATAL-ERROR-on-release%3Aprepare--with-a-super-pom-tp14332951s177p14332951.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: FATAL ERROR on release:prepare with a super-pom
De code at the linenumber is:
if ( trunkPath.endsWith( / ) )
{
trunkPath = trunkPath.substring( 0, trunkPath.length() - 1 );
}
if ( tagPath.endsWith( / ) )
{
tagPath = tagPath.substring( 0, tagPath.length() - 1 );
}
Which will throw an exception if your trunkPath or tagPath is empty.
So something is wrong with that, I don't know what.
With regards,
Nick Stolwijk
-Original Message-
From: javijava [mailto:[EMAIL PROTECTED]
Sent: Fri 12/14/2007 11:04 AM
To: users@maven.apache.org
Subject: FATAL ERROR on release:prepare with a super-pom
Hi folks,
I'm trying to do a mv nrelease:prepare from a super-pom that have a lsit of
proyects i want to release to the same version..
All was runing fine,asking the new version, the SCM TAG ..but just after
this i have a FATAL ERROR : java.lang.ArrayIndexOutOfBoundsException: 37
at
...shared.release.phase.RewritePomsForReleasePhase.TranslateUrlPath(RewritePomForReleasePhase.java:249)
If any one know this issue, reply quickly please, i need do the release
this morning.
Thanks a lot to all for all.
Have a nice day and nice holydays!!
--
View this message in context:
http://www.nabble.com/FATAL-ERROR-on-release%3Aprepare--with-a-super-pom-tp14332951s177p14332951.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: FATAL ERROR on release:prepare with a super-pom
This is deep down in the maven-release code, so no, you don't have to adjust it.
Why are you using relativePath? If you remove it and do a mvn install the super
pom is copied to your local repository and found from there.
With regards,
Nick Stolwijk
-Original Message-
From: javijava [mailto:[EMAIL PROTECTED]
Sent: Fri 12/14/2007 12:46 PM
To: users@maven.apache.org
Subject: RE: FATAL ERROR on release:prepare with a super-pom
De code at the linenumber is:
if ( trunkPath.endsWith( / ) )
{
trunkPath = trunkPath.substring( 0, trunkPath.length() - 1 );
}
if ( tagPath.endsWith( / ) )
{
tagPath = tagPath.substring( 0, tagPath.length() - 1 );
}
.Where are placed this lines? in a maven-configuration fike?
.i must modify this..or is only the way that maven work with paths?
Which will throw an exception if your trunkPath or tagPath is empty.
Is possible, that the parent tags in each sub-project are wrong?
i have the super-pom in a folder like the sub projects (same level), an
example of tags:
parent
groupIdxxx/groupId
artifactIdsuper-pom/artifactId
version0.1-SNAPSHOT/version
relativePath../super-pom/pom.xml/relativePath
/parent
Thanks 4 the reply Nick.
--
View this message in context:
http://www.nabble.com/FATAL-ERROR-on-release%3Aprepare--with-a-super-pom-tp14332951s177p14334423.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: FATAL ERROR on release:prepare with a super-pom
De code at the linenumber is:
if ( trunkPath.endsWith( / ) )
{
trunkPath = trunkPath.substring( 0, trunkPath.length() - 1 );
}
if ( tagPath.endsWith( / ) )
{
tagPath = tagPath.substring( 0, tagPath.length() - 1 );
}
.Where are placed this lines? in a maven-configuration fike?
.i must modify this..or is only the way that maven work with paths?
Which will throw an exception if your trunkPath or tagPath is empty.
Is possible, that the parent tags in each sub-project are wrong?
i have the super-pom in a folder like the sub projects (same level), an
example of tags:
parent
groupIdxxx/groupId
artifactIdsuper-pom/artifactId
version0.1-SNAPSHOT/version
relativePath../super-pom/pom.xml/relativePath
/parent
Thanks 4 the reply Nick.
--
View this message in context:
http://www.nabble.com/FATAL-ERROR-on-release%3Aprepare--with-a-super-pom-tp14332951s177p14334423.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Common reporting configuration for a set of projects / inheritance from super-pom
Hello, I would like to separate the reporting section for all of our projects in a common configuration file or pom to keep the projects pom as simple as possible. I already created a hierarchy of poms (java-pom, maven-plugin-pom and so on) for the different project types to externalize common settings for similar projects. But the reporting section included in my java-pom isn't inherited by my java projects. Searching the Internet I found out this is the expected behaviour. But how do you solve the problem of a central reporting configuration? Do you repeat the reporting configuration in every project pom? Greetings, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to disable Super POM
Hi, I'm using Maven 2.0.5 for dependency management in my Ant script. The ant script is a generic script which can be used to build multiple projects. And the projects share a lot of API's which we have planned to manage using an internal central repository. So I created a Parent POM file for all the dependency API's in the central repository and a child POM for each project to be built. The Child POM will have only the dependencies required for a particular project. Now though I have Parent POM and a internal repository configured while execution Maven tries to fetch certain missing pieces from the http://repo1.maven.org/maven2/. I learnt that this repository is configured in the Super POM and will be inherited by all the POM files. I need to disable this feature so that Maven should only refer to the internal repository. I tried to get information through internet but I wasn't able to get it. Some one if you know how to do this or if you see that I'm missing some thing please advice. Thanks in Advance, - Aravinth.
Re: How to disable Super POM
Generally people override central by utilizing settings.xml: settings mirrors mirror idmirror-maven-central/id mirrorOfcentral/mirrorOf namelocal corporate repo override for central/name urlurl to your local corporate repo/url /mirror /mirrors /settings Wayne On 3/22/07, Aravindhan Damodharan [EMAIL PROTECTED] wrote: Hi, I'm using Maven 2.0.5 for dependency management in my Ant script. The ant script is a generic script which can be used to build multiple projects. And the projects share a lot of API's which we have planned to manage using an internal central repository. So I created a Parent POM file for all the dependency API's in the central repository and a child POM for each project to be built. The Child POM will have only the dependencies required for a particular project. Now though I have Parent POM and a internal repository configured while execution Maven tries to fetch certain missing pieces from the http://repo1.maven.org/maven2/. I learnt that this repository is configured in the Super POM and will be inherited by all the POM files. I need to disable this feature so that Maven should only refer to the internal repository. I tried to get information through internet but I wasn't able to get it. Some one if you know how to do this or if you see that I'm missing some thing please advice. Thanks in Advance, - Aravinth. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to disable Super POM
Hi Wayne, Thanks for the reply. I tried setting up mirrors. But that didn't do. The build script still refers the Maven's default Central repository. One good thing is the script first checks in my internal repository for an artifact. And if it doesn't exit it tries to get it from the Maven Central. I have even set the offline parameter to true to prevent Maven from connecting to network. But still no use. The log in the console shows that Maven tries to fetch from both the internal and the Maven's Central repository. Is there any other way to do this ? Thanks in Advance, - Aravinth. Generally people override central by utilizing settings.xml: settings mirrors mirror idmirror-maven-central/id mirrorOfcentral/mirrorOf namelocal corporate repo override for central/name urlurl to your local corporate repo/url /mirror /mirrors /settings Wayne On 3/22/07, Aravindhan Damodharan [EMAIL PROTECTED] wrote: Hi, I'm using Maven 2.0.5 for dependency management in my Ant script. The ant script is a generic script which can be used to build multiple projects. And the projects share a lot of API's which we have planned to manage using an internal central repository. So I created a Parent POM file for all the dependency API's in the central repository and a child POM for each project to be built. The Child POM will have only the dependencies required for a particular project. Now though I have Parent POM and a internal repository configured while execution Maven tries to fetch certain missing pieces from the http://repo1.maven.org/maven2/. I learnt that this repository is configured in the Super POM and will be inherited by all the POM files. I need to disable this feature so that Maven should only refer to the internal repository. I tried to get information through internet but I wasn't able to get it. Some one if you know how to do this or if you see that I'm missing some thing please advice. Thanks in Advance, - Aravinth.
Re: How to disable Super POM
First off, you mention the build script -- what exactly are you talking about? Simply the pom.xml files you've created, which Maven uses to create your build -- or do you have some other build script process in addition to Maven. I'd suspect you have a stray repository defined in some random pom in your project or in one of your dependencies. Search your ~/.m2 directory for repository in *.pom files. Try mvn help:effective-pom from your top level project and look at all the repository nodes in all your poms. Also try mvn -X ... to get more debugging information about your build while it executes which might make the problem more obvious. Finally, try mirrorOf*/mirrorOf in your settings.xml to override ALL repositories. At that point, I don't think it is possible for Maven to attempt to connect to any repo except the one defined in settings.xml. Wayne On 3/22/07, Aravindhan Damodharan [EMAIL PROTECTED] wrote: Hi Wayne, Thanks for the reply. I tried setting up mirrors. But that didn't do. The build script still refers the Maven's default Central repository. One good thing is the script first checks in my internal repository for an artifact. And if it doesn't exit it tries to get it from the Maven Central. I have even set the offline parameter to true to prevent Maven from connecting to network. But still no use. The log in the console shows that Maven tries to fetch from both the internal and the Maven's Central repository. Is there any other way to do this ? Thanks in Advance, - Aravinth. Generally people override central by utilizing settings.xml: settings mirrors mirror idmirror-maven-central/id mirrorOfcentral/mirrorOf namelocal corporate repo override for central/name urlurl to your local corporate repo/url /mirror /mirrors /settings Wayne On 3/22/07, Aravindhan Damodharan [EMAIL PROTECTED] wrote: Hi, I'm using Maven 2.0.5 for dependency management in my Ant script. The ant script is a generic script which can be used to build multiple projects. And the projects share a lot of API's which we have planned to manage using an internal central repository. So I created a Parent POM file for all the dependency API's in the central repository and a child POM for each project to be built. The Child POM will have only the dependencies required for a particular project. Now though I have Parent POM and a internal repository configured while execution Maven tries to fetch certain missing pieces from the http://repo1.maven.org/maven2/. I learnt that this repository is configured in the Super POM and will be inherited by all the POM files. I need to disable this feature so that Maven should only refer to the internal repository. I tried to get information through internet but I wasn't able to get it. Some one if you know how to do this or if you see that I'm missing some thing please advice. Thanks in Advance, - Aravinth. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to disable Super POM
only the dependencies required for a particular project. Now though I have Parent POM and a internal repository configured while execution Maven tries to fetch certain missing pieces from the http://repo1.maven.org/maven2/. I learnt that this repository is configured in the Super POM and will be inherited by all the POM files. I need to disable this feature so that Maven should only refer to the internal repository. I tried to get information through internet but I wasn't able to get it. Some one if you know how to do this or if you see that I'm missing some thing please advice. Thanks in Advance, - Aravinth.
Re: How to disable Super POM
which we have planned to manage using an internal central repository. So I created a Parent POM file for all the dependency API's in the central repository and a child POM for each project to be built. The Child POM will have only the dependencies required for a particular project. Now though I have Parent POM and a internal repository configured while execution Maven tries to fetch certain missing pieces from the http://repo1.maven.org/maven2/. I learnt that this repository is configured in the Super POM and will be inherited by all the POM files. I need to disable this feature so that Maven should only refer to the internal repository. I tried to get information through internet but I wasn't able to get it. Some one if you know how to do this or if you see that I'm missing some thing please advice. Thanks in Advance, - Aravinth. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to disable Super POM
to network. But still no use. The log in the console shows that Maven tries to fetch from both the internal and the Maven's Central repository. Is there any other way to do this ? Thanks in Advance, - Aravinth. Generally people override central by utilizing settings.xml: settings mirrors mirror idmirror-maven-central/id mirrorOfcentral/mirrorOf namelocal corporate repo override for central/name urlurl to your local corporate repo/url /mirror /mirrors /settings Wayne On 3/22/07, Aravindhan Damodharan [EMAIL PROTECTED] wrote: Hi, I'm using Maven 2.0.5 for dependency management in my Ant script. The ant script is a generic script which can be used to build multiple projects. And the projects share a lot of API's which we have planned to manage using an internal central repository. So I created a Parent POM file for all the dependency API's in the central repository and a child POM for each project to be built. The Child POM will have only the dependencies required for a particular project. Now though I have Parent POM and a internal repository configured while execution Maven tries to fetch certain missing pieces from the http://repo1.maven.org/maven2/. I learnt that this repository is configured in the Super POM and will be inherited by all the POM files. I need to disable this feature so that Maven should only refer to the internal repository. I tried to get information through internet but I wasn't able to get it. Some one if you know how to do this or if you see that I'm missing some thing please advice. Thanks in Advance, - Aravinth. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -- Tommy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
reporting on super pom ?
Hi all !!! I would like to add the information about distributionManagement and reporting in somewhere in order to be common to all projects. I know that is a super pom used by maven, but how can I customize that pom? (where is it?). Besides, distributionManagement does not get inherited, is there a way to define that info in some other place? (.m2/settings.xml ?). My objective is make reporting common to all projects and make the site and site:deploy automatically with continuum. Is there other way to do this? Any tips would be very appreciated... THX in advance! Rodrigo Looking for earth-friendly autos? Browse Top Cars by Green Rating at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/
maven2 warning when using company super pom ?
We have a company super pom with no modules. Just common dependencies, java
compile version, etc.
It is included in all of our projects as parent.
However when I run mvn clean package on my project pom I get a warning in phase
site:attach-descriptor
saying that the parent pom does not exist in the parent folder.
[INFO] [site:attach-descriptor]
[WARNING] Unable to load parent project from a relative path: Could not find
the model file 'C:\${path_to_myproject}\..\pom.xml'.
Is there a way to get rid of this message? I thought a parent pom should not
necessary be in a parent folder unless includes the child pom as module. In
my case it does not so I would expect to have no warnings.
thanks,
Attila
-
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
Re: Super POM
Good day, FYI, it's in maven-project ( [1] ). Also you can see it in the documentation [2] . Cheers, Franz [1] http://svn.apache.org/repos/asf/maven/components/trunk/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml [2] http://maven.apache.org/guides/introduction/introduction-to-the-pom.html jiangshachina wrote: Hi Wayne, but you can find it if you search the Maven jars. I'll do. But you shouldn't extract the file, edit, and add it back to the jar; instead just write your configuration etc in your own local project pom.xml file. Of course, I don't modify the POM. I just be curious about the matter. a cup of Java, cheers! Sha Jiang Wayne Fay wrote: I wrote this email a long, long time ago. ;-) Since then, I have found out that there certainly is a real super pom which is in one of the Maven jars... forget which one, but you can find it if you search the Maven jars. But you shouldn't extract the file, edit, and add it back to the jar; instead just write your configuration etc in your own local project pom.xml file. Wayne On 12/24/06, jiangshachina [EMAIL PROTECTED] wrote: Hi Wayne, I really don't understand your words. If Super POM doesn't exist in my machine as a real and independent file, then it may be built by source codes as a concept. Does it means that if the concept of Super POM is changed, then the source of Maven would be changed, too? I cannot imagine that. a cup of Java, cheers! Sha Jiang Wayne Fay wrote: There is no Super POM in the filesystem somewhere. It is merely a concept. /home/brian/java/projects/pom.xml /home/brian/java/projects/proj1/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj1/lib/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj1/web/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/lib/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/web/pom.xml (parent = ../pom.xml) Thus all projects will share the /projects/pom.xml as a super pom. Wayne On 4/6/06, Brian Robinson [EMAIL PROTECTED] wrote: Can anyone tell me where I can find the Super POM on the file system? I want to have one place where I can have all projects use our repository, and I would like to avoid using parent tags in each pom.xml in my many projects. Also, ideally we won't have to have every developer use their own settings.xml to set this up either. It seems like the super POM is the right place to put it, but I can't find it. Maybe I'm misunderstanding what the Super POM is? Thanks, -Brian Even when you've played the game of your life, it's the feeling of teamwork that you'll remember. - John C. Maxwell -- View this message in context: http://www.nabble.com/Super-POM-tf1407288s177.html#a8039753 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Super-POM-tf1407288s177.html#a8073900 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM
Hi franz, I get it. Thanks very much! a cup of Java, cheers! Sha Jiang franz see wrote: Good day, FYI, it's in maven-project ( [1] ). Also you can see it in the documentation [2] . Cheers, Franz [1] http://svn.apache.org/repos/asf/maven/components/trunk/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml [2] http://maven.apache.org/guides/introduction/introduction-to-the-pom.html jiangshachina wrote: Hi Wayne, but you can find it if you search the Maven jars. I'll do. But you shouldn't extract the file, edit, and add it back to the jar; instead just write your configuration etc in your own local project pom.xml file. Of course, I don't modify the POM. I just be curious about the matter. a cup of Java, cheers! Sha Jiang Wayne Fay wrote: I wrote this email a long, long time ago. ;-) Since then, I have found out that there certainly is a real super pom which is in one of the Maven jars... forget which one, but you can find it if you search the Maven jars. But you shouldn't extract the file, edit, and add it back to the jar; instead just write your configuration etc in your own local project pom.xml file. Wayne On 12/24/06, jiangshachina [EMAIL PROTECTED] wrote: Hi Wayne, I really don't understand your words. If Super POM doesn't exist in my machine as a real and independent file, then it may be built by source codes as a concept. Does it means that if the concept of Super POM is changed, then the source of Maven would be changed, too? I cannot imagine that. a cup of Java, cheers! Sha Jiang Wayne Fay wrote: There is no Super POM in the filesystem somewhere. It is merely a concept. /home/brian/java/projects/pom.xml /home/brian/java/projects/proj1/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj1/lib/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj1/web/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/lib/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/web/pom.xml (parent = ../pom.xml) Thus all projects will share the /projects/pom.xml as a super pom. Wayne On 4/6/06, Brian Robinson [EMAIL PROTECTED] wrote: Can anyone tell me where I can find the Super POM on the file system? I want to have one place where I can have all projects use our repository, and I would like to avoid using parent tags in each pom.xml in my many projects. Also, ideally we won't have to have every developer use their own settings.xml to set this up either. It seems like the super POM is the right place to put it, but I can't find it. Maybe I'm misunderstanding what the Super POM is? Thanks, -Brian Even when you've played the game of your life, it's the feeling of teamwork that you'll remember. - John C. Maxwell -- View this message in context: http://www.nabble.com/Super-POM-tf1407288s177.html#a8039753 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Super-POM-tf1407288s177.html#a8082243 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM
Hi Wayne, I really don't understand your words. If Super POM doesn't exist in my machine as a real and independent file, then it may be built by source codes as a concept. Does it means that if the concept of Super POM is changed, then the source of Maven would be changed, too? I cannot imagine that. a cup of Java, cheers! Sha Jiang Wayne Fay wrote: There is no Super POM in the filesystem somewhere. It is merely a concept. /home/brian/java/projects/pom.xml /home/brian/java/projects/proj1/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj1/lib/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj1/web/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/lib/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/web/pom.xml (parent = ../pom.xml) Thus all projects will share the /projects/pom.xml as a super pom. Wayne On 4/6/06, Brian Robinson [EMAIL PROTECTED] wrote: Can anyone tell me where I can find the Super POM on the file system? I want to have one place where I can have all projects use our repository, and I would like to avoid using parent tags in each pom.xml in my many projects. Also, ideally we won't have to have every developer use their own settings.xml to set this up either. It seems like the super POM is the right place to put it, but I can't find it. Maybe I'm misunderstanding what the Super POM is? Thanks, -Brian Even when you've played the game of your life, it's the feeling of teamwork that you'll remember. - John C. Maxwell -- View this message in context: http://www.nabble.com/Super-POM-tf1407288s177.html#a8039753 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM
I wrote this email a long, long time ago. ;-) Since then, I have found out that there certainly is a real super pom which is in one of the Maven jars... forget which one, but you can find it if you search the Maven jars. But you shouldn't extract the file, edit, and add it back to the jar; instead just write your configuration etc in your own local project pom.xml file. Wayne On 12/24/06, jiangshachina [EMAIL PROTECTED] wrote: Hi Wayne, I really don't understand your words. If Super POM doesn't exist in my machine as a real and independent file, then it may be built by source codes as a concept. Does it means that if the concept of Super POM is changed, then the source of Maven would be changed, too? I cannot imagine that. a cup of Java, cheers! Sha Jiang Wayne Fay wrote: There is no Super POM in the filesystem somewhere. It is merely a concept. /home/brian/java/projects/pom.xml /home/brian/java/projects/proj1/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj1/lib/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj1/web/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/lib/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/web/pom.xml (parent = ../pom.xml) Thus all projects will share the /projects/pom.xml as a super pom. Wayne On 4/6/06, Brian Robinson [EMAIL PROTECTED] wrote: Can anyone tell me where I can find the Super POM on the file system? I want to have one place where I can have all projects use our repository, and I would like to avoid using parent tags in each pom.xml in my many projects. Also, ideally we won't have to have every developer use their own settings.xml to set this up either. It seems like the super POM is the right place to put it, but I can't find it. Maybe I'm misunderstanding what the Super POM is? Thanks, -Brian Even when you've played the game of your life, it's the feeling of teamwork that you'll remember. - John C. Maxwell -- View this message in context: http://www.nabble.com/Super-POM-tf1407288s177.html#a8039753 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM
Hi Wayne, but you can find it if you search the Maven jars. I'll do. But you shouldn't extract the file, edit, and add it back to the jar; instead just write your configuration etc in your own local project pom.xml file. Of course, I don't modify the POM. I just be curious about the matter. a cup of Java, cheers! Sha Jiang Wayne Fay wrote: I wrote this email a long, long time ago. ;-) Since then, I have found out that there certainly is a real super pom which is in one of the Maven jars... forget which one, but you can find it if you search the Maven jars. But you shouldn't extract the file, edit, and add it back to the jar; instead just write your configuration etc in your own local project pom.xml file. Wayne On 12/24/06, jiangshachina [EMAIL PROTECTED] wrote: Hi Wayne, I really don't understand your words. If Super POM doesn't exist in my machine as a real and independent file, then it may be built by source codes as a concept. Does it means that if the concept of Super POM is changed, then the source of Maven would be changed, too? I cannot imagine that. a cup of Java, cheers! Sha Jiang Wayne Fay wrote: There is no Super POM in the filesystem somewhere. It is merely a concept. /home/brian/java/projects/pom.xml /home/brian/java/projects/proj1/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj1/lib/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj1/web/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/lib/pom.xml (parent = ../pom.xml) /home/brian/java/projects/proj2/web/pom.xml (parent = ../pom.xml) Thus all projects will share the /projects/pom.xml as a super pom. Wayne On 4/6/06, Brian Robinson [EMAIL PROTECTED] wrote: Can anyone tell me where I can find the Super POM on the file system? I want to have one place where I can have all projects use our repository, and I would like to avoid using parent tags in each pom.xml in my many projects. Also, ideally we won't have to have every developer use their own settings.xml to set this up either. It seems like the super POM is the right place to put it, but I can't find it. Maybe I'm misunderstanding what the Super POM is? Thanks, -Brian Even when you've played the game of your life, it's the feeling of teamwork that you'll remember. - John C. Maxwell -- View this message in context: http://www.nabble.com/Super-POM-tf1407288s177.html#a8039753 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Super-POM-tf1407288s177.html#a8044517 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
super pom filter
I have a pom that has a couple of modules, I would like to post a site
directly to my baseDir or more accurately my top most pom's directory. I
tried something like this in my top most pom:
distributionManagement
site
idtest.site/id
nameTest Website/name
urlfile:${baseDir}\website2\${project.version}\/url
/site
/distributionManagement
but ${baseDir} gets redefined with each sub pom. is there something like a
${top.most.pom.dir}, a ${projecet.dir} filter, or a work-around so all of
the module's site content end's up in the same place - only using files
inside that directory.
Thanks
Fox
--
View this message in context:
http://www.nabble.com/super-pom-filter-tf2217708.html#a6142939
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: super pom filter
I stopped using the URL for parent or master poms. Instead I deploy a
shared pom to our internal respository.
You have to make sure that the using pom defines either the repository
where you deployed the master pom or have it defined in your
settings.xml. Either way you have to provide to maven the location of
your repository.
A using pom's reference in my case would look like the following:
parent
groupIdmarkettools.pom/groupId
artifactIdmaster-pom/artifactId
version4.0.5/version
/parent
Andreas
-Original Message-
From: foxcoll [mailto:[EMAIL PROTECTED]
Sent: Monday, September 04, 2006 3:21 PM
To: users@maven.apache.org
Subject: super pom filter
I have a pom that has a couple of modules, I would like to post a site
directly to my baseDir or more accurately my top most pom's directory. I
tried something like this in my top most pom:
distributionManagement
site
idtest.site/id
nameTest Website/name
urlfile:${baseDir}\website2\${project.version}\/url
/site
/distributionManagement
but ${baseDir} gets redefined with each sub pom. is there something
like a
${top.most.pom.dir}, a ${projecet.dir} filter, or a work-around so all
of
the module's site content end's up in the same place - only using files
inside that directory.
Thanks
Fox
--
View this message in context:
http://www.nabble.com/super-pom-filter-tf2217708.html#a6142939
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: basedir of super pom
Can Clover read your license file from the classpath ? Then you could deploy your (jarred) license to your maven repo and add it as a dependency to the clover plugin. See the checkstyle plugin docs [1] for more information - it allows you to do a similar thing with checkstyle configurations. Tom 1. http://maven.apache.org/plugins/maven-checkstyle-plugin/tips.html On 8/16/06, Ingo Düppe [EMAIL PROTECTED] wrote: This is not really a good solution, because then you have to be always online and must have contact to the server. No other solution? Regards, Ingo Emmanuel Venisse schrieb: No you can't. It would be better to use an url to reference your clover license file. Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
basedir of super pom
Hello,
is it possible in a multi module project to reference a directory in an
absolute manner of the super pom?
Independent of the current position I like to reference a directory from
the top root directory of myproject.
For instance I have following project structure:
myproject
module-1
module-1-api
pom.xml
module-1-core
pom.xml
pom.xml
module-2
module-2-api
pom.xml
module-2-core
pom.xml
pom.xml
src
test
clover
clover.license
pom.xml == my super pom
I like to define in my super pom.xml that the clover license is in the
directory /src/test/clover/clover.license but all possible variables I
found like ${basedir}or ${pom.dir} doesn't work.
Any ideas?
Regards,
Ingo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: basedir of super pom
No you can't.
It would be better to use an url to reference your clover license file.
Emmanuel
Ingo Düppe a écrit :
Hello,
is it possible in a multi module project to reference a directory in an
absolute manner of the super pom?
Independent of the current position I like to reference a directory from
the top root directory of myproject.
For instance I have following project structure:
myproject
module-1
module-1-api
pom.xml
module-1-core
pom.xml
pom.xml
module-2
module-2-api
pom.xml
module-2-core
pom.xml
pom.xml
src
test
clover
clover.license
pom.xml == my super pom
I like to define in my super pom.xml that the clover license is in the
directory /src/test/clover/clover.license but all possible variables I
found like ${basedir}or ${pom.dir} doesn't work.
Any ideas?
Regards,
Ingo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: basedir of super pom
This is not really a good solution, because then you have to be always online and must have contact to the server. No other solution? Regards, Ingo Emmanuel Venisse schrieb: No you can't. It would be better to use an url to reference your clover license file. Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: basedir of super pom
Could you just symlink the license file around to the various directories? On 8/16/06, Wayne Fay [EMAIL PROTECTED] wrote: Set up Apache on your box and point it to the top root directory. Then its always online and you're obviously connected to the server, so you can use a URL to the file. Wayne On 8/16/06, Ingo Düppe [EMAIL PROTECTED] wrote: This is not really a good solution, because then you have to be always online and must have contact to the server. No other solution? Regards, Ingo Emmanuel Venisse schrieb: No you can't. It would be better to use an url to reference your clover license file. Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super Pom
Maybe this link response to your question: http://maven.apache.org/ref/current/maven-model/maven.html HTH Tung Nguyen - Original Message From: Lakshman Srilakshmanan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: users@maven.apache.org Sent: Thursday, July 27, 2006 2:03:58 AM Subject: RE: Super Pom Hi Emmanuel, Thanks for your reply. The http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html describes how to include a customised checkstyle within a POM. I need to know the location of the super POM itself, if one exists. Thanks Lakshman -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, 26 July 2006 5:28 PM To: Maven Users List Subject: Re: Super Pom http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html Lakshman Srilakshmanan a écrit : Hi All, I have used maven 1.x for a couple of years now and am in the process of migrating to maven 2.x I need to set some configuration globally (eg customised checkstyle). I find the appropriate place would be to include it in the super pom. Unfortunately I don't seem to be able to find it. Could you please direct me to where it is located. Thanks Lakshman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Super Pom
Hi Stephen, Thanks for your suggestion, I was coming to the same conclusion. What puzzled me was the manual Better Builds with Maven pg 24, where they refer to a Super POM that is implicitly inherited by all pom's. I guess this is buried deep in the maven code somewhere and not available for the end user. Could you please confirm my observation above, about the Super POM. Thanks Lakshman -Original Message- From: Stephen Duncan [mailto:[EMAIL PROTECTED] Sent: Thursday, 27 July 2006 10:38 AM To: Maven Users List Subject: Re: Super Pom You can choose to make a super-pom that all your projects inherit from to provide common configuration. - Stephen On 7/26/06, Lakshman Srilakshmanan [EMAIL PROTECTED] wrote: Hi Emmanuel, Thanks for your reply. The http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html describes how to include a customised checkstyle within a POM. I need to know the location of the super POM itself, if one exists. Thanks Lakshman -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, 26 July 2006 5:28 PM To: Maven Users List Subject: Re: Super Pom http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html Lakshman Srilakshmanan a écrit : Hi All, I have used maven 1.x for a couple of years now and am in the process of migrating to maven 2.x I need to set some configuration globally (eg customised checkstyle). I find the appropriate place would be to include it in the super pom. Unfortunately I don't seem to be able to find it. Could you please direct me to where it is located. Thanks Lakshman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Super Pom
Thanks Stephen, Sending to maven users list for future reference. Thanks Lakshman -Original Message- From: Stephen Duncan [mailto:[EMAIL PROTECTED] Sent: Friday, 28 July 2006 12:09 PM To: Lakshman Srilakshmanan Subject: Re: Super Pom Yes. That Super POM is basically a set of default values built in to Maven (from my understanding). This includes things like a profile activated by performRelease=true that includes the javadoc:jar and source:jar goals at package time, etc. - Stephen On 7/27/06, Lakshman Srilakshmanan [EMAIL PROTECTED] wrote: Hi Stephen, Thanks for your suggestion, I was coming to the same conclusion. What puzzled me was the manual Better Builds with Maven pg 24, where they refer to a Super POM that is implicitly inherited by all pom's. I guess this is buried deep in the maven code somewhere and not available for the end user. Could you please confirm my observation above, about the Super POM. Thanks Lakshman -Original Message- From: Stephen Duncan [mailto:[EMAIL PROTECTED] Sent: Thursday, 27 July 2006 10:38 AM To: Maven Users List Subject: Re: Super Pom You can choose to make a super-pom that all your projects inherit from to provide common configuration. - Stephen On 7/26/06, Lakshman Srilakshmanan [EMAIL PROTECTED] wrote: Hi Emmanuel, Thanks for your reply. The http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html describes how to include a customised checkstyle within a POM. I need to know the location of the super POM itself, if one exists. Thanks Lakshman -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, 26 July 2006 5:28 PM To: Maven Users List Subject: Re: Super Pom http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html Lakshman Srilakshmanan a écrit : Hi All, I have used maven 1.x for a couple of years now and am in the process of migrating to maven 2.x I need to set some configuration globally (eg customised checkstyle). I find the appropriate place would be to include it in the super pom. Unfortunately I don't seem to be able to find it. Could you please direct me to where it is located. Thanks Lakshman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Super Pom
Dear all, For maven2, the child POM will inherit all properties from parent pom. thanks. Tel: (020)36315358-328 Fax: (020)36315170 Lakshman Srilakshmanan [EMAIL PROTECTED]To: Maven Users List users@maven.apache.org ost.com.au cc: Subject: RE: Super Pom 28/07/2006 10:12 Please respond to Maven Users List Thanks Stephen, Sending to maven users list for future reference. Thanks Lakshman -Original Message- From: Stephen Duncan [mailto:[EMAIL PROTECTED] Sent: Friday, 28 July 2006 12:09 PM To: Lakshman Srilakshmanan Subject: Re: Super Pom Yes. That Super POM is basically a set of default values built in to Maven (from my understanding). This includes things like a profile activated by performRelease=true that includes the javadoc:jar and source:jar goals at package time, etc. - Stephen On 7/27/06, Lakshman Srilakshmanan [EMAIL PROTECTED] wrote: Hi Stephen, Thanks for your suggestion, I was coming to the same conclusion. What puzzled me was the manual Better Builds with Maven pg 24, where they refer to a Super POM that is implicitly inherited by all pom's. I guess this is buried deep in the maven code somewhere and not available for the end user. Could you please confirm my observation above, about the Super POM. Thanks Lakshman -Original Message- From: Stephen Duncan [mailto:[EMAIL PROTECTED] Sent: Thursday, 27 July 2006 10:38 AM To: Maven Users List Subject: Re: Super Pom You can choose to make a super-pom that all your projects inherit from to provide common configuration. - Stephen On 7/26/06, Lakshman Srilakshmanan [EMAIL PROTECTED] wrote: Hi Emmanuel, Thanks for your reply. The http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html describes how to include a customised checkstyle within a POM. I need to know the location of the super POM itself, if one exists. Thanks Lakshman -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, 26 July 2006 5:28 PM To: Maven Users List Subject: Re: Super Pom http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html Lakshman Srilakshmanan a écrit : Hi All, I have used maven 1.x for a couple of years now and am in the process of migrating to maven 2.x I need to set some configuration globally (eg customised checkstyle). I find the appropriate place would be to include it in the super pom. Unfortunately I don't seem to be able to find it. Could you please direct me to where it is located. Thanks Lakshman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com
Super Pom
Hi All, I have used maven 1.x for a couple of years now and am in the process of migrating to maven 2.x I need to set some configuration globally (eg customised checkstyle). I find the appropriate place would be to include it in the super pom. Unfortunately I don't seem to be able to find it. Could you please direct me to where it is located. Thanks Lakshman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super Pom
http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html Lakshman Srilakshmanan a écrit : Hi All, I have used maven 1.x for a couple of years now and am in the process of migrating to maven 2.x I need to set some configuration globally (eg customised checkstyle). I find the appropriate place would be to include it in the super pom. Unfortunately I don't seem to be able to find it. Could you please direct me to where it is located. Thanks Lakshman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Super Pom
Hi Emmanuel, Thanks for your reply. The http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html describes how to include a customised checkstyle within a POM. I need to know the location of the super POM itself, if one exists. Thanks Lakshman -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, 26 July 2006 5:28 PM To: Maven Users List Subject: Re: Super Pom http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html Lakshman Srilakshmanan a écrit : Hi All, I have used maven 1.x for a couple of years now and am in the process of migrating to maven 2.x I need to set some configuration globally (eg customised checkstyle). I find the appropriate place would be to include it in the super pom. Unfortunately I don't seem to be able to find it. Could you please direct me to where it is located. Thanks Lakshman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super Pom
You can choose to make a super-pom that all your projects inherit from to provide common configuration. - Stephen On 7/26/06, Lakshman Srilakshmanan [EMAIL PROTECTED] wrote: Hi Emmanuel, Thanks for your reply. The http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html describes how to include a customised checkstyle within a POM. I need to know the location of the super POM itself, if one exists. Thanks Lakshman -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, 26 July 2006 5:28 PM To: Maven Users List Subject: Re: Super Pom http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html Lakshman Srilakshmanan a écrit : Hi All, I have used maven 1.x for a couple of years now and am in the process of migrating to maven 2.x I need to set some configuration globally (eg customised checkstyle). I find the appropriate place would be to include it in the super pom. Unfortunately I don't seem to be able to find it. Could you please direct me to where it is located. Thanks Lakshman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Super POM
Hi All, I'm new to Maven and am struggling to create a super pom. I am involved in a project which has a number of sub projects and would like to have a super pom for the general configs, which are inherited by the sub projects. The problem is that I can create a super pom by hand, but when I reference it using parent/ the sub project goes of to the repo to download... I just wanted a super pom that I could use to set project wide configs. I tried various params with mvn archetype:create but no luck. Could someone please point me in the right direction. Many thanks in advance. -- Viz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM
sorry, in the local repo it's mvn install for a remote repo it's mvn deploy Arnaud On 7/10/06, Arnaud HERITIER [EMAIL PROTECTED] wrote: The parent POM must be deployed in your local repository to allow yours subprojects to find it. You just have to do : mvn deploy in the superPOM directory Arnaud On 7/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi All, I'm new to Maven and am struggling to create a super pom. I am involved in a project which has a number of sub projects and would like to have a super pom for the general configs, which are inherited by the sub projects. The problem is that I can create a super pom by hand, but when I reference it using parent/ the sub project goes of to the repo to download... I just wanted a super pom that I could use to set project wide configs. I tried various params with mvn archetype:create but no luck. Could someone please point me in the right direction. Many thanks in advance. -- Viz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM
Viz Heres one I have setup... ?xml version=1.0 encoding=UTF-8? project 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/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.company/groupId artifactIdcompany/artifactId version1/version packagingpom/packaging nameNexus Alpha Ltd/name description /description organization nameCompany Name/name urlhttp://www.company.com//url /organization urlhttp://www.company.com//url distributionManagement repository idinternal-released/id urlscp://192.168.6.194/var/mvn/internal-released/url /repository snapshotRepository idinternal-snapshot/id urlscp://192.168.6.194/var/mvn/internal-snapshot/url /snapshotRepository /distributionManagement /project Now I have release this to my internal repo, but i guess you could just install it to your local repo. Also you could have a project that has modules. like the following dir structure myproject myproject/pom.xml myproject/module1/pom.xml myproject/module2/pom.xml the top level pom would contain your global settings and the modules element modules modulemodule1/module modulemodule2/module /modules Im still new to maven 2 also but i hope this gives you some ideas. Ben On 7/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi All, I'm new to Maven and am struggling to create a super pom. I am involved in a project which has a number of sub projects and would like to have a super pom for the general configs, which are inherited by the sub projects. The problem is that I can create a super pom by hand, but when I reference it using parent/ the sub project goes of to the repo to download... I just wanted a super pom that I could use to set project wide configs. I tried various params with mvn archetype:create but no luck. Could someone please point me in the right direction. Many thanks in advance. -- Viz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Super POM
Hi Arnuad, When I create the new project for the super pom what archetypeArtefactId should I use? Kind regards, -- Viz -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: 10 July 2006 14:12 To: Maven Users List Subject: Re: Super POM sorry, in the local repo it's mvn install for a remote repo it's mvn deploy Arnaud On 7/10/06, Arnaud HERITIER [EMAIL PROTECTED] wrote: The parent POM must be deployed in your local repository to allow yours subprojects to find it. You just have to do : mvn deploy in the superPOM directory Arnaud On 7/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi All, I'm new to Maven and am struggling to create a super pom. I am involved in a project which has a number of sub projects and would like to have a super pom for the general configs, which are inherited by the sub projects. The problem is that I can create a super pom by hand, but when I reference it using parent/ the sub project goes of to the repo to download... I just wanted a super pom that I could use to set project wide configs. I tried various params with mvn archetype:create but no luck. Could someone please point me in the right direction. Many thanks in advance. -- Viz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM
I built (myslef) 2.1 yesterday and relativePath is not working. So is this bug only commited to 2.0.5 branch? On 7/10/06, Carsten Karkola [EMAIL PROTECTED] wrote: There was a Bug that is fixed in 2.0.5 (I'm waiting for the public release, to try it out :-) ): http://jira.codehaus.org/browse/MNG-2308 The super-Pom should also be found vi parent-entries if it is one dir up or the relativePath entry is specified. regards, carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Super POM
Hey Everyone, Done it - Really appreaciate the help! Kind regards, -- Viz -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ben short Sent: 10 July 2006 14:19 To: Maven Users List Subject: Re: Super POM Viz Heres one I have setup... ?xml version=1.0 encoding=UTF-8? project 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/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.company/groupId artifactIdcompany/artifactId version1/version packagingpom/packaging nameNexus Alpha Ltd/name description /description organization nameCompany Name/name urlhttp://www.company.com//url /organization urlhttp://www.company.com//url distributionManagement repository idinternal-released/id urlscp://192.168.6.194/var/mvn/internal-released/url /repository snapshotRepository idinternal-snapshot/id urlscp://192.168.6.194/var/mvn/internal-snapshot/url /snapshotRepository /distributionManagement /project Now I have release this to my internal repo, but i guess you could just install it to your local repo. Also you could have a project that has modules. like the following dir structure myproject myproject/pom.xml myproject/module1/pom.xml myproject/module2/pom.xml the top level pom would contain your global settings and the modules element modules modulemodule1/module modulemodule2/module /modules Im still new to maven 2 also but i hope this gives you some ideas. Ben On 7/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi All, I'm new to Maven and am struggling to create a super pom. I am involved in a project which has a number of sub projects and would like to have a super pom for the general configs, which are inherited by the sub projects. The problem is that I can create a super pom by hand, but when I reference it using parent/ the sub project goes of to the repo to download... I just wanted a super pom that I could use to set project wide configs. I tried various params with mvn archetype:create but no luck. Could someone please point me in the right direction. Many thanks in advance. -- Viz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Super POM
No problem... Are these two configured/setup/located differently? -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: 10 July 2006 17:12 To: Maven Users List Subject: Re: Super POM Also, as an aside (sorry, I'm a stickler for correct terms!), there is a difference between a super POM and a parent POM. The SuperPOM is the global default for the whole Maven POM structure, and conceptually, the POM from which all POMs inherit. A parent is just any POM that is interited from. Eric On 7/10/06, Marc L. Veary [EMAIL PROTECTED] wrote: Hey Everyone, Done it - Really appreaciate the help! Kind regards, -- Viz -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ben short Sent: 10 July 2006 14:19 To: Maven Users List Subject: Re: Super POM Viz Heres one I have setup... ?xml version=1.0 encoding=UTF-8? project 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/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.company/groupId artifactIdcompany/artifactId version1/version packagingpom/packaging nameNexus Alpha Ltd/name description /description organization nameCompany Name/name urlhttp://www.company.com//url /organization urlhttp://www.company.com//url distributionManagement repository idinternal-released/id urlscp://192.168.6.194/var/mvn/internal-released/url /repository snapshotRepository idinternal-snapshot/id urlscp://192.168.6.194/var/mvn/internal-snapshot/url /snapshotRepository /distributionManagement /project Now I have release this to my internal repo, but i guess you could just install it to your local repo. Also you could have a project that has modules. like the following dir structure myproject myproject/pom.xml myproject/module1/pom.xml myproject/module2/pom.xml the top level pom would contain your global settings and the modules element modules modulemodule1/module modulemodule2/module /modules Im still new to maven 2 also but i hope this gives you some ideas. Ben On 7/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi All, I'm new to Maven and am struggling to create a super pom. I am involved in a project which has a number of sub projects and would like to have a super pom for the general configs, which are inherited by the sub projects. The problem is that I can create a super pom by hand, but when I reference it using parent/ the sub project goes of to the repo to download... I just wanted a super pom that I could use to set project wide configs. I tried various params with mvn archetype:create but no luck. Could someone please point me in the right direction. Many thanks in advance. -- Viz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM
The super POM is internal to Maven. I honestly don't know for certain if the superPOM is a seperate file, or a conceptual thing, but I believe it is the former, and this is probably it: http://svn.apache.org/repos/asf/maven/components/trunk/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml Eric On 7/10/06, Marc L. Veary [EMAIL PROTECTED] wrote: No problem... Are these two configured/setup/located differently? -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: 10 July 2006 17:12 To: Maven Users List Subject: Re: Super POM Also, as an aside (sorry, I'm a stickler for correct terms!), there is a difference between a super POM and a parent POM. The SuperPOM is the global default for the whole Maven POM structure, and conceptually, the POM from which all POMs inherit. A parent is just any POM that is interited from. Eric On 7/10/06, Marc L. Veary [EMAIL PROTECTED] wrote: Hey Everyone, Done it - Really appreaciate the help! Kind regards, -- Viz -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ben short Sent: 10 July 2006 14:19 To: Maven Users List Subject: Re: Super POM Viz Heres one I have setup... ?xml version=1.0 encoding=UTF-8? project 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/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.company/groupId artifactIdcompany/artifactId version1/version packagingpom/packaging nameNexus Alpha Ltd/name description /description organization nameCompany Name/name urlhttp://www.company.com//url /organization urlhttp://www.company.com//url distributionManagement repository idinternal-released/id urlscp://192.168.6.194/var/mvn/internal-released/url /repository snapshotRepository idinternal-snapshot/id urlscp://192.168.6.194/var/mvn/internal-snapshot/url /snapshotRepository /distributionManagement /project Now I have release this to my internal repo, but i guess you could just install it to your local repo. Also you could have a project that has modules. like the following dir structure myproject myproject/pom.xml myproject/module1/pom.xml myproject/module2/pom.xml the top level pom would contain your global settings and the modules element modules modulemodule1/module modulemodule2/module /modules Im still new to maven 2 also but i hope this gives you some ideas. Ben On 7/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi All, I'm new to Maven and am struggling to create a super pom. I am involved in a project which has a number of sub projects and would like to have a super pom for the general configs, which are inherited by the sub projects. The problem is that I can create a super pom by hand, but when I reference it using parent/ the sub project goes of to the repo to download... I just wanted a super pom that I could use to set project wide configs. I tried various params with mvn archetype:create but no luck. Could someone please point me in the right direction. Many thanks in advance. -- Viz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to implement an organisational super pom ?
Here is a god example of a organisational super pom http://maven.sateh.com/repository/org/apache/apache/2/ I have created one for my compnay that contains the following... distributionManagement repository idinternal-released/id urlscp://192.168.6.194/var/mvn/internal-released/url /repository snapshotRepository idinternal-snapshot/id urlscp://192.168.6.194/var/mvn/internal-snapshot/url /snapshotRepository /distributionManagement Although each developer has to have the login details, for the repos, in thier settings.xml. But so far its working fine. Ben On 6/22/06, Alexandre Poitras [EMAIL PROTECTED] wrote: You confuse multi-modules project and super pom. A super pom doesn't need to declare any modules. It is an independant project which has its own version and distributed in your internal repository so that any project can download whenever it needs it. It should fix your problems. On 6/20/06, Dhananjay Nene [EMAIL PROTECTED] wrote: Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. Having said that since maven itself does use a super pom which does not suffer from these limitations hopefully there's some way to implement - but I couldn't figure it out so far. Dhananjay Roald Bankras wrote: Nathan What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Beyer,Nathan [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 12:29 AM To: Maven Users List Subject: RE: How to implement an organisational super pom ? From my adventures in trying to do this, I've found that it's just not a good idea in the current state of things. There are some things that can be done with dependencyManagement and pluginManagement, but that only goes so far. My suggestion is to standardize things via archetypes to generate POMs in a certain fashion. For common automated build stuff use profile settings for the build user. -Nathan -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 1:34 PM To: Maven Users List Subject: How to implement an organisational super pom ? I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
Re: How to implement an organisational super pom ?
Dhananjay Nene wrote: Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. You don't need to have your super-pom in cvs. Use a versioning number scheme for the pom like this 1, 2, 3.. i.e. incremental numbers. Install each new version of the pom into your company Maven repository. That way you have copies of the released versions of your super-pom in your Maven repo. snip -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to implement an organisational super pom ?
You confuse multi-modules project and super pom. A super pom doesn't need to declare any modules. It is an independant project which has its own version and distributed in your internal repository so that any project can download whenever it needs it. It should fix your problems. On 6/20/06, Dhananjay Nene [EMAIL PROTECTED] wrote: Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. Having said that since maven itself does use a super pom which does not suffer from these limitations hopefully there's some way to implement - but I couldn't figure it out so far. Dhananjay Roald Bankras wrote: Nathan What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Beyer,Nathan [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 12:29 AM To: Maven Users List Subject: RE: How to implement an organisational super pom ? From my adventures in trying to do this, I've found that it's just not a good idea in the current state of things. There are some things that can be done with dependencyManagement and pluginManagement, but that only goes so far. My suggestion is to standardize things via archetypes to generate POMs in a certain fashion. For common automated build stuff use profile settings for the build user. -Nathan -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 1:34 PM To: Maven Users List Subject: How to implement an organisational super pom ? I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to implement an organisational super pom ?
Nathan What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Beyer,Nathan [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 12:29 AM To: Maven Users List Subject: RE: How to implement an organisational super pom ? From my adventures in trying to do this, I've found that it's just not a good idea in the current state of things. There are some things that can be done with dependencyManagement and pluginManagement, but that only goes so far. My suggestion is to standardize things via archetypes to generate POMs in a certain fashion. For common automated build stuff use profile settings for the build user. -Nathan -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 1:34 PM To: Maven Users List Subject: How to implement an organisational super pom ? I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.0/368 - Release Date: 6/16/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.0/368 - Release Date: 6/16/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to implement an organisational super pom ?
Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. Having said that since maven itself does use a super pom which does not suffer from these limitations hopefully there's some way to implement - but I couldn't figure it out so far. Dhananjay Roald Bankras wrote: Nathan What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Beyer,Nathan [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 12:29 AM To: Maven Users List Subject: RE: How to implement an organisational super pom ? From my adventures in trying to do this, I've found that it's just not a good idea in the current state of things. There are some things that can be done with dependencyManagement and pluginManagement, but that only goes so far. My suggestion is to standardize things via archetypes to generate POMs in a certain fashion. For common automated build stuff use profile settings for the build user. -Nathan -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 1:34 PM To: Maven Users List Subject: How to implement an organisational super pom ? I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to implement an organisational super pom ?
- The release plugin issue, sounds to me like a bug. - For SCM I think that you can just override the scm configuration for the project. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 10:40 AM To: Maven Users List Subject: Re: How to implement an organisational super pom ? Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. Having said that since maven itself does use a super pom which does not suffer from these limitations hopefully there's some way to implement - but I couldn't figure it out so far. Dhananjay Roald Bankras wrote: Nathan What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Beyer,Nathan [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 12:29 AM To: Maven Users List Subject: RE: How to implement an organisational super pom ? From my adventures in trying to do this, I've found that it's just not a good idea in the current state of things. There are some things that can be done with dependencyManagement and pluginManagement, but that only goes so far. My suggestion is to standardize things via archetypes to generate POMs in a certain fashion. For common automated build stuff use profile settings for the build user. -Nathan -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 1:34 PM To: Maven Users List Subject: How to implement an organisational super pom ? I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.1/369 - Release Date: 6/19/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.1/369 - Release Date: 6/19/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to implement an organisational super pom ?
You can override any configuraion you want, version or anything. We use parent poms all the time with no problems at all On 6/20/06, Dhananjay Nene [EMAIL PROTECTED] wrote: Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. Having said that since maven itself does use a super pom which does not suffer from these limitations hopefully there's some way to implement - but I couldn't figure it out so far. Dhananjay Roald Bankras wrote: Nathan What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Beyer,Nathan [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 12:29 AM To: Maven Users List Subject: RE: How to implement an organisational super pom ? From my adventures in trying to do this, I've found that it's just not a good idea in the current state of things. There are some things that can be done with dependencyManagement and pluginManagement, but that only goes so far. My suggestion is to standardize things via archetypes to generate POMs in a certain fashion. For common automated build stuff use profile settings for the build user. -Nathan -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 1:34 PM To: Maven Users List Subject: How to implement an organisational super pom ? I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to implement an organisational super pom ?
What factors/bases should be taken into account when thinking to create super POM or not? Create parent - child model or not, especially if the components also used in another different projects? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sanchez Sent: Tuesday, June 20, 2006 3:18 PM To: Maven Users List Subject: Re: How to implement an organisational super pom ? You can override any configuraion you want, version or anything. We use parent poms all the time with no problems at all On 6/20/06, Dhananjay Nene [EMAIL PROTECTED] wrote: Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. Having said that since maven itself does use a super pom which does not suffer from these limitations hopefully there's some way to implement - but I couldn't figure it out so far. Dhananjay Roald Bankras wrote: Nathan What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Beyer,Nathan [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 12:29 AM To: Maven Users List Subject: RE: How to implement an organisational super pom ? From my adventures in trying to do this, I've found that it's just not a good idea in the current state of things. There are some things that can be done with dependencyManagement and pluginManagement, but that only goes so far. My suggestion is to standardize things via archetypes to generate POMs in a certain fashion. For common automated build stuff use profile settings for the build user. -Nathan -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 1:34 PM To: Maven Users List Subject: How to implement an organisational super pom ? I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL
How to implement an organisational super pom ?
I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to implement an organisational super pom ?
From my adventures in trying to do this, I've found that it's just not a good idea in the current state of things. There are some things that can be done with dependencyManagement and pluginManagement, but that only goes so far. My suggestion is to standardize things via archetypes to generate POMs in a certain fashion. For common automated build stuff use profile settings for the build user. -Nathan -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 1:34 PM To: Maven Users List Subject: How to implement an organisational super pom ? I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent vs. Multi Project super pom
Hi Kenney, 2006/6/13, Kenney Westerhof [EMAIL PROTECTED]: On Mon, 12 Jun 2006, Stephen Duncan wrote: Hi, I'd thought I'd throw in a pair of $0.01.. Using the aggregating POM as the parent pom implies that the projects are structured in a directory structure matching the child-parent relationship. That means that the child-parent relationship is the inverse of the parent-module relationship. A simple sample is the grouping of a set of plugins. Since they're siblings in the directory structure, the parent pom can easily serve as the parent pom, defining all things common to plugins. ...the parent pom can easily serve as the parent pom... ;-) Isn't there any more precise wording? But like you, I've also found that this sometimes gives problems, since there's no multiple inheritance. In my case it was when working on a project that consists of two applications, both EARs each containing a WAR using the same web framework (and thus sharing some settings and dependencies). The modules were grouped by application, and using the parent-as-aggregator there's no way to let both WAR projects have the same settings if they're not siblings in the directory structure. There's also some common POM configuration for the two applications (for instance the groupId's). Another advantage, more of convenience, of differ between parent and aggregating pom: you can have the parent pom at the same level as it's inherited poms. Thus in Eclipse I can edit at least the parent pom easily, since I can import it as a Eclipse project. This is not true for the aggregating pom, though. But since typically the parent pom is more often edited than the aggregating pom, this is fine by me. Basically, there are too many relations to fit into a tree (it becomes a graph), and you just have to pick the one that makes the most sense. In my experience, it's convenient to have the parent pom as an aggregator so your project tree is actually a tree. OK, understood. (But with the lack of not beeing able to edit the parent pom easily inside Eclipse.) On a side note, there are some plugins, like the site plugin, that currently kind of expect the parent-module relationship to be bidirectional (meaning modules must specify the aggregator as their parent). The behaviour of this plugin depends on whether it's run in reactor-mode or not, and when the modules define different parents, you get unexpected results. But this is being addressed. See, it's the implicit assumptions, that make me scratch my head. -- Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent vs. Multi Project super pom
Hi Stephen,
2006/6/13, Stephen Duncan [EMAIL PROTECTED]:
I personally do more as you do.
I have team-wide super-POMs I have a primary one that has basic
url, issue management, etc. type settings. Then I have a core POM
with common dependencyManagment section to encourage use of the same
versions of Jar's to prevent incompatibilities, as well as common
reporting configuration. Then I have a webapp parent POM that
specifically states the provided dependencies for webapps to be
deployed to our target server, as well as webapp specific stuff, such
as setting finalName${project.artifactId}/finalName to remove the
version number from wars, and wtpVersion1.0/wtpVersion for the
Eclipse plugin.
Right Stephen, that's the kind of pom inheritance, which I quite like
about Maven. It gives me the chance to encourage reliable and
maintenable project configurations throughout the company.
-- Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent vs. Multi Project super pom
On 6/13/06, Stefan Hübner [EMAIL PROTECTED] wrote: Hi Kenney, 2006/6/13, Kenney Westerhof [EMAIL PROTECTED]: On Mon, 12 Jun 2006, Stephen Duncan wrote: Another advantage, more of convenience, of differ between parent and aggregating pom: you can have the parent pom at the same level as it's inherited poms. Thus in Eclipse I can edit at least the parent pom easily, since I can import it as a Eclipse project. This is not true for the aggregating pom, though. But since typically the parent pom is more often edited than the aggregating pom, this is fine by me. -- Stefan Note: With Eclipse 3.2, you can have overlapping projects, so it is possible to edit the aggregating pom that lives a directory above the modules. -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Parent vs. Multi Project super pom
Hi all, this is kind of a best-practise-question about your habbits of using the concepts of multi-project-super-pom. First of all, are there distinctive terms commonly agreed upon for each of those concepts? Second, those two ways of using POMs appear to me to be orthogonal to each other, really. Parent POMs are used to define common characterisitics for a group of projects. Multi Project POMs on the other hand aggregate modules belonging to a greater project. I usually have the habbit of defining two diffent poms for multiproject situations. e.g.: /multiproject-pom X -parent-pom Y -module A / pom A (parent pom: Y) -module B / pom B (parent pom: Y) In most examples found though (e.g. in maven's own sources themselfs) typically multi project poms at the same time are used as parent poms for those modules they aggregated. So, what I can't get my head around yet is, is it just a matter of habbit or taste to combine those two usages in just one POM? or am I really missing something important here, if I define two distinctive POMs the way described above. I'm thinking about this for quite a while now and any clarification would be much appreciated. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent vs. Multi Project super pom
I personally do more as you do.
I have team-wide super-POMs I have a primary one that has basic
url, issue management, etc. type settings. Then I have a core POM
with common dependencyManagment section to encourage use of the same
versions of Jar's to prevent incompatibilities, as well as common
reporting configuration. Then I have a webapp parent POM that
specifically states the provided dependencies for webapps to be
deployed to our target server, as well as webapp specific stuff, such
as setting finalName${project.artifactId}/finalName to remove the
version number from wars, and wtpVersion1.0/wtpVersion for the
Eclipse plugin.
For multi-module project, I have an aggregating POM that defines the
modules, but each module uses the appropriate super-POM as its
parent, not the aggregating POM.
I've found this to work better for us. But I too have been wondering
what the reasoning for the pattern of using the aggregating POM also
as the parent POM is...
-Stephen
On 6/12/06, Stefan Hübner [EMAIL PROTECTED] wrote:
Hi all,
this is kind of a best-practise-question about your habbits of using
the concepts of multi-project-super-pom.
First of all, are there distinctive terms commonly agreed upon for
each of those concepts?
Second, those two ways of using POMs appear to me to be orthogonal to
each other, really. Parent POMs are used to define common
characterisitics for a group of projects. Multi Project POMs on the
other hand aggregate modules belonging to a greater project. I usually
have the habbit of defining two diffent poms for multiproject
situations. e.g.:
/multiproject-pom X
-parent-pom Y
-module A / pom A (parent pom: Y)
-module B / pom B (parent pom: Y)
In most examples found though (e.g. in maven's own sources themselfs)
typically multi project poms at the same time are used as parent poms
for those modules they aggregated.
So, what I can't get my head around yet is, is it just a matter of
habbit or taste to combine those two usages in just one POM? or am I
really missing something important here, if I define two distinctive
POMs the way described above.
I'm thinking about this for quite a while now and any clarification
would be much appreciated.
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen Duncan Jr
www.stephenduncanjr.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent vs. Multi Project super pom
On Mon, 12 Jun 2006, Stephen Duncan wrote:
Hi,
I'd thought I'd throw in a pair of $0.01..
Using the aggregating POM as the parent pom implies that the projects
are structured in a directory structure matching the child-parent
relationship. That means that the child-parent relationship is the
inverse of the parent-module relationship.
A simple sample is the grouping of a set of plugins. Since they're
siblings in the directory structure, the parent pom can easily serve as
the parent pom, defining all things common to plugins.
But like you, I've also found that this sometimes gives problems,
since there's no multiple inheritance. In my case it was when working on a
project that consists of two applications, both EARs each containing a WAR
using the same web framework (and thus sharing some settings and
dependencies). The modules were grouped by application, and using the
parent-as-aggregator there's no way to let both WAR projects have the same
settings if they're not siblings in the directory structure. There's also
some common POM configuration for the two applications (for instance the
groupId's).
Basically, there are too many relations to fit into a tree (it becomes a
graph), and you just have to pick the one that makes the most sense.
In my experience, it's convenient to have the parent pom
as an aggregator so your project tree is actually a tree.
On a side note, there are some plugins, like the site plugin, that
currently kind of expect the parent-module relationship to be
bidirectional (meaning modules must specify the aggregator as their parent).
The behaviour of this plugin depends on whether it's run in reactor-mode
or not, and when the modules define different parents, you get unexpected
results. But this is being addressed.
-- Kenney
I personally do more as you do.
I have team-wide super-POMs I have a primary one that has basic
url, issue management, etc. type settings. Then I have a core POM
with common dependencyManagment section to encourage use of the same
versions of Jar's to prevent incompatibilities, as well as common
reporting configuration. Then I have a webapp parent POM that
specifically states the provided dependencies for webapps to be
deployed to our target server, as well as webapp specific stuff, such
as setting finalName${project.artifactId}/finalName to remove the
version number from wars, and wtpVersion1.0/wtpVersion for the
Eclipse plugin.
For multi-module project, I have an aggregating POM that defines the
modules, but each module uses the appropriate super-POM as its
parent, not the aggregating POM.
I've found this to work better for us. But I too have been wondering
what the reasoning for the pattern of using the aggregating POM also
as the parent POM is...
-Stephen
On 6/12/06, Stefan Hübner [EMAIL PROTECTED] wrote:
Hi all,
this is kind of a best-practise-question about your habbits of using
the concepts of multi-project-super-pom.
First of all, are there distinctive terms commonly agreed upon for
each of those concepts?
Second, those two ways of using POMs appear to me to be orthogonal to
each other, really. Parent POMs are used to define common
characterisitics for a group of projects. Multi Project POMs on the
other hand aggregate modules belonging to a greater project. I usually
have the habbit of defining two diffent poms for multiproject
situations. e.g.:
/multiproject-pom X
-parent-pom Y
-module A / pom A (parent pom: Y)
-module B / pom B (parent pom: Y)
In most examples found though (e.g. in maven's own sources themselfs)
typically multi project poms at the same time are used as parent poms
for those modules they aggregated.
So, what I can't get my head around yet is, is it just a matter of
habbit or taste to combine those two usages in just one POM? or am I
really missing something important here, if I define two distinctive
POMs the way described above.
I'm thinking about this for quite a while now and any clarification
would be much appreciated.
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen Duncan Jr
www.stephenduncanjr.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
