I agree with Hervé and others that javadoc-plugin 2.10 is too untested to
be put into the ASF pom yet.
So we to respin the release, because the tag has 2.10 in it.
Den 24 sep 2014 05:56 skrev Hervé BOUTEMY herve.bout...@free.fr:
-1 to upgrading m-javadoc-p to 2.10: seems someone really needs to
GitHub user miyajan opened a pull request:
https://github.com/apache/maven-surefire/pull/48
SUREFIRE-1098 Fix runOrder=balanced is not working
http://jira.codehaus.org/browse/SUREFIRE-1098
The first getConfigChecksum in executeProvider is calculated with empty
properties.
I will cancel and respin at some point today.
On Wed, Sep 24, 2014 at 2:02 AM, Dennis Lundberg
dennisl.apa...@gmail.com wrote:
I agree with Hervé and others that javadoc-plugin 2.10 is too untested to
be put into the ASF pom yet.
So we to respin the release, because the tag has 2.10 in it.
Here's the link for this week:
https://plus.google.com/u/0/b/113247990055413254822/events/cj2viqoundr31t42n57tp871qm8
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
Hi,
we solved 9 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212version=20323
* [MCHANGES-343] Update maven-reporting-impl to 2.3
* [MCHANGES-342] Removed dependency
plexus-container-default:1.0-alpha-9-stable-1
* [MCHANGES-341] Externalize JIRA server timeout values to
We decided to try this again.
On Mon, Sep 22, 2014 at 5:27 PM, Benson Margulies bimargul...@gmail.com wrote:
Hi,
Here is release 15 of the POM we maintain for the entire ASF. The
changes since release 14 can be seen here:
Hi,
Here is release 15 of the POM we maintain for the entire ASF. The
changes since release 14 can be seen here:
http://svn.apache.org/viewvc/maven/pom/tags/apache-15/pom.xml?r1=HEADr2=1575044diff_format=h
Staging repo:
https://repository.apache.org/content/repositories/orgapacheapache-1002
Hey,
we here was more meant as whether anyone wanted to jump in and fix
another issue before I would do the release. Not as in let US do this so I
do not have to ;-) .
Regards
Mirko
--
Sent from my mobile
On Sep 23, 2014 9:47 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi Mirko,
Hello
GitHub user Batmat opened a pull request:
https://github.com/apache/maven-scm/pull/21
SCM-781: Added a recursive goal to validate scm URL.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Batmat/maven-scm SCM-781
Alternatively
Hi,
I am using ants maven tasks to converts my existing ant’s build script to
refer to maven repository for dependency management instead of keeping a
copy of libraries in the project. Using as follows.
artifact:remoteRepository id=myrepository url=
http://x/artifactory/fmw-virtual/
Hello,
I wanted to submit a patch that I made to the maven-scm-plugin for sending
files to SCM in a batch fashion. I tried to submit it to
http://jira.codehaus.org/browse/MSCMPUB (the URL specified at
http://maven.apache.org/plugins/maven-scm-publish-plugin/issue-tracking.html)
but I wasn't able
Hi,
sha1 checked Ok...
tested with Maven 2.2.1, 3.0.5, 3.1.1,3.2.1, 3.2.2, 3.2.3
via mvn -Prun-its clean verfiy
no issues found ...
Site ok as well...
so +1 from me.
Kind regards
Karl-Heinz Marbaise
On 9/24/14 3:23 PM, Mirko Friedenhagen wrote:
Hi,
we solved 9 issues:
+1 from me
Kind regards
Karl-Heinz Marbaise
On 9/22/14 8:58 AM, Karl Heinz Marbaise wrote:
Hi,
We solved N issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11128version=18533
There are still a couple of issues left in JIRA:
Hi,
Sorry if this isn't worthy of the developers list but I believe that it is
appropriate.
We are trying to stand up a highly-available Maven repository that is protected
by an SSO solution using Basic Auth over SSL. The architecture is as follows:
1.)Maven clients connect over
There is yet another http connector implementation [1] (the more the
merrier, right? :-) ). It is based on square okhttp client and is pretty
simple. I didn't try redirects, but auth credentials are not scoped to a
specific url, so there is a chance this connector may work.
This is the connector
Hi Igor,
I am trying to use this okhttp-based wagon, but it is giving me an odd
error that I have not seen before.
I tried different versions of Maven and Java (7 and 8), and I went
through the code to see if I could find any configuration properties
that I needed to set in a
What maven version do you use?
On September 24, 2014 9:00:00 PM EDT, Mark Nelson mark.x.nel...@oracle.com
wrote:
Hi Igor,
I am trying to use this okhttp-based wagon, but it is giving me an odd
error that I have not seen before.
I tried different versions of Maven and Java (7 and 8), and I went
I tired 3.2.1 and 3.2.3.
Mark Nelson | Architect | 61.2.9491.1177
Platform Engineering
Oracle Development
http://redstack.wordpress.com/
Oracle BPM Suite 11g: Advanced BPMN Topics
by Mark Nelson and Tanya Williams
http://bit.ly/UbNKLD
On 9/25/2014 11:09 AM, Igor Fedorenko wrote:
What maven
We updated 0.13.1 of the connector to use Aether 1.0, but 3.2.3 still uses
0.9.0.M2 so you'll need to use the 0.13.0 version of the connector. There were
API changes in Aether.
On Sep 24, 2014, at 9:11 PM, Mark Nelson mark.x.nel...@oracle.com wrote:
I tired 3.2.1 and 3.2.3.
Mark Nelson |
Thanks for the suggestion, but it still gives the same error.
Mark Nelson | Architect | 61.2.9491.1177
Platform Engineering
Oracle Development
http://redstack.wordpress.com/
Oracle BPM Suite 11g: Advanced BPMN Topics
by Mark Nelson and Tanya Williams
http://bit.ly/UbNKLD
On 9/25/2014 12:04 PM,
Same error with 0.12.0 - maybe I am missing some necessary configuration?
All I did was add a build/extension with the GAV for this wagon.
Is there anything else I need to do to enable it?
Mark Nelson | Architect | 61.2.9491.1177
Platform Engineering
Oracle Development
No, you are not missing anything. We don't usually use the connector as
build extension and there appear some sisu/guice related bugs that
result in the exception you see.
I just released version 0.12.1 of the connector, which appears to work
with maven 3.2.3 and I assume will work with earlier
Thanks a lot Igor,
I tried this release, and I am still getting authorization errors (see
below). In order to see what is going on, I have been using a HTTP
proxy (fiddler) to see all the requests, headers, cookies, etc. To do
that, I need to tell Maven to ignore the SSL, which I have been
From the javax.net.debug output, it looks like it is getting redirected
to the authentication server, which sends back a 401, and then it does
not send credentials, but rather just prints an error and gives up.
Mark Nelson | Architect | 61.2.9491.1177
Platform Engineering
Oracle Development
24 matches
Mail list logo