Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
I just tested this too :)
This is because the aar generation calls the "ConsumeAarMojo" which adds the
classes of the aar dep in the target\classes folder which in turns gets picked
up by the aar creation.
We have 2 possible solutions:
1. Change the ConsumeAarMojo
2. filter the aar classes out.
Original comment by benoit.b...@gmail.com
on 6 Jan 2014 at 9:45
Also, trying to set the dependent aar to scope=provided causes build failures
due to missing classes.
Original comment by Philip.S...@gmail.com
on 12 Jan 2014 at 10:58
Um, why would you setting an AAR dep to provided?
Original comment by william....@xandar.com.au
on 12 Jan 2014 at 11:00
I was trying to prevent the classes from being included in the generated aar. I
was both trying optional / provided to mark the dependency as optional.
Original comment by Philip.S...@gmail.com
on 12 Jan 2014 at 11:03
fixed in 3.8.3-SNAPSHOT
Original comment by benoit.b...@gmail.com
on 11 Feb 2014 at 5:47
How do we close of these issues?
Original comment by william....@xandar.com.au
on 11 Feb 2014 at 9:47
Fixed in 3.9.0
Original comment by william....@xandar.com.au
on 27 Feb 2014 at 10:28
Original issue reported on code.google.com by
william....@xandar.com.au
on 6 Jan 2014 at 7:34Attachments: