September 2015 - jbosstools-issues

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-508: ---------------------------------- Fixed typos in title and description. Max, you need a new keyboard. :D > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-508: ----------------------------- Summary: integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism (was: integration stacks updatsesites mixes discovery and earlyaccess causing inconsistent update mechanis,) > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discoveyr plugins was kept *separate* from the actual updatesites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stacks updatsesites mixes discovery and earlyaccess causing inconsistent update mechanis,

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-508: ----------------------------- Description: While reviewing JBIDE-20803 I noticed the following: {code} jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... {code} The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: But there are a few problems: 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. #1 is mainly just to reduce the number of updatesites actually necessary for users to work with #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. I would also have expected that the discovery site with the discoveyr plugins was kept *separate* from the actual updatesites to avoid any coupling between these. was: While reviewing JBIDE-20803 I noticed the following: {code] jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... {code} The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: But there are a few problems: 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. #1 is mainly just to reduce the number of updatesites actually necessary for users to work with #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. I would also have expected that the discovery site with the discoveyr plugins was kept *separate* from the actual updatesites to avoid any coupling between these. > integration stacks updatsesites mixes discovery and earlyaccess causing inconsistent update mechanis, > ----------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discoveyr plugins was kept *separate* from the actual updatesites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20812) For JBIDE 4.3.0.Final: Code Freeze + Branch [Hibernate]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20812?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20812. ---------------------------------- Assignee: Koen Aers Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [Hibernate] > ------------------------------------------------------- > > Key: JBIDE-20812 > URL: https://issues.jboss.org/browse/JBIDE-20812 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [Hibernate]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20825) For JBIDE 4.3.0.Final: Code Freeze + Branch [LiveReload]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20825?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20825. ---------------------------------- Assignee: Xavier Coulon Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [LiveReload] > -------------------------------------------------------- > > Key: JBIDE-20825 > URL: https://issues.jboss.org/browse/JBIDE-20825 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [LiveReload]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20822) For JBIDE 4.3.0.Final: Code Freeze + Branch [Arquillian]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20822?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20822. ---------------------------------- Assignee: Snjezana Peco Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [Arquillian] > -------------------------------------------------------- > > Key: JBIDE-20822 > URL: https://issues.jboss.org/browse/JBIDE-20822 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [Arquillian]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20821) For JBIDE 4.3.0.Final: Code Freeze + Branch [Webservices]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20821?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20821. ---------------------------------- Assignee: Xavier Coulon Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [Webservices] > --------------------------------------------------------- > > Key: JBIDE-20821 > URL: https://issues.jboss.org/browse/JBIDE-20821 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [Webservices]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20820) For JBIDE 4.3.0.Final: Code Freeze + Branch [BrowserSim]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20820?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20820. ---------------------------------- Assignee: Konstantin Marmalyukov Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [BrowserSim] > -------------------------------------------------------- > > Key: JBIDE-20820 > URL: https://issues.jboss.org/browse/JBIDE-20820 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [BrowserSim]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20819) For JBIDE 4.3.0.Final: Code Freeze + Branch [Birt]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20819?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20819. ---------------------------------- Assignee: Snjezana Peco Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [Birt] > -------------------------------------------------- > > Key: JBIDE-20819 > URL: https://issues.jboss.org/browse/JBIDE-20819 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [Birt]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20780) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20780?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-20780. ------------------------------- Resolution: Done Upversioned astools, jmx by minor, wtp and archives to .100 All unit tests pass. > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Server] > ---------------------------------------------------------- > > Key: JBIDE-20780 > URL: https://issues.jboss.org/browse/JBIDE-20780 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Server]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 September 2015