On 2010-02-12, Antoine Levy-Lambert wrote:
>> Doing something similar for the compress-antlib tells me that my syntax
>> seems to be fine and that Ant 1.8.0 is not available from the Maven repo
>> (I know that you know).
> This is fixed now :
The file
http://repo2.maven.org/maven2/org/apache/an
On 2010-02-12, Martijn Kruithof wrote:
> On 11-2-2010 17:12, Stefan Bodewig wrote:
>> If we put work into creating a branch for the website, then it should
>> save us at least some work (the update of the site), so, yes.
>> Count this at least as a +0.5;-)
> It is not like the current way of pu
Stefan Bodewig wrote:
The file
http://repo2.maven.org/maven2/org/apache/ant/ant/maven-metadata.xml
still doesn't contain any version ther than 1.7.0.
Now, this file contains 1.7.0 and 1.8.0
The latter is a guess since it is not available from the mvn repo either
- I'll publish the latest r
I have built a final candidate for IvyDE 2.1.0. You can download the
distribution at [1]. A staging updatesite has been deployed at [2]. I have
taken the following actions since the last build:
1. Rebuilt with the "final" version qualifier.
2. Added my pub key to the KEYS file (thanks Nicholas)
Sorry, I neglected to add the URLs referenced in my last email:
[1] http://people.apache.org/~jschneider/ivyde-2.1.0/
[2] http://people.apache.org/~jschneider/staging/updatesite/
Also, in case anybody notices, I have not merged changes the fixes I have
made on the 2.1.0 branch back to trunk, but
Jeffrey,
I reviewed the JIRAs and look forward to a patch. I am moving forward with
the 2.1.0 release of IvyDE without them with the understanding that the
2.2.0 development cycle will be much shorter. We are doing this 2.1.0
release with most of the features that we have implemented since 2.0.0
On Feb 12, 2010, at 10:20 AM, Jon Schneider wrote:
I have built a final candidate for IvyDE 2.1.0. You can download the
distribution at [1]. A staging updatesite has been deployed at
[2]. I have
taken the following actions since the last build:
1. Rebuilt with the "final" version qualifie
Thanks John. I provided a patch for the branch comparison code earlier today
and will provide a patch for the optional extended revision id this weekend.
Given that these features will be available in trunk by no later than Sunday,
Feb 14th, I will edit the Jira issues targeting the 2.2.0 rele
Can you Ivy guys make sure I'm not on crack with this? Tests pass
and this seems to do the right thing. I suppose a test might be in
order as well, though I'm not really sure how to navigate the
structure of Ivy's tests... :|
On Feb 12, 2010, at 3:16 PM, mben...@apache.org wrote:
Author
I've filed an issue for this: https://issues.apache.org/jira/browse/IVY-1170
Carl Quinn wrote:
>
> While tracking down some unexpected behavior in our Ivy-based build
> system, I ran across what looks like a bug in
> LatestVersionMatcher.needModuleDescriptor(). In that method, it has a
> hard-c
10 matches
Mail list logo
