[JBoss JIRA] (JBIDE-22999) Red Hat Central Rebranding
by James Cobb (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22999?page=com.atlassian.jira.plugi... ]
James Cobb updated JBIDE-22999:
-------------------------------
Attachment: jbosstools-central-webpage-2.0.0-revised.zip
> Red Hat Central Rebranding
> --------------------------
>
> Key: JBIDE-22999
> URL: https://issues.jboss.org/browse/JBIDE-22999
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Fix For: 4.4.x
>
> Attachments: central-rhd-icon.png, fullIDE.png, jbosstools-central-webpage-2.0.0-revised.zip, tools_rebrand.png, tools_rebrand_r1v2.png, tools_rebrand_r1v3.png, tools_rebrand_r2v1.png
>
>
> Quoting [~james.cobb], from JBIDE-22382
> {quote}
> I've pulled in the branding fro RHD into this IDE panel.
> 1. I've opted to use colors verses an grey monotones
> 2. I've used Red Hat icons from the icon set
> Thoughts?
> {quote}
> !tools_rebrand.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder when indexing some Camel artifacts
by Jane Murphey (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Jane Murphey updated JBIDE-23766:
---------------------------------
Attachment: devstudio10.0ISinstalledFTplugins.png
> ZipException in CDICoreBuilder when indexing some Camel artifacts
> -----------------------------------------------------------------
>
> Key: JBIDE-23766
> URL: https://issues.jboss.org/browse/JBIDE-23766
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.4.2.Final
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Fix For: 4.4.3.AM2
>
> Attachments: FT_FISprojectBldFail_011917.rtf, FT_blankBlueprintProj.log, FuseToolingInstalledSW.png, blankBlueprintPomError.png, devstudio10.0ISinstalledFTplugins.png, newFuseFISProjectCreateLog.hang, newFuseProjectCreateLog2.hang, settings.xml
>
>
> it would be nice to provide more information in log such as teh classes in inspection by CDI Core Builder
> {noformat}
> !ENTRY org.jboss.tools.common.core 4 0 2017-01-17 11:17:20.815
> !MESSAGE invalid LOC header (bad signature)
> !STACK 0
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(Native Method)
> at java.util.zip.ZipFile.access$1400(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419)
> at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at java.io.DataInputStream.readFully(DataInputStream.java:195)
> at java.io.DataInputStream.readFully(DataInputStream.java:169)
> at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:433)
> at org.jboss.jandex.Indexer.index(Indexer.java:689)
> at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56)
> at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder when indexing some Camel artifacts
by Jane Murphey (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Jane Murphey updated JBIDE-23766:
---------------------------------
Attachment: newFuseFISProjectCreateLog.hang
newFuseProjectCreateLog2.hang
> ZipException in CDICoreBuilder when indexing some Camel artifacts
> -----------------------------------------------------------------
>
> Key: JBIDE-23766
> URL: https://issues.jboss.org/browse/JBIDE-23766
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.4.2.Final
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Fix For: 4.4.3.AM2
>
> Attachments: FT_FISprojectBldFail_011917.rtf, FT_blankBlueprintProj.log, FuseToolingInstalledSW.png, blankBlueprintPomError.png, newFuseFISProjectCreateLog.hang, newFuseProjectCreateLog2.hang, settings.xml
>
>
> it would be nice to provide more information in log such as teh classes in inspection by CDI Core Builder
> {noformat}
> !ENTRY org.jboss.tools.common.core 4 0 2017-01-17 11:17:20.815
> !MESSAGE invalid LOC header (bad signature)
> !STACK 0
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(Native Method)
> at java.util.zip.ZipFile.access$1400(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419)
> at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at java.io.DataInputStream.readFully(DataInputStream.java:195)
> at java.io.DataInputStream.readFully(DataInputStream.java:169)
> at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:433)
> at org.jboss.jandex.Indexer.index(Indexer.java:689)
> at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56)
> at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder when indexing some Camel artifacts
by Jane Murphey (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Jane Murphey commented on JBIDE-23766:
--------------------------------------
[~aurelien.pupier] Project>clean did not work. After removing the .m2/repository and all its contents, tried several times to reopen JBDS, but it always hung. Tried to uninstall it with its uninstaller, but that failed too. Not sure how to uninstall it manually.
Started over: installed new instance of JBDS 10.2.0.GA; installed devstudio/10.0/IS (see attached graphic for plugin versions); enabled FT prefs>staging repos; installed and started up CDK Dev Env and OpenShift; Created a Fuse FIS project based on SprintBoot on OpenShift template. JBDS hung on "Waiting for workspace build to complete" on both attempts. See attached *.hang files (Console diagnostic logs)
> ZipException in CDICoreBuilder when indexing some Camel artifacts
> -----------------------------------------------------------------
>
> Key: JBIDE-23766
> URL: https://issues.jboss.org/browse/JBIDE-23766
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.4.2.Final
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Fix For: 4.4.3.AM2
>
> Attachments: FT_FISprojectBldFail_011917.rtf, FT_blankBlueprintProj.log, FuseToolingInstalledSW.png, blankBlueprintPomError.png, settings.xml
>
>
> it would be nice to provide more information in log such as teh classes in inspection by CDI Core Builder
> {noformat}
> !ENTRY org.jboss.tools.common.core 4 0 2017-01-17 11:17:20.815
> !MESSAGE invalid LOC header (bad signature)
> !STACK 0
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(Native Method)
> at java.util.zip.ZipFile.access$1400(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419)
> at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at java.io.DataInputStream.readFully(DataInputStream.java:195)
> at java.io.DataInputStream.readFully(DataInputStream.java:169)
> at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:433)
> at org.jboss.jandex.Indexer.index(Indexer.java:689)
> at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56)
> at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23709) Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23709?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23709:
-------------------------------------
Fix Version/s: 4.4.3.AM2
> Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23709
> URL: https://issues.jboss.org/browse/JBIDE-23709
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Fix For: 4.4.3.AM2
>
> Attachments: project-selected-no-scaling.png, service-selected-scaling-possible.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have at least 1 service & pod running in OpenShift
> # EXEC: in OpenShift Explorer: select the project that contains the service/pod
> # EXEC: in Properties view: select "Pod" tab and then your running pod (not the build pod, but the pod that's running your service). Open up the context menu
> Result:
> "Scale" with is child entries is missing from the context menu.
> !project-selected-no-scaling.png!
> While it's present if you have the service selected in the OpenShift Explorer.
> !service-selected-scaling-possible.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23708:
-------------------------------------
Fix Version/s: 4.4.3.AM2
> Pod Log: unable to get build log if build failed with error
> -----------------------------------------------------------
>
> Key: JBIDE-23708
> URL: https://issues.jboss.org/browse/JBIDE-23708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Labels: logs, properties
> Fix For: 4.4.3.AM2
>
> Attachments: cannot-get-logs-for-erroring-build.png, webconsole-logs-for-erroring-build.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a build that failed (ex. launch a nodejs build and shut down your vpn. The build will fail because it cannot connect to the registry)
> # EXEC: in Properties view: select "Builds" tab and choose your erroring build. Choose "Build Log..." in it's context menu
> Result:
> You're told that you cannot get the logs for an erroring build. You therefore cannot have insights on why your build failed:
> !cannot-get-logs-for-erroring-build.png!
> The webconsole allows you to inspect those logs:
> !webconsole-logs-for-erroring-build.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4238) CDK installer: should install into Application for MacOS
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4238?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4238:
--------------------------------
Fix Version/s: 10.3.0.AM2
> CDK installer: should install into Application for MacOS
> --------------------------------------------------------
>
> Key: JBDS-4238
> URL: https://issues.jboss.org/browse/JBDS-4238
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.2.0.AM1
> Environment: mac OS
> Reporter: Andre Dietisheim
> Assignee: Denis Golovin
> Fix For: 10.3.0.AM2
>
>
> the cdk installer for MacOS installs DevStudio and the CDK into <Home>/DevelopmentSuite.
> There are a few non-optimals here:
> * Home is afaik not visible by default in Finder.
> * Furthermore applications are by default installed into Applications in MacOS.
> Possible improvements:
> In order to behave like a first class MacOS-citizen we should install DevSuite and CDK independently into Applications (or maybe CDK into Document as it isnt the application in the strict sense, it's only a Virtualbox image, a Vagrantfile etc.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23761) ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23761?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23761 at 1/20/17 11:38 AM:
--------------------------------------------------------------
Rob's solution from 3 days ago was incomplete. Here are a couple more PRs to make it MORE complete:
https://github.com/jbosstools/jbosstools-server/pull/462 (merged already?)
https://github.com/jbosstools/jbosstools-server/pull/463 (to be merged)
https://github.com/jbosstools/jbosstools-server/pull/464 (not sure if this will help)
Basically the problem is that the jbosstools-server_master job is building the old x.y.2.v2016 versions of plugins into the update site it's creating, instead of the new x.y.3.v2017 versions:
{code}
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
{code}
instead of:
{code}
/home/nboldt/tru/jbosstools-server/site/target/repository/features/org.jboss.ide.eclipse.as.test.feature.source_3.2.3.v20170119-2212.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/features/org.jboss.ide.eclipse.as.test.feature_3.2.3.v20170119-2212.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.itests.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.itests_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.management.itests.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.management.itests_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.test.core.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.test.core_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.jmx.core.test.source_1.8.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.jmx.core.test_1.8.3.v20170119-2157.jar
{code}
was (Author: nickboldt):
Rob's solution from 3 days ago was incomplete. Here are a couple more PRs to make it MORE complete:
https://github.com/jbosstools/jbosstools-server/pull/462 (merged already?)
https://github.com/jbosstools/jbosstools-server/pull/463 (to be merged)
https://github.com/jbosstools/jbosstools-server/pull/464 (not sure if this will help)
Basically the problem is that the jbosstools-server_master job is building the old x.y.2.v2016 versions of plugins into the update site it's creating, instead of the new x.y.3.v2017 versions:
{code}
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
{code}
instead of:
{code}
/home/nboldt/tru/jbosstools-server/site/target/repository/features/org.jboss.ide.eclipse.as.test.feature_3.2.3.v20170119-2212.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/features/org.jboss.ide.eclipse.as.test.feature.source_3.2.3.v20170119-2212.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.itests_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.itests.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.management.itests_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.management.itests.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.test.core_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.test.core.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.jmx.core.test_1.8.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.jmx.core.test.source_1.8.3.v20170119-2157.jar
{code}
> ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23761
> URL: https://issues.jboss.org/browse/JBIDE-23761
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server, updatesite
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> [7:30 AM] Pavol Srna: @RobStryker hi Rob, got a minute?
> [7:31 AM] Pavol Srna: @RobStryker wondering if the (as, runtime) test-framework can be made available e.g. here: http://download.jboss.org/jbosstools/neon/snapshots/updates/coretests/mas...
> [7:31 AM] Pavol Srna: what do you think?
> [7:34 AM] Pavol Srna: I don't see it in the org.jboss.ide.eclipse.as.test.feature on site, maybe needs a rebuild?
> [12:49 PM] Nick Boldt: if you want more test plugins/features in the coretests site... make sure they're part of the server site [1] and then PR me to add them to the coretests site [2].
> [1] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
> [2] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> Submit PR against this:
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23761) ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23761?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23761 at 1/20/17 11:37 AM:
--------------------------------------------------------------
Rob's solution from 3 days ago was incomplete. Here are a couple more PRs to make it MORE complete:
https://github.com/jbosstools/jbosstools-server/pull/462 (merged already?)
https://github.com/jbosstools/jbosstools-server/pull/463 (to be merged)
https://github.com/jbosstools/jbosstools-server/pull/464 (not sure if this will help)
Basically the problem is that the jbosstools-server_master job is building the old x.y.2.v2016 versions of plugins into the update site it's creating, instead of the new x.y.3.v2017 versions:
{code}
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
{code}
instead of:
{code}
/home/nboldt/tru/jbosstools-server/site/target/repository/features/org.jboss.ide.eclipse.as.test.feature_3.2.3.v20170119-2212.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/features/org.jboss.ide.eclipse.as.test.feature.source_3.2.3.v20170119-2212.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.itests_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.itests.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.management.itests_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.management.itests.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.test.core_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.test.core.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.jmx.core.test_1.8.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.jmx.core.test.source_1.8.3.v20170119-2157.jar
{code}
was (Author: nickboldt):
Rob's solution from 3 days ago was incomplete. Here are a couple more PRs to make it MORE complete:
https://github.com/jbosstools/jbosstools-server/pull/462 (merged already?)
https://github.com/jbosstools/jbosstools-server/pull/463 (to be merged)
https://github.com/jbosstools/jbosstools-server/pull/464 (not sure if this will help)
Basically the problem is that the jbosstools-server_master job is building the old x.y.2.v2016 versions of plugins into the update site it's creating, instead of the new x.y.3.v2017 versions:
{code}
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
{code}
instead of:
{code}
/home/nboldt/tru/jbosstools-server/site/target/repository/features/org.jboss.ide.eclipse.as.test.feature_3.2.3.v20170119-2212.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/features/org.jboss.ide.eclipse.as.test.feature.source_3.2.3.v20170119-2212.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.itests_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.itests.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.management.itests_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.management.itests.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.test.core_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.test.core.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.jmx.core.test_1.8.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.jmx.core.test.source_1.8.3.v20170119-2157.jar
{code}
> ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23761
> URL: https://issues.jboss.org/browse/JBIDE-23761
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server, updatesite
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> [7:30 AM] Pavol Srna: @RobStryker hi Rob, got a minute?
> [7:31 AM] Pavol Srna: @RobStryker wondering if the (as, runtime) test-framework can be made available e.g. here: http://download.jboss.org/jbosstools/neon/snapshots/updates/coretests/mas...
> [7:31 AM] Pavol Srna: what do you think?
> [7:34 AM] Pavol Srna: I don't see it in the org.jboss.ide.eclipse.as.test.feature on site, maybe needs a rebuild?
> [12:49 PM] Nick Boldt: if you want more test plugins/features in the coretests site... make sure they're part of the server site [1] and then PR me to add them to the coretests site [2].
> [1] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
> [2] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> Submit PR against this:
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23761) ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23761?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23761 at 1/20/17 11:36 AM:
--------------------------------------------------------------
Rob's solution from 3 days ago was incomplete. Here are a couple more PRs to make it MORE complete:
https://github.com/jbosstools/jbosstools-server/pull/462 (merged already?)
https://github.com/jbosstools/jbosstools-server/pull/463 (to be merged)
https://github.com/jbosstools/jbosstools-server/pull/464 (not sure if this will help)
Basically the problem is that the jbosstools-server_master job is building the old x.y.2.v2016 versions of plugins into the update site it's creating, instead of the new x.y.3.v2017 versions:
{code}
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
{code}
instead of:
{code}
/home/nboldt/tru/jbosstools-server/site/target/repository/features/org.jboss.ide.eclipse.as.test.feature_3.2.3.v20170119-2212.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/features/org.jboss.ide.eclipse.as.test.feature.source_3.2.3.v20170119-2212.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.itests_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.itests.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.management.itests_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.management.itests.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.test.core_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.as.test.core.source_3.2.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.jmx.core.test_1.8.3.v20170119-2157.jar
/home/nboldt/tru/jbosstools-server/site/target/repository/plugins/org.jboss.tools.jmx.core.test.source_1.8.3.v20170119-2157.jar
{code}
was (Author: nickboldt):
Rob's solution from 3 days ago was incomplete. Here are a couple more PRs to make it MORE complete:
https://github.com/jbosstools/jbosstools-server/pull/462 (merged already?)
https://github.com/jbosstools/jbosstools-server/pull/463 (to be merged)
> ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23761
> URL: https://issues.jboss.org/browse/JBIDE-23761
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server, updatesite
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> [7:30 AM] Pavol Srna: @RobStryker hi Rob, got a minute?
> [7:31 AM] Pavol Srna: @RobStryker wondering if the (as, runtime) test-framework can be made available e.g. here: http://download.jboss.org/jbosstools/neon/snapshots/updates/coretests/mas...
> [7:31 AM] Pavol Srna: what do you think?
> [7:34 AM] Pavol Srna: I don't see it in the org.jboss.ide.eclipse.as.test.feature on site, maybe needs a rebuild?
> [12:49 PM] Nick Boldt: if you want more test plugins/features in the coretests site... make sure they're part of the server site [1] and then PR me to add them to the coretests site [2].
> [1] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
> [2] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> Submit PR against this:
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months