Am 2017-05-22 um 09:13 schrieb Plamen Totev:
Hi,
As the branch is now merged is there anything that blocks the release of
Plexus IO 3.0.0?
I need to do some more stuff like parent release, etc. It is in my
pipeline. Will try to do this by the end of the week.
Michael
Hi,
As the branch is now merged is there anything that blocks the release of
Plexus IO 3.0.0?
Regards,
Plamen Totev
Am 2017-05-05 um 10:44 schrieb Anders Hammar:
On Fri, May 5, 2017 at 10:22 AM, Michael Osipov <1983-01...@gmx.net> wrote:
This will also ultimately mean that these plugins will run with Maven 3.3
only
if someone still uses an older version and Java 6 to build their projects.
If someone still
On Fri, May 5, 2017 at 10:22 AM, Michael Osipov <1983-01...@gmx.net> wrote:
> This will also ultimately mean that these plugins will run with Maven 3.3
> only
> if someone still uses an older version and Java 6 to build their projects.
>
I don't follow.
Not to confuse anyone we should separate
This will also ultimately mean that these plugins will run with Maven 3.3 only
if someone still uses an older version and Java 6 to build their projects.
> That's the big question I'd like clarify first.
> Commons Compress has gone Java 7 in a minor release and people are requesting
> it for
That's the big question I'd like clarify first.
Commons Compress has gone Java 7 in a minor release and people are requesting
it for Plexus Archiver...
> How would we handle this wrt versions of our plugins when the requirements
> for those are bumped from Java 6 to Java 7?
>
> For example,
On Fri, May 5, 2017 at 9:01 AM, Olivier Lamy wrote:
> well IMHO we can definitely have everything 7 mandatory...
>
I'm fine with that, but I think we should at least bump minor version of a
plugin when this happens.
/Anders
>
> On 5 May 2017 at 16:45, Anders Hammar
well IMHO we can definitely have everything 7 mandatory...
On 5 May 2017 at 16:45, Anders Hammar wrote:
> How would we handle this wrt versions of our plugins when the requirements
> for those are bumped from Java 6 to Java 7?
>
> For example, maven-jar-plugin has
How would we handle this wrt versions of our plugins when the requirements
for those are bumped from Java 6 to Java 7?
For example, maven-jar-plugin has plexus-archiver as a dependency. m-jar-p
v3.0.2 requires Java 6. Is a bump to v3.1.0 enough for going to Java 7?
/Anders
On Thu, May 4, 2017
On Thu, May 4, 2017 at 1:39 PM, Michael Osipov wrote:
> Hi folks,
>
> five months ago I asked about Java 7 upgrade of Plexus Archiver [1] and
> received no reaction. I will move to a new major and integrate Plamen's
> changes.
>
> Additionally, he was so kind to work on
10 matches
Mail list logo