maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mathias Arens (JIRA)" <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MRELEASE-354) Versions defined in profiles are not updated
Date Thu, 11 Dec 2008 10:11:19 GMT

    [ http://jira.codehaus.org/browse/MRELEASE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157684#action_157684
] 

Mathias Arens edited comment on MRELEASE-354 at 12/11/08 4:10 AM:
------------------------------------------------------------------

I have exactly the same problem. My dependencies in a profile section are not updated as well.

In my example the 'example-artifact' dependency in the JBoss-4.2.3.GA profile has not been
updated to the new 0.5-SNAPSHOT version:
{code:xml}
  ...
  <profile>
     <id>JBoss-4.2.3.GA</id>
       <activation>
	  <activeByDefault>true</activeByDefault>
	</activation>
	<dependencies>
	  <dependency>
	    <groupId>example.groupId</groupId>
	    <artifactId>example-artifact</artifactId>
	    <version>0.4-SNAPSHOT</version>
	    <type>ejb</type>
	    <exclusions>
	      <exclusion>
		<groupId>asm</groupId>
		<artifactId>asm</artifactId>
	      </exclusion>
	      ....
{code} 
I agree with Martin that all dependencies defined in profile sections should be updated no
matter which profile is active at the moment.

      was (Author: mathiasarens):
    I have exactly the same problem. My dependencies in a profile section are not updated
as well.

In my example the 'example-artifact' dependency in the JBoss-4.2.3.GA profile has not been
updated to the new 0.5-SNAPSHOT version:
       ...
	<profile>
			<id>JBoss-4.2.3.GA</id>
			<activation>
				<activeByDefault>true</activeByDefault>
			</activation>
			<dependencies>
				<dependency>
					<groupId>example.groupId</groupId>
					<artifactId>example-artifact</artifactId>
					<version>0.4-SNAPSHOT</version>
					<type>ejb</type>
					<exclusions>
						<exclusion>
							<groupId>asm</groupId>
							<artifactId>asm</artifactId>
						</exclusion>
						....
I agree with Martin that all dependencies defined in profile sections should be updated no
matter which profile is active at the moment.
  
> Versions defined in profiles are not updated
> --------------------------------------------
>
>                 Key: MRELEASE-354
>                 URL: http://jira.codehaus.org/browse/MRELEASE-354
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-7
>         Environment: Maven version: 2.0.9
> Java version: 1.6.0_06
> OS name: "windows 2000" version: "5.0" arch: "x86" Family: "windows"
>            Reporter: Martin von Zweigbergk
>
> Versions defined in profiles (in either <dependencies> or <dependecyManagement>)
should be updated, regardless of which profile are active.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message