Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Oomph setup script does not complete #397

Closed
konfri opened this issue Dec 1, 2017 · 16 comments
Closed

Oomph setup script does not complete #397

konfri opened this issue Dec 1, 2017 · 16 comments

Comments

@konfri
Copy link

konfri commented Dec 1, 2017

Hey,

I've tried to setup the groovy plugin workspace but I wasn't able to complete successfully due to some missing dependencies.

screen shot 2017-12-01 at 18 07 45

I've tried Neon as well as Oxygen as target but both didn't work.

Best regards,
Kon

@eric-milles
Copy link
Member

Oh, yes, the tests require the "org.eclipse.test" feature now. Let me see if I can add that to the setup.

@konfri
Copy link
Author

konfri commented Dec 1, 2017

That would be great :)

@eric-milles
Copy link
Member

Should be okay now

@konfri
Copy link
Author

konfri commented Dec 3, 2017

Hey,

thank you for you effort :) I retried the setup with the default entry given by the eclipse installer. I still did not finish completely without dependencies issues. As I'm not sure if the update of the setup file is immediately visible, I downloaded the setup file (including your changes) and tried to executed the installer with the local file.

screen shot 2017-12-03 at 13 06 54

I had to use a different name due to naming conflict with the default one just for the try. But unfortunately it did not complete successfully :(

@eric-milles
Copy link
Member

eric-milles commented Dec 4, 2017 via email

@eric-milles eric-milles reopened this Dec 4, 2017
@felixdo
Copy link
Contributor

felixdo commented Dec 4, 2017 via email

@konfri
Copy link
Author

konfri commented Dec 4, 2017

It's basically the dependency issue that I mentioned in the first post. Thanks for investigating it @felixdo :)

@eric-milles
Copy link
Member

eric-milles commented Dec 4, 2017 via email

@felixdo
Copy link
Contributor

felixdo commented Dec 4, 2017 via email

@konfri
Copy link
Author

konfri commented Dec 4, 2017

Yes, the same issue remains. Just tried on a different machine with the default entry from "Eclipse IDE for Eclipse Committers" -> "Groovy-Eclipse"

2017-12-04 19_40_51-eclipse updater

felixdo added a commit to felixdo/groovy-eclipse that referenced this issue Dec 4, 2017
felixdo added a commit to felixdo/groovy-eclipse that referenced this issue Dec 4, 2017
* The org.eclipse.test feature doesn't need to be installed into the
IDE, so I removed that.
* We only need to make sure that the feature can be found when the
target platform is resolved, so I added the required p2 repos to the
relevant repository lists.

Signed-off-by: Felix Dorner <[email protected]>
@felixdo
Copy link
Contributor

felixdo commented Dec 4, 2017

Konfri, if you replace the groovy-eclipse.setup file in your git clone with the one I just committed here felixdo@44c599c and then try to 'Help->Perform Setup Tasks', does it complete?

If it does, then I'll create a pull request for Eric. You can then also safely uninstall the org.eclipse.test feature via Help->About Eclipse->Installation Details...

Explanation: For testing changes to .setup files, there is a mechanism that works like this: In your eclipse.ini there should be a line that says something like

-Doomph.redirection.Groovy-Eclipse=https://raw.githubusercontent.com/groovy/groovy-eclipse/master/groovy-eclipse.setup->file:/C:/develop/groovy-eclipse/git/groovy-eclipse/groovy-eclipse.setup
This means that the local .setup contents will be used when oomph tries to execute the groovy-eclipse setup, effectively overriding the contents of the file in our master branch on github. That's how to test modifications to the setup before publishing them.

@konfri
Copy link
Author

konfri commented Dec 4, 2017

@felixdo thanks for the PL. Works now :)

@felixdo
Copy link
Contributor

felixdo commented Dec 4, 2017

As a sidenote.. when I run the installer, I still cannot see erics changes from over 10 weeks ago. For example, I still get greclipse 4.6 in my IDE even if the setup now asks for 4.7. Can you check under Help->About->Installation Details if it sais e46 or e47 under the groovy features (for example check the groovy jdt patch)

@konfri
Copy link
Author

konfri commented Dec 4, 2017

It is set to 4.7 but I must admit that I've selected Oxygen :)

screen shot 2017-12-04 at 23 56 24

@felixdo
Copy link
Contributor

felixdo commented Dec 5, 2017

@eric-milles even if it apparently works now, there's still another issue with the setup. I will check and come back to you.

felixdo added a commit to felixdo/groovy-eclipse that referenced this issue Dec 5, 2017
felixdo added a commit to felixdo/groovy-eclipse that referenced this issue Dec 5, 2017
* The org.eclipse.test feature doesn't need to be installed into the
IDE, so I removed that.
* We only need to make sure that the feature can be found when the
target platform is resolved, so I added the required p2 repos to the
relevant repository lists.

Signed-off-by: Felix Dorner <[email protected]>
@felixdo felixdo mentioned this issue Dec 5, 2017
@konfri
Copy link
Author

konfri commented Dec 5, 2017

As my issues has been fix, I will close this :)

@konfri konfri closed this as completed Dec 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants