You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Mark Brouwer (JIRA)" <ji...@apache.org> on 2007/01/15 09:59:28 UTC
[jira] Created: (RIVER-8) com.sun.jini.tool.ClassDep empty inside
collection doesn't work
com.sun.jini.tool.ClassDep empty inside collection doesn't work
---------------------------------------------------------------
Key: RIVER-8
URL: https://issues.apache.org/jira/browse/RIVER-8
Project: Apache River
Issue Type: Bug
Reporter: Mark Brouwer
Priority: Minor
If you look at the API for {{com.sun.jini.tool.ClassDep}} it states that when you don't specify inside namespaces all namespaces are considered. This works fine if you specify your seed for the dependency checking with the {{addClasses}} method, however if you seed through the {{addRoots}} method you are lost. The code doesn't check whether the inside set is empty and if it is, it will ignore all classes found through the specified root(s). For more information see http://archives.java.sun.com/cgi-bin/wa?A2=ind0608&L=jini-users&F=&S=&P=10531.
This issue has been resolved already as part of the Cheiron project, see [http://issue.cheiron.org/browse/JSK-17|JSK-17], and is listed here to keep track of all issues against {{com.sun.jini.tool.ClassDep}} and to facilitate discussion.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (RIVER-8) com.sun.jini.tool.ClassDep empty inside
collection doesn't work
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer updated RIVER-8:
-----------------------------
Fix Version/s: AR2
> com.sun.jini.tool.ClassDep empty inside collection doesn't work
> ---------------------------------------------------------------
>
> Key: RIVER-8
> URL: https://issues.apache.org/jira/browse/RIVER-8
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_tool
> Affects Versions: jtsk_2.1
> Reporter: Mark Brouwer
> Assignee: Mark Brouwer
> Priority: Minor
> Fix For: AR2
>
>
> If you look at the API for {{com.sun.jini.tool.ClassDep}} it states that when you don't specify inside namespaces all namespaces are considered. This works fine if you specify your seed for the dependency checking with the {{addClasses}} method, however if you seed through the {{addRoots}} method you are lost. The code doesn't check whether the inside set is empty and if it is, it will ignore all classes found through the specified root(s). For more information see http://archives.java.sun.com/cgi-bin/wa?A2=ind0608&L=jini-users&F=&S=&P=10531.
> This issue has been resolved already as part of the Cheiron project, see [JSK-17|http://issue.cheiron.org/browse/JSK-17], and is listed here to keep track of all issues against {{com.sun.jini.tool.ClassDep}} and to facilitate discussion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (RIVER-8) com.sun.jini.tool.ClassDep empty inside
collection doesn't work
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone closed RIVER-8.
-------------------------------
> com.sun.jini.tool.ClassDep empty inside collection doesn't work
> ---------------------------------------------------------------
>
> Key: RIVER-8
> URL: https://issues.apache.org/jira/browse/RIVER-8
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_tool
> Affects Versions: jtsk_2.1
> Reporter: Mark Brouwer
> Assignee: Mark Brouwer
> Priority: Minor
> Fix For: AR2
>
>
> If you look at the API for {{com.sun.jini.tool.ClassDep}} it states that when you don't specify inside namespaces all namespaces are considered. This works fine if you specify your seed for the dependency checking with the {{addClasses}} method, however if you seed through the {{addRoots}} method you are lost. The code doesn't check whether the inside set is empty and if it is, it will ignore all classes found through the specified root(s). For more information see http://archives.java.sun.com/cgi-bin/wa?A2=ind0608&L=jini-users&F=&S=&P=10531.
> This issue has been resolved already as part of the Cheiron project, see [JSK-17|http://issue.cheiron.org/browse/JSK-17], and is listed here to keep track of all issues against {{com.sun.jini.tool.ClassDep}} and to facilitate discussion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (RIVER-8) com.sun.jini.tool.ClassDep empty
inside collection doesn't work
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on RIVER-8 started by Mark Brouwer.
> com.sun.jini.tool.ClassDep empty inside collection doesn't work
> ---------------------------------------------------------------
>
> Key: RIVER-8
> URL: https://issues.apache.org/jira/browse/RIVER-8
> Project: River
> Issue Type: Bug
> Reporter: Mark Brouwer
> Assigned To: Mark Brouwer
> Priority: Minor
>
> If you look at the API for {{com.sun.jini.tool.ClassDep}} it states that when you don't specify inside namespaces all namespaces are considered. This works fine if you specify your seed for the dependency checking with the {{addClasses}} method, however if you seed through the {{addRoots}} method you are lost. The code doesn't check whether the inside set is empty and if it is, it will ignore all classes found through the specified root(s). For more information see http://archives.java.sun.com/cgi-bin/wa?A2=ind0608&L=jini-users&F=&S=&P=10531.
> This issue has been resolved already as part of the Cheiron project, see [JSK-17|http://issue.cheiron.org/browse/JSK-17], and is listed here to keep track of all issues against {{com.sun.jini.tool.ClassDep}} and to facilitate discussion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (RIVER-8) com.sun.jini.tool.ClassDep empty inside
collection doesn't work
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer resolved RIVER-8.
------------------------------
Resolution: Fixed
> com.sun.jini.tool.ClassDep empty inside collection doesn't work
> ---------------------------------------------------------------
>
> Key: RIVER-8
> URL: https://issues.apache.org/jira/browse/RIVER-8
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_tool
> Affects Versions: jtsk_2.1
> Reporter: Mark Brouwer
> Assignee: Mark Brouwer
> Priority: Minor
> Fix For: AR2
>
>
> If you look at the API for {{com.sun.jini.tool.ClassDep}} it states that when you don't specify inside namespaces all namespaces are considered. This works fine if you specify your seed for the dependency checking with the {{addClasses}} method, however if you seed through the {{addRoots}} method you are lost. The code doesn't check whether the inside set is empty and if it is, it will ignore all classes found through the specified root(s). For more information see http://archives.java.sun.com/cgi-bin/wa?A2=ind0608&L=jini-users&F=&S=&P=10531.
> This issue has been resolved already as part of the Cheiron project, see [JSK-17|http://issue.cheiron.org/browse/JSK-17], and is listed here to keep track of all issues against {{com.sun.jini.tool.ClassDep}} and to facilitate discussion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-8) com.sun.jini.tool.ClassDep empty inside
collection doesn't work
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer updated RIVER-8:
-----------------------------
Description:
If you look at the API for {{com.sun.jini.tool.ClassDep}} it states that when you don't specify inside namespaces all namespaces are considered. This works fine if you specify your seed for the dependency checking with the {{addClasses}} method, however if you seed through the {{addRoots}} method you are lost. The code doesn't check whether the inside set is empty and if it is, it will ignore all classes found through the specified root(s). For more information see http://archives.java.sun.com/cgi-bin/wa?A2=ind0608&L=jini-users&F=&S=&P=10531.
This issue has been resolved already as part of the Cheiron project, see [JSK-17|http://issue.cheiron.org/browse/JSK-17], and is listed here to keep track of all issues against {{com.sun.jini.tool.ClassDep}} and to facilitate discussion.
was:
If you look at the API for {{com.sun.jini.tool.ClassDep}} it states that when you don't specify inside namespaces all namespaces are considered. This works fine if you specify your seed for the dependency checking with the {{addClasses}} method, however if you seed through the {{addRoots}} method you are lost. The code doesn't check whether the inside set is empty and if it is, it will ignore all classes found through the specified root(s). For more information see http://archives.java.sun.com/cgi-bin/wa?A2=ind0608&L=jini-users&F=&S=&P=10531.
This issue has been resolved already as part of the Cheiron project, see [http://issue.cheiron.org/browse/JSK-17|JSK-17], and is listed here to keep track of all issues against {{com.sun.jini.tool.ClassDep}} and to facilitate discussion.
> com.sun.jini.tool.ClassDep empty inside collection doesn't work
> ---------------------------------------------------------------
>
> Key: RIVER-8
> URL: https://issues.apache.org/jira/browse/RIVER-8
> Project: Apache River
> Issue Type: Bug
> Reporter: Mark Brouwer
> Priority: Minor
>
> If you look at the API for {{com.sun.jini.tool.ClassDep}} it states that when you don't specify inside namespaces all namespaces are considered. This works fine if you specify your seed for the dependency checking with the {{addClasses}} method, however if you seed through the {{addRoots}} method you are lost. The code doesn't check whether the inside set is empty and if it is, it will ignore all classes found through the specified root(s). For more information see http://archives.java.sun.com/cgi-bin/wa?A2=ind0608&L=jini-users&F=&S=&P=10531.
> This issue has been resolved already as part of the Cheiron project, see [JSK-17|http://issue.cheiron.org/browse/JSK-17], and is listed here to keep track of all issues against {{com.sun.jini.tool.ClassDep}} and to facilitate discussion.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (RIVER-8) com.sun.jini.tool.ClassDep empty inside
collection doesn't work
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer reassigned RIVER-8:
--------------------------------
Assignee: Mark Brouwer
> com.sun.jini.tool.ClassDep empty inside collection doesn't work
> ---------------------------------------------------------------
>
> Key: RIVER-8
> URL: https://issues.apache.org/jira/browse/RIVER-8
> Project: River
> Issue Type: Bug
> Reporter: Mark Brouwer
> Assigned To: Mark Brouwer
> Priority: Minor
>
> If you look at the API for {{com.sun.jini.tool.ClassDep}} it states that when you don't specify inside namespaces all namespaces are considered. This works fine if you specify your seed for the dependency checking with the {{addClasses}} method, however if you seed through the {{addRoots}} method you are lost. The code doesn't check whether the inside set is empty and if it is, it will ignore all classes found through the specified root(s). For more information see http://archives.java.sun.com/cgi-bin/wa?A2=ind0608&L=jini-users&F=&S=&P=10531.
> This issue has been resolved already as part of the Cheiron project, see [JSK-17|http://issue.cheiron.org/browse/JSK-17], and is listed here to keep track of all issues against {{com.sun.jini.tool.ClassDep}} and to facilitate discussion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-8) com.sun.jini.tool.ClassDep empty inside
collection doesn't work
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer updated RIVER-8:
-----------------------------
Component/s: com_sun_jini_tool
Affects Version/s: jtsk_2.1
> com.sun.jini.tool.ClassDep empty inside collection doesn't work
> ---------------------------------------------------------------
>
> Key: RIVER-8
> URL: https://issues.apache.org/jira/browse/RIVER-8
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_tool
> Affects Versions: jtsk_2.1
> Reporter: Mark Brouwer
> Assignee: Mark Brouwer
> Priority: Minor
>
> If you look at the API for {{com.sun.jini.tool.ClassDep}} it states that when you don't specify inside namespaces all namespaces are considered. This works fine if you specify your seed for the dependency checking with the {{addClasses}} method, however if you seed through the {{addRoots}} method you are lost. The code doesn't check whether the inside set is empty and if it is, it will ignore all classes found through the specified root(s). For more information see http://archives.java.sun.com/cgi-bin/wa?A2=ind0608&L=jini-users&F=&S=&P=10531.
> This issue has been resolved already as part of the Cheiron project, see [JSK-17|http://issue.cheiron.org/browse/JSK-17], and is listed here to keep track of all issues against {{com.sun.jini.tool.ClassDep}} and to facilitate discussion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.