Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 534946

Summary: Stale ASM version 5
Product: [Modeling] MMT.ATL Reporter: Ed Willink <ed>
Component: EngineAssignee: Dennis Wagelaar <dwagelaar>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: dwagelaar
Version: unspecified   
Target Milestone: 4.0.1   
Hardware: PC   
OS: Windows 10   
See Also: https://git.eclipse.org/r/128993
https://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=6ec4cdb8040586da838e3e39c3a6c174c41cd652
https://git.eclipse.org/r/129017
https://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=f604dc72b6ec01bfcb0681558bc01135dea6949a
https://git.eclipse.org/r/132659
https://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=5524a85cbe93f8c0c75bedc49cad9bb24b1476af
https://git.eclipse.org/r/132661
https://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=ba66df460e715caaaaf7f13a0017cbfff6d5c870
https://git.eclipse.org/r/132666
https://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=ce24d257c6621df3c1fa149612ff11856ee9e43e
https://git.eclipse.org/r/132674
https://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=cbe6c713cb513c96910e8074e71365edaefaaba4
https://git.eclipse.org/r/132675
https://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=efb351215693397cdbb2e06b547754592dec8592
https://git.eclipse.org/r/132676
https://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=74ad4b2064939908218f88b03c85f35fa3fbbb20
https://git.eclipse.org/r/133954
https://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=a4111b7cf36696a7b421812178579a0487f9531b
Whiteboard:

Description Ed Willink CLA 2018-05-22 10:13:18 EDT
ATL 4.0.0M2 depends on ASM 5.X but ASM 6.X is in Orbit and used by the platform.

For OCL/QVTd I just relaxed the bounds to 5.0 to 7.0.
Comment 2 Dennis Wagelaar CLA 2018-06-04 07:36:54 EDT
Included in ATL 4.0.0 release.
Ed, can you verify?
Comment 3 Ed Willink CLA 2018-06-09 10:28:07 EDT
Verified for RC3. Unfortunately MWE has yet to migrate.
Comment 4 Ed Willink CLA 2018-07-01 07:28:41 EDT
Unfortunately the EMFTVM feature specifies real versions rather than just the default 0.0.0, so the problem in both plugins and features is only fixed in the plugins.

      <import plugin="org.eclipse.ui.ide"/>
      ...
      <import plugin="org.objectweb.asm" version="5.0.1" match="compatible"/>
Comment 5 Ed Willink CLA 2018-09-08 06:31:52 EDT
We don't seem to have an ATL 4.0.1 for 2018-09 so ATL installation forces in an additional ASM.
Comment 6 Eclipse Genie CLA 2018-09-09 12:14:49 EDT
New Gerrit change created: https://git.eclipse.org/r/128993
Comment 8 Ed Willink CLA 2018-09-09 13:15:27 EDT
A totally open upper boound is a bit dangerous. Why knows what ASM 7 will bring?

