[JBoss JIRA] (JBIDE-14826) Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14826?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-14826.
-------------------------------
> Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime
> ---------------------------------------------------------------------------
>
> Key: JBIDE-14826
> URL: https://issues.jboss.org/browse/JBIDE-14826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2, server
> Affects Versions: 4.0.1.Final
> Environment: JBDS 6.0.1, WFK 2.3.0.ER1 Seam 2.3.1.Final (I guess it's same for the community latest release)
> Reporter: Tomas Remes
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Beta2
>
>
> When you create Seam2.3 project with EAP 6.1.0 (tech preview) runtime, the EAP libraries won't be present on its classpath. This fact cause following problems, when you try to create new Seam form or reverse engineer entities from database:
> "The type javax.validation.ConstraintViolation cannot be resolved. It is indirectly referenced from required .class files"
> "The project was not built since its build path is incomplete. Cannot find the class file for javax.persistence.EntityManager."
--
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, 5 months
[JBoss JIRA] (JBIDE-14379) Seam Web project datasource settings
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14379?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-14379.
-------------------------------
> Seam Web project datasource settings
> ------------------------------------
>
> Key: JBIDE-14379
> URL: https://issues.jboss.org/browse/JBIDE-14379
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Seam 2
> Environment: JBDS 7.0.0.Alpha2, Seam2.3
> Reporter: Tomas Remes
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Beta2
>
>
> I consider default Seam Project wizard and its default datasource settings (especially running on EAP 6) as confusing. I would suggest to have the H2 datasource (there is no hsqldb) as default option at last wizard's dialog. I understand that this is question about Seam and EAP versions. EAP 5 & Seam2.2 is ok with hsqldb, but this is not true when using Seam2.3 & EAP 6.
> Next thing is when I don't specify any other datasource settings, I'll get datasource containing exactly the name of the driver (e.g h2-1.3.168-redhat-1.jar), which is not deployable. Why the default h2 driver (included in standalone.xml config) is not use?
--
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, 5 months
[JBoss JIRA] (JBIDE-15012) Runtime download dialog cannot be stopped
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15012?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15012:
-------------------------------------
> I can't cancel the scan - at least that is how it looks like.
Max: what scan exactly? As far as I know, Fred, Snjezana, and myself, are all testing the download of a runtime, which does not include any scan. In the download runtimes wizard, after selecting a runtime to download, and setting where it should be downloaded to and installed, a progress dialog pops up which tracks the progress of the download of the jboss app-server zip file. It is this dialog which we are testing. Not anything involving a scan (?)
> Runtime download dialog cannot be stopped
> -----------------------------------------
>
> Key: JBIDE-15012
> URL: https://issues.jboss.org/browse/JBIDE-15012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection, server
> Affects Versions: 4.1.0.Beta2
> Environment: OS X Mountain Lion
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.1.Final
>
>
> Go to Preferences -> JBoss Tools -> Runtime detection
> and try to download a runtime using the Download button.
> While the runtime is downloading, press Cancel/Stop to abort the download. Nothing will happen (at least in my case).
--
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, 5 months
[JBoss JIRA] (JBIDE-13040) Enable individual emails in Jenkins based on Git changes
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13040?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13040 at 6/30/13 9:20 PM:
-------------------------------------------------------------
[~mickael_istria] is this fixed now? I assume we've restarted at least once since Jun 3, right [~vjuranek] (If so, please make sure to set a proper fixversion instead of the current 4.1.x/4.2.x to avoid the wrath of jira-lint.)
was (Author: nickboldt):
[~mickael_istria] is this fixed now? I assume we've restarted at least once since Jun 3, right [~vjuranek] ?
> Enable individual emails in Jenkins based on Git changes
> --------------------------------------------------------
>
> Key: JBIDE-13040
> URL: https://issues.jboss.org/browse/JBIDE-13040
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.1.x, 4.2.x
>
>
> Now we have moved to Git, we can probably re-enable individual mailing from Jenkins. Previous issue appeared to be an issue with SVN plugin, which we don't use any longer.
--
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, 5 months