Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #23723 > unrolled thread

Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser)

Started bygalois271@gmail.com
First post2013-04-29 20:25 -0700
Last post2013-04-30 09:18 -0400
Articles 4 on this page of 24 — 7 participants

Back to article view | Back to comp.lang.java.programmer


Contents

  Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) galois271@gmail.com - 2013-04-29 20:25 -0700
    Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) lipska the kat <"nospam at neversurrender dot co dot uk"> - 2013-04-30 09:00 +0100
      Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) galois271@gmail.com - 2013-04-30 05:47 -0700
        Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) lipska the kat <"nospam at neversurrender dot co dot uk"> - 2013-04-30 14:27 +0100
          Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) galois271@gmail.com - 2013-04-30 07:07 -0700
            Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Lew <lewbloch@gmail.com> - 2013-04-30 12:30 -0700
              Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) lipska the kat <"nospam at neversurrender dot co dot uk"> - 2013-04-30 20:53 +0100
                Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Chuck Johnson <galois271@gmail.com> - 2013-04-30 13:05 -0700
                Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Arne Vajhøj <arne@vajhoej.dk> - 2013-04-30 21:26 -0400
                  Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) lipska the kat <"nospam at neversurrender dot co dot uk"> - 2013-05-01 06:55 +0100
                    Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Jeff Higgins <jeff@invalid.invalid> - 2013-05-01 03:22 -0400
                      Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Joerg Meier <joergmmeier@arcor.de> - 2013-05-01 13:10 +0200
                        Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) lipska the kat <"nospam at neversurrender dot co dot uk"> - 2013-05-02 16:44 +0100
                      Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Arne Vajhøj <arne@vajhoej.dk> - 2013-05-01 20:27 -0400
                        Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Jeff Higgins <jeff@invalid.invalid> - 2013-05-02 11:33 -0400
                    Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Arne Vajhøj <arne@vajhoej.dk> - 2013-05-01 20:23 -0400
                      Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Lew <lewbloch@gmail.com> - 2013-05-01 18:38 -0700
                        Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) lipska the kat <"nospam at neversurrender dot co dot uk"> - 2013-05-02 16:35 +0100
                          Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Lew <lewbloch@gmail.com> - 2013-05-02 12:29 -0700
                            Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Arne Vajhøj <arne@vajhoej.dk> - 2013-05-02 19:46 -0400
                              Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Lew <lewbloch@gmail.com> - 2013-05-02 18:22 -0700
                                Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Arne Vajhøj <arne@vajhoej.dk> - 2013-05-02 21:54 -0400
                            Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) lipska the kat <"nospam at neversurrender dot co dot uk"> - 2013-05-03 13:34 +0100
    Re: Including JAR files in Eclipse 4.2, specifically Rome (RSS Feed parser) Jeff Higgins <jeff@invalid.invalid> - 2013-04-30 09:18 -0400

Page 2 of 2 — ← Prev page 1 [2]


#23805

FromLew <lewbloch@gmail.com>
Date2013-05-02 18:22 -0700
Message-ID<f5bd28db-197f-41bf-aea8-4d811754e27b@googlegroups.com>
In reply to#23801
Arne Vajhøj wrote:
> Lew wrote:
>> lipska the kat wrote:
>>> Lew wrote:
>>>> You are guilty of straw-man argumentation, lipska.
> 
>>> It's spelled straw man, no hyphen
> 
>> Incorrect. The hyphen is needed when a unit modifier (like "straw man" in this case)
>> precedes the noun modified.
> 
> Many use it without hyphen:
> 
> http://en.wikipedia.org/wiki/Straw_man
> http://www.thefreedictionary.com/straw+man
> http://www.merriam-webster.com/dictionary/straw%20man
> http://oxforddictionaries.com/us/definition/american_english/straw%2Bman?q=straw+man

None of those address the issue of unit modifiers that precede the noun modified.

You missed my point entirely.

Any compound phrase, like "straw man" or "fully realized", is spelled without a hyphen when 
it is in a standalone position in a sentence, that is, not used as an adjective preceding the noun.

When used as a unit modifier prior to a noun, it's hyphenated.

"The fallacy there is straw man."
"It is a straw-man argument."

"The project will be profitable once it is fully realized."
"Somehow the fully-realized project never made a profit."

So while it is true that "straw man" is spelled without a hyphen when the hyphen is 
not required, that has no bearing on the misspelling that I called out.

I promise I will not try to correct you on fine points of non-English grammar.

-- 
Lew

[toc] | [prev] | [next] | [standalone]


#23810

FromArne Vajhøj <arne@vajhoej.dk>
Date2013-05-02 21:54 -0400
Message-ID<518318d0$0$32118$14726298@news.sunsite.dk>
In reply to#23805
On 5/2/2013 9:22 PM, Lew wrote:
> Arne Vajhøj wrote:
>> Lew wrote:
>>> lipska the kat wrote:
>>>> Lew wrote:
>>>>> You are guilty of straw-man argumentation, lipska.
>>
>>>> It's spelled straw man, no hyphen
>>
>>> Incorrect. The hyphen is needed when a unit modifier (like "straw man" in this case)
>>> precedes the noun modified.
>>
>> Many use it without hyphen:
>>
>> http://en.wikipedia.org/wiki/Straw_man
>> http://www.thefreedictionary.com/straw+man
>> http://www.merriam-webster.com/dictionary/straw%20man
>> http://oxforddictionaries.com/us/definition/american_english/straw%2Bman?q=straw+man
>
> None of those address the issue of unit modifiers that precede the noun modified.
>
> You missed my point entirely.
>
> Any compound phrase, like "straw man" or "fully realized", is spelled without a hyphen when
> it is in a standalone position in a sentence, that is, not used as an adjective preceding the noun.
>
> When used as a unit modifier prior to a noun, it's hyphenated.
>
> "The fallacy there is straw man."
> "It is a straw-man argument."
>
> "The project will be profitable once it is fully realized."
> "Somehow the fully-realized project never made a profit."
>
> So while it is true that "straw man" is spelled without a hyphen when the hyphen is
> not required, that has no bearing on the misspelling that I called out.

Did you read the links?

Two of them provide examples without hyphen in front of argument/arguments.

Now - I am not an expert in the English Language, but some
googling seems to indicate that the rules is not as hard as you
indicate.

Example:

http://www.gpo.gov/fdsys/pkg/GPO-STYLEMANUAL-2008/html/GPO-STYLEMANUAL-2008-8.htm

<quote>
Unit modifiers
6.15. 	Print a hyphen between words, or abbreviations and words,
         combined to form a unit modifier immediately preceding the word
         modified, except as indicated in rule 6.16 and elsewhere
         throughout this chapter. This applies particularly to
         combinations in which one element is a present or past
         participle.

           agreed-upon standards         Federal-State-local cooperation
           Baltimore-Washington road     German-English descent
           collective-bargaining talks   guided-missile program
           contested-election case       hearing-impaired class
           contract-bar rule             high-speed line
           cost-of-living increase       large-scale project
           drought-stricken area         law-abiding citizen
           English-speaking nation       long-term loan
           fire-tested material          line-item veto
           long-term-payment loan        U.S.-owned property; U.S.-
                                           flagship
           low-cost housing              1-inch diameter; 2-inch-
                                           diameter pipe
           lump-sum payment              a 4-percent increase, the
                                           10-percent rise
           most-favored-nation clause    but
           multiple-purpose uses         4 percent citric acid
           no-par-value stock            4 percent interest. (Note the
                                             absence of an article: a,
                                             an, or the. The word of is
                                             understood here.)
           one-on-one situation
           part-time personnel
           rust-resistant covering
           service-connected disability
           state-of-the-art technology
           supply-side economics
           tool-and-die maker
           up-or-down vote

6.16. 	Where meaning is clear and readability is not aided, it is not
         necessary to use a hyphen to form a temporary or made compound.
         Restraint should be exercised in forming unnecessary
         combinations of words used in normal sequence.

           atomic energy power           national defense
                                           appropriation
           bituminous coal industry      natural gas company
           child welfare plan            per capita expenditure
           civil rights case             Portland cement plant
           civil service examination     production credit loan
           durable goods industry        public at large
           flood control study           public utility plant
           free enterprise system        real estate tax
           ground water levels           small businessman
           high school student           Social Security pension
           elementary school grade       soil conservation measures
           income tax form               special delivery mail
           interstate commerce law       parcel post delivery
           land bank loan                speech correction class
           land use program              but no-hyphen rule (readabi-
                                           lity aided); not no hyphen
                                           rule
           life insurance company
           mutual security funds

</quote>

Arne



[toc] | [prev] | [next] | [standalone]


#23814

Fromlipska the kat <"nospam at neversurrender dot co dot uk">
Date2013-05-03 13:34 +0100
Message-ID<z8-dnRBgkvBAMx7MnZ2dnUVZ7rudnZ2d@bt.com>
In reply to#23794
On 02/05/13 20:29, Lew wrote:
> lipska the kat wrote:
>> Lew wrote:
>>> You are guilty of straw-man argumentation, lipska.
>>
>> It's spelled straw man, no hyphen
>
> Incorrect. The hyphen is needed when a unit modifier (like "straw man" in this case)
> precedes the noun modified.
>
>> How useful do you think it is to tell someone struggling to get Eclipse
>> to do what he wants that he shouldn't be using it (for whatever reason)
>
> What does that have to do with this conversation
>
> No one told the OP that he shouldn't use Eclipse, only that it should not be used
> for production builds. That is incredibly useful.
>
> And not because I think it's useful but because it has demonstrable benefits, as mentioned
> upthread.
>
> Bad habits are harder to unlearn than if you learn good habits to begin with.
>
> Someone who only learns the micro-information needed for today's question without
> a sense of where the road leads will learn more slowly.

> To be effective at computer
> programming in particular, one must develop the habit of assimilating, even if superficially,
> the nine-tenths of the knowledge iceberg that is submerged below the waterline of
> "I think this is immediately useful". If you cannot cope with that kind of data, you will never
> grow to be a very competent programmer.
>
> Now, I realize lipska that your argumentation is motivated entirely by the desire to disagree
> with me personally, and not to help the OP, which is why you resort to begging the question
> (calling it "misinformation") and challenging the usefulness of a useful answer without actually
> contributing any helpful information yourself.
>
> But the fact remains that Eclipse is not optimal as a production build tool, and that there are
> standard tools for Java projects that are superior and indeed, intended for the purpose. This is
> always useful to know, even if you aren't prepared at this very instant in time to delve in depth
> into the matter. Otherwise you might form the bad habit of relying on Eclipse for something for
> which it is not well suited, and suffer the dire consequences thereof, while having to undo an
> ineffective system and unlearn bad habits. Is that what you want for the OP?
>
> So better to set up a signpost very early in the learning path, indicating that there are dangers
> and liberating the OP to dig into that in depth now that they know there is something to research.
>
> You would shackle them with your own arrogant prejudgment of what you in your narrow,
> self-aggrandizing view of things deem is all they need, just to snark at someone whom for
> some reason you have chosen to deprecate.

Well that's all very interesting I'm sure.

I won't bore you with the details of my career too date but I will tell 
you that I have significant experience in training people to use Java 
(amongst other languages) and many, many hours spent standing in front 
of a class of students and fielding their questions has taught me this. 
When someone asks a question, what they are usually looking for is an 
answer to that question, anything else is too much information.
Compare our answers to this and other threads to see what I mean

They generally do not want a treatise on one persons view of Object 
Oriented Software Engineering or a long detailed description of why they 
are wrong to do something in some way or other. If you were as 
experienced a developer as you say you are you would know that software 
engineering is not a well defined science in the same way that 
mechanical engineering or physics or architecture are for example.

There are many ways of doing things that are 'right' because they work 
for a given situation. I have worked on projects where the chosen 'IDE' 
is Emacs and the chosen build tool is Make. Ant, batch files, shell 
scripts, cron jobs and hand rolling are all valid methods in certain 
situations. An IDE is just a tool. In any reasonably sized project there 
will be a build master who is responsible for the nightly, test, staging 
and production builds, what does it matter what tool he uses to do the 
job. If problems are encountered using Eclipse, or any other development 
tool for that matter then I suggest that in general, it is a problem 
with the user and not the tool.

> Better to know the truth than base your education on falsehood. The truth will set you free.

You said it.

lipska

-- 
Lipska the Kat©: Troll hunter, sandbox destroyer
and farscape dreamer of Aeryn Sun

[toc] | [prev] | [next] | [standalone]


#23726

FromJeff Higgins <jeff@invalid.invalid>
Date2013-04-30 09:18 -0400
Message-ID<klog4h$mt9$1@dont-email.me>
In reply to#23723
On 04/29/2013 11:25 PM, galois271@gmail.com wrote:
>
> "The type org.jdom.Document cannot be resolved. It is indirectly referenced from required .class files"
>
I've pasted you’re error message verbatim into my browser search box.
There seems to be about four common problems.
Jdom version, Jdom distribution packaging, seem to be the most common.

[toc] | [prev] | [standalone]


Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.java.programmer


csiph-web