[JBoss JIRA] (JBDS-3589) no composite*.xml files in root of JBDS installer
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3589?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3589:
-----------------------------
Description:
JBDS installer no longer includes composite*.xml in its root folder, so the jar won't work as an offline update site (eg., for an offline install of JBDS IS into Eclipse)
{code}
org.eclipse.equinox.p2.core.ProvisionException: No repository found at jar:file:/home/nboldt/tmp/JBDS_Installers/jboss-devstudio-9.1.0.Beta2-v20160127-2213-B262-installer-standalone.jar!/.
{code}
Workaround:
use jar:file:/home/nboldt/tmp/JBDS_Installers/jboss-devstudio-9.1.0.Beta2-v20160127-2213-B262-installer-standalone.jar!/jbds/ as the update site path
was:JBDS installer no longer includes composite*.xml in its root folder, so the jar won't work as an offline update site (eg., for an offline install of JBDS IS into Eclipse)
> no composite*.xml files in root of JBDS installer
> -------------------------------------------------
>
> Key: JBDS-3589
> URL: https://issues.jboss.org/browse/JBDS-3589
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> JBDS installer no longer includes composite*.xml in its root folder, so the jar won't work as an offline update site (eg., for an offline install of JBDS IS into Eclipse)
> {code}
> org.eclipse.equinox.p2.core.ProvisionException: No repository found at jar:file:/home/nboldt/tmp/JBDS_Installers/jboss-devstudio-9.1.0.Beta2-v20160127-2213-B262-installer-standalone.jar!/.
> {code}
> Workaround:
> use jar:file:/home/nboldt/tmp/JBDS_Installers/jboss-devstudio-9.1.0.Beta2-v20160127-2213-B262-installer-standalone.jar!/jbds/ as the update site path
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBDS-3589) no composite*.xml files in root of JBDS installer
by Nick Boldt (JIRA)
Nick Boldt created JBDS-3589:
--------------------------------
Summary: no composite*.xml files in root of JBDS installer
Key: JBDS-3589
URL: https://issues.jboss.org/browse/JBDS-3589
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
JBDS installer no longer includes composite*.xml in its root folder, so the jar won't work as an offline update site (eg., for an offline install of JBDS IS into Eclipse)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21635) add missing m2e mapping; fix dryrun; tweak logging
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21635?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21635:
-------------------------------
Description:
realized while using bzira that it's silently failing in jenkins and NOT reporting mapping errors.
So, I've adjusted the job to throw an error when a console log includes ERROR in it:
> add missing m2e mapping; fix dryrun; tweak logging
> --------------------------------------------------
>
> Key: JBIDE-21635
> URL: https://issues.jboss.org/browse/JBIDE-21635
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.3.1.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: bzira-fail.png
>
>
> realized while using bzira that it's silently failing in jenkins and NOT reporting mapping errors.
> So, I've adjusted the job to throw an error when a console log includes ERROR in it:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21635) add missing m2e mapping; fix dryrun; tweak logging
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21635?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21635:
-------------------------------
Description:
realized while using bzira that it's silently failing in jenkins and NOT reporting mapping errors.
So, I've adjusted the job to throw an error when a console log includes ERROR in it:
!bzira-fail.png!
But now we need to actually add a mapping for m2e 1.7 -> neon.
was:
realized while using bzira that it's silently failing in jenkins and NOT reporting mapping errors.
So, I've adjusted the job to throw an error when a console log includes ERROR in it:
> add missing m2e mapping; fix dryrun; tweak logging
> --------------------------------------------------
>
> Key: JBIDE-21635
> URL: https://issues.jboss.org/browse/JBIDE-21635
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.3.1.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: bzira-fail.png
>
>
> realized while using bzira that it's silently failing in jenkins and NOT reporting mapping errors.
> So, I've adjusted the job to throw an error when a console log includes ERROR in it:
> !bzira-fail.png!
> But now we need to actually add a mapping for m2e 1.7 -> neon.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21634) Allow a user to scale their deployment
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-21634:
-------------------------------------
Summary: Allow a user to scale their deployment
Key: JBIDE-21634
URL: https://issues.jboss.org/browse/JBIDE-21634
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Jeff Cantrill
The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of:
1. deployment (replication controller)
2. eclipse view of a deployment (server) -> walk back to the currrent deployment
3. pod -> walk back to the current deployment
updating 'spec.replicas' causes a new pods to spin up
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months