[JBoss JIRA] Created: (JBIDE-2672) Seam project deletion error.
by Aliaksey Nis (JIRA)
Seam project deletion error.
----------------------------
Key: JBIDE-2672
URL: https://jira.jboss.org/jira/browse/JBIDE-2672
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.0.0.alpha
Environment: WindowsXP SP2
JBoss Tools
Version: 3.0.0.Alpha1
Build id: 200808200023-nightly
Build date: 20 august 2008
JDK 1.5_08
Reporter: Aliaksey Nis
Attachments: SeamDelete.txt
EXECUTE: Create Seam Web EAR project.
EXECUTE: Select all parts of project in package explorer.
EXECUTE: Press Delete. Enable checkbox - delete with content. Press Ok.
FAILURE: Bunch of exceptions thrown in error log.
Error log with one(they are all same) exception attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months
[JBoss JIRA] Created: (JBDS-408) "clean" publish is required to correctly deploy or modify a seam EAR project - a regualr publish will not work
by Jay Balunas (JIRA)
"clean" publish is required to correctly deploy or modify a seam EAR project - a regualr publish will not work
--------------------------------------------------------------------------------------------------------------
Key: JBDS-408
URL: https://jira.jboss.org/jira/browse/JBDS-408
Project: Developer Studio
Issue Type: Bug
Components: seam
Affects Versions: 1.1.0.GA
Environment: fedora 8
jdk 5/6
seam 1.2 or seam 2
Reporter: Jay Balunas
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 2.0.0.alpha
Using: jbds 1.1.GA, EAP 4.3.CP02, FP01 CR3
Added eap as server, and seam 1.2.1 and/or seam 2.0 in feature pack as a seam runtime
Create a seam ear project and publish, I get:
2008-08-29 13:54:17,427 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@f3dca032{ url=file:/jboss/apps/platforms/jboss-eap-4.3.GA_CP02_FP01_CR3/jboss-eap-4.3/jboss-as/server/production/deploy/seamEapEar-ear.ear/, deployedLastModified=0 }
org.jboss.deployment.DeploymentException: url file:/jboss/apps/platforms/jboss-eap-4.3.GA_CP02_FP01_CR3/jboss-eap-4.3/jboss-as/server/production/deploy/seamEapEar-ear.ear/seamEapEar-ejb.jar could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:214)
at org.jboss.deployment.EARDeployer.init(EARDeployer.java:288)
There is not a seamEapEar-ejb.jar directory. The correct items appeared in the server project publish list.
I did a "clean" publish and now there is a "seamEapEar-ejb.jar" directory and the application works from here on out.
This was also required for "New Form" and "New Action" but not generate entities.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months
[JBoss JIRA] Created: (JBIDE-2470) No error announcement when building project archive.
by Edward Pilipczuk (JIRA)
No error announcement when building project archive.
----------------------------------------------------
Key: JBIDE-2470
URL: http://jira.jboss.com/jira/browse/JBIDE-2470
Project: Tools (JBoss Tools)
Issue Type: Bug
Environment: WindowsXP/Intel Core T730 Duo CPU @2GHz / Eclipse Version: 3.3.1.1, Build id: M20071023-1652 /
JBossTools-200806242226-nightly-ALL-win32.zip
Reporter: Edward Pilipczuk
Priority: Minor
Fix For: 2.1.2
Condition: The old archive file (e.g. jar file) is opened exclusively by the other process in windows environment.
When building then the new version of the project archive this task is accomplished silently without compliants.
However the new archive is not created nor the user is warned that the file archive has not been updated with new image on the disk.
Only file timestamp and its size indicates that nothing has changed.
I think that IO exception thrown during file updates shall be reported to the user via popup window.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months