question: is upgrading only a question of changing dependency version? or does
it require code change?
and if it requires code change, can we do it with reasonable reflection or is
it really too much change?
because if we can let the end user upgrade his config (and better document), we
would g
GitHub user mbocek opened a pull request:
https://github.com/apache/maven-surefire/pull/79
[SUREFIRE-1135] Improve ignore message for TestNG
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mbocek/maven-surefire master
Alternativ
I would pretty much abandon anything pre-Java 6 at this point and
start moving towards Java 7 soon. The checkstyle plugin right now has
three open releases with only the third being really useful ("upgrade
to latest checkstyle") and given the previous release cadence it makes
me fear that this rele
Hi Robert,
On 1/13/15 9:49 PM, Robert Scholte wrote:
Hi Karl-Heinz,
you've set the prerequisite for the parent and not for the plugin.
Prerequisites aren't inherited, so this commit doesn't have the expected
effect.
Outch...correct...fixed it...Thanks for the hint Robert.
Kind regards
Karl
Hi Karl-Heinz,
you've set the prerequisite for the parent and not for the plugin.
Prerequisites aren't inherited, so this commit doesn't have the expected
effect.
thanks,
Robert
Op Tue, 13 Jan 2015 21:24:16 +0100 schreef :
Repository: maven-scm
Updated Branches:
refs/heads/master 06c3954
Github user mbocek closed the pull request at:
https://github.com/apache/maven-surefire/pull/70
---
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
@Dennis, I committed the fix, Please verify
@maven dev, this vote is cancelled
@Karl, thank you for last release work, I will go thru the release next
time
-Dan
On Tue, Jan 13, 2015 at 12:52 AM, Dan Tran wrote:
> Thanks Dennis, the typo is already fixed before the vote.
>
> I will rename t
Hoping this is not the end of surefire/failsafe plugin nor Maven.
Yeah, my impression from Maven is that it is "static" however introduced
regular practices, the users hit us with many requests.
For me it means that I try to handle the request immediately in JIRA and
resolve it. It gives me chanc
Historically we have implemented all sorts of stuff into surefire,
without giving the user appropriate hooks to control the behaviour for
herself. One such very simple example is an extensibility point to
allow the user to run tests in a specific order they can decide
themselves. Another is opening
I think my question was not clear. I do not understand the problem you
are trying to solve, i.e. user and/or plugin developer usecases that are
not (well) supported with the current APIs. This is why I am asking for
some representative examples that highlight the problem. I do not
suggest or imply
Igor, can we join our visions and design together regarding compiler and
surefire ?
I guess we need to write a list of requirements. Later we will find possible
solutions for each + API.
--
View this message in context:
http://maven.40175.n5.nabble.com/Plugable-Softcoded-Customized-Maven-Plugin
Hi Igor,
I know that you are working on JDT and you probably want to synchronize your
activity with ours, but we don't have access API yet. Everything is in our
heads. We have only the standard surefire-api.
As we speak via email with Kristian, our current problem problem is the
injection and des
Do you think you can give a couple of representative examples that
explain what you are trying to achieve?
--
Regards,
Igor
On 2015-01-13 9:33, Tibor Digana wrote:
Hi All,
We want to prepare an experimental release of maven-surefire-plugin
customizing the plugin behavior. Basically we want to
Hi All,
We want to prepare an experimental release of maven-surefire-plugin
customizing the plugin behavior. Basically we want to uncover open API and
we expect a feedback from Maven users group.
We have received many configuration requests in this plugin which increased
JIRA issues.
We believe t
Github user cstamas commented on the pull request:
https://github.com/apache/maven-indexer/pull/10#issuecomment-69743397
+1
---
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
enable
Github user cstamas commented on the pull request:
https://github.com/apache/maven-indexer/pull/11#issuecomment-69743162
+1
---
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
enable
Github user carlspring commented on the pull request:
https://github.com/apache/maven-indexer/pull/11#issuecomment-69730289
Hi,
This code change looks good to me, thanks!
Kind regards,
Martin
---
If your project is set up for it, you can
Thanks Dennis, the typo is already fixed before the vote.
I will rename the passphraseServerKey to passphraseServerId per your
suggestion
-D
On Tue, Jan 13, 2015 at 12:08 AM, Dennis Lundberg
wrote:
> Hi,
>
> I had a quick look at the fix for
> http://jira.codehaus.org/browse/MGPG-31
> at
>
> h
Hi,
I had a quick look at the fix for
http://jira.codehaus.org/browse/MGPG-31
at
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/AbstractGpgMojo.java?r1=1647942&r2=1647941&pathrev=1647942
Unfortunately the new parameter is misspelled:
"g
19 matches
Mail list logo
