New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provision Mojo #566

Open
mosabua opened this Issue Jan 16, 2015 · 5 comments

Comments

Projects
None yet
2 participants
@mosabua
Member

mosabua commented Jan 16, 2015

It would be good to be able to replace the Maven Android SDK Deployer with a provision mojo. Initially it would be good enough to copy the repositories that are in the SDK and be able to install them to the local repo.

Later it could do deploy as well and also cover more components.

This class can be used to turn a path to a GAV. https://github.com/apache/maven-indexer/blob/master/indexer-core/src/main/java/org/apache/maven/index/artifact/M2GavCalculator.java

And some of the aehter related code in https://github.com/simpligility/maven-repository-tools can do more. It might actually be best to have the directory to repo install or deploy code in that project and then just use it here.

@mosabua mosabua self-assigned this Jan 16, 2015

@william-ferguson-au

This comment has been minimized.

Contributor

william-ferguson-au commented Jan 16, 2015

If you are a repo manager (like Nexus) you don't need to copy the 2 Android
repos anywhere. You just need to setup 2 hosted Nexus repos that point to
each folder.

Where we do need the SDk deployer is in creating and installing the jars
for the versions of Android.

On Fri, Jan 16, 2015 at 10:22 AM, Manfred Moser notifications@github.com
wrote:

It would be good to be able to replace the Maven Android SDK Deployer with
a provision mojo. Initially it would be good enough to copy the
repositories that are in the SDK and be able to install them to the local
repo.

Later it could do deploy as well and also cover more components.

This class can be used to turn a path to a GAV.
https://github.com/apache/maven-indexer/blob/master/indexer-core/src/main/java/org/apache/maven/index/artifact/M2GavCalculator.java

And some of the aehter related code in
https://github.com/simpligility/maven-repository-tools can do more. It
might actually be best to have the directory to repo install or deploy code
in that project and then just use it here.


Reply to this email directly or view it on GitHub
#566.

@william-ferguson-au

This comment has been minimized.

Contributor

william-ferguson-au commented Jan 16, 2015

.. that should have read :
If you are using a repo manager (like Nexus) ..

On Fri, Jan 16, 2015 at 10:55 AM, William Ferguson <
william.ferguson@xandar.com.au> wrote:

If you are a repo manager (like Nexus) you don't need to copy the 2
Android repos anywhere. You just need to setup 2 hosted Nexus repos that
point to each folder.

Where we do need the SDk deployer is in creating and installing the jars
for the versions of Android.

On Fri, Jan 16, 2015 at 10:22 AM, Manfred Moser notifications@github.com
wrote:

It would be good to be able to replace the Maven Android SDK Deployer
with a provision mojo. Initially it would be good enough to copy the
repositories that are in the SDK and be able to install them to the local
repo.

Later it could do deploy as well and also cover more components.

This class can be used to turn a path to a GAV.
https://github.com/apache/maven-indexer/blob/master/indexer-core/src/main/java/org/apache/maven/index/artifact/M2GavCalculator.java

And some of the aehter related code in
https://github.com/simpligility/maven-repository-tools can do more. It
might actually be best to have the directory to repo install or deploy code
in that project and then just use it here.


Reply to this email directly or view it on GitHub
#566.

@mosabua

This comment has been minimized.

Member

mosabua commented Jan 16, 2015

That only works if the repo manager file system is available to the machine that has the SDK and relies on the Maven repo being a Maven repo in the filesystem as well. This is currently the case for Nexus and Archiva. It is NOT the case for Artifactory. The safer and better way is still a deployment to a repo manager via the usual mechanism.

@mosabua

This comment has been minimized.

Member

mosabua commented Jan 16, 2015

And yes... the deployment of the Android jars that way would be good too.. sort of step 2 ..

@william-ferguson-au

This comment has been minimized.

Contributor

william-ferguson-au commented Jan 16, 2015

Good point.

On Fri, Jan 16, 2015 at 3:02 PM, Manfred Moser notifications@github.com
wrote:

That only works if the repo manager file system is available to the
machine that has the SDK and relies on the Maven repo being a Maven repo in
the filesystem as well. This is currently the case for Nexus and Archiva.
It is NOT the case for Artifactory. The safer and better way is still a
deployment to a repo manager via the usual mechanism.


Reply to this email directly or view it on GitHub
#566 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment