Eclipse is setting constantly excluded filter in build path config to **, which causes resources to be excluded from deployment. Anyone aware of this issue, and how this can be prevented? Any thoughts?
How i said in the comments of your question i did not verify any of both approaches and i only think/hope they could lead to a solution rather than i know it exactly.
First approach:
Since you handle the entire process of compilation and packaging via Maven i assume you collect required ressources with Maven only (and that if you filter out certain ressources you would do that with Maven only). In that case i would try to disable all of the eclipse filters to be included into the build path - which i would expect as the behaviour if you disable this option:
(i once experienced eclipse added a "*"Filter to my Type Filters hence i wasnt able to find anything on typesearch Ctrl+Shift+T anymore - so my hope is a similar behaviour when it comes to your filter-all-resources filter"
Second approach
Actually i think that this approach will only affect the view rather than the build/ deployment process but hey its eclipse - you just never know so i guess its worth a try:
In the following screen you should see any filters known by eclipse - i assume you will see the . Filter there as well and be able to unselect it:
I guess its worth a try - good luck ;)
Related
Is there a good way to reset Eclipse build state completely?
I am stuck getting 'Building all...' on each build (manual, BTW), even though it seems to finish normally, and it has been working just fine for weeks, and I've had this issue before, but it would resolve itself on one or more rebuilds; all of which leads me to believe that there is something internal that gets stuck in a wrong state.
Clean Project does not seem to do it. And the full rebuild 'says' it does a clean anyway, 'cleaning output folder'.
Clean + Close Project + Restart Eclipse does not seem to do it either (which fact I find rather unsatisfying and weird).
I suppose a re-import could do it.
Perhaps re-import under a different name?
But maybe there's something easier than re-import. Perhaps deleting some file or folder in Eclipse persisted state?
(Maybe tag this 'internals'? I am asking for specific solutions, but I am certainly interested in the IDE internals too, whether that will help solve this issue or not.)
I wonder, using Eclipse's PyDev plugin, how come documentation does not always show up?
Compared with
Is there a way to set Eclipse to "always show modules available along with the help attached"?
The problem is that depending on each context, the PyDev type inference engine may know or not what you're talking about... In the first situation it knows you're dealing with a string and thus can show you things properly. In the second, word is probably some parameter, so, it can't really find swapcase properly -- although it should work if you did an assert isinstance(word, str).
This thread is very useful for finding out which files in Netbeans should go into source countrol, but it doesn't cover all files.
In particular I'm wondering whether the following files should go into source control. Here are my assumptions/guesses:
nb-configuration.xml - easiest - the file itself in the comment says it should go into source control.
nbactions.xml - from what I see this file stores information typical to running the application. I.e. JVM arguments etc. So I suppose it is a question of taste - if you want other developers to have a "suggested" Run configuration - include it. Otherwise - don't. Correct?
catalog.xml - not sure what this does (I GUESS it's used by the editor to find out xml schemas and such to enable syntax coloring, but it's just a guess). Anyway - I see that this file has system-specific information (path) - so it shouldn't go into source control.
Can anyone confirm the above?
Thanks,
Piotr
I never put my IDE configuration files in the repository, for several reasons:
other colleagues may want to use theirs;
other colleagues may want to use other IDEs (such as Eclipse) and seeing those files (or even have to exclude them from the checkout) could be annoying for them;
some of these files are generally not related to a single project, others automatically generated, so no need to store them in the source code of every project.
In order to exclude them, our first solution was the .svnignore, but it was still logically wrong to modify some shared content for the specific needs of a single user, so we decided to be more strict:
in my ~/.subversion/config I have:
[miscellany]
global-ignores = nbactions.xml nbproject
Hope this helps,
Marcello
In my Maven based projects I put nbactions.xml into source control. Just make sure to change absolute paths to relative ones.
I put nbactions.xml into source control BUT there is a caveat: it's internal format can change so if your developers, for any reason, use different versions of NetBeans you could have to remove it because sharing it becomes nasty.
Recently I upgraded from NetBeans 7.3.1 to 7.4 and the "Run" action was giving a strange error message. I solved the problem by deleting and regenerating nbactions.xml: the old one had a custom Maven goal for the "Run" and "Debug" actions; it was org.codehaus.mevenide:netbeans-deploy-plugin:1.2.4:deploy it was not visible in the IDE v7.3.1 (perhaps it has been generated by an even older version for internal usage) and was generating a class not found for org.openide.util.Lookup in v7.4. I'm documenting the problem here because I found the solution by myself after an unsuccessful search on the Net. I hope this can help someone else.
I'm running Test Cases with TestNG Eclipse plugin. How can I specify a distinct folder as output to the HTML reports by configurating testng.xml?
I've seen Cedric's answer to this very similar question (http://stackoverflow.com/questions/5401746/generating-testng-reports/), but I couldn't obtain the same on TestNG Eclipse plugin. I've tried , and another bunch of similar things I've seen in the doc and nothing worked.
Extending the question a bit, we want to be able to run tests repeatedly and pick at any time the last n (say 20) reports, is it possible? It happens sometimes we use TestNG to do a lot of exploratory test. As some fails are rare and hard to repeat (and in the first approach they may not be predicted as such), sometimes the "explorer" just re-run the test and lose that inconstant fail.
Thanks in advance to any answer to the primary or a bit extended question, Regards, Henrique
try by passing argument -doutputdir in arguments tab
I am working on a project using Eclipse 3.4.2, and would like to know how many Non Comment Lines of Code (NCLOC) it has.
It is OK to be a simple plugin, but I don't wan too much bloat. My machine is already slow the way it is.
Use Eclipse regular Expression: Search->File, check Regular expression.
LOC: \n[\s]* (without blanks)
Comments: [*]+
you can subtract to get NCLOC with selected resource
You could try a metric plugin (like the ones I mention in this SO question)
That, plus a good eclipse.ini (making your eclipse run with the latest JDK), should make your configuration able to display what you want in a timely fashion.