geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Dillon <ja...@planet57.com>
Subject Re: Assemblies in the repo and their dependencies
Date Thu, 18 Jun 2009 13:55:35 GMT
hrm... weird... will try to clean some of my repo and build again.

--jason


On Jun 18, 2009, at 8:39 PM, Ivan wrote:

> It is in http://repository.apache.org/snapshots. But this site is in  
> the root pom file, it should not have problem in downloading this  
> module.
> Ivan
>
> 2009/6/18 Jason Dillon <jason@planet57.com>
> My trunk build keeps puking on:
>
> <snip>
> Missing:
> ----------
> 1) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.18-SNAPSHOT
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>      mvn install:install-file - 
> DgroupId=org.apache.geronimo.ext.tomcat -DartifactId=jasper - 
> Dversion=6.0.18-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the  
> file there:
>      mvn deploy:deploy-file -DgroupId=org.apache.geronimo.ext.tomcat  
> -DartifactId=jasper -Dversion=6.0.18-SNAPSHOT -Dpackaging=jar - 
> Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>        1) org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0- 
> alpha-2
>        2) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.18-SNAPSHOT
>
> </snip>
>
> Where is this dep?
>
>
> --jason
>
>
> On Jun 18, 2009, at 4:31 AM, David Jencks wrote:
>
>
> On Jun 17, 2009, at 1:36 AM, Jason Dillon wrote:
>
> Why do the assemblies in the repository have dependencies?  I  
> realize that they are probably there to facilitate the build, but  
> shouldn't they all be marked as <scope>provided</scope>?
>
> The reason I think they should be, is that when a user wants to use  
> the geronimo-maven-plugin with the assembly -bin in the repository,  
> before they can even download the assembly -bin, first mvn has to go  
> resolve every single dependency which is used to build that assembly  
> -bin.
>
> I think this is broken, while I can resolve by adding a tone of  
> excludes, I think that this problem should be solved so that users  
> can more easily consume the assembly artifacts we publish to the  
> repository.
>
> Any one know how easy/feasible with the current stuff (trunk and  
> 2.1.x) it would be to mark all dependencies as provided?
>
> Just thinking about it I don't see why it would cause problems.   
> Would you like to try it and see if the server at least builds?  If  
> there are no obvious problems I'd be fine with this change.
>
> thanks
> david jencks
>
>
> --jason
>
>
>
>
> -- 
> Ivan


Mime
View raw message