Hi Kristian,
I have short question
You seemed to have released a new version of plexus-archiver 2.5 but in
JIRA there is one issue related with plexus-archiver 2.5 not solved ?
Kind regards
Karl-Heinz Marbaise
On 9/23/14 7:18 AM, krosenv...@apache.org wrote:
Author: krosenvold
Date:
Hi Kristian,
an other question concerning plexus-io...
I have taken a look into jira but unfortunately there is no issue
related to plexus-io 2.0.9, 2.0.11, 2.0.12...
And only a single issue to 2.0.10 ?
Do 2.0.9, 2.0.11 never made to be released...does this mean only that
single issue has
Is it safe/good to upgrade to m-javadoc-p v2.10, as there has been several
reported issues [1] [2] [3]? We don't want to cause a lot of issues for
apache projects.
[1] http://jira.codehaus.org/i#browse/MJAVADOC-407
[2] http://jira.codehaus.org/i#browse/MJAVADOC-408
[3]
Not any more :) https://jira.codehaus.org/browse/PLXCOMP/fixforversion/20630
2.5 has full commons-compress support, java 7 file attribute support.
Kristian
2014-09-23 8:42 GMT+02:00 Karl Heinz Marbaise khmarba...@gmx.de:
Hi Kristian,
I have short question
You seemed to have released
wow, including tar from common-compress??
-D
On Mon, Sep 22, 2014 at 11:52 PM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
Not any more :)
https://jira.codehaus.org/browse/PLXCOMP/fixforversion/20630
2.5 has full commons-compress support, java 7 file attribute support.
Hi,
does someone know where to look cause currently the site staging job
seemed to blocked and waiting for 11 hours
http://ci.apache.org/builders/maven-site-staging
Kind regards
Karl-Heinz Marbaise
-
To unsubscribe,
Hi Karl-Heinz,
Karl Heinz Marbaise wrote:
Hi,
does someone know where to look cause currently the site staging job
seemed to blocked and waiting for 11 hours
http://ci.apache.org/builders/maven-site-staging
Maybe it waits for manual input on stdin (e.g. new password)?
- Jörg
Yup. Everything. I even just created
https://jira.codehaus.org/browse/PLXCOMP-240 to document it :)
It even seems like the compression is quite a lot better with cc.
Kristian
2014-09-23 8:54 GMT+02:00 Dan Tran dant...@gmail.com:
wow, including tar from common-compress??
-D
On Mon, Sep
At least all the versions are released now :) I might be able to add
some issues too
Kristian
2014-09-23 8:46 GMT+02:00 Karl Heinz Marbaise khmarba...@gmx.de:
Hi Kristian,
an other question concerning plexus-io...
I have taken a look into jira but unfortunately there is no issue
Github user Batmat closed the pull request at:
https://github.com/apache/maven-scm/pull/20
---
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
And soft link preserved after unpack??
Thanks
On Tuesday, September 23, 2014, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
Yup. Everything. I even just created
https://jira.codehaus.org/browse/PLXCOMP-240 to document it :)
It even seems like the compression is quite a lot better
I'm working on full symlink support for tar/zip for 2.5.1. There are a
few patches in jira for this already.
Kristian
2014-09-23 9:57 GMT+02:00 Dan Tran dant...@gmail.com:
And soft link preserved after unpack??
Thanks
On Tuesday, September 23, 2014, Kristian Rosenvold
+1 on these changes... you could go further... but if you are only prepared
to bite off that much right now it is better than nothing!
On 22 September 2014 22:27, Benson Margulies bimargul...@gmail.com wrote:
Hi,
Here is release 15 of the POM we maintain for the entire ASF. The
changes since
I guess I am conservative about this pom; it's not very hard for
anyone who wants a newer version of something to configure it, and if
I start respinning some other plugin will go release itself in the
middle. If folks really want things in here, perhaps the plugin
release procedure should include
I agree with conservative in this pom.
My view is that we should soak plugin updates in the Maven project pom for
at least 5 releases or 1 month (whichever is sooner) before promoting up
to the ASF parent.
In the case of GIT I am happy to make an exception as it can block others
from
My view is that we should soak plugin updates in the Maven project pom for
at least 5 releases or 1 month (whichever is sooner) before promoting up
to the ASF parent.
I agree and that's why I asked about m-javadoc-p v2.10 which was just
recently released and it seems as it has cause some
Oh, I got it _backwards_. Let's see what other people think.
On Tue, Sep 23, 2014 at 7:13 AM, Anders Hammar and...@hammar.net wrote:
My view is that we should soak plugin updates in the Maven project pom for
at least 5 releases or 1 month (whichever is sooner) before promoting up
to the ASF
Hello everybody,
there are 8 closed issues in this plugin, so maybe we should do a
release of this soon?
Regards
Mirko
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
Hi Mirko,
Hello everybody,
there are 8 closed issues in this plugin, so maybe we should do a
release of this soon?
We??...You can start a release if you like i don't see any reason
why not starting a release...there have been solved several issues which
make it worth to do a
Thank You @Stuart McCulloch (and others that helped me in this topic)! Your
explanation is very valuable and resolved my problems :)
Regards,
animator.
--
View this message in context:
-1 to upgrading m-javadoc-p to 2.10: seems someone really needs to work on
2.10.1 because 2.10 is causing real problems for a lot of people
therefore the actual choice to stay with 2.9.1 in ASF-15 is a great choice :)
Regards,
Hervé
Le mardi 23 septembre 2014 13:13:48 Anders Hammar a écrit :
Le lundi 22 septembre 2014 18:14:52 Kristian Rosenvold a écrit :
dependency
groupIdcom.google.code.findbugs/groupId
artifactIdjsr305/artifactId
version3.0.0/version
scopeprovided/scope
/dependency
The reason for this is that the findbugs
22 matches
Mail list logo
