Re: is 3.5.1 open for business?

[Igor Fedorenko]

Will do. Thank you.

--
Regards,
Igor



On April 13, 2017 3:55:43 PM Stephen Connolly 
 wrote:



Just be sure to delete the branch after merging so that the job will get
cleaned up (in 3 days time - retention strategy)

On Thu 13 Apr 2017 at 23:53, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:


None here!

On Thu 13 Apr 2017 at 23:30, Igor Fedorenko  wrote:


Thank you for the explanation, didn't find this job.

Now that both branch builds are happy, any objections I merge then to
master?

--
Regards,
Igor



On April 13, 2017 1:20:24 PM Karl Heinz Marbaise 
wrote:

> Hi Igor,
>
>
> On 13/04/17 22:09, Igor Fedorenko wrote:
>> I pushed my changes to feature branches. How do I trigger CI builds
now?
>
> They are already running your builds...
>
> Take a look here:
>
>
https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/
>
> Kind regards
> Karl Heinz Marbaise
>
>
>>
>> --
>> Regards,
>> Igor
>>
>>
>>
>> On April 7, 2017 9:24:06 AM Igor Fedorenko 
wrote:
>>
>>> I completely agree we need to prove each code change does not break
>>> existing integration tests (and I did run the tests locally with my
>>> changes, fwiw)
>>>
>>> --
>>> Regards,
>>> Igor
>>>
>>> On Fri, Apr 7, 2017, at 11:58 AM, Stephen Connolly wrote:
 I want every issue that changes code (not docs or javadocs) to have
an
 integration test run before merging.

 We were trying to get consensus on a process but the debate died
without
 a
 conclusion

 On Fri 7 Apr 2017 at 16:21, Igor Fedorenko 
wrote:

 > I have two of small-ish fixes I'd like to submit, so I was
 wondering if
 > master is open for 3.5.1 changes already or we want to give it
little
 > more time in case we need to release any emergency patches.
 >
 > Also, what is the general bug fixing protocol now, push to
directly to
 > master and be prepared to revert or always go through a
 > pull-request-review process? I don't mind going the code review
route,
 > but in this particular case both changes touch 1-2 lines of code
not
 > counting regression test code, so I am not sure how much value
formal
 > code review process will provide.
 >
 > Also, does anyone know how to get my JIRA account fixed so I can
 > assign/close/etc bugs?
 >
 > Thank you in advance.
 >
 >
 > https://issues.apache.org/jira/browse/MNG-6210
 > https://issues.apache.org/jira/browse/MNG-6209
 >
 > --
 > Regards,
 > Igor
 >
 >
-
 > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 > For additional commands, e-mail: dev-h...@maven.apache.org
 >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

--

Sent from my phone


--
Sent from my phone




-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: is 3.5.1 open for business?

[Stephen Connolly]

Just be sure to delete the branch after merging so that the job will get
cleaned up (in 3 days time - retention strategy)

