Hey Guys,

Yes this is all very good. Definity organize everthing in the /www/cvs.apache.org/repository until you are confident that everything is in its proper place, the biggest issue we encounter is broken symlinks and bad md5 signatures. Once everything is layed out the way you want it and your ready to release, just copy it into /www/www.apache.org/dist/java-repository/... which is rsynced to ibibilio every 4 hours.

Make sure premissions are group 'rw' for apcvs and all 'r' once you place it into the official repository location directory.

cheers,
Mark

Carlos Sanchez wrote:

Hi,

The maven process to deploy projects in the repository is very easy, it
seems that the maven configuration is a bit outdated. I've attached a small
patch setting up the repositories. I suggest you to move the building
process to maven, it makes life much easier.

If you have any doubt you can contact me directly or send a mail to the
maven list.

Regards

Carlos Sanchez
A Coru�a, Spain

Oness Project
http://oness.sourceforge.net




-----Original Message-----
From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 6:25 PM
To: Struts DEV Mailing List
Cc: Carlos Sanchez
Subject: RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released)


I'm bringing this thread over to the dev list because it's fairly technical and boring to the average user.

I went ahead and set up the "nightly builds" Maven repository with Struts 1.2.1 -- see http://cvs.apache.org/repository/struts/

I tried to flesh out the directories along the "idealized" Maven repository, by including 'licenses', 'distributions','poms', and 'tlds' directories as well as 'jars' Not sure if that's right or not, since it doesn't seem to be thoroughly documented; we'll just see.

Anyway, so the two pertinent questions are
1) should this go on iBiblio yet? I'm leaning towards "no" until it reaches GA status. For general reference, the Apache directory "/www/www.apache.org/dist/java-repository" is mirrored to iBiblio, so that when we decide that a Struts release is GA, we can set up that directory and have the release maven-published automatically.


2) what version number should struts-el have? 1.2.1 ? I'm not sure we've bothered with formally labelling it with a release in the past, but Maven really likes things to have versions.

On minor administrative issues, I also changed the "project.xml" file version to 1.2.1 (from
1.2.1-dev) and moved the release tag for that one file so that if someone checks out to the tag, the JAR artifact will have the correct version number.


Joe



At 5:41 PM +0200 7/12/04, Carlos Sanchez wrote:


Hi Joe,

I agree that users should use iBiblio, just said apache repository because it's mirrored.

About the use of the private repo
http://cvs.apache.org/builds/java-repository/ seems a good


idea to me,

but it hasn't been already created, nobody has upload nothing until now? Many apache projects still upload their snapshots to

the release

repository, ending at iBiblio. Should this be told to the

projects that

had uploaded snapshots to ibiblio?

I am also sure that 1.2.1 should definitely be put at http://cvs.apache.org/builds/java-repository/

Regards.



-----Original Message-----
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Monday, July 12, 2004 4:08 PM
To: Struts Users Mailing List
Subject: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1
(Beta) Released)

At 11:34 AM +0200 7/12/04, Carlos Sanchez wrote:
>Hi,
>
>Will you deploy it and the struts-el on the apache maven


repository?


>http://www.apache.org/dist/java-repository/struts/jars/

I would argue that it doesn't belong in that location

until it is

voted a full GA release.
Then again, reviewing what seems to be the "official"


word on using

