[JBoss JIRA] (JBIDE-14390) JSF 'New Project' preferences and wizard should have matching labels for the same fields
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14390?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14390:
-----------------------------------
Assignee: Daniel Azarov (was: Viacheslav Kabanovich)
> JSF 'New Project' preferences and wizard should have matching labels for the same fields
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-14390
> URL: https://issues.jboss.org/browse/JBIDE-14390
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.0.Alpha2
> Reporter: Michelle Murray
> Assignee: Daniel Azarov
> Fix For: 4.2.x
>
> Attachments: JSF_NewProjectPreferences.png, JSF_NewProjectWizard1.png, JSF_NewProjectWizard2.png
>
>
> 1. Window>Preferences>JBoss Tools>Web>JSF>Project, New Project tab has the following labels (screen capture attached):
> * Version
> * Project Template
> * Use Default Path
> * Projects Root
> * Servlet Version
> 2. File>New>Project>JBoss Tools Web>JSF>JSF Project wizard, page 1 and 2 have the following labels (screen captures attached):
> * Use default path
> * Location
> * JSF Environment
> * Template
> * ServletVersion
> List 1 and 2 refer to the same things but use different labels. The labels should be identical. I would suggest changing:
> In preferences:
> Version -> JSF Version
> Use Default Path -> Use default path
> Projects Root -> Location
> In the wizard:
> JSF Environment -> JSF Version
> Template -> Project Template
> ServletVersion -> Servlet Version
--
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
11 years, 2 months
[JBoss JIRA] (JBIDE-11899) Show a warning when no observer exists to receive an injected event
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11899?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-11899:
-----------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Show a warning when no observer exists to receive an injected event
> -------------------------------------------------------------------
>
> Key: JBIDE-11899
> URL: https://issues.jboss.org/browse/JBIDE-11899
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdi
> Affects Versions: 3.3.0.Beta2
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: LATER
>
>
> With the following event
> {code}
> @Inject
> private Event<EventLog> eventLog;
> {code}
> cannot be delivered to
> {code}
> public void log(@Observes @Now EventLog eventLog) {
> ...
> }
> {code}
> by
> {code}
> eventLog.fire();
> {code}
> Can it be of use to put a warning on field 'eventLog', when the application has no observer to receive it?
--
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
11 years, 2 months
[JBoss JIRA] (JBIDE-14456) type="url" warning in editor
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14456?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-14456:
--------------------------------------
Assignee: Daniel Azarov (was: Alexey Kazakov)
Daniel, please verify if it's fixed in WTP 3.5.1
> type="url" warning in editor
> ----------------------------
>
> Key: JBIDE-14456
> URL: https://issues.jboss.org/browse/JBIDE-14456
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Reporter: Burr Sutter
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Alpha1
>
> Attachments: scr.png, Screen Shot 2013-05-15 at 9.37.53 AM.png
>
>
> The HTML editor reports a warning on
> <div data-role="fieldcontain">
> <label for="url-1">website</label>
> <input name="url-1" id="url-1" data-clear-btn="true" value="" type="url"/>
> </div>
> generated by the jQuery Mobile Palette
--
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
11 years, 2 months
[JBoss JIRA] (JBIDE-14732) Hide preview should hide preview only
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14732?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14732:
-----------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Hide preview should hide preview only
> -------------------------------------
>
> Key: JBIDE-14732
> URL: https://issues.jboss.org/browse/JBIDE-14732
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Beta1
> Environment: Any
> Reporter: Denis Golovin
> Assignee: Alexey Kazakov
> Labels: usability
> Fix For: LATER
>
> Attachments: dialog-new.gif, dialog.gif
>
>
> Now Hide Preview button forces to close whole right part of wizard. It looks ok, but jumps to much and hides html source too. Looks like this:
> !dialog.gif!
> Would it be better to have it implemented like this:
> !dialog-new.gif!
--
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
11 years, 2 months
[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2623:
----------------------------------
Next missing IU:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/1321/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2Fjbosstools-directory.xml,eclipseBundleVersion=kepler.R,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/console}
Contains: Missing requirement: Spring AOP 4.0.0.20130522-M1 (org.springframework.aop 4.0.0.20130522-M1) requires 'package org.aopalliance.aop [1.0.0,2.0.0)' but it could not be found
{code}
> Create target platform for mirrored parts of Central / 3rd Party Extras
> -----------------------------------------------------------------------
>
> Key: JBDS-2623
> URL: https://issues.jboss.org/browse/JBDS-2623
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.Alpha2, 7.1.0.Beta1
>
> Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png
>
>
> As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central.
> Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files.
> In future, we would:
> * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org]
> * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com]
> * add a whole new aggregate for old + new content
--
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
11 years, 2 months
[JBoss JIRA] (JBIDE-15509) prepare for JBDS 7.0.1 patch release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15509?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15509:
------------------------------------
After much debate it's been decided that in addition to the actual reason for this patch release, JBIDE-15494, we ought to also update the JBDS update site to include the Kepler SR1 bits, since they were released just last week.
Respinning third candidate release now:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=7
Will push to QE when done.
> prepare for JBDS 7.0.1 patch release
> ------------------------------------
>
> Key: JBIDE-15509
> URL: https://issues.jboss.org/browse/JBIDE-15509
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: updatesite
> Affects Versions: 4.1.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.1.Final
>
> Attachments: 15509_JBDS701.CR1.png, 15509_JBT4101.CR1.png
>
>
> Placeholder JIRA to contain work needed to do to release JBDS 7.0.1.GA:
> 1. branch jbosstools-central from 4.1.x to 4.1.0.x
> 2. adjust jbosstools-central/site/category.xml so it only contains the affected features (and feature.sources)
> 3. build Central using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_410/ which gets its sources from the correct fork/branch
> 4. create new composite staging site containing the last stable release + the new staging site for jbosstools-central, eg.,
> http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1....
> 5. branch jbdevstudio-product from 4.1.x to 4.1.0.x
> 6. ensure that JBDS sources are correctly versioned (eg., 7.0.1 not 7.1.0)
> 7. build JBDS using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_70/ which sets -DBUILD_ALIAS=GA, pulls from the correct branch origin/jbosstools-4.1.0.x, and sets these overrides in the maven configuration:
> {code}
> jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools...
> jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c...
> {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
11 years, 2 months