Looks like https://issues.apache.org/jira/browse/ARCHETYPE-528
With mirror this seems to work as expected, but without is uses Central to
look for the catalog.
So that's a bug.
Robert
On Mon, 22 May 2017 17:53:36 +0200, Amélie Deltour
wrote:
(the catalog is located at
http://artifacto
I can't remember seeing ITs for maven-metadata.xml in the MRM project.
There is code which should handle these files, but it could be that this
is not yet complete.
So I would start with MRM itself, trying to prepare an IT.
Probably not a satisfying answer, but it's the best I can do.
thanks,
good links
yes, with this in mind, "api" is required for artifactId but should not be
added to module name: good catch, and good experience to share because that
was not so obvious
Regards,
Hervé
Le samedi 27 mai 2017, 18:43:22 CEST Robert Scholte a écrit :
> There's no experience with this ye
There's no experience with this yet.
Stephen Colebourne has written to related blogs: module naming[1] and
modules are not artifacts[2]
which might suggest that "api" should not be added.
I do understand the addition of "api". And to make it worse, this is
probably the most important artifac
Hi,
currently I'm trying to fix some issues in versions-maven-plugin...
At the moment I want to have multiple artifacts as SNAPSHOT's in the
repo...I have created an appropriate maven-metadata.xml file etc.
But it looks like that MRM does not handle the defined
maven-metadata.xml to simulate h
second option committed in another branch:
option 1:
http://git-wip-us.apache.org/repos/asf/maven-resolver/commit/d1724eb7
option 2:
http://git-wip-us.apache.org/repos/asf/maven-resolver/commit/17f804d7
The only part that I'm not sure in option 2 is org.apache.maven.resolver.api >
org.apache.ma
I think I would change the following 2:
org.apache.maven.resolver.connector_basic >
org.apache.maven.resolver.connector.basic (in line with transport)
org.apache.maven.resolver.test_util > org.apache.maven.resolver.testutil
it's a matter of taste: the underscores look kind of weird, but that'
please review and second if you think it's ok:
http://git-wip-us.apache.org/repos/asf/maven-resolver/commit/d1724eb7
Regards,
Hervé
Le samedi 27 mai 2017, 13:24:47 CEST Hervé BOUTEMY a écrit :
> he he, Java 9 is really coming, with associated real world questions.
>
> Maven Artifact Resolver is
On Sat, 27 May 2017 13:24:47 +0200, Hervé BOUTEMY
wrote:
he he, Java 9 is really coming, with associated real world questions.
Maven Artifact Resolver is one of rare Maven components that has a
chance to
become a collection Java 9 modules, since it was written quite recently
and is
pure
he he, Java 9 is really coming, with associated real world questions.
Maven Artifact Resolver is one of rare Maven components that has a chance to
become a collection Java 9 modules, since it was written quite recently and is
pure new code as a result of Maven 3 refactoring, then does not have s
Hi,
I've got a question from Remi Forax if we could add Java9 module
descriptors to this project.
This will be one of the first which can provide such descriptors since it
has no required dependencies other then its own and its package structure
seems valid with the new Java9 rules.
We ha
Hi,
No objection from me, thanks for keeping the ball rolling.
I tried to improve documentation by adding some useful links to other related
components [1]: I think the current state is better and ok for a release.
One key question now is about Aether wiki content [2]: should we copy it? In a
12 matches
Mail list logo
