Re: [TOOLS] Trouble building 2.0.x

[Christopher Schultz <ch...@christopherschultz.net>]

Antonio,

On 1/31/12 11:29 AM, Antonio Petrelli wrote:
> Now I remember :-D
> The 2.0.x was an attempted move to Maven, but it is a failure. You should
> use Ant there.
> The trunk (2.1.x) is working, but you have to build these projects in order:
> velocity-master
> velocity-engine-parent
> velocity-tools-parent

So, I went with Tools trunk and tried to build using Maven. It complains
that Velocity isn't available (duh, you told me that: it wants Velocity
"1-SNAPSHOT", which I didn't have).

No problem: just check it out from svn (done) and build:

$ mvn
[INFO] Building Apache Velocity 1.7
[...]
Running org.apache.velocity.test.ResourceExistsTestCase
testfile.vm was not found in path @test.dir@/resourceexists
Log was:  [debug] Initializing Velocity, Calling init()...
[...]
[INFO] BUILD FAILURE

Looks like the same type of thing I saw when trying to build Tools
2.0.x. So I looked at README.txt:

"
To build Velocity's jar, change directory into the build/ directory
and enter:

ant jar
"

Hmm, okay. ant jar. Can't download (ibiblio 404s). Fix repo.m[12].url.
ant jar.

      [get] Error opening connection java.io.FileNotFoundException:
http://mirrors.ibiblio.org/pub/mirrors/maven/commons-collections/jars/commons-collections-3.2.1.jar

This time, I re-check the repo, and, lo and behold, there's no
commons-collections-3.2.1.jar file there. :(

Do I just have bad timing with ibiblio moving stuff around or something?

Plus, if I use ant to build Velocity, how will Tools know where it ends up?

I'm sorry to be such a pain, but it's hard to code when you can compile :)

-chris

Re: [TOOLS] Trouble building 2.0.x

[Christopher Schultz <ch...@christopherschultz.net>]

Antonio,

On 2/2/12 3:19 AM, Antonio Petrelli wrote:
> 2012/2/1 Christopher Schultz <ch...@christopherschultz.net>
> 
>> Antonio,
>>
>> On 2/1/12 3:36 AM, Antonio Petrelli wrote:
>>> 2012/2/1 Christopher Schultz <ch...@christopherschultz.net>
>>>
>>>> Antonio,
>>>>
>>>> On 1/31/12 6:11 PM, Christopher Schultz wrote:
>>>>> No problem: just check it out from svn (done) and build:
>>>>
>>>> I forgot to mention that I downloaded the Velocity 1.7 tag. I wasn't
>>>> sure if trunk would be a good idea in this case.
>>>>
>>>
>>> The problem is that Tools 2.1.0-SNAPSHOT depends on Velocity
>>> 2.0.0-SNAPSHOT, that depends on velocity-master 1-SNAPSHOT.
>>> IOW, everything is ready to use Maven as the main builder for the next
>>> iteration, so you have to build everything at once or nothing at all.
>>
>> So, if I want to work on Tools, I need to use tools/trunk, and
>> velocity/trunk. Back-porting is going to be a big mess :(
>>
> 
> The question is: is backporting necessary?

Maybe. There are definitely some fixes I'd personally like to have in
the 2.0.x branch, because that's what I'm using in production right now.
I don't want to have to upgrade to Tools 2.1 (release date unknown) and
Velocity 2.0 (release date unknown) just to get those fixes.

Realistically, I can commit the changes to the 2.0.x line, build it
myself, and use it without a problem. I just figured that others might
be in my same position and like those fixes as well.

-chris

Re: [TOOLS] Trouble building 2.0.x

[Antonio Petrelli <an...@gmail.com>]

2012/2/1 Christopher Schultz <ch...@christopherschultz.net>

> Antonio,
>
> On 2/1/12 3:36 AM, Antonio Petrelli wrote:
> > 2012/2/1 Christopher Schultz <ch...@christopherschultz.net>
> >
> >> Antonio,
> >>
> >> On 1/31/12 6:11 PM, Christopher Schultz wrote:
> >>> No problem: just check it out from svn (done) and build:
> >>
> >> I forgot to mention that I downloaded the Velocity 1.7 tag. I wasn't
> >> sure if trunk would be a good idea in this case.
> >>
> >
> > The problem is that Tools 2.1.0-SNAPSHOT depends on Velocity
> > 2.0.0-SNAPSHOT, that depends on velocity-master 1-SNAPSHOT.
> > IOW, everything is ready to use Maven as the main builder for the next
> > iteration, so you have to build everything at once or nothing at all.
>
> So, if I want to work on Tools, I need to use tools/trunk, and
> velocity/trunk. Back-porting is going to be a big mess :(
>

The question is: is backporting necessary?

Antonio

Re: [TOOLS] Trouble building 2.0.x

[Christopher Schultz <ch...@christopherschultz.net>]

Antonio,

On 2/1/12 3:36 AM, Antonio Petrelli wrote:
> 2012/2/1 Christopher Schultz <ch...@christopherschultz.net>
> 
>> Antonio,
>>
>> On 1/31/12 6:11 PM, Christopher Schultz wrote:
>>> No problem: just check it out from svn (done) and build:
>>
>> I forgot to mention that I downloaded the Velocity 1.7 tag. I wasn't
>> sure if trunk would be a good idea in this case.
>>
> 
> The problem is that Tools 2.1.0-SNAPSHOT depends on Velocity
> 2.0.0-SNAPSHOT, that depends on velocity-master 1-SNAPSHOT.
> IOW, everything is ready to use Maven as the main builder for the next
> iteration, so you have to build everything at once or nothing at all.

So, if I want to work on Tools, I need to use tools/trunk, and
velocity/trunk. Back-porting is going to be a big mess :(

-chris

Re: [TOOLS] Trouble building 2.0.x

[Antonio Petrelli <an...@gmail.com>]

2012/2/1 Christopher Schultz <ch...@christopherschultz.net>

> Antonio,
>
> On 1/31/12 6:11 PM, Christopher Schultz wrote:
> > No problem: just check it out from svn (done) and build:
>
> I forgot to mention that I downloaded the Velocity 1.7 tag. I wasn't
> sure if trunk would be a good idea in this case.
>

The problem is that Tools 2.1.0-SNAPSHOT depends on Velocity
2.0.0-SNAPSHOT, that depends on velocity-master 1-SNAPSHOT.
IOW, everything is ready to use Maven as the main builder for the next
iteration, so you have to build everything at once or nothing at all.

Antonio

Re: [TOOLS] Trouble building 2.0.x

[Christopher Schultz <ch...@christopherschultz.net>]

Antonio,

On 1/31/12 6:11 PM, Christopher Schultz wrote:
> No problem: just check it out from svn (done) and build:

I forgot to mention that I downloaded the Velocity 1.7 tag. I wasn't
sure if trunk would be a good idea in this case.

-chris