[jira] [Commented] (ARIES-1368) BundleResource is not able to compute capabilities for fragments

2015-08-11 Thread Tom De Wolf (JIRA)

[ 
https://issues.apache.org/jira/browse/ARIES-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681340#comment-14681340
 ] 

Tom De Wolf commented on ARIES-1368:


John, is it not possible to have the testsupport release 2.0.0? It is rather 
urgent for our customer to be able to adopt subsystems. Otherwise we might have 
to drop aries subsystems completely which I would not prefer.

 BundleResource is not able to compute capabilities for fragments
 

 Key: ARIES-1368
 URL: https://issues.apache.org/jira/browse/ARIES-1368
 Project: Aries
  Issue Type: Bug
  Components: Subsystem
Affects Versions: subsystem-core-1.0.0, subsystem-core-1.1.0, 
 subsystem-core-1.2.0, subsystem-2.0.2, subsystem-2.0.1
Reporter: Wouter Bancken
Assignee: John Ross
 Attachments: 
 OsgiIdentityCapability.OsgiIdentityCapability(Resource,BundleManifest)-CallHierarchy.jpg,
  test-service-fragment-subsystem-1.0.1-SNAPSHOT.esa


 The computeOsgiIdentityCapability method of the BundleResource is not able to 
 compute capabilities for fragments (only for bundles). 
 This is caused by the fact that the BundleResource is hardcoded to always 
 assume a type of osgi.bundle without inspecting the manifest.
 Link to mailinglist thread: 
 http://mail-archives.apache.org/mod_mbox/aries-user/201508.mbox/%3CCAL5nZgTOVhdAPYYFOmuV%3DPquAz1a4n_D1Rd3RBrTfu2znCSjKA%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (ARIES-1368) BundleResource is not able to compute capabilities for fragments

2015-08-11 Thread John Ross (JIRA)

[ 
https://issues.apache.org/jira/browse/ARIES-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681765#comment-14681765
 ] 

John Ross commented on ARIES-1368:
--

I changed line 73 of OsgiIdentityCapability from

IdentityNamespace.TYPE_BUNDLE);

to

manifest.getHeader(Constants.FRAGMENT_HOST) == null ? 
IdentityNamespace.TYPE_BUNDLE : IdentityNamespace.TYPE_FRAGMENT);

in order to correctly identify fragments from bundles. Testing for the 
existence of the Fragment-Host header is sufficient for identifying a bundle as 
a fragment. However, this did not fix the problem. Upon further debugging, it 
looks like the Fragment-Host requirement is not being included as part of the 
corresponding resource which results in an improper resolution.

 BundleResource is not able to compute capabilities for fragments
 

 Key: ARIES-1368
 URL: https://issues.apache.org/jira/browse/ARIES-1368
 Project: Aries
  Issue Type: Bug
  Components: Subsystem
Affects Versions: subsystem-core-1.0.0, subsystem-core-1.1.0, 
 subsystem-core-1.2.0, subsystem-2.0.2, subsystem-2.0.1
Reporter: Wouter Bancken
Assignee: John Ross
 Attachments: 
 OsgiIdentityCapability.OsgiIdentityCapability(Resource,BundleManifest)-CallHierarchy.jpg,
  test-service-fragment-subsystem-1.0.1-SNAPSHOT.esa


 The computeOsgiIdentityCapability method of the BundleResource is not able to 
 compute capabilities for fragments (only for bundles). 
 This is caused by the fact that the BundleResource is hardcoded to always 
 assume a type of osgi.bundle without inspecting the manifest.
 Link to mailinglist thread: 
 http://mail-archives.apache.org/mod_mbox/aries-user/201508.mbox/%3CCAL5nZgTOVhdAPYYFOmuV%3DPquAz1a4n_D1Rd3RBrTfu2znCSjKA%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (ARIES-1373) Add switch to generator for the annotation based style of jpa 2.1.0

