+1
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Vincent Siveton
Sent: Monday, March 10, 2008 7:53 AM
To: Maven Developers List
Subject: [Vote] Release Maven Plugin Tools 2.4 projects (take 3)
Hi,
It s again me :) I would like to release (again) the Ma
+1
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Monday, March 10, 2008 7:52 PM
To: Maven Developers List
Subject: [VOTE] Release maven-shared-components parent 9
Hi
To get the latest version of maven-source-plugin into our toolchain, I'd
like to release the s
Hi,
In r636143, I removed testing modules due to [1] and in r636154, I
added missing modules.
+1
Cheers,
Vincent
[1]
http://www.nabble.com/-proposal--Plugin-tools-and-shared-reorganization-td15916254s177.html
2008/3/10, Dennis Lundberg <[EMAIL PROTECTED]>:
> Hi
>
> To get the latest version
Hi,
I finished the move in r636149. Waiting for MPA-110.
Snapshots are deployed.
Cheers,
Vincent
2008/3/8, Vincent Siveton <[EMAIL PROTECTED]>:
> Hi,
>
> Yes. The Jira projects will be:
> * plugintools: MPLUGIN (or MPA-107 if someone think it will be better)
> * testingtools: see MPA-110
>
>
Yeah, I noticed this on some others too. I'm going to have a go at
getting this all in line now.
- Brett
On 12/03/2008, at 8:26 AM, Vincent Siveton wrote:
Hi Brett,
Could you reduce the dir names for
mng-3341-metadataUpdatedFromDeploymentRepository?
I am unable to do an update on windows .
I for one would like to see some design docs on the various changes so
we can grok them. I'm not sure rolling everything out is really what we
need at this point.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 11, 2008 6:15 PM
To: Maven Developers List
That's completely true. I've implemented a new extension mechanism
with little or no documentation in the wiki or on the developers'
list. I was just about the only one committing on trunk at the time,
I was pretty careful to avoid bugs with this new implementation (and
made it number one p
Hi,
I noticed that Maven is using junit:3.8.1 quite everywhere for its tests
although a later maintenance release of the 3.x line exists with
junit:3.8.2. Is there a known issue with 3.8.2 that makes one stick to
3.8.1?
Benjamin
-
Hi Brett,
Could you reduce the dir names for
mng-3341-metadataUpdatedFromDeploymentRepository?
I am unable to do an update on windows ...
Thanks.
Vincent
2008/3/5, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> Author: brett
> Date: Wed Mar 5 18:35:59 2008
> New Revision: 634131
>
> URL: http://
Additionally Igor, who's working on m2eclipse, has also done a bunch
of classloading magic with Plexus and OSGi stuff specifically so when
you write something up I'll make sure he and Dain comment. Dain and
Igor both have classloaders that have modeled this to some extent.
On 11-Mar-08, at
On 11-Mar-08, at 9:55 AM, John Casey wrote:
On Mar 11, 2008, at 11:26 AM, Jason van Zyl wrote:
On 11-Mar-08, at 8:09 AM, John Casey wrote:
I can see solving this in a generalized extension mechanism for
Plexus - which is different from a plugin situation, since plugins
are assumed to b
I'll prepare a formal proposal on the wiki, and produce a proof-of-
concept on a branch to aid this discussion. I'll need to get Dain and
anyone else with OSGi or related experience to look this over,
though, since I'd be willing to bet that applications need to have
the ability to manage th
On 11-Mar-08, at 8:39 AM, John Casey wrote:
On Mar 11, 2008, at 10:37 AM, Jason van Zyl wrote:
The experiment that this mechanism works must be done at the
Classworlds level first.
Can you please provide some reasoning why this is an absolute,
rather than just making an assertion?
Wh
On Mar 11, 2008, at 11:26 AM, Jason van Zyl wrote:
On 11-Mar-08, at 8:09 AM, John Casey wrote:
I can see solving this in a generalized extension mechanism for
Plexus - which is different from a plugin situation, since plugins
are assumed to be leaf nodes of the classloader hierarchy, and
On 11-Mar-08, at 8:09 AM, John Casey wrote:
I can see solving this in a generalized extension mechanism for
Plexus - which is different from a plugin situation, since plugins
are assumed to be leaf nodes of the classloader hierarchy, and are
therefore simpler to manage - but not for ClassW
On Mar 11, 2008, at 10:37 AM, Jason van Zyl wrote:
The experiment that this mechanism works must be done at the
Classworlds level first.
Can you please provide some reasoning why this is an absolute, rather
than just making an assertion?
That we have enough information to mimic what nee
The experiment that this mechanism works must be done at the
Classworlds level first.
That we have enough information to mimic what need there alone, I
certainly agree with you but that can be closely modeled before we
start tearing about the internals of Maven. The source of information
same question but for writing POMs. MavenXpp3Writer writes empty pom.xml for
unknown reason.
--
View this message in context:
http://www.nabble.com/Reading-pom.xml-in-Java-tp9352387s177p15976681.html
Sent from the Maven Developers mailing list archive at Nabble.com.
---
+1
-john
On Mar 10, 2008, at 7:51 PM, Dennis Lundberg wrote:
Hi
To get the latest version of maven-source-plugin into our
toolchain, I'd
like to release the shared components parent r635758 as version 9.
A site.xml has been added in this release.
Source:
https://svn.apache.org/viewvc/ma
I can see solving this in a generalized extension mechanism for
Plexus - which is different from a plugin situation, since plugins
are assumed to be leaf nodes of the classloader hierarchy, and are
therefore simpler to manage - but not for ClassWorlds. Milos is
completely correct on this on
subj. tried to read a valid POM with MavenXpp3Reader and write it and got the
same result. is there any special requirements to be able to write with this
guy?
--
View this message in context:
http://www.nabble.com/MavenXpp3Writer-writes-an-empty-pom.xml--tp15976506s177p15976506.html
Sent from t
Hi,
I tested the helpmojo goal.
It worked fine but has some flaws that could be improved.
- the goal should generate an aggregated mojo
- the goal should generate a non project requirement mojo.
I don't have tested the remaining of the tools.
So i am -0 (Committer vote = non binding).
Please do
i'm not convinced it can be solved on the classworlds level alone. The
import of single packages needs to be done for a whole tree of jars
that the extension depends on. And it needs to be defined in one place
and that is the extension jar. The classworlds-internal solution
doesn't have any idea ab
+1
-Lukas
Vincent Siveton wrote:
Hi,
It s again me :) I would like to release (again) the Maven Plugin
Tools projects:
* maven-plugin-plugin-2.4
* maven-plugin-tools-beanshell-2.4
* maven-plugin-tools-java-2.4
* maven-plugin-tools-2.4
* maven-plugin-tools-javadoc-2.4
* maven-plugin-tools-ant-
+1
-Lukas
Dennis Lundberg wrote:
Hi
To get the latest version of maven-source-plugin into our toolchain, I'd
like to release the shared components parent r635758 as version 9. A
site.xml has been added in this release.
Source:
https://svn.apache.org/viewvc/maven/shared/trunk/pom.xml?r1=5873
+1
-Lukas
Brian E. Fox wrote:
It's time to release the next Javadoc plugin. Besides the fixes listed
below, the most important change is the reverting of javadoc acting as
an aggregator. This caused most users tons of grief during releases. The
issue for this is MJAVADOC-137 (reverted MJAVADOC
+1
--
Olivier
2008/3/11, Dennis Lundberg <[EMAIL PROTECTED]>:
> Hi
>
> To get the latest version of maven-source-plugin into our toolchain, I'd
> like to release the shared components parent r635758 as version 9. A
> site.xml has been added in this release.
>
> Source:
>
> https://svn.apache
27 matches
Mail list logo
