[JBoss JIRA] (JBIDE-22286) JavaModelException below EclipseJavaUtil.findType (thrown in Openable.generateInfos)
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBIDE-22286:
-----------------------------------------------------
Summary: JavaModelException below EclipseJavaUtil.findType (thrown in Openable.generateInfos)
Key: JBIDE-22286
URL: https://issues.jboss.org/browse/JBIDE-22286
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi
Affects Versions: 4.3.1.Final
Reporter: Automated Error Reporting Bot
The following problem was reported via the automated error reporting:
Message: jboss-javaee-webapp does not exist
{noformat}
org.eclipse.jdt.core.JavaModelException: jboss-javaee-webapp does not exist
at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
at org.eclipse.jdt.internal.core.JavaProject.getJavaProjectElementInfo(JavaProject.java:1642)
at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2329)
at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2339)
at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1357)
at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1264)
at org.jboss.tools.common.util.EclipseJavaUtil.findType(EclipseJavaUtil.java:115)
at org.jboss.tools.common.java.ParametedTypeFactory.getParametedType(ParametedTypeFactory.java:157)
at org.jboss.tools.common.java.ParametedType.buildInheritance(ParametedType.java:259)
at org.jboss.tools.common.java.ParametedType.getInheritedTypes(ParametedType.java:308)
at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:400)
at org.jboss.tools.common.java.ParametedType.getAllTypes(ParametedType.java:388)
at org.jboss.tools.cdi.internal.core.impl.ProducerMethod.getAllTypes(ProducerMethod.java:112)
at org.jboss.tools.cdi.internal.core.impl.ProducerMethod.getLegalTypes(ProducerMethod.java:94)
at org.jboss.tools.cdi.internal.core.impl.CDICache.addBean(CDICache.java:319)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.addBean(CDIProject.java:1451)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1396)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1216)
at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:442)
at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:267)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
{noformat}
Bundles:
| org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.10.1.v20150725-1910 |
| org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
| org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.12.0.v20160317-0200 |
| org.eclipse.jdt.core | 3.11.0.xx-201603042130-e45 | 3.12.0.v20160315-2126 |
| org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 |
| org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 |
| org.eclipse.jst.common.project.facet.core | 1.4.400.v201403261418 | 1.4.400.v201403261418 |
| org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 |
| org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
| org.jboss.tools.batch.core | 1.7.1.CR1-v20160129-2014-B69 | 1.7.1.Final-v20160330-2256-B84 |
| org.jboss.tools.cdi.core | 1.7.1.CR1-v20160129-2014-B69 | 1.8.0.Alpha1-v20160421-2020-B942 |
| org.jboss.tools.common | 3.7.1.CR1-v20160219-2136-B86 | 3.8.0.Alpha1-v20160426-0436-B918 |
| org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Alpha1-v20160426-0436-B918 |
| org.jboss.tools.jst.web | 3.7.1.CR1-v20160128-1907-B79 | 3.7.1.Final-v20160331-0256-B96 |
| org.jboss.tools.jst.web.kb | 3.7.1.CR1-v20160128-1907-B79 | 3.7.1.Final-v20160331-0256-B96 |
Operating Systems:
| Linux | 3.13.0 | 4.2.0 |
| MacOSX | 10.11.3 | 10.11.4 |
| Windows | 6.1.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/56cb04afe4b0f02ab7...] for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22285) JavaModelException below FileSet.checkType (thrown in JavaElement.openWhenClosed)
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBIDE-22285:
-----------------------------------------------------
Summary: JavaModelException below FileSet.checkType (thrown in JavaElement.openWhenClosed)
Key: JBIDE-22285
URL: https://issues.jboss.org/browse/JBIDE-22285
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: batch
Affects Versions: 4.3.1.Final
Reporter: Automated Error Reporting Bot
The following problem was reported via the automated error reporting:
Message: HIDDEN
{noformat}
org.eclipse.jdt.core.JavaModelException: HIDDEN
at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:556)
at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:590)
at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
at org.eclipse.jdt.internal.core.BinaryType.isAnnotation(BinaryType.java:738)
at org.jboss.tools.batch.internal.core.scanner.FileSet.checkType(FileSet.java:81)
at org.jboss.tools.batch.internal.core.scanner.FileSet.add(FileSet.java:51)
at org.jboss.tools.batch.internal.core.impl.BatchBuilder.buildJars(BatchBuilder.java:226)
at org.jboss.tools.batch.internal.core.impl.BatchBuilder.build(BatchBuilder.java:140)
at org.jboss.tools.batch.internal.core.impl.BatchBuilder.<init>(BatchBuilder.java:73)
at org.jboss.tools.batch.internal.core.impl.BatchProject.build(BatchProject.java:341)
at org.jboss.tools.jst.web.kb.internal.AbstractKbProjectExtension.load(AbstractKbProjectExtension.java:163)
at org.jboss.tools.jst.web.kb.internal.AbstractKbProjectExtension.resolveStorage(AbstractKbProjectExtension.java:154)
at org.jboss.tools.jst.web.kb.internal.AbstractKbProjectExtension.resolve(AbstractKbProjectExtension.java:148)
at org.jboss.tools.batch.internal.core.impl.BatchProject$BatchBuildJob.runInWorkspace(BatchProject.java:120)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
{noformat}
Bundles:
| org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.10.1.v20150725-1910 |
| org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
| org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.11.2.v20160212-1500 |
| org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 |
| org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 |
| org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 |
| org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 |
| org.jboss.tools.batch.core | 1.7.1.Final-v20160330-2256-B84 | 1.7.1.Final-v20160330-2256-B84 |
| org.jboss.tools.common | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 |
| org.jboss.tools.common.model | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 |
| org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 |
| org.jboss.tools.jst.web | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 |
| org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 |
Operating Systems:
| Linux | 3.13.0 | 4.4.7.fc23 |
| MacOSX | 10.11.4 | 10.11.4 |
| Windows | 6.1.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57176467e4b032f683...] for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22284) ConcurrentModificationException below ArquillianUIUtil.getActiveType (thrown in FeatureMapUtil$BasicFeatureEIterator.checkModCount)
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBIDE-22284:
-----------------------------------------------------
Summary: ConcurrentModificationException below ArquillianUIUtil.getActiveType (thrown in FeatureMapUtil$BasicFeatureEIterator.checkModCount)
Key: JBIDE-22284
URL: https://issues.jboss.org/browse/JBIDE-22284
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: arquillian
Affects Versions: 4.3.1.Final
Reporter: Automated Error Reporting Bot
The following problem was reported via the automated error reporting:
Message: HIDDEN
{noformat}
java.util.ConcurrentModificationException: null
at org.eclipse.emf.ecore.util.FeatureMapUtil$BasicFeatureEIterator.checkModCount(FeatureMapUtil.java:555)
at org.eclipse.emf.ecore.util.FeatureMapUtil$BasicFeatureEIterator.next(FeatureMapUtil.java:373)
at org.eclipse.jst.jee.model.internal.mergers.EjbJarMerger.mergeSessionBeans(EjbJarMerger.java:145)
at org.eclipse.jst.jee.model.internal.mergers.EjbJarMerger.process(EjbJarMerger.java:74)
at org.eclipse.jst.jee.model.internal.mergers.EjbJarMerger.process(EjbJarMerger.java:79)
at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.mergeWithModel(EJB3MergedModelProvider.java:214)
at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.merge(EJB3MergedModelProvider.java:204)
at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.internalModelChanged(EJB3MergedModelProvider.java:174)
at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.annotationModelChanged(EJB3MergedModelProvider.java:151)
at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider$AnnotationModelListener.modelsChanged(AbstractMergedModelProvider.java:83)
at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider$1.run(AbstractAnnotationModelProvider.java:189)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.notifyListeners(AbstractAnnotationModelProvider.java:184)
at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.notifyListeners(AbstractAnnotationModelProvider.java:157)
at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.internalPostReconcile(AbstractAnnotationModelProvider.java:467)
at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.elementChanged(AbstractAnnotationModelProvider.java:446)
at org.eclipse.jdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1662)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1652)
at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1504)
at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1463)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:770)
at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789)
at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1250)
at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1211)
at org.eclipse.jdt.internal.corext.util.JavaModelUtil.reconcile(JavaModelUtil.java:609)
at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:283)
at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:199)
at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:183)
at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getActiveType(ArquillianUIUtil.java:182)
at org.jboss.tools.arquillian.ui.internal.commands.ArquillianPropertyTester.test(ArquillianPropertyTester.java:62)
at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:100)
at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106)
at org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68)
at org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:22)
at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:199)
at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:75)
at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256)
at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166)
at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96)
at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188)
at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:199)
at org.eclipse.ui.internal.WorkbenchWindow$8.run(WorkbenchWindow.java:707)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
{noformat}
Bundles:
| org.eclipse.core.expressions | 3.5.0.v20150421-2214 | 3.5.0.v20150421-2214 |
| org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
| org.eclipse.e4.ui.workbench | 1.3.1.v20160203-0951 | 1.3.1.v20160203-0951 |
| org.eclipse.e4.ui.workbench.renderers.swt | 0.13.0.v20150901-1347 | 0.13.0.v20150901-1347 |
| org.eclipse.emf | 2.6.0.v20160208-0841 | 2.6.0.v20160208-0841 |
| org.eclipse.emf.ecore | 2.11.2.v20160208-0816 | 2.11.2.v20160208-0816 |
| org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.11.2.v20160212-1500 |
| org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 |
| org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 |
| org.eclipse.jst.jee | 1.0.700.v201404092004 | 1.0.700.v201404092004 |
| org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
| org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
| org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 |
Operating Systems:
| Windows | 10.0.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571f1795e4b08bd809...] for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3859:
--------------------------------
> Use SHA256sums to intelligently download latest CI builds into DP installer
> ---------------------------------------------------------------------------
>
> Key: JBDS-3859
> URL: https://issues.jboss.org/browse/JBDS-3859
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.0.0.Alpha1
>
>
> Per discussion with Denis today, we could:
> * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available
> * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one
> * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI
> * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps
> * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3859:
--------------------------------
> Use SHA256sums to intelligently download latest CI builds into DP installer
> ---------------------------------------------------------------------------
>
> Key: JBDS-3859
> URL: https://issues.jboss.org/browse/JBDS-3859
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.0.0.Alpha1
>
>
> Per discussion with Denis today, we could:
> * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available
> * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one
> * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI
> * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps
> * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-3859:
-----------------------------------
Assignee: Denis Golovin (was: Nick Boldt)
> Use SHA256sums to intelligently download latest CI builds into DP installer
> ---------------------------------------------------------------------------
>
> Key: JBDS-3859
> URL: https://issues.jboss.org/browse/JBDS-3859
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 10.0.0.Alpha1
>
>
> Per discussion with Denis today, we could:
> * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available
> * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one
> * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI
> * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps
> * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-3859.
---------------------------------
Resolution: Done
> Use SHA256sums to intelligently download latest CI builds into DP installer
> ---------------------------------------------------------------------------
>
> Key: JBDS-3859
> URL: https://issues.jboss.org/browse/JBDS-3859
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 10.0.0.Alpha1
>
>
> Per discussion with Denis today, we could:
> * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available
> * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one
> * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI
> * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps
> * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3859:
-----------------------------
> Use SHA256sums to intelligently download latest CI builds into DP installer
> ---------------------------------------------------------------------------
>
> Key: JBDS-3859
> URL: https://issues.jboss.org/browse/JBDS-3859
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.0.0.Alpha1
>
>
> Per discussion with Denis today, we could:
> * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available
> * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one
> * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI
> * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps
> * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3859:
--------------------------------
> Use SHA256sums to intelligently download latest CI builds into DP installer
> ---------------------------------------------------------------------------
>
> Key: JBDS-3859
> URL: https://issues.jboss.org/browse/JBDS-3859
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.0.0.Alpha1
>
>
> Per discussion with Denis today, we could:
> * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available
> * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one
> * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI
> * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps
> * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3859:
--------------------------------
> Use SHA256sums to intelligently download latest CI builds into DP installer
> ---------------------------------------------------------------------------
>
> Key: JBDS-3859
> URL: https://issues.jboss.org/browse/JBDS-3859
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.0.0.Alpha1
>
>
> Per discussion with Denis today, we could:
> * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available
> * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one
> * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI
> * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps
> * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months