It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,862

question asked: Jul 01 '10, 8:53 a.m.
question was seen: 6,934 times
last updated: Jul 01 '10, 8:53 a.m.

Related questions

Checkin generated EJB code in RTC

0
Marc van Helvoort (16) | asked Jul 01 '10, 8:53 a.m.
Hi,

I have some problems when I want to checkin and deliver generated EJB code into RTC. After the generation process the generated files are not showing up in the pending changes view, and they are impossible to deliver.

I have checked the .ignore files and the Ignored Resources option in the preferences.

And yes we do need them to check them in, because our building process needs them.

Can anybody explain why those files are ignored, and how and where to change this setting.

Regards,

Marc

5 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Jul 01 '10, 11:25 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Have you tried a "refresh" on the Eclipse project containing the
generated files? If your code generator notifies Eclipse about file
changes, then the Pending Changes view will be automatically updated,
but if it doesn't, then you have to tell Eclipse to scan those
directories for modified files.

If refresh doesn't help, look for a .jazzignore file in the directory
containing those files, and if it exists, check its content.

Cheers,
Geoff

On 7/1/2010 9:08 AM, marcvanhelvoort wrote:
Hi,

I have some problems when I want to checkin and deliver generated EJB
code into RTC. After the generation process the generated files are
not showing up in the pending changes view, and they are impossible
to deliver.

I have checked the .ignore files and the Ignored Resources option in
the preferences.

And yes we do need them to check them in, because our building process
needs them.

Can anybody explain why those files are ignored, and how and where to
change this setting.

Regards,

Marc
0
permanent link
Marc van Helvoort (16) | answered Jul 02 '10, 5:57 a.m.
Yes, I did, multiple times. I even created a new java file in the generated packages, but that file was also ignored. One way or an other, RAD keeps somewhere a setting that those files shouldn't be checkedin. But where?
0
permanent link
Marc van Helvoort (16) | answered Jul 02 '10, 6:03 a.m.
And there are no .jazzignore files in those directories
0
permanent link
Jose Miguel Ordax Cassa (2.4k●4●126●100) | answered Jul 02 '10, 6:47 a.m.
On 7/2/2010 12:08 PM, marcvanhelvoort wrote:
And there are no .jazzignore files in those directories


I think the issue is related to the fact those artifacts are marked as
"derived". Double check by clicking right button on any package or class
generated, properties, resource.

By default, "derived" artifacts are not notified to SCM implementations
in Eclipse. Don't know the way to avoid this behavior... you should
investigate at Eclipse.org (I think).

Hope this helps,

Chemi.
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Jul 02 '10, 5:43 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
To see if a file has been marked as "derived", as for its properties.
On the first tab, you'll see a "derived" check box.
If it is checked, uncheck it (:-).
If it is not checked, then this isn't your problem.

Cheers,
Geoff

On 7/2/2010 6:47 AM, Chemi wrote:
On 7/2/2010 12:08 PM, marcvanhelvoort wrote:
And there are no .jazzignore files in those directories


I think the issue is related to the fact those artifacts are marked as
"derived". Double check by clicking right button on any package or class
generated, properties, resource.

By default, "derived" artifacts are not notified to SCM implementations
in Eclipse. Don't know the way to avoid this behavior... you should
investigate at Eclipse.org (I think).

Hope this helps,

Chemi.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.