You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by co...@apache.org on 2005/11/12 19:08:02 UTC
svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Author: costin
Date: Sat Nov 12 10:07:58 2005
New Revision: 332806
URL: http://svn.apache.org/viewcvs?rev=332806&view=rev
Log:
Another change - sorry if I mess up everything, but the svn plugin is
really frustrating and I think it is important to have a consistent
environment when working in eclise and in ant/CLI.
Added:
tomcat/jasper/tc5.5.x/.classpath
tomcat/jasper/tc5.5.x/.project
Added: tomcat/jasper/tc5.5.x/.classpath
URL: http://svn.apache.org/viewcvs/tomcat/jasper/tc5.5.x/.classpath?rev=332806&view=auto
==============================================================================
--- tomcat/jasper/tc5.5.x/.classpath (added)
+++ tomcat/jasper/tc5.5.x/.classpath Sat Nov 12 10:07:58 2005
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+ <classpathentry kind="src" path="jasper2/src/share"/>
+ <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
+ <classpathentry combineaccessrules="false" kind="src" path="servletapi"/>
+ <classpathentry kind="var" path="TOMCAT_LIBS_BASE/commons-logging-1.0.4/commons-logging-api.jar"/>
+ <classpathentry kind="var" path="TOMCAT_LIBS_BASE/apache-ant-1.6.5/lib/ant.jar"/>
+ <classpathentry kind="var" path="TOMCAT_LIBS_BASE/commons-el-1.0/commons-el.jar"/>
+ <classpathentry kind="var" path="TOMCAT_LIBS_BASE/eclipse/plugins/org.eclipse.jdt.core_3.1.1.jar"/>
+ <classpathentry kind="output" path="bin"/>
+</classpath>
Added: tomcat/jasper/tc5.5.x/.project
URL: http://svn.apache.org/viewcvs/tomcat/jasper/tc5.5.x/.project?rev=332806&view=auto
==============================================================================
--- tomcat/jasper/tc5.5.x/.project (added)
+++ tomcat/jasper/tc5.5.x/.project Sat Nov 12 10:07:58 2005
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>jasper</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.jdt.core.javabuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.jdt.core.javanature</nature>
+ </natures>
+</projectDescription>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Posted by Mark Thomas <ma...@apache.org>.
Mark Thomas wrote:
> I had to add https://svn.apache.org/asf/repos/tomcat to my list of
Should be https://svn.apache.org/repos/asf/tomcat
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Posted by Mark Thomas <ma...@apache.org>.
Costin Manolache wrote:
>>>How are you making subclipse see the project ? Team->share doesn't do it for me.
>>
>>I had to add https://svn.apache.org/asf/repos/tomcat to my list of
>>repositories in Subclipse SVN repository view. Once I did that, it all
>>just worked.
>
>
> What version are you using ? I have it in my list of repos.
Subclipse 0.9.37
Eclipse 3.1.0
I did find today that I needed to start with a completely clean
workspace or previous settings seemed to hang around and confuse
Subclipse.
> Please check the same thing with current/ - if it doesn't work, then
> don't change build.xml :-)
It worked. I have updated build.xml to use current.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Posted by Costin Manolache <co...@gmail.com>.
On 11/13/05, Mark Thomas <ma...@apache.org> wrote:
> Costin Manolache wrote:
> > I'm confused - build.xml seems to checkout the real dirs, not current
> > - I found no reference to current/ in build.xml
>
> I think that makes two of us ;)
> You are right. We could change build.xml to use current. I'll test
> this and if it works, make the change.
> I am going to try and create a new, clean TC5.5.x build environment. I'll try and iron out any
> inconsistencies as I go.
That makes two of us :-) What do you think of the build.xml in sandbox ?
The current multi-layer build.xml, combined with svn, naming
conventions, etc gives me headaches - unfortunately I no longer have a
lot of time for tomcat, so keeping track is much harder. But I'm very
happy with eclipse build - I run tomcat from inside eclipse, using the
launcher I checkedin - since it's the same environment with
runtime-all.jar that I'm working on.
>
> > How are you making subclipse see the project ? Team->share doesn't do it for me.
>
> I had to add https://svn.apache.org/asf/repos/tomcat to my list of
> repositories in Subclipse SVN repository view. Once I did that, it all
> just worked.
What version are you using ? I have it in my list of repos.
Please check the same thing with current/ - if it doesn't work, then
don't change build.xml :-)
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Posted by Mark Thomas <ma...@apache.org>.
Costin Manolache wrote:
> I'm confused - build.xml seems to checkout the real dirs, not current
> - I found no reference to current/ in build.xml
I think that makes two of us ;)
You are right. We could change build.xml to use current. I'll test
this and if it works, make the change. I am going to try and create a
new, clean TC5.5.x build environment. I'll try and iron out any
inconsistencies as I go.
> How are you making subclipse see the project ? Team->share doesn't do it for me.
I had to add https://svn.apache.org/asf/repos/tomcat to my list of
repositories in Subclipse SVN repository view. Once I did that, it all
just worked.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Posted by Costin Manolache <co...@gmail.com>.
On 11/12/05, Mark Thomas <ma...@apache.org> wrote:
> Costin Manolache wrote:
> >>>What is "svn co .../current" doing - I was using this before realizing
> >>>that current doesn't work in eclipse, never used resources/build.xml
> >>
> >>It is using svn:externals to bring the various modules together under
> >>a single directory. See the svn manual for an explanation of what
> >>externals are and how they work.
> >
> >
> > Except they don't seem to work from the eclipse plugin ( at least not for me ).
>
> You can't see the contents through the http interface either :(
>
> These directories aren't browseable through any svn client that I have
> tried. The externals are properties of the directory and get processed
> on checkout. This is why you need to do the checkout using build.xml
> first. Once checked out via build.xml , Subclipse works fine for me.
I'm confused - build.xml seems to checkout the real dirs, not current
- I found no reference to current/ in build.xml
How are you making subclipse see the project ? Team->share doesn't do it for me.
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Posted by Mark Thomas <ma...@apache.org>.
Costin Manolache wrote:
>>>What is "svn co .../current" doing - I was using this before realizing
>>>that current doesn't work in eclipse, never used resources/build.xml
>>
>>It is using svn:externals to bring the various modules together under
>>a single directory. See the svn manual for an explanation of what
>>externals are and how they work.
>
>
> Except they don't seem to work from the eclipse plugin ( at least not for me ).
You can't see the contents through the http interface either :(
These directories aren't browseable through any svn client that I have
tried. The externals are properties of the directory and get processed
on checkout. This is why you need to do the checkout using build.xml
first. Once checked out via build.xml , Subclipse works fine for me.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Posted by Costin Manolache <co...@gmail.com>.
BTW - Mark, many thanks for all this work in moving to SVN, I
understand how difficult it is
and how limiting and immature SVN and svn tools are.
Costin
On 11/12/05, Costin Manolache <co...@gmail.com> wrote:
> On 11/12/05, Mark Thomas <ma...@apache.org> wrote:
> > Costin Manolache wrote:
> > > I'll fix this, sorry - I think I have made few changes to my properties.
> > >
> > > What is "svn co .../current" doing - I was using this before realizing
> > > that current doesn't work in eclipse, never used resources/build.xml
> >
> > It is using svn:externals to bring the various modules together under
> > a single directory. See the svn manual for an explanation of what
> > externals are and how they work.
>
> Except they don't seem to work from the eclipse plugin ( at least not for me ).
>
>
>
> >
> > > In the top level build.xml - jasper project is still called "jasper" -
> > > are we supposed to co jasper2 as jasper ? This is all so confusing and
> > > painfull...
> >
> > Agreed this is painful but the build script does all this for you.
> > build.xml and Subclipse are not totally interchangeable. They will
> > work together if you do the initial checkout using build.xml as per
> > the directions I wrote for Henri.
>
> No luck with this - subclipse refused to import. What version of
> eclipse/subclipse is working
> for you ?
>
>
>
> > Removing the jasper2 directory would be best but I didn't have the
> > time to fix everything this might break.
>
> Ok, but if we are checking out jasper2 directly - can we call the directory
> "jasper2" and use "jasper2" in the build.xml ?
>
> My problem is that there are too many variations and indirection and
> conflicting naming
> schemes that are involved - in jasper case, the project is called
> "Jasper", the svn dir is jasper2,
> and build.xml is using "jasper". And it is checked out in a different
> way than all other components - not from tc5.5.x ( or truck - another
> variation in connector ), but a subdir.
>
>
>
> > > Is it too late to just move everything in one directory - and avoid
> > > all this forest ?
> >
> > The current directory does exactly this using externals.
>
> Except it doesn't allways work - and it doesn't match what
> resources/build.xml is doing.
> If someone is using current/ ( as I did in CLI ) - he'll have a
> different structure than someone using build.xml. And if someone uses
> "checkout project" from eclipse - he'll get yet another structure, not
> compatible with either build.xml or resources/build.xml.
>
>
>
> >
> > > I think we allways tag and branch all the components
> > > ( jasper, container, connectors, etc ), it is so much easier to work
> > > with a single tree. Really - there are historic reasons why we had
> > > this in CVS, but they are long gone..
> >
> > I did look at other structures when we moved to SVN. Our current
> > structure is the one that:
> > - enabled us to migrate in stages
> > - required minimal changes to our build scripts
> > - made little/no difference to the effort required to create a release
> > - required minimal manual (actually scripted) intervention to do the
> > migration
> > - enabled us to maintain the traceability of our previous releases
> >
> > All the other options I considered caused big problems in one or more
> > of these areas and offered little benefit. That being said, if you
> > have a proposal for an alternative structure then I would love to see it.
>
> Well, my proposal is to at least keep the naming and scheme consistent.
>
> No Jasper/jasper/jasper2 - only one. If current/ can be made to work
> with subclipse - use it
> in resources/build.xml as well. If not - remove it, and stick with
> what is used in resources/
>
> Is it possible to "move" svn repositories, preserving history ?
>
> To be honest - if having a spaghetti tree is the price for preserving
> history, let's just create a new repo, copy the current head from all
> the subtrees we care - and move on. It sucks - but at least in future
> things will be simpler.
>
> Or just move back to CVS - it just worked. It ASF infra can't host it
> - maybe find someone who can, or move it to sourceforge or some place
> that can support CVS.
>
> Costin
>
> >
> > Mark
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: dev-help@tomcat.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Posted by Costin Manolache <co...@gmail.com>.
On 11/12/05, Mark Thomas <ma...@apache.org> wrote:
> Costin Manolache wrote:
> > I'll fix this, sorry - I think I have made few changes to my properties.
> >
> > What is "svn co .../current" doing - I was using this before realizing
> > that current doesn't work in eclipse, never used resources/build.xml
>
> It is using svn:externals to bring the various modules together under
> a single directory. See the svn manual for an explanation of what
> externals are and how they work.
Except they don't seem to work from the eclipse plugin ( at least not for me ).
>
> > In the top level build.xml - jasper project is still called "jasper" -
> > are we supposed to co jasper2 as jasper ? This is all so confusing and
> > painfull...
>
> Agreed this is painful but the build script does all this for you.
> build.xml and Subclipse are not totally interchangeable. They will
> work together if you do the initial checkout using build.xml as per
> the directions I wrote for Henri.
No luck with this - subclipse refused to import. What version of
eclipse/subclipse is working
for you ?
> Removing the jasper2 directory would be best but I didn't have the
> time to fix everything this might break.
Ok, but if we are checking out jasper2 directly - can we call the directory
"jasper2" and use "jasper2" in the build.xml ?
My problem is that there are too many variations and indirection and
conflicting naming
schemes that are involved - in jasper case, the project is called
"Jasper", the svn dir is jasper2,
and build.xml is using "jasper". And it is checked out in a different
way than all other components - not from tc5.5.x ( or truck - another
variation in connector ), but a subdir.
> > Is it too late to just move everything in one directory - and avoid
> > all this forest ?
>
> The current directory does exactly this using externals.
Except it doesn't allways work - and it doesn't match what
resources/build.xml is doing.
If someone is using current/ ( as I did in CLI ) - he'll have a
different structure than someone using build.xml. And if someone uses
"checkout project" from eclipse - he'll get yet another structure, not
compatible with either build.xml or resources/build.xml.
>
> > I think we allways tag and branch all the components
> > ( jasper, container, connectors, etc ), it is so much easier to work
> > with a single tree. Really - there are historic reasons why we had
> > this in CVS, but they are long gone..
>
> I did look at other structures when we moved to SVN. Our current
> structure is the one that:
> - enabled us to migrate in stages
> - required minimal changes to our build scripts
> - made little/no difference to the effort required to create a release
> - required minimal manual (actually scripted) intervention to do the
> migration
> - enabled us to maintain the traceability of our previous releases
>
> All the other options I considered caused big problems in one or more
> of these areas and offered little benefit. That being said, if you
> have a proposal for an alternative structure then I would love to see it.
Well, my proposal is to at least keep the naming and scheme consistent.
No Jasper/jasper/jasper2 - only one. If current/ can be made to work
with subclipse - use it
in resources/build.xml as well. If not - remove it, and stick with
what is used in resources/
Is it possible to "move" svn repositories, preserving history ?
To be honest - if having a spaghetti tree is the price for preserving
history, let's just create a new repo, copy the current head from all
the subtrees we care - and move on. It sucks - but at least in future
things will be simpler.
Or just move back to CVS - it just worked. It ASF infra can't host it
- maybe find someone who can, or move it to sourceforge or some place
that can support CVS.
Costin
>
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Posted by Mark Thomas <ma...@apache.org>.
Costin Manolache wrote:
> I'll fix this, sorry - I think I have made few changes to my properties.
>
> What is "svn co .../current" doing - I was using this before realizing
> that current doesn't work in eclipse, never used resources/build.xml
It is using svn:externals to bring the various modules together under
a single directory. See the svn manual for an explanation of what
externals are and how they work.
resources/build.xml is the source for the TC5 build.xml that is linked
to on http://tomcat.apache.org/tomcat-5.5-doc/building.html
> In the top level build.xml - jasper project is still called "jasper" -
> are we supposed to co jasper2 as jasper ? This is all so confusing and
> painfull...
Agreed this is painful but the build script does all this for you.
build.xml and Subclipse are not totally interchangeable. They will
work together if you do the initial checkout using build.xml as per
the directions I wrote for Henri.
Removing the jasper2 directory would be best but I didn't have the
time to fix everything this might break.
> Is it too late to just move everything in one directory - and avoid
> all this forest ?
The current directory does exactly this using externals.
> I think we allways tag and branch all the components
> ( jasper, container, connectors, etc ), it is so much easier to work
> with a single tree. Really - there are historic reasons why we had
> this in CVS, but they are long gone..
I did look at other structures when we moved to SVN. Our current
structure is the one that:
- enabled us to migrate in stages
- required minimal changes to our build scripts
- made little/no difference to the effort required to create a release
- required minimal manual (actually scripted) intervention to do the
migration
- enabled us to maintain the traceability of our previous releases
All the other options I considered caused big problems in one or more
of these areas and offered little benefit. That being said, if you
have a proposal for an alternative structure then I would love to see it.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Posted by Costin Manolache <co...@gmail.com>.
I'll fix this, sorry - I think I have made few changes to my properties.
What is "svn co .../current" doing - I was using this before realizing
that current doesn't work in eclipse, never used resources/build.xml
In the top level build.xml - jasper project is still called "jasper" -
are we supposed to co jasper2 as jasper ? This is all so confusing and
painfull...
Is it too late to just move everything in one directory - and avoid
all this forest ? I think we allways tag and branch all the components
( jasper, container, connectors, etc ), it is so much easier to work
with a single tree. Really - there are historic reasons why we had
this in CVS, but they are long gone..
Costin
On 11/12/05, Mark Thomas <ma...@apache.org> wrote:
> The command line build doesn't check out this directory, it checks out
> the jasper2 directory. That is why the .project & .classpath files
> were created one level lower down. Are you using the latest build.xml
> (http://svn.apache.org/repos/asf/tomcat/build/tc5.5.x/resources/build.xml)?
>
>
> Mark
>
> costin@apache.org wrote:
> > Author: costin
> > Date: Sat Nov 12 10:07:58 2005
> > New Revision: 332806
> >
> > URL: http://svn.apache.org/viewcvs?rev=332806&view=rev
> > Log:
> > Another change - sorry if I mess up everything, but the svn plugin is
> > really frustrating and I think it is important to have a consistent
> > environment when working in eclise and in ant/CLI.
> >
> >
> > Added:
> > tomcat/jasper/tc5.5.x/.classpath
> > tomcat/jasper/tc5.5.x/.project
> >
> > Added: tomcat/jasper/tc5.5.x/.classpath
> > URL: http://svn.apache.org/viewcvs/tomcat/jasper/tc5.5.x/.classpath?rev=332806&view=auto
> > ==============================================================================
> > --- tomcat/jasper/tc5.5.x/.classpath (added)
> > +++ tomcat/jasper/tc5.5.x/.classpath Sat Nov 12 10:07:58 2005
> > @@ -0,0 +1,11 @@
> > +<?xml version="1.0" encoding="UTF-8"?>
> > +<classpath>
> > + <classpathentry kind="src" path="jasper2/src/share"/>
> > + <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> > + <classpathentry combineaccessrules="false" kind="src" path="servletapi"/>
> > + <classpathentry kind="var" path="TOMCAT_LIBS_BASE/commons-logging-1.0.4/commons-logging-api.jar"/>
> > + <classpathentry kind="var" path="TOMCAT_LIBS_BASE/apache-ant-1.6.5/lib/ant.jar"/>
> > + <classpathentry kind="var" path="TOMCAT_LIBS_BASE/commons-el-1.0/commons-el.jar"/>
> > + <classpathentry kind="var" path="TOMCAT_LIBS_BASE/eclipse/plugins/org.eclipse.jdt.core_3.1.1.jar"/>
> > + <classpathentry kind="output" path="bin"/>
> > +</classpath>
> >
> > Added: tomcat/jasper/tc5.5.x/.project
> > URL: http://svn.apache.org/viewcvs/tomcat/jasper/tc5.5.x/.project?rev=332806&view=auto
> > ==============================================================================
> > --- tomcat/jasper/tc5.5.x/.project (added)
> > +++ tomcat/jasper/tc5.5.x/.project Sat Nov 12 10:07:58 2005
> > @@ -0,0 +1,17 @@
> > +<?xml version="1.0" encoding="UTF-8"?>
> > +<projectDescription>
> > + <name>jasper</name>
> > + <comment></comment>
> > + <projects>
> > + </projects>
> > + <buildSpec>
> > + <buildCommand>
> > + <name>org.eclipse.jdt.core.javabuilder</name>
> > + <arguments>
> > + </arguments>
> > + </buildCommand>
> > + </buildSpec>
> > + <natures>
> > + <nature>org.eclipse.jdt.core.javanature</nature>
> > + </natures>
> > +</projectDescription>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: dev-help@tomcat.apache.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r332806 - in /tomcat/jasper/tc5.5.x: .classpath .project
Posted by Mark Thomas <ma...@apache.org>.
The command line build doesn't check out this directory, it checks out
the jasper2 directory. That is why the .project & .classpath files
were created one level lower down. Are you using the latest build.xml
(http://svn.apache.org/repos/asf/tomcat/build/tc5.5.x/resources/build.xml)?
Mark
costin@apache.org wrote:
> Author: costin
> Date: Sat Nov 12 10:07:58 2005
> New Revision: 332806
>
> URL: http://svn.apache.org/viewcvs?rev=332806&view=rev
> Log:
> Another change - sorry if I mess up everything, but the svn plugin is
> really frustrating and I think it is important to have a consistent
> environment when working in eclise and in ant/CLI.
>
>
> Added:
> tomcat/jasper/tc5.5.x/.classpath
> tomcat/jasper/tc5.5.x/.project
>
> Added: tomcat/jasper/tc5.5.x/.classpath
> URL: http://svn.apache.org/viewcvs/tomcat/jasper/tc5.5.x/.classpath?rev=332806&view=auto
> ==============================================================================
> --- tomcat/jasper/tc5.5.x/.classpath (added)
> +++ tomcat/jasper/tc5.5.x/.classpath Sat Nov 12 10:07:58 2005
> @@ -0,0 +1,11 @@
> +<?xml version="1.0" encoding="UTF-8"?>
> +<classpath>
> + <classpathentry kind="src" path="jasper2/src/share"/>
> + <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> + <classpathentry combineaccessrules="false" kind="src" path="servletapi"/>
> + <classpathentry kind="var" path="TOMCAT_LIBS_BASE/commons-logging-1.0.4/commons-logging-api.jar"/>
> + <classpathentry kind="var" path="TOMCAT_LIBS_BASE/apache-ant-1.6.5/lib/ant.jar"/>
> + <classpathentry kind="var" path="TOMCAT_LIBS_BASE/commons-el-1.0/commons-el.jar"/>
> + <classpathentry kind="var" path="TOMCAT_LIBS_BASE/eclipse/plugins/org.eclipse.jdt.core_3.1.1.jar"/>
> + <classpathentry kind="output" path="bin"/>
> +</classpath>
>
> Added: tomcat/jasper/tc5.5.x/.project
> URL: http://svn.apache.org/viewcvs/tomcat/jasper/tc5.5.x/.project?rev=332806&view=auto
> ==============================================================================
> --- tomcat/jasper/tc5.5.x/.project (added)
> +++ tomcat/jasper/tc5.5.x/.project Sat Nov 12 10:07:58 2005
> @@ -0,0 +1,17 @@
> +<?xml version="1.0" encoding="UTF-8"?>
> +<projectDescription>
> + <name>jasper</name>
> + <comment></comment>
> + <projects>
> + </projects>
> + <buildSpec>
> + <buildCommand>
> + <name>org.eclipse.jdt.core.javabuilder</name>
> + <arguments>
> + </arguments>
> + </buildCommand>
> + </buildSpec>
> + <natures>
> + <nature>org.eclipse.jdt.core.javanature</nature>
> + </natures>
> +</projectDescription>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org