[JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-14642.
------------------------------
Fix Version/s: 4.5.1.AM1
(was: 4.5.x)
Resolution: Done
We've been using baseline checks for a couple years now, and they DO catch accidents where people forget to upversion.
So since there's been no movement here on creating a "build that does version validation" beyond what we have with versionwatch [1], I'm going to close this.
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> How to automate process of bumping version for changed modules/submodules for every release
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-14642
> URL: https://issues.jboss.org/browse/JBIDE-14642
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.1.0.Beta1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Optional
> Labels: versioning
> Fix For: 4.5.1.AM1
>
>
> The versions of plugins are constantly discovered to not be uptodated when they should and things like Usage and others where it is critical are not getting bumped.
> We need two things:
> A) detect when versions are not bumped properly - we got parts of this in various places, but they are not run nor documented regularly (having a green build verifying versions are not conflicting would be a Good Thing)
> B) document/automate a process which every affected lead can follow to make this happen and if not See #A
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18876:
-------------------------------
Fix Version/s: 4.5.1.AM1
(was: 4.5.x)
> Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18876
> URL: https://issues.jboss.org/browse/JBIDE-18876
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.5.1.AM1
>
>
> Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task.
> So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus.
> Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-18876.
------------------------------
Resolution: Cannot Reproduce Bug
Over a year of silence. Closing.
> Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18876
> URL: https://issues.jboss.org/browse/JBIDE-18876
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.5.1.AM1
>
>
> Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task.
> So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus.
> Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBTIS-1161) Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1161?page=com.atlassian.jira.plugin... ]
Nick Boldt commented on JBTIS-1161:
-----------------------------------
Solution here is most likely to remove the certification from the JBT IS plugin.xml since generally, we don't certify JBT components (only devstudio ones).
> Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-1161
> URL: https://issues.jboss.org/browse/JBTIS-1161
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, ESB
> Affects Versions: 11.0.0.GA
> Reporter: Automated Error Reporting Bot
> Assignee: Paul Leacu
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- manderse(a)redhat.com wrote: ---
> test message - why is this happening.
>
> code: 0
> plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
> fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
> exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
> exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> number of children: 0
>
> org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
>
>
> General Information:
> reported-by: manderse(a)redhat.com
> anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.11.2 (x86_64) - cocoa
> jre-version: 1.8.0_20-b26
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.jface_3.11.0.v20150602-1400
> 2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
> 3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> 4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56b7dc...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBTIS-1161) Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1161?page=com.atlassian.jira.plugin... ]
Nick Boldt updated JBTIS-1161:
------------------------------
Project: JBoss Tools Integration Stack (was: Tools (JBoss Tools))
Key: JBTIS-1161 (was: JBIDE-22703)
Component/s: distribution
ESB
(was: central-update)
Affects Version/s: 11.0.0.GA
(was: 4.4.1.AM1)
Fix Version/s: (was: 4.5.x)
> Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-1161
> URL: https://issues.jboss.org/browse/JBTIS-1161
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, ESB
> Affects Versions: 11.0.0.GA
> Reporter: Automated Error Reporting Bot
> Assignee: Nick Boldt
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- manderse(a)redhat.com wrote: ---
> test message - why is this happening.
>
> code: 0
> plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
> fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
> exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
> exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> number of children: 0
>
> org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
>
>
> General Information:
> reported-by: manderse(a)redhat.com
> anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.11.2 (x86_64) - cocoa
> jre-version: 1.8.0_20-b26
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.jface_3.11.0.v20150602-1400
> 2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
> 3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> 4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56b7dc...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBTIS-1161) Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1161?page=com.atlassian.jira.plugin... ]
Nick Boldt reassigned JBTIS-1161:
---------------------------------
Assignee: Paul Leacu (was: Nick Boldt)
> Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-1161
> URL: https://issues.jboss.org/browse/JBTIS-1161
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, ESB
> Affects Versions: 11.0.0.GA
> Reporter: Automated Error Reporting Bot
> Assignee: Paul Leacu
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- manderse(a)redhat.com wrote: ---
> test message - why is this happening.
>
> code: 0
> plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
> fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
> exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
> exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> number of children: 0
>
> org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
>
>
> General Information:
> reported-by: manderse(a)redhat.com
> anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.11.2 (x86_64) - cocoa
> jre-version: 1.8.0_20-b26
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.jface_3.11.0.v20150602-1400
> 2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
> 3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> 4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56b7dc...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months