You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/05/05 22:53:31 UTC
[jira] Commented: (MPECLIPSE-10) added eclipseDependency='false' behavior

The following comment has been added to this issue:

     Author: thierry lach
    Created: Wed, 5 May 2004 4:53 PM
       Body:
<eclipse.dependency>false</eclipse.dependency> could be useful to explicitly bypass specific jar files

My specific situation is that I am building a war file to run against an app server which is running on jdk 1.3, while eclipse is running against jdk 1.4.  Oracle requires two different jdbc driver jar files for jdk 1.3 and jdk 1.4.  I would want to tag the oracle-jdk13 jar file as war.bundle/true and eclipse.classpath/false, while not marking the oracle-jdk14 jar so it becomes part of the classpath.

I could use the same logic to address the jdk13/jdk14 xerces issues.


---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-10&page=comments#action_19394

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-10

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPECLIPSE-10
    Summary: added eclipseDependency='false' behavior
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-eclipse-plugin

   Assignee: 
   Reporter: Piotr Maj

    Created: Fri, 22 Aug 2003 6:43 AM
    Updated: Wed, 5 May 2004 4:53 PM
Environment: any

Description:
While generating .classpath file maven-eclipse-plugin includes all artifacts defined in project.xml regardless of it's type. As a side effect it may be observed that even JSP's *.tld files are included as Eclipse variables.It leads to project compile problems. Actually such project won't compile at all.

To avoid such behavior I propose a silly patch attached, which takes care of eclipseDependency property of artifacts. If it is set to 'false' the artifact will not be listed in .classpath.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org