guide_dev_troubleshooting

Troubleshooting for Developers

Table of Contents

• cobigen-eclipse or cobigen-eclipse-test has build errors after git clone or pull
  • Solution
• Getting Not authorized , ReasonPhrase: Unauthorized
  • Solution
• Testing changes on the cobigen-core
• Issues with workspace when Oomph automatic updates don’t work (especially for Indian colleagues)
  • Solution
• Issue when testing Eclipse plugin by Running as Eclipse Application.
  • Solution

cobigen-eclipse or cobigen-eclipse-test has build errors after git clone or pull

This might be caused as of the fact, that the cobigen-eclipse*/lib folder is not available after initial cloning or the contents of the lib folder are not synchonous with the dependencies specified in the pom.xml respectively with the classpath inclusions in the plugin.xml (tab runtime).

Solution

In any of these cases you can fix the issue by running a mvn clean package -Pp2-build-mars.

Getting Not authorized , ReasonPhrase: Unauthorized

You are facing an error like

[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Unresolveable build extension: Plugin org.apache.maven.wagon:wagon-ftp:1
.0-beta-6 or one of its dependencies could not be resolved: Failed to read artif
act descriptor for org.apache.maven.wagon:wagon-ftp:jar:1.0-beta-6 @
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project com.capgemini:cobigen-htmlplugin:1.1.0 (D:\toolscobigen\to
ols-cobigen2\tools-cobigen\cobigen\cobigen-htmlplugin\pom.xml) has 1 error
[ERROR]     Unresolveable build extension: Plugin org.apache.maven.wagon:wagon-f
tp:1.0-beta-6 or one of its dependencies could not be resolved: Failed to read a
rtifact descriptor for org.apache.maven.wagon:wagon-ftp:jar:1.0-beta-6: Could no
t transfer artifact org.apache.maven.wagon:wagon-ftp:pom:1.0-beta-6 from/to publ
ic (https://devon.s2-eu.capgemini.com/nexus/content/groups/public/): Not authori
zed , ReasonPhrase: Unauthorized. -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildin
gException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerE
xception

Solution

Please note the message Not authorized , ReasonPhrase: Unauthorized. → [Help 2]!

1. Please check, that you run the command by using the console.bat or a simliar console initialized with the IDE environment variables.

2. Please check your corporate login in the variables-customized.bat to be correct (DEVON_NEXUS_USER and DEVON_NEXUS_PASSWD). Make sure, that you restart the console.bat you are working in after changing the variables-customized.bat. Same holds for eclipse instances running. Please restart to make the new values accessible.

3. Please check your password to escape special characters.

4. Please check whether you are able to login to https://devon.s2-eu.capgemini.com and Nexus is up and running. If you cannot login, contact one of the main developers.

Testing changes on the cobigen-core

To test changes implemented on the cobigen-core you have to follow the next process:

1. Open a console and step into cobigen/cobigen-core-parent. Run mvn clean install and remember the jar version you have just installed.

2. Open a console and step into cobigen/cobigen-eclipse. Run mvn clean package -Pp2-build-mars.

3. On Eclipse, go to cobigen/cobigen-eclipse pom.xml and change the <version> of your cobigen-core.

4. Also check on the cobigen/cobigen-core-parent pom-xml that it is using the just installed version.

5. On Eclipse, go to cobigen/cobigen-eclipse and double-click 'plugins.xml'. On the bottom, click on 'runtime' tab. On 'classpath', add a new library and choose the jars you have just installed.

6. Refresh on Eclipse, press F5 on the cobigen-eclipse inside Eclipse.

7. If you still see compilation errors: On Eclipse, right-click cobigen/cobigen-eclipse → Maven → Update projects.

Issues with workspace when Oomph automatic updates don’t work (especially for Indian colleagues)

Executing eclipse-cobigen-development.bat file will open Eclipse with all the projects automatically imported. Oomph creates 'Working Sets' and set 'Top Level Elements' pointing to that working set. For Countries where proxy restricts Oomph to execute, we see no projects imported into project explorer/Navigator. Rather than trying manual import which later can give build issues we should follow below solution. Build Issues could be like:

[ERROR] Cannot resolve project dependencies:
[ERROR]   You requested to install 'com.capgemini.cobigen-htmlplugin 0.0.0' but it could not be found
[ERROR]
[ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
[ERROR] Cannot resolve dependencies of MavenProject: com.capgemini:com.capgemini.cobigen.eclipse.test:3.0.1 @

Solution

In Eclipse, you can click the small downward arrow in the upper right corner of the Navigator/Project Explorer view and go to 'Top Level Elements' and point them to 'Projects'. This should show all the projects inside Project Explorer View. Also, Each plugin should point to respective branch.

Issue when testing Eclipse plugin by Running as Eclipse Application.

Error message will be like:

1) Caused by: java.lang.ClassNotFoundException: An error occurred while automatically activating bundle com.devonfw.cobigen.eclipse
2) org.osgi.framework.BundleException: Error starting module.
3) org.eclipse.core.runtime.CoreException: Plug-in com.devonfw.cobigen.eclipse was unable to load class com.devonfw.cobigen.eclipse.workbenchcontrol.handler.XXXXHanlder.

Solution

Delete or rename the runtime-EclipseApplication inside workspaces folder. Re- run and try setting up workspace in that environment again. It should work!!