On Thu 13 Apr 2017 at 23:53, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> None here!
>
> On Thu 13 Apr 2017 at 23:30, Igor Fedorenko  wrote:
>
>> Thank you for the explanation, didn't find this job.
>>
>> Now that both branch builds are happy, any objections I merge then to
>> master?
>>
>> --
>> Regards,
>> Igor
>>
>>
>>
>> On April 13, 2017 1:20:24 PM Karl Heinz Marbaise 
>> wrote:
>>
>> > Hi Igor,
>> >
>> >
>> > On 13/04/17 22:09, Igor Fedorenko wrote:
>> >> I pushed my changes to feature branches. How do I trigger CI builds
>> now?
>> >
>> > They are already running your builds...
>> >
>> > Take a look here:
>> >
>> >
>> https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/
>> >
>> > Kind regards
>> > Karl Heinz Marbaise
>> >
>> >
>> >>
>> >> --
>> >> Regards,
>> >> Igor
>> >>
>> >>
>> >>
>> >> On April 7, 2017 9:24:06 AM Igor Fedorenko 
>> wrote:
>> >>
>> >>> I completely agree we need to prove each code change does not break
>> >>> existing integration tests (and I did run the tests locally with my
>> >>> changes, fwiw)
>> >>>
>> >>> --
>> >>> Regards,
>> >>> Igor
>> >>>
>> >>> On Fri, Apr 7, 2017, at 11:58 AM, Stephen Connolly wrote:
>>  I want every issue that changes code (not docs or javadocs) to have
>> an
>>  integration test run before merging.
>> 
>>  We were trying to get consensus on a process but the debate died
>> without
>>  a
>>  conclusion
>> 
>>  On Fri 7 Apr 2017 at 16:21, Igor Fedorenko 
>> wrote:
>> 
>>  > I have two of small-ish fixes I'd like to submit, so I was
>>  wondering if
>>  > master is open for 3.5.1 changes already or we want to give it
>> little
>>  > more time in case we need to release any emergency patches.
>>  >
>>  > Also, what is the general bug fixing protocol now, push to
>> directly to
>>  > master and be prepared to revert or always go through a
>>  > pull-request-review process? I don't mind going the code review
>> route,
>>  > but in this particular case both changes touch 1-2 lines of code
>> not
>>  > counting regression test code, so I am not sure how much value
>> formal
>>  > code review process will provide.
>>  >
>>  > Also, does anyone know how to get my JIRA account fixed so I can
>>  > assign/close/etc bugs?
>>  >
>>  > Thank you in advance.
>>  >
>>  >
>>  > https://issues.apache.org/jira/browse/MNG-6210
>>  > https://issues.apache.org/jira/browse/MNG-6209
>>  >
>>  > --
>>  > Regards,
>>  > Igor
>>  >
>>  >
>> -
>>  > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>  > For additional commands, e-mail: dev-h...@maven.apache.org
>>  >
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>> --
> Sent from my phone
>
-- 
Sent from my phone

Re: is 3.5.1 open for business?

[Stephen Connolly]

None here!

On Thu 13 Apr 2017 at 23:30, Igor Fedorenko  wrote:

> Thank you for the explanation, didn't find this job.
>
> Now that both branch builds are happy, any objections I merge then to
> master?
>
> --
> Regards,
> Igor
>
>
>
> On April 13, 2017 1:20:24 PM Karl Heinz Marbaise 
> wrote:
>
> > Hi Igor,
> >
> >
> > On 13/04/17 22:09, Igor Fedorenko wrote:
> >> I pushed my changes to feature branches. How do I trigger CI builds now?
> >
> > They are already running your builds...
> >
> > Take a look here:
> >
> > https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
> >
> >>
> >> --
> >> Regards,
> >> Igor
> >>
> >>
> >>
> >> On April 7, 2017 9:24:06 AM Igor Fedorenko  wrote:
> >>
> >>> I completely agree we need to prove each code change does not break
> >>> existing integration tests (and I did run the tests locally with my
> >>> changes, fwiw)
> >>>
> >>> --
> >>> Regards,
> >>> Igor
> >>>
> >>> On Fri, Apr 7, 2017, at 11:58 AM, Stephen Connolly wrote:
>  I want every issue that changes code (not docs or javadocs) to have an
>  integration test run before merging.
> 
>  We were trying to get consensus on a process but the debate died
> without
>  a
>  conclusion
> 
>  On Fri 7 Apr 2017 at 16:21, Igor Fedorenko 
> wrote:
> 
>  > I have two of small-ish fixes I'd like to submit, so I was
>  wondering if
>  > master is open for 3.5.1 changes already or we want to give it
> little
>  > more time in case we need to release any emergency patches.
>  >
>  > Also, what is the general bug fixing protocol now, push to directly
> to
>  > master and be prepared to revert or always go through a
>  > pull-request-review process? I don't mind going the code review
> route,
>  > but in this particular case both changes touch 1-2 lines of code not
>  > counting regression test code, so I am not sure how much value
> formal
>  > code review process will provide.
>  >
>  > Also, does anyone know how to get my JIRA account fixed so I can
>  > assign/close/etc bugs?
>  >
>  > Thank you in advance.
>  >
>  >
>  > https://issues.apache.org/jira/browse/MNG-6210
>  > https://issues.apache.org/jira/browse/MNG-6209
>  >
>  > --
>  > Regards,
>  > Igor
>  >
>  >
> -
>  > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>  > For additional commands, e-mail: dev-h...@maven.apache.org
>  >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone

Re: is 3.5.1 open for business?

