You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "fabrizio giustina (JIRA)" <ji...@codehaus.org> on 2005/11/26 16:26:06 UTC
[jira] Closed: (MPECLIPSE-103) Allow to skip dependencies from being included in .classpath file
[ http://jira.codehaus.org/browse/MPECLIPSE-103?page=all ]
fabrizio giustina closed MPECLIPSE-103:
---------------------------------------
Assign To: fabrizio giustina
Resolution: Won't Fix
Fix Version: 1.9
> In my project, we generate some enumerations using Castor (using xerces-2.4). The generated
> code is completely independent of XML or Castor.
If I understood correclty, you added the castor dependency in order to generate source code: the castor dependency, however, should not be a project dependency but a plugin dependency. For example this should work if you are using the maven castor plugin at http://maven.apache.org/maven-1.x/reference/plugins/castor/index.html (do you?).
If you are using a custom ant task you will need castor and xerces in the classpath, but this is not the recommended way.
First of all, castor will be in the classpath used by maven when executing tests, and this is the same situation you are seeing in eclipse (so, it SHOULD fail in eclipse if it fails with maven).
As a solution you should:
- use a plugin to generate sources and, if such plugin doesn't exist, extract your code from maven.xml and put it in a plugin (recommended)
- manually modify the classpath before calling the ant task used to generate sources, removing the castor jar from project.xml
> Allow to skip dependencies from being included in .classpath file
> -----------------------------------------------------------------
>
> Key: MPECLIPSE-103
> URL: http://jira.codehaus.org/browse/MPECLIPSE-103
> Project: maven-eclipse-plugin
> Type: New Feature
> Versions: 1.9
> Reporter: Werner Schulz
> Assignee: fabrizio giustina
> Fix For: 1.9
>
>
> Need a means to specify that some maven dependencies are NOT included in the generated .classpath file.
> Reason: Maven builds a project. This may include generating source via castor, InjectJ, etc.
> Once the source code is generated, the generated source may not depend on the various jars that helped generate it.
> That means, the Eclipse project should not depend on these jars. Currently, it is not possible to exclude these jars.
> Can you add an additional property, like <eclipse.classpath.include>no</eclipse.classpath.include>, which will
> not add the dependency to the generated classpath file.
--
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
-
For more information on JIRA, 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