Re: Heads up, Plexus IO/Archiver is going Java 7

[Michael Osipov]

Am 2017-05-22 um 09:13 schrieb Plamen Totev:

Hi,

As the branch is now merged is there anything that blocks the release of
Plexus IO 3.0.0?


I need to do some more stuff like parent release, etc. It is in my 
pipeline. Will try to do this by the end of the week.


Michael


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: The maven-archetype-plugin paradox

[Amélie Deltour]

(the catalog is located at 
http://artifactory.mycompany.com/internal-releases/archetype-catalog.xml)

On 05/22/2017 05:52 PM, Amélie Deltour wrote:
Hi,

Thanks for the link, I could not find where this "archetype" repository was 
documented.

However, I tried to use the "archetype" repository earlier, and tried again, 
and I can't make it work.

With 2.4: mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate 
-DarchetypeGroupId=com.mycompany.archetype -DarchetypeArtifactId=myCustomArchetype 
-DarchetypeCatalog=http://artifactory.mycompany.com/internal-releases/
=> it works fine (that's what we used to do)

With 3.0: mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.0:generate 
-DarchetypeGroupId=com.mycompany.archetype 
-DarchetypeArtifactId=myCustomArchetype
=> does not work - I get "[WARNING] Specified archetype not found." and I am 
proposed the list of archetypes from Maven central
Tried with both 3.0 and 3.0.1.

Attached is my full settings.xml.

Can you explain what is wrong with these settings?
(or if this is not the right place to ask, please tell me where to ask)

Amélie

On 05/19/2017 09:54 PM, Robert Scholte wrote:

Hi Amélie,

first thank you for helping to us to improve this and to get more
information about the several use cases.

If you have a repository in the settings.xml, it must be inside a profile.
This would mean that it looks more like you have to do this:
https://maven.apache.org/archetype/maven-archetype-plugin/archetype-repository.html

Right now it is required to call the repository "archetype" which also
prevents Maven from going over all repositories and trying to fetch all
catalogs.

I assume the name "archetype" is not a real issue since you need to
activate a profile, but if there are good reasons to change this, we
should have another look at it.

thanks,
Robert

On Thu, 18 May 2017 16:58:47 +0200, Amélie Deltour
 wrote:



ARCHETYPE-520 (and ARCHETYPE-358) are indeed close to the problem I try
to describe, but not exactly the same.
These issues are about using the mirror configuration to access
archetype data, i.e. using
http://myrepo.mycompany/maven/archetype-catalog.xml instead of direct
access to http://repo1.maven.org/maven2/archetype-catalog.xml, but this
is still the Maven central catalog, just accessed through a mirror
instead of accessing it directly.

But my issue, and the issue behind most ARCHETYPE-519 comments, is not a
mirror issue, it is not either a CLI vs settings.xml issue, it is about
the ability to use an *alternative catalog* which is not published on
Maven central.

In my settings.xml I have several repositories defined:

   
 internal
 repository for internal artifacts
 http://myrepo.mycompany/internal
 ...
   
   
 central
 repository for external artifacts
 http://myrepo.mycompany/external
 ...
   



With 3.x it seems that the "remote" catalog uses the catalog located at
http://myrepo.mycompany/external/archetype-catalog.xml (which is a proxy
for Maven central catalog) but we need the catalog published at
http://myrepo.mycompany/internal/archetype-catalog.xml to be used as
well and this one is ignored.
That's to say, "remote" is interpreted as the "central" repository only,
and other repositories configured in settings.xml are ignored.

This is what I call an "alternative catalog" and I think it is a valid
use case for the plugin.
This was possible with the archetypeCatalog CLI parameter (giving the
catalog URL), and it is probably what the parameter was meant for.
But is not possible anymore with 3.x.
I agree the CLI parameter can be removed, *but* the other repositories
defined in settings.xml have to be taken into account when searching for
remote archetype catalogs.

Please confirm if my use case is valid - in that case I think
ARCHETYPE-519 should be reopend or I can open a new issue if you think
it is more appropriate.
Or I misunderstood / misconfigured something: if my Maven configuration
or usage is wrong I would be glad to understand what's wrong and why.

Thanks,

Amélie


On 05/16/2017 07:06 PM, Robert Scholte wrote:

Looks like ARCHETYPE-520[1] to me. I've created an integration-test for
it, so that should work with 3.0.1

The more I think about it, the more I'm convinced we should also remove
the archetypeCatalog parameter. Right now it is only causing confusion.
Does it still make sense to have "internal", which are in fact a small
set
of embedded archetypes, and they are old (and remote available as well)?
Aether/Artifact Resolver should solve the rest: use both remote and local
as everybody is used to. Want to only use local, then I guess you should
add --offline.

WDYT?

Robert

[1] https://issues.apache.org/jira/browse/ARCHETYPE-520

On Tue, 16 May 2017 13:02:11 +0200, Anders Hammar

Re: The maven-archetype-plugin paradox

[Amélie Deltour]

Hi,

Thanks for the link, I could not find where this "archetype" repository was 
documented.

However, I tried to use the "archetype" repository earlier, and tried again, 
and I can't make it work.

With 2.4: mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate 
-DarchetypeGroupId=com.mycompany.archetype -DarchetypeArtifactId=myCustomArchetype 
-DarchetypeCatalog=http://artifactory.mycompany.com/internal-releases/
=> it works fine (that's what we used to do)

With 3.0: mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.0:generate 
-DarchetypeGroupId=com.mycompany.archetype 
-DarchetypeArtifactId=myCustomArchetype
=> does not work - I get "[WARNING] Specified archetype not found." and I am 
proposed the list of archetypes from Maven central
Tried with both 3.0 and 3.0.1.

Attached is my full settings.xml.

Can you explain what is wrong with these settings?
(or if this is not the right place to ask, please tell me where to ask)

Amélie

On 05/19/2017 09:54 PM, Robert Scholte wrote:

Hi Amélie,

first thank you for helping to us to improve this and to get more
information about the several use cases.

If you have a repository in the settings.xml, it must be inside a profile.
This would mean that it looks more like you have to do this:
https://maven.apache.org/archetype/maven-archetype-plugin/archetype-repository.html

Right now it is required to call the repository "archetype" which also
prevents Maven from going over all repositories and trying to fetch all
catalogs.

I assume the name "archetype" is not a real issue since you need to
activate a profile, but if there are good reasons to change this, we
should have another look at it.

thanks,
Robert

On Thu, 18 May 2017 16:58:47 +0200, Amélie Deltour
 wrote:



ARCHETYPE-520 (and ARCHETYPE-358) are indeed close to the problem I try
to describe, but not exactly the same.
These issues are about using the mirror configuration to access
archetype data, i.e. using
http://myrepo.mycompany/maven/archetype-catalog.xml instead of direct
access to http://repo1.maven.org/maven2/archetype-catalog.xml, but this
is still the Maven central catalog, just accessed through a mirror
instead of accessing it directly.

But my issue, and the issue behind most ARCHETYPE-519 comments, is not a
mirror issue, it is not either a CLI vs settings.xml issue, it is about
the ability to use an *alternative catalog* which is not published on
Maven central.

In my settings.xml I have several repositories defined:

   
 internal
 repository for internal artifacts
 http://myrepo.mycompany/internal
 ...
   
   
 central
 repository for external artifacts
 http://myrepo.mycompany/external
 ...
   



With 3.x it seems that the "remote" catalog uses the catalog located at
http://myrepo.mycompany/external/archetype-catalog.xml (which is a proxy
for Maven central catalog) but we need the catalog published at
http://myrepo.mycompany/internal/archetype-catalog.xml to be used as
well and this one is ignored.
That's to say, "remote" is interpreted as the "central" repository only,
and other repositories configured in settings.xml are ignored.

This is what I call an "alternative catalog" and I think it is a valid
use case for the plugin.
This was possible with the archetypeCatalog CLI parameter (giving the
catalog URL), and it is probably what the parameter was meant for.
But is not possible anymore with 3.x.
I agree the CLI parameter can be removed, *but* the other repositories
defined in settings.xml have to be taken into account when searching for
remote archetype catalogs.

Please confirm if my use case is valid - in that case I think
ARCHETYPE-519 should be reopend or I can open a new issue if you think
it is more appropriate.
Or I misunderstood / misconfigured something: if my Maven configuration
or usage is wrong I would be glad to understand what's wrong and why.

Thanks,

Amélie


On 05/16/2017 07:06 PM, Robert Scholte wrote:

Looks like ARCHETYPE-520[1] to me. I've created an integration-test for
it, so that should work with 3.0.1

The more I think about it, the more I'm convinced we should also remove
the archetypeCatalog parameter. Right now it is only causing confusion.
Does it still make sense to have "internal", which are in fact a small
set
of embedded archetypes, and they are old (and remote available as well)?
Aether/Artifact Resolver should solve the rest: use both remote and local
as everybody is used to. Want to only use local, then I guess you should
add --offline.

WDYT?

Robert

[1] https://issues.apache.org/jira/browse/ARCHETYPE-520

On Tue, 16 May 2017 13:02:11 +0200, Anders Hammar

wrote:



I would expect "remote" not be the central repo but what repo(s) (or
mirrors) 

RE: Heads up, Plexus IO/Archiver is going Java 7

[Plamen Totev]

Hi,

As the branch is now merged is there anything that blocks the release of
Plexus IO 3.0.0?

Regards,
Plamen Totev