Unfortunately I mean the other way. We have lots of maven builds in our organization that consume our gradle-built artifacts On Dec 5, 2012 4:46 PM, "Hans Dockter" <[email protected]> wrote:
> > On Dec 5, 2012, at 11:39 PM, Hans Dockter <[email protected]> wrote: > > > On Dec 5, 2012, at 11:36 PM, Steve Ebersole <[email protected]> wrote: > > I grey what you are saying and agree for the most part. Except for the > "in the gradle world" part. I think that to a degree once you apply the > maven plugin you are saying something about how you want certain things to > work. > > The use case I am most thinking of is that of mixed build tool > environments. Yes forcing publishing to just the remote repo and then the > maven build to grab it from there works. But again it's a question of what > is a reasonable expectation from someone who has a gradle build with the > maven plugin applied. > > I agree 100 percent. And we will make it very easy so Gradle behaves like > you would expect it to do. It is good that you point out the local > integration between Gradle and Maven build (a typical JBoss scenario :)). > But just by having it in separated tasks that are always both executed by > default, gives you the opportunity to exclude if you want to. > > > Just to mention it. Long term we want to be able deeply integrate with any > Maven build so that you can make it part of any logical Gradle build and > for the interaction Gradle would just do the right thing. > > Hans > >
