March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13868) Project Archives incorrectly loading saved .packages

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13868?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13868: -------------------------------- Fix Version/s: 4.0.x > Project Archives incorrectly loading saved .packages > ---------------------------------------------------- > > Key: JBIDE-13868 > URL: https://issues.jboss.org/browse/JBIDE-13868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Archives > Affects Versions: 4.0.0.Final > Environment: Eclipse juno 32 bit > Reporter: Rafael Sisto > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.0.x > > Attachments: .packages, loaded packages.png > > > After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully. > After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset. > Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars. -- 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-13868) Project Archives incorrectly loading saved .packages

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13868?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13868: ------------------------------------- Committed a fix to master. Will link PR for maintenance if possible. > Project Archives incorrectly loading saved .packages > ---------------------------------------------------- > > Key: JBIDE-13868 > URL: https://issues.jboss.org/browse/JBIDE-13868 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Affects Versions: 4.0.0.Final > Environment: Eclipse juno 32 bit > Reporter: Rafael Sisto > Assignee: Rob Stryker > Attachments: .packages, loaded packages.png > > > After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully. > After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset. > Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars. -- 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-13868) Project Archives incorrectly loading saved .packages

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13868?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13868: ------------------------------------- Regression from JBIDE-12336 > Project Archives incorrectly loading saved .packages > ---------------------------------------------------- > > Key: JBIDE-13868 > URL: https://issues.jboss.org/browse/JBIDE-13868 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Affects Versions: 4.0.0.Final > Environment: Eclipse juno 32 bit > Reporter: Rafael Sisto > Assignee: Rob Stryker > Attachments: .packages, loaded packages.png > > > After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully. > After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset. > Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars. -- 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-13602) Backport to 4.0.x - Null Java EE Web Project Archetype

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13602?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-13602. -------------------------------- Verified JBDS 6.0.1.CR1a, L64 > Backport to 4.0.x - Null Java EE Web Project Archetype > ------------------------------------------------------ > > Key: JBIDE-13602 > URL: https://issues.jboss.org/browse/JBIDE-13602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.0.0.Final > Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final > Reporter: Fred Bricon > Assignee: Denis Golovin > Priority: Minor > Labels: maven > Fix For: 4.0.1.Final > > > When trying to create a new Java EE Web Project, the following description is presented: > {quote} > This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1. > This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. > Project based on the *null:null:null* Maven archetype > {quote} > If I go forward with the creation of the project, I get the following error message: > {quote} > Failed to create project. > Root cause: For artifact null:null:null:pom : The group id cannot be empty. > {quote} -- 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 Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13859?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-13859. -------------------------------- > 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-13821) CI runs tests against minimum instead of maximum

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13821?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-13821. -------------------------------- Closing this one, if anything please reopen > 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

[JBoss JIRA] (JBIDE-13874) JPP not instantiated by runtime detection - master

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13874?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-13874: ---------------------------------- Fix Version/s: (was: 4.0.1.Final) > JPP not instantiated by runtime detection - master > -------------------------------------------------- > > Key: JBIDE-13874 > URL: https://issues.jboss.org/browse/JBIDE-13874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.1.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > > Use runtime detection against a folder containing JPP 6, and try to have it create the server. It does not create any server. -- 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-13874) JPP not instantiated by runtime detection - master

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13874?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-13874. ----------------------------------- Resolution: Done > JPP not instantiated by runtime detection - master > -------------------------------------------------- > > Key: JBIDE-13874 > URL: https://issues.jboss.org/browse/JBIDE-13874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.1.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > > Use runtime detection against a folder containing JPP 6, and try to have it create the server. It does not create any server. -- 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-13683) JPP not instantiated by runtime detection

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13683?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13683. --------------------------------- Created a clone for 4.1.x (JBIDE-13874) so can close this JIRA. > JPP not instantiated by runtime detection > ----------------------------------------- > > Key: JBIDE-13683 > URL: https://issues.jboss.org/browse/JBIDE-13683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.0.1.Final > > > Use runtime detection against a folder containing JPP 6, and try to have it create the server. It does not create any server. -- 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-13874) JPP not instantiated by runtime detection - master

by Martin Malina (JIRA)

Martin Malina created JBIDE-13874: ------------------------------------- Summary: JPP not instantiated by runtime detection - master Key: JBIDE-13874 URL: https://issues.jboss.org/browse/JBIDE-13874 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 4.0.1.Final Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.0.1.Final, 4.1.0.Alpha2 Use runtime detection against a folder containing JPP 6, and try to have it create the server. It does not create any server. -- 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