On 12/14/06, Deepak Bhole [EMAIL PROTECTED] wrote:
Why is offline behaviour useful? It is just the way Fedora does things
to ensure that everything is traceable. It is to ensure that the entire
application is built ground up from sources. All of the System
installed jars that I am referring to
On Thu, December 14, 2006 1:46 am, Joakim Erdfelt wrote:
Disclaimer: I am not attempting to set policy, just to get discussion
going,
document it, and work towards the ideal toolchain that
make the
future of apache releases smooth, consistent, and resilient
On 12/14/06, Graham Leggett [EMAIL PROTECTED] wrote:
On Thu, December 14, 2006 1:46 am, Joakim Erdfelt wrote:
Disclaimer: I am not attempting to set policy, just to get discussion
going,
document it, and work towards the ideal toolchain that
make the
future of
None of the issues assigned to 2.0.1 are critical for geronimo.
for geronimo the most important is http://jira.codehaus.org/browse/
MXMLBEANS-19, but that requires xmlbeans to release a correct pom
instead of the incorrect one that has no attribution or known origin
and that the maven
from the IDE support perspective,it would be nice to have
http://jira.codehaus.org/browse/MXMLBEANS-28 fixed.
Milos
On 12/14/06, Jason van Zyl [EMAIL PROTECTED] wrote:
Hi,
The Geronimo folks need a release of the XMLBeans plugins, could
someone help me look at the issues and see if the issues
Hi Dennis,
Thanks for the edits. Docck checks for the two reporting (javadoc and
jxr) plugins though. Should docck exclude the two reporting plugins
from the check/list of errors then?
Regards,
John
On 12/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: dennisl
Date: Thu Dec 14
John Tolentino wrote:
Hi Dennis,
Thanks for the edits. Docck checks for the two reporting (javadoc and
jxr) plugins though. Should docck exclude the two reporting plugins
from the check/list of errors then?
No I don't think so. These two plugins had to be moved to a profile
because of the
Hi,
If I understand correctly, the problem is that a 'staged' release still
contains a SNAPSHOT keyword in the metadata/filename?
Also, how would you see snapshot 'releases' without a snapshot keyword?
If there's no indicator (timestamp?) in the filename, you'll overwrite the
previous deployed
Joakime,
Do you think you could add something that would allow us to add to
set of headers that are sent to a client, and set the client string?
In Maven I would like to accurately keep track of what versions of
Maven are actively in use and I think being able to send version
information
Hi all,
Using the v2.3-SNAPSHOT version of the ear plugin, I am struggling to get
the application.xml file built correctly.
Between maven1 and maven2, the ejb plugin lost it's ability to bundle
dependencies inside the ejb.
This means (as I understand it) that it's now up to the ear plugin to
Jason van Zyl wrote:
On 13 Dec 06, at 10:26 AM 13 Dec 06, Carl Trieloff wrote:
I don't see that there is a consistent view yet on this. It would be
nice to get to a conclusion on whether the Maven community would like
to work with the downstream distros teams so that we can provide a
On 14 Dec 06, at 9:46 AM 14 Dec 06, Carl Trieloff wrote:
Suggestion:
Would a good starting point be to maybe be to create a branch where
some guys can work, and then we work item by item with the maven
community. once we get an issue out the way, and agreed by maven
team we merge the
Has anyone had a chance to look at this, to see if there's something
obviously wrong? If it looks ok, I'll start looking anywhere else
you might suggest. I'm really at a loss at this point.
On Dec 12, 2006, at 4:06 PM, Stephen Pietrowicz wrote:
That didn't work. Here is my addition
Just to clarify the building from source situation, the real requirement
is that if we were in a concrete bunker somewhere with no connection to
the outside world, and all we had was an installed fedora box + all the
source rpms for fedora, we should be able to rebuild the entire OS.
Note
Look at this file :
http://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-webapp-test/src/test/tomcat5x/conf/Catalina/localhost/continuum.xml
We use it for our web-ui test and it works fine.
Emmanuel
Stephen Pietrowicz a écrit :
Has anyone had a chance to look at this, to see if
On 14 Dec 06, at 10:30 AM 14 Dec 06, Rafael Schloming wrote:
Just to clarify the building from source situation, the real
requirement is that if we were in a concrete bunker somewhere with
no connection to the outside world, and all we had was an installed
fedora box + all the source rpms
On Wednesday 13 December 2006 18:54, Tom Huybrechts wrote:
6) All source files in the sources.jar files will contain the
following header.
---(snip)---
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE
I would like to have this optionally work across all current (and
future) wagon wheels (providers).
How about the following methods?
for reference -
http://maven.apache.org/wagon/wagon-provider-api/apidocs/org/apache/maven/wagon/Wagon.html
Wagon.setClientProperties( Properties );
On 14 Dec 06, at 12:24 PM 14 Dec 06, Joakim Erdfelt wrote:
I would like to have this optionally work across all current (and
future) wagon wheels (providers).
How about the following methods?
for reference -
http://maven.apache.org/wagon/wagon-provider-api/apidocs/org/apache/
Hi,
This has been tackled a dozen of times and I am not sure it has
anything to do with the EAR plugin, at least if we follow the spec. If
I am wrong, please let me know.
The valid way to bundle shared components/libs in a EAR is to define
the Class-Path entry of the manifest in EJB module(s)
On Dec 14, 2006, at 11:05 AM, Stephane Nicoll wrote:
Hi,
This has been tackled a dozen of times and I am not sure it has
anything to do with the EAR plugin, at least if we follow the spec. If
I am wrong, please let me know.
The valid way to bundle shared components/libs in a EAR is to define
On 12/14/06, David Jencks [EMAIL PROTECTED] wrote:
I agree that spec support is the way to go.
the jee5 ear lets you specify a lib directory (default is lib)
where all the jars inside get added to the classpath. We could work
on jee5 support, that ought to keep everyone happy. Does the
In a #maven discussion, it was uncovered that a timestamp plugin was
written for the geronimo project.
https://issues.apache.org/jira/browse/GERONIMO-1659
Is there any interest in bringing this into maven-plugins for others to
use?
+1
On 14 Dec 06, at 3:22 PM 14 Dec 06, Brian E. Fox wrote:
In a #maven discussion, it was uncovered that a timestamp plugin was
written for the geronimo project.
https://issues.apache.org/jira/browse/GERONIMO-1659
Is there any interest in bringing this into maven-plugins for
others to
use?
I think the specific use case is to make it get into filtered resources.
It would be better if it was just available without a plugin but in
2.0.x there isn't any other way apparently.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006
I'm not sure this does anything useful. I recommend using antrun if you need
timestamping.
--jason
-Original Message-
From: Brian E. Fox [EMAIL PROTECTED]
Date: Thu, 14 Dec 2006 15:22:08
To:Maven Developers List dev@maven.apache.org
Subject: Maven-timestamp-plugin
In a #maven
On 14 Dec 06, at 3:51 PM 14 Dec 06, Brian E. Fox wrote:
I think the specific use case is to make it get into filtered
resources.
It would be better if it was just available without a plugin but in
2.0.x there isn't any other way apparently.
It would be easy enough to put that in the
FYI here you can find a similar plugin which can be used to set
various properties for resource filtering (timestamp/date, a
decorated version number...). This is actually only used for
Magnolia builds but maybe it could be useful to someone else:
http://svn.magnolia.info/svn/maven-plugins/
Jason van Zyl wrote:
On 14 Dec 06, at 10:30 AM 14 Dec 06, Rafael Schloming wrote:
Just to clarify the building from source situation, the real
requirement is that if we were in a concrete bunker somewhere with no
connection to the outside world, and all we had was an installed
fedora box +
On 14 Dec 06, at 4:07 PM 14 Dec 06, Rafael Schloming wrote:
Jason van Zyl wrote:
On 14 Dec 06, at 10:30 AM 14 Dec 06, Rafael Schloming wrote:
Just to clarify the building from source situation, the real
requirement is that if we were in a concrete bunker somewhere
with no connection to
Hi,
I have managed to get the site plugin working with 2.0.4 and it
really wasn't a simple matter of rolling back some stuff. In order
for the site plugin to work with 2.0.4 the version of doxia that is
in MAVEN_HOME/lib must be used which is doxia-1.0-alpha-7. The
version of doxia in
We could add this to release plugin configuration in the parent POM.
On 14/12/2006, at 2:08 PM, Brian E. Fox wrote:
It looks like the -Preporting flag wasn't used when deploying the
sites.
Some of the reports might not be missed, but apparently this also
precludes the goal pages (ex:
Does the release plugin deploy the site now?
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 5:58 PM
To: Maven Developers List
Subject: Re: Update: Re: [vote] maven release process ( gpg / javadoc /
site / source / remote-resources )
See http://www.nabble.com/forum/ViewPost.jtp?post=7884079framed=yskin=177
for full discussion.
The problem is that a plugin contains defects that have not yet been
resolved in a release.
The defect may be fixed in a snapshot version or there may be an
unapplied patch available.
The releases of
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
On 14 Dec 06, at 7:00 PM 14 Dec 06, Brian E. Fox wrote:
Does the release plugin deploy the site now?
By default it has for a while. There are default goals (deploy, site-
deploy) if you don't specify any.
Jason.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
On 12/14/06, Jason van Zyl [EMAIL PROTECTED] wrote:
I have managed to get the site plugin working with 2.0.4 and it
really wasn't a simple matter of rolling back some stuff.
...
Thanks for doing this. But... (you knew it was coming) I'm having
trouble with it when site.xml contains
Jason van Zyl wrote:
Yah, I don't buy it. I don't know anyone who uses RPMs to do anything
with Java.
Actually, if you'll recall our conversations at ApacheCon I mentioned
something like that. RPMs make no sense because the ClassLoader can't
use them. They also make no sense because the
38 matches
Mail list logo
