jvanzyl 2004/06/05 22:52:30
Modified:maven-model build.sh
Log:
o generate the sources for the v3 model
o generate the sources for the v3 xpp3 reader/writer
both of these necessary in order to adapt the v3 POM into a v4 POM
so that m2 can slurp up v3 POMs to build m1 proj
jvanzyl 2004/06/05 22:50:24
Modified:maven-model maven.mdo
Log:
o tweak the model for v3 and v4 generation
Revision ChangesPath
1.34 +4 -4 maven-components/maven-model/maven.mdo
Index: maven.mdo
jvanzyl 2004/06/05 22:26:37
Modified:maven-model maven.mdo
Log:
o give 3.0.0 Branch.tag a version.
Revision ChangesPath
1.33 +2 -0 maven-components/maven-model/maven.mdo
Index: maven.mdo
===
jvanzyl 2004/06/05 21:49:37
Modified:maven-model build.sh
Log:
o nuke the target directory
Revision ChangesPath
1.7 +2 -0 maven-components/maven-model/build.sh
Index: build.sh
===
RCS file
jvanzyl 2004/06/05 21:01:54
Modified:maven-core/docs/apt bugs.apt
Log:
Revision ChangesPath
1.2 +1 -1 maven-components/maven-core/docs/apt/bugs.apt
Index: bugs.apt
===
RCS file: /home/cvs
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1309
Here is an overview of the issue:
-
Key:
brett 2004/06/05 20:06:45
Modified:src/java/org/apache/maven/repository Tag: MAVEN-1_0-BRANCH
AbstractArtifact.java
Log:
PR: MAVEN-1309
Submitted by: Jerome Lacoste
Reviewed by: Brett Porter
cleanup
Revision ChangesPath
No
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPMULTIPROJECT-29
Here is an overview of the issue:
-
brett 2004/06/05 20:02:14
Modified:multiproject project.xml
Log:
PR: MPMULTIPROJECT-29
wrong JIRA link
Revision ChangesPath
1.27 +1 -1 maven-plugins/multiproject/project.xml
Index: project.xml
===
brett 2004/06/05 19:57:26
Modified:xdoc/src/main/org/apache/maven DescribedDependency.java
Log:
PR: MPXDOC-107
Submitted By: Jerome Lacoste
cleanup
Revision ChangesPath
1.4 +3 -3
maven-plugins/xdoc/src/main/org/apache/maven/DescribedDependency.java
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Sat, 5 Jun 2004 10:51 PM
applied
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-107
Here is an overview of the issue:
-
jvanzyl 2004/06/05 18:47:46
Added: maven-core/docs/apt bugs.apt
maven-core/xdocs navigation.xml
Log:
Revision ChangesPath
1.1 maven-components/maven-core/docs/apt/bugs.apt
Index: bugs.apt
==
jvanzyl 2004/06/05 18:38:30
Modified:maven-core/docs/apt alpha-release-criteria.apt
configuration-management.apt plugins.apt
Added: maven-core/docs/apt index.apt install.apt
Log:
o crappy first batch of doco
Revision ChangesPath
1.5 +
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Sat, 5 Jun 2004 9:30 PM
cool - thanks for letting us know
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1261
Here is an overvie
This is done now. HEAD of maven-jelly-tags is the place to patch.
Henning P. Schmiedehausen wrote:
Brett Porter <[EMAIL PROTECTED]> writes:
--_=_NextPart_001_01C44375.89CA3B82
Content-Type: text/plain
maven-jelly-tags is intended to be moved out of the maven tree and into a
new subpr
Gilles,
Is this an issue you get when you run Maven or only when you utilise the
code in Mevenide?
Thanks,
Brett
Gilles Dodinet wrote:
hi-
while working on mevenide, i experiment a strange behaviour : i
unmarshall the pom with xpp3, then set the context through a call to
project.setContext(..),
All on the branch for now if it belongs in Maven 1.0. Will be merged to
trunk again for Maven 1.0 and patches will automatically be applied there.
Jerome Lacoste wrote:
Hi,
I've made small cleanup patches for maven-1.0.
I've made them on the branch version. Should I:
- make them on the trunc inst
The following issue has been updated:
Updater: Jerome Lacoste (mailto:[EMAIL PROTECTED])
Date: Sat, 5 Jun 2004 6:22 PM
Comment:
Patch that applies the proposed project.xml to the integrate.xml.
Changes:
Attachment changed to patch.MAVEN-1208.txt
The following issue has been updated:
Updater: Jerome Lacoste (mailto:[EMAIL PROTECTED])
Date: Sat, 5 Jun 2004 5:58 PM
Comment:
- remove unnecessary assignment
- use a single return call
Changes:
Attachment changed to patch_MPXDOC-107.txt
---
jvanzyl 2004/06/05 14:58:24
Modified:maven-core/docs/apt alpha-release-criteria.apt
Log:
Revision ChangesPath
1.4 +1 -0 maven-components/maven-core/docs/apt/alpha-release-criteria.apt
Index: alpha-release-criteria.apt
===
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-107
Here is an overview of the issue:
-
Key:
jvanzyl 2004/06/05 05:47:50
Modified:maven-core/docs/apt alpha-release-criteria.apt
Log:
Revision ChangesPath
1.3 +6 -3 maven-components/maven-core/docs/apt/alpha-release-criteria.apt
Index: alpha-release-criteria.apt
===
Gilles Dodinet wrote:
however if i use jar override
(maven.jar.myproject=lib/myproject-${pom.currentVersion}.jar), a call
to myArtifact.getPath() returns this :
[prepend is correctly set]/lib/myproject-.jar (i.e. pom.currentVersion
is not resolved)
here is a bit more details. if i declare :
to
The way is was coded initially was making it very difficult to integrate
it with Maven. Maybe it has changed.
I agree that the idea of Jester is excellent and that it would be nice
to have a Maven plugin for it (but I fear it's still not very
build-friendly).
-Vincent
> -Original Message
24 matches
Mail list logo
