Hi,
My guess is that javadoc:javadoc holds the record[1].
For remote systems a timeout parameter makes sense.
I would expect that users are familiar with the parameter pages.
If you start introducing an environment variable, it'll become a hidden
feature only visible to those few who read
Op Thu, 18 Sep 2014 23:00:16 +0200 schreef Karl Heinz Marbaise
khmarba...@gmx.de:
Hi,
I have admit the setting of M2_HOME did the trick...which looks a little
bit strange for me...
So maven 3.0.5 worked...but I have checked Maven 2.2.1 where integration
tests of maven-release-plugin
-1 due to the failure with M2.2.1 as reported by Karl-Heinz (great catch!)
The fix is trivial[1], and worth including in this release.
Robert
ps. I was amazed that the invalid hint-attribute was accepted
Sure we should move to Annotations, but that requires MRELEASE-703 to be
fixed
Can you commit the fix? I am on a train.
On Sep 19, 2014 11:44 AM, Robert Scholte rfscho...@apache.org wrote:
-1 due to the failure with M2.2.1 as reported by Karl-Heinz (great catch!)
The fix is trivial[1], and worth including in this release.
Robert
ps. I was amazed that the invalid
is it a bug to file?
Thanks
-D
On Thu, Sep 18, 2014 at 4:55 PM, Benson Margulies bimargul...@gmail.com
wrote:
I thought it was strange, too. Background: I checked out the trunk of
maven-release, built, and got that error. I scratched my head for a
day, and then a vague memory caused me to
Hi,
Hi,
My guess is that javadoc:javadoc holds the record[1].
If i count correctly 98 parameters..wow...i didn't expect being so much...
For remote systems a timeout parameter makes sense.
I would expect that users are familiar with the parameter pages.
Yes this is the source of
Thanks for your feedback, so I will add parameters.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Fri, Sep 19, 2014 at 9:16 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi,
after diving a little bit more i found the following issues...
prerequisites:
Offline (no internet connection) and a clean local repository:
mvn -Prun-its clean verify
so you got failures within the intergration test based on missing
artifacts like:
[ERROR] The following builds
I made a JIRA to cover Robert's commit.
On Fri, Sep 19, 2014 at 2:19 PM, Dan Tran dant...@gmail.com wrote:
is it a bug to file?
Thanks
-D
On Thu, Sep 18, 2014 at 4:55 PM, Benson Margulies bimargul...@gmail.com
wrote:
I thought it was strange, too. Background: I checked out the trunk of
I'm pretty sure this is still an issue for every project.
IIRC this is exactly the reason why Stephen thought of including/moving
the mock repository manager to the maven-invoker-plugin.
That much better to maintain than including all the extraArtifacts.
btw, with Offline (no internet
Hi,
Here is a respin of 2.5.1. This includes one more commit that allows
builds on Maven 2.2.1 of the plugin.
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144version=20578
There are still a couple of issues left in JIRA:
Because of the rise of Gradle usage to its inclusion as the build tool in
Android Studio, there are more and more artifacts making their way into
Maven Central whose POMs contain elements that do not conform to Maven
expectations.
A good example is this POM:
On Sep 19, 2014, at 9:35 PM, William Ferguson william.fergu...@xandar.com.au
wrote:
Because of the rise of Gradle usage to its inclusion as the build tool in
Android Studio, there are more and more artifacts making their way into
Maven Central whose POMs contain elements that do not conform
+1 for checking when uploading to Central.
Regards
Mirko
--
Sent from my mobile
On Sep 20, 2014 4:22 AM, Jason van Zyl ja...@takari.io wrote:
On Sep 19, 2014, at 9:35 PM, William Ferguson
william.fergu...@xandar.com.au wrote:
Because of the rise of Gradle usage to its inclusion as the
14 matches
Mail list logo
