lift-ng 0.12.0-RC1

[j...@joescii.com]

Hello Lift community!

I want folks who enjoy lift-ng know that I am actively working to release lift-ng 0.12.0-RC1. It will contain three PRs:

1) Support for production-mode Angular (PR here and Issue here)

2) Providing lift-ng with a Future[Box[T]] will now behave like pre-v0.11.0 lift-ng did with LAFuture[Box[T]] (that is, it will be flattened to be like a nullable JS object) (PR here).
3) Fixing compatibility with lift-cluster by wrapping ExecutionContext parameters with the new lift-ng type ExecutionContextProvider to make it possible to pass an ExecutionContext without it being serialized for clustering (PR here).

A release candidate for lift-ng is a new thing I'm trying. Now that there are a couple of folks using in projects I'm not directly involved in, I think it is best to add an RC step in releases to help folks find problems like I discovered in item 3) above.

Reply back here or on the PRs if you have any questions, comments, or concerns about the next release!

Joe

[j...@joescii.com]

Well I have not figured out how to release an RC1 through sonatype.org. If I push it to a staging repo for release, it gets blocked at the release phase. If I try pushing it to the snapshot repo, I get blocked with 400 errors. I'll look into how we publish Lift proper at some point

For now, to try the release candidate for 0.12.0, configure your app to use 0.12.0-SNAPSHOT and include the snapshot repo as an externalResolver in your sbt configuration: 

"Snapshots" at "https://oss.sonatype.org/content/repositories/snapshots"

Joe

[Antonio Salazar Cardozo]

What do you mean by “gets blocked”? Sonatype's UI for promoting releases is a bit of a pain, so

it may just be confusion from that.

Thanks,

Antonio

[Joe Barnes]

Antonio,

Pressing "Release" on the closed staging repo generates a rule failure. The following is all I have to go with:

Event: Failed: Repository Writable

Friday, April 13, 2018 09:46:45 CDT (GMT-0500)

typeId	RepositoryWritePolicy
failureMessage	Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/net/liftmodules/ng_3.0_2.11/0.12.0-RC1/ng_3.0_2.11-0.12.0-RC1-javadoc.jar'
failureMessage	Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/net/liftmodules/ng_3.0_2.11/0.12.0-RC1/ng_3.0_2.11-0.12.0-RC1.jar'
failureMessage	Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/net/liftmodules/ng_3.0_2.11/0.12.0-RC1/ng_3.0_2.11-0.12.0-RC1.pom'
failureMessage	Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/net/liftmodules/ng_3.0_2.11/0.12.0-RC1/ng_3.0_2.11-0.12.0-RC1-sources.jar'

The list of failureMessages continues for every artifact I have in the repo.

Joe

/**

 * Joe Barnes

 * Owner/Principal Consultant, joescii, llc

 * 256.541.0377

 * j...@joescii.com

 */

--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code

---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Matt Farmer]

I think this means you’ve already released a version with that version identifier

To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code

---
You received this message because you are subscribed to the Google Groups "Lift" group.

To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.

[Tim Nelson]

Joe,

If you're still having trouble, I'd suggest trying bintray, it's so much easier to deploy code to and is literally a one-button click to get it on maven central.

Tim

[Antonio Salazar Cardozo]

Indeed https://oss.sonatype.org/content/repositories/releases/net/liftmodules/ng_3.0_2.11/0.12.0-RC1/

Nice catch!

Thanks,

Antonio

To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code

---
You received this message because you are subscribed to the Google Groups "Lift" group.

To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.

[Joe Barnes]

Huh, everything seems to be working now. My guess is the first attempt succeeded, but I didn't wait long enough for it to sync all the way to maven central. The second time, I unchecked the default option to drop the repo after promotion. That's when I got the error I posted here which indeed is because of a duplicate.

Normally sync to central happens within seconds. Next time I'll check the sontatype repo that Antonio linked rather than checking central.

Thanks guys!

Joe

/**

 * Joe Barnes

 * Owner/Principal Consultant, joescii, llc

 * 256.541.0377

 * j...@joescii.com

 */