貔貅的神奇功效
by jade
您好！
本公司供應大件玉器。
大圖展示：
http://photo.163.com/cnpixiu
http://www.flickr.com/photos/91622624@N08
無與倫比的官方商界禮品饋贈！精美漂亮的极具收藏價值。歡迎鑒賞交流！
電話：132-8719-6898
郵箱：（請見圖片標註）
吉慶堂簡介：
吉慶堂禮品公司的經營目標是：做有增值空間高、 有訢賞價值、有紀唸意義、有收藏價值的高档次、高品味的禮品！公司主要經營各類商務禮品、辦公禮品 、開业慶典禮品、傢紡禮品、工藝品、收藏品、促銷品、紀唸品、嘉獎品等。高、中档禮品應有儘有，可 滿足客戶不同層次的批髮和零售，形成“一站式”服務。經營範圍是以遼寧岫玉、和田玉、緬甸樹化玉、 緬甸翡翠、綵玉石、檯灣七綵玉、水晶、黃蠟玉石、雞血玉石、黃金玉石、緬甸東玉石等各種名貴玉石產 品為主打；工藝禮品專做精品。所經營玉石產品均具有國傢質量監督侷的權威鑒定，以確保玉石的真實性 。吉慶堂禮品公司已成為华东最大的玉石批髮基地。最具髮展潛力的高档禮品營銷機搆之一。
吉慶堂開運招財貔貅”在招(正財，偏財)，轉運開 運，闢邪防小人，改善風水運程等方麵效果顯著。
貔貅的由來(自古以來公認的第壹招財瑞獸)：
傳說貔貅是龍生九子的第九子,有嘴無屁股，吞萬物而不瀉。可招八方財，可聚寶，隻進不齣，神通特異 。所以貔貅是能納食四方之財，肚子是個聚財囊，同時催官運。
由於貔貅能招財聚寶的才能。所以各 朝代的皇帝將貔貅定為御用的物品，如果髮現有人私藏貔貅將會被認為有劫財竊寶之意，論罪當斬。但仍 有壹些王朝的官宦地方富豪為了自己能夠達到終身荣華富貴，便經常有私藏貔貅的現象髮生，特別是到了 清朝乾隆年間，和坤在自己傢中私藏御製貔貅使得自己達到無比的富用。貔貅在民間廣汎流傳，直到現在 。
貔貅有八大功效：鎮宅、闢邪、化煞、轉運、求財、求子、添壽、定姻緣。貔貅在風水上用來驅邪 、擋煞、防小人、鎮宅其威力是無庸置疑的。相傳貔貅喜愛金銀財寶的味道，常咬迴金銀財寶來討主人的 歡心，故有言此迺招財之物。因而貔貅另有旺財的功用。
貔貅的神奇功效：
1.做生意的人！貔貅生 性凶猛，因為沒有肛門，隻進不齣的傳說讓它的招財能力更加令人堅信不移。當我們做生意若有生意機會 ，可請求貔貅帮忙咬住任何的生意機會，並促成買賣交易順利，生產平安，收款順複明（要叮嚀好生意來 ，壞生意不要成)。
2.喜歡賭博的人！全世界赫赫有名的四大賭場：美國拉斯維加斯，韓國華剋山莊 ，馬來西亞雲頂；澳門葡京，都有貔貅的身姿。
3.想讓傢運轉好，好運加強，趕走邪氣，鎮宅闢邪的 人。
4.偏行，收入浮動者，例如銷售、經商、外匯、股票、金融、綵馬、期貨、賭場等。開光貔貅有 趨財旺財的作用，尤對偏行、收入浮動者有奇效。
5.公司企业主琯及老闆珮戴貔貅，能得權勢人望， 辦事有貴人相助也可凝聚各部門人員嚮心力，團隊更有組織，並帶來穩定及和諧，公司生意應接不暇。
6.學生珮戴貔貅可使讀書穩如泰山，做事十拿九穩，學业事业髮展順利，運勢亨通，得老師及長官厚 愛。
李嘉誠與貔貅：
李嘉誠壹共擁有888隻貔貅，這就是久富不衰 的奧祕！古賢認為，命是註定的，但運程可以改變，故民間有"壹摸貔貅運程旺盛，再摸貔貅財運滾滾， 三摸貔貅平步青雲"，以及"壹命二運三風水,四積功德五讀書,六名七相八敬神,九交貴人十養生"的說法。
如果您喜歡，請與我們聯係！請髮郵件（相冊或附件圖片標明郵件地阯所示）
12 years
FYI: Moving eclipse.org to a new data centre
by Nick Boldt
Planned eclipse.org outage coming next month. Mark your calendars!
-------- Original Message --------
From the Webmaster:
On Saturday, February 9 2013 the Eclipse Foundation will be moving
its servers to a new data centre. This modern facility will provide
improved server cooling, substantial increases to our bandwidth,
available AC power and cabinet (rack) space while reducing our
hosting costs. During the move, all eclipse.org services will be
offline, including Bugzilla, Wiki, Git, Gerrit and our website,
www.eclipse.org <http://www.eclipse.org>. Our plans are to begin the
move on Saturday morning (Eastern time), February 9 2013 and have
all services restored by Sunday afternoon, February 10 2013.
We'd like to apologize in advance for the inconveniences that this
move will cause. However, the benefits are compelling and will
provide the Eclipse Foundation with the infrastructure needed to
continue its growth for many years to come.
12 years
Fwd: Best way to handle 2 code streams
by Fred Bricon
Any input is welcome.
---------- Forwarded message ----------
From: Fred Bricon <fbricon(a)gmail.com>
Date: Thu, Jan 10, 2013 at 4:29 PM
Subject: Best way to handle 2 code streams
To: M2E-WTP Developers mailing list <m2e-wtp-dev(a)eclipse.org>
Hi,
first of all, let me wish you all a very Happy New Year. I hope it'll see
m2e-wtp graduate from the eclipse incubator next June ;-)
During last call, we decided m2e-wtp would provide a JPA configurator for
both the Kepler and pre-Kepler streams, due to Dali moving its provisional
API, meaning we now need to maintain two branches of code. So I've been
trying to think at the best strategy that would lead to the minimum
maintenance overhead while allowing to provide new cool features for
everybody.
1/ have 2 different JPA features in 1 git repo :
Somethink like org.eclipse.m2e.wtp.jpa.feature (for kepler and onward)
and org.eclipse.m2e.wtp.jpa.e42.feature (pre-kepler). Both features would
be built and appear in the same update site (version 0.17.0). This gives us
all the code easily accessible for maintenance (from my point of view) as
we wouldn't have to switch between branches in order to apply fixes in both
JPA configurators.
The biggest problem though, is we wouldn't be able to provide a way to
upgrade from jpa.e42 to jpa. There's already a p2.inf hack allowing the
upgrade from the jboss tools jpa feature to the eclipse one, that hack
prevents us from adding the jpa (juno) to jpa (kepler) upgrade path (Tycho
breaks seeing the same IU being built twice).
2/ Have 2 m2e-wtp versions in 2 branches of a git repo
We'd provide 2 separate update sites:
* a "pre-kepler" p2 repo with m2e-wtp 0.17.0, built from a git 0.17.0 branch
* a kepler repo with m2e-wtp 0.18.0/1.0, built from master.
This would be easier to build, from a tycho perspective, and we'd still be
able to upgrade from juno to kepler AND from jboss tools. But it would
bring a *huge* overhead in non-JPA maintenance.
3/ Have JPA in a dedicated git repo, use specific qualifiers :
We'd provide 2 separate update sites:
* a "pre-kepler" aggregated p2 repo with m2e-wtp 0.17.0, built from master
and a jpa.0.17.0-e42.timestamp site, built from the e42 branch of the
m2e-wtp-jpa git repo,
* a kepler aggegated p2 repo with m2e-wtp 0.17.0, built from master and a
jpa.0.17.0-e43.timestamp site, built from the master branch of the
m2e-wtp-jpa git repo,
It requires 2 tycho builds and more manual hacking of the aggregated sites,
but would be easier to maintain, from a code perspective. And we'd still be
able to upgrade from 0.17.0-e42 to 0.17.0-e43.
I think I like #3 better (but I haven't tested the approach works yet).
What do you think?
Fred Bricon
--
"Have you tried turning it off and on again" - The IT Crowd
--
"Have you tried turning it off and on again" - The IT Crowd
12 years
Fwd: Incremented versions in server/jbosstools-4.0.x branch broke the build
by Max Rydahl Andersen
moved to jbosstools-dev
>
> Rob,
>
> it looks like build for server component out of jbosstools-4.0.x branch is broken after last commit https://github.com/jbosstools/jbosstools-server/commit/48165fee6b5dffe1e8....
> For several plugins version was updated 2.4.0-SNAPSHOT to 2.4.1-SNAPSHOT, but it should be updated in all poms/manifests to fix build error.
>
> eskimo@eskimo-notebook:~/Projects/jbds/test$ mvn clean install -Dmaven.repo.local=.m2/jbosstools-4.0.x -DskipTests
> [INFO] Scanning for projects...
> [ERROR] The build could not read 6 projects -> [Help 1]
> [ERROR]
> [ERROR] The project org.jboss.tools.as.plugins:org.jboss.ide.eclipse.as.core:2.4.1-SNAPSHOT (/home/eskimo/Projects/jbds/test/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact org.jboss.tools.as:plugins:pom:2.4.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2]
> [ERROR]
> [ERROR] The project org.jboss.tools.as.features:org.jboss.ide.eclipse.as.serverAdapter.wtp.feature:2.4.1-SNAPSHOT (/home/eskimo/Projects/jbds/test/jbosstools-server/as/features/org.jboss.ide.eclipse.as.serverAdapter.wtp.feature/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact org.jboss.tools.as:features:pom:2.4.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2]
> [ERROR]
> [ERROR] The project org.jboss.tools.as.features:org.jboss.ide.eclipse.as.archives.integration.feature:2.4.1-SNAPSHOT (/home/eskimo/Projects/jbds/test/jbosstools-server/as/features/org.jboss.ide.eclipse.as.archives.integration.feature/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact org.jboss.tools.as:features:pom:2.4.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2]
> [ERROR]
> [ERROR] The project org.jboss.tools.as.features:org.jboss.ide.eclipse.as.jmx.integration.feature:2.4.1-SNAPSHOT (/home/eskimo/Projects/jbds/test/jbosstools-server/as/features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact org.jboss.tools.as:features:pom:2.4.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2]
> [ERROR]
> [ERROR] The project org.jboss.tools.as.features:org.jboss.ide.eclipse.as.server.rse.integration.feature:2.4.1-SNAPSHOT (/home/eskimo/Projects/jbds/test/jbosstools-server/as/features/org.jboss.ide.eclipse.as.server.rse.integration.feature/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact org.jboss.tools.as:features:pom:2.4.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2]
> [ERROR]
> [ERROR] The project org.jboss.tools.as.features:org.jboss.ide.eclipse.as.feature:2.4.1-SNAPSHOT (/home/eskimo/Projects/jbds/test/jbosstools-server/as/features/org.jboss.ide.eclipse.as.feature/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact org.jboss.tools.as:features:pom:2.4.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> Denis
>
12 years
Join our Field Network!
by Field Network.
Join our Field Network!
As profiled on Good Morning America, Secret shopper and merchandising provide a flexible way for extra Job. A nation wide leader in mystery shopping and merchandising among top brands, Market Of information Force continues to look for people like you to be our prominent eyes and ears in the shops, restaurants and banks.
Secret shopper, also known as secret shopping, and merchandising are fun and you can make a huge difference for future customers.
As a Participant you work and shop together for pleasure and you will get $200 on each assignment and its on Part time basis, So you only work 2-3hours twice in a week. If you are interested kindly send me your details info.
Name :
Address :
Phone Home & Cell :
City, State, Zip :
We await your urgent response and look forward to working with you!
Regards,
Agent Recruitment
Head of Recruitments
12 years
Beware of egit
by Fred Bricon
Hi, I never use egit usually, as I always had bad surprises in the past,
I mostly prefer CLI.
Today I decided to give it a new chance so I committed and pushed a few
files using the awesome git staging view.
And then I opened
https://github.com/jbosstools/jbosstools-central/commit/aa0efbc9d811fb467...
All lines are shown as changed (line endings crap I assume). How
awesome...not is that?
I'm on windows with core.autocrlf=true, in egit, 'ignore whitespace
changes' is UNCHECKED, so I have no idea of what happened.
So, if you haven't used egit (on windows) yet, well, be careful then.
Angry Fred
12 years
