+1
Milos
On 1/11/07, Jason van Zyl [EMAIL PROTECTED] wrote:
Can we put the webapp stuff that's currently in the site plugin in
another plugin so that when you simply want to generate your site you
don't drag down Jetty and all its dependencies? It really is
something unexpected and isn't
Hi,
It looks that version 2.0.2 of maven-war-plugin is not marked as relesed
in jira so changes are not visible in changelog - they are in roadmap.
Can somebody take care about this?
Thanks,
Tomek
-
To unsubscribe, e-mail:
Ralph Goers wrote on Thursday, January 11, 2007 6:38 AM:
Well, if you absolutely positively promise to release 2.0.6 when
MNG-1577 is applied ;-) . Seriously, it has been rather frustrating
as I can't even use Maven 2 without that fix.
Yeah, not another 9 months please, I've reported this
Will this release contain solutions to
MNG-2305
MNG-2066
WAGONHTTP-6
?
These issues mean, that it is impossible to access HTTPS (SSL)
repositories from behind proxies/firewalls (i.e. from corporate networks).
Thanks and greetings
Franz
Jason van Zyl schrieb:
Hi,
I want to call a vote
[x] +1 for the full proposal - collapse all groups (implies a vote for
the next option if vote doesn't pass)
-Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Brett Porter wrote:
Folks,
I'd like to turn off continuum_ci.sh and instead only use Continuum
itself to do CI for Continuum. Any objections?
I don't see why it should be turned off, but perhaps the automatic
notifications can be turned off or just send failures. That way it would
verify
Jason van Zyl wrote:
Hi,
I want to call a vote for 2.0.5. All the issues that are going to get
done are done. We'll release and move on.
I would like to start building all releases from a standard machine with
the same JDK. I would like to propose the maven.org machine which is
monitored
+1
fabrizio
On 1/8/07, Stephane Nicoll [EMAIL PROTECTED] wrote:
Hi,
I'd like to release the ear plugin which contains a backward
compatibility issue in 2.3 [1]. The issue has been fixed and the
reporter has validated his builds successfully.
Revision 492264
Snapshot available
Jason van Zyl wrote:
Can we put the webapp stuff that's currently in the site plugin in
another plugin so that when you simply want to generate your site you
don't drag down Jetty and all its dependencies? It really is something
unexpected and isn't something most would associate with just
On 1/11/07, Trygve Laugstøl [EMAIL PROTECTED] wrote:
Jason van Zyl wrote:
Can we put the webapp stuff that's currently in the site plugin in
another plugin so that when you simply want to generate your site you
don't drag down Jetty and all its dependencies? It really is something
unexpected
+1
Emmanuel
Jason van Zyl a écrit :
Can we put the webapp stuff that's currently in the site plugin in
another plugin so that when you simply want to generate your site you
don't drag down Jetty and all its dependencies? It really is something
unexpected and isn't something most would
Agree to the plan.
Emmanuel
Jason van Zyl a écrit :
Hi,
I want to call a vote for 2.0.5. All the issues that are going to get
done are done. We'll release and move on.
I would like to start building all releases from a standard machine with
the same JDK. I would like to propose the
Can't you solve this with -Dhttps.proxyHost=xxx -Dhttps.proxyPort=... ?
On 1/11/07, Franz Fehringer [EMAIL PROTECTED] wrote:
Will this release contain solutions to
MNG-2305
MNG-2066
WAGONHTTP-6
?
These issues mean, that it is impossible to access HTTPS (SSL)
repositories from behind
In M2_OPTS (or where else?)?
Franz
Tom Huybrechts schrieb:
Can't you solve this with -Dhttps.proxyHost=xxx -Dhttps.proxyPort=... ?
On 1/11/07, Franz Fehringer [EMAIL PROTECTED] wrote:
Will this release contain solutions to
MNG-2305
MNG-2066
WAGONHTTP-6
?
These issues mean, that it is
Hello,
WAGONHTTP-6 and MNG-2066 are already resolved; the fixes only need to be
incorporated in the 2.0.5 (or 2.0.6) release.
MNG-2305 should then also be resolved.
Greetings
Franz
Tom Huybrechts schrieb:
Can't you solve this with -Dhttps.proxyHost=xxx -Dhttps.proxyPort=... ?
On 1/11/07,
I read on svn changelog that SVN v1.4 increased a lot the speed for comparing
local copy with repository.
Maybe continuum is very slow in SVN update because it is using SVN 1.3 (both
client and server needs to be updated)
see http://subversion.tigris.org/svn_1.4_releasenotes.html
just my 2
Hi all,
I am have a very strange interoperability problem between jars produced by
maven and jars produced by ant when it comes to JBoss.
JBoss supports the concept of java code running standalone accessing EJBs
in a JBoss container over a network. To do this you package up two files
into the
On 11 Jan 07, at 3:21 AM 11 Jan 07, Tomasz Pik wrote:
Hi,
It looks that version 2.0.2 of maven-war-plugin is not marked as
relesed
in jira so changes are not visible in changelog - they are in roadmap.
Can somebody take care about this?
Done.
Thanks,
Tomek
I really don't care what machine builds the release.
Maven is supposed to be able to make reproducible builds so it shouldn't
matter where you build from.
The only problem will be the contents of the local repository (snapshots),
which will be a problem on any machine.
I suppose you're going to
-0
More plugins are bad IMHO. We could either remove that functionality
and just let people site:state jetty:run '-Dwar=${site.directory}'
or, in the future, make those deps scoped optional and specify
which ones are used for what mojo so that when you run that mojo
they won't be optional
On 11/01/07, Kenney Westerhof [EMAIL PROTECTED] wrote:
In short: why bother? :)
I tend to agree with Kenney. Besides, all good developers have jetty
in their local repo already ;)
Mark
-
To unsubscribe, e-mail: [EMAIL
Hi,
this is actually a user question and should be asked on the user list.
There are also more people out there that use JBoss and maven so you
may have better luck there.
In the mean time I suggest you try to find out what it is that's
breaking it.
Take the maven2 built jar, unjar it, and try
On 11 Jan 07, at 8:56 AM 11 Jan 07, Kenney Westerhof wrote:
I really don't care what machine builds the release.
Maven is supposed to be able to make reproducible builds so it
shouldn't
matter where you build from.
You know as well as I do that isn't the case quite yet. The reduction
of
On 11 Jan 07, at 9:14 AM 11 Jan 07, Kenney Westerhof wrote:
-0
More plugins are bad IMHO.
I don't think so especially when it encourages a separation of
concerns. Publishing a site should not require a servlet container.
We could either remove that functionality
and just let people
On 11 Jan 07, at 9:20 AM 11 Jan 07, Mark Hobson wrote:
Besides, all good developers have jetty
in their local repo already ;)
Yes, following that logic why don't we just stick all the plugins in
one in one plugin and not bother trying to separate concerns at all.
Then we'll only have one
On 11/01/07, Jason van Zyl [EMAIL PROTECTED] wrote:
Yes, following that logic why don't we just stick all the plugins in
one in one plugin and not bother trying to separate concerns at all.
Then we'll only have one plugin and when people run mvn clean they
will just get everything they need?
+1
Dan
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 11, 2007 4:24 AM
To: Maven Developers List
Subject: Re: calling vote for 2.0.5
Agree to the plan.
Emmanuel
Jason van Zyl a écrit :
Hi,
I want to call a vote for 2.0.5. All the
+1
--
Regards,
Garvin LeClaire
[EMAIL PROTECTED]
On 1/11/07, Tom Huybrechts [EMAIL PROTECTED] wrote:
Can't you solve this with -Dhttps.proxyHost=xxx -Dhttps.proxyPort=... ?
On 1/11/07, Franz Fehringer [EMAIL PROTECTED] wrote:
Will this release contain solutions to
MNG-2305
MNG-2066
+1
Andy
On 10 Jan 2007, at 22:20, Jason van Zyl wrote:
Hi,
I want to call a vote for 2.0.5. All the issues that are going to
get done are done. We'll release and move on.
I would like to start building all releases from a standard machine
with the same JDK. I would like to propose the
+1
On 11 Jan 2007, at 04:49, Jason van Zyl wrote:
Can we put the webapp stuff that's currently in the site plugin in
another plugin so that when you simply want to generate your site
you don't drag down Jetty and all its dependencies? It really is
something unexpected and isn't something
I have a parent pom that defines the SCM of itself and all it's children by
using
scm:svn:http://${scm.host}/svnrepos/${object.namespace}/${artifactId}/trunk
and I end up with
scm:svn:http://${scm.host}/svnrepos/${object.namespace
}/${artifactId}/trunk/${artifactId}
I'm not sure if this is
-0 it might be nice to have access to everything once you join, but
it seems handy to have an acl of all those writing to the various areas.
On 8 Jan 2007, at 23:50, Brett Porter wrote:
Hi,
Since there was no objection to calling a vote, as discussed in the
proposal, I'd like to call a
On 8 Jan 07, at 7:04 PM 8 Jan 07, Jason van Zyl wrote:
-1
I change mine to:
[X ] +1 for the partial proposal - retain subproject access restrictions
I just want at the sub-project level.
On 8 Jan 07, at 6:50 PM 8 Jan 07, Brett Porter wrote:
Hi,
Since there was no objection to
I'm in a similar situation with patches I've provided. Some have
integration tests as well, as requested. No comments have been made
on any of the patches, they are months old.
They might not seem important, but we had to throw away our entire
Maven investment at a company I am at, after
+1 from me. For practical purposes, we can control a single environment much
more easily (eg. removing the local repository before we build a release, or
making sure it's built on JDK 1.4) than N developer boxes. Even if the
builds are 100% reproducible, it's not a bad idea to have a clean
+1 for releasing 2.0.5
+0 for micro releases. I agree with Trygve's comment that too frequent
of these can lead to inconsistent developer environments.
Cheers,
Rahul
- Original Message -
From: Jason van Zyl [EMAIL PROTECTED]
To: Maven Developers List dev@maven.apache.org
Sent:
On 11 Jan 07, at 1:16 PM 11 Jan 07, Rahul Thakur wrote:
+1 for releasing 2.0.5
+0 for micro releases. I agree with Trygve's comment that too
frequent of these can lead to inconsistent developer environments.
Really the point is to schedule them and make the roadmaps available
so
I agree with Jason on this. My initial reaction was Weekly No way I
can keep all my developers in synch.
Then I realized that just because a build comes out doesn't mean we have
to take it. As long as the plan is clear about what is fixed then it
isn't a huge problem. I might take 2.0.5
Regardless of these process issues, I should add that I'm all for
getting a release out. Congrats to the team on feeling things are
stable enough to go out and thanks for all the hard work put into
other areas of the project.
Brian
On Jan 11, 2007, at 9:30 AM, Brian Topping wrote:
I'm
MCOMPILER-22 has a problem as the javac compiler is being called with
-J for Xmx and Xms and from the docs [1] it's not accepted in argument
files.
We're gonna use always argument files when forking, can the -J option
be removed ?
[1]
Hi Everyone,
You can now generate release reports using the maven-swizzle-plugin.
Here's the related documentation:
http://people.apache.org/~jtolentino/staging_site/maven-swizzle-plugin/examples/generating-release-report.html
This is an implementation on what's discussed in this thread:
i think I got it, i'll use Xmx and Xms only when forking
On 1/11/07, Carlos Sanchez [EMAIL PROTECTED] wrote:
MCOMPILER-22 has a problem as the javac compiler is being called with
-J for Xmx and Xms and from the docs [1] it's not accepted in argument
files.
We're gonna use always argument files
John, can you give us a sample of what the final report looks like?
On 1/11/07, John Tolentino [EMAIL PROTECTED] wrote:
Hi Everyone,
You can now generate release reports using the maven-swizzle-plugin.
Here's the related documentation:
Here's the example report:
http://people.apache.org/~jtolentino/staging_site/maven-swizzle-plugin/release-report.html
On 1/12/07, Mike Perham [EMAIL PROTECTED] wrote:
John, can you give us a sample of what the final report looks like?
On 1/11/07, John Tolentino [EMAIL PROTECTED] wrote:
Hi
By the way, for this example, the changes I made to
maven-source-plugin's POM to generate the report is:
project
[...]
build
plugins
plugin
artifactIdmaven-swizzle-plugin/artifactId
configuration
projectKeyMPSOURCE/projectKey
templateRELEASE/template
On 1/11/07, John Tolentino [EMAIL PROTECTED] wrote:
Hi Everyone,
hi john
You can now generate release reports using the maven-swizzle-plugin.
have you implemented your header checked yet?
i'm interested in collaborating on release auditing (in particular for apache)
- robert
Not yet. Still looking for existing maven plugins that might be doing
this already. Not sure if the verifier plugin could do this for us.
I'm sure everyone would be happy to have new people to help out.
On 1/12/07, robert burrell donkin [EMAIL PROTECTED] wrote:
On 1/11/07, John Tolentino
On 11 Jan 07, at 3:42 PM 11 Jan 07, robert burrell donkin wrote:
On 1/11/07, John Tolentino [EMAIL PROTECTED] wrote:
Hi Everyone,
hi john
You can now generate release reports using the maven-swizzle-plugin.
have you implemented your header checked yet?
i'm interested in collaborating
+1
On 1/11/07, Fabrizio Giustina [EMAIL PROTECTED] wrote:
+1
fabrizio
On 1/8/07, Stephane Nicoll [EMAIL PROTECTED] wrote:
Hi,
I'd like to release the ear plugin which contains a backward
compatibility issue in 2.3 [1]. The issue has been fixed and the
reporter has validated his builds
Was thinking of integrating both docck and rat plugins by calling
their execute() methods.
Docck throws a MojoFailureException when documentation tests fails and
test results could be redirected to a file through the output
parameter. So integration with this plugin is straightforward.
Although
On 1/11/07, Jason van Zyl [EMAIL PROTECTED] wrote:
On 11 Jan 07, at 3:42 PM 11 Jan 07, robert burrell donkin wrote:
On 1/11/07, John Tolentino [EMAIL PROTECTED] wrote:
Hi Everyone,
hi john
You can now generate release reports using the maven-swizzle-plugin.
have you implemented your
On 12/01/2007, at 1:14 AM, Kenney Westerhof wrote:
I imagine most developers have at least a 2Mbit
downlink
You have quite an imagination :)
I recently upgraded back up to a 1.5Mbit connection from 512Kbit.
It's the highest I can get in my region, and usually is significantly
more
It appears he'll stick with mojo. But couldn't speak for him. I'll
update everyone when I get a patch and have him take a look at it.
On 1/12/07, robert burrell donkin [EMAIL PROTECTED] wrote:
On 1/11/07, Jason van Zyl [EMAIL PROTECTED] wrote:
On 11 Jan 07, at 3:42 PM 11 Jan 07, robert
On 1/11/07, John Tolentino [EMAIL PROTECTED] wrote:
Not yet. Still looking for existing maven plugins that might be doing
this already. Not sure if the verifier plugin could do this for us.
there's quite a few wrinkles to release auditing which aren't
immediately obvious
RAT code's rubbish (i
[X] 0 - Don't care.
This is one case where I'd like to be able to alias a goal to a new
plugin, or dual-alias the goal prefix. I agree the webapp belongs in
a different plugin, and probably should have started it that way, but
I really prefer to use site:run.
If it does get moved, and we
windows path length pb?
Marcelo Fukushima a écrit :
im looking into it, but i cant seen to install the modules locally -
im getting a weird random access denied error...
On 1/10/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Yes. A global patch would be better instead of separate patches.
I
Jason van Zyl wrote:
On 11 Jan 07, at 1:16 PM 11 Jan 07, Rahul Thakur wrote:
+1 for releasing 2.0.5
+0 for micro releases. I agree with Trygve's comment that too
frequent of these can lead to inconsistent developer environments.
Really the point is to schedule them and make the
+1
I'd rather download only what I need. I have 512Kpbs (max). Other
people here in Asia have slower connections because of the recent
earthquake--fiber optic cables were cut if you haven't heard the news
yet.
On 1/12/07, Brett Porter [EMAIL PROTECTED] wrote:
On 12/01/2007, at 1:14 AM, Kenney
Hi Robert,
Can you have a plexus component for the license header auditing then?
I can hook it up to the plugin when it's ready. Only two information
are needed:
- check result (a boolean value) and
- output file where the reports can link to
Thanks,
John
On 1/12/07, robert burrell donkin
On 1/11/07, John Tolentino [EMAIL PROTECTED] wrote:
Was thinking of integrating both docck and rat plugins by calling
their execute() methods.
Docck throws a MojoFailureException when documentation tests fails and
test results could be redirected to a file through the output
parameter. So
I need to release maven-script-ant 2.0.5 before releasing maven 2.0.5
Jason.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 1/11/07, John Tolentino [EMAIL PROTECTED] wrote:
Hi Robert,
Can you have a plexus component for the license header auditing then?
i think so but we may need to think about the best way to do it...
RAT's half way through a redesign ATM but i'll move that onto a branch :-/
I can hook it
Scratch that, a cut/paste got away on me.
Jason.
On 11 Jan 07, at 5:21 PM 11 Jan 07, Jason van Zyl wrote:
I need to release maven-script-ant 2.0.5 before releasing maven 2.0.5
Jason.
-
To unsubscribe, e-mail: [EMAIL
I totally agree.
This 'micro release' is a rather big bugfix release.
If you have lots of bugfix (micro) releases, and you stumble across
a bug, it's pretty easy to find if it's solved by looking at the release notes.
That is, if you update frequently. If you don't, you got lots of bugfix
On 11 Jan 07, at 6:04 PM 11 Jan 07, Kenney Westerhof wrote:
I totally agree.
On that note I have put the one in that I promised for Ralph, and
there is probably one more that I will attempt. So if anyone knows of
a couple they are up for slot them in there.
I pushed all 2.0.x issues
With the new main page for the maven 2 site, I think that it is difficult to
find the m1 site link (in the bottom left).
Can't we add it with continuum and archiva in the box other maven projects
?
WDYT ?
Arnaud
-- Forwarded message --
From: Murugan [EMAIL PROTECTED]
Date: Jan
Jason van Zyl wrote:
On 11 Jan 07, at 3:42 PM 11 Jan 07, robert burrell donkin wrote:
On 1/11/07, John Tolentino [EMAIL PROTECTED] wrote:
Hi Everyone,
hi john
You can now generate release reports using the maven-swizzle-plugin.
have you implemented your header checked yet?
i'm
yep
On 12/01/2007, at 10:38 AM, Arnaud HERITIER wrote:
With the new main page for the maven 2 site, I think that it is
difficult to
find the m1 site link (in the bottom left).
Can't we add it with continuum and archiva in the box other maven
projects
?
WDYT ?
Arnaud
--
Ok, I'll do it asap.
Arnaud
On 1/12/07, Brett Porter [EMAIL PROTECTED] wrote:
yep
On 12/01/2007, at 10:38 AM, Arnaud HERITIER wrote:
With the new main page for the maven 2 site, I think that it is
difficult to
find the m1 site link (in the bottom left).
Can't we add it with continuum
Sure, that sounds fair :-)
jason.
On 11 Jan 07, at 6:38 PM 11 Jan 07, Arnaud HERITIER wrote:
With the new main page for the maven 2 site, I think that it is
difficult to
find the m1 site link (in the bottom left).
Can't we add it with continuum and archiva in the box other maven
projects
yeah...
but now that ive settled it, ive encountered a new set of probs, this
time in the data-management with the trunk on svn:
-while backing up the continuum store, a FileWriter is used (wich uses
default system char encoding), but the stream used to write the xml
tries to use utf-8, in wich
It's now fixed
Thx to kenney.
I didn't see the problem of version with the jdk.
I deployed modello jars after building them with a jdk 1.5.
The build failed on maven.zones which uses a jdk 1.4
Arnaud
On 1/10/07, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Hi guys (and Jason particularly),
I
Marcelo Fukushima wrote:
yeah...
but now that ive settled it, ive encountered a new set of probs, this
time in the data-management with the trunk on svn:
-while backing up the continuum store, a FileWriter is used (wich uses
default system char encoding), but the stream used to write the xml
ping ??
Sorry, but I would like to have your opinion ASAP.
My holidays are ended at the end of this week and I want to finish as much
tasks as possible before.
Arnaud
On 1/10/07, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Hi guys,
Since some days I'm working on modello / maven-model /
On 1/11/07, Rahul Thakur [EMAIL PROTECTED] wrote:
Marcelo Fukushima wrote:
yeah...
but now that ive settled it, ive encountered a new set of probs, this
time in the data-management with the trunk on svn:
-while backing up the continuum store, a FileWriter is used (wich uses
default system
Issue Subscription
Filter: Design Best Practices (37 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
Marcelo Fukushima wrote:
On 1/11/07, Rahul Thakur [EMAIL PROTECTED] wrote:
Marcelo Fukushima wrote:
yeah...
but now that ive settled it, ive encountered a new set of probs, this
time in the data-management with the trunk on svn:
-while backing up the continuum store, a FileWriter is used
I don't think either of these are cases for 'package resources', but
general lifecycle improvements (Which are in the 2.1 design wiki).
Is that right?
- Brett
On 06/01/2007, at 7:47 AM, Aaron Digulla wrote:
Brett Porter wrote:
Can anyone think of a use case other than the war plugin, or
For a quick opinion ASAP, I did a quick review of the pages, and they look
pretty good. When I can review more in-depth, I may suggest some additional
info/clarifications and writing changes on the site docs.
My initial suggestion on the Overview page is that I would like a link to an
After the allotted 72 hours, the results stand as:
Full proposal: 9 (7 PMC, 2 committers): Brett, Arnaud, Emmanuel,
Trygve, Dennis, Fabrizio, Lukas, Rahul, Milos
Partial proposal: 6 (6 PMC): Joakim, John T, Kenney, Jesse, John C,
Jason
Abstained: 3 (3 PMC): Mike, Vincent S, Stephane
Yep, I understand the intent and that is good. A reasonable interval(?)
for micro releases should be fine.
I'd be quite happy about more releases of Maven in its current state.
However, what matters more, IMO, would be micro releases of the core
plugins.
Jochen
--
How fast can a year go? As
81 matches
Mail list logo
