11:01 a.m.
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Alexey Kazakov
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:37 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen reassigned JBIDE-6596:
------------------------------------------
Assignee: Rob Stryker (was: Alexey Kazakov)
Why are we still seeing this on Eclipse 3.6 ?
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.2.0.M1
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:37 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen updated JBIDE-6596:
---------------------------------------
Fix Version/s: 3.2.0.M1
Priority: Blocker (was: Major)
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.M1
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:50 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Bernhard Hurzeler commented on JBIDE-6596:
------------------------------------------
I investigated this a little and found that this probably due to that fact that the
deployer looks at the maven librarys (jboss-seam.jar) and sees that it has jar or ejb
packaging and therefore puts it in a directory.
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.M1
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:30 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen commented on JBIDE-6596:
--------------------------------------------
maven library ? Care to explain a bit ? There is no maven involved in this plain seam war
project deploy ?
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.M1
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:44 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Bernhard Hurzeler commented on JBIDE-6596:
------------------------------------------
Yes certainly. Try to create a seam/maven project and you will find a very similar issue
as was reported by Dominik. First the jboss-seam.jar is put in a folder and secondly maven
libraries that are marked as packaging jar or ejb gets put in a jar file of the same name
i.e. some.jar is jared in a file called some.jar. Hence as a consequence the classes
can't be found and the war is not working properly. I suspect that this is the same
issue as Dominik reported.
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.M1
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:16 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen updated JBIDE-6596:
---------------------------------------
Assignee: Denis Golovin (was: Rob Stryker)
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Denis Golovin
Priority: Blocker
Fix For: 3.2.0.M1
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:54 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Denis Golovin resolved JBIDE-6596.
----------------------------------
Fix Version/s: 3.2.0.M2
3.2.x
Resolution: Done
I can confirm that this issue is replicated without patch and is not with patch.
Fixed in M1 branch and trunk.
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Denis Golovin
Priority: Blocker
Fix For: 3.2.0.M1, 3.2.0.M2, 3.2.x
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:27 a.m.
New subject: [JBoss JIRA] Reopened: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Vlado Pakan reopened JBIDE-6596:
--------------------------------
Tested on jbosstools-3.2.0.M1.continuous-Update-2010-07-15_23-42-21-H151 linux 32 bit Java
Sun JDK 1.6 and it doesn't work.
File jboss-seam.jar is now deployed in main directory of .war file i.e.
<seamwarproject.war>/jboss-seam.jar and it has to be in
<seamwarproject.war>/WEB-INF/lib/jboss-seam.jar.
Seam project is not deployed and there is this error in server log and some more. This is
the first one:
11:24:20,296 ERROR [[/seamwartest]] Error configuring application listener of class
org.jboss.seam.servlet.SeamListener
java.lang.ClassNotFoundException: org.jboss.seam.servlet.SeamListener
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at
org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:262)
at
org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:256)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3859)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4389)
at
org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
at
org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142)
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
at $Proxy38.start(Unknown Source)
at
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
at
org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at
org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:297)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.start(ServiceController.java:460)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1440)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1158)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1099)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:782)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at
org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Denis Golovin
Priority: Blocker
Fix For: 3.2.0.M1, 3.2.0.M2, 3.2.x
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:40 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Denis Golovin resolved JBIDE-6596.
----------------------------------
Resolution: Done
Patch below has been applied to trunk and M1 branch. Both EAR and WAR seam projects works
out of the box now.
Index: jbosscore/org/jboss/ide/eclipse/as/core/publishers/JstPublisher.java
===================================================================
--- jbosscore/org/jboss/ide/eclipse/as/core/publishers/JstPublisher.java (revision 23424)
+++ jbosscore/org/jboss/ide/eclipse/as/core/publishers/JstPublisher.java (working copy)
@@ -117,12 +117,12 @@
if( !(new Path(module.getName()).segmentCount() > 1 ) && delete)
list.addAll(Arrays.asList(localSafeDelete(deployPath)));
- if( !deployPackaged(moduleTree) && !isBinaryObject(moduleTree)) {
+ if( !deployPackaged(moduleTree) && !j2eeModule.isBinary()) {
LocalCopyCallback handler = new LocalCopyCallback(server.getServer(), deployPath,
tempDeployPath);
PublishCopyUtil util = new PublishCopyUtil(handler);
list.addAll(Arrays.asList(util.publishFull(members, monitor)));
}
- else if( isBinaryObject(moduleTree))
+ else if(j2eeModule.isBinary())
list.addAll(Arrays.asList(copyBinaryModule(moduleTree)));
else
list.addAll(Arrays.asList(packModuleIntoJar(moduleTree[moduleTree.length-1],
deployPath)));
@@ -152,12 +152,13 @@
IStatus[] results = new IStatus[] {};
IPath deployPath = getDeployPath(moduleTree, server);
IPath tempDeployPath = getTempDeployFolder(moduleTree, server);
+ IJ2EEModule j2eeModule = (IJ2EEModule) module.loadAdapter(IJ2EEModule.class, null);
LocalCopyCallback handler = null;
- if( !deployPackaged(moduleTree) && !isBinaryObject(moduleTree)) {
+ if( !deployPackaged(moduleTree) && !j2eeModule.isBinary()) {
handler = new LocalCopyCallback(server.getServer(), deployPath, tempDeployPath);
results = new PublishCopyUtil(handler).publishDelta(delta, monitor);
} else if( delta.length > 0 ) {
- if( isBinaryObject(moduleTree))
+ if( j2eeModule.isBinary())
results = copyBinaryModule(moduleTree);
else
results = packModuleIntoJar(moduleTree[moduleTree.length-1], deployPath);
Index: jbosscore/org/jboss/ide/eclipse/as/core/publishers/PublishUtil.java
===================================================================
--- jbosscore/org/jboss/ide/eclipse/as/core/publishers/PublishUtil.java (revision 23424)
+++ jbosscore/org/jboss/ide/eclipse/as/core/publishers/PublishUtil.java (working copy)
@@ -129,9 +129,6 @@
String type, modName, name, uri, suffixedName;
for( int i = 0; i < moduleTree.length; i++ ) {
IJ2EEModule j2eeModule = (IJ2EEModule) moduleTree[i].loadAdapter(IJ2EEModule.class,
null);
- if (j2eeModule != null && j2eeModule.isBinary()) {
- continue;
- }
type = moduleTree[i].getModuleType().getId();
modName = moduleTree[i].getName();
name = new Path(modName).lastSegment();
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Denis Golovin
Priority: Blocker
Fix For: 3.2.0.M1, 3.2.0.M2, 3.2.x
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:36 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Libor Zoubek closed JBIDE-6596.
-------------------------------
verified (war and ear) on JBDS 4.0.0.v201007192217R-H398-M1
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Denis Golovin
Priority: Blocker
Fix For: 3.2.0.M1, 3.2.0.M2, 3.2.x
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:11 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Denis Golovin updated JBIDE-6596:
---------------------------------
Fix Version/s: (was: 3.2.x)
(was: 3.2.0.M2)
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Denis Golovin
Priority: Blocker
Fix For: 3.2.0.M1
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:13 p.m.
New subject: [JBoss JIRA] Closed: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Denis Golovin closed JBIDE-6596.
--------------------------------
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Denis Golovin
Priority: Blocker
Fix For: 3.2.0.M1
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:13 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6596) New Seam WAR project has incorrect deployment artifact structure
[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Denis Golovin resolved JBIDE-6596.
----------------------------------
Resolution: Done
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL: https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Denis Golovin
Priority: Blocker
Fix For: 3.2.0.M1
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5682
days inactive
5751
days old
jbosstools-issues@lists.jboss.org
13 comments
6 participants
participants (6)
-
Bernhard Hurzeler (JIRA) -
Denis Golovin (JIRA)
-
Dominik Pospisil (JIRA)
-
Libor Zoubek (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Vlado Pakan (JIRA)