[JBoss JIRA] (JBIDE-13900) Update Integration Tests to support latest EAP 6.0.x and 6.1.0.x
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13900?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-13900:
-------------------------------------
Assigning to Len so he can dispatch to whomever is best fit to check jbosstools-integration-tests
[~rob.stryker] : what's your take on org.jboss.tools.as.test.core ?
> Update Integration Tests to support latest EAP 6.0.x and 6.1.0.x
> ----------------------------------------------------------------
>
> Key: JBIDE-13900
> URL: https://issues.jboss.org/browse/JBIDE-13900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, server
> Affects Versions: 4.0.2.Final, 4.2.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 4.1.1.Final
>
>
> Found test classes which refer to JBEAP 6.0 and/or 6.1. They should be updated to refer to the latest 6.0.x AND new 6.1.0.x bits, so both are available for testing.
> {code:title=contains ref to only 6.0. Should it contain 6.1 too?}
> jbosstools-integration-tests/tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml
> jbosstools-integration-tests/tests/org.jboss.tools.central.test.ui.bot/pom.xml{code}
> {code:title=contains refs to both 6.0 and 6.1}
> jbosstools-server/as/tests/org.jboss.tools.as.test.core/pom.xml{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
12 years, 6 months
[JBoss JIRA] (JBIDE-13900) Update Integration Tests to support latest EAP 6.0.x and 6.1.0.x
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13900?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-13900:
--------------------------------
Assignee: Len DiMaggio
> Update Integration Tests to support latest EAP 6.0.x and 6.1.0.x
> ----------------------------------------------------------------
>
> Key: JBIDE-13900
> URL: https://issues.jboss.org/browse/JBIDE-13900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, server
> Affects Versions: 4.0.2.Final, 4.2.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 4.1.1.Final
>
>
> Found test classes which refer to JBEAP 6.0 and/or 6.1. They should be updated to refer to the latest 6.0.x AND new 6.1.0.x bits, so both are available for testing.
> {code:title=contains ref to only 6.0. Should it contain 6.1 too?}
> jbosstools-integration-tests/tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml
> jbosstools-integration-tests/tests/org.jboss.tools.central.test.ui.bot/pom.xml{code}
> {code:title=contains refs to both 6.0 and 6.1}
> jbosstools-server/as/tests/org.jboss.tools.as.test.core/pom.xml{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
12 years, 6 months
[JBoss JIRA] (JBIDE-15639) Support running on Eclipse Luna M2 (4.4.M2) platform
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15639?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15639:
----------------------------------------
Description:
Luna M2 has been released, with already a few changes available. We should investigate the effort of moving current master from Kepler to Luna.
As Target Platform 4.40.0.Alpha1-SNAPSHOT is now based on Luna, it is easy to try a build for a given component with
{code}mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT{code}
If you component has new compilation or test failure, you should report them as a Jira and make it a dependency of this Jira.
WTP API Migration: http://wiki.eclipse.org/New_Help_for_Old_Friends_IX
Eclipse core: Not published yet.
was:
Luna M2 has been released, with already a few changes available. We should investigate the effort of moving current master from Kepler to Luna.
As Target Platform 4.40.0.Alpha1-SNAPSHOT is now based on Luna, it is easy to try a build for a given component with
{code}mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT{code}
If you component has new compilation or test failure, you should report them as a Jira and make it a dependency of this Jira.
> Support running on Eclipse Luna M2 (4.4.M2) platform
> ----------------------------------------------------
>
> Key: JBIDE-15639
> URL: https://issues.jboss.org/browse/JBIDE-15639
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, target-platform, updatesite
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
>
> Luna M2 has been released, with already a few changes available. We should investigate the effort of moving current master from Kepler to Luna.
> As Target Platform 4.40.0.Alpha1-SNAPSHOT is now based on Luna, it is easy to try a build for a given component with
> {code}mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT{code}
> If you component has new compilation or test failure, you should report them as a Jira and make it a dependency of this Jira.
> WTP API Migration: http://wiki.eclipse.org/New_Help_for_Old_Friends_IX
> Eclipse core: Not published yet.
--
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, 6 months
[JBoss JIRA] (JBIDE-15143) Eclipse is not running newly created forge web project
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15143?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-15143:
------------------------------
Fix Version/s: 4.2.0.Alpha1
4.1.1.Beta1
> Eclipse is not running newly created forge web project
> ------------------------------------------------------
>
> Key: JBIDE-15143
> URL: https://issues.jboss.org/browse/JBIDE-15143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.1.0.Beta2
> Environment: Windows XP, Eclipse Kepler, Forge 1.3.2, Maven 3
> Reporter: Rajmahendra Hegde
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
> Attachments: 15143-app-launched.png, 15143-installing.png, 15143-mark-deployable-not-needed.png, 15143-pick-server.png, 15143-servers-view.png, EclipseJBossTools.PNG
>
>
> I created a new forge project in Eclipse forge plugin
> run scaffold to create a JSF project and when i right click the project i don't see Run as Server. I see a option of make as deplorable . its also not working.
--
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, 6 months
[JBoss JIRA] (JBIDE-15204) New Project wizard hangs when an invalid package is provided as input.
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15204?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-15204:
------------------------------
Fix Version/s: 4.2.0.Alpha1
4.1.1.Beta1
> New Project wizard hangs when an invalid package is provided as input.
> ----------------------------------------------------------------------
>
> Key: JBIDE-15204
> URL: https://issues.jboss.org/browse/JBIDE-15204
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.1.0.Beta2
> Reporter: Vineet Reynolds
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
> Attachments: eclipse-threaddump-1373927608559.tdump, forge-threaddump-1373927611426.tdump
>
>
> The new project wizard hangs when an invalid package name (according to Forge) is provided in the dialog box. On clicking the Finish button in the wizard, it hangs when running the {{new-project ....}} Forge command.
> This is due to Forge waiting for the user to supply a valid package name. See attached thread dumps.
> Other comments:
> In a way, this is related to FORGE-687, but the fix should probably go into the wizard so users can correct the name instead of Forge deciding on a default.
--
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, 6 months