Hi all,
I set my settings.xml so it will download the dependencies not from the
central (i.g. http://repo1.maven.org/maven2) but from my repository on the
server maschine.
The setting in my settings.xml looks as follow.
Does someone know what's wrong?
Regards
For me, I didn't use mirror
I simply defines available repositories and pluginRepositories.
Well, it seems working fine as long as my repositories mirror is running
correctly.
profiles
profile
idbootstrap/id
repositories
repository
...
This explains how to include/exclude resources:
http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html
I thought CVS files where by default excluded in all plugins. Do you already
override the includes/excludes in configuration ?
Tom
On Dec 28, 2007 7:11
On Dec 28, 2007 9:05 AM, Thomas Chang [EMAIL PROTECTED] wrote:
Hi all,
I set my settings.xml so it will download the dependencies not from the
central (i.g. http://repo1.maven.org/maven2) but from my repository on the
server maschine.
The setting in my settings.xml looks as follow.
You are right. Thanks!
Hi all,
I set my settings.xml so it will download the dependencies not
from the central (i.g. http://repo1.maven.org/maven2) but from my
repository on the server maschine.
The setting in my settings.xml looks as follow.
Does someone know what's
Actually I am overriding the default maven directory structure. But similar
is the case with jar applications. I guess when maven is supposed to
package(web directory), then its putting the CVS files. I concluded this
because in the classes folder inside WEB-INF there is no CVS file, probably
Hi all,
Normally the dependency/ in the pom.xml looks as follow:
...
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
/dependency
...
Now what I want to do is: I don't want to set the dependency version here but
from a property file on the
After using the buildnumber-maven-plugin I am seeing the an error while the
Maven is assembling the jar.
I had put the error trace below.
_
\smslibmvn package -e
Error stacktraces are turned on.
NFO] Scanning for projects...
NFO]
Ok Wendy,
Usualy I create the user because of the permission.
I understood, thank you for return.
- Original Message -
From: Wendy Smoak [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 28, 2007 12:57 AM
Subject: Re: Problem to send email (Validation user) with
Hi,
I think I've looked through the entire Internet by now, but I can't find any
way to explode ear:s using maven2. Does anyone know how to do this? I'm
using maven 2.0.6 and weblogic 9.2.
Regards,
Nille
--
View this message in context:
HI,
Is it possible to notify ( via email may be ) whenever a newer version of
artifact is deployed into the remote maven repository?
Any ideas?
Regards,
Amit
On Dec 28, 2007 12:03 PM, amidrunk [EMAIL PROTECTED] wrote:
Hi,
I think I've looked through the entire Internet by now,
Waouh, it may have taken some time :)
but I can't find any
way to explode ear:s using maven2. Does anyone know how to do this? I'm
using maven 2.0.6 and weblogic 9.2.
Hi, folks!
I've got a rather simple maven project for which I'd like to build several
different artifacts using classifiers. Actually I wouldn't say that these
artifacts are really different as the most important difference is the Java
source level being used (either 1.4 or 5.0, very much like
Hi, thanks for responding!
Waouh, it may have taken some time :)
You have no idea :)
See http://jira.codehaus.org/browse/MEAR-51
Looked good until I saw Would be really great if you implement that. at
the end :)
I get the impression that the purpose of exploding an ear into a deploy-dir
http://www.nabble.com/file/p14527241/continuum.log continuum.log
The attached log from Continuum 1.1 represents three consecutive builds of
exactly the same job. The first one terminates successfully at message ID
244653; the second one fails during StarTeam checkout at message 293524,
and
I have a similar problem since I upgraded to 1.0. I can't proxy some local
repositories.
I'll try to make some tests to see if it can be related to proxy settings.
Some of those repositories are on the same server. How can I access to them.
Can I put an url for a remote repo like
With which version of archiva is it ?
With a version 1.0 (I didn't test with 1.0) I have a similar problem for 2
reasons :
- Some external repositories proxied by archiva were down and each time
archiva tried to download a missing artifact it waited the http timeout
(probably 1min) to try another
I'm currently building a module whose end result is an exploded war. However,
I also want to include some other files to be deployed to the webappDirectory.
For example, I have the plugin declared with:
webappDirectory/home/brianjw/webapps/server/webappDirectory
In that directory I do get
[moved from [EMAIL PROTECTED]
On Dec 26, 2007 10:16 PM, Satya Prasad Sahu [EMAIL PROTECTED] wrote:
I am a new user to the Maven.
I tried to write a sample program to start with. But failing with the
initial set up of Maven.
I have gone through the SwiXAT user guide and I am trying to
this may be related to http://jira.codehaus.org/browse/CONTINUUM-1521
-D
On Dec 28, 2007 7:38 AM, Ken Turner [EMAIL PROTECTED] wrote:
http://www.nabble.com/file/p14527241/continuum.log continuum.log
The attached log from Continuum 1.1 represents three consecutive builds of
exactly the same
On Dec 27, 2007 12:07 PM, Mick Knutson [EMAIL PROTECTED] wrote:
I am trying to just prepare a clearcase release. But I am using several
snapshot plugins.
I also have all my modules as snapshots. How do I get maven to ignore the
plugin snapshots?
...
[INFO] Can't release project due to non
Mick Knutson wrote:
My project version is *E1B-1.0-SNAPSHOT*
I suppose your version should just be 1.0-SNAPSHOT (i.e. begin with a
number) without the quotes. The EJB part should be the artifactId.
hth,
Manos
-
To
On Dec 28, 2007 10:05 AM, Mick Knutson [EMAIL PROTECTED] wrote:
My project version is *E1B-1.0-SNAPSHOT*
Now I tried to just prepare each of my modules by themselves, and here is
what I get:
[INFO] Unable to parse the version string: *E1B-1.0-SNAPSHOT*
Since the version gets used in the
SO I changed the version to 1.0-SNAPSHOT but now get this error with the
maven dashboard pluging:
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Can't
On Dec 28, 2007 10:40 AM, Mick Knutson [EMAIL PROTECTED] wrote:
SO I changed the version to 1.0-SNAPSHOT but now get this error with the
maven dashboard pluging:
[INFO]
[ERROR] BUILD FAILURE
[INFO]
There is an RSS feed you can track on http://www.mvnrepository.com/
regards,
Wim
2007/12/28, amit kumar [EMAIL PROTECTED]:
HI,
Is it possible to notify ( via email may be ) whenever a newer version of
artifact is deployed into the remote maven repository?
Any ideas?
Regards,
Amit
--
Yes, a file URL will work - but if those repositories are proxies
themselves only the HTTP version will trigger a remote proxy.
- Brett
On 29/12/2007, Arnaud HERITIER [EMAIL PROTECTED] wrote:
I have a similar problem since I upgraded to 1.0. I can't proxy some local
repositories.
I'll try to
Hello,
I'd like to extend a mojo that is packaged within another maven plugin and
because the javadoc (and therefore the plugin metadata) isn't available to
plexus I thought of describing the plugin metadata manually. Is it possible
to specify this plugin descriptor somehow?
regards,
Bernhard
I want to append -${env} to each of my assembly tar files. Here is what I
have so far:
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-1/version
configuration
descriptors
I created a custom mojo that has a couple of attributes I'd like to
optionally set from the command line. I assume this would be something like
-Doverwrite=true when invoking the plugin (like Release plugin's
-DdryRun=true). But, I can't figure out how to get it to work.
I'm also having
Sorry. I figured it out. I was missing the expression option with the
annotation. I thought that I had already tried that.
This works:
/**
* @parameter expression=${planId} default-value=plan1
*/
private String planId;
/**
* @parameter
Does anyone know how to use release plugin together with multiper
project/modules? I have the following 5 projects:
* common (packaging=jar, parent project=main)
* core (packaging=jar, parent roject=main)
* framework (packaging=, parent parent project=main)
* web (packaging=war, parent
I just started getting this errror:
org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error
executing action 'clean-working-directory'
at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:434)
at
On Dec 28, 2007 3:40 PM, Mick Knutson [EMAIL PROTECTED] wrote:
I want to append -${env} to each of my assembly tar files. Here is what I
have so far:
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-1/version
On Dec 28, 2007 5:38 PM, Mick Knutson [EMAIL PROTECTED] wrote:
I just started getting this errror:
org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error
executing action 'clean-working-directory'
...
Caused by: java.io.IOException: Unable to delete directory
I just started getting this error:
[INFO] Error getting reports from the plugin '
org.codehaus.mojo:cobertura-maven-plugin': Unable to find the mojo '
org.codehaus.mojo:cobertura-maven-plugin:
2.2:dump-datafile' in the plugin 'org.codehaus.mojo:cobertura-maven-plugin'
On Dec 28, 2007 6:03 PM, Mick Knutson [EMAIL PROTECTED] wrote:
I just started getting this error:
[INFO] Error getting reports from the plugin '
org.codehaus.mojo:cobertura-maven-plugin': Unable to find the mojo '
org.codehaus.mojo:cobertura-maven-plugin:
2.2:dump-datafile' in the plugin
On Dec 20, 2007 6:05 PM, Mick Knutson [EMAIL PROTECTED] wrote:
*I have looked at:*
http://jira.codehaus.org/browse/CONTINUUM-1189
*And I have the same error, but I can't find a resolution for version 1.1NOT
1.1 alpha:*
That issue was closed as a duplicate of CONTINUUM-961, which was
supposed
Nothing changed from my cobertura plugin. I was trying to do a
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
version2.0/version
configuration
[WARNING] Error loading report
org.codehaus.mojo.surefire.SurefireReportMojo- AbstractMethodError:
canGenerateReport()
[INFO] Skipped About report, file index.html already exists for the
English version.
[INFO] Generate CPD Report report.
[INFO] Generate PMD Report report.
[INFO] Generate
[WARNING] Error loading report
org.codehaus.mojo.surefire.SurefireReportMojo- AbstractMethodError:
canGenerateReport()
[INFO] Skipped About report, file index.html already exists for the
English version.
[INFO] Generate CPD Report report.
[INFO] Generate PMD Report report.
[INFO] Generate
On Dec 28, 2007 7:09 PM, Mick Knutson [EMAIL PROTECTED] wrote:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
version2.0/version
...
Downloading:
Hmm
Here is my Surefire plugin:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdsurefire-report-maven-plugin/artifactId
configuration
includes
include
On 29/12/2007, Bernhard Huemer [EMAIL PROTECTED] wrote:
Hello,
I'd like to extend a mojo that is packaged within another maven plugin and
because the javadoc (and therefore the plugin metadata) isn't available to
plexus I thought of describing the plugin metadata manually. Is it
possible
Thanks. Actually I want to have something similar for our company's
repository which is lying on my LAN. The requirement is like, whenever
a developer deploys a newer version, everyone must be notified. So I
was wondering if Maven provides such a feature already.
Regards,
Hemant Malik
On
Hi,
When I say mvn deploy the maven is throwing java exception. My
repository is actually a folder on a network pc, and the folder is
mapped to Apache Web Server and thus in the poms the repository is
mentioned as http://192.168.x.x/repository , but deploy plug in
expects scp: instead of http ( i
On Dec 28, 2007 8:38 PM, amit kumar [EMAIL PROTECTED] wrote:
When I say mvn deploy the maven is throwing java exception. My
repository is actually a folder on a network pc, and the folder is
mapped to Apache Web Server and thus in the poms the repository is
mentioned as
maven release works best if you have this structure:
root
pom.xml -- parent
common
core
framework
web
Note: you should eliminate your main and move its pom to root.
Ofcourse you need to change all your module's pom accordingly.
-D
On Dec 28, 2007 3:59 PM,
On Dec 26, 2007 6:25 AM, aldana [EMAIL PROTECTED] wrote:
Heinrich Nirschl wrote:
No, the optional library may be needed for compiling. It can still be
optional if it is never loaded at runtime for a certain use case.
but how should someone know if a certain use case is not executed on
I have 26 developers and moving to 2.0.8 right now is not possible. Maybe in
a month.
As far as the reporting, I only have a generic declaration in reporting and
there is no reference to a version at all.
I also tried moving to 2.2 but I get the same error.
On Dec 28, 2007 6:22 PM, Mick
On Dec 28, 2007 5:14 PM, amidrunk [EMAIL PROTECTED] wrote:
[...]
I get the impression that the purpose of exploding an ear into a
deploy-dir
didn't really get communicated in that discussion. In my case, I can't
really point the server to the target-directories of individual projects.
We
You need to specify version=2.2 in both build and report sections
putting 2.2 in pluginManagement is not good enought
-D
On Dec 28, 2007 10:01 PM, Mick Knutson [EMAIL PROTECTED] wrote:
I have 26 developers and moving to 2.0.8 right now is not possible. Maybe in
a month.
As far as the
On Dec 28, 2007 11:01 PM, Mick Knutson [EMAIL PROTECTED] wrote:
As far as the reporting, I only have a generic declaration in reporting and
there is no reference to a version at all.
I also tried moving to 2.2 but I get the same error.
When you do what, exactly? You've pasted
53 matches
Mail list logo
