[jira] [Assigned] (ACE-514) Upgrade to Dependency Manager 4

2015-08-08 Thread Marcel Offermans (JIRA)

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

Marcel Offermans reassigned ACE-514:


Assignee: Marcel Offermans

> Upgrade to Dependency Manager 4
> ---
>
> Key: ACE-514
> URL: https://issues.apache.org/jira/browse/ACE-514
> Project: ACE
>  Issue Type: Improvement
>  Components: Architecture
>Reporter: Marcel Offermans
>Assignee: Marcel Offermans
>
> The Apache Felix project recently released Dependency Manager 4 (the current 
> release is 4.0.1). This upgrade fixes some concurrency issues, cleans up the 
> API and support concurrency a lot better than before, resulting in faster 
> startup times. It would be good to upgrade to this version, even though a 
> couple of small things have changed.



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


[jira] [Commented] (ACE-514) Upgrade to Dependency Manager 4

2015-08-08 Thread Marcel Offermans (JIRA)

[ 
https://issues.apache.org/jira/browse/ACE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14663150#comment-14663150
 ] 

Marcel Offermans commented on ACE-514:
--

Current versions of DM4 are 4.1.1 for the core and 4.0.2 for the shell. Working 
on doing the upgrade now. On the Felix website there is information about how 
to migrate.

> Upgrade to Dependency Manager 4
> ---
>
> Key: ACE-514
> URL: https://issues.apache.org/jira/browse/ACE-514
> Project: ACE
>  Issue Type: Improvement
>  Components: Architecture
>Reporter: Marcel Offermans
>Assignee: Marcel Offermans
>
> The Apache Felix project recently released Dependency Manager 4 (the current 
> release is 4.0.1). This upgrade fixes some concurrency issues, cleans up the 
> API and support concurrency a lot better than before, resulting in faster 
> startup times. It would be good to upgrade to this version, even though a 
> couple of small things have changed.



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


[jira] [Commented] (ACE-492) Update the project to use Bndtools 2.4.0

2015-08-08 Thread Marcel Offermans (JIRA)

[ 
https://issues.apache.org/jira/browse/ACE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14663151#comment-14663151
 ] 

Marcel Offermans commented on ACE-492:
--

The current build works with 2.4.1 (still using the Ant build).
Bndtools 3.0.0 will probably be released soon, so we need to test against that 
one.

> Update the project to use Bndtools 2.4.0
> 
>
> Key: ACE-492
> URL: https://issues.apache.org/jira/browse/ACE-492
> Project: ACE
>  Issue Type: Improvement
>  Components: Build
>Reporter: Marcel Offermans
>
> Bndtools 2.4.0 has just been released, so we should probably spend some time 
> upgrading the ACE build to work with it. This can probably be done in two 
> steps:
> # Ensure that the current build works with 2.4.0.
> # Migrate to gradle, as that is the new build system for 2.4.0.



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


[jira] [Closed] (ACE-459) Add BundleSymbolicName and Version to AuditLog/FeedBack on BundleEvents

2015-08-08 Thread Marcel Offermans (JIRA)

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

Marcel Offermans closed ACE-459.

Resolution: Won't Fix

As discussed in the comments, the requested information can already be obtained 
(albeit in a slightly more complicated way).

> Add BundleSymbolicName and Version to AuditLog/FeedBack on BundleEvents
> ---
>
> Key: ACE-459
> URL: https://issues.apache.org/jira/browse/ACE-459
> Project: ACE
>  Issue Type: Improvement
>  Components: Management Agent
>Affects Versions: 1.0.0
>Reporter: Wilfried Sibla
>Priority: Minor
> Attachments: EventLogger.patch
>
>
> The LogViewer within the Target dialog on the ACE server only shows the id of 
> the bundles (except directly during installation).
> It would be very helpful to have the BSN and version also there in case of 
> problem diagnostics etc.



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


[jira] [Commented] (ACE-390) Generate Maven POM files for bundles.

2015-08-08 Thread Marcel Offermans (JIRA)

[ 
https://issues.apache.org/jira/browse/ACE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14663155#comment-14663155
 ] 

Marcel Offermans commented on ACE-390:
--

The main goal is being able to upload our bundles to a Maven repository. We 
should probably take a closer look at the Dependency Manager 4 project, which 
also uses Bndtools and does that.

> Generate Maven POM files for bundles.
> -
>
> Key: ACE-390
> URL: https://issues.apache.org/jira/browse/ACE-390
> Project: ACE
>  Issue Type: Task
>  Components: Build
>Reporter: Marcel Offermans
>
> Sometimes you might want to use bundles in a Maven context. We currently have 
> no support to generate a POM from a bundle and we want to add that so we can 
> support various Maven repositories out there.



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