You can put the default values in a properties section in your pom,
then over-ride them in your default profile in settings.xml file or an
alternate settings.xml file. If using an alternate settings.xml file
you can specify it's location by using --settings path/to/settings.xml
or (-s for
Or use the help plugin. mvn help:active-profiles
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Try the remote resources plugin
http://maven.apache.org/plugins/maven-remote-resources-plugin/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Why don't you try the war:inplace goal instead of the war:war goal.
This copies classes/lib/etc... back from target into src/main/webapp.
Then use a context.xml file to define your webapp within tomcat.
JSP changes take without the need to copy any files.
Of course you'll have to be careful and
Bad sample case. That can be done with properties. What I would nead now is
the property that would come from file that is not commited to SVN. I would
like to set target dir with that property. So everyone that works with
project can set target dir pointing to Tomcat webapp dir. If
The settings.xml will work for properties, however, after re-reading
this, why don't you consider using the war:inplace goal instead, and
have each user setup a context within tomcat's webapp directory using
a context xml file that points back into your project's webapp
directory. That buys you
You can use the dependency:unpack
http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html
to unpack the classes from the jars.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Can't you just use . for current directory instead of a variable?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://maven.apache.org/general.html#plugin-version
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
i see, i had a similar issue. projects are independent and should not
'reach into' each other.
to use common stuff, jar them up in one project, install them into
your repo, then in the other projects you can add as a dependency or
use the unpack goal of the dependency plugin to explode them
mvn dependency:resolve should do the trick, add -U to force the update
if you want to use it again after maven did it's daily check
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://jira.codehaus.org/browse/CONTINUUM-1312
vote for it
--tom
i'm unaware of any plugins to prohibit unused deps but the dependency
plugin has an analyze goal can give you a report showing dependencies
that are declared and unused that I find useful when cleaning
dependencies.
mvn dependency:analyze
Why don't you just put your version in a standard properties file
using maven's resource filtering (like you are trying to do with the
java file) and have your class read it from there?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
http://jira.codehaus.org/browse/MNG-1977
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Ah, I see what you are trying to do now. Although according to the
maven lifecycle the resources should get processed before the compile.
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
so it should be working.
I think you can get your end result by manually
Do you have the maven-enforcer-plugin in your pluginManagement section?
I removed it from mine and forced the version in the usage instead of
in the management section and my build worked.
-
To unsubscribe, e-mail: [EMAIL
Actually, using version in the usage also causes the problem. But
removing the version tag of the plugin works. I'm submitting bug
report.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
The real solution is reverting to the enforcer 1.0-alpha-2 release. I
was using 1.0-alpha-3 which for some reason isn't listed as the
current release.
The JIRA for the bug in question is http://jira.codehaus.org/browse/MENFORCER-14
I'm having the same issue. Perhaps the cause is the same as whatever
fixed http://jira.codehaus.org/browse/MNG-2434?
Is anybody else experiencing this?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
mvn dependency:sources
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This started happening after upgrading from maven 2.0.6.
Has anybody else experienced this?
--
tom
.
- Yann
On 7/3/07, Tomislav Stojcevich [EMAIL PROTECTED] wrote:
This started happening after upgrading from maven 2.0.6.
Has anybody else experienced this?
--
tom
--
tom
It doesn't sound like the build is still running. It sounds like the
project still looks like it's building because of the icon. I've had
this happen several times.
I clear it up by adding a build definition to the project and specify
the goal as -v (which just gives the maven version) then I
You shouldn't need to configure anything in the pom, just do mvn
dependency:sources
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Try -cpu or a -U option with that, maybe that'll trigger the download
of the maven version.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Try mvn dependency:sources -U, the -U will force the check, if it
already checked once today, it won't check again unless you force it.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
This would be useful if you are reverse engineering the database and
there is a database change. No cvs change but a table got modified.
--
tom
Use the build helper plugin to add additional source paths
http://mojo.codehaus.org/build-helper-maven-plugin/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The maven-dependency-plugin has a sources goal.
http://mojo.codehaus.org/dependency-maven-plugin/introduction.html
mvn dependency:sources
This is not available in the released 1.0 version, but it is in the
1.1-SNAPSHOT. You need to build from source or get from mojo snapshot
repository.
Use scopeprovided/scope which makes them available at build time
but keeps them out of your war.
On 3/22/06, Tom Joad [EMAIL PROTECTED] wrote:
Hello,
Please see.
http://mojo.codehaus.org/jspc-maven-plugin/
We must add inside your pom.xml
dependency
groupIdtomcat/groupId
Will there be a way to force the build even though there were no scm changes?
I have projects that generate code from database metadata. If a
database change occurs I would need the forced build (scheduled
nightly) to still occur so that database changes are pick up and the
system is rebuilt.
The ear plugin does this for you.
I don't think it's part of the j2ee spec to have dependent jars
bundled inside the ejb.jar. I believe that they normally get grouped
together inside of an ear file.
You setup a seperate project with packaging of ear and add your
ejb.jar as a dependency. Your
See: http://jira.codehaus.org/browse/WAGON-30
Replacing the jar in your maven/lib directory as indicated in the
comments should work, it worked for me.
--tom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Add this to the buildplugins section of your pom:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
phasepackage/phase
goals
http://mojo.codehaus.org/source-repository.html
--
tom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Once created it looks like you can't change the priority. Somebody
from the maven team probably could.
I would suggest voting for it in JIRA.
I tried to rebuild the jar myself from the trunk and get the same
results, no antlib.xml and no ant package.
On 1/18/06, Rollo, Dan [EMAIL PROTECTED]
Getting the following error in 2.0.1 when I run artifact:dependencies
from a project that has a parent pom. It use to work in 2.0.
[artifact:dependencies] An error has occurred while processing the
Maven artifact tasks.
[artifact:dependencies] Diagnosis:
[artifact:dependencies]
There are poms you can copy under org.hibernate for a start.
The versions there are a bit more up to date than under hibernate and
those poms seem to have information rather than being the default as
are the ones in hibernate.
I needed the newest version of the hibernate-tools and just used the
I take back part of that. org.hibernate.hibernate.3.1rc2 has a pom
you can you for a start.
org.hibernate.hibernate-tools only had alpha5 with no pom. I made up
the following based on what was in the lib directory of the download
for the 3.1beta1. It depends on a snapshot of jtidy-r8 which is
It's out there now, along with all of the other tomcat 4.1.31 jars. I
asked the Tomcat team to post it to the Apache repository and it
eventually got sync'd.
--
tom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Yes, it's 1 level under the root. I could move it up to the root but
there are far too many reletive references in it that would have to
change.
On 11/29/05, Emmanuel Venisse [EMAIL PROTECTED] wrote:
your file is in a sub-directory?
Emmanuel
Tomislav Stojcevich a écrit :
That works for me
That works for me also, but only if the build.xml file is in the root
of the project. Mine isn't and I don't see how to specify the
location of the file.
On 11/24/05, Jeremy Hughes [EMAIL PROTECTED] wrote:
Leaving the POM filename field empty worked for me.
Jeremy
On 11/18/05, Tomislav
Added http://jira.codehaus.org/browse/CONTINUUM-459
On 11/18/05, Emmanuel Venisse [EMAIL PROTECTED] wrote:
I'll check it. File a jira issue, so i wouldn't lose it.
Emmanuel
Tomislav Stojcevich a écrit :
The same thing happens to me. I did select add ant project but when I
go to add
The same thing happens to me. I did select add ant project but when I
go to add the build definition it asks me for the pom. I tried
specifying the build.xml file for the pom and specifying the ant
target in the goal but that doesn't work.
I am using version 1.0.1.
On 11/15/05, Emmanuel
Does anybody know the best way to include sources that are generated
in one project into another project (not for compile purposes, just to
use for further source generation so as to avoid generating from
metadata again which is quite a lengthy process due to the number of
tables).
I have 2
That particular jar is a sun licensed jar so it won't be in the
central repository, you will have to get it yourself, it's POM has the
download url (the POM in the original location, not the new one
http://www.ibiblio.org/maven2/jdbc/jdbc-stdext/2.0/jdbc-stdext-2.0.pom).
See:
How do you reference something that is a collection in the POM?
Let's say there are 2 developers and I want to get their email
addresses to put in the notifier.address section of the ciManagement
section (I know a mailing list is preferred but we don't have one set
up right now and I know there
You need to specify the type as ejb-client in your client project's pom.
dependency
groupIdcom.abc/groupId
artifactIdEjb/artifactId
version1.00/version
typeejb-client/type
/dependency
On 10/25/05, Ashley Williams [EMAIL PROTECTED] wrote:
Hi,
Just wondering how I go about including an
If I am correct, maven2 includes all optional transient dependencies by
default and you have to specify an exclude for each optional transient
dependency you do not want. This could potentially lead to many excludes.
It would be nice to have a flag to to turn off all optional transient
and then only
include project1, rather than excluding project3, project4, project5, etc...
On 10/24/05, Jason van Zyl [EMAIL PROTECTED] wrote:
On Mon, 2005-10-24 at 09:30 -0400, Tomislav Stojcevich wrote:
If I am correct, maven2 includes all optional transient dependencies by
default and you
What happened to the plugin documentation?
Are they still available somewhere and am I just not finding them?
There use to be a link that took you to a list of all available plugins and
you could get to the documentation for each of the plugins that showed all
of the parameters. It's kind of
52 matches
Mail list logo