[Igor Fedorenko]

Thank you for the explanation, didn't find this job.

Now that both branch builds are happy, any objections I merge then to master?

--
Regards,
Igor



On April 13, 2017 1:20:24 PM Karl Heinz Marbaise  wrote:


Hi Igor,


On 13/04/17 22:09, Igor Fedorenko wrote:

I pushed my changes to feature branches. How do I trigger CI builds now?


They are already running your builds...

Take a look here:

https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/

Kind regards
Karl Heinz Marbaise




--
Regards,
Igor



On April 7, 2017 9:24:06 AM Igor Fedorenko  wrote:


I completely agree we need to prove each code change does not break
existing integration tests (and I did run the tests locally with my
changes, fwiw)

--
Regards,
Igor

On Fri, Apr 7, 2017, at 11:58 AM, Stephen Connolly wrote:

I want every issue that changes code (not docs or javadocs) to have an
integration test run before merging.

We were trying to get consensus on a process but the debate died without
a
conclusion

On Fri 7 Apr 2017 at 16:21, Igor Fedorenko  wrote:

> I have two of small-ish fixes I'd like to submit, so I was
wondering if
> master is open for 3.5.1 changes already or we want to give it little
> more time in case we need to release any emergency patches.
>
> Also, what is the general bug fixing protocol now, push to directly to
> master and be prepared to revert or always go through a
> pull-request-review process? I don't mind going the code review route,
> but in this particular case both changes touch 1-2 lines of code not
> counting regression test code, so I am not sure how much value formal
> code review process will provide.
>
> Also, does anyone know how to get my JIRA account fixed so I can
> assign/close/etc bugs?
>
> Thank you in advance.
>
>
> https://issues.apache.org/jira/browse/MNG-6210
> https://issues.apache.org/jira/browse/MNG-6209
>
> --
> Regards,
> Igor
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org





-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: is 3.5.1 open for business?

[Karl Heinz Marbaise]

Hi Igor,


On 13/04/17 22:09, Igor Fedorenko wrote:

I pushed my changes to feature branches. How do I trigger CI builds now?


They are already running your builds...

Take a look here:

https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/

Kind regards
Karl Heinz Marbaise




--
Regards,
Igor



On April 7, 2017 9:24:06 AM Igor Fedorenko  wrote:


I completely agree we need to prove each code change does not break
existing integration tests (and I did run the tests locally with my
changes, fwiw)

--
Regards,
Igor

On Fri, Apr 7, 2017, at 11:58 AM, Stephen Connolly wrote:

I want every issue that changes code (not docs or javadocs) to have an
integration test run before merging.

We were trying to get consensus on a process but the debate died without
a
conclusion

On Fri 7 Apr 2017 at 16:21, Igor Fedorenko  wrote:

> I have two of small-ish fixes I'd like to submit, so I was
wondering if
> master is open for 3.5.1 changes already or we want to give it little
> more time in case we need to release any emergency patches.
>
> Also, what is the general bug fixing protocol now, push to directly to
> master and be prepared to revert or always go through a
> pull-request-review process? I don't mind going the code review route,
> but in this particular case both changes touch 1-2 lines of code not
> counting regression test code, so I am not sure how much value formal
> code review process will provide.
>
> Also, does anyone know how to get my JIRA account fixed so I can
> assign/close/etc bugs?
>
> Thank you in advance.
>
>
> https://issues.apache.org/jira/browse/MNG-6210
> https://issues.apache.org/jira/browse/MNG-6209
>
> --
> Regards,
> Igor
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: is 3.5.1 open for business?

[Stephen Connolly]

Are your branch jobs here:
https://builds.apache.org/job/maven-3.x-jenkinsfile/

