On 26-Mar-07, at 12:46 AM, James M Snell wrote:

Excellent. Feel free to post the patch here or in jira and I'll get it
applied.

- James

My patch-fu being weak (darned if I can figure out how to create a complete patchset with svn diff in a timely fashion), I've
attached the following:

1. i18n.patch (root and core poms)
2. build.xml (dependencies/i18n/build.xml)
3. build.properties (dependencies/i18n/build.properties)
4. pom.xml (dependencies/i18n/pom.xml)

The way I approached it, it would probably make slightly more sense to move the i18n directory up to be a submodule, so it could take better advantage of maven inheritance. Also, a warning: I changed the version to 0.3.0-incubating-SNAPSHOT, which is what both the new POM and new build.xml create. There's no change to the master build.xml, so the new build.xml is not invoked unless it's done manually. I hope it's still useful =)

(additional conditional apologies in advance, since I'm using Mail.App attachments for the first time)

cheers,

AC

<?xml version="1.0" encoding="utf-8"?>
<project name="i18n" default="dist" basedir=".">
 <description>RFC 3987 (IRI) support library for Apache Abdera</description>
 <property name="version" value="0.3.0-incubating-SNAPSHOT"/>

 <property file="${basedir}/build.properties"/>

 <path id="test.classpath">
   <pathelement path="${dest.dir}"/>
   <pathelement path="${test.dest.dir}"/>
   <pathelement path="${junit.jar}"/>
 </path> 

 <target name="clean">
   <delete dir="${dest.dir}"/>
   <delete dir="${test.dest.dir}"/>
 </target>

 <target name="prepare">
  <mkdir dir="${dest.dir}"/>
  <mkdir dir="${test.dest.dir}"/>
 </target>

 <target name="compile" depends="prepare">
  <javac srcdir="${src.dir}" destdir="${dest.dir}"/>
 </target>

 <target name="test-compile" depends="compile">
  <javac srcdir="${test.src.dir}" destdir="${test.dest.dir}"
	classpathref="test.classpath"/>
 </target>


 <target name="test" depends="test-compile">
  <junit printsummary="yes" haltonfailure="yes">
  	<classpath>
		<path refid="test.classpath"/>
	</classpath>
  </junit>
 </target>

 <target name="dist" depends="test">
	<jar 	basedir="${dest.dir}" 
		jarfile="${basedir}/../abdera-i18n-${version}.jar"/>
 </target>
</project>
<?xml version="1.0" encoding="UTF-8"?>
<!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  The ASF licenses this file to You
  under the Apache License, Version 2.0 (the "License"); you may not
  use this file except in compliance with the License.
  You may obtain a copy of the License at
 
      http://www.apache.org/licenses/LICENSE-2.0
 
  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.  For additional information regarding
  copyright in this work, please see the NOTICE file in the top level
  directory of this distribution. -->
<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>org.apache.abdera</groupId>
  <artifactId>abdera-i18n</artifactId>
  <packaging>jar</packaging>
  <name>I18N Libraries</name>
  <version>0.3.0-incubating-SNAPSHOT</version>
  <description>RFC 3987 (Internationlaized Resource Identifier) libraries.</description>
  <inceptionYear>2007</inceptionYear>
  <url>http://incubator.apache.org/abdera</url>
  <scm>
    <connection>scm:svn:http://svn.apache.org/repos/asf/incubator/abdera/java/trunk/dependencies/i18n/</connection>
    <developerConnection>scm:svn:https://svn.apache.org/repos/asf/incubator/abdera/java/trunk/dependencies/i18n/</developerConnection>
    <url>http://svn.apache.org/repos/asf/incubator/abdera/java/trunk/dependencies/i18n/</url>
  </scm>
  <dependencies>
	<dependency>
		<groupId>junit</groupId>
		<artifactId>junit</artifactId>
		<version>3.8.2</version>
		<scope>test</scope>
	</dependency>
 </dependencies>
  <build>
	<plugins>
		<plugin>
			<artifactId>maven-compiler-plugin</artifactId>
			<configuration>
				<source>1.5</source>
				<target>1.5</target>
			</configuration>
		</plugin>
	</plugins>
  </build>
  <distributionManagement>
    <snapshotRepository>
      <id>apache.snapshots</id>
      <name>Apache SNAPSHOT Repository</name>
      <url>scp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>
    </snapshotRepository>
    <repository>
      <id>apache.incubating</id>
      <name>Apache Incubating Repository</name>
      <url>scp://people.apache.org/www/people.apache.org/repo/m2-incubating-repository</url>
    </repository>
  </distributionManagement>
</project>



Adam Constabaris wrote:
This isn't directly related, but I do have a pom for the i18n
dependency, which also requires patching the pom for the core
subproject.  If nobody's yet done a build.xml, I'll take a look at
generating one of those and submitting a patch.

cheers,

AC

On 24-Mar-07, at 3:19 PM, James M Snell wrote:

+1. that's been on my todo list. It wouldn't break my heart if someone
else got to it first ;-)

- James

Garrett Rooney wrote:
So, if the i18n code is going to be separate from the rest of Abdera (i.e. we're planning on moving it out of the tree eventually) would it
be possible to extract its build logic from build/build.xml?  I was
thinking of updating my work-in-progress ivy patch today, but I don't want to totally duplicate the current logic to build the i18n stuff.
It seems like we could just put a stupidly-simple build.xml in
dependencies/i18n, and since we are trying to make that code
independent it's going to need that eventually anyway...

-garrett




Reply via email to