Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 12 09:35

    atooni on main

    Bumping logging libraries (compare)

  • Oct 07 07:55

    atooni on main

    Removing obsolete StatisticStat… (compare)

  • Aug 17 10:26

    atooni on 3.5

    (compare)

  • Aug 17 10:26

    atooni on main

    Just some code styling (compare)

  • Aug 13 10:17

    atooni on main

    Adding test for dynamically gen… (compare)

  • Aug 11 06:30
    dependabot[bot] labeled #144
  • Aug 11 06:29
    dependabot[bot] opened #144
  • Aug 11 06:29

    dependabot[bot] on npm_and_yarn

    Bump path-parse from 1.0.6 to 1… (compare)

  • Jul 13 06:48

    atooni on 3.3.1

    (compare)

  • Jul 09 21:19

    atooni on main

    Bumping the version Refactoring redelivery Refactoring single connection f… and 1 more (compare)

  • Jul 09 21:18

    atooni on amq

    Refactoring single connection f… Fixing error handling for faile… (compare)

  • Jul 09 14:48

    atooni on amq

    Bumping the version Refactoring redelivery (compare)

  • May 18 08:50

    atooni on 3.3

    (compare)

  • May 18 08:01

    atooni on jdk11

    (compare)

  • May 18 08:01

    atooni on main

    Add settings to create JDK11 co… Bump blended mill plugins (compare)

  • May 18 07:55

    atooni on jdk11

    Bump blended mill plugins (compare)

  • May 11 18:50
    dependabot[bot] labeled #143
  • May 11 18:50
    dependabot[bot] opened #143
  • May 11 18:50

    dependabot[bot] on npm_and_yarn

    Bump hosted-git-info from 2.8.8… (compare)

  • May 08 20:15

    dependabot[bot] on npm_and_yarn

    (compare)

Andreas Gies
@atooni
Of course, you will need to visualize the sorting state with a small icon next to the column header
Juanba98
@Juanba98
so i have to setup the sampleApp too?
Juanba98
@Juanba98
i mean how can i run it? because if i use the index-dev.html i just obtain a empty window @atooni
Andreas Gies
@atooni
I am wondering if we want to include the scala binary version in our symbolic names. We did not before, but with changing the build to potentially support multiple scalaversion may be we should
A side effect is that all config files would change their name as well as it is per default ${bundleSymbolicName}.conf
Tobias Roeser
@lefou
Yes, we should. We decided against before to avoid potential conflicts downstream, but IMHO we should correct this now.
Andreas Gies
@atooni
ok
Tobias Roeser
@lefou
@atooni You added another activator to blended.akka.http. Can you provide some context for it? dc48df13d8241417ecd48eac1f5c05fc08e0976d
Andreas Gies
@atooni
Yes. This is in relation to our ui projects. The idea is that in an UI project we do have the ScalaJS code that makes up the UI. The build process then goes and does its magic to apply webpack and create an OSGi bundle, so that the resulting UI can be hosted in a blended container. Within that magic we generate code for an Activator that is based on the Activator you have seen. I have included it in the core and Akka HTTP API because it seemed a common use case to me
In other words, It is to simplify the code generate and remove the boilerplate code to host the UI from the UI projects themselves
Tobias Roeser
@lefou
What's strange is that the bundle now has two activators
But only one is it's activator. Maybe it's just the misleading name.
Or we could move this into some kind of support package
Andreas Gies
@atooni
Could Rename it to something like ...ActivatorBase or ActivatorSupport
This a class that will never be instantiated itself, just inherited from
could also make it abstract
just saw it is abstract
it kind of belongs into that bundle unless we move the entire blended related API .... I would opt for renaming to something not ending in "activator"
Andreas Gies
@atooni
@lefou Do you think we should keep the projects creating the container separate from the integration tests ? - I am thinking along the lines that the result of a container project build are published / updated docker images. Then the integration test project could simply be turned into a nightly build grabing the latest image(s) of the containers and execute. Would probably also make it easier to create a configuration matrix, create a container for each element and IT test it
Andreas Gies
@atooni
@lefou In your latest change you have deleted the RuntimeConfigBuilder which we used to package our containers. Could you point me to the replacement to save me some time digging through the changes ?
Andreas Gies
@atooni
Found it - dont worry
Tobias Roeser
@lefou
Renamed it to ProfileBuilder
I now renamed to default branch to main.
Andreas Gies
@atooni
ok
Andreas Gies
@atooni
I should have moved master to main in all blended projects now
I have also changed the container project to publish docker images with a tag upon a tag push and with the content of version.txt for SNAPSHOTS
Andreas Gies
@atooni
https://github.com/woq-blended/blended.container is now on 3.2-alpha1 with integration tests running on GH actions & autopublishing of docker images
Andreas Gies
@atooni
FYI: feature references in feature configs will now look like :
{
  name = "blended.features.akka.http.modules"
  version = "3.2-SNAPSHOT"
  features = [
    { url="mvn:de.wayofquality.blended:blended.features_2.13:3.2-SNAPSHOT"
      names = ["blended.features.akka.http.base","blended.features.spring"],
      version = "3.2-SNAPSHOT" }
  ]
  bundles = [
    { url="mvn:de.wayofquality.blended:blended.akka.http.proxy_2.13:3.2-SNAPSHOT" },
    { url="mvn:de.wayofquality.blended:blended.akka.http.restjms_2.13:3.2-SNAPSHOT" },
    { url="mvn:de.wayofquality.blended:blended.akka.http.jmsqueue_2.13:3.2-SNAPSHOT" }
  ]
}