October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3547. ---------------------------------- Resolution: Done Merged. > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 8.1.1.GA, 9.1.0.Beta1, 9.0.0.GA, 8.1.0.GA, 8.0.0.GA, 7.1.1.GA > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3547: -------------------------------- > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3547: --------------------------------- > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > Assignee: Alexey Kazakov > Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1 > > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-20947. --------------------------------- Resolution: Done Made a new commit, old commit had incorrect jira number. * 784c82b - (HEAD, origin/jbosstools-4.3.x, jbosstools-4.3.x) JBIDE-20947 - fixing bad upversion in maintenance, AS project (40 seconds ago, Rob Stryker) * 648b542 - JBIDE-20974 - Upversion maintenance (8 days ago, Rob Stryker) Also astools was incorrectly upversioned 2 weeks ago in maintenance stream, hence the second commit. > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: Please perform the following tasks: > If you expect to be doing 4.3.x maintenance work in your component: > 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.) > 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above. > 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-20947. ------------------------------- > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: Please perform the following tasks: > If you expect to be doing 4.3.x maintenance work in your component: > 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.) > 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above. > 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-20947: ----------------------------------- Resolution: (was: Done) Assignee: Rob Stryker (was: Nick Boldt) > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: Please perform the following tasks: > If you expect to be doing 4.3.x maintenance work in your component: > 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.) > 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above. > 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21031?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21031: ------------------------------- Description: Versionwatch reports [1] that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... But in 9.0.0 we had 3.1.0: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... So, in master, we have 3.2.0, which is seen by VW as being a lower version. Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. [1] https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch... and https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch... was: Versionwatch reports that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... But in 9.0.0 we had 3.1.0: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... So, in master, we have 3.2.0, which is seen by VW as being a lower version. Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. > Version of AS features in 4.3.x branch is greater than in master (4.4.x) > ------------------------------------------------------------------------ > > Key: JBIDE-21031 > URL: https://issues.jboss.org/browse/JBIDE-21031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Versionwatch reports [1] that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... > But in 9.0.0 we had 3.1.0: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... > So, in master, we have 3.2.0, which is seen by VW as being a lower version. > Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. > [1] https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch... and https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21031: ---------------------------------- Summary: Version of AS features in 4.3.x branch is greater than in master (4.4.x) Key: JBIDE-21031 URL: https://issues.jboss.org/browse/JBIDE-21031 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1 Reporter: Nick Boldt Versionwatch reports that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... But in 9.0.0 we had 3.1.0: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... So, in master, we have 3.2.0, which is seen by VW as being a lower version. Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21031?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21031: ------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > Version of AS features in 4.3.x branch is greater than in master (4.4.x) > ------------------------------------------------------------------------ > > Key: JBIDE-21031 > URL: https://issues.jboss.org/browse/JBIDE-21031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Versionwatch reports that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... > But in 9.0.0 we had 3.1.0: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... > So, in master, we have 3.2.0, which is seen by VW as being a lower version. > Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21031?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21031: ---------------------------------- Assignee: Rob Stryker > Version of AS features in 4.3.x branch is greater than in master (4.4.x) > ------------------------------------------------------------------------ > > Key: JBIDE-21031 > URL: https://issues.jboss.org/browse/JBIDE-21031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Versionwatch reports that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... > But in 9.0.0 we had 3.1.0: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... > So, in master, we have 3.2.0, which is seen by VW as being a lower version. > Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2015