[jira] [Commented] (ARIES-1814) Solve the start order limitations with SPI Fly
[
https://issues.apache.org/jira/browse/ARIES-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16549608#comment-16549608
]
ASF subversion and git services commented on ARIES-1814:
Commit 1836283 from rotty3...@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1836283 ]
Revert "ARIES-1814 Solve the start order limitations with SPI Fly by then
eliminating unused dependency on Log Service"
This reverts commit 255d3994cc87f1e28f57948e7b1cc18890b61970.
> Solve the start order limitations with SPI Fly
> --
>
> Key: ARIES-1814
> URL: https://issues.apache.org/jira/browse/ARIES-1814
> Project: Aries
> Issue Type: Improvement
> Components: SPI Fly
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
> Fix For: spifly-1.0.14
>
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in
> maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as
> Import-Package
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARIES-1814) Solve the start order limitations with SPI Fly
[
https://issues.apache.org/jira/browse/ARIES-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16549609#comment-16549609
]
ASF subversion and git services commented on ARIES-1814:
Commit 1836284 from rotty3...@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1836284 ]
ARIES-1814 Solve the start order limitations with SPI Fly by then eliminating
unused dependency on Log Service
> Solve the start order limitations with SPI Fly
> --
>
> Key: ARIES-1814
> URL: https://issues.apache.org/jira/browse/ARIES-1814
> Project: Aries
> Issue Type: Improvement
> Components: SPI Fly
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
> Fix For: spifly-1.0.14
>
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in
> maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as
> Import-Package
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARIES-1814) Solve the start order limitations with SPI Fly
[
https://issues.apache.org/jira/browse/ARIES-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545687#comment-16545687
]
ASF subversion and git services commented on ARIES-1814:
Commit 1836062 from rotty3...@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1836062 ]
ARIES-1814 Solve the start order limitations with SPI Fly by first creating a
framework extension
Signed-off-by: Raymond Auge
> Solve the start order limitations with SPI Fly
> --
>
> Key: ARIES-1814
> URL: https://issues.apache.org/jira/browse/ARIES-1814
> Project: Aries
> Issue Type: Improvement
> Components: SPI Fly
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in
> maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as
> Import-Package
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARIES-1814) Solve the start order limitations with SPI Fly
[
https://issues.apache.org/jira/browse/ARIES-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545689#comment-16545689
]
ASF subversion and git services commented on ARIES-1814:
Commit 1836064 from rotty3...@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1836064 ]
ARIES-1814 Solve the start order limitations with SPI Fly by changing the
verification approach to rely on uses constraints instead of package attributes
Signed-off-by: Raymond Auge
> Solve the start order limitations with SPI Fly
> --
>
> Key: ARIES-1814
> URL: https://issues.apache.org/jira/browse/ARIES-1814
> Project: Aries
> Issue Type: Improvement
> Components: SPI Fly
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in
> maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as
> Import-Package
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARIES-1814) Solve the start order limitations with SPI Fly
[
https://issues.apache.org/jira/browse/ARIES-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545688#comment-16545688
]
ASF subversion and git services commented on ARIES-1814:
Commit 1836063 from rotty3...@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1836063 ]
ARIES-1814 Solve the start order limitations with SPI Fly by then eliminating
unused dependency on Log Service
Signed-off-by: Raymond Auge
> Solve the start order limitations with SPI Fly
> --
>
> Key: ARIES-1814
> URL: https://issues.apache.org/jira/browse/ARIES-1814
> Project: Aries
> Issue Type: Improvement
> Components: SPI Fly
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in
> maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as
> Import-Package
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARIES-1814) Solve the start order limitations with SPI Fly
[
https://issues.apache.org/jira/browse/ARIES-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529594#comment-16529594
]
David Bosschaert commented on ARIES-1814:
-
Thanks for offering to help out with this issue [~rotty3000]!
> Solve the start order limitations with SPI Fly
> --
>
> Key: ARIES-1814
> URL: https://issues.apache.org/jira/browse/ARIES-1814
> Project: Aries
> Issue Type: Improvement
> Components: SPI Fly
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in
> maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as
> Import-Package
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
