Re: Reducing SNAPSHOT redundancy

How many build plans do you have? If I understood correctly single plan for all modules (perhaps on aggregate pom). Even small change in one module rebuilds all modules :-( Let's consider to define one build plan for each module. In addition define dependencies between build plans to reflect

Re: Which is the BEST Approach to define Global POM.XML

I hope this example helps: http://code.google.com/p/m4enterprise/source/browse/trunk/corporate-pom/pom.xml Marcin On 14 March 2012 21:29, Daivish Shah daivish.s...@gmail.com wrote: Hi Maven Team, I am trying to find out what is the best way to define company specific GLOBAL POM.XML. Which

Non-resolvable parent POM - Maven 3 ignores mirror specification in settings.xml (for site generation)

issue? And where: m-site-p or maven core? -- Marcin Kuthan Maven For Enterprise - http://code.google.com/p/m4enterprise/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h

Re: Site plugin not using properties from settings.xml in URLs

that there is no single method in the API to access properties, or m-site-p reads properties in non-standard way. -- Marcin Kuthan Maven For Enterprise - http://code.google.com/p/m4enterprise/ On 31 August 2011 19:01, Derek Lewis de...@lewisd.com wrote: Hello, The documentation there seems to indicate it's

Re: Automatic Update of Build Plugin Versions?

-pom.cleanVersion}/version /plugin The same concept can be used to customize plugins configuration (can be easily overwritten): properties !-- Automatically assign submodules the parent version (m-release-p) -- autoVersionSubmodulestrue/autoVersionSubmodules /properties -- Marcin Kuthan Maven

Re: Execution of plugin in child poms and not in current pom

the profile is enabled by default. -- Marcin Kuthan Maven For Enterprise - http://code.google.com/p/m4enterprise/ On 4 August 2011 15:47, Kreyßel, Conny conny.kreys...@inter-forum.de wrote: Hello, i try to create a company parent pom that defines the usage of the enforcer plugin with some handmade

Re: Should I use classifiers to differentiate between devel and production builds?

complete example, please look into http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-deploy/pom.xml Not ideal, but much better than profiles in the web application module. The deployment specific configuration is located in separate deploy module. -- Marcin Kuthan

NullKnownHostProvider class not found during site deployment

Hi, I could not configure site deployment with NullKnownHostProvider as known host provider. Class NullKnownHostProvider is not found :-( Actually NullKnownHostProvider class is bundled in the wagon-ssh-common library. The library is a transitive dependency of wagon-ssh which is declared as

Central repository is down ...

Hi, I checked from two different physical location. Central repo is not responding ... Does anyone could help? -- Marcin m4enterprise.googlecode.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional

Re: Central repository is down ...

Ok, it is working again :-) But I'm wondering what was the reason ... central repository availability is rather important in Maven infrastructure. Thanks, Marcin On 8 March 2011 15:23, Marcin Kuthan marcin.kut...@gmail.com wrote: Hi, I checked from two different physical location. Central

Re: Central repository is down ...

... Thanks, Marcin /Anders On Tue, Mar 8, 2011 at 15:31, Marcin Kuthan marcin.kut...@gmail.com wrote: Ok, it is working again :-) But I'm wondering what was the reason ... central repository availability is rather important in Maven infrastructure. Thanks, Marcin On 8 March 2011 15:23

Re: Continuous Delivery and Maven

Hi, On 2 March 2011 16:25, epabst epa...@gmail.com wrote:Hi I've put a lot of thought into this because I'm working on designing continuous delivery with Maven, Hudson, and Nexus.  Our criteria is this: - We want to have continuous integration of stable versioned components. - We don't want

Re: Release plugin

On 25 February 2011 10:38, zoe slattery zoe.slatt...@gmail.com wrote: On 24/02/2011 18:49, Marcin Kuthan wrote: Hi If you need different version for API part it should be set up as separate project. In the API module you probably don't need inherit from myproject-parent. aggregate

Re: Release plugin

Hi If you need different version for API part it should be set up as separate project. In the API module you probably don't need inherit from myproject-parent. aggregate \_myproject-api \_myproject-impl \_myproject-subsystem1 \_myproject-subsystem2 \_myproject-parent You can release

Re: Site plugin - broken links between modules only on site stage

parameter directly, instead of going via distributionManagement.siteUrl, see http://maven.apache.org/plugins/maven-site-plugin/usage.html (Staging a site). HTH, -Lukas Marcin Kuthan wrote: Hi Lukas I don't think that my findings are related to MSITE-135. Only 2.3-SNAPSHOT is affected. You

Re: Site plugin - broken links between modules only on site stage

