I expect we could run the unit test suite on JDK 6 / 7 / 8 in parallel with
7/8 specific code being used for the JDK that do support them, so I wonder
such a multi-module setup would work in this scenario, or would need yet
another maven module for tests :'(
2015-04-12 23:33 GMT+02:00 Hervé BOUTEM
Hi,
here is my +1...
one binding VOTE missing..
Kind regards
Karl Heinz Marbaise
On 4/10/15 8:30 AM, Karl Heinz Marbaise wrote:
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12330876
There are still a couple of issues left in JIRA:
Hi,
here is my + 1
two more binding VOTE's missing...
Kind regards
Karl Heinz Marbaise
On 4/10/15 8:07 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318120&version=12331744
There are still a couple of issues left i
notice: I made some tests, and animal-sniffer detects internals API use
then failOnWarning will not be useful for people already using animal sniffer
Regards,
Hervé
Le mardi 17 février 2015 00:04:37 Robert Scholte a écrit :
> Hi Alan,
>
> I've added a flag called failOnWarning (default:true), a
last week, during DevoxxFR, Arnaud and I showed maven-jdeps-plugin: as
expected, a lot of users didn't know about this tool
So for sure, having this plugin and a report would help
Then there is the question of: what should the report look like?
Should it be a simple stdout dump of command line re
this guy is right: there is a typo in maven-parent pom's m-release-p
configuration
But in fact, I'm completely lost with the current state:
maven-release-plugin
2.5.1
true
apache-release
deploy
fa
I'm not actually sure of what problem you're trying to solve here.
On Sat, Apr 11, 2015 at 6:49 AM, Mirko Friedenhagen <
mfriedenha...@apache.org> wrote:
> Hello,
>
> we now have pushChanges and localCheckout in the release:prepare goal.
> IMO pushing commits and tags after a successful release:p
On Sat, Apr 11, 2015 at 7:06 PM, Mirko Friedenhagen wrote:
> Stephen,
>
> this does sound even more reasonable. release.properties is deleted at the
> end of perform, so the goal could only rely on information in the pom.
>
>
Doesn't release:clean effectively do that?
> Regards
> Mirko
> --
>
Please upgrade plugin versions
animal-sniffer-maven-plugin:1.14
The signature version in JDK 1.5 due to plugins however mvn core is 1.6.
TODO: The SUREFIRE POM should not override animal version.
maven-checkstyle-plugin:2.15
buildnumber-maven-plugin:1.3
maven-doap-plugin:1.2
I don't know who nee
Le samedi 11 avril 2015 21:42:50 Paul Benedict a écrit :
> I've been giving this subject lots of thought in some of spare time. IMO,
> the most straightforward way of meeting the requirement of the MVJAR is to
> break up one's JAR project into separate modules. One module would contain
> the versio
+1
Regards,
Hervé
Le vendredi 10 avril 2015 08:30:58 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&ve
> rsion=12330876
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira
I worked on MPOM-72, but was hit by MPIR-300
when removing version from plugins in reporting section, the MPIR plugin does
not support looking into pluginManagement...
seems like we should release MPIR with MPIR-300 fixed before releasing maven-
parent
(this does not affect ASF parent pom, sinc
I am happy to discontinue mvn 2.2.1 in Surefire 3.0 asap.
It's a little bit tricky to make fine tuning of the build mvn 2.2.1, but
hopefully all surefire builds pass.
--
View this message in context:
http://maven.40175.n5.nabble.com/Time-to-remove-maven-2-2-1-builds-tp5832571p5832597.html
Sent
We need project components, project versions permissions from 2.) and issue
management from 1.).
--
View this message in context:
http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Codehaus-to-Apache-on-April-4th-tp5830262p5832593.html
Sent from the Maven Developers mailing l
Unless someone objects with a good reason, I'll delete all the jenkins
maven 2.2.1 build jobs.
Kristian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I suppose every ASF project is increasing its Maven prerequisite
(and if not, perhaps we can help :) )
I'll open a Jira issue for ASF parent about this to make it clear and do
corresponding cleanup
Regards,
Hervé
Le dimanche 12 avril 2015 11:18:40 Sean Busbey a écrit :
> Correct, we use ASF pa
Correct, we use ASF parent and not Maven parent. Also correct that we
require a minimum maven version of 3.0.4 and I think Christopher recently
mentioned increasing that further to stay ahead of planned eol.
--
Sean
On Apr 12, 2015 10:41 AM, "Hervé BOUTEMY" wrote:
> AFAIK, they use ASF parent,
AFAIK, they use ASF parent, not Maven parent
and not sure they require Maven 2.2.1 support: I had a look at Accumulo and
their minimum Maven version is 3.0.4
Regards,
Hervé
Le dimanche 12 avril 2015 07:14:47 Karl Heinz Marbaise a écrit :
> Hi Hervé,
>
> On 4/12/15 3:05 AM, Hervé BOUTEMY wrote
18 matches
Mail list logo
