| AspectJ and CVS [message #45300] |
Wed, 22 December 2004 12:08  |
Eclipse User |
|
|
|
Originally posted by: sekar.gopinathan.fhlbny.com
I created two aspect projects and checked it into cvs. I noticed that I
had two hidden files namely
1 .generated.ajsym
2 .generated.lst
Should these files be checked in as well? Or are these files some thing
like the .class files?
Also I noticed that the properties specified in the output jar and aspectj
path are not moved into cvs. So I was trying find where these project
properties are stored and was unsuccessfull. Has anyone used aspectj
projects with CVS? If so any suggetions as to how I can overcome this?
I am using Eclipse 3.0/AJDT 2.0M2 and JRE 1.4.2.
Thanks
SG
|
|
|
|
| Re: AspectJ and CVS [message #45432 is a reply to message #45343] |
Mon, 03 January 2005 20:37  |
| Eclipse User |
|
|
|
Originally posted by: sekar.gopinathan.fhlbny.com
> No, you shouldn't check these in as they are generally specific to a given
> eclipse installation, and so aren't useful anywhere else.
hmmm... One thing we do here is to one single eclipse installation on
the network and then create multiple user directories with the workspace
for them under these directories. For example
networkdrive:\j2ee\tools\eclipse - is the eclipse installation
and \j2ee\users\user1
\j2ee\users\user2
are user directories. Once setup up this way, each user has a shortcut
that points to the same eclipse installation in \j2ee\tools\eclipse
Q1: Are we doing something here that eclipse was not designed to do.
Q2: Does this mean in order get AspectJ working "properly". we have to
have an eclipse per user. I use the word "properly" because I get some
wierd exceptions. Something that brings up a small message box. I
generally ignore it. Sometimes I have to clean all my projects once or
twice to remove all the errors and compile fine. Can this be related to
the setup we have?
>The same is true for Java properties under JDT in Eclipse
> 3.0. This is being addressed in the Eclipse 3.1 line, and we hope to
> implement something similar for AJDT settings. We have enhancement 40446
> open for this (https://bugs.eclipse.org/bugs/show_bug.cgi?id=40446). We
> appreciate how useful this would be, and hope to implement it soon.
I guessed it would be treated like "java build path" entries. Just
curious...are there any particular design reason why it is not treated
like "java build path" entries from storage perpective?
Thanks
sekar
Matt Chapman wrote:
> On Wed, 22 Dec 2004 17:08:10 +0000, Sekar Gopinathan wrote:
>> I created two aspect projects and checked it into cvs. I noticed that I
>> had two hidden files namely
>> 1 .generated.ajsym
>> 2 .generated.lst
>>
>> Should these files be checked in as well? Or are these files some thing
>> like the .class files?
> No, you shouldn't check these in as they are generally specific to a given
> eclipse installation, and so aren't useful anywhere else.
>> Also I noticed that the properties specified in the output jar and aspectj
>> path are not moved into cvs.
> That is correct. The same is true for Java properties under JDT in Eclipse
> 3.0. This is being addressed in the Eclipse 3.1 line, and we hope to
> implement something similar for AJDT settings. We have enhancement 40446
> open for this (https://bugs.eclipse.org/bugs/show_bug.cgi?id=40446). We
> appreciate how useful this would be, and hope to implement it soon.
> Regards,
> Matt.
|
|
|
| Re: AspectJ and CVS [message #45490 is a reply to message #45432] |
Tue, 04 January 2005 12:26 |
| Eclipse User |
|
|
|
Originally posted by: mchapman.uk.ibm.com
On Tue, 04 Jan 2005 01:37:23 +0000, Sekar Gopinathan wrote:
> hmmm... One thing we do here is to one single eclipse installation on
> the network and then create multiple user directories with the workspace
> for them under these directories. For example
> networkdrive:\j2ee\tools\eclipse - is the eclipse installation and
> \j2ee\users\user1
> \j2ee\users\user2
> are user directories. Once setup up this way, each user has a shortcut
> that points to the same eclipse installation in \j2ee\tools\eclipse
> Q1: Are we doing something here that eclipse was not designed to do.
As far as I'm aware that sort of arrangement should be okay.
> Q2: Does
> this mean in order get AspectJ working "properly". we have to have an
> eclipse per user. I use the word "properly" because I get some wierd
> exceptions. Something that brings up a small message box. I generally
> ignore it. Sometimes I have to clean all my projects once or twice to
> remove all the errors and compile fine. Can this be related to the setup
> we have?
Sounds like it might be a bug. I don't think we've done any testing
involving network drives and multiple workspaces. When you get the
problems again, could you raise a bug? Please include the exact text of
any messages, any errors from the .metalog/.log file, and the versions of
Eclipse and AJDT you are using.
> I guessed it would be treated like "java build path" entries. Just
> curious...are there any particular design reason why it is not treated
> like "java build path" entries from storage perpective?
I guess that would involve adding our own entries to the .classpath file
for that project. We will investigate that, although I'm concerned doing
so might confuse JDT and anyone else who reads or writes the .classpath
file.
Regards,
Matt.
|
|
|
| Re: AspectJ and CVS [message #585464 is a reply to message #45300] |
Wed, 22 December 2004 14:31 |
| Eclipse User |
|
|
|
On Wed, 22 Dec 2004 17:08:10 +0000, Sekar Gopinathan wrote:
> I created two aspect projects and checked it into cvs. I noticed that I
> had two hidden files namely
> 1 .generated.ajsym
> 2 .generated.lst
>
> Should these files be checked in as well? Or are these files some thing
> like the .class files?
No, you shouldn't check these in as they are generally specific to a given
eclipse installation, and so aren't useful anywhere else.
> Also I noticed that the properties specified in the output jar and aspectj
> path are not moved into cvs.
That is correct. The same is true for Java properties under JDT in Eclipse
3.0. This is being addressed in the Eclipse 3.1 line, and we hope to
implement something similar for AJDT settings. We have enhancement 40446
open for this (https://bugs.eclipse.org/bugs/show_bug.cgi?id=40446). We
appreciate how useful this would be, and hope to implement it soon.
Regards,
Matt.
|
|
|
| Re: AspectJ and CVS [message #585501 is a reply to message #45343] |
Mon, 03 January 2005 20:37 |
| Eclipse User |
|
|
|
Originally posted by: sekar.gopinathan.fhlbny.com
> No, you shouldn't check these in as they are generally specific to a given
> eclipse installation, and so aren't useful anywhere else.
hmmm... One thing we do here is to one single eclipse installation on
the network and then create multiple user directories with the workspace
for them under these directories. For example
networkdrive:\j2ee\tools\eclipse - is the eclipse installation
and \j2ee\users\user1
\j2ee\users\user2
are user directories. Once setup up this way, each user has a shortcut
that points to the same eclipse installation in \j2ee\tools\eclipse
Q1: Are we doing something here that eclipse was not designed to do.
Q2: Does this mean in order get AspectJ working "properly". we have to
have an eclipse per user. I use the word "properly" because I get some
wierd exceptions. Something that brings up a small message box. I
generally ignore it. Sometimes I have to clean all my projects once or
twice to remove all the errors and compile fine. Can this be related to
the setup we have?
>The same is true for Java properties under JDT in Eclipse
> 3.0. This is being addressed in the Eclipse 3.1 line, and we hope to
> implement something similar for AJDT settings. We have enhancement 40446
> open for this (https://bugs.eclipse.org/bugs/show_bug.cgi?id=40446). We
> appreciate how useful this would be, and hope to implement it soon.
I guessed it would be treated like "java build path" entries. Just
curious...are there any particular design reason why it is not treated
like "java build path" entries from storage perpective?
Thanks
sekar
Matt Chapman wrote:
> On Wed, 22 Dec 2004 17:08:10 +0000, Sekar Gopinathan wrote:
>> I created two aspect projects and checked it into cvs. I noticed that I
>> had two hidden files namely
>> 1 .generated.ajsym
>> 2 .generated.lst
>>
>> Should these files be checked in as well? Or are these files some thing
>> like the .class files?
> No, you shouldn't check these in as they are generally specific to a given
> eclipse installation, and so aren't useful anywhere else.
>> Also I noticed that the properties specified in the output jar and aspectj
>> path are not moved into cvs.
> That is correct. The same is true for Java properties under JDT in Eclipse
> 3.0. This is being addressed in the Eclipse 3.1 line, and we hope to
> implement something similar for AJDT settings. We have enhancement 40446
> open for this (https://bugs.eclipse.org/bugs/show_bug.cgi?id=40446). We
> appreciate how useful this would be, and hope to implement it soon.
> Regards,
> Matt.
|
|
|
| Re: AspectJ and CVS [message #585527 is a reply to message #45432] |
Tue, 04 January 2005 12:26 |
| Eclipse User |
|
|
|
On Tue, 04 Jan 2005 01:37:23 +0000, Sekar Gopinathan wrote:
> hmmm... One thing we do here is to one single eclipse installation on
> the network and then create multiple user directories with the workspace
> for them under these directories. For example
> networkdrive:\j2ee\tools\eclipse - is the eclipse installation and
> \j2ee\users\user1
> \j2ee\users\user2
> are user directories. Once setup up this way, each user has a shortcut
> that points to the same eclipse installation in \j2ee\tools\eclipse
> Q1: Are we doing something here that eclipse was not designed to do.
As far as I'm aware that sort of arrangement should be okay.
> Q2: Does
> this mean in order get AspectJ working "properly". we have to have an
> eclipse per user. I use the word "properly" because I get some wierd
> exceptions. Something that brings up a small message box. I generally
> ignore it. Sometimes I have to clean all my projects once or twice to
> remove all the errors and compile fine. Can this be related to the setup
> we have?
Sounds like it might be a bug. I don't think we've done any testing
involving network drives and multiple workspaces. When you get the
problems again, could you raise a bug? Please include the exact text of
any messages, any errors from the .metalog/.log file, and the versions of
Eclipse and AJDT you are using.
> I guessed it would be treated like "java build path" entries. Just
> curious...are there any particular design reason why it is not treated
> like "java build path" entries from storage perpective?
I guess that would involve adding our own entries to the .classpath file
for that project. We will investigate that, although I'm concerned doing
so might confuse JDT and anyone else who reads or writes the .classpath
file.
Regards,
Matt.
|
|
|
Powered by
FUDForum. Page generated in 0.08303 seconds
Home