TOS for Data Integration version: 6.3.0
Let's says there's a routine that needs a external lib (i.e. commons lang).
I would like to make maven download this lib (I don't want to add it manually with right click, add etc..).
The goal is to make the project more 'team friendly'.
I tried to modify the pom dependencies here: 'project properties' > build > Maven > Default > Project
But is doesn't work.
Any idea how to do this?
Thank you.
use tLibraryLoad.
You may also be able to put the tLibraryLoad in a joblet along with other initialization items, and make using the joblet a standard part of each job template so that individual developers do not have to put thought into it. We do that for out initialization items, but I have not tried it with a tLibraryLoad.
Related
I am using a dependency and I have some issues with it.
I could download the sources and include it as part of my project and then start modifying the source to help me debug my issue.
However, is there an easier way to do this, using maven ? I have the source-jars downloaded but I am not sure if I can then use these source jars and modify the code as well ?
I could in theory unbar the sources and add them to my source build path, but is there an easier way to accomplish this ?
I am using maven and IntelliJ.
Are you able to get a successful build of the dependency you're having issues with (in it's own project?).
If so, change the version, e.g. 1.2.3-CUSTOM-1, make the improvements, rebuild, and use it as a proper maven depdendency with <version>1.2.3-CUSTOM-1</version>.
This might seem a lot of work, but it's not really - you end up with a properly versioned jar.... having a "hacked" version of 1.2.3 jar is asking for all sorts of problems later.
On the plus side, you can share and deploy the -CUSTOM-1 jar if you need to, and you can keep versioning -CUSTOM-2, etc.
This is the "proper way" I would say.
As Thorbjørn Ravn Andersen wrote, source jars are read-only. You can setup debugger breakpoints in them, but you can't "write" in them
Either unjar the sourced jar or if you know it came from a git release tag, clone the original repository and checkout the correct tag
Make sure its sources compile
Bump up the version in case you know you are going to hack the source
On the right pane, use Maven projects / Plus icon to add sources and use the "m" Execute goal icon to build the sources in IDEA :
i know there are 2 methode to create project with Maven.
Create Dynamic project on eclipse and convert it into maven project
Create Maven project with command line and then import the project into eclips.
i always do the 1. choise.
If You have latest eclipse IDE then its very simple.
Go to Create new Project wizard and search maven project. (if its old eclipse IDE then you probably need to install m2e plug in from market place).
select maven project and next. Check (Create a simple project) if you want customization other wise just click Next and You will be presented a number of ready made archtypes.
For simple console projects you can chose maven-archtype-quickstart. or what ever project you want to create.
Now Give groupId e.g. com.yourcompany or com.yourprojectgroup and artifactId e.g. projectname-alias . and Click Finish.
First Time eclipse will create local repo if its not already created and then put default dependencies defined by provided pom in your local repo. Further you just need maven knowledge to customize project. e.g. New Dependencies and build system etc.
I hope this will clear your mind. I prefer this way because its fast and easy.
If you create a new project in Eclipse (at least in Mars or Neon), you can choose "Maven Project" and get everything you need. Don't use eclipse goals of Maven. They are deprecated.
I'm trying to do this getting started guide from Spring. So I cloned the project using git from the command line. As I'm working with Gradle, I removed the Maven files from the repository to clean the project.
After that I open my STS and go to File -> Open Projects from File System and navigate to the /initial folder of the repository. The project is imported correctly but when I try to add some "java stuff" (packages, classes, etc.) I get several errors and I can only add folders and files, which is quite annoying for working.
To be more descriptive, I'll add some images so you can see what's happening. This is the project initially imported into STS as I described above:
Then I try to add some java stuff, let's say for example a source folder. So Right Click on library -> New -> Source folder and this is the result:
And in the properties of library I have the following:
So the question is: how can I tell to STS to recognize the library folder as a Java Project (or Gradle module, I don't know how to call it) instead of a plain folder so I can add my packages and classes?
Thanks in advance for your answers.
In case you would like to work with Gradle, you should use the Gradle integration for Eclipse (project Buildship) and install that into your STS environment. After that, you should be able to import the projects either from disc as existing Gradle project (not as file system) or via the wizard that integrates the spring guides into STS (Import Getting Started Content). The wizard for the guides also let you choose between the Maven and the Gradle variant, so you don't need to close and delete stuff yourself.
Hope this helps!!!
I am requested to port one of a biggest project to maven it has almost 200 - 300 libraries. Do i need to search in http://search.maven.org manually and update it or is there any other way to do it?
This is sort of maybe OT here depending on your perspective. But one solution is to, using NetBeans, load your project source into a blank Maven project (using a standard Maven layout), and right click all of the unresolved symbols, choosing the context option "Search Maven repository"...
It will allow you to add the correct dependency and update your pom.xml for you.
The catch is you have to be certain the version of the class is the one you want. It's not going to be an automated precoess and you'll have to do lots of integration testing... but that should get you started.
I'm trying to create an Eclipse (3.x) RCP application from plugins in such a way as to allow me to provide ordinary plugins for existing Eclipse installations, but also create an RCP application from those plugins.
My experimentation has led me to have the following layout:
com.company.testapp.plugin
com.company.testapp.feature
com.company.testapp.updatesite
Where each ID depends on the previous one. This works correctly and I can build an update site from the plugin via the feature. What I would now like to do is add something like
com.company.testapp.rcp
Containing just the required machinery to provide an RCP 'wrapper' around the feature. com.company.testapp.rcp contains a product definition, testapp.product.
However, I can't seem to make this link work; I'm getting "Product com.company.testapp.rcp.product could not be found" on trying to launch from the product configuration.
(Ultimately, I'd like to be able to drive the creation of both the update site and RCP application from Maven/Tycho—I have another com.company.testapp.master containing the master POM which I can again successfully build the update site from.)
I've found plenty of resources on building plugins with Tycho, and plenty on building RCP applications, but nothing on building both from the same source tree. I'm not an Eclipse or Tycho expert by any means, so it's possible I'm just not aware of what I should be searching for.
Is such a thing even possible?
Instead of com.company.testapp.updatesite (and com.company.testapp.rcp) create a new module: com.company.testapp.repository that defines a product and p2 repository (a replacement for old update-site mechanism). The module should have the following files:
category.xml where you define features in p2 repository and their categories (in your case com.company.testapp.feature)
*.product - a product definition file
pom.xml file that defines eclipse-repository module; detailed configuration is explained at Tycho Packaging Types - eclipse-repository