Re-index and "full checkout mode"

Hi all,

in Upsource 2.0 EAP (Build 2.0.3055), how can I
a) re-index a project after changing the project model? (in project configuration, it has multiple git locations btw)
b) switch on "full checkout mode" I've read about in an issue about maven? (https://youtrack.jetbrains.com/issue/UP-1484)

TIA,
Christian

0
13 comments

Hi Christian,

The answers on your questions are as follows:

a. It's not currently possible, howerver we do plan to add this functionality in the future versions.
b. It can be done with


<Upsource_home_dir>/lib/upsource-console.sh

p-set-checkout-mode

Let me know if it helps.

0
Avatar
Permanently deleted user

Well, actually I can't tell... if I can't reindex anything how can I learn if it works? I need to create the project before I can set it to "full" checkout mode. But as soon as I create it, upsource will start indexing with errors. New revisions don't seem to be processed after that either.
What should I do to repair/check it?

Regards,
Christian

0

Hi Christian,


You will see it in the newest revisions. The question here is why there are not shown in Upsource.. An answer should be in logs folder under Upsource home directory. Would you mind to post it here?

0
Avatar
Permanently deleted user

Ah well, they are shown. But neither did inspection work nor did it print a new error message about maven (like it did after creating the project). Even the "mvn.out" file did not exist like it did after the former error message.
After fiddling around with the project setting a bit I just got the same error like before: a missing MANIFEST.MF file reported by maven. And yes, the files does not exist in the tmp folder where it should be after checking out from git. Any other reason why the checkout could stay incomplete?

/Christian

0

Not aware of simple solution unfortunately.. Reviewing logs would be really helpful. You might upload a file via https://uploads.jetbrains.com/ form and let us know the exact file name.

Thanks in advance.

0
Avatar
Permanently deleted user

The exception in mvn.out looks like this:

[ERROR] Internal error: org.eclipse.tycho.core.osgitools.OsgiManifestParserException: Exception parsing OSGi MANIFEST /opt/upsource/Upsource2/temp/upsource-analyzer/upsource-tmp/projects/XY/maven-support/snapshot/XY/META-INF/MANIFEST.MF: Manifest file not found -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: org.eclipse.tycho.core.osgitools.OsgiManifestParserException: Exception parsing OSGi MANIFEST /opt/upsource/Upsource2/temp/upsource-analyzer/upsource-tmp/projects/XY/maven-support/snapshot/XY/META-INF/MANIFEST.MF: Manifest file not found
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.eclipse.tycho.core.osgitools.OsgiManifestParserException: Exception parsing OSGi MANIFEST /opt/upsource/Upsource2/temp/upsource-analyzer/upsource-tmp/projects/XY/maven-support/snapshot/XY/META-INF/MANIFEST.MF: Manifest file not found
at org.eclipse.tycho.core.osgitools.DefaultBundleReader.loadManifestFromDirectory(DefaultBundleReader.java:94)
at org.eclipse.tycho.core.osgitools.DefaultBundleReader.doLoadManifest(DefaultBundleReader.java:58)
at org.eclipse.tycho.core.osgitools.DefaultBundleReader.loadManifest(DefaultBundleReader.java:49)
at org.eclipse.tycho.core.osgitools.OsgiBundleProject.readArtifactKey(OsgiBundleProject.java:140)
at org.eclipse.tycho.core.osgitools.OsgiBundleProject.setupProject(OsgiBundleProject.java:135)
at org.eclipse.tycho.core.resolver.DefaultTychoResolver.setupProject(DefaultTychoResolver.java:74)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:72)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:310)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
... 11 more

I've uploaded the upsource-stderr and stdout.log via your link as log.zip, but did not get a link to post here.

/Christian

0

Hi Christian,

Sorry for the delayed response.

It seems that "full checkout mode" is not set correctly, the reason here might be my lackluster instructions. Command p-set-checkout-mode should be run with two arguments - <project name>, <value>. So in your case the steps should be as follows:

1. Run Upsource console with <Upsource_home_dir>/lib/upsource-console.sh


2. Run the following command: p-set-checkout-mode XY all


where XY - name of your project.

To check that settings were applied correctly you might want to make a backup of your data (corresponding help page - https://www.jetbrains.com/upsource/help/1.0/backup.html), then navigate to <Upsource_home_dir>/backups/<date_of_backup>/data/.backup open projects.xml file and check that <checkoutMode>all</checkoutMode> string appeared in the corresponding project block.

Please let me know if it helps.

0
Avatar
Permanently deleted user

Yes, that's what I found out from the command line help es well. So it's exactly the command I executed and which returned without error.

0
Avatar
Permanently deleted user

Well, but the checkout-mode was not set. For another project it was... maybe it's because of a dash in the project name? I'll try to set it again.

0
Avatar
Permanently deleted user

Ok, worked out when using the id not the name (but with name it did not print an error). I'll report back after the next revision is analyzed.

0

Unfortunately it happens, in the current version we do not show errors directly in the console. A thing to improve for the further releases.

Please let us know about the results.

0
Avatar
Permanently deleted user

Nice it works!

Only problem remaining: JavaFX classes are not found, which makes some classes really red :)
Any clues for this one, or should I start a new thread?

Regards and thanks,
Christian

0

Glad to hear that :)

As for JavaFX, it's not supported yet, however you might be interested in upvoting this feature request https://youtrack.jetbrains.com/issue/UP-4049

Thanks in advance.

0

Please sign in to leave a comment.