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 "Thilina Buddhika (JIRA)" <ji...@apache.org> on 2010/12/21 11:55:01 UTC
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12973557#action_12973557 ]
Thilina Buddhika commented on RAMPART-222:
------------------------------------------
Hi,
I think we need to do a set of tests before upgrading into bcprov-1.6. At the moment, it uses bcprov-1.4 in JDK 1.5/1.6(Maven 2.1.0) profiles and it does not break any functionalities.
So it is better to mark this as a improvement.
Thanks,
Thilina
> 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: Bug
> 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