[jbosstools-issues] [JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available
Nick Boldt (JIRA)
issues at jboss.org
Thu Oct 8 22:58:00 EDT 2015
[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116699#comment-13116699 ]
Nick Boldt commented on JBTIS-504:
----------------------------------
BTW, I see only some projects have moved to the new license terms. Looks a bit strange when you're installing everything and have to accept two slightly different licenses.
See: https://issues.jboss.org/browse/JBTIS-487?focusedCommentId=13116697&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13116697
> publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available
> -----------------------------------------------------------------------------------
>
> Key: JBTIS-504
> URL: https://issues.jboss.org/browse/JBTIS-504
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Fix For: 4.3.0.Alpha2
>
> Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, ea-in-non-ea.png, is-in-dev.png, is-in-dev_JBDS.png, JBDSIS-preview1.png, JBDSIS-preview2-EA.png, jbtis-disc-ea.png, jbtis-disc.png, JBTIS-preview1.png, JBTIS-preview2-EA.png
>
>
> Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list