+1
Regards,
Gabriel
El mié., 8 de may. de 2019 a la(s) 15:25, Robert Scholte (
rfscho...@apache.org) escribió:
> Hi,
>
> The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to
Remote repositories should always provide a model 4.0.0 pom, otherwise
tools including all currently known Maven versions will not work. The
first check is if the modelVersion is 4.0.0, otherwise Maven will simply
stop working.
Since the pom on the system is copied/uploaded as-is, there's
Ok ...
And what's the:
4.0.0
And the:
xmlns="http://maven.apache.org/POM/4.0.0;
About?
One should think that a system like Nexus should be able to be extended to
support multiple POM Versions ...
So as this metadata adds new features, wouldn't this simply be a
modelVersion=4.1.0?
Chris
Hi,
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12344629
There are still a couple of issues left in JIRA:
+1
T
+1
regards,
Hervé
Le mercredi 8 mai 2019, 20:25:14 CEST Robert Scholte a écrit :
> Hi,
>
> The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all
+1
/Anders (mobile)
Den ons 8 maj 2019 20:25Robert Scholte skrev:
> Hi,
>
> The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects,
On Wed, 08 May 2019 09:32:42 +0200, Christofer Dutz
wrote:
Well depending on how much metadata should be added ...
Guess we already have a lot of stuff in the pom.xml which is considered
metadata ... having some additional optional elements shouldn't break
anything (I think)
This part
Hi,
+1 from me.
Kind regards
Karl Heinz Marbaise
On 08.05.19 20:25, Robert Scholte wrote:
Hi,
The Apache Maven project consist of about 100 (sub)projects. Due to the small
number of volunteers and the huge amount of code to maintain we're missing
enough space to make real progress on all
Hi,
The Apache Maven project consist of about 100 (sub)projects. Due to the small
number of volunteers and the huge amount of code to maintain we're missing
enough space to make real progress on all these projects, including our
ambitious ideas for the next major version(s) of Maven itself.
To
It's dependency:resolve-plugins that's wrong. What you can do is run a
Maven build with the -X flag and look at the beginning of the
maven-jar-plugin execution. There you should see the resolved tree of the
plugin's dependencies.
/Anders
On Wed, May 8, 2019 at 11:18 AM Eric Lilja wrote:
> Hi,
Hi, and thanks for the answers! We (and many others I'm sure) are happy to
see new releases as soon as possible, of course :-)
Anders: Thanks for the workaround, I implemented it in our corporate pom
for maven-jar-plugin and maven-source-plugin, plus maven-javadoc-plugin.
Then I wiped out
Well depending on how much metadata should be added ...
Guess we already have a lot of stuff in the pom.xml which is considered
metadata ... having some additional optional elements shouldn't break anything
(I think)
But adding some additional files exclusively used for metadata might also be
13 matches
Mail list logo
