Skip to content

Conversation

@arjenw
Copy link

@arjenw arjenw commented Jan 19, 2016

With this change it is possible to run sbt package instead of sbt osgiBundle to create the package. This is also necessary when the JAR's are required in other plugins (which usually depend on package).

This is achieved by using dependencyClasspath and products instead of fullClasspath (causing a circular dependency on artifact when used in combination with package).

@arjenw
Copy link
Author

arjenw commented Mar 21, 2016

Any update on this?

@mdedetrich
Copy link
Collaborator

Any update on this?

@arjenw Sorry for the long wait but as you likely gathered this project wasn't really maintained until I started picking it up. Since this appears to be a breaking change its likely that we would merge this a bit later, possibly for a 1.0.x release (unless you can also keep old behaviour i.e. sbt osgiBundle intact, can you confirm or deny this?)

@arjenw
Copy link
Author

arjenw commented Oct 23, 2023

We aren't using sbt-osgi anymore, so I don't need the fix myself anymore. I leave it up to your discretion how to handle this further.

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