On Thu 13 Apr 2017 at 21:17, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> Should trigger automatically
>
> On Thu 13 Apr 2017 at 21:09, Igor Fedorenko  wrote:
>
>> I pushed my changes to feature branches. How do I trigger CI builds now?
>>
>> --
>> Regards,
>> Igor
>>
>>
>>
>> On April 7, 2017 9:24:06 AM Igor Fedorenko  wrote:
>>
>> > I completely agree we need to prove each code change does not break
>> > existing integration tests (and I did run the tests locally with my
>> > changes, fwiw)
>> >
>> > --
>> > Regards,
>> > Igor
>> >
>> > On Fri, Apr 7, 2017, at 11:58 AM, Stephen Connolly wrote:
>> >> I want every issue that changes code (not docs or javadocs) to have an
>> >> integration test run before merging.
>> >>
>> >> We were trying to get consensus on a process but the debate died
>> without
>> >> a
>> >> conclusion
>> >>
>> >> On Fri 7 Apr 2017 at 16:21, Igor Fedorenko 
>> wrote:
>> >>
>> >> > I have two of small-ish fixes I'd like to submit, so I was wondering
>> if
>> >> > master is open for 3.5.1 changes already or we want to give it little
>> >> > more time in case we need to release any emergency patches.
>> >> >
>> >> > Also, what is the general bug fixing protocol now, push to directly
>> to
>> >> > master and be prepared to revert or always go through a
>> >> > pull-request-review process? I don't mind going the code review
>> route,
>> >> > but in this particular case both changes touch 1-2 lines of code not
>> >> > counting regression test code, so I am not sure how much value formal
>> >> > code review process will provide.
>> >> >
>> >> > Also, does anyone know how to get my JIRA account fixed so I can
>> >> > assign/close/etc bugs?
>> >> >
>> >> > Thank you in advance.
>> >> >
>> >> >
>> >> > https://issues.apache.org/jira/browse/MNG-6210
>> >> > https://issues.apache.org/jira/browse/MNG-6209
>> >> >
>> >> > --
>> >> > Regards,
>> >> > Igor
>> >> >
>> >> > -
>> >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >> >
>> >> > --
>> >> Sent from my phone
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>> --
> Sent from my phone
>
-- 
Sent from my phone

Re: is 3.5.1 open for business?

[Stephen Connolly]

Should trigger automatically

On Thu 13 Apr 2017 at 21:09, Igor Fedorenko  wrote:

> I pushed my changes to feature branches. How do I trigger CI builds now?
>
> --
> Regards,
> Igor
>
>
>
> On April 7, 2017 9:24:06 AM Igor Fedorenko  wrote:
>
> > I completely agree we need to prove each code change does not break
> > existing integration tests (and I did run the tests locally with my
> > changes, fwiw)
> >
> > --
> > Regards,
> > Igor
> >
> > On Fri, Apr 7, 2017, at 11:58 AM, Stephen Connolly wrote:
> >> I want every issue that changes code (not docs or javadocs) to have an
> >> integration test run before merging.
> >>
> >> We were trying to get consensus on a process but the debate died without
> >> a
> >> conclusion
> >>
> >> On Fri 7 Apr 2017 at 16:21, Igor Fedorenko  wrote:
> >>
> >> > I have two of small-ish fixes I'd like to submit, so I was wondering
> if
> >> > master is open for 3.5.1 changes already or we want to give it little
> >> > more time in case we need to release any emergency patches.
> >> >
> >> > Also, what is the general bug fixing protocol now, push to directly to
> >> > master and be prepared to revert or always go through a
> >> > pull-request-review process? I don't mind going the code review route,
> >> > but in this particular case both changes touch 1-2 lines of code not
> >> > counting regression test code, so I am not sure how much value formal
> >> > code review process will provide.
> >> >
> >> > Also, does anyone know how to get my JIRA account fixed so I can
> >> > assign/close/etc bugs?
> >> >
> >> > Thank you in advance.
> >> >
> >> >
> >> > https://issues.apache.org/jira/browse/MNG-6210
> >> > https://issues.apache.org/jira/browse/MNG-6209
> >> >
> >> > --
> >> > Regards,
> >> > Igor
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> > For additional commands, e-mail: dev-h...@maven.apache.org
> >> >
> >> > --
> >> Sent from my phone
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone

Re: is 3.5.1 open for business?

[Igor Fedorenko]

I pushed my changes to feature branches. How do I trigger CI builds now?

--
Regards,
Igor



On April 7, 2017 9:24:06 AM Igor Fedorenko  wrote:


I completely agree we need to prove each code change does not break
existing integration tests (and I did run the tests locally with my
changes, fwiw)

--
Regards,
Igor

On Fri, Apr 7, 2017, at 11:58 AM, Stephen Connolly wrote:

