[JBoss JIRA] (TOOLSDOC-313) Copyrights and versions stated in documents do not align with the release version of the doc & the JBT release version
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-313?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-313:
-------------------------------------
Assignee: Michelle Murray (was: Nick Boldt)
> Copyrights and versions stated in documents do not align with the release version of the doc & the JBT release version
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-313
> URL: https://issues.jboss.org/browse/TOOLSDOC-313
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: General documentation issues
> Affects Versions: 4.0.1, 4.1.0
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
>
> Some places where docs' copyright dates and stated versions do not align with the version of the doc:
> {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/GettingStartedGuide/html/index.html}
> Version: 4.0.0
> Copyright © 2012 JBoss by Red Hat
> {code}
> {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/beginners_guide/html/index.html}
> Version: 3.3.0.M5
> Copyright © 2011 JBoss by Red Hat
> {code}
> {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/as/html/index.html}
> Version: 3.3.0.M5
> Copyright © 2007, 2008, 2009, 2010 JBoss by Red Hat
> {code}
> {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/jmx_ref_guide/html/index.html}
> Copyright © 2007, 2008, 2009, 2010, 2011 JBoss by Red Hat
> {code}
> And yes, this is still a problem in trunk:
> {code:title=http://docs.jboss.org/tools/nightly/trunk/en/beginners_guide/html/index.html}
> Version: 3.3.0.M5
> Copyright © 2011 JBoss by Red Hat
> {code}
> {code:title=http://docs.jboss.org/tools/nightly/trunk/en/forge_reference/html/index.html}
> Version: 3.3.1
> Copyright © 2012 JBoss by Red Hat
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-2507) Migration to org.eclipse.ui.menus where it is possible
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2507?page=com.atlassian.jira.plugin... ]
Daniel Azarov updated JBIDE-2507:
---------------------------------
Description:
Migrate form extension points listed below to org.eclipse.ui.menus where it is possible:
* org.eclipse.ui.ActionSets:
* org.eclipse.ui.EditorActions
* org.eclipse.ui.popupMenus (including 'objectContributions')
* org.eclipse.ui.viewActions
Create specific issues as subtask in this issue
[Migration Guide|http://pa-blogger.blogspot.com/2008/07/orgeclipseuimenus.html]
was:
Migrate form extension points listed below to org.eclipse.ui.menus where it is possible:
* org.eclipse.ui.ActionSets:
* org.eclipse.ui.EditorActions
* org.eclipse.ui.popupMenus (including 'objectContributions')
* org.eclipse.ui.viewActions
Create specific issues as subtask in this issue
> Migration to org.eclipse.ui.menus where it is possible
> ------------------------------------------------------
>
> Key: JBIDE-2507
> URL: https://issues.jboss.org/browse/JBIDE-2507
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cleanup
> Affects Versions: 3.0.0.alpha
> Reporter: Denis Golovin
> Assignee: Daniel Azarov
> Fix For: 4.2.x
>
>
> Migrate form extension points listed below to org.eclipse.ui.menus where it is possible:
> * org.eclipse.ui.ActionSets:
> * org.eclipse.ui.EditorActions
> * org.eclipse.ui.popupMenus (including 'objectContributions')
> * org.eclipse.ui.viewActions
> Create specific issues as subtask in this issue
> [Migration Guide|http://pa-blogger.blogspot.com/2008/07/orgeclipseuimenus.html]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBTIS-145) bad label / description on generated update site's index.html page
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-145?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-145 at 8/21/13 6:11 PM:
-----------------------------------------------------------
Ah, but you see, this isn't JBoss Tools content. It's JBoss Tools Integration Stack content, and those projects tend to roll their own, releasing on their own and providing their own header graphic.
http://download.jboss.org/jbosstools/updates/stable/juno/integration-stac...
http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
http://download.jboss.org/drools/release/6.0.0.Beta5/droolsjbpm-tools-dis...
OTOH, projects like ESB, BPEL, and jBPM3 are just using the default JBT header, because they're not moving forward as quickly.
was (Author: nickboldt):
Ah, but you see, this isn't JBoss Tools content. It's JBoss Tools Integration Stack content, and those projects tend to roll their own, releasing on their own and providing their own header graphic.
http://download.jboss.org/jbosstools/updates/stable/juno/integration-stac...
http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
http://download.jboss.org/drools/release/6.0.0.Beta5/droolsjbpm-tools-dis...
OTOH, projects like ESB, BPEL, and jBPM3 are just using the default JBT header.
> bad label / description on generated update site's index.html page
> ------------------------------------------------------------------
>
> Key: JBTIS-145
> URL: https://issues.jboss.org/browse/JBTIS-145
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Fuse IDE
> Affects Versions: 4.1.2
> Reporter: Nick Boldt
> Assignee: Lars Heinemann
>
> The description/label for your update site [1] says:
> "This is the http://fuse.fusesource.org/org.fusesource.ide.updatesite/ Update Site for Fuse :: Update Site. "
> [1] http://download.jboss.org/jbosstools/updates/development/kepler/integrati...
> I'll attach a PR for your site/pom.xml which should fix this, as well as some other enhancements to the way the html is generated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBTIS-145) bad label / description on generated update site's index.html page
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-145?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-145:
----------------------------------
Ah, but you see, this isn't JBoss Tools content. It's JBoss Tools Integration Stack content, and those projects tend to roll their own, releasing on their own and providing their own header graphic.
http://download.jboss.org/jbosstools/updates/stable/juno/integration-stac...
http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
http://download.jboss.org/drools/release/6.0.0.Beta5/droolsjbpm-tools-dis...
OTOH, projects like ESB, BPEL, and jBPM3 are just using the default JBT header.
> bad label / description on generated update site's index.html page
> ------------------------------------------------------------------
>
> Key: JBTIS-145
> URL: https://issues.jboss.org/browse/JBTIS-145
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Fuse IDE
> Affects Versions: 4.1.2
> Reporter: Nick Boldt
> Assignee: Lars Heinemann
>
> The description/label for your update site [1] says:
> "This is the http://fuse.fusesource.org/org.fusesource.ide.updatesite/ Update Site for Fuse :: Update Site. "
> [1] http://download.jboss.org/jbosstools/updates/development/kepler/integrati...
> I'll attach a PR for your site/pom.xml which should fix this, as well as some other enhancements to the way the html is generated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months