Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369532 - Problem with m2e in Eclipse 3.7 (Springsource Tools Suite 2.8.1)
Summary: Problem with m2e in Eclipse 3.7 (Springsource Tools Suite 2.8.1)
Status: CLOSED NOT_ECLIPSE
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-24 10:19 EST by Mario Jauvin CLA
Modified: 2021-04-19 13:22 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mario Jauvin CLA 2012-01-24 10:19:16 EST 
When the following dependency is added to the project pom file:

        <dependency>
            <groupId>javax.validation</groupId>
            <artifactId>validation-api</artifactId>
            <version>1.0.0.GA</version>
            <classifier>sources</classifier>
        </dependency>

Then the validation-api.1.0.0.GA.jar and validation-api.1.0.0.GA-sources.jar will be copied to the output folder with weird names (see Springsource forum post for details) and the jar file with sources will be added to the java build path as a maven dependency build entry.  I am not the expert on maven but I think that the sources should be copied to the output folder and the class files jar should be added from the maven repository.  I am not certain though.  However, the current behavior causes the class files not to be found.

See this thread:

http://forum.springsource.org/showthread.php?121870-STS-2-8-1-ROO-and-GWT-hickups&p=398013#post398013
Comment 1 Matthew Piggott CLA 2012-01-24 10:56:12 EST 
Can you create a sample project to reproduce this using vanilla eclipse+m2e
Comment 2 Igor Fedorenko CLA 2012-01-24 13:34:03 EST 
Please contact springsource to troubleshoot STS problems.
Comment 3 Mario Jauvin CLA 2012-01-25 11:14:48 EST 
I did contact Springsource and they advise me to open a bug on m2e.  Have you verified that this is not a bug in m2e?  This is a rather cavalier method of shrugging it off.
Comment 4 Igor Fedorenko CLA 2012-01-25 11:29:10 EST 
(In reply to comment #3)
> I did contact Springsource and they advise me to open a bug on m2e.  Have you
> verified that this is not a bug in m2e?  This is a rather cavalier method of
> shrugging it off.

m2e does not copy dependency jars to output folder, there is simply no code to do that in m2e. in any case, if you believe the problem is in m2e, please provide a complete standalone project and steps to reproduce the problem using clean/fresh installation of "Eclipse IDE for Java Developers" from http://eclipse.org/downloads/ (as was already requested in comment 1).
Comment 5 Fred Bricon CLA 2012-03-27 09:47:53 EDT 
Closing as not an m2e-core issue.
Downstream STS 2.9.0 fixed this issue by upgrading to m2e-wtp 0.15.x
Comment 6 Fred Bricon CLA 2012-03-27 09:48:58 EDT 
Corresponding STS issue : https://issuetracker.springsource.com/browse/STS-2411
Comment 7 Denis Roy CLA 2021-04-19 13:22:15 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/