[
https://issues.apache.org/jira/browse/FELIX-6490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned FELIX-6490:
---
Assignee: Jean-Baptiste Onofré
> Files that cannot be deployed due to a miss
Herve Boutemy created FELIX-6496:
Summary: non-reproducible Export-Package and Private-Package values
Key: FELIX-6496
URL: https://issues.apache.org/jira/browse/FELIX-6496
Project: Felix
Issu
[
https://issues.apache.org/jira/browse/FELIX-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned FELIX-6495:
---
Assignee: Jean-Baptiste Onofré
> bundle:manifest produces non reproducible B
Herve Boutemy created FELIX-6495:
Summary: bundle:manifest produces non reproducible Bnd-LastModified
Key: FELIX-6495
URL: https://issues.apache.org/jira/browse/FELIX-6495
Project: Felix
Issu
Herve Boutemy created FELIX-6494:
Summary: add version to Created-By Manifest entry
Key: FELIX-6494
URL: https://issues.apache.org/jira/browse/FELIX-6494
Project: Felix
Issue Type: Improvemen
laeubi commented on pull request #124:
URL: https://github.com/apache/felix-dev/pull/124#issuecomment-1003047363
> From my recent observations the BND-Analyzer takes some time for larger
projects with many classes to scan. So I think it is not worthless.
Sure but how often is an incr
HannesWell commented on pull request #124:
URL: https://github.com/apache/felix-dev/pull/124#issuecomment-1003042843
> > > * consider pom.xml modifications in up-to-date logic
> >
> >
> > Actually the pom's of all parent projects have to be considered as well.
I'm about to update
laeubi commented on pull request #124:
URL: https://github.com/apache/felix-dev/pull/124#issuecomment-1003033763
> > * consider pom.xml modifications in up-to-date logic
>
> Actually the pom's of all parent projects have to be considered as well.
I'm about to update this PR according
Hello
Pax Logging 2.0.14, 1.11.13 and 1.10.9 have been released with two upgrades:
- Log4j2 2.17.1
- Logback 1.2.10
These are the latest versions of the dependencies as of December 30th 2021.
Additionally, 2.0.14 and 1.11.13 contain new configuration property:
"org.ops4j.pax.logging.syncJULFor
HannesWell commented on pull request #124:
URL: https://github.com/apache/felix-dev/pull/124#issuecomment-1002992144
>- consider pom.xml modifications in up-to-date logic
Actually the pom's of all parent projects have to be considered as well.
I'm about to update this PR accord
HannesWell commented on pull request #124:
URL: https://github.com/apache/felix-dev/pull/124#issuecomment-1002968329
Besides the changes affecting the logic a moderate number of possible clean
up changes.
To you want to have a dedicated issue for a clean up or can I create a
subsequent
HannesWell opened a new pull request #124:
URL: https://github.com/apache/felix-dev/pull/124
This PR addresses issue
[FELIX-6493](https://issues.apache.org/jira/browse/FELIX-6493) and extends the
is-up-to-date logic of the Manifest goal to
- consider as not up-to-date if the MANIFEST.MF
[
https://issues.apache.org/jira/browse/FELIX-6493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hannes Wellmann updated FELIX-6493:
---
Summary: Extend is-up-to-date logic of Manifest goal (was: Extend
is-up-to-date logic in Man
Hannes Wellmann created FELIX-6493:
--
Summary: Extend is-up-to-date logic in ManifestPlugin
Key: FELIX-6493
URL: https://issues.apache.org/jira/browse/FELIX-6493
Project: Felix
Issue Type: Bu
14 matches
Mail list logo