Bug 320861 - Red Hat Developer Studio EAR build problems
Summary: Red Hat Developer Studio EAR build problems
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Developer Suite
Classification: Retired
Component: eclipse
Version: 1.0
Hardware: All
OS: Windows
low
medium
Target Milestone: ---
Assignee: Marshall Culpepper
QA Contact: eclipse-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-05 20:56 UTC by Stephen Westbom
Modified: 2008-11-27 13:58 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-11-27 13:58:15 UTC
Embargoed:


Attachments (Terms of Use)

Description Stephen Westbom 2007-10-05 20:56:17 UTC
Publish doesn't pick up specified jars in the org.eclipse.wst.common.component
file where the XML elements is like this example:

<dependent-module archiveName="tomahawk-sandbox.jar" deploy-path="/"
handle="module:/classpath/var/M2_REPO/org/apache/myfaces/tomahawk/tomahawk-sandbox/1.1.6-SNAPSHOT/tomahawk-sandbox-1.1.6-SNAPSHOT.jar">
<dependency-type>uses</dependency-type>
</dependent-module> 

within a wb-module element

Comment 1 Ben Konrath 2007-10-09 21:52:11 UTC
Reassiging to JBossIDE team.

Comment 2 Marshall Culpepper 2007-10-10 01:58:38 UTC
This has been moved over to JBossTools JIRA here:
http://jira.jboss.com/jira/browse/JBIDE-1062

Stephen, can you create a JBoss JIRA User ID and add yourself as a watcher there?

Comment 3 Max Rydahl Andersen 2007-10-10 07:54:13 UTC
Yes - Stephan, please follow up on that one in our jira.

Especially with info on how you got that element in there (or if it was just 
pure hacking with the .component file ;)

Comment 4 Stephen Westbom 2007-10-10 14:25:15 UTC
No hack, these were entries made through project properties/Java Build Path/Add
Variable/Extend (M2_REPO)/ in a 3.2 version of Eclipse.

The only thing I see that cannot be done that way is the archiveName attribute
of the dependent-module element.  Has support for this been dropped?  It is an
important indirection in the very redundant configuration settings within the
Eclipse projects plugins (hasn't anyone heard of storing the same information
once, not numerous times in different configuration files for different plug-ins).

I don't want the manifest file's classpath entries for my war to have to deal
with version numbers for jars so I use the archiveName attribute (which works
just fine in 3.2)

Comment 5 Stephen Westbom 2007-10-10 14:27:24 UTC
BTW M2_REPO is the Maven 2 local repository directory. For example on my XP
environment it is:

C:/Documents and Settings/myUserName/.m2/repository

Comment 6 Andrew Overholt 2007-10-10 15:41:59 UTC
Why isn't there a Red Hat Developer Studio bugzilla entry under Products?  This
bug is currently filed against the old Red Hat Developer Suite.

Comment 7 Bryan Che 2007-10-10 15:48:07 UTC
JBoss uses Jira, not Bugzilla.

http://jira.jboss.com/jira/browse/RHDS


Comment 8 Stephen Westbom 2007-10-10 15:52:23 UTC
Sorry about that,  I think this is a branding issue.  The product is called Red
Hat Developer Studio not JBoss Developer Studio.  It is not very clear to me as
an end user where it belongs because of this (I think you should thank your
marketing department for that).

It was the closest product link I could find on the Red Hat site.  How about a
link to the JBoss area from Red Hat to make it clearer for this product or call
it JBoss Developer Studio and make your branding versus support clearer to
outsiders.

Comment 9 Andrew Overholt 2007-10-10 16:17:51 UTC
(In reply to comment #7)
> JBoss uses Jira, not Bugzilla.
> 
> http://jira.jboss.com/jira/browse/RHDS

Then this should be closed as upstream or something.

Comment 10 Andrew Overholt 2007-10-10 16:18:29 UTC
(In reply to comment #8)
> Sorry about that,  I think this is a branding issue.

It's not your fault, Stephen :)

Comment 11 Max Rydahl Andersen 2008-11-27 13:58:15 UTC
This bug should not be in here so closing it.

btw. no follow up were done on https://jira.jboss.org/jira/browse/JBIDE-1062 and we could not reproduce so we resolved it. Please create separate issue in JBIDE jira if still an issue.

And the product is actually named JBoss Developer Studio now ;)


Note You need to log in before you can comment on or make changes to this bug.