+1
good point to tag the sources with same version of Maven
On Sat, Dec 21, 2019 at 3:18 PM Karl Heinz Marbaise
wrote:
> I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which
> preserves the state of the history and furthermore we should create a
> tag after each M
Le vendredi 27 décembre 2019, 12:37:10 CET Karl Heinz Marbaise a écrit :
> Hi,
>
> On 27.12.19 12:21, Karl Heinz Marbaise wrote:
> > Hi,
>
> > I've created a tag on the Maven Integration Testing:
> Hervé was faster than I was...
no, no, you did the tag
this was just on one of my commits :)
>
>
of our release indirectly...
Kind regards
Karl Heinz Marbaise
On Sun, 22 Dec 2019 at 00:18, Karl Heinz Marbaise wrote:
I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which
preserves the state of the history and furthermore we should create a
tag after each Maven Core release
Hi,
On 27.12.19 12:21, Karl Heinz Marbaise wrote:
Hi,
I've created a tag on the Maven Integration Testing:
Hervé was faster than I was...
Named: its-maven-3.6.3 which is pointing to the state of the tests for
Apache 3.6.3 release.
This keeps the history of the tests and gives us the
Hi,
I've created a tag on the Maven Integration Testing:
Named: its-maven-3.6.3 which is pointing to the state of the tests for
Apache 3.6.3 release.
This keeps the history of the tests and gives us the chance to clean up
the test suites..
Kind regards
Karl Heinz Marbaise
do we really need a vote for this?
this seems to be overadministrativing :)
it's not a release or produce any artifacts so just do it
On Sun, 22 Dec 2019 at 00:18, Karl Heinz Marbaise wrote:
> I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which
> preserves the
+1
On Sat, Dec 21, 2019 at 9:18 AM Karl Heinz Marbaise wrote:
>
> I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which
> preserves the state of the history and furthermore we should create a
> tag after each Maven Core release.
>
> Vote open for at least 72
Hi,
On 21.12.19 15:23, Enrico Olivelli wrote:
+1
Please also update the release guide
That should be done of course.
thanks for the hint.
Enrico
Il sab 21 dic 2019, 15:18 Karl Heinz Marbaise ha
scritto:
I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which
preserves
+1
Please also update the release guide
Enrico
Il sab 21 dic 2019, 15:18 Karl Heinz Marbaise ha
scritto:
> I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which
> preserves the state of the history and furthermore we should create a
> tag after each Maven Cor
I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which
preserves the state of the history and furthermore we should create a
tag after each Maven Core release.
Vote open for at least 72 hours.
[ ] +1
[ ] +0
[ ] -1
Kind regards
Karl Heinz Marbaise
>> I'm diving a little bit into the integration tests of maven core...
>>
>> and I realized that at the moment this list of IT's is SKIPPED
>> based on the version of Maven Core:
>>
>> mng5889FindBasedir(MvnFileLongOptionModule).SKIPPE
tegration tests of maven core...
>
> and I realized that at the moment this list of IT's is SKIPPED
> based on the version of Maven Core:
>
> mng5889FindBasedir(MvnFileLongOptionModule).SKIPPED -
> Maven version 3.7.0-SNAPSHOT not in range [3.5.0,
.
But of course I think we should make it easier to
run IT's on a change you/someone have made (scripting / Docker etc.
whatever)...
Kind regards
Karl Heinz Marbaise
On 08.12.19 20:10, Karl Heinz Marbaise wrote:
Hi,
I'm diving a little bit into the integration tests of maven core...
and I
gt; especially build tools. They will make the minimal patch from
> > > anything
> > > > > > upstream to make their changes work. I’ve helped consultants make
> > > small
> > > > > > patches in Maven, and used the integration tests
verify
> everything
> > > > else
> > > > > worked.
> > > > >
> > > > > Yes, they will always be in the history but I can’t imagine it
> would
> > be
> > > > > very nice for someone in that situation to go hunting through the
>
sts in order to verify a change. I think we would all
> > be
> > > > pretty shocked how many people still actually use Maven 2.x. The
> > support
> > > > cycle on things like airplanes is upwards of 50 years and no one will
> > > > change a thing if t
think we would all
> be
> > > pretty shocked how many people still actually use Maven 2.x. The
> support
> > > cycle on things like airplanes is upwards of 50 years and no one will
> > > change a thing if they don’t have to. I’m sure there’s lots of Maven
>
things like airplanes is upwards of 50 years and no one will
> > change a thing if they don’t have to. I’m sure there’s lots of Maven 1.x
> > and Ant in a bunch of nooks and crannies for that very reason. Didn’t
> > someone just post about writing a book about Maven 2.x? :-)
they don’t have to. I’m sure there’s lots of Maven 1.x
> and Ant in a bunch of nooks and crannies for that very reason. Didn’t
> someone just post about writing a book about Maven 2.x? :-)
>
> JvZ
>
> > On Dec 8, 2019, at 2:10 PM, Karl Heinz Marbaise
> wrote:
> >
> >
just post about writing a book
about Maven 2.x? :-)
JvZ
> On Dec 8, 2019, at 2:10 PM, Karl Heinz Marbaise wrote:
>
> Hi,
> I'm diving a little bit into the integration tests of maven core...
>
> and I realized that at the moment this list of IT's is SKIPPED
> based on the
Hi,
I'm diving a little bit into the integration tests of maven core...
and I realized that at the moment this list of IT's is SKIPPED
based on the version of Maven Core:
mng5889FindBasedir(MvnFileLongOptionModule).SKIPPED -
Maven version 3.7.0-SNAPSHOT not in range [3.5.0,3.5.1
21 matches
Mail list logo