I want every issue that changes code (not docs or javadocs) to have an
integration test run before merging.

We were trying to get consensus on a process but the debate died without
a
conclusion

On Fri 7 Apr 2017 at 16:21, Igor Fedorenko  wrote:

> I have two of small-ish fixes I'd like to submit, so I was wondering if
> master is open for 3.5.1 changes already or we want to give it little
> more time in case we need to release any emergency patches.
>
> Also, what is the general bug fixing protocol now, push to directly to
> master and be prepared to revert or always go through a
> pull-request-review process? I don't mind going the code review route,
> but in this particular case both changes touch 1-2 lines of code not
> counting regression test code, so I am not sure how much value formal
> code review process will provide.
>
> Also, does anyone know how to get my JIRA account fixed so I can
> assign/close/etc bugs?
>
> Thank you in advance.
>
>
> https://issues.apache.org/jira/browse/MNG-6210
> https://issues.apache.org/jira/browse/MNG-6209
>
> --
> Regards,
> Igor
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org





-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-surefire issue #110: SUREFIRE-1216: TEST-*.xml files generated by Sure...

[jonenst]

Github user jonenst commented on the issue:

https://github.com/apache/maven-surefire/pull/110
  
Thanks for the hard work, congratz on the 2.20 release !


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Check if parameter is explicitly set

[András Kerekes]

Hey,

