Github user olamy commented on the pull request:
https://github.com/apache/maven-scm/pull/21#issuecomment-205680496
pr merged.
Thanks!!
@batmat can you close the pr?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user asfgit closed the pull request at:
https://github.com/apache/maven-scm/pull/9
---
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 ena
Hi Andreas
Thank you for answering. I did have a look at a couple of other plugins,
but I dont understand quite why they work or how. Also each do things
differently and they do things change in different versions and
documentations get deprecated and such, so there are many variables to
try
Am 2016-04-04 um 22:07 schrieb Michael Osipov:
Am 2016-04-04 um 21:51 schrieb Thomas Finneid:
Hi
I am looking into developing a maven plugin for a Scala testing
framework named ScalaCheck.
I was wondering if there is any up to date articles or such, that
explain the main concepts of maven inte
Hi Thomas,
One way to learn how things roll is to find an existing plugin that does
something related to what you are trying to do and check the sources there.
Many of the plugins developed here in the Apache Maven project are not too
complex and might help you finding what you look for. Same goes
Am 2016-04-04 um 21:51 schrieb Thomas Finneid:
Hi
I am looking into developing a maven plugin for a Scala testing
framework named ScalaCheck.
I was wondering if there is any up to date articles or such, that
explain the main concepts of maven internals, its archtecture, work
separation between
Hi
I am looking into developing a maven plugin for a Scala testing
framework named ScalaCheck.
I was wondering if there is any up to date articles or such, that
explain the main concepts of maven internals, its archtecture, work
separation between modules, how it fits together in the build p
Looks good I think.
/Anders
On Mon, Apr 4, 2016 at 9:45 PM, Karl Heinz Marbaise
wrote:
> Hi Anders,
>
> is this kind clear enough:
>
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
Hi Anders,
is this kind clear enough:
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.056s
[INFO] Finished at: Mon Apr 04 21:44:12 CEST 20
> Keeping the parameter as deprecated but having it issue an exception could
>> simplify for the users. WDYT?
>>
>
> Sure make sense ...so i will add the behaviour to the jar-plugin...
>
Great Karl! Please make sure the deprecated text clearly states that the
param is no more supported (deprecated
Hi,
On 4/4/16 8:59 PM, Anders Hammar wrote:
Forwarding my last comment to the mailing list instead of discussing it on
this specific ticket.
Good idea...prefered way...
It would go for any plugin parameter that we remove
now when we bump a plugin to v3.0.0 and can afford breaking backwards
Forwarding my last comment to the mailing list instead of discussing it on
this specific ticket. It would go for any plugin parameter that we remove
now when we bump a plugin to v3.0.0 and can afford breaking backwards
compatibility.
Keeping the parameter as deprecated but having it issue an excep
Github user rafaelodon commented on the pull request:
https://github.com/apache/maven-scm/pull/33#issuecomment-205296420
I'm really interested in this pull-request. Not being able to associate
workItem is definetely a huge obstacle to the maven release plugin in my
current project.
13 matches
Mail list logo
