Skip to content
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

Adapting POMs and merging test- and normale module #8

Merged
merged 14 commits into from
Jul 16, 2012

Conversation

sebastiangraf
Copy link
Collaborator

Hi there,

Adaptions within this Pull Request include:

  • Merging of flickrj-android and flickrj-android-test (including removal of flickrj-android-test
  • Adapting .gitignore to ignore eclipse-stuff including removal of flickrj-android/.classpath
  • Adapting Version to 1.0.4-SNAPSHOT (will be increased to 2.0.0-SNAPSHOT within the change of the groupId, coming up next)
  • Adding several plugins generating source-, normal- and javadoc-jars. Need now gpg on the machine installed in each goal 'install' and above
  • Removal of ant-googlelib (for now, let's see if maven-gcu-plugin can act as a replacement to get rid of the ant-deployment of javadoc and base on maven only, otherwise, we switch back)

The next pull request will include the renaming from com.gmail.yuyang226 to com.googlecode.flickrj as group-id

cheers

sebastian

@sebastiangraf sebastiangraf merged commit d643d08 into yuyang226:master Jul 16, 2012
@brk3
Copy link
Collaborator

brk3 commented Jul 16, 2012

Hi Sebastian, I haven't had time to look over these commits in detail but they seem good :) However, as of this merge the google-code javadoc is currently broken, can you take a look?

@yuyang226
Copy link
Owner

Hi Brk3, Sebastian told me that he would remove the javadoc from source code, and put it to Github with a plugin.

For now, please generate a local copy of the Javadoc or directly browse the source code.

@sebastiangraf
Copy link
Collaborator Author

Here we go:
I utilized the github webspace related to yuyang226/FlickrjApi4Android to publish the Javadoc. The Javadoc is thereby accessible over http://yuyang226.github.com/FlickrjApi4Android and can easily be updated via:

  1. mvn site:site
  2. mvn ghSite:site -N
    executed in the root-folder in the project.

How does it work?

  1. Just inserted in the root/pom.xml the site-plugin including the javadoc.
  2. In root/src/site/resources, an index.html with a redirect to the javadoc is inserted (normally, maven websites are a little bit more verbose)

Within each 'mvn site:site', the website (including javadoc) is generated and accessible under root/target/site.

Afterwards, I just inserted the github-maven-module for websites in the root/pom.xml . This plugin is bound to the scm-tag whereas I inserted the ones of github in the root/pom.xml as well. Within each 'mvn ghSite:site', the website is uploaded and updated. Please note, to execute this with the '-N' flag, otherwise the build will fail.

If you adapt the link to the Javadoc on googlecode to http://yuyang226.github.com/FlickrjApi4Android/ , everything is fine. Unfortunately, google code doesn't offer such convinient access to the websites as github does (afaik). I pushed the changes to both repos.

Does that fit?

cheers

sebastian

@brk3
Copy link
Collaborator

brk3 commented Jul 17, 2012

Nice!

@yuyang226
Copy link
Owner

thanks for the excellent job!
On Jul 17, 2012 8:58 PM, "Paul Bourke" <
reply@reply.github.com>
wrote:

Nice!


Reply to this email directly or view it on GitHub:
#8 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants