You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Samisa Abeysinghe (JIRA)" <ji...@apache.org> on 2010/12/21 14:26:02 UTC

[jira] Updated: (RAMPART-222) Maven rampart-project POM does not have a profile for JDK 1.6

     [ https://issues.apache.org/jira/browse/RAMPART-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Samisa Abeysinghe updated RAMPART-222:
--------------------------------------

    Issue Type: Improvement  (was: Bug)

> Maven rampart-project POM does not have a profile for JDK 1.6
> -------------------------------------------------------------
>
>                 Key: RAMPART-222
>                 URL: https://issues.apache.org/jira/browse/RAMPART-222
>             Project: Rampart
>          Issue Type: Improvement
>          Components: distribution
>    Affects Versions: 1.4
>            Reporter: Paul Field
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Minor
>
> The rampart-project POM specifies profiles for JDK 1.4 and JDK 1.5 - with a default of JDK 1.4.
> When running on JDK 1.6 (or later), Maven 2.0 is using the default profile which will cause a dependency on bcprov-jdk13. However, I expect it should depend on bcprov-jdk16.
> Incidentally, Maven 2.1 has changed the logic of the <jdk> profile activation to use the Enforcer Version Range Syntax - so JDK 1.6 will match the 1.5 profile, which is much better behaviour (and why I marked this issue as only "minor").

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org