IncompatibleAssessmentException when user tries to submit a C/C++ Eclipse project as part of a package that originally had some Java package type

[mdreid]

When a user configures a C/C++ project that hasn't been previously assessed, the plug-in thinks it has a Java package type even when C/C++ is selected.

[mdreid]

This is not the actual issue. The actual issue is that for already created packages, we should not allow a change in package type!

Likewise, we should do some checking that if the Eclipse project is a C or C++ project, the user isn't trying to submit it as a java SWAMP package and vice versa.

[mdreid]

Talked to Jim, and he said that this workflow should work. I further investigated and found that the SwampApiWrapper does some checks that the tools and package type are compatible and uses the package type from the PackageThing. This means if a user first created a Java 8 Source Code package and then tries to submit a C/C++ Eclipse project, it will always fail.

Vamshi will look into this more

[mdreid]

This doesn't currently work. Workaround will be to create a new package behind the scenes with the new package type.