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
On 11/13/05, Mark Thomas <[EMAIL PROTECTED]> 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.
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROT
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
On 11/12/05, Mark Thomas <[EMAIL PROTECTED]> 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 togethe
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
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 <[EMAIL PROTECTED]> wrote:
> On 11/12/05, Mark Thomas <[EMAIL PROTECTED]> wrote:
> > Costin Manolache wrote:
> >
On 11/12/05, Mark Thomas <[EMAIL PROTECTED]> 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/bu
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 to
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 suppos
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
[E
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 eclis
12 matches
Mail list logo
