[jbosstools-issues] [JBoss JIRA] (JBIDE-15139) Deployment assembly fileset ignores classes on "subpackages"

Fri Jul 5 18:46:21 EDT 2013

    [ https://issues.jboss.org/browse/JBIDE-15139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787984#comment-12787984 ] 

Renato Garcia commented on JBIDE-15139:
---------------------------------------

I tested the same as above and I can confirm that using project archives also works for me. I tried to use the project archives as a workaround for this issue but I could not figure out a way of doing it.

The scenario I have, which is demonstrated in the project attached, is an EJB Project configured with a fileset deployment assembly from a Java Project so that the classes from the Java Project gets deployed to the EJB Project.

Please let me know if I can provide any additional info.

> Deployment assembly fileset ignores classes on "subpackages"
> ------------------------------------------------------------
>
>                 Key: JBIDE-15139
>                 URL: https://issues.jboss.org/browse/JBIDE-15139
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.0.0.Final, 4.1.0.Beta2
>         Environment: Linux 3.8.2-pf #15 SMP Sun Apr 7 18:07:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.7.0_21"
> OpenJDK Runtime Environment (IcedTea 2.3.9) (7u21-2.3.9-1ubuntu1ppa1)
> OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
> Eclipse Juno SR2/ Kepler
>            Reporter: Renato Garcia
>             Fix For: 4.1.0.CR1
>
>         Attachments: sample-project.zip
>
>
> The fileset deployment assembly is ignoring classes that are inside packages with empty directories. 
> For instance:
> a.Foo -> OK
> a.b.c.Bar -> NOT WORKING!
> If you add a file to a.b directory it will deploy Bar class.
> Attached the sample project that shows the error.
> It works on Helios but not on Juno and Kepler and their respective JBoss tools versions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira