We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-14391

The Maven dependency processor not able to process maven active profiles

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 5.4.2
    • Maven

      This bug behavior is similar to https://jira.atlassian.com/browse/BAM-12775
      The issue here is that we have defined an active profile to run based on the version of the JDK as described in http://maven.apache.org/guides/introduction/introduction-to-profiles.html

      Now with a single profile, the MRP fails with the error :

      2014-03-17 18:30:16,045 INFO [9-BAM::Default Agent::Agent:pool-24-thread-1] [TaskExecutorImpl] TESTA-MRP0-JOB1-5: Starting task 'Maven Dependencies Processor' of type 'com.atlassian.bamboo.plugins.maven:task.mvn.dependencies.processor'
      2014-03-17 18:30:16,045 INFO [9-BAM::Default Agent::Agent:pool-24-thread-1] [MavenDependenciesProcessorTask] Parsing maven project file D:\atlassian\BAMBOO\atlassian-bamboo-5.4.1\HOME\xml-data\build-dir\TESTA-MRP0-JOB1\pom.xml
      2014-03-17 18:30:16,197 ERROR [9-BAM::Default Agent::Agent:pool-24-thread-1] [MavenDependenciesProcessorTask] TESTA-MRP0-JOB1-5: Automatic Maven plan dependencies processing failed: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
      [ERROR] Failed to determine Java version for profile default @ line 52, column 10
      

      The segment of the pom.xml showing the profile:

      <profiles>
      		<profile>
      			<activation>
      				<jdk>1.7</jdk>
      			</activation>
      			<properties>
      				<jdk.compiler.version>1.7</jdk.compiler.version>
      			</properties>
      			<dependencies>
      				<dependency>
      					<groupId>javax.mail</groupId>
      					<artifactId>mail</artifactId>
      					<version>1.4.5</version>
      				</dependency>
      				<dependency>
      					<groupId>javax.activation</groupId>
      					<artifactId>activation</artifactId>
      					<version>1.1.1</version>
      				</dependency>
      				<dependency>
      					<groupId>org.slf4j</groupId>
      					<artifactId>slf4j-log4j12</artifactId>
      					<version>1.7.5</version>
      				</dependency>
      				<dependency> 
      					<groupId>cglib</groupId>
      					<artifactId>cglib</artifactId>
      					<version>2.2.2</version>
      				</dependency>
      				<dependency>
      					<groupId>joda-time</groupId>
      					<artifactId>joda-time</artifactId>
      					<version>2.1</version>
      				</dependency>
      				<dependency> 
      					<groupId>org.apache.commons</groupId>
      					<artifactId>commons-lang3</artifactId>
      					<version>3.1</version>
      				</dependency>
      				<dependency>
      					<groupId>org.aspectj</groupId>
      					<artifactId>aspectjweaver</artifactId>
      					<version>1.7.2</version>
      				</dependency>
      				<dependency>
      					<groupId>org.apache.openejb</groupId>
      					<artifactId>javaee-api</artifactId>
      					<version>5.0-3</version>
      					<scope>provided</scope>
      				</dependency>
      			</dependencies>
      
      			<build>
      				<plugins>
      					<plugin>
      						<artifactId>maven-jar-plugin</artifactId>
      						<version>2.4</version>
      						<configuration>
      							<classifier>jdk7</classifier>
      						</configuration>
      					</plugin>
      				</plugins>
      
      			</build>
      		</profile>
      </profiles>
      

      If we add multiple profiles with with an id, we get errors like:

      Automatic Maven plan dependencies processing failed: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[ERROR] Failed to determine Java version for profile if_jdk5 @ line 30, column 10[ERROR] Failed to determine Java version for profile if_jdk6 @ line 104, column 10
      

      Segment in pom

      <profiles>
      		<profile>
      			<id>if_jdk5</id>
      			<activation>
      				<jdk>1.5</jdk>
      			</activation>
      			<properties>
      				<jdk.compiler.version>1.5</jdk.compiler.version>
      			</properties>
      			<dependencies>
      .
      .
      .
      

      The effective poms can be generated successfully without problem and the maven task can run a build of the project

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Bamboo Data Center'
            1. Bamboo Data Center
            2. BAM-14391

            The Maven dependency processor not able to process maven active profiles

              • Icon: Bug Bug
              • Resolution: Unresolved
              • Icon: Low Low
              • None
              • 5.4.2
              • Maven

                This bug behavior is similar to https://jira.atlassian.com/browse/BAM-12775
                The issue here is that we have defined an active profile to run based on the version of the JDK as described in http://maven.apache.org/guides/introduction/introduction-to-profiles.html

                Now with a single profile, the MRP fails with the error :

                2014-03-17 18:30:16,045 INFO [9-BAM::Default Agent::Agent:pool-24-thread-1] [TaskExecutorImpl] TESTA-MRP0-JOB1-5: Starting task 'Maven Dependencies Processor' of type 'com.atlassian.bamboo.plugins.maven:task.mvn.dependencies.processor'
                2014-03-17 18:30:16,045 INFO [9-BAM::Default Agent::Agent:pool-24-thread-1] [MavenDependenciesProcessorTask] Parsing maven project file D:\atlassian\BAMBOO\atlassian-bamboo-5.4.1\HOME\xml-data\build-dir\TESTA-MRP0-JOB1\pom.xml
                2014-03-17 18:30:16,197 ERROR [9-BAM::Default Agent::Agent:pool-24-thread-1] [MavenDependenciesProcessorTask] TESTA-MRP0-JOB1-5: Automatic Maven plan dependencies processing failed: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
                [ERROR] Failed to determine Java version for profile default @ line 52, column 10
                

                The segment of the pom.xml showing the profile:

                <profiles>
                		<profile>
                			<activation>
                				<jdk>1.7</jdk>
                			</activation>
                			<properties>
                				<jdk.compiler.version>1.7</jdk.compiler.version>
                			</properties>
                			<dependencies>
                				<dependency>
                					<groupId>javax.mail</groupId>
                					<artifactId>mail</artifactId>
                					<version>1.4.5</version>
                				</dependency>
                				<dependency>
                					<groupId>javax.activation</groupId>
                					<artifactId>activation</artifactId>
                					<version>1.1.1</version>
                				</dependency>
                				<dependency>
                					<groupId>org.slf4j</groupId>
                					<artifactId>slf4j-log4j12</artifactId>
                					<version>1.7.5</version>
                				</dependency>
                				<dependency> 
                					<groupId>cglib</groupId>
                					<artifactId>cglib</artifactId>
                					<version>2.2.2</version>
                				</dependency>
                				<dependency>
                					<groupId>joda-time</groupId>
                					<artifactId>joda-time</artifactId>
                					<version>2.1</version>
                				</dependency>
                				<dependency> 
                					<groupId>org.apache.commons</groupId>
                					<artifactId>commons-lang3</artifactId>
                					<version>3.1</version>
                				</dependency>
                				<dependency>
                					<groupId>org.aspectj</groupId>
                					<artifactId>aspectjweaver</artifactId>
                					<version>1.7.2</version>
                				</dependency>
                				<dependency>
                					<groupId>org.apache.openejb</groupId>
                					<artifactId>javaee-api</artifactId>
                					<version>5.0-3</version>
                					<scope>provided</scope>
                				</dependency>
                			</dependencies>
                
                			<build>
                				<plugins>
                					<plugin>
                						<artifactId>maven-jar-plugin</artifactId>
                						<version>2.4</version>
                						<configuration>
                							<classifier>jdk7</classifier>
                						</configuration>
                					</plugin>
                				</plugins>
                
                			</build>
                		</profile>
                </profiles>
                

                If we add multiple profiles with with an id, we get errors like:

                Automatic Maven plan dependencies processing failed: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[ERROR] Failed to determine Java version for profile if_jdk5 @ line 30, column 10[ERROR] Failed to determine Java version for profile if_jdk6 @ line 104, column 10
                

                Segment in pom

                <profiles>
                		<profile>
                			<id>if_jdk5</id>
                			<activation>
                				<jdk>1.5</jdk>
                			</activation>
                			<properties>
                				<jdk.compiler.version>1.5</jdk.compiler.version>
                			</properties>
                			<dependencies>
                .
                .
                .
                

                The effective poms can be generated successfully without problem and the maven task can run a build of the project

                        Unassigned Unassigned
                        smaiyaki Sultan Maiyaki (Inactive)
                        Votes:
                        4 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            smaiyaki Sultan Maiyaki (Inactive)
                            Affected customers:
                            4 This affects my team
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated: