On 12/16/2011 11:02 PM, Mark Thomas wrote:
The good news is that Jean-Frederic has indicated via private e-mail
that he will be fixing the build scripts to use Nexus tomorrow. I would
like to see him confirm that on this list but I have no reason to doubt
his word. A quick read of [2] suggests
https://issues.apache.org/bugzilla/show_bug.cgi?id=52351
Bug #: 52351
Summary: tomcat6 started but web page stopped automatically
Product: Tomcat 6
Version: 6.0.24
Platform: PC
OS/Version: Linux
Status: NEW
https://issues.apache.org/bugzilla/show_bug.cgi?id=52351
Konstantin Kolinko knst.koli...@gmail.com changed:
What|Removed |Added
Status|NEW
On 17 December 2011 05:19, Phil Steitz phil.ste...@gmail.com wrote:
On 12/16/11 12:56 PM, Mark Thomas wrote:
All,
There are currently two options for publishing JARs to Maven Central:
1. scp+rsync via people.a.o
2. Nexus
Personally, my only requirements are:
a) that the JARs reach Maven
On Dec 17, 2011, at 6:44 AM, sebb seb...@gmail.com wrote:
On 17 December 2011 05:19, Phil Steitz phil.ste...@gmail.com wrote:
On 12/16/11 12:56 PM, Mark Thomas wrote:
All,
There are currently two options for publishing JARs to Maven Central:
1. scp+rsync via people.a.o
2. Nexus
2011/12/16 Mark Thomas ma...@apache.org
There are currently two options for publishing JARs to Maven Central:
1. scp+rsync via people.a.o
2. Nexus
In my experience in Tiles releases, the only problem we had with scp +
simple copy (we did not use rsync) is that this process breaks Maven
On 17/12/2011 18:08, Antonio Petrelli wrote:
2011/12/16 Mark Thomas ma...@apache.org
There are currently two options for publishing JARs to Maven Central:
1. scp+rsync via people.a.o
2. Nexus
In my experience in Tiles releases, the only problem we had with scp +
simple copy (we did not
2011/12/17 Mark Thomas ma...@apache.org
On 17/12/2011 18:08, Antonio Petrelli wrote:
2011/12/16 Mark Thomas ma...@apache.org
There are currently two options for publishing JARs to Maven Central:
1. scp+rsync via people.a.o
2. Nexus
In my experience in Tiles releases, the only
On 17/12/2011 18:14, Antonio Petrelli wrote:
Ok then interprete my words as: now you can use a staging repository.
This way, artifacts may be tested *before* they are released.
The scp+rsync process also has a staging repository (and using that did
not cause any meta-data issues).
The JARs are
On 16/12/2011 19:56, Mark Thomas wrote:
All,
There are currently two options for publishing JARs to Maven Central:
1. scp+rsync via people.a.o
2. Nexus
Personally, my only requirements are:
a) that the JARs reach Maven Central
b) publishing is as simple as running a single script
I
2011/12/17 Mark Thomas ma...@apache.org
On 17/12/2011 18:14, Antonio Petrelli wrote:
Ok then interprete my words as: now you can use a staging repository.
This way, artifacts may be tested *before* they are released.
The scp+rsync process also has a staging repository (and using that did
On 17/12/2011 18:35, Antonio Petrelli wrote:
2011/12/17 Mark Thomas ma...@apache.org
On 17/12/2011 18:14, Antonio Petrelli wrote:
Ok then interprete my words as: now you can use a staging repository.
This way, artifacts may be tested *before* they are released.
The scp+rsync process also
2011/12/17 Mark Thomas ma...@apache.org
On 17/12/2011 18:35, Antonio Petrelli wrote:
2011/12/17 Mark Thomas ma...@apache.org
On 17/12/2011 18:14, Antonio Petrelli wrote:
Ok then interprete my words as: now you can use a staging repository.
This way, artifacts may be tested *before*
On 17/12/2011 18:42, Antonio Petrelli wrote:
2011/12/17 Mark Thomas ma...@apache.org
On 17/12/2011 18:35, Antonio Petrelli wrote:
2011/12/17 Mark Thomas ma...@apache.org
On 17/12/2011 18:14, Antonio Petrelli wrote:
Ok then interprete my words as: now you can use a staging repository.
This
Author: jfclere
Date: Sat Dec 17 19:02:31 2011
New Revision: 1215557
URL: http://svn.apache.org/viewvc?rev=1215557view=rev
Log:
Fix the deploy-release task.
Once done you should have an entry in
https://repository.apache.org/index.html#stagingRepositories
Check it and click Close.
Once the
2011/12/17 Mark Thomas ma...@apache.org
On 17/12/2011 18:42, Antonio Petrelli wrote:
2011/12/17 Mark Thomas ma...@apache.org
On 17/12/2011 18:35, Antonio Petrelli wrote:
2011/12/17 Mark Thomas ma...@apache.org
On 17/12/2011 18:14, Antonio Petrelli wrote:
Ok then interprete my words
On 17/12/2011 19:10, Antonio Petrelli wrote:
2011/12/17 Mark Thomas ma...@apache.org
Personally, I am of the view If it ain't broke, don't fix it. If there
was something we would gain by switching to Maven then I'd be interested
but given we have an established build process with Ant that a
As requested here is a proposal to move to Maven.
2011/12/17 Mark Thomas ma...@apache.org
Using Maven has several benefits (standardization of structure, lots of
reusable plugins, supported by major IDEs),
Those are features, not benefits.
The standardization of structure is not a
On 17/12/2011 20:24, Antonio Petrelli wrote:
Ok, let's do it again :-D
1. Standardization. Maven strongly encourages to use a standardized
structure. The source should go into src/main/java, the resources in
src/main/resources etc. You can change it, but this is discouraged. With
Ant you
I'll try to keep it short because I really don't want to spend time re-beating
this dead horse.
The last time I looked a couple years ago the jars constructed out of the
single source tree could not be compiled separately in any order. I was told
this wasn't a problem, at which point I
2011/12/17 Antonio Petrelli antonio.petre...@gmail.com:
If you release to a staging directory, the Maven metadata (containg info
about previous releases) are not there, so they are created from scratch.
So, after releasing in the staging directory and voting, the copy method
simply overwrite
On 17/12/2011 21:43, Konstantin Kolinko wrote:
2011/12/17 Antonio Petrelli antonio.petre...@gmail.com:
If you release to a staging directory, the Maven metadata (containg info
about previous releases) are not there, so they are created from scratch.
So, after releasing in the staging directory
On 17/12/2011 21:12, David Jencks wrote:
I'll try to keep it short because I really don't want to spend time
re-beating this dead horse.
The last time I looked a couple years ago the jars constructed out of
the single source tree could not be compiled separately in any order.
I was told
2011/12/17 jfcl...@apache.org:
Author: jfclere
Date: Sat Dec 17 19:02:31 2011
New Revision: 1215557
URL: http://svn.apache.org/viewvc?rev=1215557view=rev
Log:
Fix the deploy-release task.
Once done you should have an entry in
https://repository.apache.org/index.html#stagingRepositories
Author: markt
Date: Sat Dec 17 22:51:29 2011
New Revision: 1220292
URL: http://svn.apache.org/viewvc?rev=1220292view=rev
Log:
Servlet 3.1 generics additions
Modified:
tomcat/trunk/java/javax/servlet/ServletRequestWrapper.java
tomcat/trunk/java/javax/servlet/ServletResponseWrapper.java
Author: markt
Date: Sat Dec 17 22:52:18 2011
New Revision: 1220293
URL: http://svn.apache.org/viewvc?rev=1220293view=rev
Log:
Fix cyclic JAR dependency and add check to ensure it doesn't return
Modified:
tomcat/trunk/java/org/apache/catalina/startup/Catalina.java
On 17/12/2011 21:59, Mark Thomas wrote:
On 17/12/2011 21:12, David Jencks wrote:
I'll try to keep it short because I really don't want to spend time
re-beating this dead horse.
The last time I looked a couple years ago the jars constructed out of
the single source tree could not be compiled
Author: markt
Date: Sat Dec 17 22:52:54 2011
New Revision: 1220294
URL: http://svn.apache.org/viewvc?rev=1220294view=rev
Log:
Fix startup failure when running with a SecurityManager
Modified:
tomcat/trunk/java/org/apache/catalina/security/SecurityClassLoad.java
Modified:
Author: markt
Date: Sat Dec 17 22:53:20 2011
New Revision: 1220295
URL: http://svn.apache.org/viewvc?rev=1220295view=rev
Log:
Add properties required by new logging helper when running under a
SecurityManager
Modified:
tomcat/trunk/conf/catalina.policy
Modified:
Author: markt
Date: Sat Dec 17 22:53:51 2011
New Revision: 1220296
URL: http://svn.apache.org/viewvc?rev=1220296view=rev
Log:
Fix cyclic JAR dependency and add check to ensure it doesn't return
Modified:
tomcat/tc7.0.x/trunk/ (props changed)
Author: markt
Date: Sat Dec 17 22:55:28 2011
New Revision: 1220297
URL: http://svn.apache.org/viewvc?rev=1220297view=rev
Log:
Add properties required by new logging helper when running under a
SecurityManager
Modified:
tomcat/tc7.0.x/trunk/ (props changed)
I forgot to mention that geronimo has been re-releasing several versions of
tomcat built with maven. We have a script to set up a maven multi module
project structure and distribute the tomcat source code from tomcat svn into
the maven projects. This stuff is under
[
https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13171763#comment-13171763
]
Brad Giaccio commented on MTOMCAT-108:
--
@Oliver
1. Sorry about the formatting I
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project tomcat-tc7.0.x-test has an issue affecting its community integration.
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
On 12/17/2011 07:27 PM, Mark Thomas wrote:
Jean-Frederic, what was your motivation for moving Tomcat to Nexus?
1 - The good thing in Nexus is that we can check the result of our
deploy-release and drop is we screw it (multi upload can fail and we
don't know when the mirroring stars).
2 -
42 matches
Mail list logo
