Hello!
I think there's a minor doc flaw in the pom introduction page:
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Example_2
The relativePath attribute in the second example should begin with ../
(not with .../):
project
parent
Hi,
I need use the customized aol properties during build. I can’t modify the
aol properties in default location since the same maven is used for building
different projects.
Could you please help me in using aol properties from different location
during build.
Regards,
Kalai
--
View this
Please create a ticket for this [1]. The users list is not a good way of
reporting bugs.
/Anders
[1] http://jira.codehaus.org/browse/MNGSITE
On Wed, Aug 10, 2011 at 09:13, Dmitry Voronov d...@retn.net wrote:
Hello!
I think there's a minor doc flaw in the pom introduction page:
I have a multimodule project and when I do a clean install from root
directory, the artifact jars are created in the target directory of the
submodule, but not getting copied to localrepository. The issue is there
even if I skip the test cases using -DskipTests=true option.
But the same
I very much doubt this.
When build, check the console output for the install plugin. It will say
where it is installing the artifacts. I've never heard of a case where this
would not work (unless you get some very clear error in the console).
/Anders
On Wed, Aug 10, 2011 at 09:46, manukm07
There is only one way I could see of this happening...
If some ***idiot*** has decided that the parent project being
installed in the local repo is a bad plan and configured the install
plugin in the parent to skip... which then gets picked up by all the
children... never mind that you then
On 08/10/2011 06:13 AM, Dan Tran wrote:
Hi,
The Mojo team is pleased to announce the release of the DBUpgrade
Maven Plugin version 1.0-beta-1
Site : http://mojo.codehaus.org/dbupgade-maven-plugin/
404 but this works:
http://mojo.codehaus.org/dbupgrade/dbupgrade-maven-plugin/
hth,
Manos
Hi,
When i run release:prepare on the maven-release-plugin then it prompt for
the release verion, tag version.
Is there is any way or configuration, that i can do in the pom.xml, so that
the release plugin don't prompt for the release version and run by taking
the default values.
Any help
Hello all,
I have a first project with just /src/main/resources/mywsdl.wsdl in
the project
I have following lines in this first project pom.xml:
groupIdcom.myworld/groupId
artifactIdshared-wsdl/artifactId
nameshared-wsdl/name
version0-SNAPSHOT/version
build
plugins
plugin
Hello,
Use batch mode. try with adding -B in the command line.
The plugin will use default value (removing -SNAPSHOT from your
current version).
2011/8/10 anamika gupta anam...@hcl.com:
Hi,
When i run release:prepare on the maven-release-plugin then it prompt for
the release verion, tag
Hi,
I am not running the maven command from command prompt. We have hudson and
Maven integration. So, Hudson triggers the maven to make the build. I need
an option in the pom.xml, so that release plugin run with the default
values.
Can you please suggest me any configuration for this plugin,
Hi Conny,
what about this idea:
1. Create a properties file 'something.properties' in Your parent POM
module directory and set the 'skip' property for the enforcer plugin in
there:
enforcer.skip=true
2. Configure the Properties Plugin in the build section of Your parent POM:
plugin
I ended up writing a custom wsdl packaging type (along with a plugin to
handle it) for a similar customer use case. If there's interest I could most
likely convince the customer to donate it to some open source org.
/Anders
On Wed, Aug 10, 2011 at 11:23, Adrien Ruffie - Petals Link
Hi,
Usually we call a plugin(ex:maven project with a mojo) using command
mvn groupid:artifactid:version:goal which is in local
repository.
What is the command which specifies it to look in my nexus repository?
Thank you in advance
-Goutham
--
View this message in context:
Short answer: it's the same command
somewhat longer answer: Maven will first look in your local repo. If not
found there, it will look in the configured remote repos (and download to
your local repo if found).
Maybe reading some of the first chapters in some Maven book will give you a
better
Cool - I did not notice that in the preferences - thanks!
Cheers, Eric
On 2011-08-09 7:31 AM, Jeff Jensen wrote:
Using m2eclipse and turning on its feature to automatically download
dependency source and JavaDoc, it will automatically configure what
you seek... :-)
On Tue, Aug 9, 2011 at
I want it to restrict to the remote repo only. It should not look into local
repo , at least first it have to look in remote and then go for local
On Wed, Aug 10, 2011 at 6:02 PM, Anders Hammar [via Maven]
ml-node+4685646-210393254-220...@n5.nabble.com wrote:
Short answer: it's the same
If I try to add a dependency to
org.hibernate:hibernate-jbosscache2:jar:3.3.2.GA:compile to my project, I
get:
/10/08/11 16:09:46 CEST: Maven Builder: INCREMENTAL_BUILD
10/08/11 16:09:47 CEST: Maven Builder: INCREMENTAL_BUILD requireFullBuild
10/08/11 16:09:47 CEST: [WARN]
10/08/11 16:09:47
thank you for the correction
-D
On Wed, Aug 10, 2011 at 2:01 AM, Manos Batsis
manos_li...@geekologue.com wrote:
On 08/10/2011 06:13 AM, Dan Tran wrote:
Hi,
The Mojo team is pleased to announce the release of the DBUpgrade
Maven Plugin version 1.0-beta-1
Site :
It says that you are calling up 2 versions not that any of them are missing.
duplicate declaration of version
3.5.4-Final
http://repo1.maven.org/maven2/org/jboss/cache/jbosscache-core/3.1.0.GA/jbosscache-core-3.1.0.GA.jar
It looks like you need to clean up your dependency tree to exclude older
My mistake - I copied too much from the console and included some older
messages from when I was trying different solutions for my problem.
I have now removed ALL dependencies from my pom. I get no errors.
But as soon as I add just this dependency (nothing else):
dependency
Someone else has a dependency on
org.jboss.cache:jbosscache-core:jar:3.1.0.GA
You need to look at your dependency tree and exclude this from the
package that is trying to add it in.
Ron
On 10/08/2011 11:08 AM, ccc wrote:
My mistake - I copied too much from the console and included some
There is absolutely nothing else.
I am just trying to add ONE dependency: hibernate-jbosscache2
I can not control its dependencies, and I have NOTHING else in my pom.xml
As I said, the previous error you pointed out was from another test.
Now, with an empty pom with just one dependency, it just
If you look at the dependency tree, where is the reference to
jbosscache-core-3.1.0.
You appear to be adding just 3.3.2.GA, so 3.1.0.GA has to be coming from
somewhere else. Parent POM?
See where it is in the dependency tree.
Maven is not making this up.
Ron
GA On 10/08/2011 11:24 AM, ccc
I am adding:
*hibernate-**jbosscache2*:jar:3.3.2.GA
which has a dependency on
*jbosscache-core*-3.1.0.GA
They are 2 different things, not 2 versions of the same thing.
It seems to me the problem is that Maven can't find the jbosscache-core
project.
In order to solve this I tried a bunch of
I want it to restrict to the remote repo only. It should not look into local
repo , at least first it have to look in remote and then go for local
Maven always tries to use the local repo first when resolving things.
So if you want to use version 1.2.3 of a plugin, and it is available
locally,
I need use the customized aol properties during build. I can’t modify the
aol properties in default location since the same maven is used for building
different projects.
What are aol properties?
Wayne
-
To unsubscribe,
Googling jbosscache-core maven turned up this lnk as the number 1 hit.
http://www.mvnbrowser.com/artifact-details.html?groupId=org.jboss.cacheartifactId=jbosscache-core
Does that help?
On 10/08/2011 11:39 AM, ccc wrote:
I am adding:
*hibernate-**jbosscache2*:jar:3.3.2.GA
which has a
Actually, the repository they tell you to add in that link
repository
idJBOSS/id
nameJBoss Repository/name
urlhttp://repository.jboss.org/maven2//url
/repository
is the old JBoss repo. I have added the new one (see my initial message),
but even with that one, it doesn't work.
Could you
I'm trying to use the release plugin with git. The git scm plugin seems to
get hung up when applying the tag.
If you look at the Working directory messages below, when it tries to
apply the tag it goes up 1 directory such that the command executes outside
of my git repository.
Is there
I don't have a lot of time to test things and I don't actually do any
development work without my staff's permission.
They let me set policy, set priorities and do high level design but find
my coding contributions incomplete and almost always untested.
They will admit, if pressed, that my code
Looks like Sonatype's repository has it:
https://oss.sonatype.org/index.html#nexus-search;quick~hibernate-jbosscache2
Best,
Laird
More info from an actual resolution:
[INFO] maven-dependency-plugin:2.2:go-offline (default-cli) @ my-project
Downloading:
http://download.java.net/maven/glassfish/org/hibernate/hibernate-jbosscache2/3.3.2.GA/hibernate-jbosscache2-3.3.2.GA.pom
Downloading:
Hey
Can this be the other way ?
I used the mirror tags in settings.xml to point to my nexus repository.
mirrors
mirror
idmy-repo-releases/id
name Releases/name
urlhttp://mavenrepo.releases/url
mirrorOfcentral/mirrorOf
/mirror
/mirrors
This thing actually
10/08/11 16:23:55 CEST: [WARN] The POM for
org.jboss.cache:jbosscache-core:jar:3.1.0.GA is missing, no dependency
information available
This is the only important line in your entire log. This says that
Maven cannot find the pom file for jbosscache-core version 3.1.0.GA.
All of your problems
Can this be the other way ?
What is the other way?
mirrorOfcentral/mirrorOf
also trying to download the other dependencies(ex:
plexus-interactivity-api) form the same repo which dont exist.
Saying a repo is a mirror of Central means that all artifacts which
do exist in Central must
Wayne, Laird
First, thanks for trying to help.
Second, I pretty much figured that out before posting the question.
I guess my 1st message was too verbose, but if you look at the end of it, I
said I could see the jbosscache-core artifact in JBoss's repo, but for some
reason my maven couldn't.
I
On Wed, Aug 10, 2011 at 3:41 PM, ccc calinco...@gmail.com 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.
As you can see from my earlier message, this repository:
repository
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
I am new on MAVEN, I am trying to configure the CAS to auth against
LDAP, and I am having the following problems,
please help
--Alex
Directory of C:\cas-server-3.4.2.1\cas-server-support-ldap
08/10/2011 08:44 AMDIR .
08/10/2011 08:44 AMDIR ..
08/10/2011 08:44 AM
The JBoss repo you're using (http://repository.jboss.org/maven2/), is an old
one which I believe has been shut down. (That's why you get access denied.)
It has been migrated to a Nexus instance at JBoss. If you search the JBoss
wiki you will find info about the new repos at that instance.
/Anders
thanks for any input and lessons learned.
Situation: my company has a number of web apps. all using dojo they all have
custom profiled dojo builds that are checked into the web apps source code.
We have discovered that someone over the years has made some coding changes
to these generated files
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
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
Did you read this Wiki page and follow the directions??
l:pom:1.1b from/to jboss
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
I'm using an ant build.xml that generates classes and compiles them with the
tools.jar from the JDK.
I am using MAVEN 2.2.1 version. JDK 1.5 to execute MAVEN. As maven 2.2.1
version supports higher then JDK 1.5 only so I have to use it.
This maven-antrun-plugin doesn't allow to specify neither
On Thu, Aug 11, 2011 at 12:06 AM, goutham goutham.vasire...@gmail.com wrote:
I want it to restrict to the remote repo only. It should not look into local
repo , at least first it have to look in remote and then go for local
On Wed, Aug 10, 2011 at 6:02 PM, Anders Hammar [via Maven]
You have to create Profile for that..
If you will put following entry in your settings.xml file it will first look
at the remote repository and then it will look for your local repository.
Basically you need to create profile
profile
idRepository Proxy/id
activation
On Thu, Aug 11, 2011 at 9:01 AM, Daivish Shah daivish.s...@gmail.com wrote:
I'm using an ant build.xml that generates classes and compiles them with the
tools.jar from the JDK.
I am using MAVEN 2.2.1 version. JDK 1.5 to execute MAVEN. As maven 2.2.1
version supports higher then JDK 1.5 only
Hi,
I tried giving JRE and TOOLS JAR from build.xml file. But it's working fine
if i run as ANT script.
But when i execute as MAVEN it's taking JAVA_HOME variable which is setup as
system variable so my system JAVA_HOME is 1.5 and i want to compile with
1.4.2 from MAVEN Only.
Even i gave
On Thu, Aug 11, 2011 at 9:47 AM, Daivish Shah daivish.s...@gmail.com wrote:
Hi,
I tried giving JRE and TOOLS JAR from build.xml file. But it's working fine
if i run as ANT script.
But when i execute as MAVEN it's taking JAVA_HOME variable which is setup as
system variable so my system
sounds like he'd be better off pitching the ant build for a full maven build
and using toolchains to get m-compiler-p compiling with 1.4... or pitching
maven and using ant.
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a
52 matches
Mail list logo
