Hi all,
I'm using maven with eclipse IDE. An interesting fonctionality of Eclipse (and much
IDE may do same) is the ability to
attach java sources to a jar. Using maven dependencies and maven eclipse plugin to
generate classpath does not set this
property.
Is they're some plan to add a new entr
Ok, after the discussion on the thread titled "[Proposal] Project
deliverables definition in POM", it seems we agree on adding a
element in the POM for now. As not everyone has answered, I'd like to
propose a vote for this. If it passes, I can implement it quickly.
Here's my +1
Thanks
-Vincent
Vincent Massol wrote:
Ok, after the discussion on the thread titled "[Proposal] Project
deliverables definition in POM", it seems we agree on adding a
element in the POM for now. As not everyone has answered, I'd like to
propose a vote for this. If it passes, I can implement it quickly.
Here's my
> -Original Message-
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> Sent: 13 November 2003 10:44
> To: Maven Developers List
> Subject: Re: [VOTE] Adding type element in POM
[snip]
>
> When any changes to POM will be introduced should we increment it to
> 4?
+1. The pom:validate sh
Vincent Massol wrote:
-Original Message-
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: 13 November 2003 10:44
To: Maven Developers List
Subject: Re: [VOTE] Adding type element in POM
[snip]
When any changes to POM will be introduced should we increment it to
4?
+1. T
Jason van Zyl wrote:
...
I would just like to avoid the complete arbitrary nature of the gump
descriptor when it comes things that are generated from a project.
In Centipede we use the Gump descriptor for the artifacts, and we
had the same need of having to extend it to specify the artifact type.
H
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1031
Here is an overview of the issue:
-
Michal Maczka wrote:
Other thinng I was thinking of is to introduce element
javadocUrl will point to URL when project's javadocs are accessible.
This can be used for liniking project's javadocs with javadocs of other
projects
(http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javadoc.html
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1032
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1033
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1034
Here is an overview of the issue:
-
Joakim Erdfelt wrote:
Michal Maczka wrote:
Other thinng I was thinking of is to introduce element
javadocUrl will point to URL when project's javadocs are accessible.
This can be used for liniking project's javadocs with javadocs of
other projects
(http://java.sun.com/j2se/1.4.2/docs/toold
On Thu, 2003-11-13 at 04:43, Michal Maczka wrote:
> Vincent Massol wrote:
>
> >Ok, after the discussion on the thread titled "[Proposal] Project
> >deliverables definition in POM", it seems we agree on adding a
> >element in the POM for now. As not everyone has answered, I'd like to
> >propose a
> We can make it without tag.
>
> For example it is just enough to put download URL of javamail to
> http://www.ibblio.org/maven/javamail/poms/javamail-1.1.pom
> and every project can profit from this.
>
> Anyway - I am _not_ proposing that we should drop tag.
Heh. *whew*.
But having the po
Erdfelt,
Also, if there is open discussion about changes to the pom, are there
plans to address any of the requests for project.xml changes in the
jira? (i have a personal interest in MAVEN-954, and would like to
see more meta-data in the elements. In a corporate
environment, phone number, dep
> >Also, if there is open discussion about changes to the pom, are there
> >plans to address any of the requests for project.xml changes in the
> >jira? (i have a personal interest in MAVEN-954, and would like to
> >see more meta-data in the elements. In a corporate
> >environment, phone number
Howdy,
I am starting to compare MAVEN_RC1_REFACTOR, MAVEN_RC2_UNSTABLE and HEAD
and having copies of the core plugins in each of those is really
annoying.
Could we move all of the plugins to maven-plugins and figure out a
simple way to pull in what we consider core plugins for the bootstrap?
Thi
jvanzyl 2003/11/13 07:28:55
Removed: src/plugins-build/ant Tag: MAVEN_RC1_REFACTOR .cvsignore
plugin.jelly plugin.properties project.properties
project.xml
src/plugins-build/ant/src/plugin-resources/templates Tag:
Hi,
I've implemented the new tag in the POM. See attached. I have
also added support to multiple version of the POM. Before committing I
wanted to get a green signal from you.
Thanks
-Vincent
maven-patch.zip
Description: Zip compressed data
-
On Thu, 2003-11-13 at 12:44, Vincent Massol wrote:
> Hi,
>
> I've implemented the new tag in the POM. See attached. I have
> also added support to multiple version of the POM. Before committing I
> wanted to get a green signal from you.
What does "support to multiple version of the POM" mean?
>
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1035
Here is an overview of the issue:
-
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 13 November 2003 19:41
> To: Maven Developers List
> Subject: Re: [PATCH] Implementing the new tag in POM
>
> On Thu, 2003-11-13 at 12:44, Vincent Massol wrote:
> > Hi,
> >
> > I've implemented the new tag in
vmassol 2003/11/13 12:14:37
Modified:.build-bootstrap.xml maven.xml
build-bootstrap-core.xml
src/java/org/apache/maven DefaultProjectUnmarshaller.java
DefaultProjectMarshaller.java
xdocs/reference proje
vmassol 2003/11/13 12:30:20
Modified:pom/xdocs changes.xml
pom plugin.jelly project.xml
Log:
Added support for validating different POM versions.
Revision ChangesPath
1.7 +5 -0 maven-plugins/pom/xdocs/changes.xml
Index: changes.xml
==
vmassol 2003/11/13 12:45:07
Modified:pom/xdocs changes.xml
pom plugin.jelly
Log:
Verify valid POM versions. Only "3" and "4" are currently allowed.
Revision ChangesPath
1.8 +3 -0 maven-plugins/pom/xdocs/changes.xml
Index: changes.xml
Hi,
I'd like to make a mandatory element in POM version 4. What do
you think? The reason is that I don't what the default can be if it's
not specified and if we want to have plugins that start using the
id/groupId/type elements, there must be a groupId defined.
Here's my +1
Thanks
-Vincent
--
On Thu, 2003-11-13 at 15:57, Vincent Massol wrote:
> Hi,
>
> I'd like to make a mandatory element in POM version 4. What do
> you think? The reason is that I don't what the default can be if it's
> not specified and if we want to have plugins that start using the
> id/groupId/type elements, there
+1 painful, but important..
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 13, 2003 10:05 PM
> To: Maven Developers List
> Subject: Re: [VOTE] Make groupId mandatory for POM version 4?
>
>
> On Thu, 2003-11-13 at 15:57, Vincent Massol wrot
vmassol 2003/11/13 13:17:53
Modified:src/xsd maven-project-4.xsd
Log:
Nuked the / elements. The version element was conflicting with
the newly renamed currentVersion element. We can always add the versions elements back
if need be (possibly with different names).
Revision Ch
Vincent Massol wrote:
Hi,
I'd like to make a mandatory element in POM version 4. What do
you think? The reason is that I don't what the default can be if it's
not specified and if we want to have plugins that start using the
id/groupId/type elements, there must be a groupId defined.
Here's my
vmassol 2003/11/13 14:11:55
Modified:src/java/org/apache/maven DefaultProjectUnmarshaller.java
DefaultProjectMarshaller.java
src/java/org/apache/maven/project Project.java
xdocschanges.xml
Log:
Added new mandatory element
vmassol 2003/11/13 14:12:51
Modified:src/xsd maven-project-4.xsd
Log:
Added new mandatory element
Revision ChangesPath
1.4 +1 -0 maven/src/xsd/maven-project-4.xsd
Index: maven-project-4.xsd
==
+1
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Friday, 14 November 2003 7:58 AM
> To: 'Maven Developers List'
> Subject: [VOTE] Make groupId mandatory for POM version 4?
>
>
> Hi,
>
> I'd like to make a mandatory element in POM version
> 4. What do y
Jason,
I think it would be better not to mess with it right now. But it's a fine
goal for a cleaner bootstrap - the bootstrap ant task can just pull down the
JARs from the repo.
As far as what is different between the original branch and the new RC2
branch, diffs probably aren't going to help. Wh
vmassol 2003/11/13 14:25:45
Modified:src/xsd maven-project-4.xsd
xdocschanges.xml
Log:
Made mandatory in POM version 4.
Revision ChangesPath
1.5 +1 -1 maven/src/xsd/maven-project-4.xsd
Index: maven-project-4.xsd
=
On Thu, 2003-11-13 at 17:24, Brett Porter wrote:
> Jason,
>
> I think it would be better not to mess with it right now. But it's a fine
> goal for a cleaner bootstrap - the bootstrap ant task can just pull down the
> JARs from the repo.
The bootstrap can just run the reactor in ../maven-plugins i
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 14 November 2003 00:01
> To: Maven Developers List
> Subject: RE: Moving all plugins to maven-plugins
>
> On Thu, 2003-11-13 at 17:24, Brett Porter wrote:
> > Jason,
> >
> > I think it would be better not to mes
> Are the memory leaks completely gone in RC2_UNSTABLE as they
> are in RC1_REFACTOR? If so then then that's a big cross
> section I won't look at.
I think there is still one leak in the project loading (caused by betwixt?)
but is very minor - a few kb per project I think.
I can rebuild all of m
On Thu, 2003-11-13 at 18:24, Brett Porter wrote:
> > Are the memory leaks completely gone in RC2_UNSTABLE as they
> > are in RC1_REFACTOR? If so then then that's a big cross
> > section I won't look at.
>
> I think there is still one leak in the project loading (caused by betwixt?)
> but is very
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1036
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Henri Tremblay (mailto:[EMAIL PROTECTED])
Date: Thu, 13 Nov 2003 6:18 PM
Comment:
Here is the fix. It's a modified version of the file currently available in the head
branch.
Changes:
Attachment changed to checkstyle.j
The following issue has been updated:
Updater: Henri Tremblay (mailto:[EMAIL PROTECTED])
Date: Thu, 13 Nov 2003 6:19 PM
Comment:
And here's the diff
Changes:
Attachment changed to diff.txt
-
For
+1 to fixing that
However what are the exact details of how it is to be fixed?
/
/ or (with weird : and + notation)
/ or (with : notation shorthand)
/
Whatever the solution, i'd prefer that the dependency definition and the
POM definition were equivalent.
What kind of deprecation
On Thu, 2003-11-13 at 21:08, Ben Walding wrote:
> +1 to fixing that
>
> However what are the exact details of how it is to be fixed?
>
> /
-1
> / or (with weird : and + notation)
-1
> / or (with : notation shorthand)
-1
The has to go away because this is something we will define
i
> What kind of deprecation period were you planning?
I would suggest that we don't finalise POM v4 until 1.1, and both v3 and v4
should be loadable. If we decide to remove v3 support in the future to
simplify it, that's probably a decision for the time.
It would be good if there were a stylesheet
> That's why I sent the patch... :-) It simply means that I've
> renamed maven-project.xsd in maven-project-3.xsd and added a
> maven-project-4.xsd. I've not sent the patch for the pom
> plugin but it checks the maven-project-${pom.pomVersion}.xsd file.
The documentation references the CVS repo
46 matches
Mail list logo