2015-08-11 Thread Christian Schneider (JIRA)

 [ 
https://issues.apache.org/jira/browse/ARIES-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider resolved ARIES-1373.

Resolution: Fixed

 Add switch to generator for the annotation based style of jpa 2.1.0
 ---

 Key: ARIES-1373
 URL: https://issues.apache.org/jira/browse/ARIES-1373
 Project: Aries
  Issue Type: Improvement
  Components: Blueprint
Affects Versions: blueprint-maven-plugin-1.1.0
Reporter: Christian Schneider
Assignee: Christian Schneider
 Fix For: blueprint-maven-plugin-1.2.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (ARIES-1258) Refactorings in subsystem tests

2015-08-11 Thread Christian Schneider (JIRA)

 [ 
https://issues.apache.org/jira/browse/ARIES-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider updated ARIES-1258:
---
Assignee: (was: Christian Schneider)

 Refactorings in subsystem tests
 ---

 Key: ARIES-1258
 URL: https://issues.apache.org/jira/browse/ARIES-1258
 Project: Aries
  Issue Type: Test
  Components: Subsystem
Reporter: Christian Schneider

 The subsystem tests currently use a mix of maven, ArchiveFixture and custom 
 code to create test subsystem esa files.
 I would like to replace this with TinyBundles.
 Advantages are:
 - We use the standard bundling tool of pax exam
 - The complete bundles and esa files can be created using TinyBundles so the 
 code is more cohesive as it happens in one place
 - When running the tests from eclipse the project dir is not littered with 
 build artifacts anymore



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [VOTE] transaction blueprint 1.1.1

2015-08-11 Thread Christian Schneider

Closing this vote with 5 binding +1s and no other votes.

Thanks to everyone.
Christian

On 08.08.2015 20:23, Christian Schneider wrote:

Because of a critical error I had to do another bugfix release.

I've staged a release for vote at:
https://repository.apache.org/content/repositories/orgapachearies-1036

*Release Notes - Aries - Version transaction-blueprint-1.1.1*

** Bug
* [ARIES-1369] - Transaction is not rolled back if coordination 
has failed



https://issues.apache.org/jira/browse/ARIES/fixforversion/12333243

Please review and vote:
  [ ] +1 Release the above artifacts
  [ ] -1 Do not

Here is my +1

Cheers,
Christian
--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com



--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com



[jira] [Commented] (ARIES-1368) Fragment resources receive the osgi.identity capability type of osgi.bundle but should receive osgi.fragment. Also, osgi.wiring.host capabilities and requirements are n

2015-08-11 Thread John Ross (JIRA)

[ 
https://issues.apache.org/jira/browse/ARIES-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14692791#comment-14692791
 ] 

John Ross commented on ARIES-1368:
--

Patches attached.

(1) Assign osgi.identity type of osgi.fragment instead of osgi.bundle to 
fragment resources.
(2) Add support for the computation of osgi.wiring.host capabilities and 
requirements for bundle and fragment resources.
(3) Add tests.
(4) Point subsystem-core to version 2.0.0-SNAPSHOT of aries-testsupport.
(5) Update licenses on already modified files.

I'll commit as soon as I figure out how to set up my credentials again.

 Fragment resources receive the osgi.identity capability type of osgi.bundle 
 but should receive osgi.fragment. Also, osgi.wiring.host capabilities and 
 requirements are not computed for bundle or fragment resources.
 -

 Key: ARIES-1368
 URL: https://issues.apache.org/jira/browse/ARIES-1368
 Project: Aries
  Issue Type: Bug
  Components: Subsystem
Affects Versions: subsystem-core-1.0.0, subsystem-core-1.1.0, 
 subsystem-core-1.2.0, subsystem-2.0.1, subsystem-2.0.2
Reporter: Wouter Bancken
Assignee: John Ross
 Attachments: 
 OsgiIdentityCapability.OsgiIdentityCapability(Resource,BundleManifest)-CallHierarchy.jpg,
  org.apache.aries.subsystem.core.patch, 
 org.apache.aries.subsystem.itests.patch, 
 test-service-fragment-subsystem-1.0.1-SNAPSHOT.esa


 The computeOsgiIdentityCapability method of the BundleResource is not able to 
 compute capabilities for fragments (only for bundles). 
 This is caused by the fact that the BundleResource is hardcoded to always 
 assume a type of osgi.bundle without inspecting the manifest.
 Link to mailinglist thread: 
 http://mail-archives.apache.org/mod_mbox/aries-user/201508.mbox/%3CCAL5nZgTOVhdAPYYFOmuV%3DPquAz1a4n_D1Rd3RBrTfu2znCSjKA%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (ARIES-1368) Fragment resources receive the osgi.identity capability type of osgi.bundle but should receive osgi.fragment. Also, osgi.wiring.host capabilities and requirements are not

2015-08-11 Thread John Ross (JIRA)

 [ 
https://issues.apache.org/jira/browse/ARIES-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Ross updated ARIES-1368:
-
Summary: Fragment resources receive the osgi.identity capability type of 
osgi.bundle but should receive osgi.fragment. Also, osgi.wiring.host 
capabilities and requirements are not computed for bundle or fragment 
resources.  (was: BundleResource is not able to compute capabilities for 
fragments)

 Fragment resources receive the osgi.identity capability type of osgi.bundle 
 but should receive osgi.fragment. Also, osgi.wiring.host capabilities and 
 requirements are not computed for bundle or fragment resources.
 -

 Key: ARIES-1368
 URL: https://issues.apache.org/jira/browse/ARIES-1368
 Project: Aries
  Issue Type: Bug
  Components: Subsystem
Affects Versions: subsystem-core-1.0.0, subsystem-core-1.1.0, 
 subsystem-core-1.2.0, subsystem-2.0.1, subsystem-2.0.2
Reporter: Wouter Bancken
Assignee: John Ross
 Attachments: 
 OsgiIdentityCapability.OsgiIdentityCapability(Resource,BundleManifest)-CallHierarchy.jpg,
  test-service-fragment-subsystem-1.0.1-SNAPSHOT.esa


 The computeOsgiIdentityCapability method of the BundleResource is not able to 
 compute capabilities for fragments (only for bundles). 
 This is caused by the fact that the BundleResource is hardcoded to always 
 assume a type of osgi.bundle without inspecting the manifest.
 Link to mailinglist thread: 
 http://mail-archives.apache.org/mod_mbox/aries-user/201508.mbox/%3CCAL5nZgTOVhdAPYYFOmuV%3DPquAz1a4n_D1Rd3RBrTfu2znCSjKA%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)