I have added a config file to my project called mash.chirp.config but there are no code behind files created when I save?
Thanks
Chirpy wasn't finding my config file because the paths should contain back slashses instead of forward slashes!
Works like a charm!
Related
Recently I switched over from the legacy css integration to using the current method of css support via the CN1 Preferences dialog. Ever since then, I've had repeated problems accessing strings from the localization resource file.
A few important points:
I have two theme files, but even importing the strings as a csv file into the theme generated by css doesn't work
I've tried all possible combinations of theme initialization with the two theme files, including initializing just one of them, with no consistent success (occasionally it works, but then if I modify the css and the theme file gets regenerated it stops working again)
I created a brand new project and copied my code into it, imported the string files, and it worked - until I turned on css support. Then I was back to square one
When it fails to work, the method UIManager.getL10NResourceNames() returns an empty array
Any help would be greatly appreciated!
CSS controls the file and as a result you can no longer change the theme.res file by other means. You need to keep a separate localization.res file and load that strictly for the localization functionality of your application. You can use Resources.open("/localization.res") to load an arbitrary resource file.
After much poking around, I found the solution. It turns out my situation was the result of a few non-standard things I did. First of all, I had a theme.res file which I renamed using IntelliJ's Refactor >> Rename function, which renamed the hardcoded css theme name in the build.xml file to my new name. I needed to manually revert that string in order to prevent the css compile task from overwriting my theme file. The second thing I noticed is that sometimes (I'm not clear on what caused this) the theme file was not being refreshed in the /out directory when running the app locally. This would manifest itself, for instance, when I would add an image in the theme file, but when running the code it wouldn't be able to find it in the Resources hashtable. Every time this happens, I now know to just delete the contents of /out, thereby forcing the IDE to rebuild/recopy the theme file (I could probably just copy it manually to the /out directory, but I think deleting it is safest).
I am using getssl to create a SSL from lets-encrypt. I think I have everything setup correct but am running into an issue with the Challenge file. The server I am using MVC on Windows on Liquid Web is not letting me use a file without an extension. If I add .txt to the challenge file it works correctly, so I know the file is accessable.
So I see two choices: First is to have getssl add a file extension to the Challenge file. Second is to allow files without extensions under MVC/Windows.
I have tried changing the web.config file and also looking for changes to the setting but neither have been fruitful.
http://my.site.com/.well-known/acme-challenge/WLasfaweaefqwwqetfgewfweqrtfwefwefsefasdfasdf_W1nuoZqCWbHTU
Found the answer here finally:
Letsencrypt acme-challenge on wordpress or asp.net mvc
Add the config file in the directory you want to download the file from.
When using the thinBackup Jenkins plugin one can configure it to include additional files. It seems impossible to include whole additional folders though.
In our case (see screenshot below) it is adding the secret.* files properly but does fail to include the secrets folder (or in the case shown here the .key files in the secrets folder).
Are we configuring this wrong or is it just not possible to include arbitrary folders?
I played around with regex and if you want to backup all the files in secrets folder, try below regex.
It works fine
^(.*\.xml)|^(secrets|.*\.key|.*\.KEY|.*\.Secret|.*\.secret|.*\.mac|.*\.MAC|.*\.seed|.*\.crumbSalt|.*\.consoleAnnotator|.*\.serverCookie|.*\-switch|whitelisted\-callables\.d|.*\.conf|filepath\-filters\.d|.*\.conf)$
You actually need to use the vertical bar to represent a folder or subfolder. I believe the fix for your regex in the screenshot would be changing (secrets/.*.key) to:
(secrets|.*\.key)
Any further subfolders have a similar syntax, such as getting *.groovy from jenkins/scriptler/scripts/:
(scriptler|scripts|.*\.groovy)
Maybe you've already figured this out, but if not, I hope this helps.
Bill
Basically I have a solution which is having 2 projects.
Main Website
Console Application which will be used to schedule Jobs.
My problem here is the both the projects are using a XML file which have lots of configuration. The developers are updating the file in the main project but not in the Console App.
So is there any way to include the XML file in the main project into the debug/release folders of the console application directly. So that, when they get the latest of console app, it can pickup the file from the referenced location that is in the main project. Hope I am making sense..!
-Ram
I suggest you to Specify the File Add Option, add config file in Main Project and to add another file but by linking on the first.
Every change on first is reflected on second file.
link : http://support.microsoft.com/kb/306234
You want to just have once copy of the XML file checked into TFS.
Then, add that one XML file to both website project and the console application projects. Set the properties of the XML file to Content - Always copy.
Something like this would work...
/root
/Website
website.csproj
/Console
console.csproj
/Config
MyConfigFile.xml
In both the website.csproj and the console.csproj you would have an entry like this...
<Content Include="..\Config\MyConfigFile.xml">
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Content>
I am using Editable Email plugin in Jenkins to attach a file with the email. The problem is that the plugin is unable to find the file to attach.
My file structure is like this -
ReportDirectory
workspace
ReportDirectory contains the report which I want to attach. I believe that the base directory for the plugin is the workspace. So I am giving the attachment location as
../ReportDirectory/DemoReport.html.
I have also tried
ReportDirectory/DemoReport.html
and many more options.
Am I doing something wrong?
I figured it out.
The Editable Email plugin uses the Ant File Syntax for locating the attachment. When I took at the documentation for Ant File Syntax ( http://ant.apache.org/manual/dirtasks.html ), it says that
In general, patterns are considered relative paths, relative to a task dependent base directory (the dir attribute in the case of ). Only files found below that base directory are considered. So while a pattern like ../foo.java is possible, it will not match anything when applied since the base directory's parent is never scanned for files.
Since the base directory in this case is the "workspace" and my directory "ReportDirectory" is not located in it so the Ant is not able to access it.
Two solutions exist:
Move the "Report Directory" somewhere in "workspace". I did not prefer this because I did not want to mess up the workspace.
Once the report has been created in "ReportDirectory", use your Ant\MSBuild script to copy it temporarily in the "workspace" and then the Email plugin shall be able to access it by something like **/Report.html or something.
#Amey - thanks for your efforts though :)
Another solution is create a symbolic link from $JENKINS_HOME/jobs/workspace/$workspace_name to the path with your $workspace_name. This way worked for me.
ReportDirectory/DemoReport.html
is the correct way to do it.
Please keep in mind that the path to the file and the file name is case sensitive so I assume your entering the correct name.
One more thing is to check is that the report is actually created and is located at the path mentioned by you.
Another thing you could try
ReportDirectory/*
Jenkins will use the directory available in its workspace.
You can send multiple attachments as below.
reportFolder/html/index.html, screenShotsFolder/screenShots/*.jpg
Simple answer:
Copy your file into the workspace(into your job directory), then under Attachment, just give the file name without any quotation or anything. This will automatically tell Jenkins to pick up your file. That's it!
Pls don't confuse yourself after seeing all the configurations.