merci Olivier ;-)
it works if I do:
org.apache.maven.plugins
maven-resources-plugin
false
${*}
Thanks
Yann
--
View this message in context:
http://maven.40175.n5.nabble.com/Filtering-
Wayne Fay wrote
>
> Yes. What version of Maven are you using?
>
> If you aren't using @@ token, you should turn it off. That is
> described in the docs.
>
>
I use maven 3.0.3
Sorry but I don't see in the doc where to turn off the interpolation of @@
token, could you help ?
Thanks
Yann.
--
V
Hello,
Sorry for being unclear...
In a simple maven jar project I have the following pom:
4.0.0
org.test.mvn
mvnTestFiltering
jar
mvnTestFiltering
1.0.0-SNAPSHOT
true
Hello,
If in file, where filtering is activated, I have
@${project.artifactId}
then ${project.artifactId} won't be replaced.
If i do the same test with the at sign after ${project.artifactId} then it
wil be replaced.
Should I fill a bug ? where ?
Thanks
Yann
--
View this message in context:
ht
I haven't reproduced the problem on a separate project yet.
I have used m2eclipse and got 2 different results:
On the Dependecy Hierarchy the dependency appears as compile but on the
Dependency Graph it appears as provided. But I still couldn't see what is
pulling this dependency as compiled.
Wh
According to the maven 3 release notes
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html it's not
reliable.
"Furthermore, not all parts of the Maven 2.x resolution API could be bridged
onto Aether. Most notably the maven-dependency-tree shared component which
is used for mvn depende
maven 3.0.3
I have a parent company pom that defines a dependency as provided.
This provided dependency has a number of dependencies itself, among which
commons-collections:commons-collections.
My understanding is that all dependencies on which the provided dependency
depends on should also be p
Wayne Fay wrote:
>
> That would be the correct next step. But again, I'm not making any
> statements as to whether or not this will actually occur. It will need
> to be discussed on the Dev list and in the Jira.
>
> I can think of an awful lot of reasons why this should not be
> implemented -- f
@Jörg : we had the same issue with the class-path of the manifest. to resolve
it you have to add useUniqueVersions to false to all archives (jar, ejb,
war...):
org.apache.maven.plugins
maven-jar-plugin
Yes, maybe
I don't know how was working maven 2 for this, but if it is the simplest way
then yes.
Does it sound a reasonnable request/feature ?
thanks
Yann.
--
View this message in context:
http://maven.40175.n5.nabble.com/Issue-with-mvn3-timestamp-snapshots-being-downloaded-in-local-repository-
I did the test with the new maven 3.0.3 distribution and I still get the same
behaviour.
For me, it sounds like a regression compare to Maven 2.
I understand why for deployment this behaviour has been removed so that
snapshot artifacts will always be deployed using a timestamped version. But
I don
@benjamin
There are several drawbacks with the
maven-dependency-plugin:purge-local-repository:
- Performances slowdown if used systematically, i.e. included in project's
pom or worse super pom, due to the downloads from the remote. One benefit of
upgrading to maven 3 for us is the performance imp
> So what you describe is normal and has been like this since Maven 2.x
With Maven 2 we used unique snapshot versions.
The issue with Maven 3 is that developers local repositories might grow
significantly since several timestamp snapshots are downloaded.
Also we don't have a mechanism to purge
It's my understanding that timestamp snapshots should only exist in remote
snapshot repositories and are created when doing a mvn deploy.
What I see though is timestamp snapshots downloaded into my local repository
when doing mvn install.
Here the test case:
artifact a (jar) depends on artifact b
eclipse (it should convert them in 2.0)
- check that you have the same error.
It will help us to analyze the problem.
arnaud
On Dec 4, 2007 10:55 PM, Yann Albou <[EMAIL PROTECTED]> wrote:
I just tried with the latest snapshot and I get the same behaviour.
I see these warnings during i
r that says "Invalid classpath publish/export
dependency..."
Siarhei Dudzin a écrit :
Do you get the same from getting the latest snapshot instead of the trunk?
Where do you see this waring? During import or after import in the problems
view?
On 12/4/07, Yann Albou <[EMAIL PROTECTED]>
Is someone facing the same issue ?
Yann.
Yann Albou a écrit :
Hello,
After generating my eclipse projects with "mvn -Dwtpversion=2.0
eclipse:eclipse" and importing these projects into an europa workspace I
get the following Warning:
"Claspath entry
M2_REPO/commons-logging/
MAIL PROTECTED]> wrote:
I'm on a Linux machine and simply created a symlink to the parent pom in
one of the submodules. Then it showed up in Eclipse.
Hth,
Nick Stolwijk
Yann Albou wrote:
Hello;
I use a multi module maven project.
after generating the eclipse project and importing these
Hello;
I use a multi module maven project.
after generating the eclipse project and importing these project in an
eclipse workspace I get all my projects in my worspace.
Now I would to have a way to get access to the root pom.xml (parent pom
of all my imported projects).
Do you guys have an
Hello,
After generating my eclipse projects with "mvn -Dwtpversion=2.0
eclipse:eclipse" and importing these projects into an europa workspace I
get the following Warning:
"Claspath entry
M2_REPO/commons-logging/commons-logging/1.0.4/commons-loggin-1.0.4.jar
will not be exported or published
Hello,
I am writting a M2 plugin in which I need to access to The Manifest
Information.
Based on the Maven Project (MavenProject project) I was expected to get
a method like project.getManifestConfiguration() but it doesn't exist.
I have also tried to play with the MavenArchiver component b
Hi,
I use the m2 cobertura plugin.
It works fine.
For information I had to add the following in order to make it works:
org.apache.maven.plugins
maven-surefire-plugin
net.sourceforge.cobertura.datafile
target/cobertura/cobertura.ser
Hello,
In a mojo, I would like to generate the manifest.mf file as we can find
it in the result jar (with the Class-Path entry).
I tried to play with the MavenProject component but without success.
Thanks
Yann
-
To unsubscr
s above the children modules.
I'd suggest a similar arrangement with your own poms. You will need
another "level" of parent poms to make this happen.
Wayne
On 12/18/06, Yann Albou <[EMAIL PROTECTED]> wrote:
Hello,
In my pom parent I have defined (in the pluginManagement sect
Hello,
In my pom parent I have defined (in the pluginManagement section) a
plugin configuration that is bind to a phase:
[...]
[...]
maven-assembly-plugin
jar-with-dependencies
I had a similar issue: I set up to the url tag :
http://yoururl in my pom parent.
(I don't know why but you cannot use relative url)
Yann
Breddy wrote:
Group,
I have a POM that inherits from another using a relative path that looks
something like ../parent-pom-dir/pom.xml. All POM inheritance
Wendy Smoak wrote:
On 12/5/06, Christian Goetze <[EMAIL PROTECTED]> wrote:
If I generate the default site according to the mergere book, I get
essentially a useless cover page with a navigation menu that lists the
modules, but without links
I've seen that happen too. Most of my projects have
Done, I added a section "How to create your own predefine assembly"
Yann.
Wendy Smoak wrote:
On 12/3/06, Yann Albou <[EMAIL PROTECTED]> wrote:
I think this tips should be in the assembly plugin documentation.
Each plugin has a page on the wiki where we encourage use
maven-assembly-plugin
Of course you can overwrite default plugin configuration.
Hope it will help other people.
Yann.
Wendy Smoak wrote:
On 12/2/06, Yann Albou <[EMAIL PROTECTED]> wrote:
I saw I can configure a descriptorRefs, but it seems limited to
predefined assembly files
I have created my own assembly.xml file.
Now I would like to make this file available through the maven repository.
Is this possible ?
I saw I can configure a descriptorRefs, but it seems limited to
predefined assembly files (bin, jar-with-dependencies, or src).
I would like to add my own descri
I have created a plugin with a goal: "myplugin:mygoal" with phase is
"generate-sources" and requiresDependencyResolution is set to "compile".
If I run "mvn myplugin:mygoal" everything is fine.
if I run "mvn install" everything is fine ("myplugin:mygoal" is run at
"generate-sources" phase).
B
spath.
In addition, finalName only effects the name of the artifact generated in
the target directory. If you install/deploy the same artifact it will
(should) have the standard naming of ${artifactId}-${version}. This is A
Good Thing, as it prevents ambiguity in the repository.
HTH,
Doug
On 10/1
Hi,
I try to use the finalName in my parent pom as following:
${artifactId} (without the version number)
If I run maven from the parent pom everything works fine: all my
artifacts are generated without the version number. and also the
classpath entry of the manifest.mf file is correctly set.
would be very useful for us to have this little feature.
Yann.
dan tran wrote:
dont think it is possible.
What is the point of removing every thing inside but not the directory?
-D
On 9/29/06, Yann Albou <[EMAIL PROTECTED]> wrote:
Hi,
When running "mvn clean", Is it posib
Hi,
When running "mvn clean", Is it posible to not remove the directory
target but only what is inside ?
Yann.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Jan,
What I tried to do to resolve this problem is to define a propeties
xmlbeans.version in the plugin:
org.apache.
xmlbean
${xmlbean.version}
2.0.0
And then when you run maven in your project use:
mvn -Dxmlbean.version=2.2.0 install
unfort
Yann Albou wrote:
Hello,
I have exactly the same problem.
I also tried to create a profile directly in the pom :
my.profile
true
Hello,
I have exactly the same problem.
I also tried to create a profile directly in the pom :
my.profile
true
olveP
luginsMojo.java
It was working before the refactor but could be broken now. It will at
least give you a reference point.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Yann Albou
Sent: Thursday, September 21, 2006 3:57 PM
To: users@maven.apache.org
Subje
Hello,
I tried to create a plugin in which I would like to acces dependencies
(not the dependencies from the project that use this plugin but only the
dependencies from this plugin).
I tried the following:
/**
* My Goal.
* @goal mygoal
*/
public class MyMojo extends AbstractMojo {
/
40 matches
Mail list logo
