release plugin doesnt update parent pom

Hi Consider a multi-module project with a root pom.xml and this root pom has another parent pom.xml which is considered as separated project parent groupIdcom.foo.core/groupId artifactIdcore-parent/artifactId version0.0.2-SNAPSHOT/version /parent when executing

Re: AW: release plugin doesnt update parent pom

behaviour would be to fail with a 'cannot release with a SNAPSHOT dependency' exception in your case. You can easily work around this issue if you manually release the parent pom first. LieGrue, strub --- is_maximum mnr...@gmail.com schrieb am Sa, 26.12.2009: Von: is_maximum mnr

Re: AW: release plugin doesnt update parent pom

? This definitely works and is used e.g. by JBoss folks for their 'version-matrix' (see e.g. the weld build). LieGrue, strub --- is_maximum mnr...@gmail.com schrieb am Sa, 26.12.2009: Von: is_maximum mnr...@gmail.com Betreff: Re: AW: release plugin doesnt update parent pom An: users

Re: problem regarding maven release plugin

Dan Tran wrote: Release plugin cannot proceed with snapshot dependencies including build plugin. The main rational is it want to guarantee the release code is producible. Note snapshots can go away any time and it can have behaviors changed any time. -D Yes that's right but this

problem regarding maven release plugin

Hi We are using Maven release plugin version 2 beta 9 1 - We've got some problem in releasing our applications. There are a bunch of projects defined in our company and each is being developed by a team. Because we are in developing phase for some dependencies we use SNAPSHOT versions and we

need a new feature in maven profiles

Hi When you define a profile and need to exclude some resource files and you have a multi-module application it is very hard and untidy you define that profile in each module. If we were able to define that profile in parent pom.xml it was really nice but the problem is currently when you

possible bug in maven release plugin

Hi I am using maven release plugin version 2.0 beta 9 this plugin works just fine with Subversion but after executing release:perform all the svn metadata will be removed or maybe corrupted and the project no longer will be updated from svn Is this a bug? do I have to report an issue? - --

Re: deploy with different version and group id

Any idea? - -- Regards Mohammad Norouzi Help each other to reach the future faster http://pixelshot.wordpress.com Pixelshot Photoblog http://brainable.blogspot.com Brainable Blog -- View this message in context:

maven profile doesn't work when packaging is jar

Hi I am using maven v2.0.9. In my project I have 3 modules including a web module. in web module the profiles work just fine and I can change the resources directory but in another module from which a jar file is produced the profiles doesn't work and the default resources directory will be

deploy with different version and group id

Hi We have defined some profiles for different platforms and app servers. A profile namely 'release' is created to deploy the modules of our project in different groupId and version. We need different groupId because there are a bunch of large scale projects are developing in our company by

deploying JAR file using the pom.xml inside the JAR

Hi the process of installing libraries in a repository is really time consuming. consider you are in a company in which internet is accessible through a remote desktop connection and you can't connect to maven repository directly, you can doanload the OpenEjb with toiling and then you want to

Re: deploying JAR file using the pom.xml inside the JAR

David Blevins wrote: On Oct 21, 2008, at 5:38 AM, David Blevins wrote: Just read this email a little closer and realized you are talking about an offline scenario where all you have is an openejb zip file. Yea, in that scenario it would be nice if maven had an easy way to put