Release 1.1.0 about camunda-bpm-spring-boot-starter

[meyerdan]

There are already 30 commis on master since last release.
Why not release it right away?
Do you need more stuff?

🍔

[jangalinski]

webjar camunda webapp starter did not work when I tested it ... this schould be part of the release. Can anyone confirm/retest?

[meyerdan]

Can't you release the current status and then do another relase with only the webjar thing?

[jangalinski]

We could ... but why should we release with a "closed" issue that does not work? Can you just run the webapp example on your machine and see how it goes?

[meyerdan]

Sounds like that issue needs re-opening :=)

Idea 1:

• re-open webjar issue
• move webjar stuff to branch
• release project.
• then fix webjar stuff

Idea 2:

• just release it and declare the webjar stuff as "experimental" or "known issue".

You are probably thinking: "why is that guy trolling here in the spring boot project? Doesn't he have other things to do? Doesn't he have his own releases to cut?"

The answer is: Yes I do. However, I know the desire of putting that last feature / bugfix ... into the release and while I am doing that discovering new things to put the next thing in there as well and by this putting off the release again and again and in the end never releasing anything. Knowing this so well I can maybe help somewhere else when I think I see similar tendencies. But feel free to completely ignore / mute me :=)

[osteinhauer]

By the way issue #3 is still open. Anyway there must be someone who tests and create issues. Without I have no idea what is not working.

Nevertheless I can follow Daniel: There can be a release without the web starter.

[hawky-4s-]

I will test #3 and put some work into the project tomorrow or monday as slacktime to fix any remaining issues.
Can we agree on a release date next week?

[osteinhauer]

I agree with a release independent if #3 is integrated or not.

[nikku]

I am a fan of releasing early and often. #3 looks like a nice candiate for a follow up release. 🌵

[lofidewanto]

I tried the webjar stuff:

1. I can open the 3 webapps: tasklist, cockpit and admin.
2. I have to insert a new user for Camunda as usual and this works just fine.
3. Problem: with the new created user I cannot login into the webapp. This looks like the problem of the "standard" H2 DB in memory.

I will try to use other DB and try to restart the Spring Boot service.

[jangalinski]

What is the url you use to access the webapp?

[osteinhauer]

Are you running the example Applikation? If so, there should be no context in the URL and the frontend should be accessible using http://localhost:8080/

[lofidewanto]

OK it works, I also try with our own process model project. The problem was the Spring Security. If you have the jar in your classpath you need to turn it off:

security.basic.enabled=false

or just exclude the spring-security.jar.

I can use all three webapps without any problem.

Thanks,
Lofi

[jangalinski]

Yes, I run the example-webapp Application. I get a 404 when I open http://localhost:8080/

[lofidewanto]

Try this address:
localhost:8080/"context"/app/cockpit/index.html

Or just without "context".

[jangalinski]

This localhost:8080//app/cockpit/index.html works for me.

I would have expected localhost:8080/camunda (or localhost:8080/ as oliver suggested). Do we need to set an acceptance criteria on the issue ("should be reachable under ....")? I find it rather unintuitive to guess link contents ....

But still: it works ... so I am with you for the 1.1.0 release 👍

[osteinhauer]

I expected that the webapp is reachable under /. It worked for me but I was blended by browser cache - sorry for that.

I fixed this with commit 897dc0b and added some docu with commit 90b1561.

Please verify and do the release.

[meyerdan]

Still no release 😿

[jangalinski]

Sorry, I checked that the cockpit is accessible with the latest fix from Oliver but then discovered that the tasklist is not usable because filters do not work because of the json-header bug Daniel found.

We can release though, just have to accept missing tasklist as known bug. Christian?

[meyerdan]

Lets make deal :Dollar:

1. You do a release of Spring Boot
2. I will fix the tasklist header bug :)
3. You do another release of Spring Boot

This way we have two releases :Zap:

[jangalinski]

And we all know: 2 releases are better than 1 release. At least twice as good, I'd say :-)

[meyerdan]

awesomeness = 2^(Number of releases)

[osteinhauer]

please please do the release

...sounds like a song :)

Am 29.01.2016 um 10:57 schrieb Daniel Meyer [email protected]:

awesomeness = 2^(Number of releases)

—
Reply to this email directly or view it on GitHub #31 (comment).

[nikku]

Be noisy guys. More releases, more publicity, more fame and fortune for camunda-bpm-spring-boot-starter.

I will trigger the release when I get a cookie from ya!

On 29.01.16 13:22, Nico Rehwaldt wrote:

Be noisy guys. More releases, more publicity, more fame and fortune
for camunda-bpm-spring-boot-starter.

—
Reply to this email directly or view it on GitHub
#31 (comment).

[osteinhauer]

🍪

Am 29.01.2016 um 13:23 schrieb camunda-jenkins [email protected]:

I will trigger the release when I get a cookie from ya!

On 29.01.16 13:22, Nico Rehwaldt wrote:

Be noisy guys. More releases, more publicity, more fame and fortune
for camunda-bpm-spring-boot-starter.

—
Reply to this email directly or view it on GitHub
#31 (comment).

—
Reply to this email directly or view it on GitHub #31 (comment).

[meyerdan]

😿 😿 😿

[nikku]

👍 for release.

[hawky-4s-]

Release 🍻 today and 🍪s on monday for me please -> 1.1.0

[meyerdan]

😹 😹 😹

[meyerdan]

Will there be a blogpost as well?

[meyerdan]

Would be really cool if we could produce some kind of blogpost or release notes so that users know that there is a new release and what is in it.
A short announcement, 5 lines of text would be enough...

Let me know if I can help out.