[JBoss JIRA] (JBIDE-14412) jQuery Mobile wizards do not show descriptions
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-14412:
---------------------------------------------
Summary: jQuery Mobile wizards do not show descriptions
Key: JBIDE-14412
URL: https://issues.jboss.org/browse/JBIDE-14412
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html source editing
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.1.0.Beta1
Implementation assigns description to wizards, but DefaultDropWizardPage.runValidation() makes a call setMessage("",NONE) which overrides description with an empty message.
It should rather call setMessage(null,NONE);
--
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, 11 months
[JBoss JIRA] (JBTIS-83) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
by Len DiMaggio (JIRA)
Len DiMaggio created JBTIS-83:
---------------------------------
Summary: JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
Key: JBTIS-83
URL: https://issues.jboss.org/browse/JBTIS-83
Project: JBoss Tools Integration Stack
Issue Type: Task
Security Level: Public (Everyone can see)
Components: ESB
Affects Versions: 4.0.0
Reporter: Len DiMaggio
Assignee: Paul Leacu
Fix For: 4.0.0
JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
Steps as defined by Nick (thanks Nick!):
a) the contents of the examples are in a former employee's SVN workspace
and haven't been updated since a couple of years. They don't really work
as well as they could.
b) the examples are all mostly duplicated in the quickstarts folder that
ships with SOA-P 5.3.1. See
https://bugzilla.redhat.com/show_bug.cgi?id=951677 and
https://issues.jboss.org/browse/JBTIS-62
Basically, we need to:
* fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable
eclipse projects (merge in contents from duplicate examples in Denny's
workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned;
if not, no great need.
* copy the older examples that are not already in SOA-P 5.3 - the ones
that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be
available there.
* update the BPEL Examples guide as needed
* document the fact that these examples are no longer available as
importable zipped example projects contributed by a plugin, but rather
as already-unpacked projects nested within the SOA-P runtime zip
--
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, 11 months
[JBoss JIRA] (JBDS-2624) Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2624?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-2624.
----------------------------
Max is happy, so closing.
> Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2624
> URL: https://issues.jboss.org/browse/JBDS-2624
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: updatesite
> Affects Versions: 7.0.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Max Rydahl Andersen
> Priority: Trivial
> Fix For: 7.0.0.Beta1
>
> Attachments: InstallContentAfterRunningUniversalInstaller.png
>
>
> After installation Eclipse Install dialog looks like:
> !InstallContentAfterRunningUniversalInstaller.png!
> These two features should not be visible after installation:
> 1. Usage Feature - should be included into JBDS product feature
> 2. Common Mylyn - should be uncategorised, because it doesn't provide any visible functionality for user and it is installed when Mylyn Issue Tracker Connector installed out of central.
--
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, 11 months
[JBoss JIRA] (JBIDE-14411) Internal interface constant used by seam tests
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-14411:
-----------------------------------
Summary: Internal interface constant used by seam tests
Key: JBIDE-14411
URL: https://issues.jboss.org/browse/JBIDE-14411
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 4.1.0.Beta1
Reporter: Rob Stryker
Assignee: Alexey Kazakov
Fix For: 4.1.0.Beta1
It seems you're pulling a string "EAP" from an interface which was not meant to be public.
It'd be better to use JBossServerType.EAP.getId() instead.
org.jboss.tools.runtime.seam.detector.test/src/org/jboss/tools/runtime/seam/detector/test/SeamRuntimeDetectionTest.java:import org.jboss.ide.eclipse.as.core.runtime.IJBossRuntimePluginConstants
--
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, 11 months
[JBoss JIRA] (JBIDE-14410) Maven Test class importing internal class JBossASHandler
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-14410:
-----------------------------------
Summary: Maven Test class importing internal class JBossASHandler
Key: JBIDE-14410
URL: https://issues.jboss.org/browse/JBIDE-14410
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.1.0.Beta1
Reporter: Rob Stryker
Assignee: Fred Bricon
Priority: Critical
Fix For: 4.1.0.Beta1
./jbosstools-central/maven/tests/org.jboss.tools.maven.sourcelookup.test/src/org/jboss/tools/maven/sourcelookup/test/SourceLookupTest.java has the following method:
{code}
private static IRuntimeDetectorDelegate getJBossASHandler() {
Set<IRuntimeDetector> detectors = RuntimeCoreActivator.getDefault().getRuntimeDetectors();
for (IRuntimeDetector detector:detectors) {
IRuntimeDetectorDelegate delegate = ((RuntimeDetector)detector).getDelegate();
if (delegate instanceof JBossASHandler) {
return delegate;
}
}
return null;
}
{code}
The class and its package name are not technically API. It would be best if you instead compared against the handler's id: org.jboss.tools.runtime.handlers.JBossASHandler
Since this ID is declared in plugin.xml, it's best if you hard-code the string.
Trying to clean up people who depend on my internal classes so that I can get to organizing stuff properly.
--
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, 11 months
[JBoss JIRA] (JBIDE-14088) Generate TP source feature site + composite site merging matching TP with TP sources
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14088?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-14088:
-------------------------------------
Great work and I'm very pleased, but, fix the important gaps ;)
I will say if we can get facets, tm/rse, (for me) and egit (for me and some others) in there, this will be very very useful for others. Other devs have been telling me they often have to rebuild their env also since eclipse m6 keeps breaking workspaces.
This is great progress!
> Generate TP source feature site + composite site merging matching TP with TP sources
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-14088
> URL: https://issues.jboss.org/browse/JBIDE-14088
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.1.0.Beta1
>
> Attachments: JBIDE-14088.missing.txt, JBIDE14088.sources.list.txt
>
>
> Every time we produce a target platform update site zip on download.jboss.org we should also produce an update site containing only sources.
> Then the composite site http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... could include:
> * REPO/
> * SRC-REPO/ *NEW*
> * compositeArtifacts.xml, compositeContent.xml --> points to both REPO/ and SRC-REPO/ *NEW*
> * jbosstoolstarget-4.30.5.Alpha4-SNAPSHOT.zip
> * jbosstoolstarget-4.30.5.Alpha4-SNAPSHOT.zip.MD5
> * jbosstoolstarget-sources-4.30.5.Alpha4-SNAPSHOT.zip *NEW*
> * jbosstoolstarget-sources-4.30.5.Alpha4-SNAPSHOT.zip.MD5 *NEW*
--
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, 11 months
[JBoss JIRA] (JBIDE-14088) Generate TP source feature site + composite site merging matching TP with TP sources
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14088?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-14088:
-------------------------------------
This works *VERY* well. It is fast, repeatable, and in all ways fantastic. But there are gaps, and I wonder why.
The big things that I'm missing are FACETED PROJECTS (?!? what?) and RSE source, and then I'm all set! I'm really not sure why faceted project source is not included here. ALL of the rest of WTP is. So to me the absence of faceted projects is problematic.
For RSE (which I *do* need), none of it is available.
I am attaching a list of jars in my multiple/target/jbosstools.multiple.target.repo folder which are missing corresponding source jars. I'm not asking you to investigate each and every one, because that's a waste of time. But, it can help you spot obvious errors for things that are missing.
For me, the things that are missing are all the facet jars (org.eclipse.wst AND org.eclipse.jst) as well as RSE / tm (targeted management). But for others, things like Egit, birt, m2e, m2e-wtp, mylyn, and swtbot might be useful to make this solution the best ever.
While I am now 98% pleased, I'm still keeping this jira opened until RSE / TM and faceted projects have their source, just because I like to nag you ;)
> Generate TP source feature site + composite site merging matching TP with TP sources
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-14088
> URL: https://issues.jboss.org/browse/JBIDE-14088
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.1.0.Beta1
>
> Attachments: JBIDE-14088.missing.txt, JBIDE14088.sources.list.txt
>
>
> Every time we produce a target platform update site zip on download.jboss.org we should also produce an update site containing only sources.
> Then the composite site http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... could include:
> * REPO/
> * SRC-REPO/ *NEW*
> * compositeArtifacts.xml, compositeContent.xml --> points to both REPO/ and SRC-REPO/ *NEW*
> * jbosstoolstarget-4.30.5.Alpha4-SNAPSHOT.zip
> * jbosstoolstarget-4.30.5.Alpha4-SNAPSHOT.zip.MD5
> * jbosstoolstarget-sources-4.30.5.Alpha4-SNAPSHOT.zip *NEW*
> * jbosstoolstarget-sources-4.30.5.Alpha4-SNAPSHOT.zip.MD5 *NEW*
--
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, 11 months