Pushing to master-git and pushing releases. All the license headers and
GAV's are still codehaus.
Kristian
to., 09.06.2011 kl. 15.15 -0400, skrev John Casey:
> Yeah, I thought that's what we were talking about...so, if you clone the
> git repo, the "commit bit" you're talking about is for pul
Yeah, I thought that's what we were talking about...so, if you clone the
git repo, the "commit bit" you're talking about is for pulling those
changes back to the sonatype clone, right?
Not to be a pain, but who's saying sonatype's the ultimate authority on
plexus?
On 6/9/11 2:57 PM, Arnaud H
On Thu, Jun 9, 2011 at 6:32 PM, John Casey wrote:
>
>
> On 6/9/11 6:09 AM, Kristian Rosenvold wrote:
>
>> It was like
>> that at codehaus, and it still works that way.
>>
>
> Sorry to display my ignorance, but I haven't done much with the plexus-*
> code in awhile...
>
> Other than the container,
Stephen Connolly wrote:
> Will this affect toolchains from using the older javac and running
> tests with older jvms?
>
> toolchains is the recommended way to compile with older java versions
> and run tests with older java versions...
>
> I see no reason, as long as toolchains based invoking of
On 6/9/11 6:09 AM, Kristian Rosenvold wrote:
It was like
that at codehaus, and it still works that way.
Sorry to display my ignorance, but I haven't done much with the plexus-*
code in awhile...
Other than the container, where is the plexus-compiler stuff now, if not
codehaus? Are we talk
Totally agree, onward and upward!
On 6/9/11 5:30 AM, Kristian Rosenvold wrote:
I'd like to gradually start migrating some of these to java 1.5. Doing
so will effectively prevent any java 1.4 clients from upgrading.
It's my opinion that this move will effectively be the end of java all
1.4 suppo
Interesting question. I don't know the answer ;)
Are there any formalized test benches (IT's or similar) for the
toolchains stuff ? Easiest thing in the world to just try ;)
Kristian
to., 09.06.2011 kl. 10.41 +0100, skrev Stephen Connolly:
> Will this affect toolchains from using the older jav
> Actually I'd go further one step: plexus has been developed to 90% by ASF
> committers. So I'd rather go and move plexus over to maven completely while
> upgrading to java 1.5 and rewrite/drop parts with uncertain provenience.
I don't really see the point of all this moving stuff around, are w
n Rosenvold wrote:
> From: Kristian Rosenvold
> Subject: Move plexus dependencies to java 1.5 (Important!)
> To: dev@maven.apache.org
> Date: Thursday, June 9, 2011, 9:30 AM
> I'd like to gradually start migrating
> some of these to java 1.5. Doing
> so will effectively p
Will this affect toolchains from using the older javac and running
tests with older jvms?
toolchains is the recommended way to compile with older java versions
and run tests with older java versions...
I see no reason, as long as toolchains based invoking of older java
versions is not affected, w
no objections.
Onward !
2011/6/9 Kristian Rosenvold :
> I'd like to gradually start migrating some of these to java 1.5. Doing
> so will effectively prevent any java 1.4 clients from upgrading.
>
> It's my opinion that this move will effectively be the end of java all
> 1.4 support. (The surefire
I'd like to gradually start migrating some of these to java 1.5. Doing
so will effectively prevent any java 1.4 clients from upgrading.
It's my opinion that this move will effectively be the end of java all
1.4 support. (The surefire fork is the only "declared" java 1.3/1.4 (!)
support left that I
12 matches
Mail list logo
