Hi all,
Last week I installed the Maven Integration for Eclipse (from
http://m2eclipse.sonatype.org/update) in Eclipse Ganymede and it runs. I.g.
I can see the maven logo in the context-menu when I right click on a
project.
Yesterday I uninstall the Maven Integration for Eclipse because of some
Hi!
On Thursday 04 September 2008 John Casey wrote:
On the last go around, we had one issue pop up with maven plugin builds
(though it might also apply to build extensions in the reactor as well).
I've fixed it, and now here's the lucky 13th release candidate:
Hi,
I've just noticed that filtering doesn't work if the character prefixing
the property reference is a $ (dollar sign).
Example:
pom.xml:
properties
FOOBAR/FOO
/properties
build
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
that's because $${blah} is an escape for ${blah}
On Thu, Sep 4, 2008 at 9:41 AM, Henric Larsson [EMAIL PROTECTED]
wrote:
Hi,
I've just noticed that filtering doesn't work if the character prefixing
the property reference is a $ (dollar sign).
Example:
pom.xml:
properties
I should correct that. there are some escapes, and AFAIK the behaviour you
are seeing is by design.
not sure what the exact escapes are... but they should be detailed somewhere
On Thu, Sep 4, 2008 at 9:55 AM, Stephen Connolly
[EMAIL PROTECTED] wrote:
that's because $${blah} is an escape for
I get lots of these Messeages durring a Site Report Generation:
[INFO] Generating Test JavaDocs report.
[WARNING] The Javadoc plugin parameter 'proxyHost' is deprecated since 2.4. Ple
se configure an active proxy in your settings.xml.
[WARNING] The Javadoc plugin parameter 'proxyPort' is
Hello,
On my project we have quite a large codebase separated in several Maven
multimodule projects. In one of the parent poms I have configured to use
maven-dependency-plugin to verify that we use dependencies appropriately, as
described here:
Hi, Thanks for you reply.
I should correct that. there are some escapes, and AFAIK the behaviour
you
are seeing is by design.
not sure what the exact escapes are... but they should be detailed
somewhere
Still seems wrong to me, if double dollar is supposed to work as an
escape, I would
Folks;
eventually figuring out that my webapps better be deployed to the
application server as an ear rather than separate war archives (partly
because we're about to dump EJB modules in there rather soon as well, and
partly because most of the .wars share the same libraries and so deploying
an
Here's what I think I've understood out of my reading and my
experimentation:
Maven's version numbers have forms like this:
major[.minor[.fix]]-[blahblahblah[-buildnr]]
Where major, minor, fix are parsed and compared as integers. Assumed
to be zero if missing?
blahblahblah is parsed and
In my pom I declare a distributionManagement repository on a central server
with url${remoteRepository}/url. This variable is defined in the
settings.xml. The variable is resolved correctly on deploy goal.
In the same pom I declare the same repository for dependency checking, also
with the
Hi,
I don't know how I did get it but maven doesn't find the wagon ftp extension
anymore:
[INFO] snapshot net.atos.wlp:parent-pom:0.0.1-SNAPSHOT: checking for updates
from internal
[WARNING] repository metadata for: 'snapshot
net.atos.wlp:parent-pom:0.0.1-SNAPSHOT' could not be
I'm not instantiating the wagon - Plexus should be doing that and injecting it
into my plugin. My plugin project depends upon my wagon projecy which depends
upon wagon-ssh (which contains ScpWagon). Scope for the dependencies are both
compile.
Thanks,
Justin
- Original Message -
From:
Hi,
I don't know if this is an issue or a bug or both:
In my settings.xml I define an internal repository :
repositories
repository
idinternal/id
nameRepository on deacr001/name
urlfile://Y:/IPS/Produkt/maven-repository/internal/url
Hello,
I have this file : src/main/resources/faces-config.xml
After mvn clean compile this file is put at the root of the classes
directory.
But I don't want that, so I tried :
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
FWIW (probably not much) I also tried merging my two projects into one and see
the same result.
Justin
From: Edelson, Justin
Sent: Thu 9/4/2008 8:14 AM
To: users@maven.apache.org
Subject: Re: Stuck on custom wagon and plexus
I'm not instantiating the wagon
Resources aren't compiled. See
http://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html
for information on how to exclude resource files.
Justin
From: Marc Schneider [mailto:[EMAIL PROTECTED]
Sent: Thu 9/4/2008 9:07 AM
To: Maven
On Thu, Sep 4, 2008 at 9:07 AM, Marc Schneider
[EMAIL PROTECTED]wrote:
I have this file : src/main/resources/faces-config.xml
After mvn clean compile this file is put at the root of the classes
directory.
But I don't want that, so I tried :
Can I ask what you do want to do with it, if not
On Thu, Sep 4, 2008 at 6:06 AM, [EMAIL PROTECTED] wrote:
From intuitive feeling I would say: there is a reference to a defined
repository in settings.xml, so Maven will find the missing attributes, but no
it does not, it does like this:
...
not very helpful this error message. It seems
Geoffrey Wiseman a écrit :
On Thu, Sep 4, 2008 at 9:07 AM, Marc Schneider
[EMAIL PROTECTED]wrote:
I have this file : src/main/resources/faces-config.xml
After mvn clean compile this file is put at the root of the classes
directory.
But I don't want that, so I tried :
Can I ask what
Geoffrey Wiseman a écrit :
On Thu, Sep 4, 2008 at 9:07 AM, Marc Schneider
[EMAIL PROTECTED]wrote:
I have this file : src/main/resources/faces-config.xml
After mvn clean compile this file is put at the root of the classes
directory.
But I don't want that, so I tried :
Can I ask what
Thanks for your answer.
So I add this in the build section :
resources
resource
directorysrc/main/resources/directory
excludes
exclude**/faces-config.xml/exclude
/excludes
/resource
/resources
but after mvn
org.codehaus.mojo.webstart:webstart-maven-plugin: checking
for updates from central
Downloading:
http://repo1.maven.org/maven2/org/codehaus/mojo/webstart/webstart-maven-plugin/1.0-alpha-2-custom-20080904/webstart-maven-plugin-1.0-alpha-2-custom-20080904.pom
Downloading:
http://mvn.internal.com/maven2/deploy/org/codehaus/mojo
Hmm. That works for me. If you run mvn -X, do you see that the exclude is being
passed to the resources plugin? Should look something like this:
[DEBUG] (f) resources = [Resource {targetPath: null, filtering: false,
FileSet {directory: YOUR_PROJECT_DIRECTORY\src\main\resources, PatternSet
Hi,
I am trying to debug a jboss application (in particular with Seam) whose
source are contained in my maven repository ( I downloaded them with
'mvn dependency:sources' command, and I can see them).
I set up the source path under Eclipse-Server-Open Launch
Configuration-Source , choosing under
Hello,
I have created a .mdo with a required int attribute of count, and I built
with the goals java and xpp3-writer.
Here is the snippet from my .mdo file for the attribute.
field xml.attribute=true
version1.0.0/version
namecount/name
requiredtrue/required
typeint/type
/field
Yes sorry you're right in fact this works.
Thanks for your help.
Marc.
Edelson, Justin a écrit :
Hmm. That works for me. If you run mvn -X, do you see that the exclude is
being passed to the resources plugin? Should look something like this:
[DEBUG] (f) resources = [Resource
Hi,
since some time all my maven generated eclipse configs for webapps
(packagingwar/packaging, including m2 plugin generated configs, do
not contain source entries for /src/main/java.
I use maven 2.0.9, Eclipse ganymede, m2eclipse 0.9.5.20080717-1821,
maven eclipse plugin 2.5.1.
See
I am a newbie to using the release plugin, but I have a need to use just
part of the functionality of the release:prepare goal. How can this be
done? I have read the optional arguments and do not see a way to do this.
For example I might need to
* Just check that there are no snapshot
I'm also interested in using maven embedder and don't know which
version to use and where to find it. I had been using 2.1-SNAPSHOT
from the snapshot repo but it seems to no longer be available.
On Wed, Sep 3, 2008 at 1:12 PM, Shalin Shekhar Mangar
[EMAIL PROTECTED] wrote:
Hello,
I'm trying to
The Maven team is pleased to announce the release of the Maven Help
Plugin, version 2.1
The Maven Help plugin provides goals aimed at helping to make sense
out of the build environment. It includes the ability to view the
effective POM and settings files, after inheritance and active
profiles
On Thu, Sep 4, 2008 at 8:58 AM, Scott Carter [EMAIL PROTECTED] wrote:
I am a newbie to using the release plugin, but I have a need to use just
part of the functionality of the release:prepare goal. How can this be
done? I have read the optional arguments and do not see a way to do this.
For
You can hack together a new plugin pretty quickly that uses the
maven-release-manager components to achieve what you need. We did this
in order to integrate a release mechanism into our Hudson build server.
-Original Message-
From: Dan Tran [mailto:[EMAIL PROTECTED]
Sent: Thursday,
Have you read this document -
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
It may help answer some of the questions.
-Original Message-
From: Benjamin Smith-Mannschott [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 04, 2008 6:21 AM
To: Maven
Maven will use the first version of a plugin it sees, so somewhere in
your workspace you have an old version of the dependency plugin and when
running the other projects, it is still using this old version.
-Original Message-
From: Rune Flobakk [mailto:[EMAIL PROTECTED]
Sent: Thursday,
Martin Höller wrote:
Hi!
On Thursday 04 September 2008 John Casey wrote:
On the last go around, we had one issue pop up with maven plugin builds
(though it might also apply to build extensions in the reactor as well).
I've fixed it, and now here's the lucky 13th release candidate:
Thank you for your reply, Brian!
Yes, that is what I figured as well. The workspace consists of several
projects which does not share the same parent pom (only in the context
of running eclipse:eclipse). So I don't want to be forced to upgrade the
version of the plugin in projects which I
I have a Jboss ESB example project with ant build script to convert to
maven. Maven usually prefers certain directory structure. There is a
plugin for jboss esb packaging. Is there somewhere I can find the
directory structure and pom.xml?
Christian,
Is there any reasons you can't import your projects or check them out from
version control using Maven Project import wizard in m2eclipse? See
http://docs.codehaus.org/display/M2ECLIPSE/Importing+Maven+projects
As one of m2eclipse developers, I would NOT recommend using
If this is a custom plugin, make sure your plugin's POM contains:
packagingmaven-plugin/packaging
cody zhang wrote:
The PluginDescriptor for the plugin Plugin
[org.apache.maven.plugins:maven-checksnapshot-plugin] was not found. [INFO]
We have used the plugin with great success and can send you our layout but
basically use the standard maven 2 structure as follows
src/main/java
src/main/resources
put the jbm-queue-service.xml file in the resources directory and the
following files in the resource/META-INF directory
On Sep 4, 2008, at 18:47, Beyer,Nathan wrote:
Have you read this document -
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
It may help answer some of the questions.
Yes. That helped, as did
On Thu, Sep 4, 2008 at 8:52 PM, Benjamin Smith-Mannschott
[EMAIL PROTECTED] wrote:
On Sep 4, 2008, at 18:47, Beyer,Nathan wrote:
Have you read this document -
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
It may help answer some of the questions.
I've replicated this problem in some of my own projects. It seems that
the key is to have the compiler plugin configured in the
pluginManagement section of the POM, and then to enable a report like
the javadoc reports that will cause the lifecycle to fork and compile
sources. At that point, it
I figured the directory structure would be similar to regular maven
project. So, I have the following:
src/main/java
src/main/resources
src/test/java
src/test/resources
I followed your suggestion to move the deployment.xml and jboss-esb.xml
to src/main/resources/META-INF directory.
In the
Here are some relevant sections of my pom
packagingjboss-esb/packaging
build
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
/resources
plugins
plugin
groupIdorg.codehaus.mojo/groupId
Are you sure the packaging is jboss-esb rather than just esb as the error
message states? I got the same error you did when i changed my packaging to
just esb. Make sure you only have one packaging entry.
Scott Ryan
President/CTO
Soaring Eagle L.L.C.
Highlands Ranch, Co. 80129
(303) 263-3044
I have exactly the same packaging and plugin as yours.
modelVersion4.0.0/modelVersion
groupIdmyCompany/groupId
artifactIdmyEsb/artifactId
packagingjboss-esb/packaging
version1.0-SNAPSHOT/version
namemyEsb/name
I use jboss-esb for packaging.
The
Only one packaging element is in the pom.xml. That should be ok.
The error shows esb is a very strange.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott
Ryan
Sent: September 4, 2008 4:36 PM
To: Maven Users List
Subject: Re: Jboss ESB and Maven
Are
Are you sure esb does not appear anywhere else in your pom or any parent
pom?
Scott Ryan
President/CTO
Soaring Eagle L.L.C.
Highlands Ranch, Co. 80129
(303) 263-3044
[EMAIL PROTECTED]
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 2:45 PM, Lam Hayward [EMAIL PROTECTED]wrote:
I have exactly the
try changing the packaging to war and see if you get a warning about
web.xml when you do mvn install.
Scott Ryan
President/CTO
Soaring Eagle L.L.C.
Highlands Ranch, Co. 80129
(303) 263-3044
[EMAIL PROTECTED]
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 3:04 PM, Scott Ryan [EMAIL PROTECTED]
I created a brand new Java project from eclipse and all the maven
directory from scratch. It works now!!
It produced the .esb file.
Thanks.
In terms of jar dependency, a lot of the jboss esb jars can't be found
in maven repo. Do you simply add them to your local repository? Or is
there a
http://repository.jboss.com/maven2
should have all the jboss stuff
Scott Ryan
President/CTO
Soaring Eagle L.L.C.
Highlands Ranch, Co. 80129
(303) 263-3044
[EMAIL PROTECTED]
www.soaringeagleco.com
On Thu, Sep 4, 2008 at 3:05 PM, Lam Hayward [EMAIL PROTECTED]wrote:
I created a brand new Java
The Mojo team is pleased to announce the release of the Versions Maven
Plugin, version 1.0-alpha-1.
This plugin allows:
* the querying for newer versions of plugins used in a project.
* the querying for newer versions of dependencies used in a project.
* updating a project's parent to the latest
I think this is a bug. I had the same problems trying to escape things
recently as well.
However, you might try the following for your use case:
[EMAIL PROTECTED]@
Cheers,
Brett
2008/9/4 Henric Larsson [EMAIL PROTECTED]
Hi, Thanks for you reply.
I should correct that. there are some
Sorry, it should have been clear to me where you were instantiating it :)
I think this is still a classloading issue, as it is a clash between the
built-in wagon-ssh and the dependency you are trying to use.
If you are using Maven 2.0.9, try again with Maven 2.0.8 (it might also be
this bug:
It's definitely a classloading issue as I was ultimately able to do what I
needed to do with reflection. But that code is really ugly and I'd like to
understand the problem. Rolling back to 2.0.8 isn't really an option as I have
some projects that are dependent upon the deterministic dependency
2008/9/5 Edelson, Justin [EMAIL PROTECTED]
It's definitely a classloading issue as I was ultimately able to do what I
needed to do with reflection. But that code is really ugly and I'd like to
understand the problem. Rolling back to 2.0.8 isn't really an option as I
have some projects that
I don't have that problem (TestNG 5.8).
Are you sure that you're not using the JUnit assert classes, etc?
Cheers,
Brett
2008/9/1 Wim Deblauwe [EMAIL PROTECTED]
Hi,
when I run 'mvn dependency:analyze' I always get this warning:
[WARNING] Used undeclared dependencies found:
[WARNING]
Does it work from the command line version of Maven 2.0.8? IIUC, m2e uses a
snapshot version of Maven that doesn't support extensions.
- Brett
2008/9/4 [EMAIL PROTECTED]
Hi,
I don't know how I did get it but maven doesn't find the wagon ftp
extension anymore:
[INFO] snapshot
Hi,
I am trying to create scripts in Maven.
Steps Performed:
1. Extracted the maven2.9 distribution in a folder.
2. Set the Maven bin directory in my classpath.
3. Changed directory to my maven project.
4. Run following command: mvn install
Issue 1:
=
It was not able to
C:\tracert
http://repo1.maven.org/maven2/org/apache/servicemix/samples/3.2.1/samples-3.2.1.pom
Unable to resolve target system name
http://repo1.maven.org/maven2/org/apache/servicemix/samples/3.2.1/samples-3.2.1.pom.
This is simply an invalid execution of the command. Windows tracert,
ping,
Take it from the CI system, there is no official release.
http://ci.sonatype.org/view/Maven%203.0.x/job/maven-3.0.x-bootstrap/
On 4-Sep-08, at 9:00 AM, Kem Elbrader wrote:
I'm also interested in using maven embedder and don't know which
version to use and where to find it. I had been using
Hi Wayne,
Thanks for a quick reply.
Please find the updated output for the commands. I would like to highlight
one thing that I have also mentioned in my last mail that I am also not able
to access the link using Web Browser. Current I am located in Japan and my
team is in india. The link is
C:\tracert
repo1.maven.org/maven2/org/apache/servicemix/samples/3.2.1/samples-3.2.1.pom
Unable to resolve target system name
repo1.maven.org/maven2/org/apache/servicemix/samples/3.2.1/samples-3.2.1.pom.
As I said before, you are using these commands incorrectly.
tracert repo1.maven.org
ping
From intuitive feeling I would say: there is a reference to a defined
repository in settings.xml, so Maven will find the missing attributes,
but no it does not, it does like this:
...
not very helpful this error message. It seems that I have to force my
developers to define the URL two
66 matches
Mail list logo