2.3-SNAPSHOT, some staging issues should be fixed with http://jira.codehaus.org/browse/MSITE-533. HTH, -Lukas Marcin Kuthan wrote: Hi My multi module project is structured with separate aggregate pom and parent pom (aggregate pom is not a parent pom). All modules are aggregated

Re: Site plugin - broken links between modules only on site stage

can attach a simple test project that would help, I haven't tried to fix this yet. -Lukas Marcin Kuthan wrote: Hi Lukas I'm sorry that I didn't specify versions in the first post. I tested my poms with version 2.2 (for Maven 2.2.1) and version 3.0-beta-3 (for Maven 3.0.2). In both cases

Site plugin - broken links between modules only on site stage

Hi My multi module project is structured with separate aggregate pom and parent pom (aggregate pom is not a parent pom). All modules are aggregated by aggragate pom (parent pom is also submodule of aggregate pom). All submodules inherit from parent pom. Aggregate pom:

Re: Maven3, ssh wagon - add wagon without modifying project pom.xml

Hi Brian You can add wagon-ssh libary to the M2_HOME/lib directory. I didn't test this configuration but it should work. Marcin On 27 January 2011 00:53, Brian Ferris bdfer...@gmail.com wrote: I discovered that with the upgrade to Maven 3, the ssh wagon is no longer included by default, which

Site deployment (scp) with NullKnownHostProvider fails on Maven3

Hi I'm working on corporate pom and I would keep common corporate pom version for Maven 2 and Maven 3. But I can't configure site deployment with scp wagon provider for Maven 2 and 3. To avoid interaction during scp deployment I configured server with NullKnownHostProvider in settings.xml.

Re: Site deployment (scp) with NullKnownHostProvider fails on Maven3

For m2, I'm not sure I understand you correctly, first you say it works, then you say it doesn't with the ssh extension (which you shouldn't need for scp). Maybe it's a version incompatibility, the current site plugin (m2) has a dependency on wagon-provider-api-1.0-beta-4. HTH, -Lukas Marcin

Re: One project per package or multiple packages in same project?

On 25 January 2011 19:23, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Tue, Jan 25, 2011 at 8:09 AM, Miguel Almeida migueldealme...@gmail.com wrote: I agree with you. I'm still quite new to advanced Maven topics so it still seems counter-intuitive to store the config file outside the

Re: metadata.versioning.release entry in maven-metadata.xml file is not updated by Maven 3

elements are not used at all. And release and versions elements are used incorrectly. Thanks, Marcin On 23 December 2010 12:06, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Marcin Kuthan wrote: http://code.google.com/p/m4enterprise/source/browse/snapshot-repository/com/googlecode

Re: metadata.versioning.release entry in maven-metadata.xml file is not updated by Maven 3

Thanks Benjamin. I will keep the artifacts in the repository for reference. Marcin On 23 December 2010 13:22, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Marcin Kuthan wrote: After 1.1 deployment latest release version has not been updated: http://code.google.com/p/m4enterprise

metadata.versioning.release entry in maven-metadata.xml file is not updated by Maven 3

Hi My assumption is that after artifact deployment into repository the maven-metadata.xml is updated. The metadata.versioning.release element should be updated to the latest deployed artifact version. The assumption is true for Maven 2.2.1 but not for 3.0.1. You can easily reproduce the issue

Re: metadata.versioning.release entry in maven-metadata.xml file is not updated by Maven 3

://m4enterprise.googlecode.com/svn/trunk/test1. Could you tell me where I can find the official reference for maven-metadata format? Has it been changed since Maven 2.x? Thanks, Marcin On 22 December 2010 16:59, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Marcin Kuthan wrote: You can easily

Re: How to avoid '/./' part of URL during site deployment?

it properly. On 2010-12-15 23:24, Marcin Kuthan wrote: I configured extension explicitly: extension        artifactIdwagon-webdav-jackrabbit/artifactId     groupIdorg.apache.maven.wagon/groupId     version1.0-beta-7/version /extension Exactly the same URL with '/./' and stack trace

Re: How to avoid '/./' part of URL during site deployment?

For further information please track the following issues: http://jira.codehaus.org/browse/MSITE-531 http://jira.codehaus.org/browse/MOJO-1611 On 16 December 2010 09:29, Marcin Kuthan marcin.kut...@gmail.com wrote: @Denis: I will create issues for both plugins (site and wagon) as you

How to avoid '/./' part of URL during site deployment?

Hi, I configured my project to use Wagon WebDAV provider to deploy project site. In general it works as I expected but it fails if the site is deployed on googlecode. Transfer error: org.apache.maven.wagon.TransferFailedException: Failed to transfer file:

How to avoid '/./' part of URL during site deployment?

Hi, I configured my project to use Wagon WebDAV provider to deploy project site. In general it works as I expected but it fails if the site is deployed on googlecode. Transfer error: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: