update 2.3.0-incubating-SNAPSHOT to drop the snapshot in prep for release
-
Key: UIMA-1614
URL: https://issues.apache.org/jira/browse/UIMA-1614
Project: UIMA
Issue Type
update 2.3.0-incubating-SNAPSHOT to drop the snapshot in prep for release
-
Key: UIMA-1614
URL: https://issues.apache.org/jira/browse/UIMA-1614
Project: UIMA
Issue Type: Task
to 2.3.0-incubating-SNAPSHOT version
Key: UIMA-1461
URL: https://issues.apache.org/jira/browse/UIMA-1461
Project: UIMA
Issue Type: Task
Components: Sandbox
Reporter
update sandbox POMs to 2.3.0-incubating-SNAPSHOT version
Key: UIMA-1461
URL: https://issues.apache.org/jira/browse/UIMA-1461
Project: UIMA
Issue Type: Task
Components
point in which
handle common properties, this can be a good practice.
Tommaso
--Thilo
-Original Message-
From: Thilo Goetz [mailto:twgo...@gmx.de]
Sent: Tuesday, June 16, 2009 10:12 AM
To: uima-dev@incubator.apache.org
Subject: Re: 2.3.0-incubating-SNAPSHOT
Jukka Zitting
Tommaso Teofili wrote:
2009/6/16 Thilo Goetz twgo...@gmx.de
LeHouillier, Frank D. wrote:
No, but you should look at the maven release plugin for handling the
change from 2.n-SNAPSHOT in (trunk) to 2.n (in tags) to 2.n+1-SNAPSHOT
(back in trunk). It should handle all of the SNAPSHOT
Somebody please remind me: what's the purpose of the
-SNAPSHOT version name? Doesn't this just mean that
every POM needs to updated twice for a new version,
once with the snapshot tag, and once without?
Why aren't we going to the next version directly?
It's not like we're publishing snapshot
SNAPSHOT is a special version in maven that indicates the latest code;
typically TRUNK or HEAD in a source control. With this version, maven will
automatically grab the latest SNAPSHOT every time you build. On the other
hand, when you are using 2.0, once maven has downloaded this artifact, it
From my point of view, -SNAPSHOT versions are for example nightly builds.
For real releases with create a tag in SVN and building on this tag is no
SNAPSHOT.
-- Michael
Thilo Goetz wrote:
Somebody please remind me: what's the purpose of the
-SNAPSHOT version name? Doesn't this just mean that
Tommaso Teofili wrote:
SNAPSHOT is a special version in maven that indicates the latest code;
typically TRUNK or HEAD in a source control. With this version, maven will
automatically grab the latest SNAPSHOT every time you build. On the other
hand, when you are using 2.0, once maven has
Michael Baessler wrote:
From my point of view, -SNAPSHOT versions are for example nightly builds.
For real releases with create a tag in SVN and building on this tag is no
SNAPSHOT.
Yes but we don't *do* any nightly builds. Why do we
go to all this trouble if we don't use it for
anything?
Hi,
On Tue, Jun 16, 2009 at 3:40 PM, Thilo Goetztwgo...@gmx.de wrote:
I guess I'm just displaying my maven ignorance here. Since
we're not uploading any snapshot artifacts to any maven
repos, does it still buy us anything?
It does. If I build UIMA today, I get a SNAPSHOT version in my local
Jukka Zitting wrote:
Hi,
On Tue, Jun 16, 2009 at 3:40 PM, Thilo Goetztwgo...@gmx.de wrote:
I guess I'm just displaying my maven ignorance here. Since
we're not uploading any snapshot artifacts to any maven
repos, does it still buy us anything?
It does. If I build UIMA today, I get a
is abandoned forever.
-Original Message-
From: Thilo Goetz [mailto:twgo...@gmx.de]
Sent: Tuesday, June 16, 2009 10:12 AM
To: uima-dev@incubator.apache.org
Subject: Re: 2.3.0-incubating-SNAPSHOT
Jukka Zitting wrote:
Hi,
On Tue, Jun 16, 2009 at 3:40 PM, Thilo Goetztwgo...@gmx.de wrote
sometimes build UIMA trunk internally, this
won't be the case if SNAPSHOT is abandoned forever.
I do agree
-Original Message-
From: Thilo Goetz [mailto:twgo...@gmx.de]
Sent: Tuesday, June 16, 2009 10:12 AM
To: uima-dev@incubator.apache.org
Subject: Re: 2.3.0-incubating-SNAPSHOT
not planning on acquiring the maven skill to improve the situation.
So help in that quarter would be appreciated.
--Thilo
-Original Message-
From: Thilo Goetz [mailto:twgo...@gmx.de]
Sent: Tuesday, June 16, 2009 10:12 AM
To: uima-dev@incubator.apache.org
Subject: Re: 2.3.0-incubating
Update UIMA dependency to 2.3.0-incubating-SNAPSHOT
---
Key: UIMA-1346
URL: https://issues.apache.org/jira/browse/UIMA-1346
Project: UIMA
Issue Type: Task
Components: Sandbox
[
https://issues.apache.org/jira/browse/UIMA-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann closed UIMA-1346.
---
Resolution: Fixed
Update UIMA dependency to 2.3.0-incubating-SNAPSHOT
: org.apache.uima
ArtifactId: uimaj
Version: 2.3.0-incubating-SNAPSHOT
Reason: Unable to download the artifact from any repository
org.apache.uima:uimaj:pom:2.3.0-incubating-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2
between both suggestions.
But we still have to change for each child POM the version number of the parent
:-(
change UIMA version from 2.2.1-incubating to 2.3.0-incubating-SNAPSHOT
--
Key: UIMA-681
[
https://issues.apache.org/jira/browse/UIMA-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Baessler closed UIMA-681.
-
Resolution: Fixed
change UIMA version from 2.2.1-incubating to 2.3.0-incubating-SNAPSHOT
for correct release version
- check common_book_info.xml and index.html in the uima-docbooks project
all other places are updated automatically using Maven properties
change UIMA version from 2.2.1-incubating to 2.3.0-incubating-SNAPSHOT
for each child POM the version number of the
parent :-(
change UIMA version from 2.2.1-incubating to 2.3.0-incubating-SNAPSHOT
--
Key: UIMA-681
URL: https://issues.apache.org/jira/browse
2.2.1-incubating to 2.3.0-incubating-SNAPSHOT
--
Key: UIMA-681
URL: https://issues.apache.org/jira/browse/UIMA-681
Project: UIMA
Issue Type: Task
Components: Build
. In that case we have external dependencies for the build.
I haven't tried that way, so I'm also not sure if it works.
change UIMA version from 2.2.1-incubating to 2.3.0-incubating-SNAPSHOT
--
Key: UIMA-681
2.2.1-incubating to 2.3.0-incubating-SNAPSHOT
--
Key: UIMA-681
URL: https://issues.apache.org/jira/browse/UIMA-681
Project: UIMA
Issue Type: Task
Components: Build
to manage the
version numbers?
I give it a try, but it doesn't work for me.
change UIMA version from 2.2.1-incubating to 2.3.0-incubating-SNAPSHOT
--
Key: UIMA-681
URL: https://issues.apache.org/jira
, has
a guide to using properties. I haven't tried it myself. What did you try
that didn't work for you?
change UIMA version from 2.2.1-incubating to 2.3.0-incubating-SNAPSHOT
--
Key: UIMA-681
28 matches
Mail list logo
