Awesome, thanks. That means the new container works with everything now.
Jason.
On 12 Dec 06, at 12:35 AM 12 Dec 06, Brian E. Fox wrote:
Hi Jason,
The fix was easy because the new classworlds is much better than
the old
one. I don't have karma in maven-core so I attached the patch to
MNG-18
On 12/11/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
We are intentionally publishing the latest docs. (Okay, month-old by
now... where does the time go?) It was discussed on the list before
it happened, and was brought up again recently to make sure we're all
on the same page:
http://www.nabbl
Hi Jason,
The fix was easy because the new classworlds is much better than the old
one. I don't have karma in maven-core so I attached the patch to
MNG-1898. This patch works with both 2.0.4 and 2.1.
I also came across and patched a bug in the mvn.bat file:
http://jira.codehaus.org/browse/MNG-2699
On 11 Dec 06, at 10:25 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
What is the State resolver?
Dependency resolver. Basically a state machine that consumes OSGi
dependency information, determines what's missing and asks for more.
How the conditions are satisfied is up to the implementati
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 9:10 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
Jason van Zyl wrote:
So m2eclipse *does* depend upon the Maven embedder currently...and at
the moment there is no way to use the meta info in manifest.mf,
plugin.xml, (and read/changed in memory
In http://jira.codehaus.org/browse/MSUREFIREREP-6 someone requested
that a report-only goal get created to provide a workaround.
I've provided a patch that does that. Can someone apply and consider releasing?
Cheers
-
To unsub
On 11 Dec 06, at 9:10 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
Jason van Zyl wrote:
So m2eclipse *does* depend upon the Maven embedder currently...and
at the moment there is no way to use the meta info in manifest.mf,
plugin.xml, (and read/changed in memory in the PDE) to 'build' a
pom
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 8:22 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 7:13 PM 11 Dec 06, Scott Lewis wrote:
Hi Tom,
A quick comment: with Eclipse, version dependency requirements can
be specified at the level of individual
On 11 Dec 06, at 8:22 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 7:13 PM 11 Dec 06, Scott Lewis wrote:
Hi Tom,
A quick comment: with Eclipse, version dependency requirements
can be specified at the level of individual bundles/plugins and
at the lev
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 7:13 PM 11 Dec 06, Scott Lewis wrote:
Hi Tom,
A quick comment: with Eclipse, version dependency requirements can
be specified at the level of individual bundles/plugins and at the
level of features (sets of plugins).
This is described in th
On 11 Dec 06, at 7:13 PM 11 Dec 06, Scott Lewis wrote:
Hi Tom,
A quick comment: with Eclipse, version dependency requirements can
be specified at the level of individual bundles/plugins and at the
level of features (sets of plugins).
This is described in that document under these subsect
Hi Tom,
Tom Huybrechts wrote:
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
On 12/11/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
> In any Eclipse install, each Import-Package is provided by at least
> one bundle, and you can make a POM dependency on that bundle. It is
> quite easy
Hi Fabrizio,
Fabrizio Giustina wrote:
On 12/11/06, Scott Lewis <[EMAIL PROTECTED]> wrote:
There is a (recently proposed/adopted) version numbering spec that
describes using the qualifier segment to distinguish between release,
integration, and nightly builds. See here for the details:
I can
+1 for all the plugins
--
Regards,
Garvin LeClaire
[EMAIL PROTECTED]
On 12/11/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Joakim Erdfelt wrote:
> After a chat with Jason about the new release process / staging / etc...
> I feel it is time to get a release out for the following plugins.
>
Joakim Erdfelt wrote:
After a chat with Jason about the new release process / staging / etc...
I feel it is time to get a release out for the following plugins.
maven-gpg-plugin 1.0
maven-javadoc-plugin 2.2
+1
maven-site-plugin 2.0
maven-source-plugin 2.0.2
+1
But there is one unresolved is
On 11 Dec 06, at 6:36 PM 11 Dec 06, Joakim Erdfelt wrote:
Real world html parsing is not easy.
I would rather not create yet another implementation.
We went from nekohtml (with it's xerces requirement) at 8.1MB to jtidy
(with jre/jaxp support) at 135KB.
I think this is an adequate reduction.
Bes
Real world html parsing is not easy.
I would rather not create yet another implementation.
We went from nekohtml (with it's xerces requirement) at 8.1MB to jtidy
(with jre/jaxp support) at 135KB.
I think this is an adequate reduction.
Best bang for the buck, etc...
- Joakim
Brett Porter wrote:
>
Running org.apache.maven.plugin.eclipse.RadPluginTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 100.971 sec
Running org.apache.maven.plugin.eclipse.EclipsePluginTest
Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 82.783 sec
I'm assuming the reason it is s
On 11 Dec 06, at 6:13 PM 11 Dec 06, Barrie Treloar wrote:
On 12/12/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 11 Dec 06, at 5:55 PM 11 Dec 06, Barrie Treloar wrote:
> Is there a JIRA available for sandboxed plugins?
>
If there's something very active in the sandbox I can create a JIRA
On 12/12/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 11 Dec 06, at 5:55 PM 11 Dec 06, Barrie Treloar wrote:
> Is there a JIRA available for sandboxed plugins?
>
If there's something very active in the sandbox I can create a JIRA
project.
It was maven-plugin-testing-tools which I think wi
On 11 Dec 06, at 5:55 PM 11 Dec 06, Barrie Treloar wrote:
Is there a JIRA available for sandboxed plugins?
If there's something very active in the sandbox I can create a JIRA
project.
Jason.
-
To unsubscribe, e-mail: [
On 12/12/06, Barrie Treloar <[EMAIL PROTECTED]> wrote:
Is there a JIRA available for sandboxed plugins?
Found it in http://jira.codehaus.org/browse/MNG under components Sandbox.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Is there a JIRA available for sandboxed plugins?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The test cases for DefaultInvokerTest.testBuildShouldSucceed and
DefaultInvokerTest.testBuildShouldFail are identical, except for the
last assert.
testBuildShouldSucceed() correctly works, so since the
result.getExitCode() is 0, testBuildShouldFail() can never succeed.
Any ideas what testBuildSh
That reminds me of something...
http://jira.codehaus.org/browse/MPCLOVER-54
Never got any feedback though, so I don't know if/how it was resolved.
-Lukas
Brett Porter wrote:
I can give you an account if you want to try, I've no inclination to
myself :)
Doesn't -Djava.awt.headless=true wor
On 11 Dec 06, at 5:20 PM 11 Dec 06, Wendy Smoak wrote:
On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
Yes (pointed this out originally last week) - for example:
http://maven.apache.org/plugins/maven-ear-plugin/
modules.html#harModule
(only available in v2.3-SNAPSHOT) and
http://mave
On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
Yes (pointed this out originally last week) - for example:
http://maven.apache.org/plugins/maven-ear-plugin/modules.html#harModule
(only available in v2.3-SNAPSHOT) and
http://maven.apache.org/plugins/maven-eclipse-plugin/make-artifacts-mojo
> > did you finally remove the usage of a parent pom for install-files?
> > that made it easier to add information to all the artifacts than
> > regenerate all poms
[disussion del]
err, this appears to be out of context and I am struggling to work out
what is being discussed.
Are there links to
Well, it's a blocker on upgrading it in Maven, that's all, until one
thing is sorted out. I wouldn't think any mangling should be truly
necessary - we should be able to put the wagon implementation stuff
in a separate classloader rather than the one the plugins derive from
anyway. But it's
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
On 12/11/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
> In any Eclipse install, each Import-Package is provided by at least
> one bundle, and you can make a POM dependency on that bundle. It is
> quite easy to implement this by feeding al
Brett Porter wrote:
I don't understand this. Is there a field in the documentation that is
only available in the snapshot and not documented as such?
Yes (pointed this out originally last week) - for example:
http://maven.apache.org/plugins/maven-ear-plugin/modules.html#harModule
(only avail
On 11 Dec 06, at 3:59 PM 11 Dec 06, Brett Porter wrote:
Hi,
Can I please ask that any plugin votes (and other votes) contain an
SVN rev# that we are voting on? We agreed some time back that that
was a requirement and that a vote was reset if anything changed
after getting burned by somet
On 11 Dec 06, at 4:25 PM 11 Dec 06, Brett Porter wrote:
It's not just size that matters...
Anything used from wagon-http-lightweight will currently be
distributed in the core. That means that plugins will be forced to
use the version you distribute. I could see this as a problem for
jtidy
On 12/11/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
In any Eclipse install, each Import-Package is provided by at least
one bundle, and you can make a POM dependency on that bundle. It is
quite easy to implement this by feeding all bundles in the install
into the resolver and having it calcula
- last but not least: package-level dependencies can't be handled by
maven as is. IMHO this could not be a big problem at the moment: you
could be forced to manually add transitive dependencies but at the
end it doesn't really hurt (BTW, in eclipse builds package-level
dependencies are very rare
Edwin,
You should list who submitted the fix in the comment.
- Brett
On 11/12/2006, at 7:30 PM, [EMAIL PROTECTED] wrote:
Author: epunzalan
Date: Mon Dec 11 00:30:32 2006
New Revision: 485552
URL: http://svn.apache.org/viewvc?view=rev&rev=485552
Log:
PR: MRM-247
Add timestamp when the indexe
It's not just size that matters...
Anything used from wagon-http-lightweight will currently be
distributed in the core. That means that plugins will be forced to
use the version you distribute. I could see this as a problem for jtidy.
Is there anyway you can do this with just JDK 1.4 method
On 12/11/06, Scott Lewis <[EMAIL PROTECTED]> wrote:
There is a (recently proposed/adopted) version numbering spec that
describes using the qualifier segment to distinguish between release,
integration, and nightly builds. See here for the details:
I can see that the docs outline rules in choos
http://jira.codehaus.org/browse/MNG-2696
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 10, 2006 11:21 PM
To: Maven Developers List
Subject: Re: maven-cli assembly exceptions
Fair general point, but I think someone should look into the issue with
Hi,
Are you seeing any other startup errors in the Tomcat logs/console?
BTW, have you seen this thread?
http://www.nabble.com/RE:-Deploy-trunk-on-tomcat-t2625572.html
Cheers,
Rahul
Stephen Pietrowicz wrote:
Hi,
I've checked out the latest version of Continuum from the source tree,
built i
/export/home/continuum/public_html/maven-1.x/builds
I'll give you group admin rights so you can add an ant project. But
that's another bug :)
On 11/12/2006, at 9:07 PM, Arnaud HERITIER wrote:
Hi,
I can edit it and I changed the scm url (even if I received a 500
error -
you already op
I can give you an account if you want to try, I've no inclination to
myself :)
Doesn't -Djava.awt.headless=true work? This seems like a serious
oversight in the clover plugin. Plenty must be using this headless.
- Brett
On 11/12/2006, at 9:18 PM, Arnaud HERITIER wrote:
I have an error w
Hi,
Can I please ask that any plugin votes (and other votes) contain an
SVN rev# that we are voting on? We agreed some time back that that
was a requirement and that a vote was reset if anything changed after
getting burned by something sneaking in. It seems to have been
curtailed recentl
On 12/12/2006, at 6:24 AM, Graham Leggett wrote:
When I asked as the the status of the ear plugin last week, the
answer was that it was pretty much ready. I asked for a vote, but
none came - probably because people were busy this time of year, so
being proactive and knowing the drill I cal
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
On 12/11/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> did you finally remove the usage of a parent pom for install-files?
> that made it easier to add information to all the artifacts than
> regenerate all poms
yes, at the moment no pa
On 12/9/06, Jesse McConnell <[EMAIL PROTECTED]> wrote:
continuum 1.0.3 has been out for a while now and there have been a lot
of tangible improvements that we should get into peoples hands in the
form of the alpha releases. I figured with labeling of alpha we can
freely change the model if we ne
Hi Fabrizio,
A small clarification below
Fabrizio Giustina wrote:
Hi Graham
On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
These two features together, with some scripting and a place to host the
repository, is in theory all that would be needed to make eclipse jars
automatically avai
1&2 are fixed. I am waiting for Jason's instructions for 3.
Thanks,
Stéphane
On 12/11/06, Daniel Kulp <[EMAIL PROTECTED]> wrote:
-1
The normal set of issues:
1) pom.xml does not have the apache header
2) The rest of the files have the OLD apache header, not the new one required
as of Nov 1.
3
On 12/11/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
did you finally remove the usage of a parent pom for install-files?
that made it easier to add information to all the artifacts than
regenerate all poms
yes, at the moment no parent is used. It's a minor change, I could
turn it on before th
Dan,
Yes. Please keep your vote till I apply Jason's stuff. I'll make sure
to put the right license in the source file and I'll deploy a new
snapshot.
Thanks for checking this.
Regards,
Stéphane
On 12/11/06, Daniel Kulp <[EMAIL PROTECTED]> wrote:
-1
The normal set of issues:
1) pom.xml does
Hi Graham
On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
These two features together, with some scripting and a place to host the
repository, is in theory all that would be needed to make eclipse jars
automatically available to maven users.
I think that at the moment having a manually-
-1
The normal set of issues:
1) pom.xml does not have the apache header
2) The rest of the files have the OLD apache header, not the new one required
as of Nov 1.
3) No LICENSE of NOTICE file in the resulting jar (may need to wait for
Jason's changes)
Dan
On Monday 11 December 2006 14:34, St
Scott Lewis is already helping with eclipse-maven relationship
This is a proposal for a new project at Eclipse foundation that will
increase this collaboration http://www.eclipse.org/proposals/kepler/
On 12/11/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
Please consider http://jira.codehaus.org
Please consider http://jira.codehaus.org/browse/MECLIPSE-201 if you
want to deploy these artifacts to central. Once the POMs are out
released, they can't be changed untill there is a new release.
Would'nt it be a good idea to try to involve people from Eclipse in this ?
Tom
On 12/11/06, Graham
+1
fabrizio
On 12/11/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
Hi,
I'd like to release maven-ear-plugin 2.3 [1]. This release includes:
* Support of classifier
* Automatic generation of JBoss specific deployment descriptor (jboss-app.xml)
* Support of exploded modules
* File name mapping
Graham,
On Monday 11 December 2006 14:24, Graham Leggett wrote:
> Jason van Zyl wrote:
> > Asking for a vote means that people can make preparations and actually
> > figure out what's going to be done for the next release. Create a
> > roadmap, field help and plan toward making something release
the idea is to setup a repository with eclipse artifacts generated
from install-files and sync org.eclipse.* from there to the central
maven repo, not to create new things in ibiblio
On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
Carlos Sanchez wrote:
> that sounds good and can be setup
Hi,
I'd like to release maven-ear-plugin 2.3 [1]. This release includes:
* Support of classifier
* Automatic generation of JBoss specific deployment descriptor (jboss-app.xml)
* Support of exploded modules
* File name mappings to avoid clashes
* Support of HAR files
* Bug fixes
The snapshot is
Carlos Sanchez wrote:
that sounds good and can be setup as if it were another mirror, the
important questions
who will volunteer to do it?
is enough people asking for them that it makes sense?
In theory, keeping such a repository up to date could be done from a
zone, and it's not a problem fo
Jason van Zyl wrote:
Asking for a vote means that people can make preparations and actually
figure out what's going to be done for the next release. Create a
roadmap, field help and plan toward making something release worthy.
When all that is done, the work has been looked over and it is felt
did you finally remove the usage of a parent pom for install-files?
that made it easier to add information to all the artifacts than
regenerate all poms
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
I was already planning to start a vote, so a +1 from me since we
already waited too l
Is it expected that the Maven2 site plugin will eventually configure
certain reports as "external links", opening them in a new browser
window, just as the Maven1 xdoc plugin did?
I searched JIRA and Google and couldn't find any references, but I
wanted to post here before opening a new feature re
the tagBase isn't required when we use the standard branches/trunk/tags
Emmanuel
[EMAIL PROTECTED] a écrit :
Author: jvanzyl
Date: Mon Dec 11 10:55:00 2006
New Revision: 485811
URL: http://svn.apache.org/viewvc?view=rev&rev=485811
Log: (empty)
Modified:
maven/release/trunk/pom.xml
Modifi
+1
Stéphane
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
I was already planning to start a vote, so a +1 from me since we
already waited too long and added so many changes and enhancements
lately.
Anyway, as usual there are a couple of things that need to be done before:
- license
Hi,
This is in response to John's email about integration testing, some
notes that I've taken while trying to clean up the integration
testing, and some suggestions about where we go from here with
respect to integration testing. You will see from the list below that
there are many proble
I am +1 with Jason.
Graham, I understand the need and will call for a vote later today. I
am not sure I'll be able to do it this week though since I am at
Javapolis the whole week.
Cheers,
Stéphane
On 12/11/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 11 Dec 06, at 12:26 PM 11 Dec 06, G
[ ] Top Left
[ x ] Top Right
[ ] Lower Left
[ ] Lower Right
--
Regards,
Garvin LeClaire
[EMAIL PROTECTED]
On 11 Dec 06, at 12:26 PM 11 Dec 06, Graham Leggett wrote:
On Mon, December 11, 2006 7:12 pm, Jason van Zyl wrote:
You didn't ask for a release, you tried to call a vote. Very
different things.
Explain how these are different?
Asking for a vote means that people can make preparations and
On Mon, December 11, 2006 7:12 pm, Jason van Zyl wrote:
> You didn't ask for a release, you tried to call a vote. Very
> different things.
Explain how these are different?
> That's an example of how it works and how
> you can participate. Do some work, get a say. It's pretty standard
> Apache st
that sounds good and can be setup as if it were another mirror, the
important questions
who will volunteer to do it?
is enough people asking for them that it makes sense?
On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
Hi all,
I have seen some effort scattered here and there for providin
On 11 Dec 06, at 11:45 AM 11 Dec 06, Graham Leggett wrote:
On Mon, December 11, 2006 6:10 pm, Jason van Zyl wrote:
Some who is not developing the code cannot call a vote. At least one
that's going to actually be voted on. I can't walk into the httpd
mailing list and ask for a release of httpd
your wish is etc...
plexus-utils 1.4-alpha-1 released :)
Andy
Fabrizio Giustina wrote:
Thanks Jason,
could I ask you to take care of the plexus-utils stuff? Should be the
only non-maven dependency needed for this release, I could take care
of the rest... the plexus release should be solved inde
To be fair to Graham, I think it would be reasonable to go to the
mailing list and say "There hasn't been an httpd release in 6 months.
Would you guys consider releasing it sometime soon?" I assume that's
the intent of his original message.
mike
On 12/11/06, Jason van Zyl <[EMAIL PROTECTED]> w
On Mon, December 11, 2006 6:10 pm, Jason van Zyl wrote:
> Some who is not developing the code cannot call a vote. At least one
> that's going to actually be voted on. I can't walk into the httpd
> mailing list and ask for a release of httpd. Come on.
I am not aware of any barrier stopping anybody
On 11 Dec 06, at 10:54 AM 11 Dec 06, Graham Leggett wrote:
On Mon, December 11, 2006 3:37 pm, Jason van Zyl wrote:
You cannot start a vote unless you are a committer.
It does? I could not find anything like this at
http://www.apache.org/foundation/voting.html. Binding votes are
cast by
PM
On Mon, December 11, 2006 3:37 pm, Jason van Zyl wrote:
> You cannot start a vote unless you are a committer.
It does? I could not find anything like this at
http://www.apache.org/foundation/voting.html. Binding votes are cast by
PMC members as I understand (I am on the httpd PMC), but a call for
Hi all,
I have seen some effort scattered here and there for providing maven2
repositories containing the jars that make up the eclipse platform. It
would be great if an automated repository could be created that would keep
eclipse jars accessible to maven.
The eclipse:make-artifacts goal in the
I have not seen any issues with the JPackage Fedora
RPMs, and have been running with them for about 2
months now.
I just followed the instructions here:
http://fedoranews.org/mediawiki/index.php/JPackage_Java_for_FC4
They even let you easily switch between Java
implementation using an "Alternativ
If we fix all backward compat problems then there is no reason for
anyone to use a new plugin with an old release of maven...
The artifact plugin should be released for RC1, as it contains the fix
for MPARTIFACT-71 (the reject HostKey error), which was the only
blocking plugin issue we had in
On 12/11/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
It was needed, then I woke up the next morning and had a better way
to do it without requiring an upgrade.
cool, thanks for the clarification... you should sleep more :)
fabrizio
On 11 Dec 06, at 9:17 AM 11 Dec 06, Fabrizio Giustina wrote:
On 12/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Log:
o updating to released parent and fall back to released plexus-
archiver
Can I ask why a snapshot versions of plexus archiver was used before?
A new feature that I u
On 12/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Log:
o updating to released parent and fall back to released plexus-archiver
Can I ask why a snapshot versions of plexus archiver was used before?
When I see a dependency upgraded to a snapshot I assume there is
really a good valid reaso
Thanks Jason,
could I ask you to take care of the plexus-utils stuff? Should be the
only non-maven dependency needed for this release, I could take care
of the rest... the plexus release should be solved independently from
this vote.
fabrizio
On 12/11/06, Jason van Zyl <[EMAIL PROTECTED]> wrot
Then I'm getting some weird error from the clean plugin saying it
can't find the classes generated by modello. The FileSet.
Jason.
On 11 Dec 06, at 8:42 AM 11 Dec 06, Joakim Erdfelt wrote:
Definitely deployed.
(snip from archiva-webapp)
org.apache.maven.plugins
maven
+1
Go for it, I will help you release and move stuff. I question is far
from settled as to integration testing but the eclipse plugin release
needs to be made. I'll be doing nothing but releases from now until
the new year it seems so I can help you with anything related to m2.
Jason.
On
Definitely deployed.
(snip from archiva-webapp)
org.apache.maven.plugins
maven-clean-plugin
2.1.1
${basedir}/
derby.log
${ba
Jason van Zyl a écrit :
On 11 Dec 06, at 8:01 AM 11 Dec 06, Joakim Erdfelt wrote:
The fileset support in the clean plugin is most certainly deployed.
It is used heavily in continuum and archiva to cleanup after the
war:inplace overlay.
Deployed or released?
released, version 2.1.1
Jaso
You cannot start a vote unless you are a committer.
Jason.
On 11 Dec 06, at 4:08 AM 11 Dec 06, Graham Leggett wrote:
Hi all,
I would like to propose a release of the maven-ear-plugin.
Regards,
Graham
--
-
To unsubscribe,
On 11 Dec 06, at 8:01 AM 11 Dec 06, Joakim Erdfelt wrote:
The fileset support in the clean plugin is most certainly deployed.
It is used heavily in continuum and archiva to cleanup after the
war:inplace overlay.
Deployed or released?
Jason.
- Joakim
[EMAIL PROTECTED] wrote:
Author: jvanz
On 11 Dec 06, at 8:23 AM 11 Dec 06, Fabrizio Giustina wrote:
Ok, I think that for the maven-site-plugin the removal of the
dependency from maven 2.1 is a prerequisite for this vote?
Was implicit, Kenney will get rid of it.
Also, does this mean we are voting for a release of
doxia-decoratio
Ok, I think that for the maven-site-plugin the removal of the
dependency from maven 2.1 is a prerequisite for this vote?
Also, does this mean we are voting for a release of
doxia-decoration-model, doxia-site-renderer, maven-reporting-api (used
by site, not sure which of them should be rolled back
The WAGONHTTP-6 patch has been applied.
There was a recent cleanup of http and https proxy cleanup for both HTTP
wagon providers, as well as the new WebDAV wagon provider.
Big Thanks !
-
To unsubscribe, e-mail: [EMAIL PROTECTED
The WAGONHTTP-6 patch has been applied.
There was a recent cleanup of http and https proxy cleanup for both HTTP
wagon providers, as well as the new WebDAV wagon provider.
- Joakim
Franz Fehringer wrote:
> Hello,
>
> Are the patches applied in the meantime?
> Is MNG-2305 resolved with this also?
The fileset support in the clean plugin is most certainly deployed.
It is used heavily in continuum and archiva to cleanup after the
war:inplace overlay.
- Joakim
[EMAIL PROTECTED] wrote:
> Author: jvanzyl
> Date: Sun Dec 10 18:59:29 2006
> New Revision: 485470
>
> URL: http://svn.apache.org/view
Hi all,
While trying to run the eclipse:make-artifacts goals against an up to date
eclipse v3.2.1 installation, it bombs out with a NullPointerException like
so:
java.lang.NullPointerException
at
org.apache.maven.plugin.eclipse.MakeArtifactsMojo.processSingleFile(MakeArtifactsMojo.java:28
+1 to all
Vincent
2006/12/10, Joakim Erdfelt <[EMAIL PROTECTED]>:
After a chat with Jason about the new release process / staging / etc...
I feel it is time to get a release out for the following plugins.
maven-gpg-plugin 1.0
maven-javadoc-plugin 2.2
maven-site-plugin 2.0
maven-source-plugin 2
Jason van Zyl wrote:
Have you ever tried using a cleaning installed Redhat and trying to use
the Java stuff that's installed? In the recent past I spent an hour
trying to figure out why AMQ tests were failing and it was because gjc
was picking stuff up instead of the JDK I installed. Then I
Hello,
Hello.
Are the patches applied in the meantime?
No, they are not.
Is MNG-2305 resolved with this also?
I think so. The order of the proxies in your configuration files will
have no impact. If you omit the https proxy, maven will fall back on
the proxy declared for http
Will the
+1 to all
Andy
Fabrizio Giustina wrote:
a +1 for all of them, we really need a release at this point
there is only something left that needs to be fixed before the
release: documentation for the gpg plugin needs to be rewritten, I see
that the usage guide refers to the "Genesis Tools Plugin fo
I have an error with the clover plugin.
Clover tries to generate images, but java doesn't find display settings :
java.lang.InternalError: Can't connect to X11 window server using ':0.0' as
the value of the DISPLAY variable.
Can we launch a virtual X server and setup the DISPLAY environment varia
1 - 100 of 108 matches
Mail list logo
