You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by jk...@apache.org on 2006/05/13 18:33:18 UTC
svn commit: r406126 -
/tapestry/tapestry4/trunk/framework/src/java/org/apache/tapestry/html/dojo/
Author: jkuhnert
Date: Sat May 13 09:33:17 2006
New Revision: 406126
URL: http://svn.apache.org/viewcvs?rev=406126&view=rev
Log:
Removing to upgrade
Removed:
tapestry/tapestry4/trunk/framework/src/java/org/apache/tapestry/html/dojo/
Re: svn commit: r406126 - /tapestry/tapestry4/trunk/framework/src/java/org/apache/tapestry/html/dojo/
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
To answer the last question: I would oppose any linking outside.
As to how to handle this, I don't know. I do see it as an issue when a
chunk of the codebase is "deleted and added" for a release. There's no
indication as to what really changed. If we have a dependency on it, I
believe we should use released versions only, then have them controlled
(or *cringe* referenced as a dependency by maven) and used like jars are
now. I am, of course, speaking of the cuff as I know very little about
how you're referencing dojo - but my initial concern remains. If we have
to blindly upgrade a portion of our codebase "once per tapestry
release", I believe we have a problem.
Jesse Kuhnert wrote:
> Yeah it will definitely be something that needs to happen at least once per
> tapestry release. I'm definitely open to ideas :) In other projects I've
> worked on we've done an svn link to the dojo src itself while developing
> and
> only built a compressed release when deploying it to production.
>
> We're getting closer to that I think, but I also want to start "building"
> the tapestry js portions for release builds as well. (ie you can package
> and
> compress js for external packages using the same build stuff that dojo
> does.
> ) Much like the unit tests though I'm less than thrilled with the idea of
> having to require someone to have a working dojo svn checked out on their
> system to build tapestry. The unit test portion I have fixed with our
> custom
> ant task. I definitely feel comfortable enough with the rhino engine API
> now
> that I think I can do the same thing for building stuff as well..
>
> My big question though is are we allowed to link directly to an external
> svn
> repository like that, and if so - do we even want to?
>
> On 5/14/06, Brian K. Wallace <br...@transmorphix.com> wrote:
>>
> Is this something we're going to have to do for dojo upgrades? Is this
> something that could be bundled better to alleviate the need to remove
> and replace on upgrades?
>
> jkuhnert@apache.org wrote:
>> Author: jkuhnert
>> Date: Sat May 13 09:33:17 2006
>> New Revision: 406126
>
>> URL: http://svn.apache.org/viewcvs?rev=406126&view=rev
>> Log:
>> Removing to upgrade
>
>> Removed:
>
> tapestry/tapestry4/trunk/framework/src/java/org/apache/tapestry/html/dojo/
>
>
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEZ1tyaCoPKRow/gARAk1jAJ4nhTfE+SIN8PSLlCdMDE/EceH7vwCg1bHd
Z45yuyeqCZeDcOtqt39nJvo=
=bzIz
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: svn commit: r406126 - /tapestry/tapestry4/trunk/framework/src/java/org/apache/tapestry/html/dojo/
Posted by Jesse Kuhnert <jk...@gmail.com>.
Yeah it will definitely be something that needs to happen at least once per
tapestry release. I'm definitely open to ideas :) In other projects I've
worked on we've done an svn link to the dojo src itself while developing and
only built a compressed release when deploying it to production.
We're getting closer to that I think, but I also want to start "building"
the tapestry js portions for release builds as well. (ie you can package and
compress js for external packages using the same build stuff that dojo does.
) Much like the unit tests though I'm less than thrilled with the idea of
having to require someone to have a working dojo svn checked out on their
system to build tapestry. The unit test portion I have fixed with our custom
ant task. I definitely feel comfortable enough with the rhino engine API now
that I think I can do the same thing for building stuff as well..
My big question though is are we allowed to link directly to an external svn
repository like that, and if so - do we even want to?
On 5/14/06, Brian K. Wallace <br...@transmorphix.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Is this something we're going to have to do for dojo upgrades? Is this
> something that could be bundled better to alleviate the need to remove
> and replace on upgrades?
>
> jkuhnert@apache.org wrote:
> > Author: jkuhnert
> > Date: Sat May 13 09:33:17 2006
> > New Revision: 406126
> >
> > URL: http://svn.apache.org/viewcvs?rev=406126&view=rev
> > Log:
> > Removing to upgrade
> >
> > Removed:
> >
> tapestry/tapestry4/trunk/framework/src/java/org/apache/tapestry/html/dojo/
> >
> >
> >
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
>
> iD8DBQFEZ1A1aCoPKRow/gARAvHrAJ9hEZJioNN656vE/LqI6p/M/LlhUwCfcaP1
> j2/SWuYxVGFxW1Mx4pNqj6M=
> =7NCL
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.
Re: svn commit: r406126 - /tapestry/tapestry4/trunk/framework/src/java/org/apache/tapestry/html/dojo/
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is this something we're going to have to do for dojo upgrades? Is this
something that could be bundled better to alleviate the need to remove
and replace on upgrades?
jkuhnert@apache.org wrote:
> Author: jkuhnert
> Date: Sat May 13 09:33:17 2006
> New Revision: 406126
>
> URL: http://svn.apache.org/viewcvs?rev=406126&view=rev
> Log:
> Removing to upgrade
>
> Removed:
> tapestry/tapestry4/trunk/framework/src/java/org/apache/tapestry/html/dojo/
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEZ1A1aCoPKRow/gARAvHrAJ9hEZJioNN656vE/LqI6p/M/LlhUwCfcaP1
j2/SWuYxVGFxW1Mx4pNqj6M=
=7NCL
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org