Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
So, we are in the process of upgrading to TOS 7.2.1 from TOS 6.3.1.
In TOS 6.3.1, if I had to import any custom jars, I would start adding them via tLoadLibrary and it was the end of the story.
Coming to TOS 7.2.1, it looks like the functionality seems to have changed. When I go to tLibraryLoad, it asks me to select a jar.. I select the ellipsis and try to search for the jar. If it is not there, I go to the "Artifact repository lcoal m2/ nexus" and install a new module by browsing to the respective jar. All is well.
Now, lets say, I create a new project (Same workspace)... I go to tLibraryLoad... I cannot see the jar in the list (This happens randomly, sometimes I see it, other times I don't)... So, I go to "Artifact repository local m2/ nexus" and browse for that jar, it tells me "This module already installed with the selected maven URI, please set another custom URI."
So far, my workaround has been to go to my workspace/configuration/m2 folder and delete the respective jars and go through this routine.. it works but fails randomly.
What has changed/ what am I doing differently here? The TOS 7.2.1 documentation does not go through in detail about this.
How is the lcoal m2/ nexus repository supposed to work? I am tearing my head here and unable to figure out whats happening.
Any help is appreciated.
Hello,
What you see for me is more a bug / design issue.
Indeed, more things were added to link to the nexus / be more close to maven for the build way.
Please don't hesitate to create a Jira (in TUP project for this case), and explain your issue / what you would like to see.
We'll see if we can improve all of this in the next release.
Thanks,
Nicolas