Re: [mdmbl-dev] OpenMDM web broken as of 10-16-2017 because of version r

[<m.koller@xxxxxxxxxxxxxxxx>]

Hi Silvio,

thanks for reporting this issue.

Can you please file a bug at https://bugs.eclipse.org/bugs/.

We will look into the issue and track it in Bugzilla.


Best regards,

Matthias

-----Ursprüngliche Nachricht-----
Von: mdmbl-dev-bounces@xxxxxxxxxxx [mailto:mdmbl-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Silvio Heuberger
Gesendet: Montag, 16. Oktober 2017 17:29
An: mdmbl-dev@xxxxxxxxxxx
Betreff: [mdmbl-dev] OpenMDM web broken as of 10-16-2017 because of version
ranges/tracking versions

Then there's also this issue as of now:

Since the package.json in the web client also uses 'tracking' versions or
'the caret notation', it seems that the client is as of now broken because
of some new versions of dependencies (it's quite hard to find what broke
it):

"dependencies": {
    "@angular/common": "^2.4.8",
    "@angular/compiler": "^2.4.8",
    "@angular/core": "^2.4.8",
    "@angular/forms": "^2.4.8"
(...)
    "reflect-metadata": "^0.1.3",
    "rxjs": "^5.1.0",
    "ts-helpers": "^1.1.1",
    "zone.js": "^0.7.6"
  }

This is basically as good as telling npm: Take anything you can find on the
internet and try to run the build with it.

If I now (October 16. 2017, 16:45) run the npm build from a clean state and
then create a list of all dependencies I end up with the following output
(please see the attached text files).
Interestingly enough, there is also errors printed to stderr, but the build
still succeeds.

As a matter of fact, if one then navigates to the webapp deployed in
glassfish, after login you simply see this:

    Loading....

Anyone have any hints on how to fix it or what broke it?
It's going to be hard to track down because of the unspecified versions... 

Cheers,
Silvio