Just thinking about how different repositories can be handled. I think
we should at least track the "origin" repository ids an artifact has
been resolved from to have something to match against the effective
repositories of a project. So that an artifact resolved from a
repository not part of a con
I am toying with having the format be xml.gz rather than xml
JavaScript, Rubies, .NET and the JRE all have portable implementations so
would seem reasonable given the high repeats in the content.
OTOH transport GZ should be easy and makes the file easier for users to
inspect
Thought?
On Monday
On Monday 26 September 2016, Christian Schulte wrote:
> Am 09/26/16 um 15:29 schrieb Stephen Connolly:
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
--
Sent from my phone
Am 09/26/16 um 15:29 schrieb Stephen Connolly:
>
On Monday 26 September 2016, Christian Schulte wrote:
> Am 26.09.2016 um 15:29 schrieb Stephen Connolly:
> > Here's an approximation of my current thinking:
> >
> >
> >
> >
> > [...]
> > [...]
> > ...
> >
> >
> >
>
> groupId, artifactId an
Am 26.09.2016 um 15:29 schrieb Stephen Connolly:
> Here's an approximation of my current thinking:
>
>
>
>
> [...]
> [...]
> ...
>
>
>
groupId, artifactId and version are the ones specified at
level, correct?
>
>
On Mon, 26 Sep 2016 14:17:59 +0200, Stephen Connolly
wrote:
https://www.youtube.com/watch?v=Wef9p4ykNMM
Some questions Robert had:
1. Do we need module-info.java for src/main/test?
* Well if I'm creating a test-jar to allow reuse of the tests in
downstream
projects, then yes we do
So
XPP3 spec also knows about an attribute called combine.id, which I've
implemented in plexus-utils-3.0.22 (which again is part of Maven-3.3.9)
This is especially handy in case of Lists. Maybe that can help you.
Robert
ps.I can't find links to the docs, sorry...
On Mon, 26 Sep 2016 20:27:59 +02
I'm helping out a bit with the bnd-maven-plugin.
They are currently recursing up the chain of parents, looking at the
DOM for , to combine parent and child information.
There's
http://blog.sonatype.com/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/,
but
(a) gosh it looks
Sounds reasonable. I think you have your answer
On Monday 26 September 2016, Stian Soiland-Reyes wrote:
> If you don't mind helping with back porting, then we can help push
> maintenance releases out :)
>
> On 26 Sep 2016 11:03 a.m., "Stephen Connolly" <
> stephen.alan.conno...@gmail.com > wrote
If you don't mind helping with back porting, then we can help push
maintenance releases out :)
On 26 Sep 2016 11:03 a.m., "Stephen Connolly" <
stephen.alan.conno...@gmail.com> wrote:
> Well another question is how much longer will we support Java 7 anyway...
> what we have said in the past is the
Here's an approximation of my current thinking:
[...]
[...]
...
...
...
https://www.youtube.com/watch?v=Wef9p4ykNMM
Some questions Robert had:
1. Do we need module-info.java for src/main/test?
* Well if I'm creating a test-jar to allow reuse of the tests in downstream
projects, then yes we do
2. Is Animal-Sniffer relevant now that we have --release N?
* Well more
We do not have to rush however I can optimistically imaging the some
colleagues like Kristian would enjoy their spare time on reworking Maven
sources to Java 8 :-)
On Mon, Sep 26, 2016 at 12:04 PM, stephenconnolly [via Maven] <
ml-node+s40175n5881611...@n5.nabble.com> wrote:
> Well another questi
Well another question is how much longer will we support Java 7 anyway...
what we have said in the past is the next release line after JDK9 is
released will only support Java 8+... now we could change that, but that is
*currently* what we have currently stated. I suspect that a bump to Java 8
by co
Thanks Robert!
Rgds,Rory
On 25/09/2016 14:09, Robert Scholte wrote:
Hi Rory,
I've just tested my multirelease demo project and can confirm that
8165723 is fixed in 9-ea+136-jigsaw.
thanks,
Robert
On Tue, 20 Sep 2016 12:02:26 +0200, Rory O'Donnell
wrote:
Hi Robert & Kristian,
16 matches
Mail list logo