Sure, let me give you more context. The parameter has a default value that
users can override. But if they don't set it and another condition is true
(some file exists in the project), then we want to use a different value, a
different default. Maybe the best is to remove the default value, and in
the Mojo's execute() if it's null (the user didn't set it) we can decide
what value to assign to it based on the mentioned condition.

András

On Thu, Apr 13, 2017, 02:41 Karl Heinz Marbaise  wrote:

> Hi,
>
> On 13/04/17 02:05, András Kerekes wrote:
> > Hi,
> >
> > I'm working on a Maven plugin and I'd like to check whether a parameter
> for
> > a Mojo has been explicitly set by the user (via POM), or it contains the
> > default value. Is there a way to do this?
>
> Maybe I misunderstand a thing but why do you need to distinguish between
> those two? Isn't that why defaultValue exist?
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Building a Java9 project just using JDK9

[Paul Hammant]

>
>
>> I don't see any activity either, so my idea is to replace XStream, see
> MWAR-397[1]
>

Just for the record, Jörg is working through the Java9 issues for XStream
presently - https://github.com/x-stream/xstream/commits/master

- Paul

Re: [VOTE] Apache Mahout 0.13.0 Release Candidate

[Stephen Connolly]

Is it you want the profiles activated during the release:perform fork?

If that is the case you need to modify the "arguments" parameter of the
release goal. Depending on how your pom is set up this could be as simple
as  "-Darguments=-P+viennacl -P+..." or you may have to modify the pom
(though if you always need those
Profiles active for a release modifying the Pom to include them as release
profiles may be the way to go)

On Thu 13 Apr 2017 at 04:30, Andrew Musselman  wrote:

> Hi Maven team, we are having trouble getting a couple new modules included
> in our release build and our former "Maven person" can't contribute any
> more at their new job.
>
> Anyone up for some troubleshooting? We release from master, our source repo
> is at https://github.com/apache/mahout, and our latest artifacts are at
>
> https://repository.apache.org/content/repositories/orgapachemahout-1042/org/apache/mahout/apache-mahout-distribution/0.13.0/
> .
>
> Thanks for any help you can offer.
>
> Best
> Andrew
>
> -- Forwarded message -
> From: Andrew Musselman 
> Date: Wed, Apr 12, 2017 at 8:10 PM
> Subject: Re: [VOTE] Apache Mahout 0.13.0 Release Candidate
> To: 
>
>
> Does anyone know anyone on the Maven project or who understands the fine
> points of making things like this works?
>
> On Wed, Apr 12, 2017 at 8:06 PM Andrew Musselman <
> andrew.mussel...@gmail.com>
> wrote:
>
> > Okay consider this vote cancelled.
> >
> > On Wed, Apr 12, 2017 at 8:02 PM Andrew Palumbo 
> wrote:
> >
> >> The line that I suggested the other day:
> >>
> >>
> >> mvn -Pmahout-release,apache-release,viennacl,hadoop2 release:prepare
> >> release:perform
> >>
> >>
> >> doesn't seem to have activated the viennacl profile
> >>
> >> 
> >> From: Andrew Palumbo 
> >> Sent: Wednesday, April 12, 2017 10:58:16 PM
> >> To: d...@mahout.apache.org
> >> Subject: Re: [VOTE] Apache Mahout 0.13.0 Release Candidate
> >>
> >>
> >> off the top of my head i dont know if it is a regression.   My guess is
> >> that they were missing before.  I think that this may have something to
> do
> >> with activating the profile -Pviennacl at release time.
> >>
> >> 
> >> From: Andrew Musselman 
> >> Sent: Wednesday, April 12, 2017 10:48:13 PM
> >> To: d...@mahout.apache.org; u...@mahout.apache.org
> >> Subject: Re: [VOTE] Apache Mahout 0.13.0 Release Candidate
> >>
> >> Is it a regression or were they missing before, do you know?
> >>
> >> On Wed, Apr 12, 2017 at 7:42 PM Andrew Palumbo 
> >> wrote:
> >>
> >> >
> >> > It looks like we're missing some jars from the binary distro:
> >> >
> >> >
> >> > bin
> >> >
> >> > mahout-integration-0.13.0.jar
> >> >
> >> > confmahout-math-0.13.0.jar derby.log
> >> >  mahout-math-scala_2.10-0.13.0.jar docs
> >> > mahout-mr-0.13.0.jar examples
> >> > mahout-mr-0.13.0-job.jar flink
> >> >  mahout-spark_2.10-0.13.0-dependency-reduced.jar h2o
> >> >  mahout-spark_2.10-0.13.0.jar lib
> >> >  metastore_db LICENSE.txt NOTICE.txt
> >> > mahout-examples-0.13.0.jar  README.md
> mahout-examples-0.13.0-job.jar
> >> > viennacl mahout-hdfs-0.13.0.jar  viennacl-omp
> >> >
> >> > 
> >> > From: Andrew Musselman 
> >> > Sent: Tuesday, April 11, 2017 12:05 PM
> >> > To: u...@mahout.apache.org; d...@mahout.apache.org
> >> > Subject: Re: [VOTE] Apache Mahout 0.13.0 Release Candidate
> >> >
> >> > I've checked hashes and sigs, and run a build with passing tests for
> >> > vanilla, viennacl, and viennacl-omp profiles.
> >> >
> >> > The spark shell runs the SparseSparseDrmTimer.mscala example in the
> >> binary
> >> > build and all three source profiles; I saw the GPU get exercised when
> >> > running the viennacl profile from source, and saw all cores on the CPU
> >> get
> >> > exercised when running the viennacl-omp profile from source.
> >> >
> >> > So far I'm +1 (binding).
> >> >
> >> >
> >> >
> >> > On Tue, Apr 11, 2017 at 8:55 AM, Andrew Musselman <
> >> > andrew.mussel...@gmail.com> wrote:
> >> >
> >> > > This is the vote for release 0.13.0 of Apache Mahout.
> >> > >
> >> > > The vote will be going for at least 72 hours and will be closed on
> >> > Friday,
> >> > > April 17th, 2017 or once there are at least 3 PMC +1 binding votes
> >> > (whichever
> >> > > occurs earlier).  Please download, test and vote with
> >> > >
> >> > > [ ] +1, accept RC as the official 0.13.0 release of Apache Mahout
> >> > > [ ] +0, I don't care either way,
> >> > > [ ] -1, do not accept RC as the official 0.13.0 release of Apache
> >> Mahout,
> >> > > because...
> >> > >
> >> > >
> >> > > Maven staging repo:
> >> > >
> >> > > *
> >> >
> >>
> 

Re: Check if parameter is explicitly set

[Karl Heinz Marbaise]

Hi,

On 13/04/17 02:05, András Kerekes wrote:

Hi,

I'm working on a Maven plugin and I'd like to check whether a parameter for
a Mojo has been explicitly set by the user (via POM), or it contains the
default value. Is there a way to do this?


Maybe I misunderstand a thing but why do you need to distinguish between 
those two? Isn't that why defaultValue exist?


Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org