[JBoss JIRA] Created: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
4:09 p.m.
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.1.Final, 3.2.0.Final
Environment: Eclipse Helios SR1
Reporter: Eric B
Assignee: Fred Bricon
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
4:15 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9778:
------------------------------------
What version of m2e-wtp is installed?
Can you attach your pom.xml and eclipse config files? No need of your java code, you can
obfuscate any sensible information.
Have you tried doing a right click on project, Maven > Update Project configuration?
What JBoss AS are you deploying to?
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
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
11:06 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
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
11:06 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
Eric B updated JBIDE-9778:
--------------------------
Attachment: jboss tools maven bug.zip
Set of 3 pom/.project/.classpath configuration files
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
11:14 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
Eric B updated JBIDE-9778:
--------------------------
Attachment: Screenshot-engine-configuration-1.0-SNAPSHOT.jar .png
Screenshot of configuration.jar file (flattened view)
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,
Screenshot-engine-configuration-1.0-SNAPSHOT.jar .png
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
11:14 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
Eric B commented on JBIDE-9778:
-------------------------------
I have also attached a screenshot of the produced jar file (flattened view). Note how the
paths all start with main/java/com/private instead of com/private.
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,
Screenshot-engine-configuration-1.0-SNAPSHOT.jar .png
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
11:23 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
Eric B commented on JBIDE-9778:
-------------------------------
I just noticed, actually, that the problem is even more critical. I had missed it
originally, but the created jar file is actually a jar of java files and not the class
files! (See screenshot) This means that it isn't even the compiled classes that are
being exported by the deploy process....
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,
Screenshot-engine-configuration-1.0-SNAPSHOT.jar .png
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
2:27 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9778:
------------------------------------
Eric,
the attached projects are missing the ./settings folders (It's kinda a big deal). can
you attach a more complete version please?
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,
Screenshot-engine-configuration-1.0-SNAPSHOT.jar .png
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
9:22 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
Eric B updated JBIDE-9778:
--------------------------
Attachment: jboss tools maven bug - complete.zip
Updated config files w/ .settings folder included.
Includes original config files and poms from the original zip file as well for
completeness
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 - complete.zip, jboss tools maven bug -
complete.zip, jboss tools maven bug.zip, Screenshot-engine-configuration-1.0-SNAPSHOT.jar
.png
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
9:22 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
Eric B updated JBIDE-9778:
--------------------------
Attachment: jboss tools maven bug - complete.zip
Updated config files w/ .settings folder included.
Includes original config files and poms from the original zip file as well for
completeness
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 - complete.zip, jboss tools maven bug -
complete.zip, jboss tools maven bug.zip, Screenshot-engine-configuration-1.0-SNAPSHOT.jar
.png
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
4:42 a.m.
New subject: [JBoss JIRA] (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
Fred Bricon resolved JBIDE-9778.
--------------------------------
Resolution: Migrated to another ITS
It's an upstream (i.e. m2e-wtp) bug. I opened
https://issues.sonatype.org/browse/MECLIPSEWTP-182 to follow up on the problem.
As a workaround, you need to manually add the correct source path folders in your
org.eclipse.wst.common.component file :
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="java">
<wb-resource deploy-path="/"
source-path="/src/main/java"/>
<wb-resource deploy-path="/"
source-path="/src/main/resources"/>
</wb-module>
</project-modules>
{noformat}
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 - complete.zip, jboss tools maven bug -
complete.zip, jboss tools maven bug.zip, Screenshot-engine-configuration-1.0-SNAPSHOT.jar
.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:50 a.m.
New subject: [JBoss JIRA] (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9778:
------------------------------------
Eric, do you still have the problem? Importing the projects as maven projects, if you
remove the eclipse config files beforehand?
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 - complete.zip, jboss tools maven bug -
complete.zip, jboss tools maven bug.zip, Screenshot-engine-configuration-1.0-SNAPSHOT.jar
.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9 a.m.
New subject: [JBoss JIRA] (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
[
https://issues.jboss.org/browse/JBIDE-9778?page=com.atlassian.jira.plugin...
]
Eric B commented on JBIDE-9778:
-------------------------------
The problem is alleviated by modifying the org.eclipse.wst.common.component file as
indicated above. I have since finished working on the project so in maintenance mode I do
not have much day-to-day work on the project any longer.
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 - complete.zip, jboss tools maven bug -
complete.zip, jboss tools maven bug.zip, Screenshot-engine-configuration-1.0-SNAPSHOT.jar
.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5204
days inactive
5306
days old
jbosstools-issues@lists.jboss.org
12 comments
5 participants
participants (5)
-
Eric B (Commented) (JIRA) -
Eric B (JIRA)
-
Fred Bricon (Commented) (JIRA)
-
Fred Bricon (JIRA)
-
Fred Bricon (Resolved) (JIRA)