August 2013 - jbosstools-issues - Jboss List Archives

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15341?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15341: ------------------------------------ Job renamed from old JBT 4.0 convention to new JBTIS-<project>-<branch> and kicked. Waiting for a free slave. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=1012 > use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final > -------------------------------------------------------------------------------------- > > Key: JBIDE-15341 > URL: https://issues.jboss.org/browse/JBIDE-15341 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Robert (Bob) Brodt > 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-15338) use latest parent pom & target platform so we can release jBPM3 tooling v 4.5.200.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15338?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15338: ------------------------------------ Job renamed from old JBT 4.0 convention to new JBTIS-<project>-<branch> and kicked. Waiting for a free slave. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=2006 > use latest parent pom & target platform so we can release jBPM3 tooling v 4.5.200.Final > --------------------------------------------------------------------------------------- > > Key: JBIDE-15338 > URL: https://issues.jboss.org/browse/JBIDE-15338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jbpm > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Koen Aers > 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.Alpha2-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 jbpm3 tooling v 4.5.200.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-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: ------------------------------------ Job renamed from old JBT 4.0 convention to new JBTIS-<project>-<branch> and kicked. Waiting for a free slave. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=1188 > 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] (TOOLSDOC-310) redirect /latest to /reference where the latest released docs can be found

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-310?page=com.atlassian.jira.plug... ] Nick Boldt edited comment on TOOLSDOC-310 at 8/15/13 11:10 AM: --------------------------------------------------------------- Release of JBT 4.1.0.Final docs and update of /latest symlink: https://github.com/jbosstools/jbosstools-documentation/pull/163 [~mmurray]: please approve the above PR & push it in. Files are already updated on http://docs.jboss.org/tools/ and http://docs.jboss.org/tools/latest/ Also updated https://www.jboss.org/tools/docs/reference/ If we all agree, I think this issue can be closed. :D was (Author: nickboldt): Release of JBT 4.1.0.Final docs and update of /latest symlink: https://github.com/jbosstools/jbosstools-documentation/pull/163 [~mmurray]: please approve the above PR & push it in. > redirect /latest to /reference where the latest released docs can be found > -------------------------------------------------------------------------- > > Key: TOOLSDOC-310 > URL: https://issues.jboss.org/browse/TOOLSDOC-310 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.1.0 > > > for some reason https://github.com/jbosstools/jbosstools-documentation/pull/48 removed the latest link assuming latest is used to point to the nightly build. > That is not what it is for. > It is to point to the latest docs made available. > This link (before: http://docs.jboss.org/tools/latest/) was used to point to the last latest documentation. > I believe this should be put back since this is how other docs refer to the latest version. > We could even go so ar to create a docs.jboss.org/tools/4.0, docs.jboss.org/tools/3.3 etc. folder each with their /latest link in them. > Latest links are trivial to make with sftp as part of the release upload anyway thus should be all possible to script if it is too cumbersome to remember. -- 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-15343) JBIDE-14979 followup

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15343: ----------------------------------- Summary: JBIDE-14979 followup Key: JBIDE-15343 URL: https://issues.jboss.org/browse/JBIDE-15343 Project: Tools (JBoss Tools) Issue Type: Task Components: server Affects Versions: 4.1.0.Final Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.1.1.Final, 4.2.0.Alpha1 Update javadoc as per max's request in https://github.com/jbosstools/jbosstools-server/pull/116 -- 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-15312) Update all AS versions AND manifest.mf dependency version ranges

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15312?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15312: ------------------------------------- Maintenance should be pushed to 2.4.200 Master should be pushed to 2.5.0 > Update all AS versions AND manifest.mf dependency version ranges > ----------------------------------------------------------------- > > Key: JBIDE-15312 > URL: https://issues.jboss.org/browse/JBIDE-15312 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > API has been added in both branch and master. THis requires an update of version ranges. -- 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-12821) component.exclusion.patterns doesn't support regex pattern

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12821?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12821: --------------------------------------------- [~rob.stryker] we need to see how much this change will impact. it is a rather nasty issue having it "partially" work. > component.exclusion.patterns doesn't support regex pattern > ---------------------------------------------------------- > > Key: JBIDE-12821 > URL: https://issues.jboss.org/browse/JBIDE-12821 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven, server > Affects Versions: 3.3.1.Final > Reporter: Sébastien Pinel > Assignee: Rob Stryker > Priority: Critical > Labels: f2f2012 > Fix For: 4.2.0.Alpha1 > > Attachments: webapp.zip > > > Using maven-war-plugin, you can use packageIncludes/packageExcludes with a regex (e.g. http://maven.apache.org/plugins/maven-war-plugin/examples/including-exclu...). > With m2e-wtp, the property is correctly added to "org.eclipse.wst.common.component" setting file but JBoss AS tools only support 2 special characters ('*', '?'). -- 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-12821) component.exclusion.patterns doesn't support regex pattern

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12821?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12821: ---------------------------------------- Fix Version/s: (was: 4.1.1.Final) > component.exclusion.patterns doesn't support regex pattern > ---------------------------------------------------------- > > Key: JBIDE-12821 > URL: https://issues.jboss.org/browse/JBIDE-12821 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven, server > Affects Versions: 3.3.1.Final > Reporter: Sébastien Pinel > Assignee: Rob Stryker > Priority: Critical > Labels: f2f2012 > Fix For: 4.2.0.Alpha1 > > Attachments: webapp.zip > > > Using maven-war-plugin, you can use packageIncludes/packageExcludes with a regex (e.g. http://maven.apache.org/plugins/maven-war-plugin/examples/including-exclu...). > With m2e-wtp, the property is correctly added to "org.eclipse.wst.common.component" setting file but JBoss AS tools only support 2 special characters ('*', '?'). -- 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-12821) component.exclusion.patterns doesn't support regex pattern

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12821?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12821: ---------------------------------------- Fix Version/s: 4.1.1.Final 4.2.0.Alpha1 (was: 4.1.x) (was: 4.2.x) > component.exclusion.patterns doesn't support regex pattern > ---------------------------------------------------------- > > Key: JBIDE-12821 > URL: https://issues.jboss.org/browse/JBIDE-12821 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven, server > Affects Versions: 3.3.1.Final > Reporter: Sébastien Pinel > Assignee: Rob Stryker > Priority: Critical > Labels: f2f2012 > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > Attachments: webapp.zip > > > Using maven-war-plugin, you can use packageIncludes/packageExcludes with a regex (e.g. http://maven.apache.org/plugins/maven-war-plugin/examples/including-exclu...). > With m2e-wtp, the property is correctly added to "org.eclipse.wst.common.component" setting file but JBoss AS tools only support 2 special characters ('*', '?'). -- 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-15341) use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final

by Robert (Bob) Brodt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15341?page=com.atlassian.jira.plugi... ] Robert (Bob) Brodt commented on JBIDE-15341: -------------------------------------------- Merged your pull requests - thanks Nick! > use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final > -------------------------------------------------------------------------------------- > > Key: JBIDE-15341 > URL: https://issues.jboss.org/browse/JBIDE-15341 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Robert (Bob) Brodt > 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

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