[GitHub] aries pull request #69: Aries 1490 add feature to configure the 'Subsystem-C...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/69


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ARIES-1490) The esa maven plugin provides more flexibility when creating the subsystem manifest

[Tom De Wolf (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892554#comment-15892554
 ] 

Tom De Wolf commented on ARIES-1490:


[~bosschaert] thank you for taking care of it so soon. We'll take a look at the 
other pull request that now needs some adaptations. When that is done, we will 
notify you again. Thanks!

> The esa maven plugin provides more flexibility when creating the subsystem 
> manifest
> ---
>
> Key: ARIES-1490
> URL: https://issues.apache.org/jira/browse/ARIES-1490
> Project: Aries
>  Issue Type: New Feature
>  Components: ESA Maven Plugin
>Affects Versions: esa-maven-plugin-1.0.0
>Reporter: Wouter Bancken
>Assignee: David Bosschaert
> Fix For: esa-maven-plugin-1.0.0
>
>
> When determining which dependencies are included in the archive, the ESA 
> maven plugin provides different possibilities as to which dependencies are 
> included (transitive dependencies vs only direct dependencies). 
> When generating the subsystem manifest, the plugin always decides to only 
> list the direct dependencies and therefore it does not include the transitive 
> dependencies as part of the subsystem content even though they are present in 
> the archive.
> Additionally, the type of the dependencies (e.g. 'pom') is not taken into 
> account. This makes it impossible to extract a sequence of related 
> dependencies into a separate pom file to improve the overall readability. The 
> readability would improve greatly if a related set of dependencies could be 
> imported from another pom.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (ARIES-1490) The esa maven plugin provides more flexibility when creating the subsystem manifest

[David Bosschaert (JIRA)]

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

David Bosschaert resolved ARIES-1490.
-
   Resolution: Fixed
Fix Version/s: esa-maven-plugin-1.0.0

Many thanks for the patch, [~tom.dewolf]! It's applied in 
https://svn.apache.org/viewvc?view=revision=1785159

> The esa maven plugin provides more flexibility when creating the subsystem 
> manifest
> ---
>
> Key: ARIES-1490
> URL: https://issues.apache.org/jira/browse/ARIES-1490
> Project: Aries
>  Issue Type: New Feature
>  Components: ESA Maven Plugin
>Affects Versions: esa-maven-plugin-1.0.0
>Reporter: Wouter Bancken
>Assignee: David Bosschaert
> Fix For: esa-maven-plugin-1.0.0
>
>
> When determining which dependencies are included in the archive, the ESA 
> maven plugin provides different possibilities as to which dependencies are 
> included (transitive dependencies vs only direct dependencies). 
> When generating the subsystem manifest, the plugin always decides to only 
> list the direct dependencies and therefore it does not include the transitive 
> dependencies as part of the subsystem content even though they are present in 
> the archive.
> Additionally, the type of the dependencies (e.g. 'pom') is not taken into 
> account. This makes it impossible to extract a sequence of related 
> dependencies into a separate pom file to improve the overall readability. The 
> readability would improve greatly if a related set of dependencies could be 
> imported from another pom.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1490) The esa maven plugin provides more flexibility when creating the subsystem manifest

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892544#comment-15892544
 ] 

ASF GitHub Bot commented on ARIES-1490:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/69


> The esa maven plugin provides more flexibility when creating the subsystem 
> manifest
> ---
>
> Key: ARIES-1490
> URL: https://issues.apache.org/jira/browse/ARIES-1490
> Project: Aries
>  Issue Type: New Feature
>  Components: ESA Maven Plugin
>Affects Versions: esa-maven-plugin-1.0.0
>Reporter: Wouter Bancken
>Assignee: David Bosschaert
>
> When determining which dependencies are included in the archive, the ESA 
> maven plugin provides different possibilities as to which dependencies are 
> included (transitive dependencies vs only direct dependencies). 
> When generating the subsystem manifest, the plugin always decides to only 
> list the direct dependencies and therefore it does not include the transitive 
> dependencies as part of the subsystem content even though they are present in 
> the archive.
> Additionally, the type of the dependencies (e.g. 'pom') is not taken into 
> account. This makes it impossible to extract a sequence of related 
> dependencies into a separate pom file to improve the overall readability. The 
> readability would improve greatly if a related set of dependencies could be 
> imported from another pom.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1490) The esa maven plugin provides more flexibility when creating the subsystem manifest

