You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Davis Ford <da...@zenoconsulting.biz> on 2006/05/16 20:18:47 UTC
SNAPSHOT question
Hi, if I have pom.xml for a project that has
<version>1.0-SNAPSHOT</version>
and I do:
mvn deploy
It sends up a release with the timestamp in the 1.0-SNAPSHOT/ dir.
However, what if a developer wants to do a release, not a snapshot?
If I try
mvn -Dversion=1.2 deploy
It uploads a new SNAPSHOT with a timestamp into the 1.0-SNAPSHOT dir.
Is there some way to override this?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SNAPSHOT question
Posted by Davis Ford <da...@zenoconsulting.biz>.
Wayne - as a matter of principle, I totally agree with you there.
Thanks...it has been a long day. I was trying to illustrate an
example -- albeit not very well....but what you say makes total sense.
On 5/16/06, Wayne Fay <wa...@gmail.com> wrote:
> I (personally) think you might want to review your building and
> tagging approach...
>
> 1.0-SNAPSHOT is "before" 1.0
> 1.3 is "never" built until after 1.0 is final
> Once we build 1.3, the next build would be 1.4-SNAPSHOT
> My "deploy" process would be: check out code, change from 1.3-SNAPSHOT
> to 1.3, check in, tag with build-1.3, then build and deploy
>
> If you have some grand plan that you're working towards, and this does
> not apply or make sense for your organization or your SCM, then you
> can safely ignore it. But it just sounds like your SNAPSHOT versioning
> plan etc might be a little "off" from the "traditional" approach...
>
> Wayne
>
> On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> > We are using a horrible tool called MKS Source Integrity. Believe you
> > me -- I have opined for SVN many times.
> >
> > Building an SCM plugin is not gonna happen soon enough to solve our needs.
> >
> > So, unless someone on the list has any other insight, it appears the
> > only way for a team/developer to do a release of a module is to
> > manually edit <version>
> >
> > FROM: <version>1.0-SNAPSHOT</version>
> > TO: <version>1.3</version>
> >
> > C:\myproject>mvn deploy
> >
> > Then, manually change it back or ensure that the pom.xml does not get
> > checked in with 1.3. I want to have 1.0-SNAPSHOT checked into version
> > control, so our nightly build will do the following:
> >
> > 1) suck out the latest from this MKS thing
> > 2) do a deploy (to the snapshot repo)
> > 3) run all integration tests
> >
> >
> >
> > On 5/16/06, Wayne Fay <wa...@gmail.com> wrote:
> > > I'd install SVN. ;-)
> > >
> > > No really, I'm not aware of any way to utilize the release plugin
> > > without an SCM. So you'll probably need to build an SCM plugin for
> > > your specific SCM tool and integrate it into M2 to properly use the
> > > release plugin. Or write a new plugin that works similar to release
> > > but does not do the SCM steps first.
> > >
> > > What are you using, if not CVS or SVN? Starteam? Clear <something>?
> > >
> > > Wayne
> > >
> > > On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> > > > Hi Wayne,
> > > >
> > > > I looked at mvn release, but it seems tied to SCM system.
> > > > Unfortunately, we don't use svn or cvs -- and I have no clue how to
> > > > integrate it with the thing we are using (I really wish we were using
> > > > svn).
> > > >
> > > > Is there a simple example of using "mvn release" that does not depend
> > > > on the scm system?
> > > >
> > > > Thx,
> > > > Davis
> > > >
> > > > On 5/16/06, Wayne Fay <wa...@gmail.com> wrote:
> > > > > You're looking for "mvn release" not deploy. Release will update the
> > > > > <version> tags and install the artifact properly in the specified
> > > > > repositories.
> > > > >
> > > > > However its a little more complex than simply "mvn release" so check
> > > > > out the m2 book (better builds with maven), the user list archive, the
> > > > > maven website, etc for details.
> > > > >
> > > > > Wayne
> > > > >
> > > > > On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> > > > > > Hi, if I have pom.xml for a project that has
> > > > > >
> > > > > > <version>1.0-SNAPSHOT</version>
> > > > > >
> > > > > > and I do:
> > > > > >
> > > > > > mvn deploy
> > > > > >
> > > > > > It sends up a release with the timestamp in the 1.0-SNAPSHOT/ dir.
> > > > > >
> > > > > > However, what if a developer wants to do a release, not a snapshot?
> > > > > >
> > > > > > If I try
> > > > > >
> > > > > > mvn -Dversion=1.2 deploy
> > > > > >
> > > > > > It uploads a new SNAPSHOT with a timestamp into the 1.0-SNAPSHOT dir.
> > > > > >
> > > > > > Is there some way to override this?
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Zeno Consulting, Inc.
> > > > (248) 894-4922 (p)
> > > > (206) 202-4077 (f)
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> > Zeno Consulting, Inc.
> > (248) 894-4922 (p)
> > (206) 202-4077 (f)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Zeno Consulting, Inc.
(248) 894-4922 (p)
(206) 202-4077 (f)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SNAPSHOT question
Posted by Wayne Fay <wa...@gmail.com>.
I (personally) think you might want to review your building and
tagging approach...
1.0-SNAPSHOT is "before" 1.0
1.3 is "never" built until after 1.0 is final
Once we build 1.3, the next build would be 1.4-SNAPSHOT
My "deploy" process would be: check out code, change from 1.3-SNAPSHOT
to 1.3, check in, tag with build-1.3, then build and deploy
If you have some grand plan that you're working towards, and this does
not apply or make sense for your organization or your SCM, then you
can safely ignore it. But it just sounds like your SNAPSHOT versioning
plan etc might be a little "off" from the "traditional" approach...
Wayne
On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> We are using a horrible tool called MKS Source Integrity. Believe you
> me -- I have opined for SVN many times.
>
> Building an SCM plugin is not gonna happen soon enough to solve our needs.
>
> So, unless someone on the list has any other insight, it appears the
> only way for a team/developer to do a release of a module is to
> manually edit <version>
>
> FROM: <version>1.0-SNAPSHOT</version>
> TO: <version>1.3</version>
>
> C:\myproject>mvn deploy
>
> Then, manually change it back or ensure that the pom.xml does not get
> checked in with 1.3. I want to have 1.0-SNAPSHOT checked into version
> control, so our nightly build will do the following:
>
> 1) suck out the latest from this MKS thing
> 2) do a deploy (to the snapshot repo)
> 3) run all integration tests
>
>
>
> On 5/16/06, Wayne Fay <wa...@gmail.com> wrote:
> > I'd install SVN. ;-)
> >
> > No really, I'm not aware of any way to utilize the release plugin
> > without an SCM. So you'll probably need to build an SCM plugin for
> > your specific SCM tool and integrate it into M2 to properly use the
> > release plugin. Or write a new plugin that works similar to release
> > but does not do the SCM steps first.
> >
> > What are you using, if not CVS or SVN? Starteam? Clear <something>?
> >
> > Wayne
> >
> > On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> > > Hi Wayne,
> > >
> > > I looked at mvn release, but it seems tied to SCM system.
> > > Unfortunately, we don't use svn or cvs -- and I have no clue how to
> > > integrate it with the thing we are using (I really wish we were using
> > > svn).
> > >
> > > Is there a simple example of using "mvn release" that does not depend
> > > on the scm system?
> > >
> > > Thx,
> > > Davis
> > >
> > > On 5/16/06, Wayne Fay <wa...@gmail.com> wrote:
> > > > You're looking for "mvn release" not deploy. Release will update the
> > > > <version> tags and install the artifact properly in the specified
> > > > repositories.
> > > >
> > > > However its a little more complex than simply "mvn release" so check
> > > > out the m2 book (better builds with maven), the user list archive, the
> > > > maven website, etc for details.
> > > >
> > > > Wayne
> > > >
> > > > On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> > > > > Hi, if I have pom.xml for a project that has
> > > > >
> > > > > <version>1.0-SNAPSHOT</version>
> > > > >
> > > > > and I do:
> > > > >
> > > > > mvn deploy
> > > > >
> > > > > It sends up a release with the timestamp in the 1.0-SNAPSHOT/ dir.
> > > > >
> > > > > However, what if a developer wants to do a release, not a snapshot?
> > > > >
> > > > > If I try
> > > > >
> > > > > mvn -Dversion=1.2 deploy
> > > > >
> > > > > It uploads a new SNAPSHOT with a timestamp into the 1.0-SNAPSHOT dir.
> > > > >
> > > > > Is there some way to override this?
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Zeno Consulting, Inc.
> > > (248) 894-4922 (p)
> > > (206) 202-4077 (f)
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> Zeno Consulting, Inc.
> (248) 894-4922 (p)
> (206) 202-4077 (f)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SNAPSHOT question
Posted by Davis Ford <da...@zenoconsulting.biz>.
We are using a horrible tool called MKS Source Integrity. Believe you
me -- I have opined for SVN many times.
Building an SCM plugin is not gonna happen soon enough to solve our needs.
So, unless someone on the list has any other insight, it appears the
only way for a team/developer to do a release of a module is to
manually edit <version>
FROM: <version>1.0-SNAPSHOT</version>
TO: <version>1.3</version>
C:\myproject>mvn deploy
Then, manually change it back or ensure that the pom.xml does not get
checked in with 1.3. I want to have 1.0-SNAPSHOT checked into version
control, so our nightly build will do the following:
1) suck out the latest from this MKS thing
2) do a deploy (to the snapshot repo)
3) run all integration tests
On 5/16/06, Wayne Fay <wa...@gmail.com> wrote:
> I'd install SVN. ;-)
>
> No really, I'm not aware of any way to utilize the release plugin
> without an SCM. So you'll probably need to build an SCM plugin for
> your specific SCM tool and integrate it into M2 to properly use the
> release plugin. Or write a new plugin that works similar to release
> but does not do the SCM steps first.
>
> What are you using, if not CVS or SVN? Starteam? Clear <something>?
>
> Wayne
>
> On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> > Hi Wayne,
> >
> > I looked at mvn release, but it seems tied to SCM system.
> > Unfortunately, we don't use svn or cvs -- and I have no clue how to
> > integrate it with the thing we are using (I really wish we were using
> > svn).
> >
> > Is there a simple example of using "mvn release" that does not depend
> > on the scm system?
> >
> > Thx,
> > Davis
> >
> > On 5/16/06, Wayne Fay <wa...@gmail.com> wrote:
> > > You're looking for "mvn release" not deploy. Release will update the
> > > <version> tags and install the artifact properly in the specified
> > > repositories.
> > >
> > > However its a little more complex than simply "mvn release" so check
> > > out the m2 book (better builds with maven), the user list archive, the
> > > maven website, etc for details.
> > >
> > > Wayne
> > >
> > > On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> > > > Hi, if I have pom.xml for a project that has
> > > >
> > > > <version>1.0-SNAPSHOT</version>
> > > >
> > > > and I do:
> > > >
> > > > mvn deploy
> > > >
> > > > It sends up a release with the timestamp in the 1.0-SNAPSHOT/ dir.
> > > >
> > > > However, what if a developer wants to do a release, not a snapshot?
> > > >
> > > > If I try
> > > >
> > > > mvn -Dversion=1.2 deploy
> > > >
> > > > It uploads a new SNAPSHOT with a timestamp into the 1.0-SNAPSHOT dir.
> > > >
> > > > Is there some way to override this?
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> > Zeno Consulting, Inc.
> > (248) 894-4922 (p)
> > (206) 202-4077 (f)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Zeno Consulting, Inc.
(248) 894-4922 (p)
(206) 202-4077 (f)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SNAPSHOT question
Posted by Wayne Fay <wa...@gmail.com>.
I'd install SVN. ;-)
No really, I'm not aware of any way to utilize the release plugin
without an SCM. So you'll probably need to build an SCM plugin for
your specific SCM tool and integrate it into M2 to properly use the
release plugin. Or write a new plugin that works similar to release
but does not do the SCM steps first.
What are you using, if not CVS or SVN? Starteam? Clear <something>?
Wayne
On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> Hi Wayne,
>
> I looked at mvn release, but it seems tied to SCM system.
> Unfortunately, we don't use svn or cvs -- and I have no clue how to
> integrate it with the thing we are using (I really wish we were using
> svn).
>
> Is there a simple example of using "mvn release" that does not depend
> on the scm system?
>
> Thx,
> Davis
>
> On 5/16/06, Wayne Fay <wa...@gmail.com> wrote:
> > You're looking for "mvn release" not deploy. Release will update the
> > <version> tags and install the artifact properly in the specified
> > repositories.
> >
> > However its a little more complex than simply "mvn release" so check
> > out the m2 book (better builds with maven), the user list archive, the
> > maven website, etc for details.
> >
> > Wayne
> >
> > On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> > > Hi, if I have pom.xml for a project that has
> > >
> > > <version>1.0-SNAPSHOT</version>
> > >
> > > and I do:
> > >
> > > mvn deploy
> > >
> > > It sends up a release with the timestamp in the 1.0-SNAPSHOT/ dir.
> > >
> > > However, what if a developer wants to do a release, not a snapshot?
> > >
> > > If I try
> > >
> > > mvn -Dversion=1.2 deploy
> > >
> > > It uploads a new SNAPSHOT with a timestamp into the 1.0-SNAPSHOT dir.
> > >
> > > Is there some way to override this?
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> Zeno Consulting, Inc.
> (248) 894-4922 (p)
> (206) 202-4077 (f)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SNAPSHOT question
Posted by Davis Ford <da...@zenoconsulting.biz>.
Hi Wayne,
I looked at mvn release, but it seems tied to SCM system.
Unfortunately, we don't use svn or cvs -- and I have no clue how to
integrate it with the thing we are using (I really wish we were using
svn).
Is there a simple example of using "mvn release" that does not depend
on the scm system?
Thx,
Davis
On 5/16/06, Wayne Fay <wa...@gmail.com> wrote:
> You're looking for "mvn release" not deploy. Release will update the
> <version> tags and install the artifact properly in the specified
> repositories.
>
> However its a little more complex than simply "mvn release" so check
> out the m2 book (better builds with maven), the user list archive, the
> maven website, etc for details.
>
> Wayne
>
> On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> > Hi, if I have pom.xml for a project that has
> >
> > <version>1.0-SNAPSHOT</version>
> >
> > and I do:
> >
> > mvn deploy
> >
> > It sends up a release with the timestamp in the 1.0-SNAPSHOT/ dir.
> >
> > However, what if a developer wants to do a release, not a snapshot?
> >
> > If I try
> >
> > mvn -Dversion=1.2 deploy
> >
> > It uploads a new SNAPSHOT with a timestamp into the 1.0-SNAPSHOT dir.
> >
> > Is there some way to override this?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Zeno Consulting, Inc.
(248) 894-4922 (p)
(206) 202-4077 (f)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SNAPSHOT question
Posted by Wayne Fay <wa...@gmail.com>.
You're looking for "mvn release" not deploy. Release will update the
<version> tags and install the artifact properly in the specified
repositories.
However its a little more complex than simply "mvn release" so check
out the m2 book (better builds with maven), the user list archive, the
maven website, etc for details.
Wayne
On 5/16/06, Davis Ford <da...@zenoconsulting.biz> wrote:
> Hi, if I have pom.xml for a project that has
>
> <version>1.0-SNAPSHOT</version>
>
> and I do:
>
> mvn deploy
>
> It sends up a release with the timestamp in the 1.0-SNAPSHOT/ dir.
>
> However, what if a developer wants to do a release, not a snapshot?
>
> If I try
>
> mvn -Dversion=1.2 deploy
>
> It uploads a new SNAPSHOT with a timestamp into the 1.0-SNAPSHOT dir.
>
> Is there some way to override this?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org