On 10/08/2011 5:31 PM, ccc wrote:
I am behind a proxy, but I doubt that's causing the issue.
It hasn't caused any issue with other artifacts, but ... I can't be 100%
sure.
I ran Maven from Eclipse, but I'll run it from the console and try your
suggestions.
I will report back with whatever results I get :)
I am not the admin of our servers, but maybe I'll talk the guy into putting
up a nexus of our own.
Trying to use Maven without your own repo is a good way to lose a ton of
time.
We ran for about 2 years without a repo and once we put it in, we
realized how much grief we went through for nothing.
It is easy to put in and once you get it configured and your
settings.xml set up, Maven becomes so much easier and so much more
transparent.
It is well worth the effort to get your server admin to set up a Nexus
or some other repo.
We are using the free version and it saves us a lot of time.
- Once you set up your repo proxies, individual developers don't have to
worry about finding things.
- Once you upload the third party libraries that have licenses that
prevent them from being in a public repo, everyone has access to it
without having to think about downloading it.
- A repo forces you to think about releases and SNAPSHOTs in a rational
way so that your software development is organized.
- Just knowing that a release is immutable (except by asking the Nexus
administrator to remove it) means that people take releasing a library
or utility seriously.
- Being able to deploy SNAPSHOTS that others can use means that
SNAPSHOTS start to get little guarantees about their level of
functionality and degree of testing that makes collaborative development
more productive.
Just wish we had done it earlier.
On Wed, Aug 10, 2011 at 10:09 PM, Wayne Fay [via Maven]<
[email protected]> wrote:
I had already tried putting the JBOss repo in my settings.xml, I even
tried
using a mirror of it provided by some other company. Nothing worked.
That's why this issue has been so frustrating.
So any ideas or suggestions about how to fix the issue or work around it
would be greatly appreciated.
mvn -X compile may provide additional useful debugging information. Or
it may not, some people have trouble grokking all the info it spews.
Are you behind an Internet proxy?
Are you connecting to a local Nexus or other MRM instance? [If not,
you should consider installing something...]
What does the updatePolicy for this repository look like in
settings.xml or Nexus config?
etc
You should also try mvn -U to force an update of any jars/poms that
are involved in this build. Perhaps the pom file will be downloadable
when you try again. If not, there isn't a whole lot we'll be able to
do to help you. You could also just download the pom file and copy it
to the proper place in your local repo cache just to get past this
issue.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden
email]<http://user/SendEmail.jtp?type=node&node=4687106&i=0>
For additional commands, e-mail: [hidden
email]<http://user/SendEmail.jtp?type=node&node=4687106&i=1>
------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://maven.40175.n5.nabble.com/Problem-adding-hibernate-jbosscache2-to-my-project-tp4685996p4687106.html
To unsubscribe from Problem adding hibernate-jbosscache2 to my project, click
here<http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4685996&code=Y2FsaW5jb3NtYUBnbWFpbC5jb218NDY4NTk5NnwtODMyNDk5MTY1>.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