[Tom De Wolf (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892389#comment-15892389
 ] 

Tom De Wolf commented on ARIES-1490:


[~bosschaert] are you still processing pull requests for the esa-maven-plugin? 
if not, who should I contact to get the pull request for this issue merged and 
released?

> The esa maven plugin provides more flexibility when creating the subsystem 
> manifest
> ---
>
> Key: ARIES-1490
> URL: https://issues.apache.org/jira/browse/ARIES-1490
> Project: Aries
>  Issue Type: New Feature
>  Components: ESA Maven Plugin
>Affects Versions: esa-maven-plugin-1.0.0
>Reporter: Wouter Bancken
>
> When determining which dependencies are included in the archive, the ESA 
> maven plugin provides different possibilities as to which dependencies are 
> included (transitive dependencies vs only direct dependencies). 
> When generating the subsystem manifest, the plugin always decides to only 
> list the direct dependencies and therefore it does not include the transitive 
> dependencies as part of the subsystem content even though they are present in 
> the archive.
> Additionally, the type of the dependencies (e.g. 'pom') is not taken into 
> account. This makes it impossible to extract a sequence of related 
> dependencies into a separate pom file to improve the overall readability. The 
> readability would improve greatly if a related set of dependencies could be 
> imported from another pom.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] aries pull request #69: Aries 1490 add feature to configure the 'Subsystem-C...

[tomdw]

GitHub user tomdw opened a pull request:

https://github.com/apache/aries/pull/69

Aries 1490 add feature to configure the 'Subsystem-Content' header to 
include only direct content or also transitive content

Solves ARIES-1490

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tomdw/aries 
ARIES-1490-add-all-as-content-packaging-option

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/69.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #69


commit ba0c1994663f9d3fa9c0ac0fd088ba20498f78ff
Author: Tom De Wolf 
Date:   2017-03-02T15:04:27Z

ARIES-1490 better error message

commit 0e1310975a30456fbb15da266e00b6bbdd06d8d0
Author: Tom De Wolf 
Date:   2017-03-02T15:04:45Z

ARIES-1490 typo in javadocs

commit 7ce4ddd5f1e8de25855937608493f54f4ee554e9
Author: Tom De Wolf 
Date:   2017-03-02T15:07:59Z

ARIES-1490 do not include ‘pom’ artefacts in esa subsystems - avoid 
error in maven run of plugin

commit 747c306d1e3cfcd0cbab517a430ef51d53db64a7
Author: Tom De Wolf 
Date:   2017-03-02T15:09:40Z

ARIES-1490 add missing test for archiveContent=all and setup with 
difference between project artefacts (transitive) and project 
dependencyArtefacts (direct)

commit 72d08649a363260f5a68d72c81c42e859bfc1725
Author: Tom De Wolf 
Date:   2017-03-02T15:11:28Z

ARIES-1490 add feature to configure the ‘manifestContent’ to determine 
if in the manifest Subsystem-Content header only the direct dependencies 
(content) needs to be included or also the transitive dependencies (all)




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (ARIES-1486) can't create proxy on java 8 vm for interfaces containing lambda

[Alexey Markevich (JIRA)]

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

Alexey Markevich updated ARIES-1486:

Attachment: static_method.log

What about static interface method?

> can't create proxy on java 8 vm  for interfaces containing lambda
> -
>
> Key: ARIES-1486
> URL: https://issues.apache.org/jira/browse/ARIES-1486
> Project: Aries
>  Issue Type: Bug
>  Components: Proxy
>Affects Versions: proxy-impl-1.0.5
> Environment: Java 8 vm
>Reporter: Samuel Bratton
>Assignee: Samuel Bratton
> Fix For: proxy-impl-1.0.5
>
> Attachments: aries1486.patch, static_method.log
>
>
> Creating proxy of an interface containing a default method implemented with a 
> lambda will result in a invalid Proxy class file (see attached test case).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)