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

Include Lift and Scala version numbers in package name #27

Merged
merged 1 commit into from
Jan 10, 2018

Conversation

pdyraga
Copy link
Contributor

@pdyraga pdyraga commented Jan 8, 2018

Lift 3.0 and 3.1 libs are not guaranteed to be mutually compatible. The same for various Scala versions project is compiled for.
In order to let developers refer to the right version, we put Lift and Scala version number in package name.

For example:

lift-formality_3.1_2.11-1.1.0-SNAPSHOT.jar

Lift 3.0 and 3.1 libs are not guaranteed to be mutually compatible. The same for various Scala versions project is compiled for.
In order to let developers refer to the right version, we put Lift and Scala version number in package name.
@pdyraga pdyraga mentioned this pull request Jan 8, 2018
@@ -1,25 +1,33 @@
val liftVersion = settingKey[String]("Lift Web Framework full version number")
val liftEdition = settingKey[String]("Lift Edition (such as 2.6 or 3.0)")
Copy link
Member

Choose a reason for hiding this comment

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

Any reason to have these be settingKey instead of just val?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Building for multiple Scala versions is easy - we can just add crossScalaVersions (which I didn't add here because I see it in #26) and it works out of the box. However, I haven't seen so far anything like that for building against different library versions. With settingKey we can do just:

> set liftVersion:="2.6"
[info] Defining *:liftVersion
[info] The new value will be used by *:libraryDependencies, *:liftEdition
[info] Reapplying settings...
[info] Set current project to lift-formality (in build file:/Users/piotr/git/lift-formality/)

> package
(...)
[info] Packaging /Users/piotr/git/lift-formality/target/scala-2.11/lift-formality_2.6_2.11-1.1.0-SNAPSHOT.jar ...
[info] Done packaging.

Copy link
Member

Choose a reason for hiding this comment

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

Gotcha. Fair enough!

Copy link
Member

@Shadowfiend Shadowfiend left a comment

Choose a reason for hiding this comment

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

LGTM!

@Shadowfiend Shadowfiend merged commit 12fb099 into hacklanta:master Jan 10, 2018
@pdyraga
Copy link
Contributor Author

pdyraga commented Jan 10, 2018

🎉

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