M5 spin status :: no aggregate or JBDS installers available yet; many bot and non-UI test failures, plus one inter-build compilation failure
by Nick Boldt
Since turning on the stable branch jobs, here's what's borked...
https://issues.jboss.org/browse/JBIDE-10349
Still trying to get a clean stable_branch aggregate build (and then JBT
builds too) - last time the aggregate failed due to missing Central,
OTDT, and OpenShift (hadn't spun clean yet).
---
Details:
- hibernate : test failure in org.hibernate.eclipse.console.test
- jbpm : test failure in org.jboss.tools.jbpm.convert.test
- jsf : test failure in org.jboss.tools.jsf.vpe.jsf.test
- maven : 15 bot test failures (same failures in trunk) ... should these
just be turned off and only run locally / manually?
- struts : COMPILE FAILED - upstream bits missing? "The import
org.jboss.tools.jst.web.validation cannot be resolved."
---
There are also a few jobs for which the latest build failed, but at
least we have one good build since branching. This suggests we're having
some stability issues w/ a few Jenkins slaves, but at least we're
getting clean spins when the server is quiet(er).
= archives : aborted build? [Dec 4 ok]
= birt : failed to find usage bits (poor timing between builds) [Dec 4 ok]
= seam : no more locks failure [Dec 4 ok]
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
6 months, 2 weeks
Window Tester as alternative to SWTBot ?
by Mickael Istria
Hi all,
During EclipseCon Europe, I chatted with a guy who's a pure
technology-agnostic guy (not a contributor, not a guru, not an
evangelist, just a user who gives his user story in an objective way).
He used to use SWTBot to write tests, but he started using Google
WindowTester Pro [1] instead since it got released under EPL by Google
[2]. He told me that WindowTester Pro has a bot API quite similar to
SWTBot, also compatible with JUnit and Tycho; and the most interesting
point is that Window Tester contains a recorder which allows to record
tests pretty easily. This could help us to write tests, but also be used
by end-users to provide their failing scenarios as WindowTester scenarios.
The recorder simply logs all SWT events and tries to turn meaningful
sequences of Events to user-grained UI operations (such as click). I was
reported that 90% of code written by the recorder is good for industrial
usage, the 10 remaining % requires some refactoring and Java coding; and
that using WindowTester Pro takes half the time as recording+writing
SWTBot tests to provide exactly the same thing, with the same level of
(re)usability and maintainability.
The only "darker" point I know against this tool is that it's not (yet?)
part of the Eclipse Foundation projects, it's still a Google one. But I
think that with some insistence, this project can get into the
Foundation with all the advantages that comes with it (mainly openness).
This definitely seems to be a project we should evaluate for JBoss
Tools. I opened this ticket to track this suggestion:
https://issues.jboss.org/browse/JBIDE-12953 so anyone who's interested
can go there and provide some additional feedback/ideas on whether
WindowTester Pro is good for JBoss Tools.
Cheers,
[1] http://code.google.com/p/windowtester/
https://developers.google.com/java-dev-tools/wintester/html/
[2]
http://google-opensource.blogspot.de/2012/03/announcing-windowtester-open...
--
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>
13 years, 9 months
Runtimes component
by Martin Malina
Hi Snjeza,
Recently we noticed that the runtime detection component of JBIDE has been renamed to SOA Runtime Detection [1].
This is a little confusing because old JIRAs that had this component might not have anything to do with soa. But ok, I assume you considered different solutions and found this to be best.
But anyway, I'd like make sure we understand this correctly. Is this because most of the runtime detection code was moved under Rob's as component and this renamed component should now be used only for what remained in the old place which is only soa runtimes?
So from now on bugs in runtime detection that are related to JbossAS or Seam runtimes should be logged under JBossAS/Servers component?
Thanks,
Martin
[1] https://issues.jboss.org/browse/JBIDE/component/12313665
--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic
Tel.: +420 532 294 265
13 years, 10 months
[gitmigration] Follow up - git/jira links, push force protection, svn ignores, build checkout, gitmigration guide
by Max Rydahl Andersen
Hi,
I got several questions about git migration so I thought I would just write this up quickly with current outstanding issues/info:
Jira does not show git commits in its source tab
=====================================
There is an open helpdesk request #175361 asking to add all github.com/jbosstools-* repos into JBIDE and JBDS jira.
All svn:ignores was not migrated over
=============================
This is my fault, I thought the git-svn migration I setup did this but apparently all the .gitignores that were in there came from our own svn (I assume nickboldt added them while he used git-svn)
but did not cover the same git-ignore rules as the svn-ignore ones - thus there is some inconsistencies here.
We dont really need many of these .gitignore's I believe, thus I've added a root .gitignore in (almost) all projects that excludes target/ and bin/ dir globally. nothing else.
If your project has a specific file it needs excluding (i.e. a internal build jar) then add that to a local .gitignore for that directoy - not to the global one.
If you got an editor that creates funky named scratch files I suggest you configure a global exclude for it. See Global .gitignore at https://help.github.com/articles/ignoring-files
What happens if I do push --force on our master repos ?
===========================================
A kittten dies, an angel looses its wings and everyone who have pulled from this repo will now have to go through excruciating pain of recloning/repulling and rebasing their work.
Oh - and did I mention you might loose someone already pushed changes ?
Unfortunately github does not allow this to be disabled on projects hosted on github.com (they do on their enterprise repo product - http://stackoverflow.com/questions/5094524/github-prevent-colaborator-fro...)
Thus for now - just don't do it.
I'll try and setup a warning system (add requestb.in hooks to all repos), for it in case it does happen so we can at least detect it and restore a proper repo if it occurs. (Hibernate core repos have this and helped them a few times)
/max
13 years, 10 months
Red Deer Info?
by Max Rydahl Andersen
I asked this on https://github.com/jbosstools/jbosstools-integration-tests/pull/3 but I assume noone saw it since the issue is closed, so repeating it here:
How is this red deer stuff going to work ? which updatesites will contain it ? I did not realize these are actually eclipse plugins - and thus not just maven dependencies. by reddeer being on its own the maintanence of those updatesites and releases needs to be done fully before we should have tests depending on them, right?
I saw today there is something like p2-reddeer.rhcloud.com/stable - what is that and why are we publishing this way and how are this stuff supposed to be used ?
There have been no info/news on this but now alot of our tests is suddenly dependent on this making our builds rely on something that is *not* mirrored nor communicated how to use afaik ?
Did I miss something ? i.e. i'm still not following why we want to have separate infrastructure for something this eclipse specific ? but first of all i'm worried about having jbosstools code dependent on something like this very unknown reddeer.
/max
13 years, 10 months
Forge runtime bundled version
by Pavol Srna
Hi guys,
I'm wondering why do we want to ship JBT 4.0 Beta1 with Forge Tools
bundled with forge 1.0.6.Final runtime if there currently is Forge
1.1.1.Final available?
--
Pavol Srna
QA Engineer, JBDS
Phone: +420 532 294 352
irc: psrna
Red Hat Czech
Purkynova 99, 612 00 Brno, Czech Republic
13 years, 10 months
Where can I get JDBC drivers?
by Andrej Podhradsky
Hi all,
in bot tests for Teiid designer I use 2 jdbc drivers - for SQL Server and for Oracle.
Since there is an intention to avoid pushing jar files into github, I'm looking for another way how to get these drivers.
Is there any maven repository from which I can download these drivers?
Best Regards
--
Andrej Podhradsky
Quality Assurance Associate
JBoss SOA Platform
IRC: apodhrad at #jbossqa #jbosssoa #jbosssoaqa #devstudio-qa #brno
13 years, 10 months
Build failed in Jenkins: jbosstools-4.0_trunk.aggregate #5791
by ci-builds＠redhat.com
See <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk....>
Changes:
[nickboldt] remove flow and jbpm4 from the soa tests site (JBIDE-12631)
[nickboldt] remove runtime-soa test feature as it's no longer in jbosstools-runtime-soa repo (JBIDE-12828)
[nickboldt] remove runtime-soa test feature as it's no longer in jbosstools-runtime-soa repo (JBIDE-12828)
[Max Rydahl Andersen] JBIDE-12951 add bin and target to all root .gitignores
------------------------------------------
Started by upstream project "jbosstools-4.0_trunk.webtools.aggregate" build number 517
[EnvInject] - Loading node environment variables.
Building remotely on soa3-RHEL5-x86
Updating https://svn.jboss.org/repos/devstudio/trunk/hudson-jobs/settings
At revision 10639
no change for https://svn.jboss.org/repos/devstudio/trunk/hudson-jobs/settings since the previous build
Checkout:jbosstools-4.0_trunk.aggregate / <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk....> - hudson.remoting.Channel@b349923:soa3-RHEL5-x86
Using strategy: Default
Last Built Revision: Revision 8a189ceb5d527acc3b376d12b273e490f0d3fc0c (origin/master)
Fetching changes from 1 remote Git repository
Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git
Commencing build of Revision 8e05efbd5398e1afcae987ae92e1a046a47e0221 (origin/master)
Checking out Revision 8e05efbd5398e1afcae987ae92e1a046a47e0221 (origin/master)
[jbosstools-4.0_trunk.aggregate] $ bash -xe /tmp/hudson5237399946584741924.sh
[jbosstools-4.0_trunk.aggregate] $ /qa/tools/opt/apache-maven-3.0.4/bin/mvn -f <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk....> -DRELEASE=No "-DMAVEN_FLAGS=clean install -B -U -fae -P hudson,jbosstools-nightly-staging-composite,jenkins.target.maximum,local.site,local.composite" "-Dupdate.site.description=Nightly Build" -Ddownload.cache.directory=/home/hudson/static_build_env/jbds/download-cache -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true -Dlocal.site=file:///home/hudson/static_build_env/jbds/target-platform_4.0.juno.SR1a/e421-wtp341.target/ -DBUILD_ID=2012-10-26_19-06-10 -DJOB_NAME=jbosstools-4.0_trunk.aggregate -DBUILD_NUMBER=5791 -Dlocal.composite=file:///home/hudson/static_build_env/jbds/builds/staging/_composite_/core/trunk/ -Dmaven.repo.local=<http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk....> clean install -B -U -fae -P hudson,jbosstools-nightly-staging-composite,jenkins.target.maximum,local.site,local.composite -gs /home/hudson/.m2/settings.xml -s <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk....>
[INFO] Scanning for projects...
Downloading: http://snapshots.jboss.org/maven2/org/jboss/tools/parent/4.0.0.Beta2-SNAP...
Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
Downloaded: http://snapshots.jboss.org/maven2/org/jboss/tools/parent/4.0.0.Beta2-SNAP... (610 B at 1.0 KB/sec)
Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (610 B at 0.4 KB/sec)
[WARNING] Could not transfer metadata org.jboss.tools:parent:4.0.0.Beta2-SNAPSHOT/maven-metadata.xml from/to jenkins.composite (file:///home/hudson/static_build_env/jbds/builds/staging/_composite_/core/trunk/): No connector available to access repository jenkins.composite (file:///home/hudson/static_build_env/jbds/builds/staging/_composite_/core/trunk/) of type p2 using the available factories WagonRepositoryConnectorFactory
[WARNING] Could not transfer metadata org.jboss.tools:parent:4.0.0.Beta2-SNAPSHOT/maven-metadata.xml from/to jbosstools-target-site (${jbosstools-target-site}): No connector available to access repository jbosstools-target-site (${jbosstools-target-site}) of type p2 using the available factories WagonRepositoryConnectorFactory
Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (28 KB at 67.9 KB/sec)
Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
Downloading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
Downloading: http://snapshots.jboss.org/maven2/org/jboss/tools/target-platforms/jbosst...
Downloading: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos...
Downloaded: http://snapshots.jboss.org/maven2/org/jboss/tools/target-platforms/jbosst... (871 B at 3.0 KB/sec)
Downloaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (871 B at 2.0 KB/sec)
Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (871 B at 1.9 KB/sec)
Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (32 KB at 73.3 KB/sec)
[INFO] Computing target platform for MavenProject: org.jboss.tools:org.jboss.tools.site.core:0.0.2-SNAPSHOT @ <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk....>
[INFO] Adding repository file:/home/hudson/static_build_env/jbds/builds/staging/_composite_/core/trunk/
[INFO] Adding repository file:/home/hudson/static_build_env/jbds/builds/staging/_composite_/core/trunk/
[INFO] Adding repository http://download.jboss.org/jbosstools/updates/juno/SR1a/latest/
[INFO] Adding repository http://download.jboss.org/jbosstools/updates/juno/SR1a/latest/
[INFO] Adding repository file:/home/hudson/static_build_env/jbds/target-platform_4.0.juno.SR1a/e421-wtp341.target/
[INFO] Adding repository file:/home/hudson/static_build_env/jbds/target-platform_4.0.juno.SR1a/e421-wtp341.target/
[INFO] Resolving dependencies of MavenProject: org.jboss.tools:org.jboss.tools.site.core:0.0.2-SNAPSHOT @ <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk....>
[INFO] Cannot complete the request. Generating details.
[INFO] Cannot complete the request. Generating details.
[INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.site.core raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.maven.hibernate 1.4.0.Beta2-v20121025-0211-B14 requires 'bundle org.hibernate.eclipse.console 0.0.0' but it could not be found
[ERROR] Missing requirement: org.jboss.tools.maven.hibernate 1.4.0.Beta2-v20121025-0241-B15 requires 'bundle org.hibernate.eclipse.console 0.0.0' but it could not be found
[ERROR] Cannot satisfy dependency: org.jboss.tools.maven.hibernate.feature.feature.group 1.4.0.Beta2-v20121025-0211-B14 depends on: org.jboss.tools.maven.hibernate [1.4.0.Beta2-v20121025-0211-B14]
[ERROR] Cannot satisfy dependency: org.jboss.tools.maven.hibernate.feature.feature.group 1.4.0.Beta2-v20121025-0241-B15 depends on: org.jboss.tools.maven.hibernate [1.4.0.Beta2-v20121025-0241-B15]
[ERROR] Cannot satisfy dependency: org.jboss.tools.maven.hibernate.feature.source.feature.group 1.4.0.Beta2-v20121025-0211-B14 depends on: org.jboss.tools.maven.hibernate.feature.feature.group [1.4.0.Beta2-v20121025-0211-B14]
[ERROR] Cannot satisfy dependency: org.jboss.tools.maven.hibernate.feature.source.feature.group 1.4.0.Beta2-v20121025-0241-B15 depends on: org.jboss.tools.maven.hibernate.feature.feature.group [1.4.0.Beta2-v20121025-0241-B15]
[ERROR] Cannot satisfy dependency: org.jboss.tools.site.core raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT depends on: org.jboss.tools.maven.hibernate.feature.source.feature.group 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2121-B129 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2121-B129 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2121-B129 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2145-B130 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2145-B130 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2145-B130 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.maven.hibernate 1.4.0.Beta2-v20121025-0211-B14 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.maven.hibernate 1.4.0.Beta2-v20121025-0241-B15 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.feature.feature.group 3.4.0.Beta2-v20121024-2051-B7 to org.hibernate.eclipse.feature.feature.group 3.2.0.", "Unable to satisfy dependency from org.jboss.tools.seam.feature.feature.group 3.4.0.Beta2-v20121025-0246-B8 to org.hibernate.eclipse.feature.feature.group 3.2.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.site.core raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT to org.hibernate.eclipse.feature.feature.group 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.site.core raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT to org.hibernate.eclipse.feature.source.feature.group 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2121-B129 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2121-B129 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2121-B129 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2145-B130 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2145-B130 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2145-B130 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.maven.hibernate 1.4.0.Beta2-v20121025-0211-B14 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.maven.hibernate 1.4.0.Beta2-v20121025-0241-B15 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.feature.feature.group 3.4.0.Beta2-v20121024-2051-B7 to org.hibernate.eclipse.feature.feature.group 3.2.0.", "Unable to satisfy dependency from org.jboss.tools.seam.feature.feature.group 3.4.0.Beta2-v20121025-0246-B8 to org.hibernate.eclipse.feature.feature.group 3.2.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.site.core raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT to org.hibernate.eclipse.feature.feature.group 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.site.core raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT to org.hibernate.eclipse.feature.source.feature.group 0.0.0.", "No solution found because the problem is unsatisfiable."]
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2121-B129 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2121-B129 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2121-B129 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2145-B130 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2145-B130 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.4.0.Beta2-v20121024-2145-B130 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.maven.hibernate 1.4.0.Beta2-v20121025-0211-B14 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.maven.hibernate 1.4.0.Beta2-v20121025-0241-B15 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.feature.feature.group 3.4.0.Beta2-v20121024-2051-B7 to org.hibernate.eclipse.feature.feature.group 3.2.0.", "Unable to satisfy dependency from org.jboss.tools.seam.feature.feature.group 3.4.0.Beta2-v20121025-0246-B8 to org.hibernate.eclipse.feature.feature.group 3.2.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121024-2051-B7 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse.console 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.seam.ui 3.4.0.Beta2-v20121025-0246-B8 to bundle org.hibernate.eclipse.libs 3.4.0.", "Unable to satisfy dependency from org.jboss.tools.site.core raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT to org.hibernate.eclipse.feature.feature.group 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.site.core raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT to org.hibernate.eclipse.feature.source.feature.group 0.0.0.", "No solution found because the problem is unsatisfiable."]
at org.eclipse.tycho.p2.impl.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:79)
at org.eclipse.tycho.p2.impl.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:83)
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:118)
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:76)
at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:448)
at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:425)
at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:98)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:64)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
... 11 more
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
Build step 'Invoke top-level Maven targets' marked build as failure
Description set:
13 years, 10 months
