> 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: UIM
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
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
>
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
Tommaso Teofili wrote:
> 2009/6/16 Thilo Goetz
>
>> 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 dependenc
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
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 Goetz wrote:
>>> I guess I'm just displaying my maven ignorance here. Since
>>&g
ce we do 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
f SNAPSHOT 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 Goet
Jukka Zitting wrote:
> Hi,
>
> On Tue, Jun 16, 2009 at 3:40 PM, Thilo Goetz 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 SNAPSHO
Hi,
On Tue, Jun 16, 2009 at 3:40 PM, Thilo Goetz 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
Maven reposi
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?
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 dow
>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 th
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
never
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 relea
[
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-SNAPS
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
ase version, and update uima-as
> poms to 2.3.0-incubating-SNAPSHOT
> --
>
> Key: UIMA-1186
> URL: https://issues.apache.org/jir
down-level dependencies in
the Uima AS pom files. upgrade base uima dependency and also uima-as version
number to 2.3.0-incubating-SNAPSHOT (was: The maven build fails due to invalid
dependencies in the Uima AS pom files. The core UIMA version is higher than
expected. Modify the Uima AS poms to
d to resolve artifact.
GroupId: 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
gt;> 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
>>> --
>&g
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
>> --
>>
[
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-SNAPS
ally using Maven properties
> change UIMA version from 2.2.1-incubating to 2.3.0-incubating-SNAPSHOT
> --
>
> Key: UIMA-681
> URL: https://issues.apache.org/jira/browse/UIMA-681
>
mix 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
> --
>
>
sfully, because the child POM
inherits from the maven repository (local, in my case). It's not enough to
change the pom in the uimaj project without running mvn install on it.
> change UIMA version from 2.2.1-incubating t
n 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
> --
>
, 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
> --
>
>
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
[
https://issues.apache.org/jira/browse/UIMA-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Baessler updated UIMA-681:
--
Summary: change UIMA version from 2.2.1-incubating to
2.3.0-incubating-SNAPSHOT (was: change
31 matches
Mail list logo
