You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2009/02/06 11:11:19 UTC
[jira] Commented: (MNG-3768) [regression] Class folder system
dependency doesn't work anymore
[ http://jira.codehaus.org/browse/MNG-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=164216#action_164216 ]
Brett Porter commented on MNG-3768:
-----------------------------------
Francois... when I apply that patch, 3288 still fails. The cases are certainly incompatible.
Is there really no way you can package those classes into an artifact?
> [regression] Class folder system dependency doesn't work anymore
> ----------------------------------------------------------------
>
> Key: MNG-3768
> URL: http://jira.codehaus.org/browse/MNG-3768
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.1.0-M1
> Environment: Any
> Reporter: Francois Loison
> Fix For: 2.1.0-M2
>
> Attachments: mng-3288.zip, MNG-3768.patch.txt, mng-3768.zip, patch-MNG-3768-distribution.txt
>
>
> My project use system dependencies pointing to class folders.
> <dependency>
> <groupId>class-folder</groupId>
> <artifactId>class-folder</artifactId>
> <version>N</version>
> <scope>system</scope>
> <systemPath>C:/appli/classes</systemPath>
> </dependency>
> Such class folders dependencies worked fine with maven 2.0.7
> They are needed by my project as it relies on a legacy application not packaged into a jar file.
> Root cause is located in file DefaultArtifactResolver.java:
> if ( !systemFile.isFile() )
> {
> throw new ArtifactNotFoundException( "System artifact: " + artifact + " is not a file: " + systemFile,
> artifact );
> }
--
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