[JBoss JIRA] (JBIDE-20793) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Central]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20793?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-20793.
-------------------------------
Resolution: Done
Done in master
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Central]
> -----------------------------------------------------------
>
> Key: JBIDE-20793
> URL: https://issues.jboss.org/browse/JBIDE-20793
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Central]: Please perform the following tasks:
> 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.)
> Otherwise:
> 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT
> {code}
> 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20782) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20782?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20782:
--------------------------------------
Assignee: Alexey Kazakov
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Base]
> --------------------------------------------------------
>
> Key: JBIDE-20782
> URL: https://issues.jboss.org/browse/JBIDE-20782
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Base]: Please perform the following tasks:
> 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.)
> Otherwise:
> 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT
> {code}
> 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20782) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20782?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-20782.
----------------------------------
Resolution: Done
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Base]
> --------------------------------------------------------
>
> Key: JBIDE-20782
> URL: https://issues.jboss.org/browse/JBIDE-20782
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Base]: Please perform the following tasks:
> 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.)
> Otherwise:
> 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT
> {code}
> 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20785) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20785?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20785:
--------------------------------------
Assignee: Alexey Kazakov
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [JavaEE]
> ----------------------------------------------------------
>
> Key: JBIDE-20785
> URL: https://issues.jboss.org/browse/JBIDE-20785
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [JavaEE]: Please perform the following tasks:
> 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.)
> Otherwise:
> 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT
> {code}
> 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20785) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20785?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-20785.
----------------------------------
Resolution: Done
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [JavaEE]
> ----------------------------------------------------------
>
> Key: JBIDE-20785
> URL: https://issues.jboss.org/browse/JBIDE-20785
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [JavaEE]: Please perform the following tasks:
> 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.)
> Otherwise:
> 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT
> {code}
> 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20786) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [JST]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20786?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-20786.
----------------------------------
Assignee: Alexey Kazakov
Resolution: Done
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [JST]
> -------------------------------------------------------
>
> Key: JBIDE-20786
> URL: https://issues.jboss.org/browse/JBIDE-20786
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [JST]: Please perform the following tasks:
> 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.)
> Otherwise:
> 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT
> {code}
> 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20773) JBoss Tools source zip contains nested zips?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20773?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-20773.
------------------------------
Fix Version/s: 4.3.0.Final
Resolution: Cannot Reproduce Bug
With a clean workspace, could not reproduce.
So, maybe we ned to just purge the site/cache/*.zip between builds? I've added this to the two jobs [1], [2].
{code}
# JBIDE-20773 purge cache of old source zips
rm -fr ${WORKSPACE}/sources/aggregate/site/cache/*.zip
{code}
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
> JBoss Tools source zip contains nested zips?
> --------------------------------------------
>
> Key: JBIDE-20773
> URL: https://issues.jboss.org/browse/JBIDE-20773
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.0.Final
>
>
> I noticed that the latest JBT 4.3.0.CR1a build's source zip and update site are both 388M [1]:
> {code}
> [ ] jbosstools-4.3.0.CR1-src.zip 17-Sep-2015 22:51 388M
> [ ] repository.zip 17-Sep-2015 22:49 388M
> {code}
> [1] http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-4.3.0...
> Yet when I build locally, I get these sizes:
> {code}
> -rw-rw-r-- 1 nboldt nboldt 247M Sep 23 14:05 repository.zip
> -rw-rw-r-- 1 nboldt nboldt 222M Sep 23 14:09 jbosstools-4.3.0.CR2-src.zip
> {code}
> Also noticed that the CR1a src zip contains this:
> {code}
> jbosstools-4.3.0.CR1-src
> jbosstools-livereload_ccd14f8a3ac6f99379c932b1ecbd069679c53c20_sources.zip
> jbosstools-aerogear_8cc37fac2c06c12165becc71377d4367627146db_sources.zip
> jbosstools-vpe_a6c1b12f38e9e56c4f2aa3af5ca057c90b1ca60a_sources.zip
> jbosstools-javaee_788cd9fabcfb402ffe30c060d338cb334fb8f754_sources.zip
> jbosstools-webservices_0b33c0e8aee5da84a0c8a55906b95084a4ea0b8a_sources.zip
> {code}
> The in the *src folder:
> {code}
> buildinfo
> jbosstools-aerogear-4760415028f4cd667cffc1caaa0647b26a791bd2
> jbosstools-arquillian-412c297a0a6092cd5b877e9972c6a96dcf57c3fb
> jbosstools-base-49f978da2bbccf381b26dbd64dc08ccd1138a0ab
> jbosstools-birt-d2e797324294e60048d39d24536f2f16b1b78e30
> jbosstools-browsersim-b284a67fa3ccac3dfa2383873aeb24a3a4486c8e
> jbosstools-build-sites-0580a57bed9d3b0ae957b2f5f6f26cc71a3159c2
> jbosstools-central-b3f750efa36eea63bc7dd2f77d3aca798583c48e
> jbosstools-forge-20aafeb5f36fcf70f3658e9ad45c6b8b405b8af2
> jbosstools-freemarker-171cac721242580d65699e52544f38c44eac7019
> jbosstools-hibernate-fe17a3451ec4c278da05f4563ab6ebadb5437717
> jbosstools-javaee-c46ca764fae83c2525d4b8ad885b12b8b3f0c14d
> jbosstools-jst-333c9a71aca9b449b5bae05a12e770f988ef7178
> jbosstools-livereload-bf4fa2662aa7e625198ce178701c9a0b9fd9bd72
> jbosstools-openshift-951590f4f5cf8d004b36e30d460d985be50ed42e
> jbosstools-portlet-4eec888e7045ab1413934670cbdcdf7a11447b52
> jbosstools-server-b3c0959c85a130fca26165e46737e90565aad983
> jbosstools-vpe-ce6b5237c98a138a3ef55ec7baf0c3e37ed81490
> jbosstools-webservices-6aa98d422ce06a4aa53d35076cd405bc5f78ef31
> jbosstools-xulrunner-2edce933f7d64efbb4d7a5b16be8dadae8de766e
> {code}
> When I build locally, I get just one subfolder in the zip:
> {code}
> jbosstools-4.3.0.CR1-src
> {code}
> and in the *src folder:
> {code}
> buildinfo
> jbosstools-aerogear-4760415028f4cd667cffc1caaa0647b26a791bd2
> jbosstools-arquillian-412c297a0a6092cd5b877e9972c6a96dcf57c3fb
> jbosstools-base-49f978da2bbccf381b26dbd64dc08ccd1138a0ab
> jbosstools-birt-d2e797324294e60048d39d24536f2f16b1b78e30
> jbosstools-browsersim-2dce9b6a53cb99e400ff6d4023d1545f5393db26
> jbosstools-build-sites-6b2a3fe3373341e0ed8c3f31e2f62d75217c2873
> jbosstools-central-b3f750efa36eea63bc7dd2f77d3aca798583c48e
> jbosstools-forge-20aafeb5f36fcf70f3658e9ad45c6b8b405b8af2
> jbosstools-freemarker-171cac721242580d65699e52544f38c44eac7019
> jbosstools-hibernate-fe17a3451ec4c278da05f4563ab6ebadb5437717
> jbosstools-javaee-c46ca764fae83c2525d4b8ad885b12b8b3f0c14d
> jbosstools-jst-333c9a71aca9b449b5bae05a12e770f988ef7178
> jbosstools-livereload-bf4fa2662aa7e625198ce178701c9a0b9fd9bd72
> jbosstools-openshift-951590f4f5cf8d004b36e30d460d985be50ed42e
> jbosstools-portlet-4eec888e7045ab1413934670cbdcdf7a11447b52
> jbosstools-server-b3c0959c85a130fca26165e46737e90565aad983
> jbosstools-vpe-ce6b5237c98a138a3ef55ec7baf0c3e37ed81490
> jbosstools-webservices-6aa98d422ce06a4aa53d35076cd405bc5f78ef31
> jbosstools-xulrunner-2edce933f7d64efbb4d7a5b16be8dadae8de766e
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBTIS-399) Cannot install Fuse/SwitchYard tooling in offline mode
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-399?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-399:
----------------------------------
Hey [~apodhrad] - this now works for me like this:
1. Install jboss-devstudio-9.0.0.CR1-v20150918-0257-B105-installer-standalone
2. Add the zip files (jbdsis-alpha2, jbdsis-alpha2-ea) - no jbds-core
3. Try to install SY from jbdsis-alpha2-ea
What specifically did you install for jbds-core?
> Cannot install Fuse/SwitchYard tooling in offline mode
> ------------------------------------------------------
>
> Key: JBTIS-399
> URL: https://issues.jboss.org/browse/JBTIS-399
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Critical
> Fix For: 9.0.0.Alpha1
>
> Attachments: error.txt, oi1.png, oi2.png, oi3.png
>
>
> Cannot install JBDS-IS 8.0.0.GA early access in offline mode. Note that DV tooling (Teiid Designer and ModeShape) can be installed without any problem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months