How about updating the platform req to Java 6 and be done with it?
Gary
On Mon, Apr 13, 2015 at 2:34 PM, Jörg Schaible
wrote:
> Hi Luc,
>
> -1, it claims to be Java 5 compatible, but it is not (at least not the
> tests):
>
> == %<
> $ mvn -P
Hi Luc,
-1, it claims to be Java 5 compatible, but it is not (at least not the
tests):
== %<
$ mvn -P java-1.5 clean test
[INFO] Scanning for projects...
[INFO]
[INFO]
-
Le 13/04/2015 22:08, Gary Gregory a écrit :
> +1.
>
> Tested with src zip; MD5, ASC OK. Site builds (including JIRA report, which
> fails with Maven 3.3.1.). Reports looks good. Can't attest if PMD and
> Checkstyle are better or worse than previous release though.
We generally aim at 0 chectyle a
Le 13/04/2015 20:29, Benedikt Ritter a écrit :
> Hi,
>
> tested with:
>
> Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c;
> 2015-03-13T21:10:27+01:00)
> Maven home: /usr/local/Cellar/maven/3.3.1/libexec
> Java version: 1.8.0_31, vendor: Oracle Corporation
> Java home:
> /Library/Jav
On 13 April 2015 at 12:19, Benedikt Ritter wrote:
> Hello Duncan,
>
> 2015-04-11 8:02 GMT+02:00 :
>
>> Author: djones
>> Date: Sat Apr 11 06:02:34 2015
>> New Revision: 1672833
>>
>> URL: http://svn.apache.org/r1672833
>> Log:
>> Update for LANG-1069: CharSet.getInstance documentation does not cle
+1.
Tested with src zip; MD5, ASC OK. Site builds (including JIRA report, which
fails with Maven 3.3.1.). Reports looks good. Can't attest if PMD and
Checkstyle are better or worse than previous release though.
Tested with:
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
2014-12-14
Hi,
tested with:
Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c;
2015-03-13T21:10:27+01:00)
Maven home: /usr/local/Cellar/maven/3.3.1/libexec
Java version: 1.8.0_31, vendor: Oracle Corporation
Java home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/jre
Default loc
On Mon, Apr 13, 2015 at 10:51 AM, Luc Maisonobe wrote:
> Le 13/04/2015 18:15, Gary Gregory a écrit :
> > When I build from the src zip, I get a bunch of:
> >
> > [ERROR]
> > java.lang.IllegalArgumentException: One of setGitDir or setWorkTree must
> be
> > called.
>
> Yes, it is caused by the buil
Le 13/04/2015 18:15, Gary Gregory a écrit :
> When I build from the src zip, I get a bunch of:
>
> [ERROR]
> java.lang.IllegalArgumentException: One of setGitDir or setWorkTree must be
> called.
Yes, it is caused by the buildnumber plugin that cannot find the git
commit since you are not in a git
When I build from the src zip, I get a bunch of:
[ERROR]
java.lang.IllegalArgumentException: One of setGitDir or setWorkTree must be
called.
at
org.eclipse.jgit.lib.BaseRepositoryBuilder.requireGitDirOrWorkTree(BaseRepositoryBuilder.java:582)
at
org.eclipse.jgit.lib.BaseRepositoryB
On Sat, Apr 11, 2015 at 12:39 PM, Peter Ansell
wrote:
> On 11 April 2015 at 22:11, Reto Gmür wrote:
> > On Mon, Mar 30, 2015 at 2:07 PM, Benedikt Ritter
> wrote:
> >
> >> Hello Reto,
> >>
> >> 2015-03-30 14:45 GMT+02:00 Reto Gmür :
> >>
> >> > Hi all,
> >> >
> >> > The clerezza commons RDF prop
+1 from myself.
Luc
Le 2015-04-13 00:02, Bruno P. Kinoshita a écrit :
+1 non binding.
Build works fine in the following environment
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
2014-12-15T06:29:23+13:00)
Maven home: /opt/apache-maven-3.2.5
Java version: 1.8.0_40, vendor: Oracl
Hello Duncan,
2015-04-11 8:02 GMT+02:00 :
> Author: djones
> Date: Sat Apr 11 06:02:34 2015
> New Revision: 1672833
>
> URL: http://svn.apache.org/r1672833
> Log:
> Update for LANG-1069: CharSet.getInstance documentation does not clearly
> explain how to include negation character in set. Javadoc
2015-04-13 2:27 GMT+02:00 Matt Benson :
> +1 to what Peter said: it's a functional interface so it is
> lambda-compatible anyway.
>
Well, yes it would be a functional interface, but it would lack all the
default methods defined in java.util.function.Predicate if we don't extend
it later.
>
> Ma
14 matches
Mail list logo
