Hi Tibor,
On 11/28/15 9:36 PM, Tibor Digana wrote:
..but I don't understand why you want to have the descriptor in sources jar?
So we could discuss why a site archive needs a descriptor? Why does a
javadoc archive should have a descriptor
(https://issues.apache.org/jira/browse/MJAVADOC-431).
IIUC, Maven is now supported by sdkman
But I still don't see how/where
Where is the Maven support for SDKMAN hosted, that we could contribute to?
Regards,
Hervé
Notice: old issue about this is https://issues.apache.org/jira/browse/MNG-5749
Le vendredi 27 novembre 2015 08:07:33 Marco Vermeulen
Am 2015-11-28 um 23:35 schrieb Tibor Digana:
For me the descriptor was always useless. Do you Karl, Michael mean that
this cofiguration does not work?
http://maven.apache.org/shared/maven-archiver/index.html#class_archive>>
It does not help because it is disabled (hardcoded) in Javadoc Plugin:
For me the descriptor was always useless. Do you Karl, Michael mean that
this cofiguration does not work?
http://maven.apache.org/shared/maven-archiver/index.html#class_archive>>
You did not mention Jira # in maven-source-plugin.
On Sat, Nov 28, 2015 at 11:15 PM, Michael Osipov
wrote:
> Am 20
Am 2015-11-28 um 21:36 schrieb Tibor Digana:
..but I don't understand why you want to have the descriptor in sources jar?
Is the plugin buggy or something or it is just arbitrary some reason found
for a release?
Please see MJAVADOC-431 and the PR but I consider them as special cases
and not wo
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-160335576
No worries. :-)
I am glad that you continue with this issue. Btw I finished previous fix in
surefire and I am trying to dig into this issue.
On Sa
Github user juherr commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-160335454
I got it for 5.13 and 5.14.2: like reporter, listener attribute has changed
too.
I will fix it asap.
I'm open for help with 5.14.3
---
If your proje
Github user juherr commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-160334856
Some artifacts was corrupted before. Now, they are the same than central.
For 5.14.3:
-
> [WARNING] The POM for org.testng:testng:jar:5.14.3 is
..but I don't understand why you want to have the descriptor in sources jar?
Is the plugin buggy or something or it is just arbitrary some reason found
for a release?
On Sat, Nov 28, 2015 at 7:14 PM, Karl Heinz Marbaise
wrote:
> Hi,
>
> at the moment the maven-source-plugin creates archives (sou
Am 2015-11-28 um 19:56 schrieb Karl Heinz Marbaise:
Hi Michael,
On 11/28/15 7:43 PM, Michael Osipov wrote:
Am 2015-11-28 um 19:14 schrieb Karl Heinz Marbaise:
Hi,
at the moment the maven-source-plugin creates archives (source archives)
which do not contain a maven descriptor ...
/META-INF/ma
Hi Michael,
On 11/28/15 7:43 PM, Michael Osipov wrote:
Am 2015-11-28 um 19:14 schrieb Karl Heinz Marbaise:
Hi,
at the moment the maven-source-plugin creates archives (source archives)
which do not contain a maven descriptor ...
/META-INF/maven//../pom.xml
/META-INF/maven//../pom.prope
Am 2015-11-28 um 19:14 schrieb Karl Heinz Marbaise:
Hi,
at the moment the maven-source-plugin creates archives (source archives)
which do not contain a maven descriptor ...
/META-INF/maven//../pom.xml
/META-INF/maven//../pom.properties
I would like to change the default behaviour to pr
Hi,
at the moment the maven-source-plugin creates archives (source archives)
which do not contain a maven descriptor ...
/META-INF/maven//../pom.xml
/META-INF/maven//../pom.properties
I would like to change the default behaviour to produce this maven
descriptor...in source archives .
Hi,
We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12331499
There are several issue open:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
Staging repo:
https://re
14 matches
Mail list logo
