October 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6231) New Seam Project Wizard should not deploy project automatically

by Dominik Pospisil (JIRA)

New Seam Project Wizard should not deploy project automatically --------------------------------------------------------------- Key: JBIDE-6231 URL: https://jira.jboss.org/jira/browse/JBIDE-6231 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.GA Reporter: Dominik Pospisil Assignee: Alexey Kazakov New Seam Project Wizard automatically deploys created project on target server. This feature is incosistent with DynamicWebProject wizard and should be considered to be removed. -- 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

15 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-1177) .metadata deploy issues

by Brice Ruth (JIRA)

.metadata deploy issues ----------------------- Key: JBDS-1177 URL: https://jira.jboss.org/jira/browse/JBDS-1177 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Environment: WinXP SP2, jdk1.5.0_13, eclipse-jee-galileo-sr2, jboss_tools 3.1 final, m2e 0.10 Reporter: Brice Ruth >From #JbossTools on IRC: [11:07] <bruth> Another issue: apparently when I change from the default of deploying to .metadata to using the JBoss deploy/ folder, two things don't happen, (1) the files aren't cleaned out from .metadata and (2) the references that tell the JBoss instance to deploy things in the .metadata folder aren't removed, so JBoss starts, deploys from deploy/ then also tries to deploy from .metadata, generating all sorts of duplicate MBean errors -- 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

15 years, 1 month

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6102) Server deployment status synchronization improvements

by Dominik Pospisil (JIRA)

Server deployment status synchronization improvements ----------------------------------------------------- Key: JBIDE-6102 URL: https://jira.jboss.org/jira/browse/JBIDE-6102 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Dominik Pospisil Assignee: Rob Stryker Fix For: 3.2.next I can see couple of ways how the project deployment status could be improved. 1) Currently, project deployment status could get easily out of sync. Once the JBT successfully initiates project deployment, it always assumes that the deployment was successful. JBT does not detect deployment failures and If something went wrong it gets out of sync. JBT should check deployment result. Also, when a project is manually undeployed / deployed from the server the change is not picked up by JBT. 2) The server view only displays deployments managed by JBT within current workspace. It would be nice if the user has an overview of projects/applications/resources deployed in different workspaces or externally. It would be really handy e.g. when a user often switches workspaces, deploy various project in different workspaces. It could prevent a user of being confused what actually is or is not deployed. -- 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

15 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6156) Exceptions in Seam Wizard under unusual circumstances

by Rob Stryker (JIRA)

Exceptions in Seam Wizard under unusual circumstances ----------------------------------------------------- Key: JBIDE-6156 URL: https://jira.jboss.org/jira/browse/JBIDE-6156 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.GA Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.next, 3.6-Helios https://bugs.eclipse.org/bugs/show_bug.cgi?id=303317 Fixed this bug upstream but not sure if they'll accept the patch ;) I'm not sure if there's already a bug here for it but I'll dup it if there is. Build Identifier: I20090528-2000 Path for project must have only one segment. java.lang.IllegalArgumentException: Path for project must have only one segment. at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) at org.eclipse.core.internal.resources.WorkspaceRoot.getProject(WorkspaceRoot.java:181) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.getFacetedProject(FacetedProjectWorkingCopy.java:428) at org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate.refresh(LibraryInstallDelegate.java:376) at org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate$2.handleEvent(LibraryInstallDelegate.java:132) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.notifyListeners(FacetedProjectWorkingCopy.java:1690) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.resumeEventNotification(FacetedProjectWorkingCopy.java:1735) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.setTargetedRuntimes(FacetedProjectWorkingCopy.java:1237) at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.setRuntimeAndDefaultFacets(SeamProjectWizard.java:222) at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard$2.propertyChanged(NewProjectDataModelFacetWizard.java:215) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyListeners(DataModelImpl.java:346) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyPropertyChange(DataModelImpl.java:337) Reproducible: Always Steps to Reproduce: EXECUTE: New dynamic web project. EXECUTE: Input project name "test2/2" ASSERT: Warning, related to incorrect project name appears. EXECUTE: Change Server runtime FAILURE: Two same exceptions thrown in error log each time, when runtime changes. -- 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

15 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6215) 5 ASTestSuite tests failing for last 4 builds

by Nick Boldt (JIRA)

5 ASTestSuite tests failing for last 4 builds ----------------------------------------------- Key: JBIDE-6215 URL: https://jira.jboss.org/jira/browse/JBIDE-6215 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.next Reporter: Nick Boldt Assignee: Rob Stryker These tests have been failing for the last 4 builds: ASTestSuite.testEar5WithJBoss42 ASTestSuite.testEar5WithJBoss50 ASTestSuite.testEar5WithJBoss51 ASTestSuite.testMain ASTestSuite.testMain http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.2.next/lastCom... -- 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

