Even this an old problem...
I still believe http://jira.codehaus.org/browse/MNG-5265 is a
potential security issue.
But no time ATM to work on that.
On 14 January 2014 00:24, Stephen Connolly
wrote:
> I have added a wiki page summary of this discussion:
>
> https://cwiki.apache.org/confluence/di
Stephen Connolly wrote:
> Added... now how come it wasn't on the issue tracker list
Thanks!
- Jörg
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Added... now how come it wasn't on the issue tracker list
On 13 January 2014 19:09, Jörg Schaible wrote:
> Hi Stephen,
>
> Stephen Connolly wrote:
>
> > I have added a wiki page summary of this discussion:
> >
> > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>
> I mis
On Monday, 13 January 2014, Benson Margulies wrote:
> In XML Schema, these aren't 'comments', these are 'comment nodes' --
>
>This is not the type you are looking for
>
> which is what I'm suggesting is reasonable,
Yep I agree... But it's out of scope for 3.2.0... Let's discuss in a few
week
Hi Rory,
The Apache Maven team has introduced a wiki page[1] to keep track of JDK8
specific issues.
These are results when we started to build+test all our plugins with JDK8.
We see that the javadoc executable has become stricter.
Especially the "reference not found" is tricky, since there's
Hi Stephen,
Stephen Connolly wrote:
> I have added a wiki page summary of this discussion:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
I miss MNG-5207 bitterly on the radar. M3 is not able to calculate a proper
build sequence and uses either a stale SNAPSHOT or
The following issues I proposed to move to 4.x. I have not heard anything
to the contrary... shall I pull the trigger on these?
- http://jira.codehaus.org/browse/MNG-4622 Throw Validation Error if pom
contains a dependency with two different versions.
- http://jira.codehaus.org/browse/MNG
wiki updated ;-)
On 13 January 2014 17:56, Benson Margulies wrote:
> Done.
>
> On Mon, Jan 13, 2014 at 12:53 PM, Benson Margulies
> wrote:
> > On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
> > wrote:
> >> On 13 January 2014 16:13, Benson Margulies
> wrote:
> >>>
> >>> Why isn't this cop
Dedicated comments nodes can be useful. For example, both XML Schema format
and the Spring Framework schemas allow dedicated comment nodes. I don't
have any opinion if dedicated comment nodes are useful for Maven POMs but I
am willing to listen and learn.
On Mon, Jan 13, 2014 at 10:59 AM, Stephen
In XML Schema, these aren't 'comments', these are 'comment nodes' --
This is not the type you are looking for
which is what I'm suggesting is reasonable, as opposed to capturing
text from comments. If I've
missed something I'd be happy to be educated.
On Mon, Jan 13, 2014 at 12:56 PM, Paul
Done.
On Mon, Jan 13, 2014 at 12:53 PM, Benson Margulies
wrote:
> On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
> wrote:
>> On 13 January 2014 16:13, Benson Margulies wrote:
>>>
>>> Why isn't this copied to the dev list?
>>
>>
>> It was, check the headers
>
> I see. GMail has learned a new
On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
wrote:
> On 13 January 2014 16:13, Benson Margulies wrote:
>>
>> Why isn't this copied to the dev list?
>
>
> It was, check the headers
I see. GMail has learned a new prank, which is to skip 'dev' in the
brief listing of who is on the email.
>
No problem, I just want to keep us moving forward... either trimming the
scope or getting things done until we can cut 3.2.0 and start thinking
about useful problems for the community, such as model version 5.0.0 ;-)
On 13 January 2014 15:43, Jason van Zyl wrote:
> I need another few hours to f
On 13 January 2014 16:13, Benson Margulies wrote:
> Why isn't this copied to the dev list?
>
It was, check the headers
>
>
> I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
> remotely under consideration.
I moved MNG-3879 to 4.0 backlog.
Your action was to split out the se
Why isn't this copied to the dev list?
I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
remotely under consideration. It is a proposal, to start with, to add
an element to the POM:
some text
...
which would make it a job for 4.0. It was never my inten
I need another few hours to finish one thing I'm working on, and then I'll take
another walk through JIRA. I have 8 customer branches I need to rebase and
clean up before I get to it.
On Jan 13, 2014, at 8:24 AM, Stephen Connolly
wrote:
> I have added a wiki page summary of this discussion:
>
There is a fine line between stability and missing out on good, newer
features.
IMHO, requiring Maven to use code/language features no newer than those of
a JDK twice
deprecated by Oracle lands on the "missing out on good newer features".
Without listing any nice-to-have features in more recent la
I have added a wiki page summary of this discussion:
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
Reminder, I pegged some action items against Benson, Olivier, Kristian &
Jason... See the action required section... mostly just status updates.
On 7 January 2014 22:03,
yes I know... but that doesn't get the full Java 8 API... which brings the
fun of animal sniffer back in play... I'd rather be able to just rely on
Java 8 the full shebang! That ain't happening before Java 8 is released...
if we'd rather a policy of "1 and 0 back" I'd be happy with that too!
On 1
https://github.com/orfjackal/retrolambda
2014/1/13 Stephen Connolly
> We are gearing up for the release of Maven 3.2.0... wherein we will drop
> support for Java 1.5 as the runtime that Maven requires (we will still
> support compiling and running tests with older JVMs via toolchains though)
>
We are gearing up for the release of Maven 3.2.0... wherein we will drop
support for Java 1.5 as the runtime that Maven requires (we will still
support compiling and running tests with older JVMs via toolchains though)
This means we will effectively enter a realm of "1 and 1 back"
Do we want to s
21 matches
Mail list logo
