[JBoss JIRA] (JBIDE-13452) investigate removing JBT_VERSION, JBDS_VERSION from parent pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13452?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13452 at 3/26/13 12:06 PM:
--------------------------------------------------------------
Patch to remove all references to JBDS_VERION from poms, ensure timestamps for installer/site and sources/results are the same (even though Tycho and Maven produce different timestamps), and clean up HTML pages at the same time (JBDS-2466):
https://issues.jboss.org/secure/attachment/12361568/JBIDE13452_JBDS2466.r...
was (Author: nickboldt):
Patch to fix this issue and clean up HTML pages at the same time (JBDS-2466):
https://issues.jboss.org/secure/attachment/12361568/JBIDE13452_JBDS2466.r...
> investigate removing JBT_VERSION, JBDS_VERSION from parent pom
> --------------------------------------------------------------
>
> Key: JBIDE-13452
> URL: https://issues.jboss.org/browse/JBIDE-13452
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, target-platform, updatesite
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION (min and max) from parent pom
> Can we switch to using dynamic maven variables like project.version instead?
> Moving forward, jobs will override/set the version of target platform used to build (min) and test (max), and developers will be required to decide when/if to move to a newer parent pom or target platform version(s) if needed. For projects that are released, jobs will run only when TP changes (ie., will watch the jbosstools-target-platforms repo for changes).
--
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
[JBoss JIRA] (JBIDE-13452) investigate removing JBT_VERSION, JBDS_VERSION from parent pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13452?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13452:
-------------------------------
Fix Version/s: 4.1.0.Alpha2
> investigate removing JBT_VERSION, JBDS_VERSION from parent pom
> --------------------------------------------------------------
>
> Key: JBIDE-13452
> URL: https://issues.jboss.org/browse/JBIDE-13452
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, target-platform, updatesite
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION (min and max) from parent pom
> Can we switch to using dynamic maven variables like project.version instead?
> Moving forward, jobs will override/set the version of target platform used to build (min) and test (max), and developers will be required to decide when/if to move to a newer parent pom or target platform version(s) if needed. For projects that are released, jobs will run only when TP changes (ie., will watch the jbosstools-target-platforms repo for changes).
--
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
[JBoss JIRA] (JBIDE-13452) investigate removing JBT_VERSION, JBDS_VERSION from parent pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13452?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13452:
------------------------------------
Patch to fix this issue and clean up HTML pages at the same time:
[^https://issues.jboss.org/secure/attachment/12361568/12361568_JBIDE13452_JBDS2466.remove.JBDS_VERSION_clean.up.results.html.patch.txt]
> investigate removing JBT_VERSION, JBDS_VERSION from parent pom
> --------------------------------------------------------------
>
> Key: JBIDE-13452
> URL: https://issues.jboss.org/browse/JBIDE-13452
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, target-platform, updatesite
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION (min and max) from parent pom
> Can we switch to using dynamic maven variables like project.version instead?
> Moving forward, jobs will override/set the version of target platform used to build (min) and test (max), and developers will be required to decide when/if to move to a newer parent pom or target platform version(s) if needed. For projects that are released, jobs will run only when TP changes (ie., will watch the jbosstools-target-platforms repo for changes).
--
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
[JBoss JIRA] (JBIDE-13452) investigate removing JBT_VERSION, JBDS_VERSION from parent pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13452?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13452 at 3/26/13 12:03 PM:
--------------------------------------------------------------
Patch to fix this issue and clean up HTML pages at the same time:
[^https://issues.jboss.org/secure/attachment/12361568/JBIDE13452_JBDS2466.remove.JBDS_VERSION_clean.up.results.html.patch.txt]
was (Author: nickboldt):
Patch to fix this issue and clean up HTML pages at the same time:
[^https://issues.jboss.org/secure/attachment/12361568/12361568_JBIDE13452_JBDS2466.remove.JBDS_VERSION_clean.up.results.html.patch.txt]
> investigate removing JBT_VERSION, JBDS_VERSION from parent pom
> --------------------------------------------------------------
>
> Key: JBIDE-13452
> URL: https://issues.jboss.org/browse/JBIDE-13452
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, target-platform, updatesite
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION (min and max) from parent pom
> Can we switch to using dynamic maven variables like project.version instead?
> Moving forward, jobs will override/set the version of target platform used to build (min) and test (max), and developers will be required to decide when/if to move to a newer parent pom or target platform version(s) if needed. For projects that are released, jobs will run only when TP changes (ie., will watch the jbosstools-target-platforms repo for changes).
--
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
[JBoss JIRA] (JBIDE-13452) investigate removing JBT_VERSION, JBDS_VERSION from parent pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13452?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13452 at 3/26/13 12:03 PM:
--------------------------------------------------------------
Patch to fix this issue and clean up HTML pages at the same time (JBDS-2466):
https://issues.jboss.org/secure/attachment/12361568/JBIDE13452_JBDS2466.r...
was (Author: nickboldt):
Patch to fix this issue and clean up HTML pages at the same time:
[^https://issues.jboss.org/secure/attachment/12361568/JBIDE13452_JBDS2466.remove.JBDS_VERSION_clean.up.results.html.patch.txt]
> investigate removing JBT_VERSION, JBDS_VERSION from parent pom
> --------------------------------------------------------------
>
> Key: JBIDE-13452
> URL: https://issues.jboss.org/browse/JBIDE-13452
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, target-platform, updatesite
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION (min and max) from parent pom
> Can we switch to using dynamic maven variables like project.version instead?
> Moving forward, jobs will override/set the version of target platform used to build (min) and test (max), and developers will be required to decide when/if to move to a newer parent pom or target platform version(s) if needed. For projects that are released, jobs will run only when TP changes (ie., will watch the jbosstools-target-platforms repo for changes).
--
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
[JBoss JIRA] (JBIDE-13634) Build flow jobs name/description are missing
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13634?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-13634.
------------------------------
Fix Version/s: 4.1.0.Alpha2
Resolution: Rejected
6 build flow jobs merged into a single one, so if you want to know what's been built in a given build for that job, just look in the build's console output. Missing description on the job is an upstream issue I can't fix, so closing.
> Build flow jobs name/description are missing
> ---------------------------------------------
>
> Key: JBIDE-13634
> URL: https://issues.jboss.org/browse/JBIDE-13634
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: UpStream
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> I'm trying to grok the buildflow job setup.
> For now I can just see tons of buildflow.<n>_<branch> builds are failing.
> Clicking on them gets me to for example http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBos...
> There seem to be no info in these on what they do - the name is just a number and nothing in description.
> Even when logged in I couldn't figure out how to see what these various numbers are for ?
> I did find when clicking configure that the description refer to https://issues.jboss.org/browse/JBIDE-13308 ...but that description does not show up anywhere. Is that a bug in Jenkins ?
> https://issues.jboss.org/browse/JBIDE-13308 does not seem to define what the numbers mean either.
> What am I missing ?
> Could we get some better names on these ? (ie. base-flow, 3rdparty-flow, javaee-central-flow or at least a blurp in a visible description field on where/how to view these in case the names are just to have a stable url ?
> (I do know i can click configure and go in an see the DSL but that seems rather tedious).
>
--
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
[JBoss JIRA] (JBIDE-13834) install-grinder tests fail due to missing deps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13834?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-13834.
------------------------------
Resolution: Out of Date
With Kepler M6 TP and updated central site publishing mechanism, this is no longer a problem.
> install-grinder tests fail due to missing deps
> ----------------------------------------------
>
> Key: JBIDE-13834
> URL: https://issues.jboss.org/browse/JBIDE-13834
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/90/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fbuilds%2Fstaging%2Fdevstudio-7.0_trunk.updatesite%2Fproduct%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fbuilds%2Fstaging%2Fdevstudio-7.0_trunk.updatesite%2Fproduct%2Fdevstudio-directory.xml,eclipseBundleVersion=kepler.M5,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/console}
> Contains: Only one of the following can be installed at once:
> Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20130212-1819 (org.eclipse.m2e.wtp.overlay 0.17.0.20130212-1819)
> Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20130205-1928 (org.eclipse.m2e.wtp.overlay 0.17.0.20130205-1928)
> Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20121219-1146 (org.eclipse.m2e.wtp.overlay 0.17.0.20121219-1146)
> Contains: Cannot satisfy dependency:
> Contains: From: Maven Integration (Selected) 7.0.0.Alpha1-v20130206-0326-B3219 (com.jboss.jbds.m2e.feature.feature.group 7.0.0.Alpha1-v20130206-0326-B3219)
> Contains: To: org.eclipse.m2e.wtp.feature.feature.group [0.17.0.20130205-1928]
> Contains: Cannot satisfy dependency:
> Contains: From: m2e-wtp - Maven Integration for WTP (Incubation) 0.17.0.20130205-1928 (org.eclipse.m2e.wtp.feature.feature.group 0.17.0.20130205-1928)
> Contains: To: org.eclipse.m2e.wtp.overlay [0.17.0.20130205-1928]
> Contains: Cannot satisfy dependency:
> Contains: From: m2e-wtp - Maven Integration for WTP (Incubation) 0.17.0.20130212-1819 (org.eclipse.m2e.wtp.feature.feature.group 0.17.0.20130212-1819)
> Contains: To: org.eclipse.m2e.wtp.overlay [0.17.0.20130212-1819]
> {code}
> Should clone this job so we have a stable branch version available too, pulling from these locations:
> * http://download.jboss.org/jbosstools/discovery/nightly/core/4.1.kepler/
> * http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.1.kepler/
--
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