Moving from Maven to Gradle integration requires removing all the .project files resulting in empty change sets on the Rational Team Concert SCM side.

1	Ben Tran (160●1●8) \| asked Mar 17 '16, 3:58 p.m. edited Mar 17 '16, 3:58 p.m. There is an issue when moving from Maven to Gradle that for any of the referenced projects that are linked to the master-module results in any new changes showing up empty under Pending Changes.

Accepted answer

permanent link

Rafael Hayama (159●2●6) | answered Mar 17 '16, 4:00 p.m.

In order to overcome this we need to use the workspace that we had worked on previously and had not imported in via the gradle plugin but had ran the gradle init and had cleaned out the existing pom files and .project files - C:\workspaces\Maven-FX_IntegrationWorkspace_gradle in order to be able to get this to share in RTC. Don’t modify anything and had RTC create the ignored resources for us when going through and ignoring files.

We then need to unloaded the workspace and reloaded. It should throw an error message since when doing the gradle import it looks for a gradle.prefs at the powersuitefx-master-module level

Therefore, we need to copy from another workspace and modify the path to be the workspace that was working in. We will need to look at that for the future and might just require everyone to copy in the specific info in the gradle.prefs

{

"1.0": {

"project_path": ":",

"project_dir": "C:\\workspaces\\FXTestwithRTC601Version\\powersuitefx-master-module",

"connection_project_dir": "C:\\workspaces\\FXTestwithRTC601Version\\powersuitefx-master-module",

"connection_gradle_user_home": null,

"connection_gradle_distribution": "GRADLE_DISTRIBUTION(WRAPPER)",

"connection_java_home": null,

"connection_jvm_arguments": "",

"connection_arguments": ""

}

}

Additionally, it made modifications to the master-module.proj where it added in a bunch of ids. I undid those changes and might have to add this .project to the ignored resources. We should be able to check in other subproject files with no issues when having the .project file look the way it is suppose to.

It appears that it does this everytime you import the gradle project. So more effort will need to go into this and determine why this is happening.

Here's the .project before

<projectdescription>

<name>powersuitefx-master-module</name>

<comment></comment>

<projects>

</projects>

<buildspec>

<buildcommand>

<name>org.eclipse.m2e.core.maven2Builder</name>

<arguments>

</arguments>

</buildcommand>

<buildcommand>

<name>org.eclipse.buildship.core.gradleprojectbuilder</name>

<arguments>

</arguments>

</buildcommand>

</buildspec>

<natures>

<nature>org.eclipse.m2e.core.maven2Nature</nature>

<nature>org.eclipse.buildship.core.gradleprojectnature</nature>

</natures>

</projectdescription>

Here's the .project after

<projectdescription>

<name>powersuitefx-master-module</name>

<comment></comment>

<projects>

</projects>

<buildspec>

<buildcommand>

<name>org.eclipse.m2e.core.maven2Builder</name>

<arguments>

</arguments>

</buildcommand>

<buildcommand>

<name>org.eclipse.buildship.core.gradleprojectbuilder</name>

<arguments>

</arguments>

</buildcommand>

</buildspec>

<natures>

<nature>org.eclipse.m2e.core.maven2Nature</nature>

<nature>org.eclipse.buildship.core.gradleprojectnature</nature>

</natures>

<filteredresources>

<filter>

<id>1456182141084</id>

<name></name>

<type>26</type>

<matcher>

<id>org.eclipse.ui.ide.multiFilter</id>

<arguments>1.0-projectRelativePath-matches-false-false-javafx-claims</arguments>

</matcher>

</filter>

<filter>

<id>1456182141093</id>

<name></name>

<type>26</type>

<matcher>

<id>org.eclipse.ui.ide.multiFilter</id>

<arguments>1.0-projectRelativePath-matches-false-false-javafx-contentmanagement</arguments>

</matcher>

</filter>

<filter>

<id>1456182141098</id>

<name></name>

<type>26</type>

<matcher>

<id>org.eclipse.ui.ide.multiFilter</id>

<arguments>1.0-projectRelativePath-matches-false-false-javafx-customer</arguments>

</matcher>

</filter>

<filter>

<id>1456182141103</id>

<name></name>

<type>26</type>

<matcher>

<id>org.eclipse.ui.ide.multiFilter</id>

<arguments>1.0-projectRelativePath-matches-false-false-javafx-financials</arguments>

</matcher>

</filter>

<filter>

<id>1456182141108</id>

<name></name>

<type>26</type>

<matcher>

<id>org.eclipse.ui.ide.multiFilter</id>

<arguments>1.0-projectRelativePath-matches-false-false-javafx-framework</arguments>

</matcher>

</filter>

<filter>

<id>1456182141113</id>

<name></name>

<type>26</type>

<matcher>

<id>org.eclipse.ui.ide.multiFilter</id>

<arguments>1.0-projectRelativePath-matches-false-false-javafx-mstech-viewer</arguments>

</matcher>

</filter>

<filter>

<id>1456182141119</id>

<name></name>

<type>26</type>

<matcher>

<id>org.eclipse.ui.ide.multiFilter</id>

<arguments>1.0-projectRelativePath-matches-false-false-javafx-policy</arguments>

</matcher>

</filter>

<filter>

<id>1456182141124</id>

<name></name>

<type>26</type>

<matcher>

<id>org.eclipse.ui.ide.multiFilter</id>

<arguments>1.0-projectRelativePath-matches-false-false-powersuite-app</arguments>

</matcher>

</filter>

<filter>

<id>1456182141131</id>

<name></name>

<type>26</type>

<matcher>

<id>org.eclipse.ui.ide.multiFilter</id>

<arguments>1.0-projectRelativePath-matches-false-false-build</arguments>

</matcher>

</filter>

<filter>

<id>1456182141137</id>

<name></name>

<type>26</type>

<matcher>

<id>org.eclipse.ui.ide.multiFilter</id>

<arguments>1.0-projectRelativePath-matches-false-false-.gradle</arguments>

</matcher>

</filter>

</filteredresources>

</projectdescription>

Check in this version and we should have the same issue where we could not check in files any longer and they showed up blank.

Undoing these changes is going to throw another error saying it doesn't exist.

To overcome this we need to reload the workspace and make sure that the .project file is not modified. It should work afterwards.

Ben Tran selected this answer as the correct answer

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

It's all about the answers!

Related questions

Moving from Maven to Gradle integration requires removing all the .project files resulting in empty change sets on the Rational Team Concert SCM side.

Accepted answer

Your answer