March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13863) org.junit4 replaced w/ org.junit; please update your test plugins' manifest.mf files

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13863: ---------------------------------- Summary: org.junit4 replaced w/ org.junit; please update your test plugins' manifest.mf files Key: JBIDE-13863 URL: https://issues.jboss.org/browse/JBIDE-13863 Project: Tools (JBoss Tools) Issue Type: Bug Components: modeshape Affects Versions: 4.0.0.Alpha1-SOA Reporter: Nick Boldt Assignee: Dan Florian Because Kepler M6 target platform no longer includes org.junit4_4.8, and instead includes org.junit_4.11, you will need to adjust your tests' manifest.mf files. {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integration-tests.aggregate_master/78/console} [ERROR] Software being installed: site raw:1.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):1.0.0-SNAPSHOT [ERROR] Missing requirement: org.jboss.tools.modeshape.jcr.test 3.2.0.Alpha1-v20130308-0851-B89 requires 'bundle org.junit4 0.0.0' but it could not be found [ERROR] Missing requirement: org.jboss.tools.modeshape.jcr.test 3.2.0.Alpha1-v20130313-1951-B90 requires 'bundle org.junit4 0.0.0' but it could not be found [ERROR] Cannot satisfy dependency: org.jboss.tools.modeshape.jcr.test.feature.feature.group 3.2.0.Alpha1-v20130308-0851-B89 depends on: org.jboss.tools.modeshape.jcr.test [3.2.0.Alpha1-v20130308-0851-B89] [ERROR] Cannot satisfy dependency: org.jboss.tools.modeshape.jcr.test.feature.feature.group 3.2.0.Alpha1-v20130313-1951-B90 depends on: org.jboss.tools.modeshape.jcr.test [3.2.0.Alpha1-v20130313-1951-B90] [ERROR] Cannot satisfy dependency: site raw:1.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):1.0.0-SNAPSHOT depends on: org.jboss.tools.modeshape.jcr.test.feature.feature.group 0.0.0 {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13859) Fix dependencies on org.jboss.tools.ui.bot.ext to restrict version

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13859?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-13859: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-tests/pull/205, https://github.com/jbosstools/jbosstools-integration-tests/pull/206 (was: https://github.com/jbosstools/jbosstools-integration-tests/pull/205) > Fix dependencies on org.jboss.tools.ui.bot.ext to restrict version > ------------------------------------------------------------------ > > Key: JBIDE-13859 > URL: https://issues.jboss.org/browse/JBIDE-13859 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: QA > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > Our bot tests in https://github.com/jbosstools/jbosstools-integration-tests depend on bundle org.jboss.tools.ui.bot.ext . Most of the time we first install bot ext to the local repo (mvn install) and then run the given test (mvn verify). The problem is that the bot ext requirement is not strict about the version required, so many times the wrong version from local maven repo is used. > For example you're trying to run a test from jbosstools-4.0.x branch so org.jboss.tools.ui.bot.ext version 4.0.x should be used, but if you installed 4.1.x version of bot ext on that machine in the past, it will use that one instead. This is not desired. > So in branch jbosstools-4.0.x we need this in every test bundle manifest: > org.jboss.tools.ui.bot.ext;bundle-version="[4.0.0,4.1.0)" > For master (4.1.x) we need this: > org.jboss.tools.ui.bot.ext;bundle-version="[4.1.0,4.2.0)" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13853) Compile errors when using Kepler M6

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13853?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13853: -------------------------------- Fix Version/s: 4.1.0.Alpha2 > Compile errors when using Kepler M6 > ----------------------------------- > > Key: JBIDE-13853 > URL: https://issues.jboss.org/browse/JBIDE-13853 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > There are 1356 errors in the hibernate component when using Kepler M6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13853) Compile errors when using Kepler M6

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13853?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13853: -------------------------------- Issue Type: Bug (was: Feature Request) > Compile errors when using Kepler M6 > ----------------------------------- > > Key: JBIDE-13853 > URL: https://issues.jboss.org/browse/JBIDE-13853 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Koen Aers > > There are 1356 errors in the hibernate component when using Kepler M6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13853) Compile errors when using Kepler M6

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13853?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13853: -------------------------------- Priority: Blocker (was: Major) > Compile errors when using Kepler M6 > ----------------------------------- > > Key: JBIDE-13853 > URL: https://issues.jboss.org/browse/JBIDE-13853 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Koen Aers > Priority: Blocker > > There are 1356 errors in the hibernate component when using Kepler M6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13862) Deploying project should be automatically added to OpenShift Server adapter

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-13862: -------------------------------------- Summary: Deploying project should be automatically added to OpenShift Server adapter Key: JBIDE-13862 URL: https://issues.jboss.org/browse/JBIDE-13862 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers, openshift Affects Versions: 4.1.0.Alpha1 Reporter: Stefan Bunciak Assignee: Rob Stryker Fix For: 4.1.0.Alpha2 Attachments: server.png, server1.png, server2.png Deploying project is automatically added to OpenShift Server adapter after application import: * after application import contains the deploying project: !server.png|thumbnail! When created manually via OpenShift Explorer (Application - Create Server Adapter), the deploying project is not automatically added, even though I'm selecting the deploying project: * !server2.png|thumbnail! *->* !server1.png|thumbnail! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13862) Deploying project should be automatically added to OpenShift Server adapter

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13862?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-13862: ----------------------------------- Attachment: server.png server1.png server2.png > Deploying project should be automatically added to OpenShift Server adapter > --------------------------------------------------------------------------- > > Key: JBIDE-13862 > URL: https://issues.jboss.org/browse/JBIDE-13862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > Attachments: server.png, server1.png, server2.png > > > Deploying project is automatically added to OpenShift Server adapter after application import: > * after application import contains the deploying project: !server.png|thumbnail! > When created manually via OpenShift Explorer (Application - Create Server Adapter), the deploying project is not automatically added, even though I'm selecting the deploying project: > * !server2.png|thumbnail! *->* !server1.png|thumbnail! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13841) Fix ModeShape bot tests to run with Java 7

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13841?page=com.atlassian.jira.plugi... ] Andrej Podhradsky resolved JBIDE-13841. --------------------------------------- Resolution: Done https://github.com/jbosstools/jbosstools-integration-tests/pull/204 > Fix ModeShape bot tests to run with Java 7 > ------------------------------------------ > > Key: JBIDE-13841 > URL: https://issues.jboss.org/browse/JBIDE-13841 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: QA > Affects Versions: 4.0.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Priority: Minor > > ModeShape bot tests fail with Java 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13603) Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13603?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13603: ------------------------------------ I think what happened here is that while the parent pom was updated to point to the new TP (4.22.2) the jobs were still using the 4.22.1 version. So... we're going to need to respin JBT and JBDS. :( > Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP > --------------------------------------------------- > > Key: JBIDE-13603 > URL: https://issues.jboss.org/browse/JBIDE-13603 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, maven > Affects Versions: 4.0.0.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Labels: respin-a > Fix For: 4.0.1.Final > > > Although we agreed to not backport all the changes linked to the jbt->m2e-wtp configurator migration (see JBIDE-13048), we can still make the 4.0.x stream of JBT / JBDS use the latest m2e 1.3 and m2e-wtp (core) 0.17.0. > So JBT 4.0.1 / JBDS 6.0.1 would keep their JBoss JSF/JAX-RS/JPA configurators, but still use the latest and greatest m2e core stuff. > * from http://download.eclipse.org/m2e-wtp/milestones/juno/0.17.0 : > org.eclipse.m2e.wtp.feature 0.17.0.20130212-1821 > (org.sonatype.m2e.mavenarchiver 0.15.0.201207090125-signed-201209140800 is identical to previous versions) > * m2e 1.3.1 can also be mirrored from http://download.eclipse.org/technology/m2e/milestones/1.3 : > org.eclipse.m2e.feature 1.3.1.20130219-0909.jar > org.eclipse.m2e.logback.feature 1.3.1.20130219-0909.jar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13821) CI runs tests against minimum instead of maximum

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13821?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-13821. -------------------------------- Resolution: Done OK, old variable removed. > CI runs tests against minimum instead of maximum > ------------------------------------------------ > > Key: JBIDE-13821 > URL: https://issues.jboss.org/browse/JBIDE-13821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.0.x, 4.1.0.Alpha2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > As Maven executions set a value for the TARGET_PLATFORM_VERSION value, this property is not overriden by the maximum profile. > Maven order to set properties is > # look a -D... to set property, if not found > # look at active profiles to set property, if not found > # look at default value of property to set it > This makes that in mvn execution for tests, the TARGET_PLATFORM_VERSION is set to minimal is CI jobs, whereas with using the -Pmaximun profile, we expect maximum. > This is a critical issue since it caused hours of confusions to debug on 4.0.x branch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2013