You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Kalle Korhonen (JIRA)" <ji...@apache.org> on 2010/02/08 20:09:28 UTC
[jira] Created: (SHIRO-137) Go through Shiro dependencies and
consider marking most third-party dependencies as provided
Go through Shiro dependencies and consider marking most third-party dependencies as provided
--------------------------------------------------------------------------------------------
Key: SHIRO-137
URL: https://issues.apache.org/jira/browse/SHIRO-137
Project: Shiro
Issue Type: Improvement
Affects Versions: 0.9
Reporter: Kalle Korhonen
Assignee: Kalle Korhonen
Priority: Minor
Fix For: 1.0.0
It's unlikely that users would use Shiro support modules to pull in a dependency to third-party libraries (such as Spring), but rather they explicitly declare the version they are dependent on. If we mark this dependencies as provided, we are forcing users to explicity declare those dependencies but at the same time, we avoid issues with potential version conflicts. What I don't like about this issue is that it's kind of open-ended, but I'll do a first pass before 1.0.0 and then close.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SHIRO-137) Go through Shiro dependencies and
consider marking most third-party dependencies as provided
Posted by "Kalle Korhonen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHIRO-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kalle Korhonen resolved SHIRO-137.
----------------------------------
Resolution: Fixed
> Go through Shiro dependencies and consider marking most third-party dependencies as provided
> --------------------------------------------------------------------------------------------
>
> Key: SHIRO-137
> URL: https://issues.apache.org/jira/browse/SHIRO-137
> Project: Shiro
> Issue Type: Improvement
> Affects Versions: 0.9
> Reporter: Kalle Korhonen
> Assignee: Kalle Korhonen
> Priority: Minor
> Fix For: 1.0.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> It's unlikely that users would use Shiro support modules to pull in a dependency to third-party libraries (such as Spring), but rather they explicitly declare the version they are dependent on. If we mark this dependencies as provided, we are forcing users to explicity declare those dependencies but at the same time, we avoid issues with potential version conflicts. What I don't like about this issue is that it's kind of open-ended, but I'll do a first pass before 1.0.0 and then close.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work logged: (SHIRO-137) Go through Shiro dependencies and
consider marking most third-party dependencies as provided
Posted by "Kalle Korhonen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHIRO-137?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_11007 ]
Kalle Korhonen logged work on SHIRO-137:
----------------------------------------
Author: Kalle Korhonen
Created on: 19/Feb/10 04:42 AM
Start Date: 19/Feb/10 04:42 AM
Worklog Time Spent: 0.5h
Issue Time Tracking
-------------------
Time Spent: 0.5h
Remaining Estimate: 0h (was: 2h)
> Go through Shiro dependencies and consider marking most third-party dependencies as provided
> --------------------------------------------------------------------------------------------
>
> Key: SHIRO-137
> URL: https://issues.apache.org/jira/browse/SHIRO-137
> Project: Shiro
> Issue Type: Improvement
> Affects Versions: 0.9
> Reporter: Kalle Korhonen
> Assignee: Kalle Korhonen
> Priority: Minor
> Fix For: 1.0.0
>
> Original Estimate: 2h
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It's unlikely that users would use Shiro support modules to pull in a dependency to third-party libraries (such as Spring), but rather they explicitly declare the version they are dependent on. If we mark this dependencies as provided, we are forcing users to explicity declare those dependencies but at the same time, we avoid issues with potential version conflicts. What I don't like about this issue is that it's kind of open-ended, but I'll do a first pass before 1.0.0 and then close.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (SHIRO-137) Go through Shiro dependencies and
consider marking most third-party dependencies as provided
Posted by "Kalle Korhonen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHIRO-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SHIRO-137 started by Kalle Korhonen.
> Go through Shiro dependencies and consider marking most third-party dependencies as provided
> --------------------------------------------------------------------------------------------
>
> Key: SHIRO-137
> URL: https://issues.apache.org/jira/browse/SHIRO-137
> Project: Shiro
> Issue Type: Improvement
> Affects Versions: 0.9
> Reporter: Kalle Korhonen
> Assignee: Kalle Korhonen
> Priority: Minor
> Fix For: 1.0.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> It's unlikely that users would use Shiro support modules to pull in a dependency to third-party libraries (such as Spring), but rather they explicitly declare the version they are dependent on. If we mark this dependencies as provided, we are forcing users to explicity declare those dependencies but at the same time, we avoid issues with potential version conflicts. What I don't like about this issue is that it's kind of open-ended, but I'll do a first pass before 1.0.0 and then close.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.