the Apache repositories (http://article.gmane.org/gmane.comp.jakarta.commons.devel/39469),
it simply says that location is for "versioned releases"


as opposed

to "nightly builds".

For what it's worth, I think that the intention is not

that Maven

users would have http://www.apache.org/dist/java-repository/ as a repository, but rather than they'd use iBiblio, which is mirrored from that. I don't know if anyone feels strongly about it, but that's how I read the previously cited email.

If we don't put Struts 1.2.1 on iBiblio, we should

definitely put

it at http://cvs.apache.org/builds/java-repository/

I'll do either one, but I'll wait to see if a few

opinions roll in

before taking action.

Joe



>I have built it from cvs sources with maven and the size is not the same.
>
>Regards
>
>Carlos Sanchez
>A Coru�a, Spain
>
>Oness Project
>http://oness.sourceforge.net
>
>
>> -----Original Message-----
>> From: Ted Husted [mailto:[EMAIL PROTECTED] >>


Sent: Sunday,

July 11, 2004 9:11 PM >> To: [EMAIL PROTECTED] >> Cc: [EMAIL PROTECTED] >> Subject: [ANN] Struts 1.2.1 (Beta) Released >> >> The Struts team announces the release of Struts 1.2.1, currently >> ranked at Beta quality.
>>
>> This release removes many features deprecated in


prior releases


> >> (Struts 1.1 and Struts 1.0.2) and also provides several new


>> features. Fixes to known problems have been applied. More detail is >> available at >> >> * http://struts.apache.org/userGuide/release-notes.html
>>
>> The binary, source, and library distributions are


available at

>> * http://cvs.apache.org/dist/struts/v1.2.1/


>>
>> The library distribution contains only the requisite JARs, without >> the documentation or example applications.
>>
>> We invite your comments on how well this release works with your >> own applications. Based on feedback from the Struts community, this >> release may be dubbed "ready for prime time"
>> and promoted to "General Availabilty" quality.
>>
>> Please note that Struts now uses "Tomcat-style" releases. If the >> feedback on this release were positive, Struts


1.2.1 may be

promoted >> directly to "GA", without creating yet-another distribution. If a >> serious problem were found and

fixed, then we

will issue Struts  >> 1.2.2 and try again.
>>
>>  ####
>>
>>
>>
>>
>>




---------------------------------------------------------------------


>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail:


[EMAIL PROTECTED] >>

>> > > >






--------------------------------------------------------------------


-  >To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]


--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "In fact, when I die, if I don't hear 'A Love Supreme,'


I'll turn

back; I'll know I'm in the wrong place."
    - Carlos Santana





---------------------------------------------------------------------


To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place."
- Carlos Santana







------------------------------------------------------------------------

Index: project.properties
===================================================================
RCS file: /home/cvspublic/jakarta-struts/project.properties,v
retrieving revision 1.12
diff -u -r1.12 project.properties
--- project.properties  7 Jul 2004 11:12:02 -0000       1.12
+++ project.properties  12 Jul 2004 18:09:15 -0000
@@ -125,3 +125,20 @@
# in order to deploy to the repository:
#ssh configuration settings just require your apache id to log on with
#maven.username=<apache-user-name> (DON'T UNCOMMENT THIS LINE IN SHARED project.propert
+
+
+# Repository to deploy to
+maven.repo.list=apachecvs
+
+maven.repo.apachecvs=scp://cvs.apache.org
+maven.repo.apachecvs.directory=/repository
+#maven.repo.apachecvs.username=
+#maven.repo.apachecvs.privatekey=
+#maven.repo.apachecvs.passphrase=
+
+# Use -Dmaven.repo.list=apache when making releases
+maven.repo.apache=scp://${pom.distributionSite}
+maven.repo.apache.directory=${pom.distributionDirectory}
+maven.repo.apache.username=${maven.repo.apachecvs.username}
+maven.repo.apache.privatekey=${maven.repo.apachecvs.privatekey}
+maven.repo.apache.passphrase=${maven.repo.apachecvs.passphrase}
Index: project.xml
===================================================================
RCS file: /home/cvspublic/jakarta-struts/project.xml,v
retrieving revision 1.31
diff -u -r1.31 project.xml
--- project.xml 12 Jul 2004 16:12:30 -0000      1.31
+++ project.xml 12 Jul 2004 18:09:18 -0000
@@ -21,7 +21,8 @@
  <issueTrackingUrl>http://issues.apache.org/bugzilla/</issueTrackingUrl>
  <siteAddress>struts.apache.org</siteAddress>
  <siteDirectory>/www/jakarta.apache.org/struts</siteDirectory>
-  
<distributionDirectory>/www/apache.mirrors.pair.com/jakarta/struts/</distributionDirectory>
+  <distributionSite>www.apache.org</distributionSite>
+  
<distributionDirectory>/www/www.apache.org/dist/java-repository/</distributionDirectory>
  <repository>
    <connection>scm:cvs:pserver:[EMAIL 
PROTECTED]:/home/cvspublic:jakarta-struts</connection>
    <developerConnection>scm:cvs:pserver:[EMAIL 
PROTECTED]:/home/cvs:jakarta-struts</developerConnection>



------------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to