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 2006/03/23 02:33:25 UTC
Maven 2 repository containing Action 1.3?
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: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven 2 repository containing Action 1.3?
Posted by Don Brown <mr...@twdata.org>.
Either will work, thanks.
Don
Wendy Smoak wrote:
> On 3/22/06, Don Brown <mr...@twdata.org> 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-repository/org/apache/struts/tiles/
>
> (For that to work, you need a <server> configured in settings.xml. See:
> http://svn.apache.org/repos/asf/struts/shale/trunk/build/maven2/README.txt )
>
> I don't care for the timestamps in the filenames, but I haven't come
> across an option to turn it off. (I'd rather just see one file,
> struts-action-1.3.2-SNAPSHOT.jar, that gets overwritten each time we
> publish a snapshot.)
>
> Do you need the test builds published, or are the snapshots okay?
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> 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 2 repository containing Action 1.3?
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/22/06, Don Brown <mr...@twdata.org> 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-repository/org/apache/struts/tiles/
(For that to work, you need a <server> configured in settings.xml. See:
http://svn.apache.org/repos/asf/struts/shale/trunk/build/maven2/README.txt )
I don't care for the timestamps in the filenames, but I haven't come
across an option to turn it off. (I'd rather just see one file,
struts-action-1.3.2-SNAPSHOT.jar, that gets overwritten each time we
publish a snapshot.)
Do you need the test builds published, or are the snapshots okay?
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven 2 repository containing Action 1.3?
Posted by Alexandre Poitras <al...@gmail.com>.
+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 <ni...@capgemini.com> wrote:
>
> 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.struts.tiles", "org.apache.struts.taglibs" groupIds with
> only one artifact per groupId.
>
> Wendy Smoak a écrit :
> > On 3/22/06, Martin Cooper <ma...@apache.org> wrote:
> >
> >
> >> Meaning that the dependency would look like this?
> >>
> >> <dependency>
> >> <groupId>org.apache.struts.action</groupId>
> >> <artifactId>struts-action</artifactId>
> >> <version>1.3.0</version>
> >> </dependency>
> >>
> >
> > Yes.
> >
> >
> >> I don't think the version numbers were changed before the 1.3.0 tags,
> >>
> >>> so if you want to deploy the 1.3.0 jars from the distributions, a
> >>> little revisionist history will be necessary for the version numbers
> >>> as well as the groupId.
> >>>
> >> Not sure I understand this. If I wanted to create a local or remote repo
> >> that satisfied the above dependency (assuming it's correct), what do I need
> >> to do?
> >>
> >
> > Edit the pom.xml files from the 1.3.0 tag or distribution to fix the
> > version and groupId. Depending on whether you want to build from
> > source or just install an existing jar, either mvn install or mvn
> > install:install-file with appropriate parameters:
> > http://maven.apache.org/plugins/maven-install-plugin/
> >
> > For deploying to a remote repository (maven-snapshot-repository) I've
> > just been using 'mvn deploy:deploy-file'. There's an example in the
> > shale/build/maven2 README file:
> > http://svn.apache.org/repos/asf/struts/shale/trunk/build/maven2/README.txt
> >
> > HTH,
> > --
> > Wendy
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
> >
>
> This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Alexandre Poitras
Québec, Canada
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven 2 repository containing Action 1.3?
Posted by Joe Germuska <Jo...@Germuska.com>.
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, I just don't think it's
necessary to have that extra layer in there.
Not something I feel extremely strongly about, but since two other
folks brought it up, I figured I'd chime in.
Joe
--
Joe Germuska
Joe@Germuska.com * http://blog.germuska.com
"You really can't burn anything out by trying something new, and
even if you can burn it out, it can be fixed. Try something new."
-- Robert Moog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven 2 repository containing Action 1.3?
Posted by Martin Cooper <ma...@apache.org>.
On 3/23/06, Alexandre Poitras <al...@gmail.com> 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
> | |
> | |--- all the sub projects share the groupId
> org.apache.struts.action
> |
> |
> ---------------- groupdId : org.apache.struts
> artifactId : shale
> |
> |--- all the sub projects share the groupId
> org.apache.struts.shale
>
> Those are best practices recommended by the Maven team.
I'm probably missing something, since my M2 knowledge is minimal at the
moment (but I'm working on that ;), but what you have above implies compound
artifacts. I thought an artifact was a unit (e.g. one jar file), no? In the
above, if I declared a dependency like so:
<groupId>org.apache</groupId>
<artifactId>struts</artifactId>
what would I get? My expectation is that I'd get an error. ;-)
--
Martin Cooper
On 3/23/06, Martin Cooper <ma...@apache.org> wrote:
> > On 3/22/06, Nicolas De Loof <ni...@capgemini.com> 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 two groups we would have today would be
> > org.apache.struts.action and org.apache.struts.shale. The 'action'
> > references the Action framework, and not the 'action' package of the
> Action
> > framework.
> >
> > AFAIK groupId is expected to gather artifacts from the same development
> > > team.
> > > For example, "org.apache.maven" groupId is used for all maven
> artifacts
> >
> >
> > The main difference that I see here is that the maven artifacts within
> that
> > group are intended to work together, while our 'action' and 'shale' will
> > very rarely be used together, and are really alternatives.
> >
> > Using "org.apache.struts.action" means there will also be
> > > "org.apache.struts.tiles", "org.apache.struts.taglibs" groupIds with
> > > only one artifact per groupId.
> >
> >
> > No, it doesn't. As I described above, the 'action' is not the Java
> package
> > but the framework.
> >
> > --
> > Martin Cooper
> >
> >
> > Wendy Smoak a écrit :
> > > > On 3/22/06, Martin Cooper <ma...@apache.org> wrote:
> > > >
> > > >
> > > >> Meaning that the dependency would look like this?
> > > >>
> > > >> <dependency>
> > > >> <groupId>org.apache.struts.action</groupId>
> > > >> <artifactId>struts-action</artifactId>
> > > >> <version>1.3.0</version>
> > > >> </dependency>
> > > >>
> > > >
> > > > Yes.
> > > >
> > > >
> > > >> I don't think the version numbers were changed before the 1.3.0tags,
> > > >>
> > > >>> so if you want to deploy the 1.3.0 jars from the distributions, a
> > > >>> little revisionist history will be necessary for the version
> numbers
> > > >>> as well as the groupId.
> > > >>>
> > > >> Not sure I understand this. If I wanted to create a local or remote
> > > repo
> > > >> that satisfied the above dependency (assuming it's correct), what
> do I
> > > need
> > > >> to do?
> > > >>
> > > >
> > > > Edit the pom.xml files from the 1.3.0 tag or distribution to fix the
> > > > version and groupId. Depending on whether you want to build from
> > > > source or just install an existing jar, either mvn install or mvn
> > > > install:install-file with appropriate parameters:
> > > > http://maven.apache.org/plugins/maven-install-plugin/
> > > >
> > > > For deploying to a remote repository (maven-snapshot-repository)
> I've
> > > > just been using 'mvn deploy:deploy-file'. There's an example in
> the
> > > > shale/build/maven2 README file:
> > > >
> > >
> http://svn.apache.org/repos/asf/struts/shale/trunk/build/maven2/README.txt
> > > >
> > > > HTH,
> > > > --
> > > > Wendy
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > > For additional commands, e-mail: dev-help@struts.apache.org
> > > >
> > > >
> > > >
> > >
> > > This message contains information that may be privileged or
> confidential
> > > and is the property of the Capgemini Group. It is intended only for
> the
> > > person to whom it is addressed. If you are not the intended
> recipient, you
> > > are not authorized to read, print, retain, copy,
> disseminate, distribute,
> > > or use this message or any part thereof. If you receive this message
> in
> > > error, please notify the sender immediately and delete all copies of
> this
> > > message.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: dev-help@struts.apache.org
> > >
> > >
> >
> >
>
>
> --
> Alexandre Poitras
> Québec, Canada
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Maven 2 repository containing Action 1.3?
Posted by Alexandre Poitras <al...@gmail.com>.
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.
On 3/23/06, Wendy Smoak <ws...@gmail.com> wrote:
> On 3/23/06, Alexandre Poitras <al...@gmail.com> 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
> > | |
> > | |--- all the sub projects share the groupId
> > org.apache.struts.action
> > |
> > |
> > ---------------- groupdId : org.apache.struts
> > artifactId : shale
> > |
> > |--- all the sub projects share the groupId
> > org.apache.struts.shale
> >
> > Those are best practices recommended by the Maven team.
>
> AFAICT, this is exactly what I'm suggesting -- that all the Action
> related artifacts share the 'org.apache.struts.action' groupId.
>
> I didn't understand your initial comment about a "parent project"
> though. We don't have one. We have three separate frameworks --
> Action, Shale, and Tiles.
>
> Shale and Tiles already live in org.apache.struts.shale and
> org.apache.struts.tiles, respectively:
> http://cvs.apache.org/maven-snapshot-repository/org/apache/struts/
>
> (Martin, you wouldn't declare a dependency on anything at the
> org.apache:struts level... there won't be any build artifacts at that
> level, it's just an administrative grouping.)
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Alexandre Poitras
Québec, Canada
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven 2 repository containing Action 1.3?
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/23/06, Alexandre Poitras <al...@gmail.com> 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
> | |
> | |--- all the sub projects share the groupId
> org.apache.struts.action
> |
> |
> ---------------- groupdId : org.apache.struts
> artifactId : shale
> |
> |--- all the sub projects share the groupId
> org.apache.struts.shale
>
> Those are best practices recommended by the Maven team.
AFAICT, this is exactly what I'm suggesting -- that all the Action
related artifacts share the 'org.apache.struts.action' groupId.
I didn't understand your initial comment about a "parent project"
though. We don't have one. We have three separate frameworks --
Action, Shale, and Tiles.
Shale and Tiles already live in org.apache.struts.shale and
org.apache.struts.tiles, respectively:
http://cvs.apache.org/maven-snapshot-repository/org/apache/struts/
(Martin, you wouldn't declare a dependency on anything at the
org.apache:struts level... there won't be any build artifacts at that
level, it's just an administrative grouping.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven 2 repository containing Action 1.3?
Posted by Alexandre Poitras <al...@gmail.com>.
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.action
|
|
---------------- groupdId : org.apache.struts
artifactId : shale
|
|--- all the sub projects share the groupId
org.apache.struts.shale
Those are best practices recommended by the Maven team.
On 3/23/06, Martin Cooper <ma...@apache.org> wrote:
> On 3/22/06, Nicolas De Loof <ni...@capgemini.com> 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 two groups we would have today would be
> org.apache.struts.action and org.apache.struts.shale. The 'action'
> references the Action framework, and not the 'action' package of the Action
> framework.
>
> AFAIK groupId is expected to gather artifacts from the same development
> > team.
> > For example, "org.apache.maven" groupId is used for all maven artifacts
>
>
> The main difference that I see here is that the maven artifacts within that
> group are intended to work together, while our 'action' and 'shale' will
> very rarely be used together, and are really alternatives.
>
> Using "org.apache.struts.action" means there will also be
> > "org.apache.struts.tiles", "org.apache.struts.taglibs" groupIds with
> > only one artifact per groupId.
>
>
> No, it doesn't. As I described above, the 'action' is not the Java package
> but the framework.
>
> --
> Martin Cooper
>
>
> Wendy Smoak a écrit :
> > > On 3/22/06, Martin Cooper <ma...@apache.org> wrote:
> > >
> > >
> > >> Meaning that the dependency would look like this?
> > >>
> > >> <dependency>
> > >> <groupId>org.apache.struts.action</groupId>
> > >> <artifactId>struts-action</artifactId>
> > >> <version>1.3.0</version>
> > >> </dependency>
> > >>
> > >
> > > Yes.
> > >
> > >
> > >> I don't think the version numbers were changed before the 1.3.0 tags,
> > >>
> > >>> so if you want to deploy the 1.3.0 jars from the distributions, a
> > >>> little revisionist history will be necessary for the version numbers
> > >>> as well as the groupId.
> > >>>
> > >> Not sure I understand this. If I wanted to create a local or remote
> > repo
> > >> that satisfied the above dependency (assuming it's correct), what do I
> > need
> > >> to do?
> > >>
> > >
> > > Edit the pom.xml files from the 1.3.0 tag or distribution to fix the
> > > version and groupId. Depending on whether you want to build from
> > > source or just install an existing jar, either mvn install or mvn
> > > install:install-file with appropriate parameters:
> > > http://maven.apache.org/plugins/maven-install-plugin/
> > >
> > > For deploying to a remote repository (maven-snapshot-repository) I've
> > > just been using 'mvn deploy:deploy-file'. There's an example in the
> > > shale/build/maven2 README file:
> > >
> > http://svn.apache.org/repos/asf/struts/shale/trunk/build/maven2/README.txt
> > >
> > > HTH,
> > > --
> > > Wendy
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: dev-help@struts.apache.org
> > >
> > >
> > >
> >
> > This message contains information that may be privileged or confidential
> > and is the property of the Capgemini Group. It is intended only for the
> > person to whom it is addressed. If you are not the intended recipient, you
> > are not authorized to read, print, retain, copy, disseminate, distribute,
> > or use this message or any part thereof. If you receive this message in
> > error, please notify the sender immediately and delete all copies of this
> > message.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
--
Alexandre Poitras
Québec, Canada
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven 2 repository containing Action 1.3?
Posted by Martin Cooper <ma...@apache.org>.
On 3/22/06, Nicolas De Loof <ni...@capgemini.com> 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 two groups we would have today would be
org.apache.struts.action and org.apache.struts.shale. The 'action'
references the Action framework, and not the 'action' package of the Action
framework.
AFAIK groupId is expected to gather artifacts from the same development
> team.
> For example, "org.apache.maven" groupId is used for all maven artifacts
The main difference that I see here is that the maven artifacts within that
group are intended to work together, while our 'action' and 'shale' will
very rarely be used together, and are really alternatives.
Using "org.apache.struts.action" means there will also be
> "org.apache.struts.tiles", "org.apache.struts.taglibs" groupIds with
> only one artifact per groupId.
No, it doesn't. As I described above, the 'action' is not the Java package
but the framework.
--
Martin Cooper
Wendy Smoak a écrit :
> > On 3/22/06, Martin Cooper <ma...@apache.org> wrote:
> >
> >
> >> Meaning that the dependency would look like this?
> >>
> >> <dependency>
> >> <groupId>org.apache.struts.action</groupId>
> >> <artifactId>struts-action</artifactId>
> >> <version>1.3.0</version>
> >> </dependency>
> >>
> >
> > Yes.
> >
> >
> >> I don't think the version numbers were changed before the 1.3.0 tags,
> >>
> >>> so if you want to deploy the 1.3.0 jars from the distributions, a
> >>> little revisionist history will be necessary for the version numbers
> >>> as well as the groupId.
> >>>
> >> Not sure I understand this. If I wanted to create a local or remote
> repo
> >> that satisfied the above dependency (assuming it's correct), what do I
> need
> >> to do?
> >>
> >
> > Edit the pom.xml files from the 1.3.0 tag or distribution to fix the
> > version and groupId. Depending on whether you want to build from
> > source or just install an existing jar, either mvn install or mvn
> > install:install-file with appropriate parameters:
> > http://maven.apache.org/plugins/maven-install-plugin/
> >
> > For deploying to a remote repository (maven-snapshot-repository) I've
> > just been using 'mvn deploy:deploy-file'. There's an example in the
> > shale/build/maven2 README file:
> >
> http://svn.apache.org/repos/asf/struts/shale/trunk/build/maven2/README.txt
> >
> > HTH,
> > --
> > Wendy
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
> >
>
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain, copy, disseminate, distribute,
> or use this message or any part thereof. If you receive this message in
> error, please notify the sender immediately and delete all copies of this
> message.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Maven 2 repository containing Action 1.3?
Posted by Nicolas De Loof <ni...@capgemini.com>.
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.struts.tiles", "org.apache.struts.taglibs" groupIds with
only one artifact per groupId.
Wendy Smoak a écrit :
> On 3/22/06, Martin Cooper <ma...@apache.org> wrote:
>
>
>> Meaning that the dependency would look like this?
>>
>> <dependency>
>> <groupId>org.apache.struts.action</groupId>
>> <artifactId>struts-action</artifactId>
>> <version>1.3.0</version>
>> </dependency>
>>
>
> Yes.
>
>
>> I don't think the version numbers were changed before the 1.3.0 tags,
>>
>>> so if you want to deploy the 1.3.0 jars from the distributions, a
>>> little revisionist history will be necessary for the version numbers
>>> as well as the groupId.
>>>
>> Not sure I understand this. If I wanted to create a local or remote repo
>> that satisfied the above dependency (assuming it's correct), what do I need
>> to do?
>>
>
> Edit the pom.xml files from the 1.3.0 tag or distribution to fix the
> version and groupId. Depending on whether you want to build from
> source or just install an existing jar, either mvn install or mvn
> install:install-file with appropriate parameters:
> http://maven.apache.org/plugins/maven-install-plugin/
>
> For deploying to a remote repository (maven-snapshot-repository) I've
> just been using 'mvn deploy:deploy-file'. There's an example in the
> shale/build/maven2 README file:
> http://svn.apache.org/repos/asf/struts/shale/trunk/build/maven2/README.txt
>
> HTH,
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
>
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven 2 repository containing Action 1.3?
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/22/06, Martin Cooper <ma...@apache.org> wrote:
> Meaning that the dependency would look like this?
>
> <dependency>
> <groupId>org.apache.struts.action</groupId>
> <artifactId>struts-action</artifactId>
> <version>1.3.0</version>
> </dependency>
Yes.
> I don't think the version numbers were changed before the 1.3.0 tags,
> > so if you want to deploy the 1.3.0 jars from the distributions, a
> > little revisionist history will be necessary for the version numbers
> > as well as the groupId.
>
> Not sure I understand this. If I wanted to create a local or remote repo
> that satisfied the above dependency (assuming it's correct), what do I need
> to do?
Edit the pom.xml files from the 1.3.0 tag or distribution to fix the
version and groupId. Depending on whether you want to build from
source or just install an existing jar, either mvn install or mvn
install:install-file with appropriate parameters:
http://maven.apache.org/plugins/maven-install-plugin/
For deploying to a remote repository (maven-snapshot-repository) I've
just been using 'mvn deploy:deploy-file'. There's an example in the
shale/build/maven2 README file:
http://svn.apache.org/repos/asf/struts/shale/trunk/build/maven2/README.txt
HTH,
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Maven 2 repository containing Action 1.3?
Posted by Martin Cooper <ma...@apache.org>.
On 3/22/06, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 3/22/06, Don Brown <mr...@twdata.org> 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-snapshot-repository, but first we have to change
> the groupId for the Action sub-projects. I think it should be
> org.apache.struts.action.
Meaning that the dependency would look like this?
<dependency>
<groupId>org.apache.struts.action</groupId>
<artifactId>struts-action</artifactId>
<version>1.3.0</version>
</dependency>
I don't think the version numbers were changed before the 1.3.0 tags,
> so if you want to deploy the 1.3.0 jars from the distributions, a
> little revisionist history will be necessary for the version numbers
> as well as the groupId.
Not sure I understand this. If I wanted to create a local or remote repo
that satisfied the above dependency (assuming it's correct), what do I need
to do?
--
Martin Cooper
--
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Maven 2 repository containing Action 1.3?
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/22/06, Don Brown <mr...@twdata.org> 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-snapshot-repository, but first we have to change
the groupId for the Action sub-projects. I think it should be
org.apache.struts.action.
I don't think the version numbers were changed before the 1.3.0 tags,
so if you want to deploy the 1.3.0 jars from the distributions, a
little revisionist history will be necessary for the version numbers
as well as the groupId.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org