Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Tue, 28 Aug 2012 04:31:21 -0500 (CDT)
From: "Vladimir Kravets (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Message-ID: 
 <162060037.47454.1346146281121.JavaMail.j2ee-jira@codehaus01.managed.contegix.com>
Subject: [jira] (MNG-5337) Maven activation profile feature cannot differ
 jdk version with build number
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Vladimir Kravets created MNG-5337:
-------------------------------------

             Summary: Maven activation profile feature cannot differ jdk version with build number
                 Key: MNG-5337
                 URL: https://jira.codehaus.org/browse/MNG-5337
             Project: Maven 2 & 3
          Issue Type: Bug
    Affects Versions: 3.0.5, 3.1
            Reporter: Vladimir Kravets
            Priority: Minor
         Attachments: fix_jdk_build_version_activator.diff

Since Oracle can apply some major changes between builds we need to have ability to detect build number from profile -> activation -> jdk tag
By now using only first three components of jdk version. I propose to use first 4 components of the version to be able to process it further.

E.g. from ~1.6.0-30 classpath separator is ";" instead of ":". In 1.7.x also using ";".


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira