You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Don Brown <mr...@twdata.org> on 2005/08/30 06:24:31 UTC
New Validator 1.2.0-dev dependency
In case you missed it, I changed our validator dependency to 1.2.0-dev,
which it really already was, but now it is enforced. Since most folks
don't have a commons-validator-1.2.0-dev.jar lying around, I added my
apache remote jar repository as an alternate for Maven to retrieve
from. This repository contains the validator jar so folks don't have to
checkout validator and build their own jar.
Is this ok, or is there a better way to handle this?
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: New Validator 1.2.0-dev dependency
Posted by Don Brown <mr...@twdata.org>.
Ok, I changed the commons-validator version to SNAPSHOT, so Maven will
now try to download the latest one each time it is ran. This will let
us add features to commons-validator and be sure they are available to
Struts immediately, however it will also mean Maven will access the
network each time it is ran.
I'd like to take this opportunity to remind everyone of the "-o"
switch. This switch will tell Maven to run in "offline" mode, meaning
it won't try to download new snapshot jars. For example:
maven -o jar
HTH,
Don
Don Brown wrote:
> Wendy Smoak wrote:
>
>> Don, was that .jar file compiled with JDK 1.5 by any chance?
>
>
>
> Doh, you are right. I updated it with the correct one. Perhaps this
> should be made a SNAPSHOT so maven will always try to download the
> latest one?
>
> Don
>
>>
>> java:compile:
>> [echo] Compiling to e:\svn\struts\current\core/target/classes
>> [echo]
>> ==========================================================
>>
>> NOTE: Targetting JVM 1.4, classes
>> will not run on earlier JVMs
>>
>> ==========================================================
>>
>> [javac] Compiling 146 source files to
>> E:\svn\struts\current\core\target\classes
>> E:\svn\struts\current\core\src\share\org\apache\struts\validator\ValidatorForm.j
>>
>> ava:29: cannot access org.apache.commons.validator.Validator
>> bad class file: C:\Documents and
>> Settings\wendy\.maven\repository\commons-validator\jars\commons-validator-1.2.0-dev.jar(org/apache/commons/validator/Validator.class)
>>
>> class file has wrong version 49.0, should be 48.0
>> Please remove or make sure it appears in the correct subdirectory of
>> the classpath.
>> import org.apache.commons.validator.Validator;
>> ^
>> 1 error
>>
>> BUILD FAILED
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven remote repositories and SNAPSHOT (was New Validator 1.2.0-dev dependency)
Posted by Wendy Smoak <ja...@wendysmoak.com>.
----- Original Message -----
From: "Don Brown" <mr...@twdata.org>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Monday, August 29, 2005 10:01 PM
Subject: Maven remote repositories and SNAPSHOT (was New Validator 1.2.0-dev
dependency)
> Ok, it should all be setup. Unfortunately, it has the limitation of using
> my personal remote repository which no one else can modify. Does the
> nightly builds publish SNAPSHOT jars anywhere? That would be darn useful
> for us.
>
> How to use SNAPSHOT:
> 1. Make the version in your project.xml "SNAPSHOT"
> 2. Publish the jar to a remote repository, in this case my
> "people.apache.org/~mrdon/repository"
> 3. Tell maven to also look in this new repository for jars by modifying
> project.properties. In this case, I added the following property:
> maven.repo.remote=http://people.apache.org/~mrdon/repository/,http://www.ibiblio.org/maven/
>
> To setup your own remote repository for Apache:
> 1. Ssh into your account at people.apache.org
> 2. Create a public_html directory if one doesn't exist
> 3. Create a public_html/repository then subdirectories for each project
> 4. Publish jars to your repository via scp. In this case, the following
> command worked well for me:
> scp target/commons-validator-1.2.0-dev.jar
> people.apache.org:public_html/repository/commons-validator/jars/commons-validator-SNAPSHOT.jar
>
> HTH,
>
> Don
>
> Wendy Smoak wrote:
>
>> From: "Don Brown" <mr...@twdata.org>
>>
>>> Doh, you are right. I updated it with the correct one. Perhaps this
>>> should be made a SNAPSHOT so maven will always try to download the
>>> latest one?
>>
>>
>> Yes! And then teach me how, so I can do it for Standalone Tiles and the
>> Shale build files. :)
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven remote repositories and SNAPSHOT (was New Validator 1.2.0-dev dependency)
Posted by Craig McClanahan <cr...@gmail.com>.
On 9/1/05, Ted Husted <te...@gmail.com> wrote:
>
> It says Shale is up to date at 265744, but the URL message is not there
> for me.
>
> Since Spring is under the Apache License, can't we just park this JAR
> with our own? We don't like to binaries in the repository, for
> technical reasons, but I don't think there would be a legal problem
> with tucking an Apache Licensed JAR in our snapshot repository.
>
> Has anyone asked Spring to make their JARs available in an Maven
> repository?
Which spring jars are you looking for? All the 1.2.2 jars other than webflow
*are* at ibiblio. And, at least in the Ant build, the dependency on webflow
is totally optional, so lacking it will have no impact.
If that (optionality at compile time) is too difficult to hack in to the
maven scripts, it'd be better for me to just move those classes elsewhere
anyway, since they aren't destned to be part of Shale -- having them here
was laziness on my part, not wanting to set up another build environment for
it :-).
Craig
-Ted.
>
> On 9/1/05, Wendy Smoak <ja...@wendysmoak.com> wrote:
> > From: "Ted Husted" <te...@gmail.com>
> >
> > > Here goes:
> > > Attempting to download spring-webflow-PR4.jar.
> > > WARNING: Failed to download spring-webflow-PR4.jar.
> >
> > This .jar file isn't available in a public repository, so you have to go
> > find it and put it in your local repository.
> >
> >
> http://sourceforge.net/project/showfiles.php?group_id=73357&package_id=148517&release_id=342750
> >
> > Unzip that and copy 'spring-webflow-PR4.jar' into
> > ${maven.repo.local}/repository/springframework/ . ( ${maven.repo.local}
> is
> > usually ~/.maven/ .)
> >
> > Once you get 'core-library' to build, the others should work.
> >
> > Also... when was the last time you did 'svn up' on
> /struts/current/shale/ ?
> > I added URLs to the dependencies last night, so it should have printed
> out a
> > message like "Try downloading from ... " when it couldn't find the
> webflow
> > .jar file.
> >
> > I updated the instructions on my site, and will change the BuildingShale
> > Wiki page later.
> > http://wiki.wsmoak.net/cgi-bin/wiki.pl?ShaleMavenBuild
> >
> > HTH,
> > --
> > Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Maven remote repositories and SNAPSHOT (was New Validator 1.2.0-dev dependency)
Posted by Ted Husted <te...@gmail.com>.
It says Shale is up to date at 265744, but the URL message is not there for me.
Since Spring is under the Apache License, can't we just park this JAR
with our own? We don't like to binaries in the repository, for
technical reasons, but I don't think there would be a legal problem
with tucking an Apache Licensed JAR in our snapshot repository.
Has anyone asked Spring to make their JARs available in an Maven repository?
-Ted.
On 9/1/05, Wendy Smoak <ja...@wendysmoak.com> wrote:
> From: "Ted Husted" <te...@gmail.com>
>
> > Here goes:
> > Attempting to download spring-webflow-PR4.jar.
> > WARNING: Failed to download spring-webflow-PR4.jar.
>
> This .jar file isn't available in a public repository, so you have to go
> find it and put it in your local repository.
>
> http://sourceforge.net/project/showfiles.php?group_id=73357&package_id=148517&release_id=342750
>
> Unzip that and copy 'spring-webflow-PR4.jar' into
> ${maven.repo.local}/repository/springframework/ . ( ${maven.repo.local} is
> usually ~/.maven/ .)
>
> Once you get 'core-library' to build, the others should work.
>
> Also... when was the last time you did 'svn up' on /struts/current/shale/ ?
> I added URLs to the dependencies last night, so it should have printed out a
> message like "Try downloading from ... " when it couldn't find the webflow
> .jar file.
>
> I updated the instructions on my site, and will change the BuildingShale
> Wiki page later.
> http://wiki.wsmoak.net/cgi-bin/wiki.pl?ShaleMavenBuild
>
> HTH,
> --
> Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven remote repositories and SNAPSHOT (was New Validator
1.2.0-dev dependency)
Posted by Wendy Smoak <ja...@wendysmoak.com>.
From: "Ted Husted" <te...@gmail.com>
> Here goes:
> Attempting to download spring-webflow-PR4.jar.
> WARNING: Failed to download spring-webflow-PR4.jar.
This .jar file isn't available in a public repository, so you have to go
find it and put it in your local repository.
http://sourceforge.net/project/showfiles.php?group_id=73357&package_id=148517&release_id=342750
Unzip that and copy 'spring-webflow-PR4.jar' into
${maven.repo.local}/repository/springframework/ . ( ${maven.repo.local} is
usually ~/.maven/ .)
Once you get 'core-library' to build, the others should work.
Also... when was the last time you did 'svn up' on /struts/current/shale/ ?
I added URLs to the dependencies last night, so it should have printed out a
message like "Try downloading from ... " when it couldn't find the webflow
.jar file.
I updated the instructions on my site, and will change the BuildingShale
Wiki page later.
http://wiki.wsmoak.net/cgi-bin/wiki.pl?ShaleMavenBuild
HTH,
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven remote repositories and SNAPSHOT (was New Validator 1.2.0-dev dependency)
Posted by Ted Husted <te...@gmail.com>.
On 9/1/05, Wendy Smoak <ja...@wendysmoak.com> wrote:
> The 'build-all' goal is usually run from the /struts/current/build. You're
> one level down, in the svn external under 'site', so the relative directory
> structure doesn't look right.
OK, that works.
> > When I try the instructions from the Shale Maven thread, many of the
> > unreleased JARS (the snapshots, I guess) are not downloaded.
>
> Can you post a build log? I just checked out struts/shale/trunk/ to a temp
> directory and
> $ maven build-all
> worked fine. There's only one SNAPSHOT dependency, on Tiles. If it's
> failing because of dependencies, it should be printing out messages.
Here goes:
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Starting the reactor...
Our processing order:
Shale Core Library
Shale Test Framework
Shale Clay Plugin
Shale Use Cases
+----------------------------------------
| Building Shale Framework... Shale Core Library
| Memory: 2M/4M
+----------------------------------------
Attempting to download tiles-core-SNAPSHOT.jar.
Attempting to download spring-webflow-PR4.jar.
WARNING: Failed to download spring-webflow-PR4.jar.
+----------------------------------------
| Building Shale Framework... Shale Test Framework
| Memory: 3M/4M
+----------------------------------------
Attempting to download shale-core-1.0.0-dev.jar.
WARNING: Failed to download shale-core-1.0.0-dev.jar.
+----------------------------------------
| Building Shale Framework... Shale Clay Plugin
| Memory: 3M/4M
+----------------------------------------
Attempting to download shale-core-1.0.0-dev.jar.
WARNING: Failed to download shale-core-1.0.0-dev.jar.
Attempting to download shale-test-1.0.0-dev.jar.
WARNING: Failed to download shale-test-1.0.0-dev.jar.
+----------------------------------------
| Building Shale Framework... Shale Use Cases
| Memory: 3M/4M
+----------------------------------------
Attempting to download shale-core-1.0.0-dev.jar.
WARNING: Failed to download shale-core-1.0.0-dev.jar.
Attempting to download shale-clay-1.0.0-dev.jar.
WARNING: Failed to download shale-clay-1.0.0-dev.jar.
Attempting to download shale-test-1.0.0-dev.jar.
WARNING: Failed to download shale-test-1.0.0-dev.jar.
BUILD SUCCESSFUL
Total time: 9 seconds
Again, I'm just using everything straight out of the box. I added
Maven to my path, but that's it.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven remote repositories and SNAPSHOT (was New Validator 1.2.0-dev dependency)
Posted by Wendy Smoak <ja...@wendysmoak.com>.
From: "Ted Husted" <te...@gmail.com>
> I'm not clear on where we stand with the alternate repositories.
>
> Do I need to make local changes to my setup to get Struts Classic or
> Struts Shale to build.
You shouldn't. Any additional repositories should be added to
'maven.repo.remote' in the 'project.properties' for that sub-project.
> Right now, Maven is refusing to build Struts Classic for me when I run
> it from site/build.
> It says the build is successful, but nothing actually happens.
The 'build-all' goal is usually run from the /struts/current/build. You're
one level down, in the svn external under 'site', so the relative directory
structure doesn't look right.
(The 'build-all' goal might work from any sub-project... I haven't tried it
elsewhere. And 'multiproject:site' needs to be run from
/struts/current/site to get the correct directory structure.)
> When I try the instructions from the Shale Maven thread, many of the
> unreleased JARS (the snapshots, I guess) are not downloaded.
Can you post a build log? I just checked out struts/shale/trunk/ to a temp
directory and
$ maven build-all
worked fine. There's only one SNAPSHOT dependency, on Tiles. If it's
failing because of dependencies, it should be printing out messages.
HTH,
--
Wendy Smoak
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven remote repositories and SNAPSHOT (was New Validator 1.2.0-dev dependency)
Posted by Wendy Smoak <ja...@wendysmoak.com>.
From: "Ted Husted" <te...@gmail.com>
> Right now, Maven is refusing to build Struts Classic for me when I run
> it from site/build.
Looking at it now...
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven remote repositories and SNAPSHOT (was New Validator 1.2.0-dev dependency)
Posted by Ted Husted <te...@gmail.com>.
I'm not clear on where we stand with the alternate repositories.
Do I need to make local changes to my setup to get Struts Classic or
Struts Shale to build.
Right now, Maven is refusing to build Struts Classic for me when I run
it from site/build.
It says the build is successful, but nothing actually happens.
When I try the instructions from the Shale Maven thread, many of the
unreleased JARS (the snapshots, I guess) are not downloaded.
Right now, I'm using Maven and Struts "out of the box", without any
custom changes to my local setup.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven remote repositories and SNAPSHOT (was New Validator 1.2.0-dev dependency)
Posted by Phil Steitz <ph...@gmail.com>.
You can also use http://cvs.apache.org/repository for snapshots. This is not
mirrored and is designated for internal use snapshot builds.
Phil
On 8/29/05, Wendy Smoak <ja...@wendysmoak.com> wrote:
>
> [Oops, wrong button]
>
> From: "Don Brown" <mr...@twdata.org>
>
> > Does the nightly builds publish SNAPSHOT jars anywhere? That would be
> > darn useful for us.
>
> James and I were discussing SNAPSHOTs as being less frequent than nightly,
> just when it's stable and something interesting has changed. Could we use
> http://struts.apache.org/maven ? That way everyone would have access to
> publish them.
>
> > 2. Publish the jar to a remote repository, in this case my
> > "people.apache.org/~mrdon/repository<http://people.apache.org/~mrdon/repository>
> "
>
> They don't have to be signed or in any way "official" then? I wasn't sure
> if there were rules... And it seems like I retrieved a snapshot of some
> project recently and there were extra text files sitting near the .jar
> file.
> Maybe those are for Maven2, though.
>
> Thanks!
> --
> Wendy
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Maven remote repositories and SNAPSHOT (was New Validator 1.2.0-dev dependency)
Posted by Wendy Smoak <ja...@wendysmoak.com>.
[Oops, wrong button]
From: "Don Brown" <mr...@twdata.org>
> Does the nightly builds publish SNAPSHOT jars anywhere? That would be
> darn useful for us.
James and I were discussing SNAPSHOTs as being less frequent than nightly,
just when it's stable and something interesting has changed. Could we use
http://struts.apache.org/maven ? That way everyone would have access to
publish them.
> 2. Publish the jar to a remote repository, in this case my
> "people.apache.org/~mrdon/repository"
They don't have to be signed or in any way "official" then? I wasn't sure
if there were rules... And it seems like I retrieved a snapshot of some
project recently and there were extra text files sitting near the .jar file.
Maybe those are for Maven2, though.
Thanks!
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Maven remote repositories and SNAPSHOT (was New Validator 1.2.0-dev
dependency)
Posted by Don Brown <mr...@twdata.org>.
Ok, it should all be setup. Unfortunately, it has the limitation of
using my personal remote repository which no one else can modify. Does
the nightly builds publish SNAPSHOT jars anywhere? That would be darn
useful for us.
How to use SNAPSHOT:
1. Make the version in your project.xml "SNAPSHOT"
2. Publish the jar to a remote repository, in this case my
"people.apache.org/~mrdon/repository"
3. Tell maven to also look in this new repository for jars by modifying
project.properties. In this case, I added the following property:
maven.repo.remote=http://people.apache.org/~mrdon/repository/,http://www.ibiblio.org/maven/
To setup your own remote repository for Apache:
1. Ssh into your account at people.apache.org
2. Create a public_html directory if one doesn't exist
3. Create a public_html/repository then subdirectories for each project
4. Publish jars to your repository via scp. In this case, the
following command worked well for me:
scp target/commons-validator-1.2.0-dev.jar
people.apache.org:public_html/repository/commons-validator/jars/commons-validator-SNAPSHOT.jar
HTH,
Don
Wendy Smoak wrote:
> From: "Don Brown" <mr...@twdata.org>
>
>> Doh, you are right. I updated it with the correct one. Perhaps this
>> should be made a SNAPSHOT so maven will always try to download the
>> latest one?
>
>
> Yes! And then teach me how, so I can do it for Standalone Tiles and
> the Shale build files. :)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: New Validator 1.2.0-dev dependency
Posted by Wendy Smoak <ja...@wendysmoak.com>.
From: "Don Brown" <mr...@twdata.org>
> Doh, you are right. I updated it with the correct one. Perhaps this
> should be made a SNAPSHOT so maven will always try to download the latest
> one?
Yes! And then teach me how, so I can do it for Standalone Tiles and the
Shale build files. :)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: New Validator 1.2.0-dev dependency
Posted by Don Brown <mr...@twdata.org>.
Wendy Smoak wrote:
> Don, was that .jar file compiled with JDK 1.5 by any chance?
Doh, you are right. I updated it with the correct one. Perhaps this
should be made a SNAPSHOT so maven will always try to download the
latest one?
Don
>
> java:compile:
> [echo] Compiling to e:\svn\struts\current\core/target/classes
> [echo]
> ==========================================================
>
> NOTE: Targetting JVM 1.4, classes
> will not run on earlier JVMs
>
> ==========================================================
>
> [javac] Compiling 146 source files to
> E:\svn\struts\current\core\target\classes
> E:\svn\struts\current\core\src\share\org\apache\struts\validator\ValidatorForm.j
>
> ava:29: cannot access org.apache.commons.validator.Validator
> bad class file: C:\Documents and
> Settings\wendy\.maven\repository\commons-validator\jars\commons-validator-1.2.0-dev.jar(org/apache/commons/validator/Validator.class)
>
> class file has wrong version 49.0, should be 48.0
> Please remove or make sure it appears in the correct subdirectory of
> the classpath.
> import org.apache.commons.validator.Validator;
> ^
> 1 error
>
> BUILD FAILED
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: New Validator 1.2.0-dev dependency
Posted by Wendy Smoak <ja...@wendysmoak.com>.
> In case you missed it, I changed our validator dependency to 1.2.0-dev,
> which it really already was, but now it is enforced. Since most folks
> don't have a commons-validator-1.2.0-dev.jar lying around, I added my
> apache remote jar repository as an alternate for Maven to retrieve
> from. This repository contains the validator jar so folks don't have to
> checkout validator and build their own jar.
Don, was that .jar file compiled with JDK 1.5 by any chance?
java:compile:
[echo] Compiling to e:\svn\struts\current\core/target/classes
[echo]
==========================================================
NOTE: Targetting JVM 1.4, classes
will not run on earlier JVMs
==========================================================
[javac] Compiling 146 source files to
E:\svn\struts\current\core\target\classes
E:\svn\struts\current\core\src\share\org\apache\struts\validator\ValidatorForm.j
ava:29: cannot access org.apache.commons.validator.Validator
bad class file: C:\Documents and
Settings\wendy\.maven\repository\commons-validator\jars\commons-validator-1.2.0-dev.jar(org/apache/commons/validator/Validator.class)
class file has wrong version 49.0, should be 48.0
Please remove or make sure it appears in the correct subdirectory of the
classpath.
import org.apache.commons.validator.Validator;
^
1 error
BUILD FAILED
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: New Validator 1.2.0-dev dependency
Posted by Don Brown <mr...@twdata.org>.
Sure, that would be a much better way to do it. I'm trying to deploy
validator's SNAPSHOT, but I don't believe I have a private key in my
home directory, or at least none that I'm aware of.
Don
Joe Germuska wrote:
> At 9:24 PM -0700 8/29/05, Don Brown wrote:
>
>> In case you missed it, I changed our validator dependency to
>> 1.2.0-dev, which it really already was, but now it is enforced. Since
>> most folks don't have a commons-validator-1.2.0-dev.jar lying around,
>> I added my apache remote jar repository as an alternate for Maven to
>> retrieve from. This repository contains the validator jar so folks
>> don't have to checkout validator and build their own jar.
>> Is this ok, or is there a better way to handle this?
>
>
> I would only suggest that rather than using Don's home directory, we use
> the non-mirrored Apache repository:
>
> http://cvs.apache.org/repository/
>
> If you edit your ~/build.properties and add lines like the below
> (editded for user name and private key file location) then you can use
>
> maven jar:deploy-snapshot -Dmaven.repo.list=apache
>
> to create a JAR and move it via SCP to the server. (Of course, if
> someone were doing a regular release, they would replace 'apache' with
> 'ibiblio-mirror', and of course, those names are arbitrary as long as
> the values in maven.repo.list match some defined maven.repo.X value.
>
> I'd also suggest changing the order of "maven.repo.remote" to favor
> ibiblio.org, since for non-SNAPSHOT dependencies, Maven goes in order
> but stops as soon as it is satisfied. May as well minimize wasted HTTP
> calls to cvs.apache.org.
>
> Joe
>
>
> #---- Properties for Maven Artifact PlugIn
> #---- http://maven.apache.org/reference/plugins/artifact/properties.html
> #IBiblio Mirror
> maven.repo.ibiblio-mirror=scp://people.apache.org
> maven.repo.ibiblio-mirror.directory=/www/www.apache.org/dist/java-repository
>
> maven.repo.ibiblio-mirror.group=apcvs
> maven.repo.ibiblio-mirror.username=germuska
> maven.repo.ibiblio-mirror.privatekey=/Users/germuska/.ssh/id_rsa
>
> # Apache repository
> maven.repo.apache=scp://people.apache.org
> maven.repo.apache.directory=/www/cvs.apache.org/repository
> maven.repo.apache.group=apcvs
> maven.repo.apache.username=germuska
> maven.repo.apache.privatekey=/Users/germuska/.ssh/id_rsa
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: New Validator 1.2.0-dev dependency
Posted by Joe Germuska <Jo...@Germuska.com>.
At 9:24 PM -0700 8/29/05, Don Brown wrote:
>In case you missed it, I changed our validator dependency to
>1.2.0-dev, which it really already was, but now it is enforced.
>Since most folks don't have a commons-validator-1.2.0-dev.jar lying
>around, I added my apache remote jar repository as an alternate for
>Maven to retrieve from. This repository contains the validator jar
>so folks don't have to checkout validator and build their own jar.
>Is this ok, or is there a better way to handle this?
I would only suggest that rather than using Don's home directory, we
use the non-mirrored Apache repository:
http://cvs.apache.org/repository/
If you edit your ~/build.properties and add lines like the below
(editded for user name and private key file location) then you can use
maven jar:deploy-snapshot -Dmaven.repo.list=apache
to create a JAR and move it via SCP to the server. (Of course, if
someone were doing a regular release, they would replace 'apache'
with 'ibiblio-mirror', and of course, those names are arbitrary as
long as the values in maven.repo.list match some defined maven.repo.X
value.
I'd also suggest changing the order of "maven.repo.remote" to favor
ibiblio.org, since for non-SNAPSHOT dependencies, Maven goes in order
but stops as soon as it is satisfied. May as well minimize wasted
HTTP calls to cvs.apache.org.
Joe
#---- Properties for Maven Artifact PlugIn
#---- http://maven.apache.org/reference/plugins/artifact/properties.html
#IBiblio Mirror
maven.repo.ibiblio-mirror=scp://people.apache.org
maven.repo.ibiblio-mirror.directory=/www/www.apache.org/dist/java-repository
maven.repo.ibiblio-mirror.group=apcvs
maven.repo.ibiblio-mirror.username=germuska
maven.repo.ibiblio-mirror.privatekey=/Users/germuska/.ssh/id_rsa
# Apache repository
maven.repo.apache=scp://people.apache.org
maven.repo.apache.directory=/www/cvs.apache.org/repository
maven.repo.apache.group=apcvs
maven.repo.apache.username=germuska
maven.repo.apache.privatekey=/Users/germuska/.ssh/id_rsa
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"Narrow minds are weapons made for mass destruction" -The Ex
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: New Validator 1.2.0-dev dependency
Posted by James Mitchell <ja...@mac.com>.
That's perfect. The nightly build will automatically pickup the new
repository location and dependency....gotta love it!
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: jmitchell@apache.org
Skype: callto://jmitchtx
On Aug 30, 2005, at 12:24 AM, Don Brown wrote:
> In case you missed it, I changed our validator dependency to 1.2.0-
> dev, which it really already was, but now it is enforced. Since
> most folks don't have a commons-validator-1.2.0-dev.jar lying
> around, I added my apache remote jar repository as an alternate for
> Maven to retrieve from. This repository contains the validator jar
> so folks don't have to checkout validator and build their own jar.
> Is this ok, or is there a better way to handle this?
>
> Don
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org