Notes/Domino XPages Development Forum - Prohibit design replace on files like .classpath & .project

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

~George Minponebergettu

Oct 7, 2011, 9:02 AM

24 Posts

Prohibit design replace on files like .classpath & .project

Category: Other Domino Designer Tooling
Platform: Windows
Release: 8.5.2
Role: Developer
Tags: design replace .classpath
Replies: 2

I'd like to share some java code between agents and XPages. As Domino reference different sets of java in these two scenarios, I have to maintain the consistency manually. These are the backgrounds of my question.

I found the .classpath file not updated after a design replace. Further investigation revealed files like .classpath, build.properties, java source and class files are sometimes set to prohibit design replace, i.e. have an additional 'P' in $flags. But I cannot see any rules. I have three dbs. In the first one, .project, .xsp.properties & xspdesign.properties have 'P'; in the second one, build.properties, plugin.xml, .classpath & activator.class have 'P'; in the third one just created from the template of the second, none has 'P'.

Anyone knows about such quirks?

~Elizabeth Xanluzenobu

Oct 7, 2011, 9:33 PM

2 Posts

Re: Prohibit design replace on files like .classpath & .project

This was resolved in 8.5.3. We do by default still set the P flag on plugin.xml and .project, but you can override these by setting them in the new dialog available off of the application right click menu. Previous releases set the P flag on all hidden files automatically (unless they were copied in from a standard template where those flags are removed before shipping). And editing them with older Designers would set the P flag on, also. You should see Designer 8.5.3 resolve these issues (we clean up the flags automatically when we safely can in 8.5.3).

Hope this helps.

~George Minponebergettu

Oct 11, 2011, 2:15 AM

24 Posts

Re: Prohibit design replace on files like .classpath & .project

Thanks a lot.

P.S. I've tested with my 8.5.2 client and found the following rules stand.

In a db newly created with a template, all those files have no 'P' flag set.

Once edited, if the db where the element resides inherits design from a template, P flag is set. If the db is template itself and doesn't inherit design from other db, P flag is not set.

Hi Maureen, one more question, per my understanding, only the 8.5.3 designer is needed to fix these issues. The server is not mandated to upgrade. Am I right?