Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: #12 : prepare the MANIFEST for packaging as osgi fragment #13

Closed
wants to merge 1 commit into from

Conversation

erwindl0
Copy link

@erwindl0 erwindl0 commented Jan 5, 2022

No description provided.

Comment on lines +1 to +15
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Liquibase Slf4j Logging
Bundle-SymbolicName: com.mattbertolini.liquibase.logging.slf4j
Bundle-Version: 4.0.0
Automatic-Module-Name: com.mattbertolini.liquibase.logging.slf4j
Bundle-RequiredExecutionEnvironment: JavaSE-11
Export-Package: com.mattbertolini.liquibase.logging.slf4j;version="4.0.0"
Import-Package: liquibase.logging;version="4.0.0",
liquibase.logging.core;version="4.0.0",
org.junit.jupiter.api;version="5.7.1";resolution:=optional,
org.mockito;version="2.23.0";resolution:=optional,
org.mockito.stubbing;version="2.23.0";resolution:=optional,
org.slf4j;version="1.7.0"
Fragment-Host: org.liquibase.core;bundle-version="[4.0.0,5.0.0)"
Copy link
Owner

@mattbertolini mattbertolini Jan 5, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: I don't understand why the file was moved from src/main/resources? Also, is there a way to generate these values? I don't want to be in the business of figuring out these imports. The liquibase version supported is version 4.1, not 4.0. Finally, the library supports Java 8 so that execution environment would have to be changed.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is to make it easier to import/maintain it in Eclipse IDE.

I could go for other approaches indeed, based on the BND tool, to generate the manifest.
But I don't know if/how they support Ant&Ivy builds, afaik they have maven integration only.

Comment on lines +66 to +69

<target name="-process-meta-inf-resources" if="meta_inf.dir.exists">
<macro:processresources dir="${meta_inf.dir}" todir="${build.main.dir}/META-INF"/>
</target>
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this, or any of the ant changes are needed if the manifest file is just kept where it is.

@@ -20,6 +20,7 @@
import liquibase.logging.LogMessageFilter;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import org.mockito.stubbing.OngoingStubbing;
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this import needed. I don't see any other changes.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch, will remove it.

@mattbertolini
Copy link
Owner

Hi. Thanks for the PR. I'm a bit hesitant about adding this as I am not too familar with OSGi. I see the build is failing so that will need to be addressed.

@erwindl0
Copy link
Author

erwindl0 commented Jan 6, 2022

Hmm, apparently emptying the resources folder effectively made it disappear in the repo, which was not the case on my local system. I'll adapt things.

@mattbertolini
Copy link
Owner

Closing as the OSGi metadata was generated via BND in #14.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants