[JBoss JIRA] (JBIDE-16960) removed GPE feature from Beta2-SNAPSHOT targetplatform, and now the JBT agg site won't build
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16960:
----------------------------------
Summary: removed GPE feature from Beta2-SNAPSHOT targetplatform, and now the JBT agg site won't build
Key: JBIDE-16960
URL: https://issues.jboss.org/browse/JBIDE-16960
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Nick Boldt
I removed the deprecated GPE feature [1] because it can't be installed onto Luna (JBIDE-16910).
[1] https://github.com/jbosstools/jbosstools-target-platforms/pull/48/files#d...
So now we get this:
{code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/8748/console}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.site.core raw:4.2.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.2.0-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 requires 'bundle com.google.gdt.eclipse.suite 3.0.1' but it could not be found
[ERROR] Cannot satisfy dependency: org.jboss.tools.gwt.feature.feature.group 1.1.0.Final-v20130205-2223-B78 depends on: org.jboss.tools.gwt.core [1.1.0.Final-v20130205-2223-B78]
[ERROR] Cannot satisfy dependency: org.jboss.tools.site.core raw:4.2.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.2.0-SNAPSHOT depends on: org.jboss.tools.gwt.feature.feature.group 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 to bundle com.google.gwt.eclipse.core 0.0.0.; Unable to satisfy dependency from org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 to bundle com.google.gdt.eclipse.suite 3.0.1.; Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.6.0.Beta2-v20140321-0445-B465 to bundle com.google.gwt.eclipse.core 2.5.0.; Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.6.0.Beta2-v20140321-0445-B465 to bundle com.google.gwt.eclipse.oophm 3.0.0.; No solution found because the problem is unsatisfiable.] -> [Help 1]{code}
Does the *org.jboss.tools.gwt.feature* need to remain in the JBT update site? Or... should I add the com.google.gwt.eclipse.core plugin back into the JBoss Tools 4.40.0.Beta2-SNAPSHOT target platform [2]? At the moment, only com.google.gwt.eclipse.sdkbundle_2.5.1 is present (in the previous TP [3], we had more:
{code:title=http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta1/REPO/plugins/}
com.google.appengine.*
com.google.gdt.eclipse.*
com.google.gwt.eclipse.core_3.4.2.v201310081834-rel-r43.jar
com.google.gwt.eclipse.oophm_3.4.2.v201310081834-rel-r43.jar
com.google.gwt.eclipse.sdkbundle_2.5.1.jar
{code}
[2] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
[3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-482) Add info on new download feature for enterprise servers
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-482:
----------------------------------------
Summary: Add info on new download feature for enterprise servers
Key: TOOLSDOC-482
URL: https://issues.jboss.org/browse/TOOLSDOC-482
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: User Guide - JBoss Server Tools
Affects Versions: 4.2.0.Beta1
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.2.0.Beta1
Within IDE could always download JBoss AS servers. That functionality has now been extended to downloading JBoss EAP servers.
Writer task: Edit topic 23487, which was previously solely for JBT. Add conditions as necessary to the steps so that they accommodate the JBDS/EAP workflow. Make two new screen caps for JBDS/EAP and use conditions to add then to the existing <imageobject> tags. Add this topic to the JBDS User Guide content spec after Features Overview [22815].
--
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, 7 months
[JBoss JIRA] (JBIDE-16960) removed GPE feature from Beta2-SNAPSHOT targetplatform, and now the JBT agg site won't build
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16960?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16960:
-------------------------------
Affects Version/s: 4.2.0.Beta1
> removed GPE feature from Beta2-SNAPSHOT targetplatform, and now the JBT agg site won't build
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-16960
> URL: https://issues.jboss.org/browse/JBIDE-16960
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
>
> I removed the deprecated GPE feature [1] because it can't be installed onto Luna (JBIDE-16910).
> [1] https://github.com/jbosstools/jbosstools-target-platforms/pull/48/files#d...
> So now we get this:
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/8748/console}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.site.core raw:4.2.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.2.0-SNAPSHOT
> [ERROR] Missing requirement: org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 requires 'bundle com.google.gdt.eclipse.suite 3.0.1' but it could not be found
> [ERROR] Cannot satisfy dependency: org.jboss.tools.gwt.feature.feature.group 1.1.0.Final-v20130205-2223-B78 depends on: org.jboss.tools.gwt.core [1.1.0.Final-v20130205-2223-B78]
> [ERROR] Cannot satisfy dependency: org.jboss.tools.site.core raw:4.2.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.2.0-SNAPSHOT depends on: org.jboss.tools.gwt.feature.feature.group 0.0.0
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 to bundle com.google.gwt.eclipse.core 0.0.0.; Unable to satisfy dependency from org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 to bundle com.google.gdt.eclipse.suite 3.0.1.; Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.6.0.Beta2-v20140321-0445-B465 to bundle com.google.gwt.eclipse.core 2.5.0.; Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.6.0.Beta2-v20140321-0445-B465 to bundle com.google.gwt.eclipse.oophm 3.0.0.; No solution found because the problem is unsatisfiable.] -> [Help 1]{code}
> Does the *org.jboss.tools.gwt.feature* need to remain in the JBT update site? Or... should I add the com.google.gwt.eclipse.core plugin back into the JBoss Tools 4.40.0.Beta2-SNAPSHOT target platform [2]? At the moment, only com.google.gwt.eclipse.sdkbundle_2.5.1 is present (in the previous TP [3], we had more:
> {code:title=http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta1/REPO/plugins/}
> com.google.appengine.*
> com.google.gdt.eclipse.*
> com.google.gwt.eclipse.core_3.4.2.v201310081834-rel-r43.jar
> com.google.gwt.eclipse.oophm_3.4.2.v201310081834-rel-r43.jar
> com.google.gwt.eclipse.sdkbundle_2.5.1.jar
> {code}
> [2] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
> [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
--
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, 7 months
[JBoss JIRA] (JBIDE-16960) removed GPE feature from Beta2-SNAPSHOT targetplatform, and now the JBT agg site won't build
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16960?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16960:
-------------------------------
Priority: Blocker (was: Major)
> removed GPE feature from Beta2-SNAPSHOT targetplatform, and now the JBT agg site won't build
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-16960
> URL: https://issues.jboss.org/browse/JBIDE-16960
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Priority: Blocker
>
> I removed the deprecated GPE feature [1] because it can't be installed onto Luna (JBIDE-16910).
> [1] https://github.com/jbosstools/jbosstools-target-platforms/pull/48/files#d...
> So now we get this:
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/8748/console}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.site.core raw:4.2.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.2.0-SNAPSHOT
> [ERROR] Missing requirement: org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 requires 'bundle com.google.gdt.eclipse.suite 3.0.1' but it could not be found
> [ERROR] Cannot satisfy dependency: org.jboss.tools.gwt.feature.feature.group 1.1.0.Final-v20130205-2223-B78 depends on: org.jboss.tools.gwt.core [1.1.0.Final-v20130205-2223-B78]
> [ERROR] Cannot satisfy dependency: org.jboss.tools.site.core raw:4.2.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.2.0-SNAPSHOT depends on: org.jboss.tools.gwt.feature.feature.group 0.0.0
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 to bundle com.google.gwt.eclipse.core 0.0.0.; Unable to satisfy dependency from org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 to bundle com.google.gdt.eclipse.suite 3.0.1.; Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.6.0.Beta2-v20140321-0445-B465 to bundle com.google.gwt.eclipse.core 2.5.0.; Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.6.0.Beta2-v20140321-0445-B465 to bundle com.google.gwt.eclipse.oophm 3.0.0.; No solution found because the problem is unsatisfiable.] -> [Help 1]{code}
> Does the *org.jboss.tools.gwt.feature* need to remain in the JBT update site? Or... should I add the com.google.gwt.eclipse.core plugin back into the JBoss Tools 4.40.0.Beta2-SNAPSHOT target platform [2]? At the moment, only com.google.gwt.eclipse.sdkbundle_2.5.1 is present (in the previous TP [3], we had more:
> {code:title=http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta1/REPO/plugins/}
> com.google.appengine.*
> com.google.gdt.eclipse.*
> com.google.gwt.eclipse.core_3.4.2.v201310081834-rel-r43.jar
> com.google.gwt.eclipse.oophm_3.4.2.v201310081834-rel-r43.jar
> com.google.gwt.eclipse.sdkbundle_2.5.1.jar
> {code}
> [2] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
> [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-482) Add info on new download feature for enterprise servers
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-482?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-482:
-------------------------------------
Sprint: 2014/S5 (31-Mar > 13-Apr)
> Add info on new download feature for enterprise servers
> -------------------------------------------------------
>
> Key: TOOLSDOC-482
> URL: https://issues.jboss.org/browse/TOOLSDOC-482
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Server Tools
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Within IDE could always download JBoss AS servers. That functionality has now been extended to downloading JBoss EAP servers.
> Writer task: Edit topic 23487, which was previously solely for JBT. Add conditions as necessary to the steps so that they accommodate the JBDS/EAP workflow. Make two new screen caps for JBDS/EAP and use conditions to add then to the existing <imageobject> tags. Add this topic to the JBDS User Guide content spec after Features Overview [22815].
--
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, 7 months
[JBoss JIRA] (JBIDE-16896) download runtime UI wizards has some weird workflow
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16896?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-16896:
-----------------------------------------
+1 to Max's issues with C) - not clear to me.
> download runtime UI wizards has some weird workflow
> ---------------------------------------------------
>
> Key: JBIDE-16896
> URL: https://issues.jboss.org/browse/JBIDE-16896
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
>
> using download runtime the dialogs gets maxed out dependent on the lenght of the URL it looks like.
> Making the wizard very clumsy to look and work with.
> - the table is just taking up all space - and the url is not useful (can't copy/paste/link it)
> - the table is in a dailog and there is 90% whitespace
> How about
> A) show the name and description in table
> B) Show the *info* url and if authorization is required enable username/password on the first page instead of requiring a second page for just that ?
> C) why can't we do authentication in a progress when clicking next instead of requiring users to manually click validate ?
> or at least tell the user to validate instead of just blanking out Next and *once* the credentials are valid actually show that isntead of just enabling Next.
> D) the license text shown is LGPL license - not $0 subscription (opening separate bug for this)
> E) the info url for the server is never actually shown in the workflow
> F) when clicking finish the dialog returns instantly to JBoss Runtime creation and it tells me the home dir does not exist...why did it not fill it in and let me wait ?
> G) It actually creates the server for me in the background *while* im in the server wizard flow....thats just weird.
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-481) Add section about reporting JBDS/JBT errors from within IDE
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-481?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-481:
-------------------------------------
Assignee: Suz Dorfield (was: Michelle Murray)
> Add section about reporting JBDS/JBT errors from within IDE
> -----------------------------------------------------------
>
> Key: TOOLSDOC-481
> URL: https://issues.jboss.org/browse/TOOLSDOC-481
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Suz Dorfield
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> Use case: Providing as much information as possible when submitting bugs found in JBDS/JBT increases the efficiently with which problems can be identified and resolved or reported upstream by the development team. The Report Problem wizard creates a .zip file containing IDE log files that you can then add to JIRAs you submit against JBDS/JBT.
> Procedure: Within IDE, Help > Report Problem; opens wizard in which to input details of problems, wizard creates zip with user's description of problem and IDE log files.
> Writer task: Create new topic including screen cap of wizard and add to JBDS and JBT user guide content specs at end of Features of JBoss Central and the JBoss Perspective section. May need to use conditions in topic text since topic will be shared by JBDS and JBT.
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-481) Add section about reporting JBDS/JBT errors from within IDE
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-481?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-481:
-------------------------------------
Original Estimate: 3 hours
Remaining Estimate: 3 hours
> Add section about reporting JBDS/JBT errors from within IDE
> -----------------------------------------------------------
>
> Key: TOOLSDOC-481
> URL: https://issues.jboss.org/browse/TOOLSDOC-481
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> Use case: Providing as much information as possible when submitting bugs found in JBDS/JBT increases the efficiently with which problems can be identified and resolved or reported upstream by the development team. The Report Problem wizard creates a .zip file containing IDE log files that you can then add to JIRAs you submit against JBDS/JBT.
> Procedure: Within IDE, Help > Report Problem; opens wizard in which to input details of problems, wizard creates zip with user's description of problem and IDE log files.
> Writer task: Create new topic including screen cap of wizard and add to JBDS and JBT user guide content specs at end of Features of JBoss Central and the JBoss Perspective section. May need to use conditions in topic text since topic will be shared by JBDS and JBT.
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-481) Add section about reporting JBDS/JBT errors from within IDE
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-481?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-481:
-------------------------------------
Description:
Use case: Providing as much information as possible when submitting bugs found in JBDS/JBT increases the efficiently with which problems can be identified and resolved or reported upstream by the development team. The Report Problem wizard creates a .zip file containing IDE log files that you can then add to JIRAs you submit against JBDS/JBT.
Procedure: Within IDE, Help > Report Problem; opens wizard in which to input details of problems, wizard creates zip with user's description of problem and IDE log files.
Writer task: Create new topic including screen cap of wizard and add to JBDS and JBT user guide content specs at end of Features of JBoss Central and the JBoss Perspective section. May need to use conditions in topic text since topic will be shared by JBDS and JBT.
> Add section about reporting JBDS/JBT errors from within IDE
> -----------------------------------------------------------
>
> Key: TOOLSDOC-481
> URL: https://issues.jboss.org/browse/TOOLSDOC-481
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
>
> Use case: Providing as much information as possible when submitting bugs found in JBDS/JBT increases the efficiently with which problems can be identified and resolved or reported upstream by the development team. The Report Problem wizard creates a .zip file containing IDE log files that you can then add to JIRAs you submit against JBDS/JBT.
> Procedure: Within IDE, Help > Report Problem; opens wizard in which to input details of problems, wizard creates zip with user's description of problem and IDE log files.
> Writer task: Create new topic including screen cap of wizard and add to JBDS and JBT user guide content specs at end of Features of JBoss Central and the JBoss Perspective section. May need to use conditions in topic text since topic will be shared by JBDS and JBT.
--
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, 7 months
[JBoss JIRA] (TOOLSDOC-481) Add section about reporting JBDS/JBT errors from within IDE
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-481?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-481:
-------------------------------------
Sprint: 2014/S5 (31-Mar > 13-Apr)
> Add section about reporting JBDS/JBT errors from within IDE
> -----------------------------------------------------------
>
> Key: TOOLSDOC-481
> URL: https://issues.jboss.org/browse/TOOLSDOC-481
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> Use case: Providing as much information as possible when submitting bugs found in JBDS/JBT increases the efficiently with which problems can be identified and resolved or reported upstream by the development team. The Report Problem wizard creates a .zip file containing IDE log files that you can then add to JIRAs you submit against JBDS/JBT.
> Procedure: Within IDE, Help > Report Problem; opens wizard in which to input details of problems, wizard creates zip with user's description of problem and IDE log files.
> Writer task: Create new topic including screen cap of wizard and add to JBDS and JBT user guide content specs at end of Features of JBoss Central and the JBoss Perspective section. May need to use conditions in topic text since topic will be shared by JBDS and JBT.
--
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, 7 months