[jbosstools-issues] [JBoss JIRA] (JBDS-2137) provide staging site for devstudio-directory.xml file; update rel guide docs to point to new URL
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Mon May 14 13:30:17 EDT 2012
[ https://issues.jboss.org/browse/JBDS-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12692745#comment-12692745 ]
Nick Boldt edited comment on JBDS-2137 at 5/14/12 1:30 PM:
-----------------------------------------------------------
Fixed:
{code:title=https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml}
<?xml version='1.0' encoding='UTF-8'?>
<directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/">
<!-- include JBDS Core Central discovery plugin -->
<entry url="staging/discovery/com.jboss.jbds.central.discovery_1.0.0.v20120328-1758-H123-Beta2.jar" permitCategories="true"/>
<!-- include JBDS SOA Central discovery plugin too -->
<!-- <entry url="staging/discovery/com.jboss.jbds.central.discovery.soa-tooling_1.0.0.v20120501-0347-H6-Beta1-SOA.jar" permitCategories="true"/> -->
</directory>
{code}
{code:title=https://devstudio.jboss.com/updates/5.0/staging/devstudio-directory.xml}
<?xml version='1.0' encoding='UTF-8'?>
<directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/">
<!-- include JBDS Core Central discovery plugin -->
<entry url="discovery/com.jboss.jbds.central.discovery_1.0.0.v20120510-2156-H157-Beta3.jar" permitCategories="true"/>
<!-- include JBDS SOA Central discovery plugin too -->
<entry url="discovery/com.jboss.jbds.central.discovery.soa-tooling_1.0.0.v20120501-0347-H6-Beta1-SOA.jar" permitCategories="true"/>
</directory>
{code}
Docs updated:
https://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/
Will close this after I verify my doc/scriptlet stuff works... after we push Beta3b to QE, then to EA.
was (Author: nickboldt):
Fixed:
{code:title=https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml}
<?xml version='1.0' encoding='UTF-8'?>
<directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/">
<!-- include JBDS Core Central discovery plugin -->
<entry url="staging/discovery/com.jboss.jbds.central.discovery_1.0.0.v20120328-1758-H123-Beta2.jar" permitCategories="true"/>
<!-- include JBDS SOA Central discovery plugin too -->
<!-- <entry url="staging/discovery/com.jboss.jbds.central.discovery.soa-tooling_1.0.0.v20120501-0347-H6-Beta1-SOA.jar" permitCategories="true"/> -->
</directory>
{code}
{code:title=https://devstudio.jboss.com/updates/5.0/staging/devstudio-directory.xml}
<?xml version='1.0' encoding='UTF-8'?>
<directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/">
<!-- include JBDS Core Central discovery plugin -->
<entry url="discovery/com.jboss.jbds.central.discovery_1.0.0.v20120510-2156-H157-Beta3.jar" permitCategories="true"/>
<!-- include JBDS SOA Central discovery plugin too -->
<entry url="discovery/com.jboss.jbds.central.discovery.soa-tooling_1.0.0.v20120501-0347-H6-Beta1-SOA.jar" permitCategories="true"/>
</directory>
{code}
Docs updated:
https://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/
> provide staging site for devstudio-directory.xml file; update rel guide docs to point to new URL
> -------------------------------------------------------------------------------------------------
>
> Key: JBDS-2137
> URL: https://issues.jboss.org/browse/JBDS-2137
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central, updatesite
> Affects Versions: 5.0.0.Beta2, 5.0.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 5.0.0.Beta3
>
>
> I should have pushed these bits to a DIFFERENT directory.xml file. Will fix that so that public == QE'd and EA released, whereas there's a different URL which QE can use with the -D flag to test (without having to jump through complex hoops.
> On 05/11/2012 12:51 PM, Max Andersen wrote:
> > Yes but nothing should be out on EA before QE and team gives green light. That's my problem here.
> >
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list