15 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6057) Shouldn't "deploy in workspace" be using the "standard" servers projects from WTP

by Max Rydahl Andersen (JIRA)

Shouldn't "deploy in workspace" be using the "standard" servers projects from WTP --------------------------------------------------------------------------------- Key: JBIDE-6057 URL: https://jira.jboss.org/jira/browse/JBIDE-6057 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.2.next When using Tomcat server in WTP the deployment is stored in the WTP Servers Project which seems to make much more sense than somewhere hidden inside eclipse preferences/settings storage ? -- 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

15 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5983) [SPRING CLEAN] Remove useless codes from Smooks tools projects.

by Xue Peng (JIRA)

[SPRING CLEAN] Remove useless codes from Smooks tools projects. --------------------------------------------------------------- Key: JBIDE-5983 URL: https://jira.jboss.org/jira/browse/JBIDE-5983 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0.CR2 Reporter: Xue Peng Assignee: Xue Peng Remove useless codes from Smooks tools projects. -- 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

15 years, 1 month

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-6045) import more samples from riftsaw samples

by Feng Qian (JIRA)

import more samples from riftsaw samples ---------------------------------------- Key: JBIDE-6045 URL: https://jira.jboss.org/jira/browse/JBIDE-6045 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Affects Versions: 3.1.0.CR2 Reporter: Feng Qian Fix For: 3.2.next Now we have two project samples from riftsaw. They are not enough for user. We should import more samples from Riftsaw. -- 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

15 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5931) Renamaing deployed project on running server results in the project to be deployed twice

by Dominik Pospisil (JIRA)

Renamaing deployed project on running server results in the project to be deployed twice ---------------------------------------------------------------------------------------- Key: JBIDE-5931 URL: https://jira.jboss.org/jira/browse/JBIDE-5931 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.CR2 Reporter: Dominik Pospisil Assignee: Rob Stryker When a user renames a project deployed on running server, the project remains deployed using original name and an attempt to deploy using new name is made. The project should be undeployed first. If the project contains named resources (datasources, queues, ws...) the second deployment fails. 1) Create Dynamic web project 2) Run the project on server 3) Choose Refactor -> Rename on the project -- 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

15 years, 1 month

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5691) Exported files don't honor the module assembly settings

by Fred Bricon (JIRA)

Exported files don't honor the module assembly settings ------------------------------------------------------- Key: JBIDE-5691 URL: https://jira.jboss.org/jira/browse/JBIDE-5691 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Environment: Vista, eclipse 3.5.1, JBT 3.1.CR1 Reporter: Fred Bricon I'm investigating ways to implement SAR support in m2eclipse (for selfish motivations I agree). A SAR project would need to export dependencies in a lib folder, inside the archive. During my investigation, I tried to use the JBT 3.1.CR1 module assembly page, which would, from my understanding, allow me to reach the desired effect. So I've created sample maven-less projects : -sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The resulting org.eclipse.wst.common.component contains : {noformat} <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="sarproject"> <wb-resource deploy-path="/" source-path="/src"/> <dependent-module archiveName="junit.jar" deploy-path="/" handle="module:/classpath/var/JUNIT_HOME/junit.jar"> <dependency-type>uses</dependency-type> </dependent-module> </wb-module> </project-modules> {noformat} -earproject : needed so sarproject can be a Module project (which totally sucks). I've manually tweaked org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed. Here is the end result : {noformat} <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="earproject"> <wb-resource deploy-path="/" source-path="/EarContent"/> <dependent-module archiveName="sarproject.sar" deploy-path="/" handle="module:/resource/sarproject/sarproject"> <dependency-type>uses</dependency-type> </dependent-module> </wb-module> </project-modules> {noformat} Now, when earproject.ear, there's no junit.jar to be found in sarproject.sar (not expected) nor in the ear (expected). When using export module on sarproject, the resulting file doesn't contain junit.jar either. This looks like a bug I've opened at eclipse's bugzilla for Connector projects : https://bugs.eclipse.org/bugs/show_bug.cgi?id=298735 The module assembly page looks very promising in theory, as it would allow support for any kind of archives (sar, har ...) but from what I understand it's only usable for ear and war projects. This bug should probably be opened at eclipse.org or is totally a duplicate of #298735 (you tell me), but I think the module assembly page should not be visible on unsupported projects. regards, Fred Bricon -- 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

15 years, 1 month

4
15
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2010