Maven support?

[djh123]

Maven support?

[GoogleCodeExporter]

sure would

Original comment by [email protected] on 28 Mar 2011 at 3:24

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Please add to the maven repository. You can follow the instructions here: 
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage
+Guide

Original comment by [email protected] on 1 Jul 2011 at 4:27

[GoogleCodeExporter]

try this 
http://www.thewebsemantic.com/2009/04/11/your-very-own-google-code-maven-repo/

custom repo on google code itself .. I use it in gmultipart 
(http://code.google.com/p/gmultipart/)

Original comment by [email protected] on 6 Jul 2011 at 5:50

[GoogleCodeExporter]

I personally do not use Maven much. This request seems to be quite popular, 
though, so is there any volunteer to try to do it?

Original comment by [email protected] on 31 Mar 2012 at 2:52

[GoogleCodeExporter]

How do you build the engine today? Using Maven makes more sense, if you switch 
your build to Maven. While I can offer to provide consulting, it also means 
that you have to feel comfortable with that. But perhaps you will find it quite 
useful? 

Otherwise we need to provide a more artifical approach. I still can provide 
what you need for that. 

Original comment by [email protected] on 31 Mar 2012 at 3:08

[GoogleCodeExporter]

ACE is currently built using Ant.
It seems like there are several users that need Maven for building and having 
the artifacts into a Maven repository.

So, I was asking somebody that knows Maven more than me to contribute the 
needed stuff for that.

As this is an open-source, free of charge, Apache license library, such 
contribution is expected to be contributed for free.

Original comment by [email protected] on 31 Mar 2012 at 3:16

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ok, let me explain what I mean.

There are two ways to solve this request:

1. You go ahead building with ant, but you provide the needed artifacts for 
Maven users. Advantage: No code changes in ACE, but risk of inconsistencies 
with Maven and you will not get the advantages of an Maven build.

2. You switch your build to Maven. Advantage: Native Maven support, easier 
build maintanance. But we need minor directory changes and you need to learn, 
how to build with Maven.

I can help you what ever you choose. But the choice is yours.

Original comment by [email protected] on 31 Mar 2012 at 4:32

[GoogleCodeExporter]

Definitely option #1.

Original comment by [email protected] on 31 Mar 2012 at 8:35

[GoogleCodeExporter]

I would actually recommend option 2 (but I am partial ..). However if you 
choose option 2 I would suggest to look at using the Maven Ant Task or better 
the Aether Ant Tasks.

Original comment by [email protected] on 2 Apr 2012 at 5:25

[GoogleCodeExporter]

And I would very much suggest to push the artifacts to the Central repo rather 
than wasting time with your own repo.

Original comment by [email protected] on 2 Apr 2012 at 5:26

[GoogleCodeExporter]

One day I will do this. Just wondered how much the community wants to 
contribute to this effort. Thanks!

Original comment by [email protected] on 10 May 2012 at 9:20

[GoogleCodeExporter]

Maven xml configuration available @ https://github.com/jondwillis/AChartEngine

But it seems that the demo has not a maven configuration.

Original comment by [email protected] on 14 Jul 2012 at 6:56

[GoogleCodeExporter]

I added correct pom.xml on https://github.com/netcook/AChartEngine

Original comment by [email protected] on 20 Nov 2012 at 3:06

[GoogleCodeExporter]

Thanks for pom.xml, it was helpful. I had to tweak it a little bit in order to 
make it work.

I setup a public repository for the interested ones. In order to use 
AChartEngine in a Maven project, you will need to add this repository:

<repository>
    <id>achartengine</id>
    <name>Public AChartEngine repository</name>
    <url>https://repository-achartengine.forge.cloudbees.com/snapshot/</url>
</repository>

And add this dependency:

<dependency>
    <groupId>org.achartengine</groupId>
    <artifactId>achartengine</artifactId>
    <version>1.1.0</version>
</dependency>

Original comment by [email protected] on 14 Jan 2013 at 6:00

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by [email protected] on 14 Jan 2013 at 6:01

• Changed state: New

[GoogleCodeExporter]

Original comment by [email protected] on 14 Jan 2013 at 6:01

• Changed state: Fixed

[GoogleCodeExporter]

I do not consider it completely fixed as the repo does not contain any javadoc 
or source jars. Please add them too...

Original comment by [email protected] on 27 Jul 2013 at 11:05