You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Joe Germuska <jo...@germuska.com> on 2007/01/12 21:05:21 UTC
mvn deployment best practices? (Re: Permissions problems deploying to snapshot repo)
Great -- and I just verified that I am able to deploy, which I did, for
struts-annotations.
That leads me to a couple of small "practice" questions for the team.
First, I really like having source code in the maven repository, so that mvn
eclipse:eclipse -DdownloadSources=true can get them all and wire them into
my project. I can get them deployed by using
mvn compile source:jar deploy
instead of
mvn deploy
but I might forget, as might the rest of the team. Is there a way we can
configure Maven to always deploy sources? Does anyone object to always
deploying sources?
Secondly, do we have any rules, or even guidelines, about when we should
deploy SNAPSHOTs to the repo? I can't think of any particular reason, but I
don't want to just bust off doing it whenever the whim strikes me, unless
people think that's OK.
Joe
On 1/12/07, Don Brown <mr...@twdata.org> wrote:
>
> Fixed.
>
> Don
>
> Joe Germuska wrote:
> > Hey, I just sent this to users@struts... and when I went to build a new
> > snapshot of struts-annotations, I got a "permission denied"
> >
> > Turns out the existing file is owned by mrdon:apcvs with 644 perms.
> >
> > I think we need to make sure everyone who does deployments adds
> > permissions
> > configs to their ~/.m2/settings.xml file
> >
> > <filePermissions>664</filePermissions>
> > <directoryPermissions>775</directoryPermissions>
> >
> > as described here:
> > http://maven.apache.org/settings.html
> >
> > In the meantime, Don, can you (or someone with sudo privs) execute
> > chmod 664
> >
> /www/people.apache.org/repo/m2-snapshot-repository/org/apache/struts/struts-annotations/1.0-SNAPSHOT/struts-
> >
> > annotations-1.0-SNAPSHOT.jar
> >
> > on the repo server?
> >
> > Joe
> >
> > On 1/12/07, Joe Germuska <jo...@germuska.com> wrote:
> >>
> >> This was actually just fixed in an obscure side dependency,
> >> struts-annotations (https://issues.apache.org/struts/browse/WW-1392)
> >>
> >> I haven't deployed snapshots to the Apache repo since Struts moved to
> >> M2;
> >> I'll give that a crack right now, but if you need to, you could check
> >> out
> >>
> >> http://svn.apache.org/repos/asf/struts/maven/trunk/struts-annotations/
> >>
> >> and do mvn install
> >>
> >> and that should do it...
> >>
> >> (in general, discussion of unreleased versions of struts is targeted at
> >> the dev list, but it's not a big deal...)
> >>
> >> Joe
> >>
> >> On 1/12/07, Eric Rank <er...@lo-fi.net> wrote:
> >> >
> >> > Greetings,
> >> >
> >> > I don't know if this is the best place to post this, so let me know
> >> > if this question is out of scope.
> >> >
> >> > I recently attempted building the latest snapshot of Struts 2 (rev
> >> > 495680) on Mac OS X and I get this error when building with Maven.
> >> >
> >> > =========================
> >> >
> >> > Missing:
> >> > ----------
> >> > 1) com.sun:tools:jar:1.5.0
> >> >
> >> > Try downloading the file manually from the project website.
> >> >
> >> > Then, install it using the command:
> >> > mvn install:install-file -DgroupId= com.sun
> >> -DartifactId=tools \
> >> > -Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file
> >> >
> >> > Path to dependency:
> >> > 1) org.apache.struts:struts2-core:jar:2.0.3-SNAPSHOT
> >> > 2) org.apache.struts:struts-annotations:jar:1.0-SNAPSHOT
> >> > 3) com.sun:tools:jar:1.5.0
> >> >
> >> > ==========================
> >> >
> >> > It seems to me that there's a dependency of the tools.jar library.
> >> > That'd be fine, but I'm trying to build this on a Mac, where
> >> > tools.jar doesn't exist.
> >> >
> >> > ( http://developer.apple.com/documentation/Java/Conceptual/
> >> > Java14Development/02-JavaDevTools/JavaDevTools.html#//apple_ref/doc/
> >> > uid/TP40001884-208117 )
> >> >
> >> > Am I missing something? or did I stumble upon a real problem?
> >> >
> >> > Also, for what it's worth, building the revision tagged as 2.0.2
> >> > works fine.
> >> >
> >> > Thanks,
> >> >
> >> > Eric Rank
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> >> > For additional commands, e-mail: user-help@struts.apache.org
> >> >
> >> >
> >>
> >>
> >> --
> >> Joe Germuska
> >> Joe@Germuska.com * http://blog.germuska.com
> >>
> >> "The truth is that we learned from João forever to be out of tune."
> >> -- Caetano Veloso
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Joe Germuska
Joe@Germuska.com * http://blog.germuska.com
"The truth is that we learned from João forever to be out of tune."
-- Caetano Veloso
Re: mvn deployment best practices? (Re: Permissions problems
deploying to snapshot repo)
Posted by Martin Gilday <fo...@opensymphony.com>.
Is there not already a Bamboo build going on that could do this? I know you can do this with Continuum so see no reason why Bambo couldn't.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=58438&messageID=115378#115378
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: mvn deployment best practices? (Re: Permissions problems deploying to snapshot repo)
Posted by Ted Husted <hu...@apache.org>.
On 1/12/07, Joe Germuska <jo...@germuska.com> wrote:
> Secondly, do we have any rules, or even guidelines, about when we should
> deploy SNAPSHOTs to the repo? I can't think of any particular reason, but I
> don't want to just bust off doing it whenever the whim strikes me, unless
> people think that's OK.
Ideally, it would be great if an automated process pushed out a new
daily snapshot on any day there was a commit, or every day regardless.
But lacking automation, I think we're left with whim. :)
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: mvn deployment best practices? (Re: Permissions problems deploying
to snapshot repo)
Posted by Don Brown <mr...@twdata.org>.
I believe xwork and Struts 2 are set to always deploy sources. Copy the
relevant section out of the pom into the annotations jar if you want
sources for it as well.
Don
Joe Germuska wrote:
> Great -- and I just verified that I am able to deploy, which I did, for
> struts-annotations.
>
> That leads me to a couple of small "practice" questions for the team.
>
> First, I really like having source code in the maven repository, so
> that mvn
> eclipse:eclipse -DdownloadSources=true can get them all and wire them
> into
> my project. I can get them deployed by using
> mvn compile source:jar deploy
> instead of
> mvn deploy
>
> but I might forget, as might the rest of the team. Is there a way we can
> configure Maven to always deploy sources? Does anyone object to always
> deploying sources?
>
> Secondly, do we have any rules, or even guidelines, about when we should
> deploy SNAPSHOTs to the repo? I can't think of any particular reason,
> but I
> don't want to just bust off doing it whenever the whim strikes me, unless
> people think that's OK.
>
> Joe
>
> On 1/12/07, Don Brown <mr...@twdata.org> wrote:
>>
>> Fixed.
>>
>> Don
>>
>> Joe Germuska wrote:
>> > Hey, I just sent this to users@struts... and when I went to build
>> a new
>> > snapshot of struts-annotations, I got a "permission denied"
>> >
>> > Turns out the existing file is owned by mrdon:apcvs with 644 perms.
>> >
>> > I think we need to make sure everyone who does deployments adds
>> > permissions
>> > configs to their ~/.m2/settings.xml file
>> >
>> > <filePermissions>664</filePermissions>
>> > <directoryPermissions>775</directoryPermissions>
>> >
>> > as described here:
>> > http://maven.apache.org/settings.html
>> >
>> > In the meantime, Don, can you (or someone with sudo privs) execute
>> > chmod 664
>> >
>> /www/people.apache.org/repo/m2-snapshot-repository/org/apache/struts/struts-annotations/1.0-SNAPSHOT/struts-
>>
>> >
>> > annotations-1.0-SNAPSHOT.jar
>> >
>> > on the repo server?
>> >
>> > Joe
>> >
>> > On 1/12/07, Joe Germuska <jo...@germuska.com> wrote:
>> >>
>> >> This was actually just fixed in an obscure side dependency,
>> >> struts-annotations (https://issues.apache.org/struts/browse/WW-1392)
>> >>
>> >> I haven't deployed snapshots to the Apache repo since Struts moved to
>> >> M2;
>> >> I'll give that a crack right now, but if you need to, you could check
>> >> out
>> >>
>> >>
>> http://svn.apache.org/repos/asf/struts/maven/trunk/struts-annotations/
>> >>
>> >> and do mvn install
>> >>
>> >> and that should do it...
>> >>
>> >> (in general, discussion of unreleased versions of struts is
>> targeted at
>> >> the dev list, but it's not a big deal...)
>> >>
>> >> Joe
>> >>
>> >> On 1/12/07, Eric Rank <er...@lo-fi.net> wrote:
>> >> >
>> >> > Greetings,
>> >> >
>> >> > I don't know if this is the best place to post this, so let me know
>> >> > if this question is out of scope.
>> >> >
>> >> > I recently attempted building the latest snapshot of Struts 2 (rev
>> >> > 495680) on Mac OS X and I get this error when building with Maven.
>> >> >
>> >> > =========================
>> >> >
>> >> > Missing:
>> >> > ----------
>> >> > 1) com.sun:tools:jar:1.5.0
>> >> >
>> >> > Try downloading the file manually from the project website.
>> >> >
>> >> > Then, install it using the command:
>> >> > mvn install:install-file -DgroupId= com.sun
>> >> -DartifactId=tools \
>> >> > -Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file
>> >> >
>> >> > Path to dependency:
>> >> > 1) org.apache.struts:struts2-core:jar:2.0.3-SNAPSHOT
>> >> > 2) org.apache.struts:struts-annotations:jar:1.0-SNAPSHOT
>> >> > 3) com.sun:tools:jar:1.5.0
>> >> >
>> >> > ==========================
>> >> >
>> >> > It seems to me that there's a dependency of the tools.jar library.
>> >> > That'd be fine, but I'm trying to build this on a Mac, where
>> >> > tools.jar doesn't exist.
>> >> >
>> >> > ( http://developer.apple.com/documentation/Java/Conceptual/
>> >> >
>> Java14Development/02-JavaDevTools/JavaDevTools.html#//apple_ref/doc/
>> >> > uid/TP40001884-208117 )
>> >> >
>> >> > Am I missing something? or did I stumble upon a real problem?
>> >> >
>> >> > Also, for what it's worth, building the revision tagged as 2.0.2
>> >> > works fine.
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Eric Rank
>> >> >
>> >> >
>> >> >
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>> >> > For additional commands, e-mail: user-help@struts.apache.org
>> >> >
>> >> >
>> >>
>> >>
>> >> --
>> >> Joe Germuska
>> >> Joe@Germuska.com * http://blog.germuska.com
>> >>
>> >> "The truth is that we learned from João forever to be out of tune."
>> >> -- Caetano Veloso
>> >
>> >
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> 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