[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder

[Eric B (JIRA)]

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

Eric B commented on JBIDE-9778:
-------------------------------

I have the following version installed:
JBoss by Red Hat: Maven Integration for Eclipse WTP : 0.13.1.20110728-1800 : org.maven.ide.eclipse.wtp

Yes - I have tried Maven->Update Project on the webapp project as well as the Java project but to no avail.  Same issue still remains.

I am deploying to JBoss 6.1, but using the JBoss 6.0 template/plugin since there is no 6.1 plugin available.

I am attaching the 3 different poms along with the .project and .classpath files for each.  Please let me know if you need additional config information.  I have removed the <parent> tags in all three poms as I don't expect that you would have much interest in them, but all 3 projects all point to the same parent pom.  Finally, for simplicity sake, I am only attaching 3 sets of files even though the structure has deeper nesting as well (ie: my configuration library also depends on another project, as well as my server project also depending on another nested library, which in turns depends on the configuration library, etc...).  If you need a more thorough structure, please let me know and I can provide that.

Thanks,

Eric

> Maven embedded projects are not properly generated as jars in the deploy folder
> -------------------------------------------------------------------------------
>
>                 Key: JBIDE-9778
>                 URL: https://issues.jboss.org/browse/JBIDE-9778
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 3.2.0.Final, 3.2.1.Final
>         Environment: Eclipse Helios SR1
>            Reporter: Eric B
>            Assignee: Fred Bricon
>              Labels: jar, maven
>         Attachments: jboss tools maven bug.zip
>
>
> I have a Maven eclipse webapp project created and deployed in my JBoss server.  I have the deploy set to deploy as an exploded war, so I can see all the files that it produces in the deployment directory.
> My webapp project is dependent on another Eclipse project (server.jar artifact).  If I have both projects open in Eclipse at the same time, everything works fine.
> My server.jar project is also dependent on other Eclipse projects (supportLib.jar).  If I have those dependent projects opened at the same time, then the exploded jar file is invalid.  Instead of exporting everything in src/main/java/* to the jar file, it exports everything from src/*.  Consequently, the TopLevel in my jar file in the embedded projects is main.java.myTLD instead of myTLD.
> For example, if I have the supportLib.jar project with files "src/main/java/myTld/file.java" opened at the same time as server.jar and webapp.war, then the exported war for supportLib.jar in the webapp.war folder is contains "META-INF and main" rather than "META-INF and myTLD".
> I have updated to the latest version of JBoss Tools from the Helios update site and continue to see this problem.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira