[JBoss JIRA] (JBIDE-18983) Project cannot be built. Possible open file handle
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18983?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18983:
-------------------------------
Sprint: devex #128 February 2018
> 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: Jeff MAURY
> Fix For: 4.4.4.AM1
>
>
> 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
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22362:
-------------------------------------
Fix Version/s: 4.4.4.AM1
(was: 4.4.3.Final)
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.4.AM1
>
> Attachments: enabling-dev-mode-has-encountered-an-error.png
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBTIS-1032) Drools - Fix failing smoke tests
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1032?page=com.atlassian.jira.plugin... ]
Tomas David commented on JBTIS-1032:
------------------------------------
The problem was that smoke and verification jenkins jobs have {{skipRequirements}} set to true and it causes that drools runtime was not downloaded.
I removed the tests which using runtime downloading from smoke tests suite.
> Drools - Fix failing smoke tests
> --------------------------------
>
> Key: JBTIS-1032
> URL: https://issues.jboss.org/browse/JBTIS-1032
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: drools/ jBPM, QE
> Affects Versions: 4.4.0.Final
> Reporter: Andrej Podhradsky
> Assignee: Tomas David
> Fix For: 10.1.0.GA
>
> Attachments: archive.zip
>
>
> Please see the attached zip file which contains all reports and screenshots
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month