You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by Kurt T Stam <ku...@gmail.com> on 2009/06/12 06:29:09 UTC
broken trunk build?
Hi guys,
I tried building the trunk today and noticed that the size of my ode.war
dropped from
52426305 Apr 29 15:26 ode.war
to
34306632 Jun 11 23:47 ode.war
and the current war is not working for me. No processes get deployed
when I copy the examples to ode/WEB-INF/processes, while that works fine
in the Apr 29 build.
Is the current code base simply not working, or is it me?
Thx,
--Kurt
Re: broken trunk build?
Posted by Kurt T Stam <ku...@gmail.com>.
Sure,
Besides the jars being compressed now, I also see a difference in the
web.xml. Does this file get touched during the build? When I deploy the
war now it does not get picked up by tomcat at all. When I replace it
with an old web.xml it does get deployed again.
To test simply deploy the ode.war to tomcat. When I do that with the new
ode.war I see no "DEBUG - GeronimoLog.debug(" logging (with GEN and
deploying HelloWorld2 does not result in an process deployment.
Please let me know what else I can give you!
thx,
--Kurt
Alex Boisvert wrote:
> Yes, there was a bug
> <https://issues.apache.org/jira/browse/BUILDR-253> in buildr 1.3.3 and
> before where jars were created without compression.
>
> Can you give us more details on what's not working with ode.war?
>
> alex
>
>
> On Fri, Jun 12, 2009 at 7:12 AM, Kurt T Stam <kurt.stam@gmail.com
> <ma...@gmail.com>> wrote:
>
> BTW, I tried this on both OSX as well as Centos-5.3, jdk5_19,
> buildr-1.3.4. It runs all the unittests. It looks like the
> compression of the ode jars changed.
>
> --Kurt
>
>
> Kurt T Stam wrote:
>
> Hi guys,
>
> I tried building the trunk today and noticed that the size of
> my ode.war dropped from
>
> 52426305 Apr 29 15:26 ode.war
>
> to
>
> 34306632 Jun 11 23:47 ode.war
>
> and the current war is not working for me. No processes get
> deployed when I copy the examples to ode/WEB-INF/processes,
> while that works fine in the Apr 29 build.
>
> Is the current code base simply not working, or is it me?
>
> Thx,
>
> --Kurt
>
>
>
Re: broken trunk build?
Posted by Kurt T Stam <ku...@gmail.com>.
Hi Alex,
How does this fix get to me?
/buildr/trunk/lib/buildr/packaging/ziptask.rb
Is this distributed as a gem?And does buildr pull this in a build time?
If so which other gems are being used, just in case I want to freeze them..
Thx,
--Kurt
Alex Boisvert wrote:
> Yes, there was a bug
> <https://issues.apache.org/jira/browse/BUILDR-253> in buildr 1.3.3 and
> before where jars were created without compression.
>
> Can you give us more details on what's not working with ode.war?
>
> alex
>
>
> On Fri, Jun 12, 2009 at 7:12 AM, Kurt T Stam <kurt.stam@gmail.com
> <ma...@gmail.com>> wrote:
>
> BTW, I tried this on both OSX as well as Centos-5.3, jdk5_19,
> buildr-1.3.4. It runs all the unittests. It looks like the
> compression of the ode jars changed.
>
> --Kurt
>
>
> Kurt T Stam wrote:
>
> Hi guys,
>
> I tried building the trunk today and noticed that the size of
> my ode.war dropped from
>
> 52426305 Apr 29 15:26 ode.war
>
> to
>
> 34306632 Jun 11 23:47 ode.war
>
> and the current war is not working for me. No processes get
> deployed when I copy the examples to ode/WEB-INF/processes,
> while that works fine in the Apr 29 build.
>
> Is the current code base simply not working, or is it me?
>
> Thx,
>
> --Kurt
>
>
>
Re: broken trunk build?
Posted by Kurt T Stam <ku...@gmail.com>.
Thx Alex,
I went back to buildr 1.2.10, and now my build is happy again.
--Kurt
Alex Boisvert wrote:
> Yes, there was a bug
> <https://issues.apache.org/jira/browse/BUILDR-253> in buildr 1.3.3 and
> before where jars were created without compression.
>
> Can you give us more details on what's not working with ode.war?
>
> alex
>
>
> On Fri, Jun 12, 2009 at 7:12 AM, Kurt T Stam <kurt.stam@gmail.com
> <ma...@gmail.com>> wrote:
>
> BTW, I tried this on both OSX as well as Centos-5.3, jdk5_19,
> buildr-1.3.4. It runs all the unittests. It looks like the
> compression of the ode jars changed.
>
> --Kurt
>
>
> Kurt T Stam wrote:
>
> Hi guys,
>
> I tried building the trunk today and noticed that the size of
> my ode.war dropped from
>
> 52426305 Apr 29 15:26 ode.war
>
> to
>
> 34306632 Jun 11 23:47 ode.war
>
> and the current war is not working for me. No processes get
> deployed when I copy the examples to ode/WEB-INF/processes,
> while that works fine in the Apr 29 build.
>
> Is the current code base simply not working, or is it me?
>
> Thx,
>
> --Kurt
>
>
>
Re: broken trunk build?
Posted by Alex Boisvert <bo...@intalio.com>.
Yes, there was a bug <https://issues.apache.org/jira/browse/BUILDR-253> in
buildr 1.3.3 and before where jars were created without compression.
Can you give us more details on what's not working with ode.war?
alex
On Fri, Jun 12, 2009 at 7:12 AM, Kurt T Stam <ku...@gmail.com> wrote:
> BTW, I tried this on both OSX as well as Centos-5.3, jdk5_19, buildr-1.3.4.
> It runs all the unittests. It looks like the compression of the ode jars
> changed.
>
> --Kurt
>
>
> Kurt T Stam wrote:
>
>> Hi guys,
>>
>> I tried building the trunk today and noticed that the size of my ode.war
>> dropped from
>>
>> 52426305 Apr 29 15:26 ode.war
>>
>> to
>>
>> 34306632 Jun 11 23:47 ode.war
>>
>> and the current war is not working for me. No processes get deployed when
>> I copy the examples to ode/WEB-INF/processes, while that works fine in the
>> Apr 29 build.
>>
>> Is the current code base simply not working, or is it me?
>>
>> Thx,
>>
>> --Kurt
>>
>>
>
Re: broken trunk build?
Posted by Kurt T Stam <ku...@gmail.com>.
BTW, I tried this on both OSX as well as Centos-5.3, jdk5_19,
buildr-1.3.4. It runs all the unittests. It looks like the compression
of the ode jars changed.
--Kurt
Kurt T Stam wrote:
> Hi guys,
>
> I tried building the trunk today and noticed that the size of my
> ode.war dropped from
>
> 52426305 Apr 29 15:26 ode.war
>
> to
>
> 34306632 Jun 11 23:47 ode.war
>
> and the current war is not working for me. No processes get deployed
> when I copy the examples to ode/WEB-INF/processes, while that works
> fine in the Apr 29 build.
>
> Is the current code base simply not working, or is it me?
>
> Thx,
>
> --Kurt
>