This looks like a user question to me. Try to provide more information to
us...@maven.apache.org.
On Tue, Dec 8, 2009 at 12:30 AM, wrote:
>
> Hello Team,
>Please help me in the below problem. I am trying to build the
> project, while executing the command "mvn clean install" I am gettin
Hello devs,
A long time ago I was once a committer on Apache Maven. However as time
passed, life happened elsewhere. Despite this I have been programming in
Java for the past 10 years or so and on virtually every project of mine
since Maven 1.0.2 I had the opportunity to use Maven for my build tas
Hello Team,
Please help me in the below problem. I am trying to build the
project, while executing the command "mvn clean install" I am getting
below error.
I have attached screen shot of repository files, what I have in .m2
folder.
**
use this link as example
http://svn.codehaus.org/mojo/tags/dita-maven-plugin-1.0-beta-1/src/main/java/org/codehaus/mojo/dita/AbstractDitaMojo.java
-Dan
2009/12/7 Barış Erdemir :
> Hello,
> I am trying to resolve transitive dependencies of my project. I need a list
> of all dependencies.
>
> I a
I agree to fix the behavior like you propose Paul.
It will reduce probably a little bit current performances but if it solves
the case explained by Tamas, why not ...
On Mon, Dec 7, 2009 at 4:01 PM, Paul Gier wrote:
> It seems that the copyFileIfModified implementation should be changed.
> Sin
ok. I don't know enough GIT and DSCMs.
I understand that many people want to work on various branches but I find
that dangerous if you kkep the same version.
What happens if you deploy SNAPSHOTs binairies in a repository to do
continuous integration ?
About your problem of optimization, I could un
It seems that the copyFileIfModified implementation should be changed. Since
currently it only checks if the source timestamp is newer. Maybe this should be
changed to check for the timestamps not equal (and maybe size not equal also)
instead of just a newer timestamp. That would allow the op
Okay, let's put it this way:
are you saying that all the different GIT reposes out there containing
"project A" mirrors should have different versions? Who will coordinate
those?
It's somehow incompatible with Git (and probably any other distributed SCM)
in very fundamental way
~t~
On Mon,
...
"Renaming" (changing GAVs of modules, maybe a LOT of them) is PITA in this
case, IMHO.
...
mvn versions:set -DnewVersion=A.B.C-optim-SNAPSHOT
And it's done ?
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
2009/12/7 Tamás Cser
Thanks, fixed, build passes in both maven 2 and 3.
Regards,
Stevo.
On Mon, Dec 7, 2009 at 2:36 PM, Benjamin Bentmann wrote:
> Stevo Slavić wrote:
>
> It seems 3.0-alpha-5 is not compatible with current 2.0-alpha-4 version of
>> maven-archetype-plugin - archetype:create-from-project mojo create
Well, how about a "feature branch" (short lived branches)? Or you modify all
the modules to have different GAV upon branch? This is kinda nonsense to me,
since I branch it to do some feature that I know will get back into trunk.
"Renaming" (changing GAVs of modules, maybe a LOT of them) is PITA in
You have the same version in 2 branches in a project ?
For me it is a bad practice
Each branch has it own version to avoid those sort of conflict.
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
2009/12/7 Tamás Cservenák
> Hi the
Hi there,
this is mainly about this issue:
http://jira.codehaus.org/browse/MNG-4368
It caused a lot of grief (and lost hours) to me, until I figured what
happens on me.
IMHO, no "optimization" like this should be done against local repository.
Please undo it.
Thanks,
~t~
Hello,
I am trying to resolve transitive dependencies of my project. I need a list of
all dependencies.
I am using :
/**
* @parameter expression="${dependencies}"
default-value="${project.dependencies}"
*/
private ArrayList depende
Stevo Slavić wrote:
It seems 3.0-alpha-5 is not compatible with current 2.0-alpha-4 version of
maven-archetype-plugin - archetype:create-from-project mojo creates
archetype project with packaging maven-archetype, but that packaging seems
not to be supported by / valid for 3.0-alpha-5
Try runni
Hello Maven developers,
It seems 3.0-alpha-5 is not compatible with current 2.0-alpha-4 version of
maven-archetype-plugin - archetype:create-from-project mojo creates
archetype project with packaging maven-archetype, but that packaging seems
not to be supported by / valid for 3.0-alpha-5 (see
this
See my comment
http://jira.codehaus.org/browse/MASSEMBLY-416?focusedCommentId=201500&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_201500
Greetings
Grzegorz Slowikowski
Benjamin Bentmann wrote:
Hi,
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNot
17 matches
Mail list logo
