You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2011/04/26 19:29:03 UTC
[jira] [Created] (ARIES-638) Logging improvements in
AriesApplicationManagerImpl
Logging improvements in AriesApplicationManagerImpl
---------------------------------------------------
Key: ARIES-638
URL: https://issues.apache.org/jira/browse/ARIES-638
Project: Aries
Issue Type: Improvement
Components: Application
Affects Versions: application-0.2.1
Reporter: Jarek Gawor
A bundle in an application can be completely ignored by AriesApplicationManager.createApplication() (which can lead to resolution problems later on) if it doesn't contain the Bundle-ManifestVersion header. The bundle is considered invalid if it doesn't contain the Bundle-SymbolicName and Bundle-ManifestVersion headers. That's ok but there is no indication anywhere that the bundle was ignored and for what reason. The only way to tell what's going on is by stepping through the code in a debugger.
Adding logging statements to createApplication() as the nested bundles are processed would help to see what's going on with logging enabled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ARIES-638) Logging improvements in
AriesApplicationManagerImpl
Posted by "Jeremy Hughes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025680#comment-13025680 ]
Jeremy Hughes commented on ARIES-638:
-------------------------------------
Hi Jarek, can you say what your intention w.r.t releases is with this change. On the face of it, as you've put this change in three places I suspect you will want to release a 0.2.x, but I'm guessing the change is in 0.3.x and trunk for good housekeeping purposes rather than wishing to make a release of those yet.
> Logging improvements in AriesApplicationManagerImpl
> ---------------------------------------------------
>
> Key: ARIES-638
> URL: https://issues.apache.org/jira/browse/ARIES-638
> Project: Aries
> Issue Type: Improvement
> Components: Application
> Affects Versions: application-0.2.1
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
>
> A bundle in an application can be completely ignored by AriesApplicationManager.createApplication() (which can lead to resolution problems later on) if it doesn't contain the Bundle-ManifestVersion header. The bundle is considered invalid if it doesn't contain the Bundle-SymbolicName and Bundle-ManifestVersion headers. That's ok but there is no indication anywhere that the bundle was ignored and for what reason. The only way to tell what's going on is by stepping through the code in a debugger.
> Adding logging statements to createApplication() as the nested bundles are processed would help to see what's going on with logging enabled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ARIES-638) Logging improvements in
AriesApplicationManagerImpl
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor resolved ARIES-638.
-------------------------------
Resolution: Fixed
Committed some logging improvements to trunk (revision 1096861), 0.3 branch (revision 1096862) and 0.2 branch (revision 1096863).
> Logging improvements in AriesApplicationManagerImpl
> ---------------------------------------------------
>
> Key: ARIES-638
> URL: https://issues.apache.org/jira/browse/ARIES-638
> Project: Aries
> Issue Type: Improvement
> Components: Application
> Affects Versions: application-0.2.1
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
>
> A bundle in an application can be completely ignored by AriesApplicationManager.createApplication() (which can lead to resolution problems later on) if it doesn't contain the Bundle-ManifestVersion header. The bundle is considered invalid if it doesn't contain the Bundle-SymbolicName and Bundle-ManifestVersion headers. That's ok but there is no indication anywhere that the bundle was ignored and for what reason. The only way to tell what's going on is by stepping through the code in a debugger.
> Adding logging statements to createApplication() as the nested bundles are processed would help to see what's going on with logging enabled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (ARIES-638) Logging improvements in
AriesApplicationManagerImpl
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor reassigned ARIES-638:
---------------------------------
Assignee: Jarek Gawor
> Logging improvements in AriesApplicationManagerImpl
> ---------------------------------------------------
>
> Key: ARIES-638
> URL: https://issues.apache.org/jira/browse/ARIES-638
> Project: Aries
> Issue Type: Improvement
> Components: Application
> Affects Versions: application-0.2.1
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
>
> A bundle in an application can be completely ignored by AriesApplicationManager.createApplication() (which can lead to resolution problems later on) if it doesn't contain the Bundle-ManifestVersion header. The bundle is considered invalid if it doesn't contain the Bundle-SymbolicName and Bundle-ManifestVersion headers. That's ok but there is no indication anywhere that the bundle was ignored and for what reason. The only way to tell what's going on is by stepping through the code in a debugger.
> Adding logging statements to createApplication() as the nested bundles are processed would help to see what's going on with logging enabled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ARIES-638) Logging improvements in
AriesApplicationManagerImpl
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025907#comment-13025907 ]
Jarek Gawor commented on ARIES-638:
-----------------------------------
Not really sure yet. We have some code that uses 0.2.x and some that uses 0.3.x. So I was trying to cover all the bases in case we need a release from one of those branches. And we are planning to upgrade our older code to use trunk or 0.3.x at least.
> Logging improvements in AriesApplicationManagerImpl
> ---------------------------------------------------
>
> Key: ARIES-638
> URL: https://issues.apache.org/jira/browse/ARIES-638
> Project: Aries
> Issue Type: Improvement
> Components: Application
> Affects Versions: application-0.2.1
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
>
> A bundle in an application can be completely ignored by AriesApplicationManager.createApplication() (which can lead to resolution problems later on) if it doesn't contain the Bundle-ManifestVersion header. The bundle is considered invalid if it doesn't contain the Bundle-SymbolicName and Bundle-ManifestVersion headers. That's ok but there is no indication anywhere that the bundle was ignored and for what reason. The only way to tell what's going on is by stepping through the code in a debugger.
> Adding logging statements to createApplication() as the nested bundles are processed would help to see what's going on with logging enabled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira