Issue 661 seems to be still not fixed in 1.132

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 661 seems to be still not fixed in 1.132

tvworks

I have a svn change in a module that shows up in the top level project’s changes, but it does not show up in the module’s changes.

 

Jason Chaffee

Software Architect/Server Team Manager

TVWorks LLC

APPLICATIONS DIVISION

Tel : 415.380.6316

Cell: 415.637.8061

 

 

Reply | Threaded
Open this post in threaded view
|

Re: Issue 661 seems to be still not fixed in 1.132

Kohsuke Kawaguchi
Administrator
Jason Chaffee wrote:
> I have a svn change in a module that shows up in the top level project's
> changes, but it does not show up in the module's changes.

Can you tell me the build # of the project where the change shows up and
the build # of the module where the change doesn't show up?

I have a hypothesis that I'd like to verify.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Re: Issue 661 seems to be still not fixed in 1.132

Nord, James-2
>
> Jason Chaffee wrote:
> > I have a svn change in a module that shows up in the top level
> > project's changes, but it does not show up in the module's changes.
>
> Can you tell me the build # of the project where the change
> shows up and the build # of the module where the change
> doesn't show up?
>
> I have a hypothesis that I'd like to verify.
>
I have the same issue using 1.132 (and previous)

Build numbers are all the same #183 in this instance.

Could it be because I use subversion with per project trunks as opposed
to per repository trunks?

This it the changelist for build 183 (with some name changes)

Summary
add new directory structure for test classes
Revision 245 by nordj:

add new directory structure for test classes  
 
/My-App/trunk/My-Module/src/test/java/com/mycorp/mydiv/multicastreceiver

 /My-App/trunk/My-Module/src/test/java/com/mycorp
 /My-App/trunk/My-Module/src/test/java/com/mycorp/mydiv
 /My-App/trunk/My-Module/src/test/java/com

Which shows up against the My-App project but not the My-Module module

/James
*********************************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only.  Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited.  If you have received this message in error, please immediately notify the [hidden email] and destroy the original message.  Messages sent to and from NDS may be monitored.  NDS cannot guarantee any message delivery method is secure or error-free.  Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.  We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission.  You should carry out your own virus checks before opening any attachment.  Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00
**********************************************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Re: Issue 661 seems to be still not fixed in 1.132

tvworks
In reply to this post by Kohsuke Kawaguchi
They are the same build number, I made certain of that because I thought
it might be due to a different number, but it still didn't show up.

-----Original Message-----
From: Kohsuke Kawaguchi [mailto:[hidden email]]
Sent: Thursday, August 23, 2007 5:40 PM
To: [hidden email]
Cc: [hidden email]
Subject: Re: Issue 661 seems to be still not fixed in 1.132

Jason Chaffee wrote:
> I have a svn change in a module that shows up in the top level
project's
> changes, but it does not show up in the module's changes.

Can you tell me the build # of the project where the change shows up and

the build # of the module where the change doesn't show up?

I have a hypothesis that I'd like to verify.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Issue 661 seems to be still not fixed in 1.132

Kohsuke Kawaguchi
Administrator

Thanks. Any chance either of you can zip up your job directory and send
it to me? You can delete the "workspace directory" if it contains
sensitive information. And I only need the record for the build that
exhibits the problem, but I suppose filtering that out would be tedious.

Jason Chaffee wrote:

> They are the same build number, I made certain of that because I thought
> it might be due to a different number, but it still didn't show up.
>
> -----Original Message-----
> From: Kohsuke Kawaguchi [mailto:[hidden email]]
> Sent: Thursday, August 23, 2007 5:40 PM
> To: [hidden email]
> Cc: [hidden email]
> Subject: Re: Issue 661 seems to be still not fixed in 1.132
>
> Jason Chaffee wrote:
>> I have a svn change in a module that shows up in the top level
> project's
>> changes, but it does not show up in the module's changes.
>
> Can you tell me the build # of the project where the change shows up and
>
> the build # of the module where the change doesn't show up?
>
> I have a hypothesis that I'd like to verify.
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Re: Issue 661 seems to be still not fixed in 1.132

tvworks
I will reproduce it with a simple project and send you the zip.

-----Original Message-----
From: Kohsuke Kawaguchi [mailto:[hidden email]]
Sent: Friday, August 24, 2007 6:25 PM
To: [hidden email]
Cc: [hidden email]
Subject: Re: Issue 661 seems to be still not fixed in 1.132


Thanks. Any chance either of you can zip up your job directory and send
it to me? You can delete the "workspace directory" if it contains
sensitive information. And I only need the record for the build that
exhibits the problem, but I suppose filtering that out would be tedious.

Jason Chaffee wrote:
> They are the same build number, I made certain of that because I
thought

> it might be due to a different number, but it still didn't show up.
>
> -----Original Message-----
> From: Kohsuke Kawaguchi [mailto:[hidden email]]
> Sent: Thursday, August 23, 2007 5:40 PM
> To: [hidden email]
> Cc: [hidden email]
> Subject: Re: Issue 661 seems to be still not fixed in 1.132
>
> Jason Chaffee wrote:
>> I have a svn change in a module that shows up in the top level
> project's
>> changes, but it does not show up in the module's changes.
>
> Can you tell me the build # of the project where the change shows up
and
>
> the build # of the module where the change doesn't show up?
>
> I have a hypothesis that I'd like to verify.
>


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]