For OCL I set the bounds as 5 or 6.
Comment 9 Dennis Wagelaar CLA 2018-09-10 02:55:38 EDT
(In reply to Ed Willink from comment #8)
> A totally open upper boound is a bit dangerous. Why knows what ASM 7 will
> bring?
> 
> For OCL I set the bounds as 5 or 6.

It's set as "[5.0.1, 7.0)" in the plug-in, but the feature.xml only allows you to specify a single version with a match rule. I simply relaxed that rule one step from "Compatible" to "Greater or Equal". This is also consistent with the other dependency specifications in this feature.

I suspect that the more stringent version requirements specified inside the plug-in will still be picked up by Eclipse's P2?
Comment 10 Ed Willink CLA 2018-09-10 03:53:09 EDT
(In reply to Dennis Wagelaar from comment #9)
> It's set as "[5.0.1, 7.0)" in the plug-in, but the feature.xml only allows
> you to specify a single version with a match rule.

Ah! I didn't check the commit target file.

feature.xml gives you another option. Don't specify anything. This approach is pursued by UML, QVTo and OCL; no dependencies at all in feature.xml.

It would seem that feature.xml dependencies are obsolete wrt P2's analysis of plugins. I guess that a feature.xml dependency might be useful to allow e.g. the MacOS Helios feature to narrow a version range or override an 'optional' or force an OS-specific choice. For the normal boring build I suspect that they are just there to go stale.

Anyway +1 for 4.0.1. You might consider stripping feature.xml dependencies for 4.1.
Comment 11 Eclipse Genie CLA 2018-09-10 05:34:23 EDT
New Gerrit change created: https://git.eclipse.org/r/129017
Comment 12 Eclipse Genie CLA 2018-09-10 05:34:45 EDT
Gerrit change https://git.eclipse.org/r/129017 was merged to [R4_0_maintenance].
Commit: http://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=f604dc72b6ec01bfcb0681558bc01135dea6949a
Comment 13 Dennis Wagelaar CLA 2018-10-30 12:10:35 EDT
I've released 4.0.1M1: https://www.eclipse.org/atl/downloads/#S201810300954

Ed: Can you verify that this works for you?
Comment 14 Dennis Wagelaar CLA 2018-10-30 12:28:30 EDT
(In reply to Ed Willink from comment #10)
> (In reply to Dennis Wagelaar from comment #9)
> > It's set as "[5.0.1, 7.0)" in the plug-in, but the feature.xml only allows
> > you to specify a single version with a match rule.
> 
> Ah! I didn't check the commit target file.
> 
> feature.xml gives you another option. Don't specify anything. This approach
> is pursued by UML, QVTo and OCL; no dependencies at all in feature.xml.
> 
> It would seem that feature.xml dependencies are obsolete wrt P2's analysis
> of plugins. I guess that a feature.xml dependency might be useful to allow
> e.g. the MacOS Helios feature to narrow a version range or override an
> 'optional' or force an OS-specific choice. For the normal boring build I
> suspect that they are just there to go stale.
> 
> Anyway +1 for 4.0.1. You might consider stripping feature.xml dependencies
> for 4.1.

I created bug #540619 for stripping feature.xml dependencies.
Comment 15 Ed Willink CLA 2018-10-30 17:38:32 EDT
(In reply to Dennis Wagelaar from comment #13)
> I've released 4.0.1M1: https://www.eclipse.org/atl/downloads/#S201810300954
> 
> Ed: Can you verify that this works for you?

A bit late for M1. I'll check that when I create my M2 installations I get no ASM 5.
Comment 16 Ed Willink CLA 2018-11-08 11:46:45 EST
Verified. I can now install ATL using the ASM 6.2.1 provided by the platform.
Comment 17 Ed Willink CLA 2018-11-18 06:33:11 EST
The platform has moved to ASM 7.0 for 2018-12M2.

It seems compatible for me so I've just raised my upper version bound to 8 on OCL and QVTd. Please do the same for ATL.
Comment 18 Eclipse Genie CLA 2018-11-19 05:02:01 EST
New Gerrit change created: https://git.eclipse.org/r/132659
Comment 20 Eclipse Genie CLA 2018-11-19 05:19:52 EST
New Gerrit change created: https://git.eclipse.org/r/132661
Comment 22 Eclipse Genie CLA 2018-11-19 06:16:34 EST
New Gerrit change created: https://git.eclipse.org/r/132666
Comment 24 Eclipse Genie CLA 2018-11-19 07:09:02 EST
New Gerrit change created: https://git.eclipse.org/r/132674
Comment 25 Eclipse Genie CLA 2018-11-19 07:09:04 EST
Gerrit change https://git.eclipse.org/r/132674 was merged to [R4_0_maintenance].
Commit: http://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=cbe6c713cb513c96910e8074e71365edaefaaba4
Comment 26 Eclipse Genie CLA 2018-11-19 07:11:17 EST
New Gerrit change created: https://git.eclipse.org/r/132675
Comment 27 Eclipse Genie CLA 2018-11-19 07:11:19 EST
Gerrit change https://git.eclipse.org/r/132675 was merged to [R4_0_maintenance].
Commit: http://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=efb351215693397cdbb2e06b547754592dec8592
Comment 28 Eclipse Genie CLA 2018-11-19 07:11:41 EST
New Gerrit change created: https://git.eclipse.org/r/132676
Comment 29 Eclipse Genie CLA 2018-11-19 07:11:52 EST
Gerrit change https://git.eclipse.org/r/132676 was merged to [R4_0_maintenance].
Commit: http://git.eclipse.org/c/mmt/org.eclipse.atl.git/commit/?id=74ad4b2064939908218f88b03c85f35fa3fbbb20
Comment 30 Dennis Wagelaar CLA 2018-11-19 08:03:26 EST
4.0.1M2 released. This has been built against ASM 7.0.
Comment 31 Eclipse Genie CLA 2018-12-12 14:31:57 EST
New Gerrit change created: https://git.eclipse.org/r/133954
Comment 33 Dennis Wagelaar CLA 2019-08-01 03:09:01 EDT
4.0.1 has been released a while back - closing.
Please reopen if this bug still exists in 4.0.1!