[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2743) Deployment of modules in server is messed up
Galder Zamarreno (JIRA)
jira-events at lists.jboss.org
Mon Sep 8 10:53:39 EDT 2008
[ https://jira.jboss.org/jira/browse/JBIDE-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12428603#action_12428603 ]
Galder Zamarreno commented on JBIDE-2743:
-----------------------------------------
Think I found the issue, both archives have the same ModuleIDPropertyKey.
I had manually modified it when creation of Project Archives was completely
broken on one of the nightlies.
Maybe JDBS could throw an error when something like this happens?
> Deployment of modules in server is messed up
> --------------------------------------------
>
> Key: JBIDE-2743
> URL: https://jira.jboss.org/jira/browse/JBIDE-2743
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Archives, JBossAS
> Affects Versions: 3.0.0.alpha
> Reporter: Galder Zamarreno
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 3.0.0.beta1
>
> Attachments: 1.png, 2.png, projects.zip
>
>
> Something very weird is going on here. As you can see from 1.png,
> I've created a 4.3.0.GA server for 216155 configuration and I'm
> deploying build/acme-ejb3.jar there.
> However, when I look at 2.png, it's actually deploying acme-ejb3-jmx.jar
> which in principle, is a superset of acme-ejb3.jar to which I add output from
> a different project (see project archive view in 1.png).
> After inspecting the actual deploy/acme-ejb3-jmx.jar, it's really acme-ejb3-jmx.jar
> and not acme-ejb3.jar renamed differently.
--
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
More information about the jbosstools-issues
mailing list