Incidentally, since we've talked about it, here's the pom.xml (attached); this is not a patch (since the patch will need to move directories). It also targets Java 7 by default; that's easily changed. (I don't know the target VM yet; IMO, it SHOULD be 7, since 6 is at the end of its support cycle.)
This includes no tests, although it would be easy to provide for tests as part of the build. But, as Glen suggests, this is in fact ready for "mvn package" or "mvn clean install" - and deployment capabilities are also available. On Wed, Jul 25, 2012 at 12:06 PM, Glen Mazza <[email protected]> wrote: > Umm, I would say the main priority is that Joseph creates the pom such that > proton builds via "mvn clean install" OOTB (as any good Maven project > should.) As long as he's met that threshold, I don't see a need anymore for > maintaining two sources of records for builds. > > Maven is really mind-numbingly simple for those building with it. No matter > what you're building, it's always "mvn clean install" (so long as the pom is > properly written, as it nearly always is). All you need to do is download > Maven, add $MAVEN_HOME/bin to your system path (just like you do for Ant) > and you're all set. > > The problem with providing an Ant build is that non-Maven users, never > having worked with it, tend to awfulize Maven, and then stick with Ant, > continuing their misconception of Maven. Maven is really an ice cream cone, > not a brussels sprout, but sometimes people need to be given a push to find > that out. :) Also, burdening Joseph by having him create/maintain a > separate Ant build also takes away his efforts towards creating an awesome > Maven build. > > Glen > > > >>Hi, >>It looks for me that the structure of proton-j sub-project will be >>quite simple and will not require the creation of complicated building >>scripts similar to what we have in qpid java tree right now. I believe >>that we can have 2 building systems for proton-j at least on first >>stages of the project. That would allow developers to use either ant >>or maven depending from their preferences. >>IMHO, it should not be big overhead for the project. >> >>Kind Regards, >>Alex > > -- > Glen Mazza > Talend Community Coders > coders.talend.com > blog: www.jroller.com/gmazza > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Joseph B. Ottinger http://enigmastation.com Ça en vaut la peine.
<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/xsd/maven-4.0.0.xsd";> <modelVersion>4.0.0</modelVersion> <groupId>org.apache.qpid</groupId> <artifactId>proton-j</artifactId> <version>1.0</version> <packaging>jar</packaging> <name>proton-j</name> <url>http://maven.apache.org</url> <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> </properties> <dependencies> <!-- <dependency> <groupId>org.testng</groupId> <artifactId>testng</artifactId> <version>[6.5.2,)</version> <scope>test</scope> </dependency> --> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>2.5.1</version> <configuration> <source>1.7</source> <target>1.7</target> </configuration> </plugin> </plugins> </build> </project>
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
