Broken build in jbosstools-4.2.x branch
by Denis Golovin
Fred, Rob, Nick
could you take a look at build problem below. It feels like there are
some problem with references.
Thanks
Denis
Part of the output:
[INFO] [INFO] Resolving dependencies of MavenProject:
org.jboss.tools.as.plugins:org.jboss.ide.eclipse.as.jmx.integration:3.0.1-SNAPSHOT
@
/home/eskimo/data/Projects/jbdevstudio/4.2.x/up/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.jmx.integration/pom.xml
[INFO] [INFO] Cannot complete the request. Generating details.
[INFO] [INFO] Cannot complete the request. Generating details.
[INFO] [INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86,
org.eclipse.update.install.features=true}
[INFO] [ERROR] Cannot resolve project dependencies:
[INFO] [ERROR] Software being installed:
org.jboss.ide.eclipse.as.jmx.integration 3.0.1.qualifier
[INFO] [ERROR] Missing requirement:
org.jboss.ide.eclipse.as.jmx.integration 3.0.1.qualifier requires
'bundle org.jboss.tools.jmx.jvmmonitor.ui 1.7.0' but it could not be found
[INFO] [ERROR]
[INFO] [ERROR] Internal error: java.lang.RuntimeException: No solution
found because the problem is unsatisfiable.: [Unable to satisfy
dependency from org.jboss.ide.eclipse.as.jmx.integration 3.0.1.qualifier
to bundle org.jboss.tools.jmx.jvmmonitor.ui 1.7.0.; No solution found
because the problem is unsatisfiable.] -> [Help 1]
[INFO] org.apache.maven.InternalErrorException: Internal error:
java.lang.RuntimeException: No solution found because the problem is
unsatisfiable.: [Unable to satisfy dependency from
org.jboss.ide.eclipse.as.jmx.integration 3.0.1.qualifier to bundle
org.jboss.tools.jmx.jvmmonitor.ui 1.7.0.; No solution found because the
problem is unsatisfiable.]
[INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
[INFO] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
[INFO] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
[INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
[INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[INFO] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[INFO] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[INFO] at java.lang.reflect.Method.invoke(Method.java:606)
[INFO] at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
[INFO] at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
[INFO] at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
[INFO] at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[INFO] Caused by: java.lang.RuntimeException: No solution found because
the problem is unsatisfiable.: [Unable to satisfy dependency from
org.jboss.ide.eclipse.as.jmx.integration 3.0.1.qualifier to bundle
org.jboss.tools.jmx.jvmmonitor.ui 1.7.0.; No solution found because the
problem is unsatisfiable.]
[INFO] at
org.eclipse.tycho.p2.util.resolution.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98)
[INFO] at
org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88)
[INFO] at
org.eclipse.tycho.p2.util.resolution.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)
[INFO] at
org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:166)
[INFO] at
org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:103)
[INFO] at
org.eclipse.tycho.p2.resolver.P2DependencyResolver.doResolveDependencies(P2DependencyResolver.java:352)
[INFO] at
org.eclipse.tycho.p2.resolver.P2DependencyResolver.resolveDependencies(P2DependencyResolver.java:325)
[INFO] at
org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject(DefaultTychoResolver.java:107)
[INFO] at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
[INFO] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:310)
[INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
[INFO] ... 11 more
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven
with the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
logging.
[INFO] [ERROR]
[INFO] [ERROR] For more information about the errors and possible
solutions, please read the following articles:
[INFO] [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
[INFO] ..FAILED (71.2 s)
9 years, 3 months
ACTION REQUIRED: Upversion needed in Central, VPE, Base, Openshift, and Forge
by Nick Boldt
Our Version Watch tool is failing in the master branch (JBT 4.3 / JBDS
9.0), because there are a number of projects whose plugins/features have
lower versions than those released in JBT 4.2.2 / 8.0.2.
Please fix this ASAP.
Affected projects include:
Central/Maven - https://issues.jboss.org/browse/JBIDE-19073
VPE - https://issues.jboss.org/browse/JBIDE-19074
Base - https://issues.jboss.org/browse/JBIDE-19075
OpenShift - https://issues.jboss.org/browse/JBIDE-19076
Forge - https://issues.jboss.org/browse/JBIDE-19077
887 org.jboss.tools.forge.feature,1.3.1 from jbds-9.0.0.Alpha1 Version
must be higher
887 org.jboss.tools.forge.m2e.feature,1.1.1 from jbds-9.0.0.Alpha1
Version must be higher
888 org.jboss.tools.foundation.feature,1.1.0 from jbds-9.0.0.Alpha1
Version must be higher
888 org.jboss.tools.foundation.security.linux.feature,1.1.0 from
jbds-9.0.0.Alpha1 Version must be higher
889 org.jboss.tools.maven.cdi.feature,1.6.0 from jbds-9.0.0.Alpha1
Version must be higher
890 org.jboss.tools.maven.feature,1.6.0 from jbds-9.0.0.Alpha1 Version
must be higher
890 org.jboss.tools.maven.hibernate.feature,1.6.0 from jbds-9.0.0.Alpha1
Version must be higher
890 org.jboss.tools.maven.jdt.feature,1.6.0 from jbds-9.0.0.Alpha1
Version must be higher
891 org.jboss.tools.maven.portlet.feature,1.6.0 from jbds-9.0.0.Alpha1
Version must be higher
892 org.jboss.tools.maven.sourcelookup.feature,1.6.0 from
jbds-9.0.0.Alpha1 Version must be higher
892 org.jboss.tools.openshift.egit.integration.feature,2.6.0 from
jbds-9.0.0.Alpha1 Version must be higher
892 org.jboss.tools.openshift.express.feature,2.6.0 from
jbds-9.0.0.Alpha1 Version must be higher
893 org.jboss.tools.stacks.core.feature,1.1.0 from jbds-9.0.0.Alpha1
Version must be higher
894 org.jboss.tools.vpe.browsersim.feature,3.6.0 from jbds-9.0.0.Alpha1
Version must be higher
894 org.jboss.tools.vpe.feature,3.6.0 from jbds-9.0.0.Alpha1 Version
must be higher
894 org.jboss.tools.vpe.preview.feature,3.6.0 from jbds-9.0.0.Alpha1
Version must be higher
992 org.jboss.tools.aesh.core,1.3.1 from jbds-9.0.0.Alpha1 Version must
be higher
992 org.jboss.tools.aesh.ui,1.3.1 from jbds-9.0.0.Alpha1 Version must be
higher
998 org.jboss.tools.forge.core,1.3.1 from jbds-9.0.0.Alpha1 Version must
be higher
998 org.jboss.tools.forge.m2e,1.1.1 from jbds-9.0.0.Alpha1 Version must
be higher
999 org.jboss.tools.forge.runtime.ext,1.3.1 from jbds-9.0.0.Alpha1
Version must be higher
999 org.jboss.tools.forge.ui,1.3.1 from jbds-9.0.0.Alpha1 Version must
be higher
999 org.jboss.tools.forge.ui.notifications,1.3.1 from jbds-9.0.0.Alpha1
Version must be higher
More:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
9 years, 3 months
Should we use @Ignore in non-runnable JUnit test classes, instead of <include> in pom? (was: JUnit Tests)
by Nick Boldt
No, because then AbstractTest* and TemplateTest* classes would run, and
they shouldn't be.
You can set your own <include> entries in your root pom. Then all your
projects' tests will inherit those new rules.
--
We may also have some older JUnit 3 tests (from the JDK 1.4 era?) that
might still be set to run with older JRE environments, where
@annotations are not supported.
If I'm wrong on that, and we no longer support running tests w/ old
runtimes, then yes, we could consider adding @Ignores to all the tests
which shouldn't be run, instead of using the "All" and "Suite" naming
conventions.
--
I've cc:'d the jbosstools-dev list because a wider audience might be
able to comment better on if it's time to move to using @ignore instead
of using restrictive patterns when running JUnits w/ Surefire in
Tycho/Maven builds.
N
On 01/22/2015 02:08 PM, Daniel Florian wrote:
> Guys,
>
> We currently have to add each JUnit test class to a test suite file called AllTests.java. If a test does not get added to this test suite it does not get run.
>
> I think the pom has this:
>
> <includes>
> <include>**/AllTests.class</include>
> <include>**/*AllTests*.class</include>
> <include>**/*AllBotTests*.class</include>
> <include>**/*TestSuite*.class</include>
> </includes>
>
> Could we add:
>
> <include>**/Test*.class</include>
> <include>**/*Test.class</include>
>
> So that we wouldn't need an AllTests.java. Other projects can keep using the test suite approach.
>
> With JUnit's @Ignore it is easy to stop a test from being run.
>
> wdyt?
>
> Thanks,
>
> Dan
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
9 years, 3 months
