Hi Tammo, No tangible progress on this yet; I've been thinking about the bigger transitive dependency picture and poking Ivy (and other tools that have integrated Ivy) to determine what's the best approach.
The approach you describe fits in that picture and I think it's fine to default to project.compile.dependencies. So if you want to get started on this, go ahead I'll figure out how to integrate it with the rest later. alex On Wed, Oct 13, 2010 at 12:20 PM, Tammo van Lessen <tvanles...@gmail.com>wrote: > Hi Alex, > > is there any news on that? After skimming through the code, I think a > nice way could be to let Artifacts know about their dependencies. > There could be a field that gets populated by loading the deps from > the pom (POM.load(...).dependencies) and could then be persisted to a > POM in pom_xml. The missing piece is how a newly built artifact can > know it's dependencies, this could be done via a parameter to the > package command, defaulting to project.compile.dependencies. > > How does that sound? > > Best, > Tammo > > On Fri, Aug 6, 2010 at 17:05, Tammo van Lessen <tvanles...@gmail.com> > wrote: > > Hi Alex, > > > > great. Thanks. Let me know if I can help somehow (not concealing that > > I have two left hands for Ruby). > > > > Tammo > > > > On Fri, Aug 6, 2010 at 06:51, Alex Boisvert <alex.boisv...@gmail.com> > wrote: > >> Hi Tammo, > >> > >> I've been helping to migrate a project to Buildr and we'll need to > >> publish poms with dependencies so I've started thinking about this. > >> I'm going to get started on it next week. > >> > >> alex > >> > >> On Thursday, August 5, 2010, Tammo van Lessen <tvanles...@gmail.com> > wrote: > >>> Hi guys, > >>> > >>> I was recently in the situation to find a suitable build system for > >>> "mavenizing" a project. "Mavenizing" in a sense that I needed the > >>> possibility to push them to nexus repository and that maven-based > >>> builds can simply use them (it includes a maven plugin) and can > >>> determine all dependencies transitively. > >>> > >>> I'd love to use buildr in this scenario, but therefore I'd need to > >>> somehow add a dependencies element to the generated pom. I think the > >>> dependencies could be taken from the compile and test dependencies we > >>> have in buildr. Is there a chance to put this to the roadmap if it's > >>> not already there? I guess this feature can be both over and under > >>> engineered, so perhaps a generic mechanism that allows users to > >>> customize the pom generation per subproject would be great but should > >>> be populated with smart defaults. > >>> > >>> WDYT? > >>> > >>> Best, > >>> Tammo > >>> > >>> -- > >>> Tammo van Lessen - tvanles...@gmail.com - http://www.taval.de > >>> > >> > > > > > > > > -- > > Tammo van Lessen - tvanles...@gmail.com - http://www.taval.de > > > > > > -- > Tammo van Lessen - tvanles...@gmail.com - http://www.taval.de >
