[JBoss JIRA] (TOOLSDOC-390) Update book versions for 7.1/4.2
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-390?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-390:
------------------------------------------
PR for core books was fine as only book with JBT labelling was User Guide, which previously hadn't updated. So simply make a clone of 4.1.x as 4.1.0 to keep 7.0.0 docs available for updating at future date. Then will use 4.1.x as expected and build 4.1.1/7.1.0 in it. So cherry-picked orig core PR from master and applied to 4.1.x. Ready to go!
Now left to resolve plug-in PRs.
> Update book versions for 7.1/4.2
> --------------------------------
>
> Key: TOOLSDOC-390
> URL: https://issues.jboss.org/browse/TOOLSDOC-390
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: General documentation issues
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
>
> Update Book_Info.xml & Revision History with 7.1.
> Update pom.xml with 4.2.0
> Also incorporate TOOLSDOC-313 (moving doc version out of master.xml and into pom.xml).
--
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, 9 months
[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on JBDS-2734:
------------------------------------------
[~fbricon] Really I think this would be better solved by making sure that the Forge Tools plugin can install without M2E. I'm not sure (as igor says) that adding an event would really be the best thing to do here, since that would still be progamming to the API of m2e, just without using the API. Thoughts?
> Forge 2 in JBDS
> ---------------
>
> Key: JBDS-2734
> URL: https://issues.jboss.org/browse/JBDS-2734
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: forge, requirements
> Reporter: Burr Sutter
>
> Is Forge 2 ready to be included in JBDS ?
--
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, 9 months
[JBoss JIRA] (JBIDE-15435) "installed plugins" detection seems fishy in project examples / central
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15435?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-15435:
---------------------------------------
{quote}
So Project fixes check for the presence of only one plugin/bundle id : https://github.com/jbosstools/jbosstools-central/blob/master/examples/plu...
{quote}
The plugin fix will check all the plugins you defined in a project example xml. The GWT project example declares only one plugin, but you can add as much fixes as you want.
{quote}
I think the problem is that there is some broken or non-understood semantics in how the examples define and test the existence of the required plugins.
{quote}
The plugin fix checks a plugin(s). A connector can check some IU (plugins or features). In this case connector checks features.
{quote}
Why is both plugin and connector id necessary ? shouldn't connector id be sufficient ?
{quote}
When we added the plugin fix, we didn't have either connector or central.
{quote}
Right now connector id seem to only be used when deciding what to install.
{quote}
Correct.
{quote}
how does a project example list multiple plugins ?
{quote}
You can declare plugin fixes in a project xml file as much as you want.
{quote}
and can they use features instead so they don't break if plugins gets added/remvoed ?
{quote}
They can't now, but that can be added.
Currently, Project Examples and the Software/Update page aren't compatible.
If you think that Project Examples and the Software/Update page should be compatible, we have to add a connectorId or feature (IU) fix.
> "installed plugins" detection seems fishy in project examples / central
> -----------------------------------------------------------------------
>
> Key: JBIDE-15435
> URL: https://issues.jboss.org/browse/JBIDE-15435
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, discovery, project-examples
> Affects Versions: 4.1.0.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.1.Alpha2
>
>
> Following JBDS-2753, [~maxandersen] says he installed the JBoss GWT connector, which dragged the GPE plugins.
> Some functionality seem missing according to Max (which ones?). In the JBoss Central 'software updates' page, the GWT/GPE connector is shown as missing. In the GWT example wizard, the feature appears as installed. One of the 2 is wrong, obviously.
--
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, 9 months
[JBoss JIRA] (JBDS-2701) Runtime detection problems with Portlet helloworld example in Central (wolf repo issue)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2701?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-2701.
-------------------------------
Won't fix. Closing.
And the scenario with broken recognition of JPP runtime has been verified as fixed in JBDS-2703
> Runtime detection problems with Portlet helloworld example in Central (wolf repo issue)
> ---------------------------------------------------------------------------------------
>
> Key: JBDS-2701
> URL: https://issues.jboss.org/browse/JBDS-2701
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central, servers
> Affects Versions: 7.0.0.GA
> Environment: jbdevstudio-product-universal-7.0.0.GA-v20130717-1700-B362
> RHEL6
> Reporter: Len DiMaggio
> Assignee: Peter Palaga
> Fix For: 7.0.0.GA
>
> Attachments: Screenshot-2.png, Screenshot-3.png
>
>
> Installing the helloworld portal quickstart raises these runtime detection errors:
> * The quickstart runtime detection looks for JBoss AS, does not recognize EAP 6
> * But - it does not look for/require a portal server
--
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, 9 months