Deploy jar to Maven Central repo

[GoogleCodeExporter]

Would be really helpful to Maven, Ant+Ivy, Gradle users if the dev team 
deployed the release jars to Maven Central.

It's easy to setup and do (I've done it many times), let me know if I can help 
accomplish this.

Original issue reported on code.google.com by jeffjjen...@gmail.com on 21 Oct 2011 at 8:46

[GoogleCodeExporter]

Please feed free to help :) . I think the easiest could be - you make a clone 
of  the repo add the right scripts and send me patch, I'd review it and then I 
might actually add you as committer to the code so that you can push it 
yourself? 

Would that work?

Original comment by ja...@potiuk.com on 22 Oct 2011 at 10:43

• Changed state: Accepted

[GoogleCodeExporter]

Sounds great, will do, thank you!

Original comment by jeffjjen...@gmail.com on 22 Oct 2011 at 2:04

[GoogleCodeExporter]

I've just started making the Maven POM...

Do you have any interest/willingness in changing the source dir structure to 
the Maven standard layout [1][2]?  It's easier to use the default structure, 
but if rather not change it, I can configure for the existing structure.

[1] 
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directo
ry-layout.html

[2] http://docs.codehaus.org/display/MAVENUSER/The+Standard+Directory+Layout

Original comment by jeffjjen...@gmail.com on 23 Oct 2011 at 11:32

[GoogleCodeExporter]

Hmm. You cannot just like that change Android project's source dir structure - 
it is bound to what it is - otherwise eclipse project wont run and android 
build ant scripts won't work either.

There is one problem I realized with maven approach - maven is all about 
sharing .jar files (in this context) but .jar is not nearly enough for android 
libraries (at least not till recently). There is much more than just class 
files that are used from library project - namely res/* files which are 
pre-processed by android build system and magically included at compile time. 
It seems that recent changes to android build structure (last week) have fixed 
that (now library projects actually produce .jar files) so this might be no 
problem any more.

Original comment by jarek.po...@polidea.pl on 24 Oct 2011 at 8:01

[GoogleCodeExporter]

use smth like this pom to describe the module:

<?xml version="1.0" encoding="UTF-8"?>
<project
        xmlns="http://maven.apache.org/POM/4.0.0"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>pl.polidea</groupId>
    <artifactId>treeview</artifactId>
    <version>1.0</version>
    <packaging>apk</packaging>

    <dependencies>
        <dependency>
            <groupId>com.google.android</groupId>
            <artifactId>android</artifactId>
            <version>2.2.1</version>   <!-- any android version -->
            <scope>provided</scope>
        </dependency>        
    </dependencies>

    <build>
        <sourceDirectory>src</sourceDirectory>

        <plugins>

            <plugin>
                <inherited>true</inherited>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <source>1.6</source>
                    <target>1.6</target>
                </configuration>
            </plugin>

            <plugin>
                <groupId>com.jayway.maven.plugins.android.generation2</groupId>
                <artifactId>maven-android-plugin</artifactId>
                <version>2.8.4</version>
                <configuration>
                    <source>${project.basedir}/src</source>
                    <resourceDirectory>${project.basedir}/res</resourceDirectory>
                    <sdk>
                        <path>${sdkPath}</path>
                        <platform>8</platform>
                    </sdk>
                    <attachSources>true</attachSources>
                    <!-- to attach source files and resources to .apksource -->
                </configuration>
                <extensions>true</extensions>
                <!-- otherwise 'apksource' package type is unknown -->

            </plugin>
        </plugins>
    </build>

</project>

Original comment by anton.sm...@gmail.com on 25 Oct 2011 at 10:03

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

and dependency in the module, which uses it:

<dependency>
    <groupId>pl.polidea</groupId>
    <artifactId>treeview</artifactId>
    <version>1.0</version>
    <type>apksources</type>
</dependency>

Original comment by anton.sm...@gmail.com on 25 Oct 2011 at 10:05

[GoogleCodeExporter]

it will be better to separate lib sources and demo sources into different maven 
modules

Original comment by anton.sm...@gmail.com on 25 Oct 2011 at 10:15

[GoogleCodeExporter]

Anton has the correct ideas...

We ended up not using this code, so I doubt I'll find time to make a POM for 
it.  You may want to have Anton finish it for you.

Original comment by jeffjjen...@gmail.com on 29 Oct 2011 at 5:04

[GoogleCodeExporter]

There is no way currently to get resources in the jar deployed in Maven. Until 
Google team makes it possible, we won't fix this one. 

Original comment by ja...@potiuk.com on 2 Feb 2012 at 7:15

• Changed state: WontFix