Building forge from master fails to resolve org.jboss.forge.addon:addons:jar:forge-addon:2.0.0-SNAPSHOT
by Denis Golovin
I am trying to do local build for JBoss Tools and I cannot build forge
component it always fails on forge2 runtime plug-in.
[ERROR] Failed to execute goal
org.jboss.forge:forge-maven-plugin:1.0.0.Alpha4:addon-install
(deploy-addons) on project org.jboss.tools.forge2.runtime: Execution
deploy-addons of goal
org.jboss.forge:forge-maven-plugin:1.0.0.Alpha4:addon-install failed:
Could not resolve dependencies for addon
[org.jboss.forge.addon:addons:jar:forge-addon:2.0.0-SNAPSHOT]: Could not
find artifact org.jboss.forge.addon:addons:jar:forge-addon:2.0.0-SNAPSHOT
Addon seems to be deployed correctly in snapshot repository and works
fine as declared dependency
<dependencies>
<dependency>
<groupId>org.jboss.forge.addon</groupId>
<artifactId>addons</artifactId>
<version>${version.forge}</version>
<classifier>forge-addon</classifier>
</dependency>
</dependencies>
Running
mvn dependency:go-offline
gives successful build with output
....
[INFO] --- maven-dependency-plugin:2.4:go-offline (default-cli) @
org.jboss.tools.forge2.runtime ---
[INFO] Resolved: addons-2.0.0-SNAPSHOT-forge-addon.jar
[INFO] Resolved: addons-api-2.0.0-SNAPSHOT.jar
[INFO] Resolved: addons-impl-2.0.0-SNAPSHOT.jar
[INFO] Resolved: ui-2.0.0-SNAPSHOT-forge-addon.jar
[INFO] Resolved: ui-api-2.0.0-SNAPSHOT.jar
[INFO] Resolved: ui-impl-2.0.0-SNAPSHOT.jar
[INFO] Resolved: convert-2.0.0-SNAPSHOT-forge-addon.jar
[INFO] Resolved: convert-api-2.0.0-SNAPSHOT.jar
[INFO] Resolved: convert-impl-2.0.0-SNAPSHOT.jar
[INFO] Resolved: facets-2.0.0-SNAPSHOT-forge-addon.jar
[INFO] Resolved: facets-api-2.0.0-SNAPSHOT.jar
[INFO] Resolved: facets-impl-2.0.0-SNAPSHOT.jar
[INFO] Resolved: ui-spi-2.0.0-SNAPSHOT-forge-addon.jar
[INFO] Resolved: maven-2.0.0-SNAPSHOT-forge-addon.jar
[INFO] Resolved: maven-api-2.0.0-SNAPSHOT.jar
[INFO] Resolved: maven-model-3.0.5.jar
[INFO] Resolved: plexus-utils-2.0.6.jar
[INFO] Resolved: maven-impl-2.0.0-SNAPSHOT.jar
[INFO] Resolved: xml-parser-1.0.0.Final.jar
[INFO] Resolved: shrinkwrap-resolver-impl-maven-2.0.0-beta-3.jar
[INFO] Resolved: shrinkwrap-resolver-api-maven-2.0.0-beta-3.jar
[INFO] Resolved: shrinkwrap-resolver-api-2.0.0-beta-3.jar
[INFO] Resolved: shrinkwrap-resolver-spi-maven-2.0.0-beta-3.jar
[INFO] Resolved: shrinkwrap-resolver-spi-2.0.0-beta-3.jar
[INFO] Resolved: aether-api-1.13.1.jar
[INFO] Resolved: aether-impl-1.13.1.jar
[INFO] Resolved: aether-spi-1.13.1.jar
[INFO] Resolved: aether-util-1.13.1.jar
[INFO] Resolved: aether-connector-wagon-1.13.1.jar
[INFO] Resolved: maven-aether-provider-3.0.5.jar
[INFO] Resolved: maven-model-builder-3.0.5.jar
[INFO] Resolved: maven-repository-metadata-3.0.5.jar
[INFO] Resolved: maven-settings-3.0.5.jar
[INFO] Resolved: maven-settings-builder-3.0.5.jar
[INFO] Resolved: plexus-interpolation-1.14.jar
[INFO] Resolved: wagon-provider-api-2.4.jar
[INFO] Resolved: wagon-file-2.4.jar
[INFO] Resolved: wagon-http-lightweight-2.4.jar
[INFO] Resolved: wagon-http-shared4-2.4.jar
[INFO] Resolved: jsoup-1.7.1.jar
[INFO] Resolved: httpcore-4.2.3.jar
[INFO] Resolved: commons-io-2.0.1.jar
[INFO] Resolved: maven-impl-projects-2.0.0-SNAPSHOT.jar
[INFO] Resolved: maven-core-3.0.5.jar
[INFO] Resolved: maven-artifact-3.0.5.jar
[INFO] Resolved: maven-plugin-api-3.0.5.jar
[INFO] Resolved: sisu-inject-plexus-2.3.0.jar
[INFO] Resolved: sisu-inject-bean-2.3.0.jar
[INFO] Resolved: sisu-guice-3.1.0-no_aop.jar
[INFO] Resolved: plexus-classworlds-2.4.jar
[INFO] Resolved: plexus-component-annotations-1.5.5.jar
[INFO] Resolved: plexus-sec-dispatcher-1.3.jar
[INFO] Resolved: maven-compat-3.0.5.jar
[INFO] Resolved: maven-embedder-3.0.5.jar
[INFO] Resolved: plexus-cipher-1.7.jar
[INFO] Resolved: commons-cli-1.2.jar
[INFO] Resolved: environment-2.0.0-SNAPSHOT-forge-addon.jar
[INFO] Resolved: environment-api-2.0.0-SNAPSHOT.jar
[INFO] Resolved: environment-impl-2.0.0-SNAPSHOT.jar
[INFO] Resolved: resources-2.0.0-SNAPSHOT-forge-addon.jar
[INFO] Resolved: resources-api-2.0.0-SNAPSHOT.jar
[INFO] Resolved: resources-impl-2.0.0-SNAPSHOT.jar
[INFO] Resolved: dependencies-2.0.0-SNAPSHOT-forge-addon.jar
[INFO] Resolved: dependencies-api-2.0.0-SNAPSHOT.jar
[INFO] Resolved: dependencies-impl-2.0.0-SNAPSHOT.jar
[INFO] Resolved: projects-2.0.0-SNAPSHOT-forge-addon.jar
[INFO] Resolved: projects-api-2.0.0-SNAPSHOT.jar
[INFO] Resolved: projects-impl-2.0.0-SNAPSHOT.jar
[INFO] Resolved: parser-java-2.0.0-SNAPSHOT-forge-addon.jar
[INFO] Resolved: parser-java-api-2.0.0-SNAPSHOT.jar
[INFO] Resolved: java-parser-api-1.0.1.Final.jar
[INFO] Resolved: parser-java-impl-2.0.0-SNAPSHOT.jar
[INFO] Resolved: java-parser-impl-1.0.1.Final.jar
[INFO] Resolved: org.eclipse.jdt.core-3.8.2.v20120814-155456.jar
[INFO] Resolved: resources-3.3.0-v20070604.jar
[INFO] Resolved: runtime-3.3.100-v20070530.jar
[INFO] Resolved: osgi-3.4.3.R34x_v20081215-1030.jar
[INFO] Resolved: common-3.3.0-v20070426.jar
[INFO] Resolved: jobs-3.3.0-v20070423.jar
[INFO] Resolved: preferences-3.2.100-v20070522.jar
[INFO] Resolved: contenttype-3.2.100-v20070319.jar
[INFO] Resolved: text-3.3.0-v20070606-0010.jar
...
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
It looks like forge2 related problem. Any idea what is going wrong here?
Thanks
Denis
12 years, 9 months
Review upcoming change to 4.30.5.Alpha6-SNAPSHOT target platform
by Mickael Istria
Hi all,
Please review this upcoming change for the 4.30.5.Alpha6-SNAPSHOT target
platform: https://github.com/jbosstools/jbosstools-target-platforms/pull/2
Summary of changes:
* Move to versions of Eclipse.org dependencies for Kepler RC2 (which
should be very close to the final version)
* Remove dependency on Eclipse repo and org.eclipse.update bundle
(previously required by old Atlassian connector)
* Use a snapshot SWTBot (include sources when using TP in IDE and fix
some issues with Hamcrest 1.3)
* Replaced "planner" mode by "slicer" to ensure some transitive
dependencies don't leak. This should avoid some occasional glitches we
have between mutliple and unified TP and reduce the quantity of red
builds for TP.
In order to test it locally, do as follow:
$ cd jbosstools-target-platforms/jbosstools/multiple
$ mvn clean install -P\!multiple2repo
$ cd ~/path/to/my/jbosstools-component
$ mvn clean verify -Dtpc.targetKind=multiple
If you notice any issue, please report it as a comment on
https://issues.jboss.org/browse/JBIDE-14729 .
Ideally, this PR will be merged and new TP snapshot should be published
by the end of the day so we can have a look at how CI jobs behave with
this newer versions ASAP. As I'm leaving to EclipseCon France by this
afternoon (5pm in France), I guess Nick will be the one to ask quesitons
on this topic on IRC for the next few days. I'll try to follow emails.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
12 years, 9 months
introduction of org.jboss.tools.foundation
by Max Rydahl Andersen
Hi,
Rob S. had the challenge that our extraction of stacks (used for handling download of runtimes and maven archetypes as defined in JDF/JBoss Way)
made it require common which because of its own internal dependencies have become a very big mixed bag which after several attempts have not been
reduced (at least not significantly). Main problem been that core/common had hard requirements on WTP, not just base Eclipse.
To fix/help on this issue of the common not really being common we've created org.jboss.tools.foundation (see https://issues.jboss.org/browse/JBIDE-14363)
Rob S. pushed this into base last night so it is in JBoss Tools 4.1 and in upcoming versions of JBT we can add *real core* functionallities to this foundation library.
For now it just contains the BasePlugins with logging and the class that kept being recreated File download via ECF.
This foundation now got tests, public API's and is intended to be destination for actual common parts - stuff that has no big dependencies but we all
keep reinventing/reimplementing.
As with anything if you want something added/moved to this then open jira/PR - over time we'll write up guidelines, limits and test requirements; but
for 4.1 we needed this to get a place central, examples, stacks, server and arquillian can use *without* requiring big parts of xmodel and WTP.
Note: if you see problems caused by this introduction please open jira and link to JBIDE-14363 and assign to Rob Stryker.
Thanks,
/max
12 years, 9 months
Fwd: Deadline for Beta2 and GA N&N
by Michelle Murray
----- Forwarded Message -----
From: "Michelle Murray" <mmurray(a)redhat.com>
To: "external-exadel-list list" <external-exadel-list(a)redhat.com>, jbosstools-dev(a)redhat.com
Cc: "jbds-pm-list jbds-pm-list" <jbds-pm-list(a)redhat.com>
Sent: Friday, 7 June, 2013 7:02:55 PM
Subject: Deadline for Beta2 and GA N&N
Hi devs,
I realise heading towards GA is a busy time for everyone so I want to make you are aware of two deadline now so that you can accommodate them into your schedule.
New and Noteworthy must be completed with sufficient time for me to add any new features into the release notes document.
With that in mind the deadlines for completing N&N are:
Beta2 = COB 21st June 2013
GA = COB 5th July 2013
N&N not completed by these deadlines will not get into the release notes.
I will send an email reminder closer to the date, but put it in your diary now.
Thanks,
Michelle
12 years, 9 months
Download API
by Snjezana Peco
Rob,
You have moved the ECFTransport class to the common plugin and created
an API to enable caching of downloaded files.
Max considers we need to refactor the project examples, central and
arquillian plugin to use the new API. Could you suggest the best way to
do it?
Snjeza
12 years, 9 months
