Skip to content

Conversation

@dragos
Copy link
Contributor

@dragos dragos commented Sep 20, 2013

A few changes needed for proper Eclipse consumption as OSGi:

  • create OSGi headers
  • make source jars OSGi bundles with the proper headers
  • make the version number OSGi-friendly. In particular, 3 digits + qualifier

Fixed #1.

@dragos
Copy link
Contributor Author

dragos commented Sep 20, 2013

/cc @jsuereth.

Copy link
Contributor

Choose a reason for hiding this comment

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

Is this build pushing the source bundle too? I'm a bit unfamiliar with what this does in non-eclipse OSGi environs....

Copy link
Contributor

Choose a reason for hiding this comment

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

Oh, nevermind, just saw the packageSrc. Sweet.

@jsuereth
Copy link
Contributor

LGTM. I may be copying this for OSGi-ifying sbt jars :)

@dragos
Copy link
Contributor Author

dragos commented Sep 20, 2013

👍

@dragos
Copy link
Contributor Author

dragos commented Sep 23, 2013

Could we get this in, please? /cc @gkossakowski

@gkossakowski
Copy link
Contributor

@adriaanm: I don't have access rights to merge PRs here. Is there a way to configure access right across the entire scala organization for me?

@adriaanm
Copy link
Contributor

fixed for all recently created repos -- sorry about that!

Copy link
Contributor

Choose a reason for hiding this comment

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

Note that this must be coordinated with https://github.com/scala/scala/blob/master/versions.properties, https://github.com/scala/scala-partest/blob/master/build.sbt#L19, and possibly others (TODO for me: make an overview of this)

Copy link
Member

Choose a reason for hiding this comment

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

This should not be checked in with a non-SNAPSHOT version, the release process is the only place where it should tick over to a real version, ever so briefly.

Copy link
Member

Choose a reason for hiding this comment

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

Reason: if I checkout this locally and publish-local, I will overwrite the local binaries with something newer than the released version. Those might be resolved by an upstream project inducing the subtle brand of calamity that we can do without.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree, but I didn't want to push this change in this PR, which is about OSGi. If everyone agrees on -SNAPSHOT I can prepare another PR.

Copy link
Member

Choose a reason for hiding this comment

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

Agreed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@adriaanm What should I do about those files? Wouldn't they evolve naturally, once a new release of scala-xml is cut? (assuming the propagation step is done on releases).

Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry, I again forgot about using snapshot in the repo . +1 on what Jason said.

Copy link
Contributor

Choose a reason for hiding this comment

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

Also, that change is fine in this pr, as long as it's a separate commit

@adriaanm
Copy link
Contributor

Merging -- I'll follow up with changing to snapshot version.

adriaanm added a commit that referenced this pull request Sep 26, 2013
Add OSGi headers and source bundle
@adriaanm adriaanm merged commit dbe57a4 into scala:master Sep 26, 2013
@dragos
Copy link
Contributor Author

dragos commented Sep 26, 2013

Thanks @adriaanm, I got delayed with other OSGi goodness on our side.

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.

Add OSGi headers

5 participants