[JBoss JIRA] (JBIDE-16651) Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding RedHat techpreview repo
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-16651:
-----------------------------------
Summary: Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding RedHat techpreview repo
Key: JBIDE-16651
URL: https://issues.jboss.org/browse/JBIDE-16651
Project: Tools (JBoss Tools)
Issue Type: Task
Components: maven, project-examples
Affects Versions: 4.1.1.Final
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 4.1.2.CR1
In JBoss Central, when an Enterprise runtime is selected for any given Archetype, we check if the Red Hat Enterprise repository is available by trying to resolve a redhat version of org.jboss.spec:jboss-javaee-web-6.0. Then, if some essential dependencies are defined in stacks.yaml, we also try to resolve these. If the dependencies can't be resolved, a warning message appears with a link allowing users to add the RH repo to their Maven settings.xml
Upcoming archetypes will have the Red Hat repository already added to the generated pom.xml, so adding it to settings.xml becomes unnecessary. However, we'd get false positive warning by trying to resolve org.jboss.spec:jboss-javaee-web-6.0 from the settings.xml *before* generating the archetype.
Our goal is to remove the hardcoded check from MavenArtifactHelper and, when necessary, declare org.jboss.spec:jboss-javaee-web-6.0 as an essential dependency in stacks.yaml for *old* archetypes, not declaring the RH repo in the gen'd 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, 1 month
[JBoss JIRA] (JBIDE-15162) User must install and reference an installed local EAP instance to create a remote server definition
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15162?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-15162:
----------------------------------
Assignee: Rob Stryker (was: Martin Malina)
> User must install and reference an installed local EAP instance to create a remote server definition
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15162
> URL: https://issues.jboss.org/browse/JBIDE-15162
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.Beta1
>
> Attachments: Van_1.png, Van_2.png, Van_3.png
>
>
> See the attached screenshots - it seems counter-intuitive for a user to have to reference an installed local EAP instance to too create a remote server definition
> - open the "Servers" tab (where servers are stopped/started)
> - click in the area
> - now right mouse click and select "New->Server"
> - select JBoss Middleware EAP 6.1, click next
> - this next panel requires you to enter a directory to a local EAP install
--
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, 1 month
[JBoss JIRA] (JBIDE-15162) User must install and reference an installed local EAP instance to create a remote server definition
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15162?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-15162:
---------------------------------------
Hey [~rob.stryker] I installed the latest nightly (date 20140225) to try this.
First issue: Even if I choose not to have a runtime associated with a remote server, I am still taken to the runtime setup screen. Something's wrong.
Steps:
1. Server view -> New Server
2. Select EAP 6.1+, a name and hostname, press Next
3. (second page of dialog) select rse profile and uncheck "Assign a runtime...", press Next
4. (third page of dialog) you're now at the JBoss Runtime setup page - but I don't want a runtime
> User must install and reference an installed local EAP instance to create a remote server definition
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15162
> URL: https://issues.jboss.org/browse/JBIDE-15162
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Martin Malina
> Priority: Blocker
> Fix For: 4.2.0.Beta1
>
> Attachments: Van_1.png, Van_2.png, Van_3.png
>
>
> See the attached screenshots - it seems counter-intuitive for a user to have to reference an installed local EAP instance to too create a remote server definition
> - open the "Servers" tab (where servers are stopped/started)
> - click in the area
> - now right mouse click and select "New->Server"
> - select JBoss Middleware EAP 6.1, click next
> - this next panel requires you to enter a directory to a local EAP install
--
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, 1 month
[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ]
Denis Golovin updated JBIDE-2032:
---------------------------------
Summary: Help button works not in all wizards (was: Help button works not in all wizards.)
> Help button works not in all wizards
> ------------------------------------
>
> Key: JBIDE-2032
> URL: https://issues.jboss.org/browse/JBIDE-2032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: help
> Affects Versions: 2.1.0.beta1
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG, Resource - Eclipse Platform _028.png
>
>
> Wizards with non-working help button attached.
--
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, 1 month
[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ]
Denis Golovin edited comment on JBIDE-2032 at 2/24/14 8:30 PM:
---------------------------------------------------------------
It looks like we can finally get decent help for all JBossTools/JBDS related features. It could be done by installing documentation features from p2 repo or by connecting local help information center to remote one:
1. We should deploy remote Information Center with JBT/JBDS documentation in eclipse format. Information center can be deployed as war application
2. Documentation feature(s) could be built out of current documentation (need to create features and plug-ins that would aggregate doc artifacts like topic.xml, css and html pages)
3 Every JBoss Tools UI Element like: New Wizard, Editor, Dialog, View should have set help context through call
{code}PlatformUI.getWorkbench().getHelpSystem().setHelp(container, "plugin.id.<uielementname>_<name>");{code}
where:
* <uielementname> could be one of: newwizard, dialog, editor, view and e.t.c
* <name> is readable feature name
For example for new JSF Project Wizard it would be "org.jboss.tools.jsf.ui.newwizard_jsfproject
If no context help requires then default context id should be used for example "org.jboss.tools.foundation.help.default"
4. org.jboss.tools.foundation.help registers so called Global Help Context Provider which process requested help context if itis not found by other context providers:
* RemoteContextProvider (loads context from remote Info Center server(s) registered in preferences Help->Content)
* FileContextProvider (load conext help form xml files defined through org.eclipse.help.base.contexts extension point, which is usually done in documentation bundles)
So if doc plugins (which usually defines context help) are not installed or not available from remote info center then control gets int global provider and it generates default page for context help with:
* short description
* link to external site
* command to call documentation feature installation out of JBoss Central
* command to register remote info center with JBoss Tools documentation
Default context help by default is generated for JBoss Tools, but could be overriden in JBDS or other JBoss Tools Based product.
Tested this approach on local build with local info center and it works as expected.
was (Author: dgolovin):
It looks like we can finally get decent help for all JBossTools/JBDS related features. It could be done by installing documentation features from p2 repo or by connecting local help information center to remote one:
1. We should deploy remote Information Center with JBT/JBDS documentation in eclipse format (I hope it cold be generated out of current documentation).
2. Every JBoss Tools UI Element like: New Wizard, Editor, Dialog, View should have set help context through call
{code}PlatformUI.getWorkbench().getHelpSystem().setHelp(container, "plugin.id.<uielementname>_<name>");{code}
where:
* <uielementname> could be one of: newwizard, dialog, editor, view and e.t.c
* <name> is readable feature name
For example for new JSF Project Wizard it would be "org.jboss.tools.jsf.ui.newwizard_jsfproject
If no context help requires then default context id should be used for example "org.jboss.tools.foundation.help.default"
3. org.jboss.tools.foundation.help registers so called Global Help Context Provider which process requested help context if itis not found by other context providers:
* RemoteContextProvider (loads context from remote Info Center server(s) registered in preferences Help->Content)
* FileContextProvider (load conext help form xml files defined through org.eclipse.help.bas.contexts extension point, which is usually done in documentation bundles)
So if doc plugins (which usually defines context help) are not installed or not available from remote info center then control gets int global provider and it generates default page for context help with:
* short description
* link to external site
* command to call documentation feature installation out of JBoss Central
* command to register remote info center with JBoss Tools documentation
Default context help by default is generated for JBoss Tools, but could be overriden in JBDS or other JBoss Tools Based product.
Tested this approach on local build with local info center and it works as expected.
> Help button works not in all wizards.
> -------------------------------------
>
> Key: JBIDE-2032
> URL: https://issues.jboss.org/browse/JBIDE-2032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: help
> Affects Versions: 2.1.0.beta1
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG, Resource - Eclipse Platform _028.png
>
>
> Wizards with non-working help button attached.
--
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, 1 month
[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ]
Denis Golovin edited comment on JBIDE-2032 at 2/24/14 8:31 PM:
---------------------------------------------------------------
It looks like we can finally get decent help for all JBossTools/JBDS related features. It could be done by installing documentation features from p2 repo or by connecting local help information center to remote one:
1. We should deploy remote Information Center with JBT/JBDS documentation in eclipse format. Information center can be deployed as war application
2. Documentation feature(s) could be built out of current documentation (need to create features and plug-ins that would aggregate doc artifacts like topic.xml, css and html pages)
3 Every JBoss Tools UI Element like: New Wizard, Editor, Dialog, View should have set help context through call
{code}PlatformUI.getWorkbench().getHelpSystem().setHelp(container, "plugin.id.<uielementname>_<name>");{code}
where:
* <uielementname> could be one of: newwizard, dialog, editor, view and e.t.c
* <name> is readable feature name
For example for new JSF Project Wizard it would be "org.jboss.tools.jsf.ui.newwizard_jsfproject
If no context help requires then default context id should be used for example "org.jboss.tools.foundation.help.default"
4. org.jboss.tools.foundation.help registers so called Global Help Context Provider which process requested help context if itis not found by other context providers:
* RemoteContextProvider (loads context from remote Info Center server(s) registered in preferences Help->Content)
* FileContextProvider (load conext help form xml files defined through org.eclipse.help.base.contexts extension point, which is usually done in documentation bundles)
So if doc plugins (which usually defines context help) are not installed or not available from remote info center then control gets int global provider and it generates default page for context help with:
* short description
* link to external site
* command to call documentation feature installation out of JBoss Central
* command to register remote info center with JBoss Tools documentation
Default context help by default is generated for JBoss Tools, but could be overriden in JBDS or other JBoss Tools Based product.
Tested this approach on local build with local info center and it works as expected.
was (Author: dgolovin):
It looks like we can finally get decent help for all JBossTools/JBDS related features. It could be done by installing documentation features from p2 repo or by connecting local help information center to remote one:
1. We should deploy remote Information Center with JBT/JBDS documentation in eclipse format. Information center can be deployed as war application
2. Documentation feature(s) could be built out of current documentation (need to create features and plug-ins that would aggregate doc artifacts like topic.xml, css and html pages)
3 Every JBoss Tools UI Element like: New Wizard, Editor, Dialog, View should have set help context through call
{code}PlatformUI.getWorkbench().getHelpSystem().setHelp(container, "plugin.id.<uielementname>_<name>");{code}
where:
* <uielementname> could be one of: newwizard, dialog, editor, view and e.t.c
* <name> is readable feature name
For example for new JSF Project Wizard it would be "org.jboss.tools.jsf.ui.newwizard_jsfproject
If no context help requires then default context id should be used for example "org.jboss.tools.foundation.help.default"
4. org.jboss.tools.foundation.help registers so called Global Help Context Provider which process requested help context if itis not found by other context providers:
* RemoteContextProvider (loads context from remote Info Center server(s) registered in preferences Help->Content)
* FileContextProvider (load conext help form xml files defined through org.eclipse.help.base.contexts extension point, which is usually done in documentation bundles)
So if doc plugins (which usually defines context help) are not installed or not available from remote info center then control gets int global provider and it generates default page for context help with:
* short description
* link to external site
* command to call documentation feature installation out of JBoss Central
* command to register remote info center with JBoss Tools documentation
Default context help by default is generated for JBoss Tools, but could be overriden in JBDS or other JBoss Tools Based product.
Tested this approach on local build with local info center and it works as expected.
> Help button works not in all wizards.
> -------------------------------------
>
> Key: JBIDE-2032
> URL: https://issues.jboss.org/browse/JBIDE-2032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: help
> Affects Versions: 2.1.0.beta1
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG, Resource - Eclipse Platform _028.png
>
>
> Wizards with non-working help button attached.
--
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, 1 month
[JBoss JIRA] (JBTIS-245) Please update JBTIS TP dependencies to Luna Alpha1
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-245?page=com.atlassian.jira.plugin.... ]
Rob Cernich commented on JBTIS-245:
-----------------------------------
I don't see how we can update the TP when we have at least two releases coming out prior to JBDS 8: tooling refresh in March and FSW 6.1 after that. For SwitchYard, this would require a fork, which is of little use since there is no capacity to work on any possible integration issues that may arise for Luna (i.e. we're busy enough with feature development).
I'm assuming, of course, that these next couple of releases will be targeting JBDS 7.
> Please update JBTIS TP dependencies to Luna Alpha1
> --------------------------------------------------
>
> Key: JBTIS-245
> URL: https://issues.jboss.org/browse/JBTIS-245
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: BPEL, drools/ jBPM, ESB, Fuse IDE, modeshape, savara, switchyard, teiid
> Affects Versions: 4.2.0.Alpha1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> Greetings - welcome to Luna!
> An Alpha1 version of the Eclipse Luna based JBTIS TP is now available in nexus [1]. It's also available here [2] and an integration build of the current Luna JBTIS is available here [3].
> I'm still working on dates but if we could get a first cut at the scope involved with upgrading that would help planning this thing immensely. There is SpringIDE and graphiti changes among others.
> Thanks!
> [1] https://repository.jboss.org/nexus/content/repositories/releases/org/jbos...
> [2] http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Al...
> [3] http://download.jboss.org/jbosstools/updates/integration/luna/integration...
--
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, 1 month