[JBoss JIRA] (JBTIS-386) Target Platform is missing some source plugins when generating with sources
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-386?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-386:
----------------------------------
I've built this locally as well. I'm not adding this to 4.2.1 since I need to go .Final asap. As soon as 4.2.1.Final IS target platform is released - I'll add this to 4.2.2 (either Beta1 or CR1 since the B*MS release will be coming up).
> Target Platform is missing some source plugins when generating with sources
> ---------------------------------------------------------------------------
>
> Key: JBTIS-386
> URL: https://issues.jboss.org/browse/JBTIS-386
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.0.Final-TP
> Reporter: Lars Heinemann
> Assignee: Paul Leacu
> Priority: Critical
>
> when mirroring the TP locally with sources some of the source plugins are missing. for instance org.eclipse.wst.server.ui.source.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19189) NullPointerException in TablePropertiesBlock.doAdd
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19189?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19189:
---------------------------------------
[~koen.aers], can you take a look?
> NullPointerException in TablePropertiesBlock.doAdd
> --------------------------------------------------
>
> Key: JBIDE-19189
> URL: https://issues.jboss.org/browse/JBIDE-19189
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.2.Final
> Environment: eclipse.buildId=4.4.1.M20140925-0400
> java.version=1.8.0_31
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
> Command-line arguments: -os win32 -ws win32 -arch x86_64
> Reporter: Michael Kolowicz
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
>
> I want to develop a small prototype of a application. I have create a database on MySQL 5.6 on a remote server. They have only 1 table (It´s like a easy prototype). The table have a Id-column.
> I using the eclipse 4.4.1 (on Windows 7 x64 - german), Hibernate 4.3.8, Hibernate Tools 4.0.0 (Final).
> Installation is a fresh downloaded eclipse with all actual updates. In the application is added the JDBC for MySQL and the Hibernate-Core Files.
> BTW: If i use Eclipse 4.3 with the same database, then the columns can be added an no error come up.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19194) FeedHenry requires minimal-json, but it was removed from TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19194?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19194:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/127, https://github.com/jbosstools/jbosstools-target-platforms/pull/129 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/127, https://github.com/jbosstools/jbosstools-target-platforms/pull/128)
> FeedHenry requires minimal-json, but it was removed from TP
> -----------------------------------------------------------
>
> Key: JBIDE-19194
> URL: https://issues.jboss.org/browse/JBIDE-19194
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it.
> But turns out that Feedhenry (Aerogear) also needs minimal-json.
> So... we need to add that plugin back into the TPs, and make sure that the version we include works with both Aerogear/FeedHenry (0.9.2, same code base in both 4.2.3 and 4.3.0, currently) and JST/Tern (0.9.1 in JBT 4.2, 0.9.2 in JBT 4.3).
> [~maxandersen] [~gercan] [~dgolovin] [~akazakov]
> In JBT 4.2.0-2 we include Tern 0.6 and minimal-json 0.9.1.
> In JBT 4.2.3 we include Tern 0.7 and minimal-json 0.9.1.
> In JBT 4.3.0 we _currently_ include Tern 0.8 and minimal-json 0.9.2.
> Which version should we include in the target platforms for JBT 4.2.3 (4.42.0.Beta1) and JBT 4.3.0 (4.50.0.Alpha1) ?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19194) FeedHenry requires minimal-json, but it was removed from TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19194?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-19194 at 2/10/15 9:36 AM:
-----------------------------------------------------------------
PR for 4.41.x branch: https://github.com/jbosstools/jbosstools-target-platforms/pull/129
was (Author: mickael_istria):
PR for 4.41.x branch: https://github.com/jbosstools/jbosstools-target-platforms/pull/128
> FeedHenry requires minimal-json, but it was removed from TP
> -----------------------------------------------------------
>
> Key: JBIDE-19194
> URL: https://issues.jboss.org/browse/JBIDE-19194
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it.
> But turns out that Feedhenry (Aerogear) also needs minimal-json.
> So... we need to add that plugin back into the TPs, and make sure that the version we include works with both Aerogear/FeedHenry (0.9.2, same code base in both 4.2.3 and 4.3.0, currently) and JST/Tern (0.9.1 in JBT 4.2, 0.9.2 in JBT 4.3).
> [~maxandersen] [~gercan] [~dgolovin] [~akazakov]
> In JBT 4.2.0-2 we include Tern 0.6 and minimal-json 0.9.1.
> In JBT 4.2.3 we include Tern 0.7 and minimal-json 0.9.1.
> In JBT 4.3.0 we _currently_ include Tern 0.8 and minimal-json 0.9.2.
> Which version should we include in the target platforms for JBT 4.2.3 (4.42.0.Beta1) and JBT 4.3.0 (4.50.0.Alpha1) ?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19194) FeedHenry requires minimal-json, but it was removed from TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19194?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19194:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/127, https://github.com/jbosstools/jbosstools-target-platforms/pull/128 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/127)
PR for 4.41.x branch: https://github.com/jbosstools/jbosstools-target-platforms/pull/128
> FeedHenry requires minimal-json, but it was removed from TP
> -----------------------------------------------------------
>
> Key: JBIDE-19194
> URL: https://issues.jboss.org/browse/JBIDE-19194
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it.
> But turns out that Feedhenry (Aerogear) also needs minimal-json.
> So... we need to add that plugin back into the TPs, and make sure that the version we include works with both Aerogear/FeedHenry (0.9.2, same code base in both 4.2.3 and 4.3.0, currently) and JST/Tern (0.9.1 in JBT 4.2, 0.9.2 in JBT 4.3).
> [~maxandersen] [~gercan] [~dgolovin] [~akazakov]
> In JBT 4.2.0-2 we include Tern 0.6 and minimal-json 0.9.1.
> In JBT 4.2.3 we include Tern 0.7 and minimal-json 0.9.1.
> In JBT 4.3.0 we _currently_ include Tern 0.8 and minimal-json 0.9.2.
> Which version should we include in the target platforms for JBT 4.2.3 (4.42.0.Beta1) and JBT 4.3.0 (4.50.0.Alpha1) ?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19217) org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-19217:
------------------------------------
Summary: org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
Key: JBIDE-19217
URL: https://issues.jboss.org/browse/JBIDE-19217
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.3.0.Alpha1
Environment: JBDS Version: 9.0.0.Alpha1 nightly build
Build id: Alpha1-v20150204-0904-B2748
Build date: 20150204-0904
Reporter: Jiri Peterka
Priority: Blocker
While using Hibernate console in maven project
{code}
org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:132)
at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator$1$1.convert(BasicConnectionCreator.java:118)
at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.convertSqlException(BasicConnectionCreator.java:140)
at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:54)
at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.createConnection(BasicConnectionCreator.java:75)
at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl.configure(DriverManagerConnectionProviderImpl.java:106)
at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178)
at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:80)
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2442)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2434)
at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSettings(ConfigurationProxy.java:125)
at org.hibernate.console.ConsoleConfiguration$6.execute(ConsoleConfiguration.java:438)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
at org.hibernate.console.ConsoleConfiguration.getSettings(ConsoleConfiguration.java:436)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:129)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:125)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:233)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.sql.SQLException: No suitable driver found for jdbc:h2:tcp://localhost/sakila
at java.sql.DriverManager.getConnection(DriverManager.java:689)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:51)
... 26 more
{code}
Pom.xml
{code}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.jboss.tools.hibernate.ui.bot.test</groupId>
<artifactId>mvn-hibernate43</artifactId>
<version>0.0.1-SNAPSHOT</version>
<dependencies>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-core</artifactId>
<version>4.3.0.Final</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-entitymanager</artifactId>
<version>4.3.0.Final</version>
</dependency>
<dependency>
<groupId>org.hibernate.javax.persistence</groupId>
<artifactId>hibernate-jpa-2.1-api</artifactId>
<version>1.0.0.Final</version>
</dependency>
<dependency>
<groupId>com.h2database</groupId>
<artifactId>h2</artifactId>
<version>1.3.161</version>
</dependency>
</dependencies>
</project>
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19217) org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19217?page=com.atlassian.jira.plugi... ]
Jiri Peterka updated JBIDE-19217:
---------------------------------
Fix Version/s: 4.3.0.Alpha1
> org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-19217
> URL: https://issues.jboss.org/browse/JBIDE-19217
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS Version: 9.0.0.Alpha1 nightly build
> Build id: Alpha1-v20150204-0904-B2748
> Build date: 20150204-0904
> Reporter: Jiri Peterka
> Priority: Blocker
> Fix For: 4.3.0.Alpha1
>
>
> While using Hibernate console in maven project
> {code}
> org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
> at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:132)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator$1$1.convert(BasicConnectionCreator.java:118)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.convertSqlException(BasicConnectionCreator.java:140)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:54)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.createConnection(BasicConnectionCreator.java:75)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl.configure(DriverManagerConnectionProviderImpl.java:106)
> at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178)
> at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
> at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
> at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178)
> at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:80)
> at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2442)
> at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2434)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSettings(ConfigurationProxy.java:125)
> at org.hibernate.console.ConsoleConfiguration$6.execute(ConsoleConfiguration.java:438)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.getSettings(ConsoleConfiguration.java:436)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:129)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:125)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:233)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.sql.SQLException: No suitable driver found for jdbc:h2:tcp://localhost/sakila
> at java.sql.DriverManager.getConnection(DriverManager.java:689)
> at java.sql.DriverManager.getConnection(DriverManager.java:208)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:51)
> ... 26 more
> {code}
> Pom.xml
> {code}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.jboss.tools.hibernate.ui.bot.test</groupId>
> <artifactId>mvn-hibernate43</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <dependencies>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-core</artifactId>
> <version>4.3.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-entitymanager</artifactId>
> <version>4.3.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate.javax.persistence</groupId>
> <artifactId>hibernate-jpa-2.1-api</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>com.h2database</groupId>
> <artifactId>h2</artifactId>
> <version>1.3.161</version>
> </dependency>
> </dependencies>
> </project>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18983) Project cannot be built. Possible open file handle
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18983?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-18983:
-----------------------------------
Component/s: maven
(was: build)
(was: updatesite)
> Project cannot be built. Possible open file handle
> --------------------------------------------------
>
> Key: JBIDE-18983
> URL: https://issues.jboss.org/browse/JBIDE-18983
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, maven
> Affects Versions: 4.2.1.Final
> Environment: luna x64 windows 8.1 x64
> java 8u25 x64
> Reporter: Cody Lerum
> Assignee: Nick Boldt
> Fix For: 4.2.x, 4.3.x
>
>
> Frequently when working in a Java EE7 project I will get an error like.
> "The project was not built due to "Could not delete '/gp-server/target/classes/META-INF`.". Fix the problem, then try refreshing this project and building since it may be inconsistent.
> I've looked into a process explorer in windows and then this case is happening there is always a javaw.exe process with a file handle to "V:\workspace\gp-server\target\classes\META-INF\persistence.xml
> It looks like either jboss tools or eclipse is holding on to a file handle for this.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18983) Project cannot be built. Possible open file handle
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18983?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-18983:
--------------------------------------
Assignee: (was: Nick Boldt)
> Project cannot be built. Possible open file handle
> --------------------------------------------------
>
> Key: JBIDE-18983
> URL: https://issues.jboss.org/browse/JBIDE-18983
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, maven
> Affects Versions: 4.2.1.Final
> Environment: luna x64 windows 8.1 x64
> java 8u25 x64
> Reporter: Cody Lerum
> Fix For: 4.2.x, 4.3.x
>
>
> Frequently when working in a Java EE7 project I will get an error like.
> "The project was not built due to "Could not delete '/gp-server/target/classes/META-INF`.". Fix the problem, then try refreshing this project and building since it may be inconsistent.
> I've looked into a process explorer in windows and then this case is happening there is always a javaw.exe process with a file handle to "V:\workspace\gp-server\target\classes\META-INF\persistence.xml
> It looks like either jboss tools or eclipse is holding on to a file handle for this.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months