Either will work, thanks.
Don
Wendy Smoak wrote:
On 3/22/06, Don Brown <[EMAIL PROTECTED]> wrote:
Is there a Maven 2 repository that contains Action 1.3 jars?
These were done with 'mvn deploy' from struts/current/build:
http://cvs.apache.org/maven-snapshot-repository/org/apache/
On 3/22/06, Don Brown <[EMAIL PROTECTED]> wrote:
> Is there a Maven 2 repository that contains Action 1.3 jars?
These were done with 'mvn deploy' from struts/current/build:
http://cvs.apache.org/maven-snapshot-repository/org/apache/struts/action/
http://cvs.apache.org/maven-snapshot-reposi
I see, I thought you had a global struts pom project plus a specific
pom project for every subprojects. Maven team usually suggests in a
multi-modules project to append the parent artifactId to the children
module's groupId (to conform to the directory structure).
So everything looks fine then.
O
On 3/23/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
> Well, I think it would be better to use a 3 levels project like this :
>
> groupdId : org.apache
> artifactId : struts
> |
> groupdId : org.apache.struts
> |artifactId : action
> | |
> |
On 3/23/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
>
> Well, I think it would be better to use a 3 levels project like this :
>
> groupdId : org.apache
> artifactId : struts
> |
> groupdId : org.apache.struts
> |artifactId : action
> | |
> |
Well, I think it would be better to use a 3 levels project like this :
groupdId : org.apache
artifactId : struts
|
groupdId : org.apache.struts
|artifactId : action
| |
| |--- all the sub projects share the groupId
org.apache.struts.
On 3/22/06, Nicolas De Loof <[EMAIL PROTECTED]> wrote:
>
>
> Why use "org.apache.struts.action" and not just "org.apache.struts" ?
Since I didn't create it, I can't give you a definitive answer, but my
assumption is that it allows us to have different groups for our different
"products". So the t
At 8:37 AM +0100 3/23/06, Nicolas De Loof wrote:
Why use "org.apache.struts.action" and not just "org.apache.struts" ?
I'm inclined to agree with Nico. I assume Wendy's intention was to
partition struts-action and struts-shale, which doesn't go as far as
Nico's extrapolation, but in any case
+1, the groudId org.apache.struts.action should be reserved for the
children modules and not the parent project.
On 3/23/06, Nicolas De Loof <[EMAIL PROTECTED]> wrote:
>
> Why use "org.apache.struts.action" and not just "org.apache.struts" ?
>
> AFAIK groupId is expected to gather artifacts from t
Why use "org.apache.struts.action" and not just "org.apache.struts" ?
AFAIK groupId is expected to gather artifacts from the same development
team.
For example, "org.apache.maven" groupId is used for all maven artifacts
Using "org.apache.struts.action" means there will also be
"org.apache.st
On 3/22/06, Martin Cooper <[EMAIL PROTECTED]> wrote:
> Meaning that the dependency would look like this?
>
>
> org.apache.struts.action
> struts-action
> 1.3.0
>
Yes.
> I don't think the version numbers were changed before the 1.3.0 tags,
> > so if you want to deploy
On 3/22/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>
> On 3/22/06, Don Brown <[EMAIL PROTECTED]> wrote:
>
> > Is there a Maven 2 repository that contains Action 1.3 jars? I know
> Apache has a Maven 1 repository, but does it have a
> > Maven 2 yet? I'm trying to use Maven 2 for my work with Actio
On 3/22/06, Don Brown <[EMAIL PROTECTED]> wrote:
> Is there a Maven 2 repository that contains Action 1.3 jars? I know Apache
> has a Maven 1 repository, but does it have a
> Maven 2 yet? I'm trying to use Maven 2 for my work with Action 2.
There is an m2 repo available at
cvs.apache.org/maven
Is there a Maven 2 repository that contains Action 1.3 jars? I know Apache has a Maven 1 repository, but does it have a
Maven 2 yet? I'm trying to use Maven 2 for my work with Action 2.
Thanks,
Don
-
To unsubscribe, e-mail:
14 matches
Mail list logo