[JBoss JIRA] (JBDS-2439) jbdevstudio-unity execution fails when called from different working directory
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2439?page=com.atlassian.jira.plugin.... ]
Pavol Srna closed JBDS-2439.
----------------------------
Verified in jbdevstudio-product-universal-7.0.0.Beta1-v20130526-0839-B241.jar.
> jbdevstudio-unity execution fails when called from different working directory
> ------------------------------------------------------------------------------
>
> Key: JBDS-2439
> URL: https://issues.jboss.org/browse/JBDS-2439
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 6.0.0.GA
> Reporter: Ondrej Skutka
> Assignee: Denis Golovin
> Fix For: 7.0.0.Beta1
>
>
> jbdevstudio-unity script fails with {code}line 17: ./studio/jbdevstudio: No such file or directory{code} when called from a working directory different from jbdevstudio install dir.
> This is caused by relative path in the script (??./studio/jbdevstudio??) introduced by the fix in JBDS-1781.
--
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, 10 months
[JBoss JIRA] (TOOLSDOC-343) NeedInfo: Disabling validation to remove/reduce false warnings
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-343?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-343:
------------------------------------------
[~akazakov], sorry another Q relating to this.
I get that the @FacesConverter validation is resolved. But are there any validation issues with JSF in general that report false warnings/errors? Or is this just a CDI issue now?
> NeedInfo: Disabling validation to remove/reduce false warnings
> --------------------------------------------------------------
>
> Key: TOOLSDOC-343
> URL: https://issues.jboss.org/browse/TOOLSDOC-343
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - JSF Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
>
> I came across: http://docs.jboss.org/tools/whatsnew/jst/jst-news-3.3.0.M5.html
> It states:
> 1) JSF @FacesConverter validation: faces converter validation is an issue in eclipse
> 2) Configuring Problem Severity via Quick Fix: problems if you use CDI programatically or you use CDI components that are not detectable by the tooling
> *Are these instances of validation still issues?*
> I tested (1) with <f:converter converterID="test"></f:converter> and didn't get any error or warning messages so thought it might be fixed in eclipse. Not sure how to test CDI yet (haven't got to that chapter!).
--
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, 10 months
[JBoss JIRA] (TOOLSDOC-343) NeedInfo: Disabling validation to remove/reduce false warnings
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-343?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-343:
-------------------------------------
Assignee: Alexey Kazakov (was: Michelle Murray)
> NeedInfo: Disabling validation to remove/reduce false warnings
> --------------------------------------------------------------
>
> Key: TOOLSDOC-343
> URL: https://issues.jboss.org/browse/TOOLSDOC-343
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - JSF Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Alexey Kazakov
> Fix For: 4.1.0
>
>
> I came across: http://docs.jboss.org/tools/whatsnew/jst/jst-news-3.3.0.M5.html
> It states:
> 1) JSF @FacesConverter validation: faces converter validation is an issue in eclipse
> 2) Configuring Problem Severity via Quick Fix: problems if you use CDI programatically or you use CDI components that are not detectable by the tooling
> *Are these instances of validation still issues?*
> I tested (1) with <f:converter converterID="test"></f:converter> and didn't get any error or warning messages so thought it might be fixed in eclipse. Not sure how to test CDI yet (haven't got to that chapter!).
--
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, 10 months
[JBoss JIRA] (JBIDE-14677) jobs that depend on com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0-SNAPSHOT are broken as that version no longer exists
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14677?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-14677:
----------------------------------------
Should I use the GitHub repo or SVN to make that change?
> jobs that depend on com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0-SNAPSHOT are broken as that version no longer exists
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14677
> URL: https://issues.jboss.org/browse/JBIDE-14677
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> 21 jenkins jobs such as ./DevStudio/view/DevStudio_Trunk/job/jbosstools-4.1_trunk.install-tests.matrix/config.xml and ./DevStudio/view/DevStudio_Trunk/job/jbosstools-composite-install_master/config.xml, which depend on com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0-SNAPSHOT, are currently failing. I suspect this is because the 1.1.0 release has happened.
> Complete list of config.xml files containing the string "maven-download-plugin:1" are:
> {code}
> ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.director-install-tests.egit.matrix/config.xml
> ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.director-install-tests.m2e.matrix/config.xml
> ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.install-e3.7.0-jbt_3.3.x/config.xml
> ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.install-e3.7.2-jbt_3.3.0-jbt_3.3.x/config.xml
> ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.install-e4.2-jbt_3.3.x/config.xml
> ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.install-tests.egit.matrix/config.xml
> ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.install-tests.m2e.matrix/config.xml
> ./DevStudio/view/DevStudio_6.0.juno/job/jbdevstudio-6.0_stable_branch.install-tests-e4.2-jbds_BYOE_stable_branch/config.xml
> ./DevStudio/view/DevStudio_6.0.juno/job/jbdevstudio-6.0_stable_branch.install-tests-eclipseLatest-jbds_BYOE_stable_branch/config.xml
> ./DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests-e4.2-jbt_4.0.juno/config.xml
> ./DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests-eclipseLatest-jbt_4.0.juno/config.xml
> ./DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/config.xml
> ./DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.upgrade-tests.matrix/config.xml
> ./DevStudio/view/DevStudio_6.0.juno/job/jbosstools-composite-install_40/config.xml
> ./DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-composite-install_41/config.xml
> ./DevStudio/view/DevStudio_Disabled/job/zz_disabled_jbdevstudio-7.0_trunk.install-tests-eclipseLatest-jbds_BYOE_trunk/config.xml
> ./DevStudio/view/DevStudio_Disabled/job/zz_disabled_jbosstools-4.1_trunk.install-tests-eclipseLatest-jbt_trunk/config.xml
> ./DevStudio/view/DevStudio_Trunk/job/jbosstools-4.1_trunk.install-tests-e4.3-jbt_trunk/config.xml
> ./DevStudio/view/DevStudio_Trunk/job/jbosstools-4.1_trunk.install-tests-eclipseLatest-jbt_trunk/config.xml
> ./DevStudio/view/DevStudio_Trunk/job/jbosstools-4.1_trunk.install-tests.matrix/config.xml
> ./DevStudio/view/DevStudio_Trunk/job/jbosstools-composite-install_master/config.xml
> {code}
> Can you update the above jobs to use the correct new version, either 1.2.0-SNAPSHOT or 1.1.0 ?
--
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, 10 months
[JBoss JIRA] (JBDS-2038) JBDS installer should open JBDS upon completion
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2038?page=com.atlassian.jira.plugin.... ]
Pavol Srna closed JBDS-2038.
----------------------------
Verified in jbdevstudio-product-universal-7.0.0.Beta1-v20130526-0839-B241.jar.
> JBDS installer should open JBDS upon completion
> -----------------------------------------------
>
> Key: JBDS-2038
> URL: https://issues.jboss.org/browse/JBDS-2038
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Environment: jbdevstudio-product-win32-x86_64-5.0.0.v201202250031M-H77-Beta1.jar
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Fix For: 7.0.0.Beta1
>
> Attachments: JBDS-2038-CleanupClient-2.patch, JBDS-2038-CleanupClient.patch, JBDS-2038.patch, RunJBDSAfterInstallation.png
>
>
> As a user, once the JBDS installer completes, I expect it to open the newly installed JBDS.
> On the last page of the installer, there should be a checkbox asking the user if he wants to open JBDS immediately.
--
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, 10 months
[JBoss JIRA] (JBDS-2622) Do we need to add new server types to the installer?
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2622?page=com.atlassian.jira.plugin.... ]
Pavol Srna closed JBDS-2622.
----------------------------
> Do we need to add new server types to the installer?
> ----------------------------------------------------
>
> Key: JBDS-2622
> URL: https://issues.jboss.org/browse/JBDS-2622
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.0.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 7.0.0.Beta1
>
>
> Do we need to add a new server type string for EAP 6.1?
> {code:title=https://svn.jboss.org/repos/devstudio/trunk/product/installer/src/panels/com/jboss/jbds/installer/bean/ServerType.java, lines 46-50}
> "Application Server",
> BIN_PATH+File.separatorChar + TWIDDLE_JAR_NAME,
> new String[]{"6.0","5.1", "5.0", "4.2", "4.0", "3.2"}, new ASServerTypeCondition());
>
> public static final ServerType EAP = new ServerType(
> {code}
> {code:title=https://svn.jboss.org/repos/devstudio/trunk/product/installer/src/panels/com/jboss/jbds/installer/bean/ServerType.java, lines 82-86}
> UNKNOWN_STR,
> "",
> new String[]{"6.0", "5.1", "5.0", "4.3", "4.2", "4.0", "3.2"}, null);
> public String toString() {
> {code}
> What about WildFly (AS 8), SOA-P 6, etc.?
--
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, 10 months
[JBoss JIRA] (TOOLSDOC-343) NeedInfo: Disabling validation to remove/reduce false warnings
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-343?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-343:
-------------------------------------
Assignee: Michelle Murray (was: Alexey Kazakov)
> NeedInfo: Disabling validation to remove/reduce false warnings
> --------------------------------------------------------------
>
> Key: TOOLSDOC-343
> URL: https://issues.jboss.org/browse/TOOLSDOC-343
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - JSF Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
>
> I came across: http://docs.jboss.org/tools/whatsnew/jst/jst-news-3.3.0.M5.html
> It states:
> 1) JSF @FacesConverter validation: faces converter validation is an issue in eclipse
> 2) Configuring Problem Severity via Quick Fix: problems if you use CDI programatically or you use CDI components that are not detectable by the tooling
> *Are these instances of validation still issues?*
> I tested (1) with <f:converter converterID="test"></f:converter> and didn't get any error or warning messages so thought it might be fixed in eclipse. Not sure how to test CDI yet (haven't got to that chapter!).
--
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, 10 months