Hi Jeff,
it would be good to also include a more recent version of the Camel LSP
Eclipse client. I think I saw the version included atm is from Sep
2018.
https://github.com/camel-tooling/camel-lsp-client-eclipse-update-site/tre...
Lars
-------- Weitergeleitete Nachricht --------
Von: jmaury(a)redhat.com
An: jmaury(a)redhat.com, jbosstools-dev(a)lists.jboss.org
Betreff: [jbosstools-dev] Proposed 4.11.0.AM1-SNAPSHOT target platform
change(s): m2e; 1.10.0.20181127-2120
Datum: Sat, 05 Jan 2019 07:34:38 -0500
Here is a proposal for change(s) to the JBoss Tools / Red Hat Developer
Studio / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.11.0.AM1devstudio 12.11.0.AM1
jbt/ds TPs 4.11.0.AM1-SNAPSHOT central TPs 4.11.0.AM1-SNAPSHOT
Detail / Summary:
m2e;1.10.0.20181127-2120
Related JIRA(s):
https://issues.jboss.org/browse/JBIDE-26477
Pull Request(s):
(already merged - see related JIRA(s))
p2diff Report(s):
(will attach to JIRA when available)
----------
Please review the above changes, as they have been applied and are
building today.
Once the target platform is built, jobs and parent pom will be updated
to point TARGET_PLATFORM_VERSION_MAX at the new version, 4.11.0.AM1-
SNAPSHOT.
You can use the following to build & test the target platforms locally
againstyour component(s).
Build target-platform:
cd /path/to/jbosstools-target-platforms git fetch origin
pull/<pull-request-number>/head && git checkout FETCH_HEAD # or,
using hub for git git checkout <pull-request-URL>
mvn clean install -f jbosstools/multiple/pom.xml
Then, to test the new multiple target platform against your component's
build:
cd /path/to/your/jbosstools-component
mvn clean verify -Dtpc.version=4.11.0.AM1-SNAPSHOT -
Dtpc.targetKind=multiple For Central, fetch sources from
jbosstools-discovery, then build as above.
----------_______________________________________________jbosstools-dev
mailing listjbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev