December 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-10052) New Maven Project Dialog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10052?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-10052: -------------------------------- Component/s: UpStream > New Maven Project Dialog > ------------------------ > > Key: JBIDE-10052 > URL: https://issues.jboss.org/browse/JBIDE-10052 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, UpStream > Reporter: Burr Sutter > Assignee: Fred Bricon > Labels: eap6-ux > Fix For: LATER > > Attachments: New_Maven_Project.odp > > > Many of our end-users have not yet fully embraced and learned Maven. The New Maven Project Wizard can derail the novice user. > two suggestions: > - prepopulate the artifactid > - sync up groupid and java package > - find a way to make picking the right archetype easy > see screenshots in attachment -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13283) Use Akamai for Target-Platform, Mirror, releases stuff

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13283?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13283: ----------------------------------- Summary: Use Akamai for Target-Platform, Mirror, releases stuff (was: Use Akamai for Target-Platform & Mirror stuff) Release Notes Text: (was: All our repositories that are either mirrors or target-platform are not updated often. Then we could use Akamai to improve performances. At least this folder would be good: http://download.jboss.org/jbosstools/updates/requirements/) Description: All our repositories that are either mirrors or target-platform are not updated often. Then we could use Akamai to improve performances. At least these folders would be good: * http://download.jboss.org/jbosstools/updates/requirements/ * http://download.jboss.org/jbosstools/updates/stable/ > Use Akamai for Target-Platform, Mirror, releases stuff > ------------------------------------------------------ > > Key: JBIDE-13283 > URL: https://issues.jboss.org/browse/JBIDE-13283 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > All our repositories that are either mirrors or target-platform are not updated often. Then we could use Akamai to improve performances. At least these folders would be good: > * http://download.jboss.org/jbosstools/updates/requirements/ > * http://download.jboss.org/jbosstools/updates/stable/ -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13316) Imporve versioning for TP using standard Maven way

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13316: ---------------------------------------- I created 2 branches named "tp-4.2.0.c" and "tp-4.2.1.a" which contain different versions of target platforms. See graph here: https://github.com/jbosstools/jbosstools-build/network So "miminal" currently becomes referencing branch tp-4.2.0.c and "maximal" is tp-4.2.1.a. [~nickboldt] [~maxandersen] Can I have your feedback on this approach? I think this is starting to show that target-platform and parent pom are now so loosely coupled that it does not make sense to have them in the same git repository. > Imporve versioning for TP using standard Maven way > -------------------------------------------------- > > Key: JBIDE-13316 > URL: https://issues.jboss.org/browse/JBIDE-13316 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > Currently, we deal with explicit versions in folder names that make it confusing to understand how target-platforms are versioned. > Instead, we should use usual Maven way and Git branches: one Git branch for each version of TPs. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13316) Imporve versioning for TP using standard Maven way

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-13316: -------------------------------------- Summary: Imporve versioning for TP using standard Maven way Key: JBIDE-13316 URL: https://issues.jboss.org/browse/JBIDE-13316 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: target-platform Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 4.1.0.Alpha1 Currently, we deal with explicit versions in folder names that make it confusing to understand how target-platforms are versioned. Instead, we should use usual Maven way and Git branches: one Git branch for each version of TPs. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10960) RHEL6 slaves fail to run SWT-based tests

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10960?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-10960. ------------------------------------ Fix Version/s: 4.1.0.Alpha1 (was: 3.3.x) (was: 4.0.x) Resolution: Done This seems to be OK now we're using Xvnc + metacity. > RHEL6 slaves fail to run SWT-based tests > ----------------------------------------- > > Key: JBIDE-10960 > URL: https://issues.jboss.org/browse/JBIDE-10960 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6569) Make git repo available for JBoss Tools

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6569?page=com.atlassian.jira.plugin... ] Mickael Istria closed JBIDE-6569. --------------------------------- Fix Version/s: 4.0.0.Final (was: LATER) Resolution: Duplicate Issue This request was implicitly resolved as part of the move to Git. > Make git repo available for JBoss Tools > --------------------------------------- > > Key: JBIDE-6569 > URL: https://issues.jboss.org/browse/JBIDE-6569 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.0.0.Final > > > I think it would be useful to explore how to make a git-svn repo available for jboss tools trunk. > Opening this issue for keeping track of what have been attempted so far. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10052) New Maven Project Dialog

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10052?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-10052: ----------------------------------- Assignee: Fred Bricon Fix Version/s: 4.1.0.Alpha1 (was: 3.2.x) (was: 3.3.x) Component/s: maven (was: updatesite) (was: Marketplace) > New Maven Project Dialog > ------------------------ > > Key: JBIDE-10052 > URL: https://issues.jboss.org/browse/JBIDE-10052 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Reporter: Burr Sutter > Assignee: Fred Bricon > Labels: eap6-ux > Fix For: 4.1.0.Alpha1 > > Attachments: New_Maven_Project.odp > > > Many of our end-users have not yet fully embraced and learned Maven. The New Maven Project Wizard can derail the novice user. > two suggestions: > - prepopulate the artifactid > - sync up groupid and java package > - find a way to make picking the right archetype easy > see screenshots in attachment -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13110) Put CI jobs for target-platform into a dedicated view

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13110?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-13110. ---------------------------------- Resolution: Rejected A view was created for target-platform stuff. However TP jobs will remain in the DevStudio* views too, since this is where we usually expect everything to be. > Put CI jobs for target-platform into a dedicated view > ----------------------------------------------------- > > Key: JBIDE-13110 > URL: https://issues.jboss.org/browse/JBIDE-13110 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng, target-platform > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > > As we now agree that TP are not following JBT versionning and that they are built independently of JBT releases, it would make sense to replace jbosstools-*-target-platforms jobs by jobs whose name is not related to a JBT version or branch, and to put them into their own view. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12226) org.jboss.tools.runtime.soa.test are useless

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12226?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-12226: ----------------------------------- Component/s: (was: Build/Releng) > org.jboss.tools.runtime.soa.test are useless > -------------------------------------------- > > Key: JBIDE-12226 > URL: https://issues.jboss.org/browse/JBIDE-12226 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: SOA Tooling > Affects Versions: 4.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Douglas Palmer > Fix For: 4.0.0.Alpha1-SOA > > > The tests inside org.jboss.tools.runtime.soa.test are just copy-pasted from org.jboss.tools.runtime.test. They should be removed since they are not accurate in SOA Tooling. > Instead, the runtime-soa module should contain test that verify it is able to detect SOA-P for SOA Tooling. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12393) Cannot open persistence.xml with doubleclick

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12393?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-12393. ------------------------------- > Cannot open persistence.xml with doubleclick > -------------------------------------------- > > Key: JBIDE-12393 > URL: https://issues.jboss.org/browse/JBIDE-12393 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 3.3.1 > Reporter: Jaroslav Jankovič > Assignee: Dmitry Geraskov > Fix For: 3.3.2 > > -- 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, 4 months

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 December 2012