+1
On Sat, Jan 2, 2016 at 8:42 PM, Michael Osipov wrote:
> Am 2015-12-31 um 21:30 schrieb Michael Osipov:
>>
>> Hi,
>>
>> We solved 5 issues:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12334441
>>
>>
>> There are still a couple of issues left in JIRA:
Am 2015-12-31 um 21:30 schrieb Michael Osipov:
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12334441
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=component%20%3D%20maven-shared-jar%20AND
Github user michael-o commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168405448
Now I see, the `Optional´ comes from Guava and not from Java. I think the
likelyhood is higher w/o a model change.
---
If your project is set up for it, you can reply
Github user akacme commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168404937
In other words - will it go to Maven 3.x when there is no modification to
the model itself?
---
If your project is set up for it, you can reply to this email and have your
Github user akacme commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168403276
Code has been compiled using Java 7. Model has been enhanced to store graph
of imports in dependency management section - I can rewrite it to store it
elsewhere, but such s
Github user michael-o commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168402507
You are using Java 8 features which we can't accept. Java 7 only. The model
is changed. I would opt-in for that not before Maven 4.
---
If your project is set up for it
Hi,
Great news!
Notice that source parsing is not so crucial noawadays, since we use java 5
annotations in general, both for plexus/sisu and plugin-tools: if you
deactivate javadoc parsing, you should avoid the issue.
This xould permit work in parallel:
- continue Jigsaw tests
- fix the QDox s
