一：源码打包
这里为什么是kettle 9.2，因为kettle 9.3+需要jdk11
这里直接去下载kettle的源码，tag=9.2.0.4-R。这里需要自己搭建一个nexus仓库，因为有些包从kettle的仓库里面下载不下来。
nexus新建仓库代理, 记得加到public里面去
https://repo.orl.eng.hitachivantara.com/artifactory/pnt-mvn/
完整的settings.xml
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
| This is the configuration file for Maven. It can be specified at two levels:
|
| 1. User Level. This settings.xml file provides configuration for a single user,
| and is normally provided in ${user.home}/.m2/settings.xml.
|
| NOTE: This location can be overridden with the CLI option:
|
| -s /path/to/user/settings.xml
|
| 2. Global Level. This settings.xml file provides configuration for all Maven
| users on a machine (assuming they're all using the same Maven
| installation). It's normally provided in
| ${maven.conf}/settings.xml.
|
| NOTE: This location can be overridden with the CLI option:
|
| -gs /path/to/global/settings.xml
|
| The sections in this sample file are intended to give you a running start at
| getting the most out of your Maven installation. Where appropriate, the default
| values (values used when the setting is not specified) are provided.
|
|-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<!-- localRepository
| The path to the local repository maven will use to store artifacts.
|
| Default: ${user.home}/.m2/repository
<localRepository>/path/to/local/repo</localRepository>
-->
<localRepository>D:/tools/maven/apache-maven-3.6.3/conf/repository</localRepository>
<!-- interactiveMode
| This will determine whether maven prompts you when it needs input. If set to false,
| maven will use a sensible default value, perhaps based on some other setting, for
| the parameter in question.
|
| Default: true
<interactiveMode>true</interactiveMode>
-->
<!-- offline
| Determines whether maven should attempt to connect to the network when executing a build.
| This will have an effect on artifact downloads, artifact deployment, and others.
|
| Default: false
<offline>false</offline>
-->
<!-- pluginGroups
| This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
| when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
| "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
|-->
<pluginGroups>
<!-- pluginGroup
| Specifies a further group identifier to use for plugin lookup.
<pluginGroup>com.your.plugins</pluginGroup>
-->
<pluginGroup>org.pentaho.maven.plugins</pluginGroup>
<pluginGroup>com.pentaho.maven.plugins</pluginGroup>
<pluginGroup>com.github.spotbugs</pluginGroup>
</pluginGroups>
<!-- proxies
| This is a list of proxies which can be used on this machine to connect to the network.
| Unless otherwise specified (by system property or command-line switch), the first proxy
| specification in this list marked as active will be used.
|-->
<proxies>
<!-- proxy
| Specification for one proxy, to be used in connecting to the network.
|
<proxy>
<id>optional</id>
<active>true</active>
<protocol>http</protocol>
<username>proxyuser</username>
<password>proxypass</password>
<host>proxy.host.net</host>
<port>80</port>
<nonProxyHosts>local.net|some.host.com</nonProxyHosts>
</proxy>
-->
</proxies>
<!-- servers
| This is a list of authentication profiles, keyed by the server-id used within the system.
| Authentication profiles can be used whenever maven must make a connection to a remote server.
|-->
<servers>
<!-- server
| Specifies the authentication information to use when connecting to a particular server, identified by
| a unique name within the system (referred to by the 'id' attribute below).
|
| NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
| used together.
|
<server>
<id>deploymentRepo</id>
<username>repouser</username>
<password>repopwd</password>
</server>
-->
<!-- Another sample, using keys to authenticate.
<server>
<id>siteServer</id>
<privateKey>/path/to/private/key</privateKey>
<passphrase>optional; leave empty if not used.</passphrase>
</server>
-->
<server>
<id>pentaho-public</id>
<username>devreaduser</username>
<password>{zIMyJWfHKfoHiBJAVsAgW4E5BcJzR+nhTtgPy0J+/rs=}</password>
</server>
</servers>
<!-- mirrors
| This is a list of mirrors to be used in downloading artifacts from remote repositories.
|
| It works like this: a POM may declare a repository to use in resolving certain artifacts.
| However, this repository may have problems with heavy traffic at times, so people have mirrored
| it to several places.
|
| That repository definition will have a unique id, so we can create a mirror reference for that
| repository, to be used as an alternate download site. The mirror site will be the preferred
| server for that repository.
|-->
<mirrors>
<!-- mirror
| Specifies a repository mirror site to use instead of a given repository. The repository that
| this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
| for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
|
<mirror>
<id>mirrorId</id>
<mirrorOf>repositoryId</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://my.repository.com/repo/path</url>
</mirror>
-->
<mirror>
<id>mirrorId</id>
<mirrorOf>*</mirrorOf>
<name>maven-public</name>
<url>http://172.16.30.203:8081/repository/maven-public/</url>
</mirror>
</mirrors>
<!-- profiles
| This is a list of profiles which can be activated in a variety of ways, and which can modify
| the build process. Profiles provided in the settings.xml are intended to provide local machine-
| specific paths and repository locations which allow the build to work in the local environment.
|
| For example, if you have an integration testing plugin - like cactus - that needs to know where
| your Tomcat instance is installed, you can provide a variable here such that the variable is
| dereferenced during the build process to configure the cactus plugin.
|
| As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
| section of this document (settings.xml) - will be discussed later. Another way essentially
| relies on the detection of a system property, either matching a particular value for the property,
| or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
| value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
| Finally, the list of active profiles can be specified directly from the command line.
|
| NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
| repositories, plugin repositories, and free-form properties to be used as configuration
| variables for plugins in the POM.
|
|-->
<profiles>
<!-- profile
| Specifies a set of introductions to the build process, to be activated using one or more of the
| mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
| or the command line, profiles have to have an ID that is unique.
|
| An encouraged best practice for profile identification is to use a consistent naming convention
| for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
| This will make it more intuitive to understand what the set of introduced profiles is attempting
| to accomplish, particularly when you only have a list of profile id's for debug.
|
| This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
<profile>
<id>jdk-1.4</id>
<activation>
<jdk>1.4</jdk>
</activation>
<repositories>
<repository>
<id>jdk14</id>
<name>Repository for JDK 1.4 builds</name>
<url>http://www.myhost.com/maven/jdk14</url>
<layout>default</layout>
<snapshotPolicy>always</snapshotPolicy>
</repository>
</repositories>
</profile>
-->
<!--
| Here is another profile, activated by the system property 'target-env' with a value of 'dev',
| which provides a specific path to the Tomcat instance. To use this, your plugin configuration
| might hypothetically look like:
|
| ...
| <plugin>
| <groupId>org.myco.myplugins</groupId>
| <artifactId>myplugin</artifactId>
|
| <configuration>
| <tomcatLocation>${tomcatPath}</tomcatLocation>
| </configuration>
| </plugin>
| ...
|
| NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
| anything, you could just leave off the <value/> inside the activation-property.
|
<profile>
<id>env-dev</id>
<activation>
<property>
<name>target-env</name>
<value>dev</value>
</property>
</activation>
<properties>
<tomcatPath>/path/to/tomcat/instance</tomcatPath>
</properties>
</profile>
-->
<profile>
<id>nexus</id>
<repositories>
<repository>
<id>nexus-snapshots</id>
<url>http://172.16.30.203:8081/repository/maven-snapshots/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
</snapshots>
</repository>
<repository>
<id>nexus-releases</id>
<url>http://172.16.30.203:8081/repository/maven-releases/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>snapshots</id>
<url>http://172.16.30.203:8081/repository/maven-snapshots/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>nexus-releases</id>
<url>http://172.16.30.203:8081/repository/maven-releases/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<!-- activeProfiles
| List of profiles that are active for all builds.
|
<activeProfiles>
<activeProfile>alwaysActiveProfile</activeProfile>
<activeProfile>anotherAlwaysActiveProfile</activeProfile>
</activeProfiles>
-->
<activeProfiles>
<activeProfile>nexus</activeProfile>
</activeProfiles>
</settings>
idea导入kettle，等待下载maven依赖，慢慢等，需要很长的时间。
这个包在kettle的远程仓库也没有，可以直接去掉
有些包在kettle的远程仓库有，但是下载不下来，解决方案是手动下载，然后上传到自己的maven仓库
这里需要删除本地的文件，上传再重新下载
maven依赖下载成功了，idea上maven依赖还是红色的，这是idea的bug，解决方案为pom.xml去掉依赖，maven刷新，再加上依赖，maven刷新。
maven依赖下载成功，打包一般没问题
解压，双击Spoob.bat即可使用
二：idea开发环境启动
新建application
- 错误一
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
no swt-gtk-4623 in java.library.path
no swt-gtk in java.library.path
Can't load library: C:\Users\Administrator\.swt\lib\win32\x86_64\swt-gtk-4623.dll
Can't load library: C:\Users\Administrator\.swt\lib\win32\x86_64\swt-gtk.dll
解决办法：
然后在ui的pom.xml添加依赖
<dependency>
<groupId>com.swt</groupId>
<artifactId>swt</artifactId>
<version>1.0.0</version>
<scope>system</scope>
<systemPath>${project.basedir}/lib/swt.jar</systemPath>
</dependency>
- 错误二：
org.pentaho.di.core.exception.KettleException:
Unable to find plugin with ID 'Kettle'. If this is a test, make sure kettle-core tests jar is a dependency. If this is live make sure a kettle-password-encoder-plugins.xml exits in the classpath
at org.pentaho.di.core.encryption.Encr.init(Encr.java:61)
at org.pentaho.di.core.KettleClientEnvironment.init(KettleClientEnvironment.java:124)
at org.pentaho.di.core.KettleClientEnvironment.init(KettleClientEnvironment.java:80)
at org.pentaho.di.core.KettleEnvironment.init(KettleEnvironment.java:134)
at org.pentaho.di.core.KettleEnvironment.init(KettleEnvironment.java:101)
at org.pentaho.di.core.KettleEnvironment.init(KettleEnvironment.java:82)
at org.pentaho.di.ui.spoon.Spoon$1.call(Spoon.java:643)
- 错误三：
2022/11/23 18:23:44 - General - ERROR (version Unknown, build 0 from 2022/11/23 18:23:42.892 by Administrator) : Error initializing transformation
2022/11/23 18:23:44 - General - ERROR (version Unknown, build 0 from 2022/11/23 18:23:42.892 by Administrator) : org.pentaho.ui.xul.XulException: Can not locate Xul document [ui/spoon.xul]
2022/11/23 18:23:44 - General - at org.pentaho.ui.xul.impl.AbstractXulLoader.findDocument(AbstractXulLoader.java:512)
2022/11/23 18:23:44 - General - at org.pentaho.ui.xul.impl.AbstractXulLoader.loadXul(AbstractXulLoader.java:229)
2022/11/23 18:23:44 - General - at org.pentaho.di.ui.spoon.Spoon.init(Spoon.java:870)
2022/11/23 18:23:44 - General - at org.pentaho.di.ui.spoon.Spoon.createContents(Spoon.java:9352)
2022/11/23 18:23:44 - General - at org.eclipse.jface.window.Window.create(Window.java:431)
2022/11/23 18:23:44 - General - at org.eclipse.jface.window.Window.open(Window.java:788)
2022/11/23 18:23:44 - General - at org.pentaho.di.ui.spoon.Spoon.start(Spoon.java:9383)
2022/11/23 18:23:44 - General - at org.pentaho.di.ui.spoon.Spoon.main(Spoon.java:711)
2022/11/23 18:23:44 - General - ERROR (version Unknown, build 0 from 2022/11/23 18:23:42.892 by Administrator) : Error starting Spoon shell
2022/11/23 18:23:44 - General - ERROR (version Unknown, build 0 from 2022/11/23 18:23:42.892 by Administrator) : java.lang.NullPointerException
2022/11/23 18:23:44 - General - at org.pentaho.di.ui.spoon.Spoon.init(Spoon.java:923)
2022/11/23 18:23:44 - General - at org.pentaho.di.ui.spoon.Spoon.createContents(Spoon.java:9352)
2022/11/23 18:23:44 - General - at org.eclipse.jface.window.Window.create(Window.java:431)
2022/11/23 18:23:44 - General - at org.eclipse.jface.window.Window.open(Window.java:788)
2022/11/23 18:23:44 - General - at org.pentaho.di.ui.spoon.Spoon.start(Spoon.java:9383)
2022/11/23 18:23:44 - General - at org.pentaho.di.ui.spoon.Spoon.main(Spoon.java:711)
- 错误四
2022/11/23 18:27:07 - General - ERROR (version Unknown, build 0 from 2022/11/23 18:27:05.372 by Administrator) : Error starting Spoon shell
2022/11/23 18:27:07 - General - ERROR (version Unknown, build 0 from 2022/11/23 18:27:05.372 by Administrator) : java.lang.NoClassDefFoundError: org/jaxen/JaxenException
2022/11/23 18:27:07 - General - at org.pentaho.ui.xul.impl.AbstractXulLoader.preProcess(AbstractXulLoader.java:357)
2022/11/23 18:27:07 - General - at org.pentaho.ui.xul.impl.AbstractXulLoader.loadXul(AbstractXulLoader.java:113)
2022/11/23 18:27:07 - General - at org.pentaho.ui.xul.swt.SwtXulLoader.loadXul(SwtXulLoader.java:128)
2022/11/23 18:27:07 - General - at org.pentaho.ui.xul.swt.SwtXulLoader.loadXul(SwtXulLoader.java:122)
2022/11/23 18:27:07 - General - at org.pentaho.ui.xul.impl.AbstractXulLoader.loadXul(AbstractXulLoader.java:239)
2022/11/23 18:27:07 - General - at org.pentaho.di.ui.spoon.Spoon.init(Spoon.java:870)
2022/11/23 18:27:07 - General - at org.pentaho.di.ui.spoon.Spoon.createContents(Spoon.java:9352)
2022/11/23 18:27:07 - General - at org.eclipse.jface.window.Window.create(Window.java:431)
2022/11/23 18:27:07 - General - at org.eclipse.jface.window.Window.open(Window.java:788)
2022/11/23 18:27:07 - General - at org.pentaho.di.ui.spoon.Spoon.start(Spoon.java:9383)
2022/11/23 18:27:07 - General - at org.pentaho.di.ui.spoon.Spoon.main(Spoon.java:711)
2022/11/23 18:27:07 - General - Caused by: java.lang.ClassNotFoundException: org.jaxen.JaxenException
2022/11/23 18:27:07 - General - at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
2022/11/23 18:27:07 - General - at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
2022/11/23 18:27:07 - General - at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
2022/11/23 18:27:07 - General - at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
ui添加依赖
<dependency>
<groupId>jaxen</groupId>
<artifactId>jaxen</artifactId>
</dependency>
启动成功
