August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15344) use latest parent pom & target platform so we can release BPEL tooling v 1.2.1.Final

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15344: ---------------------------------- Summary: use latest parent pom & target platform so we can release BPEL tooling v 1.2.1.Final Key: JBIDE-15344 URL: https://issues.jboss.org/browse/JBIDE-15344 Project: Tools (JBoss Tools) Issue Type: Bug Components: BPEL Affects Versions: 4.1.0.Final Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.0.Final Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha1-SNAPSHOT. Target platform referenced should be the Kepler version (4.1.1.Final) rather than the Juno version (4.0.0). Once that's fixed and the build is blue, we should release BPEL tooling v 1.2.100.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15344) use latest parent pom & target platform so we can release BPEL tooling v 1.2.1.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15344?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15344: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-bpel/pull/14 (was: https://github.com/jbosstools/jbosstools-bpel/pull/12, https://github.com/jbosstools/jbosstools-bpel/pull/13) > use latest parent pom & target platform so we can release BPEL tooling v 1.2.1.Final > ------------------------------------------------------------------------------------ > > Key: JBIDE-15344 > URL: https://issues.jboss.org/browse/JBIDE-15344 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Final > > > Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha1-SNAPSHOT. > Target platform referenced should be the Kepler version (4.1.1.Final) rather than the Juno version (4.0.0). > Once that's fixed and the build is blue, we should release BPEL tooling v 1.2.100.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-141?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-141: ---------------------------------- New sites created under here for bpel, esb, jbpm: http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... http://download.jboss.org/jbosstools/updates/development/kepler/integrati... Next, I need to do the same for the Juno stream (but that'll require rebuilding them w/ the updated 4.0.x TP, as they currently use 4.0.0-SNAPSHOT version). > fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb > ----------------------------------------------------------------------------- > > Key: JBTIS-141 > URL: https://issues.jboss.org/browse/JBTIS-141 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, ESB, jBPM3 > Affects Versions: 4.0.0, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1, 4.1.1 > > > Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. > Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15342) use latest parent pom & target platform so we can release ESB tooling v 1.5.300.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15342?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15342: ------------------------------------ Nick said: {quote}I propose we remove [1], respin it correctly from the correct 4.1.1.Final target platform and 4.1.0.Final-SNAPSHOT parent pom, and re-release it here [2]. [1] http://download.jboss.org/jbosstools/updates/development/kepler/integrati... [2] http://download.jboss.org/jbosstools/updates/development/kepler/integrati... Then we can update the composite site metadata files to point to the new correctly named site.{quote} Paul replied: {quote}Sorry - I didn't rebuild it with the new version - just copied it up to development. I like your proposal.{quote} So, I've deleted [1] and created [2]. > use latest parent pom & target platform so we can release ESB tooling v 1.5.300.Final > ------------------------------------------------------------------------------------- > > Key: JBIDE-15342 > URL: https://issues.jboss.org/browse/JBIDE-15342 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: esb > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Brian Fitzpatrick > Fix For: 4.1.0.Final > > > Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.CR1-SNAPSHOT. > Target platform referenced should be the Kepler version (4.1.1.Final) rather than the Juno version (4.0.0). > Once that's fixed and the build is blue, we should release ESB tooling v 1.5.300.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-141?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-141 at 8/15/13 4:37 PM: ----------------------------------------------------------- *JBTIS 4.1.x*: https://github.com/jbosstools/jbosstools-integration-stack/pull/71 *JBTIS 4.0.x*: https://github.com/jbosstools/jbosstools-integration-stack/pull/72 was (Author: nickboldt): *JBTIS 4.1.x* https://github.com/jbosstools/jbosstools-integration-stack/pull/71 *JBTIS 4.0.x* https://github.com/jbosstools/jbosstools-integration-stack/pull/72 > fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb > ----------------------------------------------------------------------------- > > Key: JBTIS-141 > URL: https://issues.jboss.org/browse/JBTIS-141 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, ESB, jBPM3 > Affects Versions: 4.0.0, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1, 4.1.1 > > > Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. > Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-141: -------------------------------- Summary: fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb Key: JBTIS-141 URL: https://issues.jboss.org/browse/JBTIS-141 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: BPEL, distribution, ESB, jBPM3 Affects Versions: 4.0.0, 4.1.0.Final Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.0.1, 4.1.1 Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-5166) Classes in hibernate xml editor should have different icons for different classes types

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-5166?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-5166: --------------------------------- Description: There are four types: Class, Joined Subclass, Subclass, Union-Sublass and all those classes have the same icons now, it is really good to have different icon to distinguish different types of classes form each other. was: There are fore types: Class, Joined Subclass, Subclass, Union-Sublass and all those classes have the same icons now, it is really good to have different icon to distinguish different types of classes form each other. > Classes in hibernate xml editor should have different icons for different classes types > --------------------------------------------------------------------------------------- > > Key: JBIDE-5166 > URL: https://issues.jboss.org/browse/JBIDE-5166 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 3.1.0.M4 > Reporter: Denis Golovin > Priority: Minor > Fix For: LATER > > > There are four types: > Class, > Joined Subclass, > Subclass, > Union-Sublass > and all those classes have the same icons now, it is really good to have different icon to distinguish different types of classes form each other. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-5166) Classes in hibernate xml editor should have different icons for different classes types

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-5166?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-5166: --------------------------------- Assignee: Daniel Azarov > Classes in hibernate xml editor should have different icons for different classes types > --------------------------------------------------------------------------------------- > > Key: JBIDE-5166 > URL: https://issues.jboss.org/browse/JBIDE-5166 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 3.1.0.M4 > Reporter: Denis Golovin > Assignee: Daniel Azarov > Priority: Minor > Fix For: LATER > > > There are four types: > Class, > Joined Subclass, > Subclass, > Union-Sublass > and all those classes have the same icons now, it is really good to have different icon to distinguish different types of classes form each other. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10219) Migrate org.eclipse.core.runtime.contentTypes extension points to org.eclipse.core.contenttype.contentTypes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10219?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-10219: ----------------------------------- Description: ||Module|| PR || Status || |[Hibernate|https://github.com/jbosstools/jbosstools-hibernate]| https://github.com/jbosstools/jbosstools-hibernate/pull/22 | | |[Server|https://github.com/jbosstools/jbosstools-server]| https://github.com/jbosstools/jbosstools-server/pull/133 | | |[JST|https://github.com/jbosstools/jbosstools-jst]| not affected | | |[Java EE|https://github.com/jbosstools/jbosstools-javaee]| https://github.com/jbosstools/jbosstools-javaee/pull/125 | Merged | |[jBPM|https://github.com/jbosstools/jbosstools-jbpm]| | | was: ||Module|| PR || Status || |[Hibernate|https://github.com/jbosstools/jbosstools-hibernate]| https://github.com/jbosstools/jbosstools-hibernate/pull/22 | | |[Server|https://github.com/jbosstools/jbosstools-server]| https://github.com/jbosstools/jbosstools-server/pull/133 | | |[JST|https://github.com/jbosstools/jbosstools-jst]| not affected | | |[Java EE|https://github.com/jbosstools/jbosstools-javaee]| https://github.com/jbosstools/jbosstools-javaee/pull/125 | | |[jBPM|https://github.com/jbosstools/jbosstools-jbpm]| https://github.com/jbosstools/jbosstools-jbpm/pull/16 | | > Migrate org.eclipse.core.runtime.contentTypes extension points to org.eclipse.core.contenttype.contentTypes > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-10219 > URL: https://issues.jboss.org/browse/JBIDE-10219 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: archives, common/jst/core, hibernate, jbpm, Seam 2, server > Affects Versions: 3.3.0.M4 > Reporter: Denis Golovin > Assignee: Daniel Azarov > Fix For: 4.2.0.Alpha1 > > Attachments: JBIDE-10219.patch > > > ||Module|| PR || Status || > |[Hibernate|https://github.com/jbosstools/jbosstools-hibernate]| https://github.com/jbosstools/jbosstools-hibernate/pull/22 | | > |[Server|https://github.com/jbosstools/jbosstools-server]| https://github.com/jbosstools/jbosstools-server/pull/133 | | > |[JST|https://github.com/jbosstools/jbosstools-jst]| not affected | | > |[Java EE|https://github.com/jbosstools/jbosstools-javaee]| https://github.com/jbosstools/jbosstools-javaee/pull/125 | Merged | > |[jBPM|https://github.com/jbosstools/jbosstools-jbpm]| | | -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15258) Move performance tests in separate github repository from jbosstools-base/tests

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15258?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-15258: ------------------------------------- Assignee: Denis Golovin > Move performance tests in separate github repository from jbosstools-base/tests > ------------------------------------------------------------------------------- > > Key: JBIDE-15258 > URL: https://issues.jboss.org/browse/JBIDE-15258 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core, QA > Affects Versions: 4.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.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

12 years, 8 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 August 2013