January 2015 - jbosstools-dev - Jboss List Archives

Proposed change to JBT 4.50.0 target platform:

by Matej Gagyi

Here is a proposal for a change to the JBoss Tools 4.50.0 target platform: https://github.com/jbosstools/jbosstools-target-platforms/pull/119 It consists in the following changes: * JBIDE-JBIDE-19110: Add Mockito to Target platform 4.50.0 p2diff reports are attached to the related JIRA(s). Please review the above PR(s), as it will be applied ASAP. You can use the following to build & test the target-platform locally against your component(s). Build target-platform: $ cd jbosstools-target-platforms $ git fetch origin 4.50.x $ git checkout FETCH_HEAD $ cd jbosstools/multiple $ mvn clean install Try with just built target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.50.x -Pmultiple.target -- If you want to perform a scripted install of the entire target platform into your local Eclipse or JBDS instance, you can now do so with this script: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... Usage is documented in the above script, and in this README: https://github.com/jbosstools/jbosstools-target-platforms/tree/master#upd...

8 years, 10 months

1
2
0 / 0

Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA

by Paul Leacu

Greetings - A proposal to change the JBTIS target platform is described here: https://issues.jboss.org/browse/JBTIS-382 PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/280 Synopsis: 1. Split the JBTIS target platform along release/final and non-release/early access lines so as to not expose non .Final features to the stable capture that appears when performing an 'uncategorized' install. No dependent component version change from 4.2.0.Final. http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi... http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/ Please respond by COB on Thursday, Jan 29 to the specified Jira if there are any issues. Thanks, --paull

8 years, 10 months

3
10
0 / 0

ACTION REQUIRED: Prepare for JBT 4.2.3.Beta1!

by Nick Boldt

These projects have approved changes coming (or already built) in JBT 4.2.3, so must ensure they've upversioned and are using the latest parent pom & target platform (including new Tern 0.7 and forthcoming Luna SR2 bits next week): Aerogear : https://issues.jboss.org/browse/JBIDE-19125 JST : https://issues.jboss.org/browse/JBIDE-19126 VPE : https://issues.jboss.org/browse/JBIDE-19127 Forge : https://issues.jboss.org/browse/JBIDE-19128 Server : https://issues.jboss.org/browse/JBIDE-19129 Hibernate : https://issues.jboss.org/browse/JBIDE-19130 Base : https://issues.jboss.org/browse/JBIDE-19131 OpenShift : https://issues.jboss.org/browse/JBIDE-19132 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

8 years, 10 months

1
0
0 / 0

JBoss Tools 4.2.3 / JBDS 8.1.0 schedule updated in JIRA (now with CR1!)

by Nick Boldt

In order to encourage more community participation [1] and earlier access to new features (like FeedHenry support), we will be releasing milestones sooner than we have in the past. I've updated the schedule in JIRA [2] to reflect that new change. [1] http://tools.jboss.org/cat/ [2] https://issues.jboss.org/browse/JBIDE?selectedTab=com.atlassian.jira.jira... Since we now have more time between CR1 and GA release dates, I've also added a CR1 fixversion so we can target bugfixes appropriately. Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

8 years, 10 months

1
0
0 / 0

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)

8 years, 10 months

3
2
0 / 0

ACTION REQUIRED: 1 issue with no component

by manderse＠redhat.com

This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBIDE-19085 https://issues.jboss.org/browse/JBIDE-19085 Summary: tools.jboss.org devstudio downloads does not mention it is update site content only and to use 8.0.0 installer Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 4:48:36.968043 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

8 years, 10 months

1
0
0 / 0

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

8 years, 10 months

1
0
0 / 0

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

8 years, 10 months

7
19
0 / 0

4.2.x is now open for 4.2.3 (that will be included in Developer Studio 8.1)

by Max Rydahl Andersen

Hi, Just a heads up that now that we have tagged and released 4.2.2, the jbosstools-4.2.x branch are open for issues related to 4.2.3. This 4.2.3 is planned to be what is included in JBoss Developer Studio 8.1. Please be aware that this version is intended to backwards compatible with the 4.2 releases; especially consideration is to be sure we do not break Integration stack in context of changed dependencies or any API they use. Thus as always, take care in what changes you do, have a jira for each work so QE/docs are aware and don't be afraid to ask for more than one review of PRs if any doubts. Happy 8.1! /max http://about.me/maxandersen

8 years, 10 months

2
2
0 / 0

ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.2.Final ]

by Mickael Istria

Component leads, please tag your repositories! $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called jbosstools, also often called origin $ git tag jbosstools-4.2.2.Final FETCH_HEAD $ git push jbosstools jbosstools-4.2.2.Final -- 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>

8 years, 10 months

8
7
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev January 2015