[ http://jira.codehaus.org/browse/MNG-897?page=comments#action_46844 ]
Davy Toch commented on MNG-897:
---
Question : shouldn't the POM files in antfile.zip have project as root
instead of model? If the latter works, then there is something fishy going on
in M2
[ http://jira.codehaus.org/browse/MAVEN-1697?page=comments#action_46560 ]
Davy Toch commented on MAVEN-1697:
--
It would already be an improvement if the Maven core would validate the POM by
default. This way an invalid POM would be detected at the start
Running an M2 goal in a directory not containing a POM generates confusing
messages.
Key: MNG-906
URL: http://jira.codehaus.org/browse/MNG-906
Project: Maven 2
Type: Improvement
Maven 1 should be able to retrieve dependencies from M2 repository.
---
Key: MAVEN-1694
URL: http://jira.codehaus.org/browse/MAVEN-1694
Project: Maven
Type: Improvement
Versions: 1.1-beta-2
[ http://jira.codehaus.org/browse/MPPOM-5?page=comments#action_46388 ]
Davy Toch commented on MPPOM-5:
---
The case can be closed.
I noticed that you now need a namespace http://maven.apache.org/POM/3.0.0; in
the root of the POM xml document. After adding this
[ http://jira.codehaus.org/browse/MPPOM-5?page=comments#action_46391 ]
Davy Toch commented on MPPOM-5:
---
I suppose the best solution is to modify the maven genapp plugin so it can
create Maven projects with v3.0.0 POM's (instead of adding a workaround in the
[ http://jira.codehaus.org/browse/MAVEN-1591?page=comments#action_45957 ]
Davy Toch commented on MAVEN-1591:
--
Regarding your question:
So, are you saying putting it in ${user.home}/build.properties works with
1.0.2?
Answer : yes (tested on Maven 1.0.2
[ http://jira.codehaus.org/browse/MAVEN-1649?page=comments#action_45795 ]
Davy Toch commented on MAVEN-1649:
--
It's not a Maven bug but a problem in ANT 1.6+. I had the same problem after
converting your script to ANT and running it.
The solution is simple
[ http://jira.codehaus.org/browse/MAVEN-1591?page=comments#action_45800 ]
Davy Toch commented on MAVEN-1591:
--
I think it's best to override maven.repo.local it in
${user.home}/build.properties. In this case the problem you indicated doesn't
appear.
On
[ http://jira.codehaus.org/browse/MAVEN-1644?page=comments#action_45377 ]
Davy Toch commented on MAVEN-1644:
--
Just a small correction : an error should be generated when no POM is found and
when no maven.xml is found, because it is sometimes useful to have
[ http://jira.codehaus.org/browse/MNG-666?page=comments#action_44984 ]
Davy Toch commented on MNG-666:
---
Can't you just ignore v3.0.x POM's when layout=legacy, meaning that you don't
need a POM for the dependency in order to retrieve it?
This was already the
[ http://jira.codehaus.org/browse/MPDIST-25?page=comments#action_44481 ]
Davy Toch commented on MPDIST-25:
-
You're correct that it's best not to include build.properties but instead a
kind of template file (BUILDING, build.properties.template, ...) in order
Usefulness install_repo.bat/install_repo.sh?
Key: MAVEN-1662
URL: http://jira.codehaus.org/browse/MAVEN-1662
Project: Maven
Type: Improvement
Components: cli
Versions: 1.1-beta-1
Environment: Not of
pom:validate doesn't work in maven-1.1-beta-1
-
Key: MPPOM-5
URL: http://jira.codehaus.org/browse/MPPOM-5
Project: maven-pom-plugin
Type: Bug
Versions: 1.4.1
Environment: Windows 2000, JDK 1.4.2_07
Reporter: Davy
Example more generic usage multiproject goals.
--
Key: MPMULTIPROJECT-55
URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-55
Project: maven-multiproject-plugin
Type: Improvement
Versions: 1.4.1
Environment: Not
Make jar plugin behaviour more consistent with e.g. ejb plugin behaviour.
-
Key: MPJAR-48
URL: http://jira.codehaus.org/browse/MPJAR-48
Project: maven-jar-plugin
Type: Improvement
Versions:
Goal dist:prepare-src-filesystem should also include build.properties in source
distribution.
-
Key: MPDIST-25
URL: http://jira.codehaus.org/browse/MPDIST-25
Project:
Allow distribution of artifact types other than jar (better solution then as
indicated at http://jira.codehaus.org/browse/MPDIST-13?).
--
Key: MPDIST-26
Problem DefaultModelValidator when getting model-3.0.0 POM.
---
Key: MNG-666
URL: http://jira.codehaus.org/browse/MNG-666
Project: Maven 2
Type: Bug
Components: maven-artifact-ant
Versions: 2.0-alpha-3
Exception parser must be on START_TAG or TEXT to read text in MavenXpp3Reader
for model-3.0.0 POMs.
-
Key: MNG-667
URL: http://jira.codehaus.org/browse/MNG-667
Project:
The Maven antlib task artifact:dependencies should also be able to retrieve
artifacts that don't have a POM.
--
Key: MNG-668
URL: http://jira.codehaus.org/browse/MNG-668
Running Maven in a directory not containing a POM file always results in 'Build
Successful'.
Key: MAVEN-1644
URL: http://jira.codehaus.org/browse/MAVEN-1644
Project: maven
Maven site 1.6.1 plugin always results in 'Build Successful'.
-
Key: MPSITE-28
URL: http://jira.codehaus.org/browse/MPSITE-28
Project: maven-site-plugin
Type: Bug
Components: plugin
Versions: 1.6.1
Maven functionality to download all dependencies for all plugins once.
--
Key: MAVEN-1597
URL: http://jira.codehaus.org/browse/MAVEN-1597
Project: maven
Type: Wish
Components: plugin manager
24 matches
Mail list logo
