[JBoss JIRA] (JBDS-4624) All properties for Devstudio 11.1.0.GA / JBT 4.5.1.Final are commented out in ide-config.properties
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4624?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-4624.
----------------------------
Resolution: Rejected
> All properties for Devstudio 11.1.0.GA / JBT 4.5.1.Final are commented out in ide-config.properties
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-4624
> URL: https://issues.jboss.org/browse/JBDS-4624
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 11.1.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 11.1.0.GA
>
>
> All properties for Devstudio 11.1.0.GA / JBT 4.5.1.Final are commented out in ide-config.properties at
> http://download.jboss.org/jbosstools/configuration/ide-config.properties
> {code}
> ### milestone staging
> # 4.5.oxygen version of jbosstools-earlyaccess.properties should be edited here, so the discovery job can fetch it: http://download.jboss.org/jbosstools/oxygen/snapshots/updates/earlyaccess...
> #jboss.discovery.directory.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/staging/updates/discovery.earlyaccess/4.5.1.Final/jbosstools-directory.xml
> #jboss.discovery.site.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/staging/updates/
> #jboss.discovery.earlyaccess.site.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/staging/updates/discovery.earlyaccess/4.5.1.Final/
> #jboss.discovery.earlyaccess.list.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/staging/updates/discovery.earlyaccess/4.5.1.Final/jbosstools-earlyaccess.properties
> #jboss.central.webpage.url|jbosstools|4.5.1.Final=https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=public-jboss&g=org.jboss.tools.central&a=jbosstools-central-webpage&v=2.0.0-SNAPSHOT&e=zip&mustEndWith=.zip
> #jboss.discovery.site.integration-stack.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/development/updates/integration-stack/discovery/
> #jboss.discovery.earlyaccess.site.integration-stack.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/development/updates/integration-stack/discovery/earlyaccess/
> #jboss.fuse.extras.site.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/staging/updates/fuse-extras/4.5.1.Final/
> # 4.5.oxygen version of devstudio-earlyaccess.properties should be edited here, so the discovery job can fetch it: https://devstudio.redhat.com/11/snapshots/updates/earlyaccess.properties/...
> #jboss.discovery.directory.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/staging/updates/discovery.earlyaccess/11.1.0.GA/devstudio-directory.xml
> #jboss.discovery.site.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/staging/updates/
> #jboss.discovery.earlyaccess.site.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/staging/updates/discovery.earlyaccess/11.1.0.GA/
> #jboss.discovery.earlyaccess.list.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/staging/updates/discovery.earlyaccess/11.1.0.GA/devstudio-earlyaccess.properties
> #jboss.central.webpage.url|devstudio|11.1.0.GA=https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=public-jboss&g=org.jboss.tools.central&a=jbosstools-central-webpage&v=2.0.0-SNAPSHOT&e=zip&mustEndWith=.zip
> #jboss.discovery.site.integration-stack.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/development/updates/integration-stack/discovery/
> #jboss.discovery.earlyaccess.site.integration-stack.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/development/updates/integration-stack/discovery/earlyaccess/
> #jboss.fuse.extras.site.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/staging/updates/fuse-extras/11.1.0.GA/
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25398) [Regression]Camel/Fuse keywords are missing for Jboss Tools Marketplace
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25398?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-25398:
-----------------------------------------
thanks for the fast fix!
{quote}Need more flags added? Just ask. Want to add them yourself? Give me your eclipse login id, and I'll add you to the list of admins for the Marketplace listings.{quote}
I don't have others in mind right now but if I have admin rights on the Marketplace listings it will avoid to bother you when one will come :-)
I'll send them privately.
> [Regression]Camel/Fuse keywords are missing for Jboss Tools Marketplace
> -----------------------------------------------------------------------
>
> Key: JBIDE-25398
> URL: https://issues.jboss.org/browse/JBIDE-25398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.5.1.Final
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Fix For: 4.5.1.Final
>
> Attachments: image-2017-11-16-10-00-03-122.png
>
>
> !image-2017-11-16-10-00-03-122.png|thumbnail!
> proposal of keywords to add:
> camel, apache camel, fuse, esb, fuse tooling
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13407:
------------------------------------
Nope. Infrastructure challenges prevent this from happening in the process I'd wanted to implement (similar to the process at Eclipse.org: pass a CI build's output to a signing server, wait until signed, then retrieve the signed bits & collect them into the downstream aggregates/products).
We could do potentially do a one-off manual build and sign that (rather than the above CI process) but that's manual-heavy and not very reproduceable. So I'd prefer to avoid a manual step.
If this is something that you feel is important / urgent to be solved before the end of the Oxygen stream, let me know and I can attempt to escalate to ops to see what we could do to implement this.
> Jar signing for JBT plugins/features
> ------------------------------------
>
> Key: JBIDE-13407
> URL: https://issues.jboss.org/browse/JBIDE-13407
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, updatesite
> Affects Versions: 3.3.2.Final, 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: LATER
>
> Attachments: JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, dialog_do-you-trust-these-certs.png, jbds-signed-plugins.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.png
>
>
> Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product.
> Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss Central.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months