On Fri, May 20, 2016 at 4:05 PM, Antoine Toulme <[email protected]> wrote:
> I got a few things in for 1.5. The changelog reads:
Excellent work.
> Additionally, I have started reviewing the issues in jira and as best I could
> tried to perform some triage. Some issues are old and don’t apply so much and
> I’ve started closing them. If needed we can reopen issues if they should be
> looked at again.
Sounds good.
> I have other things slowly brewing but I’d really like to knock off the old
> issues and update to Java 8 before anything else happens.
The one thing I would like to see and are willing to do the work for
is moving 'buildr/custom_pom' addon back into the core. I would
ideally like to be generating useful poms with correctly defined poms
for consumption in other build systems. Besides adding a truckload of
tests the only other thing that I think would be useful to add is the
ability to specify "provided" scoped dependencies. I am not really
sure about how to go about this.
I had thought of adding something like
compile.provides << :mydependency
This would be equivalent to
project.compile.with :mydependency
project.pom.provided_dependencies << :mydependency
We may also need to change the way we output dependencies from
<dependency>
<groupId>com.biz</groupId>
<artifactId>app</artifactId>
<version>1.0</version>
</dependency>
to
<dependency>
<groupId>com.biz</groupId>
<artifactId>app</artifactId>
<version>1.0</version>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
As Maven assumes transitive dependencies and buildr assumes no
transitive dependencies.
Thoughts?
--
Cheers,
Peter Donald
