+1 none binding. Tested with MPIR 2.8.2-SNAPSHOT which has
maven-shared-jar-1.2-SNAPSHOT, it fixes the java8/bcel issue. Sorry, I am
not able to test maven-shaded-jar-1.2 at staging repo
Thanks
-D
On Fri, Jan 1, 2016 at 3:59 AM, Michael Osipov wrote:
> Am 2016-01-01 um 05:12 schrieb Dan Tran:
Am 2016-01-01 um 23:13 schrieb Ron Wheeler:
You might want to delay your deadline for a few days to allow people who
have been on holidays to get back to work.
Good point, let's push for another week until 2016-01-10.
Michael
On 01/01/2016 3:25 PM, Michael Osipov wrote:
Just wanted you to r
Just wanted you to remember that no issue has been updated since my last
mail. You still have a couple of days to take a look. Monday is deadline.
Am 2015-12-25 um 19:00 schrieb Michael Osipov:
Hi folks,
the previous had a bad wording, so I decided to rerun that.
I'd like to do another issue
Github user michael-o commented on the pull request:
https://github.com/apache/maven/pull/75#issuecomment-168311704
I second @khmarbaise answer, I do neither understand the problem you have.
Looking at the demo project you have provided, I looks completely screwed up.
Modules are supp
Github user khmarbaise commented on the pull request:
https://github.com/apache/maven/pull/75#issuecomment-168306169
First i see your setup as wrong..cause you use modules multiple times
within the reactor (Apart from using `..` which is
simply not needed`). What i don't understand is
Hi,
So after i've dived into this a little bit more...
The problem seemed to be located by the surefire-shadefire module which
packages surefire version 2.12.4 for running the build..
The surefire-shadefire module will request a surefire-api-2.19.1 during
the build which does not exist at th
Github user nhojpatrick commented on the pull request:
https://github.com/apache/maven/pull/75#issuecomment-168305170
I've worked on 5+ projects where they ranged from 75-150 maven projects.
Allow this configuration would have simplified and reduce build times. The
usual work around I
Am 2016-01-01 um 05:12 schrieb Dan Tran:
Strange, I even went this far in my pluginManagement
org.apache.maven.plugins
maven-project-info-reports-plugin
${project-info-report.plugin.version}
org.apache.maven.shar