You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Peter Klügl <pk...@uni-wuerzburg.de> on 2012/12/12 00:39:05 UTC

Questions about TextMarker release

Hi,

I am getting ready to prepare the first RC of the TextMarker and I have 
some simple questions for the start:
- Is there a release manager for this? I guess that I will do the 
complete release, right? I do not even know if I have the rights for all 
steps.
- Is it recommended to create an "aggregate-uimaj-textmarker" project?
- How does it work with the documentation? The pdf has more than 80 
pages right now. I created a book for the developement, but maybe it's 
better if the TextMarker documentation stays in its own book?

I was reading  much about doing a release, but I do not know if all 
applies one-to-one on the TextMarker projects. I am happy for any advice

Best

Peter

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
On 12.12.2012 16:34, Marshall Schor wrote:
> I think TextMarker can have its own separate version numbers, and its own
> separate release schedule.
> For each release, it would have a (range of?) UIMA version dependencies.  Maven
> supports ranges in dependency specifications.
>
> (Just for completeness, an argument for aligning to, say, 2.4.0 or 2.4.1 is to
> reduce end-user "confusion".  But because of the likely different release
> schedules, and lack of tight coupling (perhaps) to particular release levels,
> this probably is not the right way to go here).
>
> I don't quite understand your question about the parent-pom (which parent-pom
> are you discussing?)?  Can you elaborate?
>
> -Marshall
>

I have used uimaj-parent as parent pom for the TextMarker poms (parent 
is pointing to uimaj-parent).
What should be the parent pom? There is uima-addons-parent, but no 
project for the sandbox.

My question was about a problem I observed when I just changed the 
version numbers. This resulted in a "project build error".

Peter

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
I think TextMarker can have its own separate version numbers, and its own
separate release schedule.
For each release, it would have a (range of?) UIMA version dependencies.  Maven
supports ranges in dependency specifications.

(Just for completeness, an argument for aligning to, say, 2.4.0 or 2.4.1 is to
reduce end-user "confusion".  But because of the likely different release
schedules, and lack of tight coupling (perhaps) to particular release levels,
this probably is not the right way to go here).

I don't quite understand your question about the parent-pom (which parent-pom
are you discussing?)?  Can you elaborate?

-Marshall


On 12/12/2012 7:53 AM, Peter Klügl wrote:
> Thanks for the answers.
>
> The next question: What about the version number of the TextMarker release?
>
> The projects are developed against the head of the svn and therefore the
> current version is also 2.4.1-SNAPSHOT.
> TextMarker should work just fine with uimaj-(core, ...)-2.4.0, but I do not
> remember right now, what changes of the CAS Editor are already released in
> 2.4.0. I got no compile errors yet when I set the dependency for the CAS
> Editor to 2.4.0. However, I need more testing here.
>
> So, 2.4.0 it would be? Or is an alignment, e.g., to other Eclipse-based
> tooling, not necessary?
>
> Are there any best practices for that? I am thinking, for example, about the
> version of the parent pom. Do I have to create a new workspace with some UIMA
> projects in the 2.4.0 revision?
>
> Best,
>
> Peter
>
>
>
> On 12.12.2012 02:39, Marshall Schor wrote:
>> <snip>
>>> - Is there a release manager for this?
>> You can be the release manager, or someone else could.  The RM is just the
>> person pushing through all the steps to get the release done.
>>
>>> I guess that I will do the complete release, right? I do not even know if I
>>> have the rights for all steps.
>> You should have all the rights.  If not, we'll get that fixed :-)
>>
>>> - Is it recommended to create an "aggregate-uimaj-textmarker" project?
>> A popular method for users to interact with our source, is to check out some
>> portion of the tree they're interested in , and do mvn install.  Right now, if
>> you check out the TextMarker directory (which has all the other projects in it),
>> it appears that
>>    - the projects are "flat" - all exist as children of the top TextMarker
>> directory
>>    - there is no overall "pom" the containing TextMarker directory - it has no
>> files, only the subdirectories.
>>
>> I would suggest creating a pom for the entire project, and storing it as a file
>> in the TextMarker directory (not in a separate new project called
>> aggregate-uimaj-textmarker).  This pom's purpose would be to do the aggregation
>> (via <modules>) of all the subprojects that normally ought to be built when a
>> user wants to build from source.
>>
>>> - How does it work with the documentation? The pdf has more than 80 pages
>>> right now. I created a book for the developement, but maybe it's better if the
>>> TextMarker documentation stays in its own book?
>> Sure, that's sounds correct.  Some other sandbox projects also have docbook
>> documentation.
>>
>>> I was reading  much about doing a release, but I do not know if all applies
>>> one-to-one on the TextMarker projects.
>> We'll only discover what is needed as we go step by step through the process
>> :-).
>>
>> -Marshall
>
>
>

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
+1 Marshall
On 12/12/2012 7:57 AM, Jörn Kottmann wrote:
> On 12/12/2012 01:53 PM, Peter Klügl wrote:
>> Thanks for the answers.
>>
>> The next question: What about the version number of the TextMarker release?
>>
>
> If you align with the UIMA releases you are somehow bound to its development
> cycle, in
> case you want to release more frequently this could be problematic.
>
> Jörn
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
> Thanks for your answer.
> 
> I suppose "Fixed in" is equal to "fixVersion"? Sadly, there was no version yet, when I fixed most issues.
> 
> I am using right now "project = UIMA AND component = TextMarker AND status in (Resolved, Closed) AND fixVersion = EMPTY", but I cannot use "Bullk change". After a short google search, I think this is because the issues are resolved or closed. I also cannot change "Fix Version/s" in a single issue.
> 
> I have doubts whether it is a good idea to open all (92) issues again.
> 
> Any ideas?


It's a known "problem" with the default Jira settings. When possible, I suggest to change the default Jira workflow so that closed issues can be edited (which some people object to) - but looks like the Apache Jira isn't configured in that way. Under these circumstances, I don't know another solution short of reopening the issues, again - sorry.

I think it only applies to Closed issues though. You should still be able to edit Resolved issues.

Probably it's best to reopen the closed issues, set the version and then resolve them again. It is probably also a good idea to leave issues "resolved" at least until a release has been made. I didn't read the release guidelines yet, maybe it says something about a best practice when to "Close" issues.

-- Richard

-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Hi,

On 21.12.2012 11:54, Richard Eckart de Castilho wrote:
> Am 21.12.2012 um 11:12 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>
>> 2. Preparing the Jira for the Release
>>
>> "...and that the "Fixed in release xxx" is set for each Jira issue that is part of the release."
>>
>> "There is a saved "filter" you can adjust for this that will display all fixed Jira issues with no Fixed in release xxx assigned. You can go through subsets of this (use the filter to pick the subset you want) and do "bulk Jira changes" to update multiples of these in parallel, if that makes sense.
> Such a filter is convenience, just search for all resolved/fixed issues that do not have any "fixed in" assigned.
>
>> Is this necessary that all issues are updated as it will be the first relase of the TextMarker system? And if yes, where can I find this filter?
> If you have properly set "Fixed in" every time you fixed an issue, then there is nothing to do. Sometimes, in the heat of development, when an issue is closed, its "Fixed in" field is not set immediately. That is, why there is such a point in any good release guide.
>
> When a release is done, all issues resolved in that release should have "Fixed in" set to the release being made. Thus, when the a release is being made, it is a good time to check all the resolved issues and make sure that "Fixed in" is set properly. It doesn't matter if it is the first release. Proper bookkeeping is always a good idea.
>
>

Thanks for your answer.

I suppose "Fixed in" is equal to "fixVersion"? Sadly, there was no 
version yet, when I fixed most issues.

I am using right now "project = UIMA AND component = TextMarker AND 
status in (Resolved, Closed) AND fixVersion = EMPTY", but I cannot use 
"Bullk change". After a short google search, I think this is because the 
issues are resolved or closed. I also cannot change "Fix Version/s" in a 
single issue.

I have doubts whether it is a good idea to open all (92) issues again.

Any ideas?

Best,

Peter

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Am 21.12.2012 um 11:12 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:

> 2. Preparing the Jira for the Release
> 
> "...and that the "Fixed in release xxx" is set for each Jira issue that is part of the release."
> 
> "There is a saved "filter" you can adjust for this that will display all fixed Jira issues with no Fixed in release xxx assigned. You can go through subsets of this (use the filter to pick the subset you want) and do "bulk Jira changes" to update multiples of these in parallel, if that makes sense.

Such a filter is convenience, just search for all resolved/fixed issues that do not have any "fixed in" assigned.

> Is this necessary that all issues are updated as it will be the first relase of the TextMarker system? And if yes, where can I find this filter?

If you have properly set "Fixed in" every time you fixed an issue, then there is nothing to do. Sometimes, in the heat of development, when an issue is closed, its "Fixed in" field is not set immediately. That is, why there is such a point in any good release guide.

When a release is done, all issues resolved in that release should have "Fixed in" set to the release being made. Thus, when the a release is being made, it is a good time to check all the resolved issues and make sure that "Fixed in" is set properly. It doesn't matter if it is the first release. Proper bookkeeping is always a good idea.

Cheers,

-- Richard

-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Hi,

On 09.01.2013 17:35, Marshall Schor wrote:
> On 1/9/2013 10:06 AM, Peter Klügl wrote:
>> Hi,
>>
>> next question about "Building The Release Candidate"
>>
>> I did now a trial build of the release candidate with "mvn install
>> -Papache-release". The only thing that looks not correct is the naming of the
>> pom for the Eclipse plugins, for example:
>>
>> org.apache.uima.textmarker.addons_${parsedVersion.osgiVersion}.pom
>>
>> Do I have to take care of that? This happens also for the CAS Editor plugin in
>> my workspace.
> Can you say a bit more for those of us not following all the details :-) - for
> instance, what should this be changed to, and where in the build (what part of
> the build) is this being done?

I applied "mvn install -Papache-release" on uimaj-textmarker-parent and 
those files are located in the target folder of the plugin projects. I 
expected something like org.apache.uima.textmarker.addons_2.0.0.SNAPSHOT.pom

Hmm... when I think now about it, it is possible that some maven plugin 
cannot handle the SNAPSHOT qualifier. Maybe this won't happen if the 
qualifier is removed before the actual release verison is built.


>> What is the next step? Should I already add the server properties to my
>> settings.xml as described here [1], or is there an intermediate step, e.g.,
>> uploading the trial to my people.apache.org webspace?
> You can add the server properties to your settings.xml, but please use the
> encryption technique.
> This would enable you to upload snapshots to the repository.apache.org server,
> for instance.
>
> Before doing a release, we need to finish the ip clearance process, too.

Ok, I will wait for the ip clearance issue [UIMA-2556] before I proceed.

Peter


> -Marshall
>> Best,
>>
>> Peter
>>
>> [1] http://maven.apache.org/developers/committer-settings.html
>>
>>
>> On 08.01.2013 22:40, Peter Klügl wrote:
>>> I have found the problem by taking a closer look at the uima-as pom.  ->
>>> plugin version + config
>>>
>>> Can someone verify if the org.apache.uima:parent-pom works correctly? It did
>>> not work for me and I think it needs to be updates for Jira >4.
>>> The maven-changes-plugin version points to 2.6, for example.
>>>
>>> Peter
>>>
>>>
>>> Am 08.01.2013 13:55, schrieb Peter Klügl:
>>>> Hi,
>>>>
>>>> next question about "Preparing The Sourcecode For The Release".
>>>>
>>>> I added the jiraVersion property. However, if I try to generate the report
>>>> with "mvn changes:jira-report -N", then I get an exception:
>>>>
>>>> org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
>>>> Caused by: org.xml.sax.SAXParseException: The element type "meta" must be
>>>> terminated by the matching end-tag "</meta>".
>>>>
>>>> A short google search indicates that the configuration in the pom is
>>>> probably not correct. However, the related definitions are located in the
>>>> org.apache.uima:parent-pom.
>>>>
>>>> Did I miss something, or do I have to override something in
>>>> uimaj-textmarker-parent?
>>>>
>>>> Best,
>>>>
>>>> Peter
>>>>
>>>>
>>>> On 21.12.2012 11:12, Peter Klügl wrote:
>>>>> Hi,
>>>>>
>>>>> the next two questions:
>>>>>
>>>>> 1.  Release Discussions - Release Plan
>>>>>
>>>>> http://uima.apache.org/release.html says: "At the beginning of the "UIMA
>>>>> Release Process" there must be consensus in the developer community about
>>>>> the JIRA issues that should be part of the next release and the time frame
>>>>> for the release..."
>>>>>
>>>>> Here's a list of unresolved issues:
>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20TextMarker%20ORDER%20BY%20priority%20DESC
>>>>>
>>>>> UIMA-2285 (Write documentation for the TextMarker projects) will be
>>>>> resolved before the release as it is almost done.
>>>>> UIMA-2528 (Open CAS Editor blocks eclipse start) is almost a blocker, but I
>>>>> fear that I won't be able to change anything in the TextMarker projects
>>>>> that will fix this problem.
>>>>>
>>>>> If there are no objections, then I will to move all the unresolved issues
>>>>> to the next version (2.0.1).
>>>>>
>>>>>
>>>>> 2. Preparing the Jira for the Release
>>>>>
>>>>> "...and that the "Fixed in release xxx" is set for each Jira issue that is
>>>>> part of the release."
>>>>>
>>>>> "There is a saved "filter" you can adjust for this that will display all
>>>>> fixed Jira issues with no Fixed in release xxx assigned. You can go through
>>>>> subsets of this (use the filter to pick the subset you want) and do "bulk
>>>>> Jira changes" to update multiples of these in parallel, if that makes sense."
>>>>>
>>>>> Is this necessary that all issues are updated as it will be the first
>>>>> relase of the TextMarker system? And if yes, where can I find this filter?
>>>>>
>>>>>
>>>>> Peter
>>>>>
>>>>>
>>>>> On 12.12.2012 17:33, Peter Klügl wrote:
>>>>>> Hmm, good point. Then, I prefer 2.0.0
>>>>>>
>>>>>> Peter
>>>>>>
>>>>>> On 12.12.2012 17:28, Jörn Kottmann wrote:
>>>>>>> On 12/12/2012 05:21 PM, Peter Klügl wrote:
>>>>>>>> Ok, after all comments, I think the TextMarker release number should be
>>>>>>>> 1.0.0.
>>>>>>>>
>>>>>>> It will confuse people when you release under a lower version number as
>>>>>>> you did before.
>>>>>>> I suggest to increment the version either to 1.6.0 or if there have been
>>>>>>> significant changes to
>>>>>>> 2.0.0.
>>>>>>>
>>>>>>>> Jörn, do you have an opinion about the additional CAS Editor views
>>>>>>>> (uimaj-ep-textmarker-caseditor)? They have no dependency to TextMarker,
>>>>>>>> only to the two CAS Editor projects. I will simply release them together
>>>>>>>> with TextMarker.
>>>>>>> +1
>>>>>>>
>>>>>>> Jörn
>>>>>
>>

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
On 1/21/2013 3:14 PM, Richard Eckart de Castilho wrote:
> Good luck. When you find out what's the problem, drop us a note. 
>
> I never run releases in Eclipse and teach anybody to do them on the command line. I suppose it cannot hurt if you try. Make sure you the latest Maven release.
+1.  Until I get things going correctly, I also avoid shortcuts like stacking
multiple release operations in mvn, like mvn release:prepare release:perform.  
I would do just mvn release:prepare, and only when that was ironed out would I
do release:perform.

-M
>
> Another thing: are you sure the SCM location is correct in the POM?
>
> Cheers,
>
> -- Richard
>
> Am 21.01.2013 um 21:07 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>
>> Hi Richard,
>>
>> Am 21.01.2013 20:48, schrieb Richard Eckart de Castilho:
>>> Hi Peter,
>>>
>>> to avoid username/pw on the command line, I had to use a differnent svn binary. Normally it should be enough to log in on the command line once (e.g. by issuing a "svn log" command) and let svn cache the credentials.
>>>
>>> But anyway, your error doesn't look like missing credentials (it should say something along the lines "access denied") it rather looks like a SVN server glitch - something I get on Google Code every one in a while. Did you try just calling "mvn release:prepare" again? Maven remembers where the release process got stuck and will pick up again there. If you need to abort the release, use "mvn release:rollback".
>> The first try was "mvn -DautoVersionSubmodules release:prepare release:perform" and failed. Then, I executed "mvn release:rollback" and tried only "mvn -DautoVersionSubmodules release:prepare". This also failed, followed by another rollback.
>>
>> I gonna do some internet search about the error message tomorrow . Maybe I find some explanation what might be causing this.
>>
>> Btw, I am doing this in Eclipse with "Maven/run as..." and with an external maven install. Shouldn't be a problem, I think.
>>
>> Peter
>>
>>> Cheers,
>>>
>>> -- Richard
>>>
>>> Am 21.01.2013 um 19:38 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>>>
>>>> On 17.01.2013 19:08, Richard Eckart de Castilho wrote:
>>>>> Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:
>>>>>
>>>>>>> If your release fails at some SVN operation like creating the tag, try providing "-Dusername=XXX -Dpassword=YYY" on the command line with your SVN credentials.
>>>>>> I've never had to do this.  I would be careful, in case these are sent in the
>>>>>> "clear" (I don't know about this).
>>>>> If you local SVN setup is well configured, this should not be required. I've had some issues in the past on OS X with SVN not picking up cached passwords during a Maven release. I didn't read the code, but I expect the credentials are passed on when Maven calls the external SVN process and are sent via whatever protocol you use to communicate with the SVN server. But they do end up in the shell history of course - clearing the command from there after the process is certainly wise.
>>>>>
>>>>> -- Richard
>>>>>
>>>> Hmm... that probably happened to me now but the error doesn't look like missing SVN credentials.
>>>>
>>>> The SVN setup looks fine. Any idea how to avoid "-Dusername=XXX -Dpassword=YYY"?
>>>>
>>>> Btw, I wasn't asked yet for the tag (RC1), but I think that will happen later, right?
>>>>
>>>> Here's the console:
>>>>
>>>> ...
>>>> [INFO] [INFO] Reactor Summary:
>>>> [INFO] [INFO]
>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... SUCCESS [33.945s]
>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SUCCESS [25.917s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine  SUCCESS [24.788s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide  SUCCESS [23.878s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SUCCESS [9.476s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons  SUCCESS [14.046s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SUCCESS [12.535s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Documentation .............. SUCCESS [26.484s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  SUCCESS [7.376s]
>>>> [INFO] [INFO] ------------------------------------------------------------------------
>>>> [INFO] [INFO] BUILD SUCCESS
>>>> [INFO] [INFO] ------------------------------------------------------------------------
>>>> [INFO] [INFO] Total time: 2:59.468s
>>>> [INFO] [INFO] Finished at: Mon Jan 21 19:24:28 CET 2013
>>>> [INFO] [INFO] Final Memory: 146M/461M
>>>> [INFO] [INFO] ------------------------------------------------------------------------
>>>> [INFO] Checking in modified POMs...
>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file C:\Users\pkluegl\AppData\Local\Temp\maven-scm-1977004734.commit --targets C:\Users\pkluegl\AppData\Local\Temp\maven-scm-2678525437479394015-targets"
>>>> [INFO] Working directory: D:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>> [INFO] Tagging release with the label uimaj-textmarker-parent-2.0.0...
>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\Users\pkluegl\AppData\Local\Temp\maven-scm-343353279.commit --revision 1436535 https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmarker-parent-2.0.0"
>>>> [INFO] Working directory: d:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Reactor Summary:
>>>> [INFO]
>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... FAILURE [3:16.435s]
>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SKIPPED
>>>> [INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  SKIPPED
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] BUILD FAILURE
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Total time: 3:18.044s
>>>> [INFO] Finished at: Mon Jan 21 19:24:41 CET 2013
>>>> [INFO] Final Memory: 17M/221M
>>>> [INFO] ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on project uimaj-textmarker-parent: Unable to tag SCM
>>>> [ERROR] Provider message:
>>>> [ERROR] The svn tag command failed.
>>>> [ERROR] Command output:
>>>> [ERROR] svn: E160006: No such revision 1436535
>>>> [ERROR] -> [Help 1]
>>>> [ERROR]
>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>> [ERROR]
>>>> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>>>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Thanks for the pointer, we figured out something along these lines meanwhile after re-reading the poms. We got a bit confused at one point because we thought the "skip deploy" would be in the apache-release profile, which it turned out not to be, it's in a different profile in the UIMA build master POM. Anyway, it ended up somehow being in the TM pom within the apache-release profile and after removing it from there, things started to improve ;)

-- Richard

Am 23.01.2013 um 19:34 schrieb Marshall Schor <ms...@schor.com>:

> On 1/22/2013 9:12 AM, Richard Eckart de Castilho wrote:
>> Yup, sounds like the culprit. The "apache-release" profile is used to simulate a release, isn't it? So that setting would be there to avoid the staging, which makes sense. During a "mvn release:perform", the profile "apache-release" shouldn't be active 
> 
> Whoops, this is backwards I think.  The apache-wide POM [1] configures the
> maven-release-plugin to use the profile "apache-release" when doing the deploy
> goal, see [2] for some documentation on how this setting is done. 
> 
> We enable apache-release manually, to simulate a release, without doing the mvn
> release... plugin.
> 
> -Marshall
> 
> [1] http://repo1.maven.org/maven2/org/apache/apache/10/apache-10.pom
> [2]
> http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html


-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
On 1/22/2013 9:12 AM, Richard Eckart de Castilho wrote:
> Yup, sounds like the culprit. The "apache-release" profile is used to simulate a release, isn't it? So that setting would be there to avoid the staging, which makes sense. During a "mvn release:perform", the profile "apache-release" shouldn't be active 

Whoops, this is backwards I think.  The apache-wide POM [1] configures the
maven-release-plugin to use the profile "apache-release" when doing the deploy
goal, see [2] for some documentation on how this setting is done. 

We enable apache-release manually, to simulate a release, without doing the mvn
release... plugin.

-Marshall

[1] http://repo1.maven.org/maven2/org/apache/apache/10/apache-10.pom
[2]
http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html

> and the setting shouldn't be used outside that profile unless you really want to avoid deploying dist zips or such.
>
> -- Richard
>
> Am 22.01.2013 um 15:01 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>
>> it says:
>>
>> [INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ uimaj-textmarker-parent ---
>> [INFO] [INFO] Skipping artifact deployment
>>
>> looks like my parent pom is not correctly configured. I found in the profile "apache-release":
>>
>> <plugin>
>>     <artifactId>maven-deploy-plugin</artifactId>
>>     <configuration>
>>            <skip>true</skip>
>>     </configuration>
>> </plugin>
>>
>> I copied this, when I created the my textmarker parent pom. The original setting is in build/trunk/parent-pom.
>> There is a comment about "https://issues.apache.org/jira/browse/UIMA-2008". Would that not also be a problem for uimaj releases? I think I can remove this in my pom, right?
>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
I redid everything and now I was able to close the repository. I don't 
know what the problem was.

Peter

On 22.01.2013 17:54, Peter Klügl wrote:
> A short update:
>
> I removed the skip option in my parent pom and now the release was 
> uploaded to the staging area. However, I cannot close the repository 
> because the signing key is not recognized:
>
> <quote>
> Staging ruleset evaluation on repository 'org.apache.uima-153 
> (u:pkluegl, a:132.187.15.93)' has failed.
>
> Staging Signature Validation
>     -No public key: Key with id: (66d69cca068e30f8) was not able to be 
> located on http://gpg-keyserver.de/. Upload your public key and try 
> the operation again.
>     -No public key: Key with id: (66d69cca068e30f8) was not able to be 
> located on http://pool.sks-keyservers.net:11371. Upload your public 
> key and try the operation again.
>     -No public key: Key with id: (66d69cca068e30f8) was not able to be 
> located on http://pgp.mit.edu:11371. Upload your public key and try 
> the operation again.
> </quote>
>
> I created my key following the instuctions I found on apache.org and 
> also uploaded it to some key servers, added it to my LDAP account and 
> to the KEYS file. After a short internet search, I think the key used 
> a sub key for signing. I removed the subkey, but this resulted in a 
> changed public key. So, my next steps would be to revoke my key, drop 
> the repository and rollback the changes again in order to do the 
> release process again with a new key.
>
> Although I am not sure, if this is really the problem...
>
> Any better ideas?
>
> What are your best practices to create a valid key?
>
> Peter
>
>
> On 22.01.2013 15:12, Richard Eckart de Castilho wrote:
>> Yup, sounds like the culprit. The "apache-release" profile is used to 
>> simulate a release, isn't it? So that setting would be there to avoid 
>> the staging, which makes sense. During a "mvn release:perform", the 
>> profile "apache-release" shouldn't be active and the setting 
>> shouldn't be used outside that profile unless you really want to 
>> avoid deploying dist zips or such.
>>
>> -- Richard
>>
>> Am 22.01.2013 um 15:01 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>>
>>> it says:
>>>
>>> [INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ 
>>> uimaj-textmarker-parent ---
>>> [INFO] [INFO] Skipping artifact deployment
>>>
>>> looks like my parent pom is not correctly configured. I found in the 
>>> profile "apache-release":
>>>
>>> <plugin>
>>>      <artifactId>maven-deploy-plugin</artifactId>
>>>      <configuration>
>>>             <skip>true</skip>
>>>      </configuration>
>>> </plugin>
>>>
>>> I copied this, when I created the my textmarker parent pom. The 
>>> original setting is in build/trunk/parent-pom.
>>> There is a comment about 
>>> "https://issues.apache.org/jira/browse/UIMA-2008". Would that not 
>>> also be a problem for uimaj releases? I think I can remove this in 
>>> my pom, right?
>>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
A short update:

I removed the skip option in my parent pom and now the release was 
uploaded to the staging area. However, I cannot close the repository 
because the signing key is not recognized:

<quote>
Staging ruleset evaluation on repository 'org.apache.uima-153 
(u:pkluegl, a:132.187.15.93)' has failed.

Staging Signature Validation
     -No public key: Key with id: (66d69cca068e30f8) was not able to be 
located on http://gpg-keyserver.de/. Upload your public key and try the 
operation again.
     -No public key: Key with id: (66d69cca068e30f8) was not able to be 
located on http://pool.sks-keyservers.net:11371. Upload your public key 
and try the operation again.
     -No public key: Key with id: (66d69cca068e30f8) was not able to be 
located on http://pgp.mit.edu:11371. Upload your public key and try the 
operation again.
</quote>

I created my key following the instuctions I found on apache.org and 
also uploaded it to some key servers, added it to my LDAP account and to 
the KEYS file. After a short internet search, I think the key used a sub 
key for signing. I removed the subkey, but this resulted in a changed 
public key. So, my next steps would be to revoke my key, drop the 
repository and rollback the changes again in order to do the release 
process again with a new key.

Although I am not sure, if this is really the problem...

Any better ideas?

What are your best practices to create a valid key?

Peter


On 22.01.2013 15:12, Richard Eckart de Castilho wrote:
> Yup, sounds like the culprit. The "apache-release" profile is used to simulate a release, isn't it? So that setting would be there to avoid the staging, which makes sense. During a "mvn release:perform", the profile "apache-release" shouldn't be active and the setting shouldn't be used outside that profile unless you really want to avoid deploying dist zips or such.
>
> -- Richard
>
> Am 22.01.2013 um 15:01 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>
>> it says:
>>
>> [INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ uimaj-textmarker-parent ---
>> [INFO] [INFO] Skipping artifact deployment
>>
>> looks like my parent pom is not correctly configured. I found in the profile "apache-release":
>>
>> <plugin>
>>      <artifactId>maven-deploy-plugin</artifactId>
>>      <configuration>
>>             <skip>true</skip>
>>      </configuration>
>> </plugin>
>>
>> I copied this, when I created the my textmarker parent pom. The original setting is in build/trunk/parent-pom.
>> There is a comment about "https://issues.apache.org/jira/browse/UIMA-2008". Would that not also be a problem for uimaj releases? I think I can remove this in my pom, right?
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Yup, sounds like the culprit. The "apache-release" profile is used to simulate a release, isn't it? So that setting would be there to avoid the staging, which makes sense. During a "mvn release:perform", the profile "apache-release" shouldn't be active and the setting shouldn't be used outside that profile unless you really want to avoid deploying dist zips or such.

-- Richard

Am 22.01.2013 um 15:01 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:

> it says:
> 
> [INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ uimaj-textmarker-parent ---
> [INFO] [INFO] Skipping artifact deployment
> 
> looks like my parent pom is not correctly configured. I found in the profile "apache-release":
> 
> <plugin>
>     <artifactId>maven-deploy-plugin</artifactId>
>     <configuration>
>            <skip>true</skip>
>     </configuration>
> </plugin>
> 
> I copied this, when I created the my textmarker parent pom. The original setting is in build/trunk/parent-pom.
> There is a comment about "https://issues.apache.org/jira/browse/UIMA-2008". Would that not also be a problem for uimaj releases? I think I can remove this in my pom, right?


-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
it says:

[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ 
uimaj-textmarker-parent ---
[INFO] [INFO] Skipping artifact deployment

looks like my parent pom is not correctly configured. I found in the 
profile "apache-release":

<plugin>
      <artifactId>maven-deploy-plugin</artifactId>
      <configuration>
             <skip>true</skip>
      </configuration>
</plugin>

I copied this, when I created the my textmarker parent pom. The original 
setting is in build/trunk/parent-pom.
There is a comment about 
"https://issues.apache.org/jira/browse/UIMA-2008". Would that not also 
be a problem for uimaj releases? I think I can remove this in my pom, right?

Peter

Here's the complete log:


D:\work\tmb8>mvn release:perform
[INFO] Scanning for projects...
[INFO] 
------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Apache UIMA TextMarker: uimaj-textmarker-parent
[INFO] Apache UIMA TextMarker: uimaj-textmarker
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler
[INFO] Apache UIMA TextMarker Documentation
[INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature
[INFO]
[INFO] 
------------------------------------------------------------------------
[INFO] Building Apache UIMA TextMarker: uimaj-textmarker-parent 
2.0.1-SNAPSHOT
[INFO] 
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-release-plugin:2.1:perform (default-cli) @ 
uimaj-textmarker-parent ---
[INFO] Checking out the project to perform the release ...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout 
https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmark
er-parent-2.0.0-rc1 D:\work\tmb8\target\checkout"
[INFO] Working directory: D:\work\tmb8\target
[INFO] Executing goals 'deploy'...
[WARNING] Maven will be executed in interactive mode, but no input 
stream has been configured for this MavenInvoker instance.
[INFO] [INFO] Scanning for projects...
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Reactor Build Order:
[INFO] [INFO]
[INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent
[INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker
[INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine
[INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide
[INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor
[INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons
[INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler
[INFO] [INFO] Apache UIMA TextMarker Documentation
[INFO] [INFO] Apache UIMA TextMarker Eclipse: 
uimaj-textmarker-eclipse-feature
[INFO] [INFO]
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Building Apache UIMA TextMarker: uimaj-textmarker-parent 2.0.0
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO]
[INFO] [INFO] --- build-helper-maven-plugin:1.5:parse-version 
(parse-project-version) @ uimaj-textmarker-parent ---
[INFO] [INFO]
[INFO] [INFO] --- uima-build-helper-maven-plugin:2:parse-date-time (set 
buildYear and buildMonth) @ uimaj-textmarker-parent ---
[INFO] [INFO]
[INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) 
@ uimaj-textmarker-parent ---
[INFO] [INFO]
[INFO] [INFO] --- maven-changes-plugin:2.8:jira-report (default-cli) @ 
uimaj-textmarker-parent ---
[INFO] [WARNING] Deprecated API called - not 
org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. 
Please update this plug
in.
[INFO] [INFO] Downloading from JIRA at: 
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=1
000&reset=true&jqlQuery=project+%3D+UIMA+AND+fixVersion+in+%2812323872%29+AND+status+in+%28Closed%2C+Resolved%29+AND+resolution+in+%28Fixed%
29+AND+component+in+%28TextMarker%29+ORDER+BY+type+ASC%2C+status+ASC%2C+key+ASC
[INFO] [INFO] The JIRA version is '5.2.1'
[INFO] [INFO]
[INFO] [INFO] --- maven-assembly-plugin:2.2.1:single 
(source-release-assembly) @ uimaj-textmarker-parent ---
[INFO] [INFO] uimaj-textmarker-parent-2.0.0/ already added, skipping
[INFO] [INFO] uimaj-textmarker-parent-2.0.0/LICENSE already added, skipping
[INFO] [INFO] uimaj-textmarker-parent-2.0.0/NOTICE already added, skipping
[INFO] [INFO] Building zip: 
D:\work\tmb8\target\checkout\target\uimaj-textmarker-parent-2.0.0-source-release.zip
[INFO] [INFO] uimaj-textmarker-parent-2.0.0/ already added, skipping
[INFO] [INFO] uimaj-textmarker-parent-2.0.0/LICENSE already added, skipping
[INFO] [INFO] uimaj-textmarker-parent-2.0.0/NOTICE already added, skipping
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar-no-fork 
(attach-sources-nf) @ uimaj-textmarker-parent ---
[INFO] [INFO]
[INFO] [INFO] --- maven-site-plugin:3.0:attach-descriptor 
(attach-descriptor) @ uimaj-textmarker-parent ---
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.3:sign (default) @ 
uimaj-textmarker-parent ---
[INFO] [INFO]
[INFO] [INFO] --- apache-rat-plugin:0.7:check (default-cli) @ 
uimaj-textmarker-parent ---
[INFO] [INFO] Exclude: target/**
[INFO] [INFO] Exclude: example-projects/**
[INFO] [INFO] Exclude: README*
[INFO] [INFO] Exclude: RELEASE_NOTES*
[INFO] [INFO] Exclude: issuesFixed/**
[INFO] [INFO] Exclude: src/main/resources/docbook-shared/titlepage/*.xsl
[INFO] [INFO] Exclude: marker-file-identifying-*
[INFO] [INFO] Exclude: DEPENDENCIES
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
uimaj-textmarker-parent ---
[INFO] [INFO] Installing D:\work\tmb8\target\checkout\pom.xml to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-textmarker-parent\2.0
.0\uimaj-textmarker-parent-2.0.0.pom
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\target\uimaj-textmarker-parent-2.0.0-source-release.zip 
to C:\Users\pkluegl\.m2\reposi
tory\org\apache\uima\uimaj-textmarker-parent\2.0.0\uimaj-textmarker-parent-2.0.0-source-release.zip
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\target\uimaj-textmarker-parent-2.0.0.pom.asc to 
C:\Users\pkluegl\.m2\repository\org\ap
ache\uima\uimaj-textmarker-parent\2.0.0\uimaj-textmarker-parent-2.0.0.pom.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\target\uimaj-textmarker-parent-2.0.0-source-release.zip.asc 
to C:\Users\pkluegl\.m2\re
pository\org\apache\uima\uimaj-textmarker-parent\2.0.0\uimaj-textmarker-parent-2.0.0-source-release.zip.asc
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ 
uimaj-textmarker-parent ---
[INFO] [INFO] Skipping artifact deployment
[INFO] [INFO]
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Building Apache UIMA TextMarker: uimaj-textmarker 2.0.0
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO]
[INFO] [INFO] --- build-helper-maven-plugin:1.5:parse-version 
(parse-project-version) @ uimaj-textmarker ---
[INFO] [INFO]
[INFO] [INFO] --- uima-build-helper-maven-plugin:2:parse-date-time (set 
buildYear and buildMonth) @ uimaj-textmarker ---
[INFO] [INFO]
[INFO] [INFO] --- antlr3-maven-plugin:3.1.3-1:antlr (run antlr) @ 
uimaj-textmarker ---
[INFO] [INFO] ANTLR: Processing source directory 
D:\work\tmb8\target\checkout\uimaj-textmarker\src\main\antlr3
[INFO] ANTLR Parser Generator  Version 3.1.3 Mar 17, 2009 19:23:44
[INFO] org\apache\uima\textmarker\parser\TextMarkerLexer.g
[INFO] org\apache\uima\textmarker\parser\TextMarkerParser.g
[INFO] [INFO]
[INFO] [INFO] --- build-helper-maven-plugin:1.5:add-source (add-source) 
@ uimaj-textmarker ---
[INFO] [INFO] Source directory: 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\generated-sources\antlr3 
added.
[INFO] [INFO]
[INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) 
@ uimaj-textmarker ---
[INFO] [INFO]
[INFO] [INFO] --- maven-changes-plugin:2.8:jira-report (default-cli) @ 
uimaj-textmarker ---
[INFO] [WARNING] Deprecated API called - not 
org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. 
Please update this plug
in.
[INFO] [INFO] Downloading from JIRA at: 
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=1
000&reset=true&jqlQuery=project+%3D+UIMA+AND+fixVersion+in+%2812323872%29+AND+status+in+%28Closed%2C+Resolved%29+AND+resolution+in+%28Fixed%
29+AND+component+in+%28TextMarker%29+ORDER+BY+type+ASC%2C+status+ASC%2C+key+ASC
[INFO] [INFO] The JIRA version is '5.2.1'
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:resources 
(default-resources) @ uimaj-textmarker ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 13 resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) 
@ uimaj-textmarker ---
[INFO] [INFO] Compiling 309 source files to 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\classes
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:testResources 
(default-testResources) @ uimaj-textmarker ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 146 resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile 
(default-testCompile) @ uimaj-textmarker ---
[INFO] [INFO] Compiling 80 source files to 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\test-classes
[INFO] [INFO]
[INFO] [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ 
uimaj-textmarker ---
[INFO] [INFO] Surefire report directory: 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\surefire-reports
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.uima.textmarker.action.ClearTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.862 sec
[INFO] Running org.apache.uima.textmarker.action.CreateTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.083 sec
[INFO] Running org.apache.uima.textmarker.action.FillTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.074 sec
[INFO] Running org.apache.uima.textmarker.action.FilterTypeTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.109 sec
[INFO] Running org.apache.uima.textmarker.action.GatherTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.072 sec
[INFO] Running org.apache.uima.textmarker.action.GetFeatureTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.084 sec
[INFO] Running org.apache.uima.textmarker.action.GetListTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.059 sec
[INFO] Running org.apache.uima.textmarker.action.GetTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.073 sec
[INFO] Running org.apache.uima.textmarker.action.MarkFastTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.069 sec
[INFO] Running org.apache.uima.textmarker.action.MarkLastTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.053 sec
[INFO] Running org.apache.uima.textmarker.action.MarkOnceTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.052 sec
[INFO] Running org.apache.uima.textmarker.action.MarkScoreTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.059 sec
[INFO] Running org.apache.uima.textmarker.action.MarkTableTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.055 sec
[INFO] Running org.apache.uima.textmarker.action.MarkTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.049 sec
[INFO] Running org.apache.uima.textmarker.action.MatchedTextTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.089 sec
[INFO] Running org.apache.uima.textmarker.action.MergeTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.059 sec
[INFO] Running org.apache.uima.textmarker.action.RemoveDuplicateTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.046 sec
[INFO] Running org.apache.uima.textmarker.action.RemoveTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.049 sec
[INFO] Running org.apache.uima.textmarker.action.ReplaceTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.046 sec
[INFO] Running org.apache.uima.textmarker.action.RetainTypeTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.045 sec
[INFO] Running org.apache.uima.textmarker.action.SetFeatureTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.042 sec
[INFO] Running org.apache.uima.textmarker.action.ShiftTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.042 sec
[INFO] Running org.apache.uima.textmarker.action.TransferTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.044 sec
[INFO] Running org.apache.uima.textmarker.action.TrieTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.051 sec
[INFO] Running org.apache.uima.textmarker.action.TrimTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.042 sec
[INFO] Running org.apache.uima.textmarker.action.UnmarkAllTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.041 sec
[INFO] Running org.apache.uima.textmarker.action.UnmarkTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.186 sec
[INFO] Running org.apache.uima.textmarker.AllActionsTest
[INFO] Tests run: 27, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.126 sec
[INFO] Running org.apache.uima.textmarker.AllConditionsTest
[INFO] Tests run: 27, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.028 sec
[INFO] Running org.apache.uima.textmarker.condition.AfterTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.029 sec
[INFO] Running org.apache.uima.textmarker.condition.AndTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.034 sec
[INFO] Running org.apache.uima.textmarker.condition.BeforeTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.029 sec
[INFO] Running org.apache.uima.textmarker.condition.ContainsTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.027 sec
[INFO] Running org.apache.uima.textmarker.condition.ContextCountTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.028 sec
[INFO] Running org.apache.uima.textmarker.condition.CountTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.026 sec
[INFO] Running org.apache.uima.textmarker.condition.CurrentCountTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.071 sec
[INFO] Running org.apache.uima.textmarker.condition.EndsWithTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.027 sec
[INFO] Running org.apache.uima.textmarker.condition.FeatureTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.029 sec
[INFO] Running org.apache.uima.textmarker.condition.IfTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.026 sec
[INFO] Running org.apache.uima.textmarker.condition.InListTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.026 sec
[INFO] Running org.apache.uima.textmarker.condition.IsTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.026 sec
[INFO] Running org.apache.uima.textmarker.condition.LastTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.028 sec
[INFO] Running org.apache.uima.textmarker.condition.MOfNTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.025 sec
[INFO] Running org.apache.uima.textmarker.condition.NearTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.013 sec
[INFO] Running org.apache.uima.textmarker.condition.NotTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.025 sec
[INFO] Running org.apache.uima.textmarker.condition.OrTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.032 sec
[INFO] Running org.apache.uima.textmarker.condition.ParseTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.04 sec
[INFO] Running org.apache.uima.textmarker.condition.PartOfNEQTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.027 sec
[INFO] Running org.apache.uima.textmarker.condition.PartOfTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.023 sec
[INFO] Running org.apache.uima.textmarker.condition.PositionTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.081 sec
[INFO] Running org.apache.uima.textmarker.condition.RegExpTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.023 sec
[INFO] Running org.apache.uima.textmarker.condition.ScoreTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.025 sec
[INFO] Running org.apache.uima.textmarker.condition.SizeTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.023 sec
[INFO] Running org.apache.uima.textmarker.condition.StartsWithTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.022 sec
[INFO] Running org.apache.uima.textmarker.condition.TotalCountTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.023 sec
[INFO] Running org.apache.uima.textmarker.condition.VoteTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.023 sec
[INFO] Running org.apache.uima.textmarker.DynamicAnchoringTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.043 sec
[INFO] Running org.apache.uima.textmarker.EmptyDocumentTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.024 sec
[INFO] Running org.apache.uima.textmarker.engine.HtmlAnnotatorTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.063 sec
[INFO] Running org.apache.uima.textmarker.engine.TextMarkerModifierTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.041 sec
[INFO] Running org.apache.uima.textmarker.FilteringTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.025 sec
[INFO] Running org.apache.uima.textmarker.LiteralStringMatchTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.031 sec
[INFO] Running org.apache.uima.textmarker.LongGreedyTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.001 sec
[INFO] Running org.apache.uima.textmarker.OptionalComposedEndTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.018 sec
[INFO] Running org.apache.uima.textmarker.OutOfWindowTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.079 sec
[INFO] Running org.apache.uima.textmarker.RuleInferenceTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.042 sec
[INFO] Running org.apache.uima.textmarker.seed.DefaultSeederTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.015 sec
[INFO] Running org.apache.uima.textmarker.SubAtomicTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.041 sec
[INFO] Running org.apache.uima.textmarker.verbalizer.ActionVerbalizerTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
[INFO] Running org.apache.uima.textmarker.verbalizer.ConditionVerbalizerTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.002 sec
[INFO] Running 
org.apache.uima.textmarker.verbalizer.ExpressionVerbalizerTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests run: 123, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] [INFO]
[INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
uimaj-textmarker ---
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\uima-textmarker.jar
[INFO] [INFO]
[INFO] [INFO] --- maven-assembly-plugin:2.2.1:single 
(source-release-assembly) @ uimaj-textmarker ---
[INFO] [INFO] Skipping the assembly in this project because it's not the 
Execution Root
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar-no-fork 
(attach-sources-nf) @ uimaj-textmarker ---
[INFO] [INFO] org already added, skipping
[INFO] [INFO] org\apache already added, skipping
[INFO] [INFO] org\apache\uima already added, skipping
[INFO] [INFO] org\apache\uima\textmarker already added, skipping
[INFO] [INFO] org already added, skipping
[INFO] [INFO] org\apache already added, skipping
[INFO] [INFO] org\apache\uima already added, skipping
[INFO] [INFO] org\apache\uima\textmarker already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\engine already added, skipping
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\uima-textmarker-sources.jar
[INFO] [INFO] org already added, skipping
[INFO] [INFO] org\apache already added, skipping
[INFO] [INFO] org\apache\uima already added, skipping
[INFO] [INFO] org\apache\uima\textmarker already added, skipping
[INFO] [INFO] org already added, skipping
[INFO] [INFO] org\apache already added, skipping
[INFO] [INFO] org\apache\uima already added, skipping
[INFO] [INFO] org\apache\uima\textmarker already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\engine already added, skipping
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO]
[INFO] [INFO] --- maven-site-plugin:3.0:attach-descriptor 
(attach-descriptor) @ uimaj-textmarker ---
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.3:sign (default) @ uimaj-textmarker ---
[INFO] [INFO]
[INFO] [INFO] --- apache-rat-plugin:0.7:check (default-cli) @ 
uimaj-textmarker ---
[INFO] [INFO] Exclude: src/main/java/org/apache/uima/textmarker/type/*.java
[INFO] [INFO] Exclude: 
src/main/antlr3/org/apache/uima/textmarker/parser/TextMarkerLexer.tokens
[INFO] [INFO] Exclude: 
src/test/resources/org/apache/uima/textmarker/action/*.tm
[INFO] [INFO] Exclude: src/test/resources/org/apache/uima/textmarker/*.txt
[INFO] [INFO] Exclude: src/test/resources/org/apache/uima/textmarker/*.tm
[INFO] [INFO] Exclude: 
src/test/resources/org/apache/uima/textmarker/action/*.*
[INFO] [INFO] Exclude: 
src/test/resources/org/apache/uima/textmarker/condition/*.txt
[INFO] [INFO] Exclude: 
src/test/resources/org/apache/uima/textmarker/condition/*.tm
[INFO] [INFO] Exclude: 
src/test/resources/org/apache/uima/textmarker/seed/*.txt
[INFO] [INFO] Exclude: 
src/test/resources/org/apache/uima/textmarker/seed/*.tm
[INFO] [INFO] Exclude: 
src/test/resources/org/apache/uima/textmarker/engine/*.html
[INFO] [INFO] Exclude: 
src/test/resources/org/apache/uima/textmarker/engine/*.tm
[INFO] [INFO] Exclude: issuesFixed/**
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
uimaj-textmarker ---
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\uima-textmarker.jar 
to C:\Users\pkluegl\.m2\repository\org\apa
che\uima\uimaj-textmarker\2.0.0\uimaj-textmarker-2.0.0.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker\pom.xml to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-text
marker\2.0.0\uimaj-textmarker-2.0.0.pom
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\uima-textmarker-sources.jar 
to C:\Users\pkluegl\.m2\repository
\org\apache\uima\uimaj-textmarker\2.0.0\uimaj-textmarker-2.0.0-sources.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\uima-textmarker.jar.asc 
to C:\Users\pkluegl\.m2\repository\org
\apache\uima\uimaj-textmarker\2.0.0\uimaj-textmarker-2.0.0.jar.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\uima-textmarker.pom.asc 
to C:\Users\pkluegl\.m2\repository\org
\apache\uima\uimaj-textmarker\2.0.0\uimaj-textmarker-2.0.0.pom.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\uima-textmarker-sources.jar.asc 
to C:\Users\pkluegl\.m2\reposi
tory\org\apache\uima\uimaj-textmarker\2.0.0\uimaj-textmarker-2.0.0-sources.jar.asc
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ 
uimaj-textmarker ---
[INFO] [INFO] Skipping artifact deployment
[INFO] [INFO]
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Building Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-engine 2.0.0
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO]
[INFO] [INFO] --- build-helper-maven-plugin:1.5:parse-version 
(parse-project-version) @ uimaj-ep-textmarker-engine ---
[INFO] [INFO]
[INFO] [INFO] --- uima-build-helper-maven-plugin:2:parse-date-time (set 
buildYear and buildMonth) @ uimaj-ep-textmarker-engine ---
[INFO] [INFO]
[INFO] [INFO] --- maven-dependency-plugin:2.3:unpack-dependencies 
(unpackDependentJars) @ uimaj-ep-textmarker-engine ---
[INFO] [INFO] Unpacking 
C:\Users\pkluegl\.m2\repository\antlr\antlr\2.7.7\antlr-2.7.7.jar to 
D:\work\tmb8\target\checkout\uimaj-ep-textmarke
r-engine\target\classes with includes "" and excludes ""
[INFO] [INFO] Unpacking 
C:\Users\pkluegl\.m2\repository\org\antlr\stringtemplate\3.2\stringtemplate-3.2.jar 
to D:\work\tmb8\target\checkout\
uimaj-ep-textmarker-engine\target\classes with includes "" and excludes ""
[INFO] [INFO] Unpacking 
C:\Users\pkluegl\.m2\repository\org\apache\commons\commons-lang3\3.1\commons-lang3-3.1.jar 
to D:\work\tmb8\target\ch
eckout\uimaj-ep-textmarker-engine\target\classes with includes "" and 
excludes ""
[INFO] [INFO] Unpacking 
D:\work\tmb8\target\checkout\uimaj-textmarker\target\uima-textmarker.jar 
to D:\work\tmb8\target\checkout\uimaj-ep-te
xtmarker-engine\target\classes with includes "" and excludes ""
[INFO] [INFO] Unpacking 
C:\Users\pkluegl\.m2\repository\commons-collections\commons-collections\3.2.1\commons-collections-3.2.1.jar 
to D:\wo
rk\tmb8\target\checkout\uimaj-ep-textmarker-engine\target\classes with 
includes "" and excludes ""
[INFO] [INFO] Unpacking 
C:\Users\pkluegl\.m2\repository\org\antlr\antlr\3.1.3\antlr-3.1.3.jar to 
D:\work\tmb8\target\checkout\uimaj-ep-textm
arker-engine\target\classes with includes "" and excludes ""
[INFO] [INFO] Unpacking 
C:\Users\pkluegl\.m2\repository\org\antlr\antlr-runtime\3.1.3\antlr-runtime-3.1.3.jar 
to D:\work\tmb8\target\checkou
t\uimaj-ep-textmarker-engine\target\classes with includes "" and excludes ""
[INFO] [INFO] Unpacking 
C:\Users\pkluegl\.m2\repository\org\htmlparser\htmlparser\1.6\htmlparser-1.6.jar 
to D:\work\tmb8\target\checkout\uim
aj-ep-textmarker-engine\target\classes with includes "" and excludes ""
[INFO] [INFO]
[INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) 
@ uimaj-ep-textmarker-engine ---
[INFO] [INFO]
[INFO] [INFO] --- maven-changes-plugin:2.8:jira-report (default-cli) @ 
uimaj-ep-textmarker-engine ---
[INFO] [WARNING] Deprecated API called - not 
org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. 
Please update this plug
in.
[INFO] [INFO] Downloading from JIRA at: 
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=1
000&reset=true&jqlQuery=project+%3D+UIMA+AND+fixVersion+in+%2812323872%29+AND+status+in+%28Closed%2C+Resolved%29+AND+resolution+in+%28Fixed%
29+AND+component+in+%28TextMarker%29+ORDER+BY+type+ASC%2C+status+ASC%2C+key+ASC
[INFO] [INFO] The JIRA version is '5.2.1'
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:resources 
(default-resources) @ uimaj-ep-textmarker-engine ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 1 resource
[INFO] [INFO] Copying 0 resource
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) 
@ uimaj-ep-textmarker-engine ---
[INFO] [INFO] No sources to compile
[INFO] [INFO]
[INFO] [INFO] --- maven-bundle-plugin:2.3.4:manifest (uima-bundle) @ 
uimaj-ep-textmarker-engine ---
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:testResources 
(default-testResources) @ uimaj-ep-textmarker-engine ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] skip non existing resourceDirectory 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-engine\src\test\resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile 
(default-testCompile) @ uimaj-ep-textmarker-engine ---
[INFO] [INFO] No sources to compile
[INFO] [INFO]
[INFO] [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ 
uimaj-ep-textmarker-engine ---
[INFO] [INFO] Surefire report directory: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-engine\target\surefire-reports
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] [INFO]
[INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
uimaj-ep-textmarker-engine ---
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-engine\target\org.apache.uima.textmarker.engine_2.0.0.jar
[INFO] [INFO]
[INFO] [INFO] --- maven-assembly-plugin:2.2.1:single 
(source-release-assembly) @ uimaj-ep-textmarker-engine ---
[INFO] [INFO] Skipping the assembly in this project because it's not the 
Execution Root
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar-no-fork 
(attach-sources-nf) @ uimaj-ep-textmarker-engine ---
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-engine\target\org.apache.uima.textmarker.engine_2.0.0-sources.j
ar
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO]
[INFO] [INFO] --- maven-site-plugin:3.0:attach-descriptor 
(attach-descriptor) @ uimaj-ep-textmarker-engine ---
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.3:sign (default) @ 
uimaj-ep-textmarker-engine ---
[INFO] [INFO]
[INFO] [INFO] --- apache-rat-plugin:0.7:check (default-cli) @ 
uimaj-ep-textmarker-engine ---
[INFO] [INFO] Exclude: release.properties
[INFO] [INFO] Exclude: marker-file-identifying-*
[INFO] [INFO] Exclude: issuesFixed/**
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
uimaj-ep-textmarker-engine ---
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-engine\target\org.apache.uima.textmarker.engine_2.0.0.jar 
to C:\Us
ers\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-engine\2.0.0\uimaj-ep-textmarker-engine-2.0.0.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-engine\pom.xml to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\
uimaj-ep-textmarker-engine\2.0.0\uimaj-ep-textmarker-engine-2.0.0.pom
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-engine\target\org.apache.uima.textmarker.engine_2.0.0-sources.jar
to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-engine\2.0.0\uimaj-ep-textmarker-engine-2.0.0-sources.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-engine\target\org.apache.uima.textmarker.engine_2.0.0.jar.asc 
to C
:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-engine\2.0.0\uimaj-ep-textmarker-engine-2.0.0.jar.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-engine\target\org.apache.uima.textmarker.engine_${parsedVersion.os
giVersion}.pom.asc to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-engine\2.0.0\uimaj-ep-textmarker-engine-2.0.0.pom.
asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-engine\target\org.apache.uima.textmarker.engine_2.0.0-sources.jar.
asc to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-engine\2.0.0\uimaj-ep-textmarker-engine-2.0.0-sources.jar.asc
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ 
uimaj-ep-textmarker-engine ---
[INFO] [INFO] Skipping artifact deployment
[INFO] [INFO]
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Building Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-ide 2.0.0
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [WARNING] The POM for org.eclipse.equinox:app:jar:1.0.0 is 
missing, no dependency information available
[INFO] [WARNING] The POM for org.eclipse.emf:ecore:jar:2.4.0 is missing, 
no dependency information available
[INFO] [WARNING] The POM for org.eclipse.emf.ecore:xmi:jar:2.4.0 is 
missing, no dependency information available
[INFO] [WARNING] The POM for org.eclipse.dltk:core:jar:3.0.0 is missing, 
no dependency information available
[INFO] [WARNING] The POM for org.eclipse.dltk:ui:jar:3.0.0 is missing, 
no dependency information available
[INFO] [WARNING] The POM for org.eclipse.dltk:debug:jar:3.0.0 is 
missing, no dependency information available
[INFO] [INFO]
[INFO] [INFO] --- build-helper-maven-plugin:1.5:parse-version 
(parse-project-version) @ uimaj-ep-textmarker-ide ---
[INFO] [INFO]
[INFO] [INFO] --- uima-build-helper-maven-plugin:2:parse-date-time (set 
buildYear and buildMonth) @ uimaj-ep-textmarker-ide ---
[INFO] [INFO]
[INFO] [INFO] --- antlr3-maven-plugin:3.1.3-1:antlr (run antlr) @ 
uimaj-ep-textmarker-ide ---
[INFO] [INFO] ANTLR: Processing source directory 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\src\main\antlr3
[INFO] ANTLR Parser Generator  Version 3.1.3 Mar 17, 2009 19:23:44
[INFO] org\apache\uima\textmarker\ide\core\parser\TextMarkerLexer.g
[INFO] org\apache\uima\textmarker\ide\core\parser\TextMarkerParser.g
[INFO] [INFO]
[INFO] [INFO] --- build-helper-maven-plugin:1.5:add-source (add-source) 
@ uimaj-ep-textmarker-ide ---
[INFO] [INFO] Source directory: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\target\generated-sources\antlr3 
added.
[INFO] [INFO]
[INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) 
@ uimaj-ep-textmarker-ide ---
[INFO] [WARNING] Missing POM for org.eclipse.equinox:app:jar:1.0.0
[INFO] [WARNING] Missing POM for org.eclipse.emf:ecore:jar:2.4.0
[INFO] [WARNING] Missing POM for org.eclipse.emf.ecore:xmi:jar:2.4.0
[INFO] [WARNING] Missing POM for org.eclipse.dltk:core:jar:3.0.0
[INFO] [WARNING] Missing POM for org.eclipse.dltk:ui:jar:3.0.0
[INFO] [WARNING] Missing POM for org.eclipse.dltk:debug:jar:3.0.0
[INFO] [INFO]
[INFO] [INFO] --- maven-changes-plugin:2.8:jira-report (default-cli) @ 
uimaj-ep-textmarker-ide ---
[INFO] [WARNING] Deprecated API called - not 
org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. 
Please update this plug
in.
[INFO] [INFO] Downloading from JIRA at: 
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=1
000&reset=true&jqlQuery=project+%3D+UIMA+AND+fixVersion+in+%2812323872%29+AND+status+in+%28Closed%2C+Resolved%29+AND+resolution+in+%28Fixed%
29+AND+component+in+%28TextMarker%29+ORDER+BY+type+ASC%2C+status+ASC%2C+key+ASC
[INFO] [INFO] The JIRA version is '5.2.1'
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:resources 
(default-resources) @ uimaj-ep-textmarker-ide ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 26 resources
[INFO] [INFO] Copying 23 resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) 
@ uimaj-ep-textmarker-ide ---
[INFO] [INFO] Compiling 325 source files to 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\target\classes
[INFO] [INFO]
[INFO] [INFO] --- maven-bundle-plugin:2.3.4:manifest (uima-bundle) @ 
uimaj-ep-textmarker-ide ---
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:testResources 
(default-testResources) @ uimaj-ep-textmarker-ide ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] skip non existing resourceDirectory 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\src\test\resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile 
(default-testCompile) @ uimaj-ep-textmarker-ide ---
[INFO] [INFO] No sources to compile
[INFO] [INFO]
[INFO] [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ 
uimaj-ep-textmarker-ide ---
[INFO] [INFO] Surefire report directory: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\target\surefire-reports
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] [INFO]
[INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
uimaj-ep-textmarker-ide ---
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\target\org.apache.uima.textmarker.ide_2.0.0.jar
[INFO] [INFO]
[INFO] [INFO] --- maven-assembly-plugin:2.2.1:single 
(source-release-assembly) @ uimaj-ep-textmarker-ide ---
[INFO] [INFO] Skipping the assembly in this project because it's not the 
Execution Root
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar-no-fork 
(attach-sources-nf) @ uimaj-ep-textmarker-ide ---
[INFO] [INFO] org already added, skipping
[INFO] [INFO] org\apache already added, skipping
[INFO] [INFO] org\apache\uima already added, skipping
[INFO] [INFO] org\apache\uima\textmarker already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\core already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\core\parser already added, 
skipping
[INFO] [INFO] org already added, skipping
[INFO] [INFO] org\apache already added, skipping
[INFO] [INFO] org\apache\uima already added, skipping
[INFO] [INFO] org\apache\uima\textmarker already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\core already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\core\packages already 
added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\debug already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\debug\ui already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\debug\ui\preferences 
already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\debugger already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\debugger\preferences 
already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\formatter already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\formatter\preferences 
already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\launching already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\console already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\documentation already 
added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\editor already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\preferences already 
added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\text already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\text\folding already 
added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\wizards already added, 
skipping
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\target\org.apache.uima.textmarker.ide_2.0.0-sources.jar
[INFO] [INFO] org already added, skipping
[INFO] [INFO] org\apache already added, skipping
[INFO] [INFO] org\apache\uima already added, skipping
[INFO] [INFO] org\apache\uima\textmarker already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\core already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\core\parser already added, 
skipping
[INFO] [INFO] org already added, skipping
[INFO] [INFO] org\apache already added, skipping
[INFO] [INFO] org\apache\uima already added, skipping
[INFO] [INFO] org\apache\uima\textmarker already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\core already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\core\packages already 
added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\debug already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\debug\ui already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\debug\ui\preferences 
already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\debugger already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\debugger\preferences 
already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\formatter already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\formatter\preferences 
already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\launching already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\console already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\documentation already 
added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\editor already added, 
skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\preferences already 
added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\text already added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\text\folding already 
added, skipping
[INFO] [INFO] org\apache\uima\textmarker\ide\ui\wizards already added, 
skipping
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO]
[INFO] [INFO] --- maven-site-plugin:3.0:attach-descriptor 
(attach-descriptor) @ uimaj-ep-textmarker-ide ---
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.3:sign (default) @ 
uimaj-ep-textmarker-ide ---
[INFO] [INFO]
[INFO] [INFO] --- apache-rat-plugin:0.7:check (default-cli) @ 
uimaj-ep-textmarker-ide ---
[INFO] [INFO] Exclude: release.properties
[INFO] [INFO] Exclude: marker-file-identifying-*
[INFO] [INFO] Exclude: 
src/main/antlr3/org/apache/uima/textmarker/ide/core/parser/TextMarkerLexer.tokens
[INFO] [INFO] Exclude: 
src/main/antlr3/org/apache/uima/textmarker/ide/core/parser/TextMarkerParser.tokens
[INFO] [INFO] Exclude: 
src/main/resources/org/apache/uima/textmarker/ide/formatter/*.tm
[INFO] [INFO] Exclude: 
src/main/resources/org/apache/uima/textmarker/ide/formatter/preferences/*.tm
[INFO] [INFO] Exclude: 
src/main/resources/org/apache/uima/textmarker/ide/launching/*.tm
[INFO] [INFO] Exclude: 
src/main/resources/org/apache/uima/textmarker/ide/ui/documentation/*.html
[INFO] [INFO] Exclude: 
src/main/resources/org/apache/uima/textmarker/ide/ui/preferences/*.txt
[INFO] [INFO] Exclude: issuesFixed/**
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
uimaj-ep-textmarker-ide ---
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\target\org.apache.uima.textmarker.ide_2.0.0.jar 
to C:\Users\pk
luegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-ide\2.0.0\uimaj-ep-textmarker-ide-2.0.0.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\pom.xml to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uim
aj-ep-textmarker-ide\2.0.0\uimaj-ep-textmarker-ide-2.0.0.pom
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\target\org.apache.uima.textmarker.ide_2.0.0-sources.jar 
to C:\
Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-ide\2.0.0\uimaj-ep-textmarker-ide-2.0.0-sources.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\target\org.apache.uima.textmarker.ide_2.0.0.jar.asc 
to C:\User
s\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-ide\2.0.0\uimaj-ep-textmarker-ide-2.0.0.jar.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\target\org.apache.uima.textmarker.ide_${parsedVersion.osgiVers
ion}.pom.asc to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-ide\2.0.0\uimaj-ep-textmarker-ide-2.0.0.pom.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-ide\target\org.apache.uima.textmarker.ide_2.0.0-sources.jar.asc 
to
  C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-ide\2.0.0\uimaj-ep-textmarker-ide-2.0.0-sources.jar.asc
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ 
uimaj-ep-textmarker-ide ---
[INFO] [INFO] Skipping artifact deployment
[INFO] [INFO]
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Building Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-caseditor 2.0.0
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO]
[INFO] [INFO] --- build-helper-maven-plugin:1.5:parse-version 
(parse-project-version) @ uimaj-ep-textmarker-caseditor ---
[INFO] [INFO]
[INFO] [INFO] --- uima-build-helper-maven-plugin:2:parse-date-time (set 
buildYear and buildMonth) @ uimaj-ep-textmarker-caseditor ---
[INFO] [INFO]
[INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) 
@ uimaj-ep-textmarker-caseditor ---
[INFO] [INFO]
[INFO] [INFO] --- maven-changes-plugin:2.8:jira-report (default-cli) @ 
uimaj-ep-textmarker-caseditor ---
[INFO] [WARNING] Deprecated API called - not 
org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. 
Please update this plug
in.
[INFO] [INFO] Downloading from JIRA at: 
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=1
000&reset=true&jqlQuery=project+%3D+UIMA+AND+fixVersion+in+%2812323872%29+AND+status+in+%28Closed%2C+Resolved%29+AND+resolution+in+%28Fixed%
29+AND+component+in+%28TextMarker%29+ORDER+BY+type+ASC%2C+status+ASC%2C+key+ASC
[INFO] [INFO] The JIRA version is '5.2.1'
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:resources 
(default-resources) @ uimaj-ep-textmarker-caseditor ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 2 resources
[INFO] [INFO] skip non existing resourceDirectory 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\src\main\resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) 
@ uimaj-ep-textmarker-caseditor ---
[INFO] [INFO] Compiling 19 source files to 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\target\classes
[INFO] [INFO]
[INFO] [INFO] --- maven-bundle-plugin:2.3.4:manifest (uima-bundle) @ 
uimaj-ep-textmarker-caseditor ---
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:testResources 
(default-testResources) @ uimaj-ep-textmarker-caseditor ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] skip non existing resourceDirectory 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\src\test\resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile 
(default-testCompile) @ uimaj-ep-textmarker-caseditor ---
[INFO] [INFO] No sources to compile
[INFO] [INFO]
[INFO] [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ 
uimaj-ep-textmarker-caseditor ---
[INFO] [INFO] Surefire report directory: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\target\surefire-reports
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] [INFO]
[INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
uimaj-ep-textmarker-caseditor ---
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\target\org.apache.uima.textmarker.caseditor_2.0.0.jar

[INFO] [INFO]
[INFO] [INFO] --- maven-assembly-plugin:2.2.1:single 
(source-release-assembly) @ uimaj-ep-textmarker-caseditor ---
[INFO] [INFO] Skipping the assembly in this project because it's not the 
Execution Root
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar-no-fork 
(attach-sources-nf) @ uimaj-ep-textmarker-caseditor ---
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\target\org.apache.uima.textmarker.caseditor_2.0.0-sou
rces.jar
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO]
[INFO] [INFO] --- maven-site-plugin:3.0:attach-descriptor 
(attach-descriptor) @ uimaj-ep-textmarker-caseditor ---
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.3:sign (default) @ 
uimaj-ep-textmarker-caseditor ---
[INFO] [INFO]
[INFO] [INFO] --- apache-rat-plugin:0.7:check (default-cli) @ 
uimaj-ep-textmarker-caseditor ---
[INFO] [INFO] Exclude: release.properties
[INFO] [INFO] Exclude: src/test/resources/ManualTests/*
[INFO] [INFO] Exclude: marker-file-identifying-*
[INFO] [INFO] Exclude: issuesFixed/**
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
uimaj-ep-textmarker-caseditor ---
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\target\org.apache.uima.textmarker.caseditor_2.0.0.jar 
to
  C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-caseditor\2.0.0\uimaj-ep-textmarker-caseditor-2.0.0.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\pom.xml to 
C:\Users\pkluegl\.m2\repository\org\apache\ui
ma\uimaj-ep-textmarker-caseditor\2.0.0\uimaj-ep-textmarker-caseditor-2.0.0.pom
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\target\org.apache.uima.textmarker.caseditor_2.0.0-source
s.jar to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-caseditor\2.0.0\uimaj-ep-textmarker-caseditor-2.0.0-sources.jar

[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\target\org.apache.uima.textmarker.caseditor_2.0.0.jar.as
c to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-caseditor\2.0.0\uimaj-ep-textmarker-caseditor-2.0.0.jar.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\target\org.apache.uima.textmarker.caseditor_${parsedVers
ion.osgiVersion}.pom.asc to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-caseditor\2.0.0\uimaj-ep-textmarker-casedito
r-2.0.0.pom.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-caseditor\target\org.apache.uima.textmarker.caseditor_2.0.0-source
s.jar.asc to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-caseditor\2.0.0\uimaj-ep-textmarker-caseditor-2.0.0-sources
.jar.asc
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ 
uimaj-ep-textmarker-caseditor ---
[INFO] [INFO] Skipping artifact deployment
[INFO] [INFO]
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Building Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-addons 2.0.0
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO]
[INFO] [INFO] --- build-helper-maven-plugin:1.5:parse-version 
(parse-project-version) @ uimaj-ep-textmarker-addons ---
[INFO] [INFO]
[INFO] [INFO] --- uima-build-helper-maven-plugin:2:parse-date-time (set 
buildYear and buildMonth) @ uimaj-ep-textmarker-addons ---
[INFO] [INFO]
[INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) 
@ uimaj-ep-textmarker-addons ---
[INFO] [INFO]
[INFO] [INFO] --- maven-changes-plugin:2.8:jira-report (default-cli) @ 
uimaj-ep-textmarker-addons ---
[INFO] [WARNING] Deprecated API called - not 
org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. 
Please update this plug
in.
[INFO] [INFO] Downloading from JIRA at: 
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=1
000&reset=true&jqlQuery=project+%3D+UIMA+AND+fixVersion+in+%2812323872%29+AND+status+in+%28Closed%2C+Resolved%29+AND+resolution+in+%28Fixed%
29+AND+component+in+%28TextMarker%29+ORDER+BY+type+ASC%2C+status+ASC%2C+key+ASC
[INFO] [INFO] The JIRA version is '5.2.1'
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:resources 
(default-resources) @ uimaj-ep-textmarker-addons ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 75 resources
[INFO] [INFO] skip non existing resourceDirectory 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\src\main\resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) 
@ uimaj-ep-textmarker-addons ---
[INFO] [INFO] Compiling 129 source files to 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\target\classes
[INFO] [INFO]
[INFO] [INFO] --- maven-bundle-plugin:2.3.4:manifest (uima-bundle) @ 
uimaj-ep-textmarker-addons ---
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:testResources 
(default-testResources) @ uimaj-ep-textmarker-addons ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] skip non existing resourceDirectory 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\src\test\resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile 
(default-testCompile) @ uimaj-ep-textmarker-addons ---
[INFO] [INFO] No sources to compile
[INFO] [INFO]
[INFO] [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ 
uimaj-ep-textmarker-addons ---
[INFO] [INFO] Surefire report directory: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\target\surefire-reports
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] [INFO]
[INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
uimaj-ep-textmarker-addons ---
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\target\org.apache.uima.textmarker.addons_2.0.0.jar
[INFO] [INFO]
[INFO] [INFO] --- maven-assembly-plugin:2.2.1:single 
(source-release-assembly) @ uimaj-ep-textmarker-addons ---
[INFO] [INFO] Skipping the assembly in this project because it's not the 
Execution Root
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar-no-fork 
(attach-sources-nf) @ uimaj-ep-textmarker-addons ---
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\target\org.apache.uima.textmarker.addons_2.0.0-sources.j
ar
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO]
[INFO] [INFO] --- maven-site-plugin:3.0:attach-descriptor 
(attach-descriptor) @ uimaj-ep-textmarker-addons ---
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.3:sign (default) @ 
uimaj-ep-textmarker-addons ---
[INFO] [INFO]
[INFO] [INFO] --- apache-rat-plugin:0.7:check (default-cli) @ 
uimaj-ep-textmarker-addons ---
[INFO] [INFO] Exclude: release.properties
[INFO] [INFO] Exclude: src/test/resources/ManualTests/*
[INFO] [INFO] Exclude: marker-file-identifying-*
[INFO] [INFO] Exclude: issuesFixed/**
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
uimaj-ep-textmarker-addons ---
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\target\org.apache.uima.textmarker.addons_2.0.0.jar 
to C:\Us
ers\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-addons\2.0.0\uimaj-ep-textmarker-addons-2.0.0.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\pom.xml to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\
uimaj-ep-textmarker-addons\2.0.0\uimaj-ep-textmarker-addons-2.0.0.pom
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\target\org.apache.uima.textmarker.addons_2.0.0-sources.jar
to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-addons\2.0.0\uimaj-ep-textmarker-addons-2.0.0-sources.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\target\org.apache.uima.textmarker.addons_2.0.0.jar.asc 
to C
:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-addons\2.0.0\uimaj-ep-textmarker-addons-2.0.0.jar.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\target\org.apache.uima.textmarker.addons_${parsedVersion.os
giVersion}.pom.asc to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-addons\2.0.0\uimaj-ep-textmarker-addons-2.0.0.pom.
asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-addons\target\org.apache.uima.textmarker.addons_2.0.0-sources.jar.
asc to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-addons\2.0.0\uimaj-ep-textmarker-addons-2.0.0-sources.jar.asc
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ 
uimaj-ep-textmarker-addons ---
[INFO] [INFO] Skipping artifact deployment
[INFO] [INFO]
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Building Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-textruler 2.0.0
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO]
[INFO] [INFO] --- build-helper-maven-plugin:1.5:parse-version 
(parse-project-version) @ uimaj-ep-textmarker-textruler ---
[INFO] [INFO]
[INFO] [INFO] --- uima-build-helper-maven-plugin:2:parse-date-time (set 
buildYear and buildMonth) @ uimaj-ep-textmarker-textruler ---
[INFO] [INFO]
[INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) 
@ uimaj-ep-textmarker-textruler ---
[INFO] [INFO]
[INFO] [INFO] --- maven-changes-plugin:2.8:jira-report (default-cli) @ 
uimaj-ep-textmarker-textruler ---
[INFO] [WARNING] Deprecated API called - not 
org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. 
Please update this plug
in.
[INFO] [INFO] Downloading from JIRA at: 
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=1
000&reset=true&jqlQuery=project+%3D+UIMA+AND+fixVersion+in+%2812323872%29+AND+status+in+%28Closed%2C+Resolved%29+AND+resolution+in+%28Fixed%
29+AND+component+in+%28TextMarker%29+ORDER+BY+type+ASC%2C+status+ASC%2C+key+ASC
[INFO] [INFO] The JIRA version is '5.2.1'
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:resources 
(default-resources) @ uimaj-ep-textmarker-textruler ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 16 resources
[INFO] [INFO] Copying 0 resource
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) 
@ uimaj-ep-textmarker-textruler ---
[INFO] [INFO] Compiling 84 source files to 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-textruler\target\classes
[INFO] [INFO]
[INFO] [INFO] --- maven-bundle-plugin:2.3.4:manifest (uima-bundle) @ 
uimaj-ep-textmarker-textruler ---
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:testResources 
(default-testResources) @ uimaj-ep-textmarker-textruler ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 0 resource
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile 
(default-testCompile) @ uimaj-ep-textmarker-textruler ---
[INFO] [INFO] Nothing to compile - all classes are up to date
[INFO] [INFO]
[INFO] [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ 
uimaj-ep-textmarker-textruler ---
[INFO] [INFO] Surefire report directory: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-textruler\target\surefire-reports
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] [INFO]
[INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
uimaj-ep-textmarker-textruler ---
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-textruler\target\org.apache.uima.textmarker.textruler_2.0.0.jar

[INFO] [INFO]
[INFO] [INFO] --- maven-assembly-plugin:2.2.1:single 
(source-release-assembly) @ uimaj-ep-textmarker-textruler ---
[INFO] [INFO] Skipping the assembly in this project because it's not the 
Execution Root
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar-no-fork 
(attach-sources-nf) @ uimaj-ep-textmarker-textruler ---
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-textruler\target\org.apache.uima.textmarker.textruler_2.0.0-sou
rces.jar
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO]
[INFO] [INFO] --- maven-site-plugin:3.0:attach-descriptor 
(attach-descriptor) @ uimaj-ep-textmarker-textruler ---
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.3:sign (default) @ 
uimaj-ep-textmarker-textruler ---
[INFO] [INFO]
[INFO] [INFO] --- apache-rat-plugin:0.7:check (default-cli) @ 
uimaj-ep-textmarker-textruler ---
[INFO] [INFO] Exclude: release.properties
[INFO] [INFO] Exclude: marker-file-identifying-*
[INFO] [INFO] Exclude: issuesFixed/**
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
uimaj-ep-textmarker-textruler ---
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-textruler\target\org.apache.uima.textmarker.textruler_2.0.0.jar 
to
  C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-textruler\2.0.0\uimaj-ep-textmarker-textruler-2.0.0.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-textruler\pom.xml to 
C:\Users\pkluegl\.m2\repository\org\apache\ui
ma\uimaj-ep-textmarker-textruler\2.0.0\uimaj-ep-textmarker-textruler-2.0.0.pom
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-textruler\target\org.apache.uima.textmarker.textruler_2.0.0-source
s.jar to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-textruler\2.0.0\uimaj-ep-textmarker-textruler-2.0.0-sources.jar

[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-textruler\target\org.apache.uima.textmarker.textruler_2.0.0.jar.as
c to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-textruler\2.0.0\uimaj-ep-textmarker-textruler-2.0.0.jar.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-textruler\target\org.apache.uima.textmarker.textruler_${parsedVers
ion.osgiVersion}.pom.asc to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-textruler\2.0.0\uimaj-ep-textmarker-textrule
r-2.0.0.pom.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-ep-textmarker-textruler\target\org.apache.uima.textmarker.textruler_2.0.0-source
s.jar.asc to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-ep-textmarker-textruler\2.0.0\uimaj-ep-textmarker-textruler-2.0.0-sources
.jar.asc
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ 
uimaj-ep-textmarker-textruler ---
[INFO] [INFO] Skipping artifact deployment
[INFO] [INFO]
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Building Apache UIMA TextMarker Documentation 2.0.0
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO]
[INFO] [INFO] --- build-helper-maven-plugin:1.5:parse-version 
(parse-project-version) @ uima-docbook-textmarker ---
[INFO] [INFO]
[INFO] [INFO] --- uima-build-helper-maven-plugin:2:parse-date-time (set 
buildYear and buildMonth) @ uima-docbook-textmarker ---
[INFO] [INFO]
[INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) 
@ uima-docbook-textmarker ---
[INFO] [INFO]
[INFO] [INFO] --- maven-changes-plugin:2.8:jira-report (default-cli) @ 
uima-docbook-textmarker ---
[INFO] [WARNING] Deprecated API called - not 
org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. 
Please update this plug
in.
[INFO] [INFO] Downloading from JIRA at: 
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=1
000&reset=true&jqlQuery=project+%3D+UIMA+AND+fixVersion+in+%2812323872%29+AND+status+in+%28Closed%2C+Resolved%29+AND+resolution+in+%28Fixed%
29+AND+component+in+%28TextMarker%29+ORDER+BY+type+ASC%2C+status+ASC%2C+key+ASC
[INFO] [INFO] The JIRA version is '5.2.1'
[INFO] [INFO]
[INFO] [INFO] --- maven-dependency-plugin:2.3:unpack (copyDocbookInfo) @ 
uima-docbook-textmarker ---
[INFO] [INFO] Configured Artifact: 
org.apache.uima:uima-build-resources:3:jar
[INFO] [INFO] Unpacking 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uima-build-resources\3\uima-build-resources-3.jar 
to D:\work\tmb8\ta
rget\checkout\uima-docbook-textmarker\target with includes 
"docbook-shared/**" and excludes ""
[INFO] [INFO]
[INFO] [INFO] --- maven-dependency-plugin:2.3:unpack 
(copyDocbookInfoNextToOlink) @ uima-docbook-textmarker ---
[INFO] [INFO] Configured Artifact: 
org.apache.uima:uima-build-resources:1:jar
[INFO] > isMarkerOlder:
[INFO]   artifact1 = 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uima-build-resources\1\uima-build-resources-1.jar
[INFO]   marker    = 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uima-docbook-olink\1-SNAPSHOT\dependency-maven-plugin-markers\org.apach
e.uima-uima-build-resources-jar-1376161406
[INFO]     artifact1 lastModified: 1352305443684
[INFO]     marker lastModified: 1352305443684
[INFO] < false = marker older than artifact?
[INFO] [INFO] uima-build-resources-1.jar already unpacked.
[INFO] [INFO]
[INFO] [INFO] --- maven-dependency-plugin:2.3:unpack (getOlink) @ 
uima-docbook-textmarker ---
[INFO] [INFO] Configured Artifact: 
org.apache.uima:uima-docbook-olink:olink:1-SNAPSHOT:zip
[INFO] > isMarkerOlder:
[INFO]   artifact1 = 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uima-docbook-olink\1-SNAPSHOT\uima-docbook-olink-1-SNAPSHOT-olink.zip
[INFO]   marker    = 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uima-docbook-olink\1-SNAPSHOT\dependency-maven-plugin-markers\org.apach
e.uima-uima-docbook-olink-zip-olink-1-SNAPSHOT.marker
[INFO]     artifact1 lastModified: 1352305447018
[INFO]     marker lastModified: 1352305447018
[INFO] < false = marker older than artifact?
[INFO] [INFO] uima-docbook-olink-1-SNAPSHOT-olink.zip already unpacked.
[INFO] [INFO]
[INFO] [INFO] --- maven-assembly-plugin:2.2.1:single 
(source-release-assembly) @ uima-docbook-textmarker ---
[INFO] [INFO] Skipping the assembly in this project because it's not the 
Execution Root
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar-no-fork 
(attach-sources-nf) @ uima-docbook-textmarker ---
[INFO] [INFO]
[INFO] [INFO] --- maven-site-plugin:3.0:attach-descriptor 
(attach-descriptor) @ uima-docbook-textmarker ---
[INFO] [INFO]
[INFO] [INFO] --- docbkx-maven-plugin:2.0.13:generate-html (html) @ 
uima-docbook-textmarker ---
[INFO] [INFO] Processing input file: tools.textmarker.book.xml
[INFO] [INFO] 
D:\work\tmb8\target\checkout\uima-docbook-textmarker\target\site\d\tools.textmarker.book.html 
has been generated.
[INFO] [INFO]
[INFO] [INFO] --- docbkx-maven-plugin:2.0.13:generate-pdf (pdf) @ 
uima-docbook-textmarker ---
[INFO] [INFO] Processing input file: tools.textmarker.book.xml
[INFO] [INFO] targetFileExtension pdf
[INFO] [INFO] type fo
[INFO] 22.01.2013 14:42:08 org.apache.fop.events.LoggingEventListener 
processEvent
[INFO] WARNUNG: Font "Symbol,normal,700" not found. Substituting with 
"Symbol,normal,400".
[INFO] 22.01.2013 14:42:08 org.apache.fop.events.LoggingEventListener 
processEvent
[INFO] WARNUNG: Font "ZapfDingbats,normal,700" not found. Substituting 
with "ZapfDingbats,normal,400".
[INFO] 22.01.2013 14:42:09 org.apache.fop.events.LoggingEventListener 
processEvent
[INFO] WARNUNG: Line 1 of a paragraph overflows the available area by 
1106 millipoints. (See position 667:1033)
[INFO] [INFO] 
D:\work\tmb8\target\checkout\uima-docbook-textmarker\target\docbkx\pdf\tools.textmarker.book.pdf 
has been generated.
[INFO] [INFO] 
D:\work\tmb8\target\checkout\uima-docbook-textmarker\target\docbkx\pdf\tools.textmarker.book.fo 
has been generated.
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:copy-resources 
(docbook-copy-images) @ uima-docbook-textmarker ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 45 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:copy-resources 
(docbook-copy-css) @ uima-docbook-textmarker ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 1 resource
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:copy-resources 
(docbook-move-pdf) @ uima-docbook-textmarker ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 1 resource
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.3:sign (default) @ 
uima-docbook-textmarker ---
[INFO] [INFO]
[INFO] [INFO] --- apache-rat-plugin:0.7:check (default-cli) @ 
uima-docbook-textmarker ---
[INFO] [INFO] Exclude: target/**
[INFO] [INFO] Exclude: example-projects/**
[INFO] [INFO] Exclude: README*
[INFO] [INFO] Exclude: RELEASE_NOTES*
[INFO] [INFO] Exclude: issuesFixed/**
[INFO] [INFO] Exclude: src/main/resources/docbook-shared/titlepage/*.xsl
[INFO] [INFO] Exclude: marker-file-identifying-*
[INFO] [INFO] Exclude: DEPENDENCIES
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
uima-docbook-textmarker ---
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uima-docbook-textmarker\pom.xml to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uim
a-docbook-textmarker\2.0.0\uima-docbook-textmarker-2.0.0.pom
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uima-docbook-textmarker\target\uima-docbook-textmarker-2.0.0.pom.asc 
to C:\Users\pklue
gl\.m2\repository\org\apache\uima\uima-docbook-textmarker\2.0.0\uima-docbook-textmarker-2.0.0.pom.asc
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ 
uima-docbook-textmarker ---
[INFO] [INFO] Skipping artifact deployment
[INFO] [INFO]
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Building Apache UIMA TextMarker Eclipse: 
uimaj-textmarker-eclipse-feature 2.0.0
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO]
[INFO] [INFO] --- build-helper-maven-plugin:1.5:parse-version 
(parse-project-version) @ uimaj-textmarker-eclipse-feature ---
[INFO] [INFO]
[INFO] [INFO] --- uima-build-helper-maven-plugin:2:parse-date-time (set 
buildYear and buildMonth) @ uimaj-textmarker-eclipse-feature ---
[INFO] [INFO]
[INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) 
@ uimaj-textmarker-eclipse-feature ---
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:copy-resources (filter 
feature.xml) @ uimaj-textmarker-eclipse-feature ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 1 resource
[INFO] [INFO]
[INFO] [INFO] --- maven-changes-plugin:2.8:jira-report (default-cli) @ 
uimaj-textmarker-eclipse-feature ---
[INFO] [WARNING] Deprecated API called - not 
org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. 
Please update this plug
in.
[INFO] [INFO] Downloading from JIRA at: 
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=1
000&reset=true&jqlQuery=project+%3D+UIMA+AND+fixVersion+in+%2812323872%29+AND+status+in+%28Closed%2C+Resolved%29+AND+resolution+in+%28Fixed%
29+AND+component+in+%28TextMarker%29+ORDER+BY+type+ASC%2C+status+ASC%2C+key+ASC
[INFO] [INFO] The JIRA version is '5.2.1'
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:resources 
(default-resources) @ uimaj-textmarker-eclipse-feature ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 2 resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) 
@ uimaj-textmarker-eclipse-feature ---
[INFO] [INFO] No sources to compile
[INFO] [INFO]
[INFO] [INFO] --- maven-resources-plugin:2.5:testResources 
(default-testResources) @ uimaj-textmarker-eclipse-feature ---
[INFO] [debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] skip non existing resourceDirectory 
D:\work\tmb8\target\checkout\uimaj-textmarker-eclipse-feature\src\test\resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO]
[INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile 
(default-testCompile) @ uimaj-textmarker-eclipse-feature ---
[INFO] [INFO] No sources to compile
[INFO] [INFO]
[INFO] [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ 
uimaj-textmarker-eclipse-feature ---
[INFO] [INFO] Surefire report directory: 
D:\work\tmb8\target\checkout\uimaj-textmarker-eclipse-feature\target\surefire-reports
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] [INFO]
[INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
uimaj-textmarker-eclipse-feature ---
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-textmarker-eclipse-feature\target\uimaj-textmarker-eclipse-feature_2.0.0.jar
[INFO] [INFO]
[INFO] [INFO] --- maven-assembly-plugin:2.2.1:single 
(source-release-assembly) @ uimaj-textmarker-eclipse-feature ---
[INFO] [INFO] Skipping the assembly in this project because it's not the 
Execution Root
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar-no-fork 
(attach-sources-nf) @ uimaj-textmarker-eclipse-feature ---
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO] Building jar: 
D:\work\tmb8\target\checkout\uimaj-textmarker-eclipse-feature\target\uimaj-textmarker-eclipse-feature_2.0.0-sour
ces.jar
[INFO] [INFO] META-INF already added, skipping
[INFO] [INFO] META-INF\DEPENDENCIES already added, skipping
[INFO] [INFO] META-INF\LICENSE already added, skipping
[INFO] [INFO] META-INF\NOTICE already added, skipping
[INFO] [INFO]
[INFO] [INFO] --- maven-site-plugin:3.0:attach-descriptor 
(attach-descriptor) @ uimaj-textmarker-eclipse-feature ---
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.3:sign (default) @ 
uimaj-textmarker-eclipse-feature ---
[INFO] [INFO]
[INFO] [INFO] --- apache-rat-plugin:0.7:check (default-cli) @ 
uimaj-textmarker-eclipse-feature ---
[INFO] [INFO] Exclude: target/**
[INFO] [INFO] Exclude: example-projects/**
[INFO] [INFO] Exclude: README*
[INFO] [INFO] Exclude: RELEASE_NOTES*
[INFO] [INFO] Exclude: issuesFixed/**
[INFO] [INFO] Exclude: src/main/resources/docbook-shared/titlepage/*.xsl
[INFO] [INFO] Exclude: marker-file-identifying-*
[INFO] [INFO] Exclude: DEPENDENCIES
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
uimaj-textmarker-eclipse-feature ---
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker-eclipse-feature\target\uimaj-textmarker-eclipse-feature_2.0.0.jar 
to
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-textmarker-eclipse-feature\2.0.0\uimaj-textmarker-eclipse-feature-2.0.0.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker-eclipse-feature\pom.xml to 
C:\Users\pkluegl\.m2\repository\org\apache
\uima\uimaj-textmarker-eclipse-feature\2.0.0\uimaj-textmarker-eclipse-feature-2.0.0.pom
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker-eclipse-feature\target\uimaj-textmarker-eclipse-feature_2.0.0-sources
.jar to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-textmarker-eclipse-feature\2.0.0\uimaj-textmarker-eclipse-feature-2.0.0-source
s.jar
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker-eclipse-feature\target\uimaj-textmarker-eclipse-feature_2.0.0.jar.asc
  to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-textmarker-eclipse-feature\2.0.0\uimaj-textmarker-eclipse-feature-2.0.0.jar.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker-eclipse-feature\target\uimaj-textmarker-eclipse-feature_${parsedVersi
on.osgiVersion}.pom.asc to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-textmarker-eclipse-feature\2.0.0\uimaj-textmarker-eclipse-f
eature-2.0.0.pom.asc
[INFO] [INFO] Installing 
D:\work\tmb8\target\checkout\uimaj-textmarker-eclipse-feature\target\uimaj-textmarker-eclipse-feature_2.0.0-sources
.jar.asc to 
C:\Users\pkluegl\.m2\repository\org\apache\uima\uimaj-textmarker-eclipse-feature\2.0.0\uimaj-textmarker-eclipse-feature-2.0.0-so
urces.jar.asc
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ 
uimaj-textmarker-eclipse-feature ---
[INFO] [INFO] Skipping artifact deployment
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Reactor Summary:
[INFO] [INFO]
[INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... 
SUCCESS [16.720s]
[INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... 
SUCCESS [27.537s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-engine  SUCCESS [20.417s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide  
SUCCESS [23.239s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-caseditor  SUCCESS [9.074s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-addons  SUCCESS [12.279s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-textruler  SUCCESS [12.165s]
[INFO] [INFO] Apache UIMA TextMarker Documentation .............. 
SUCCESS [25.173s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: 
uimaj-textmarker-eclipse-feature  SUCCESS [7.102s]
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] BUILD SUCCESS
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Total time: 2:34.713s
[INFO] [INFO] Finished at: Tue Jan 22 14:42:20 CET 2013
[INFO] [INFO] Final Memory: 147M/463M
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] Cleaning up after release...
[INFO] 
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... SUCCESS 
[2:59.594s]
[INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  
SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  
SKIPPED
[INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  
SKIPPED
[INFO] 
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] 
------------------------------------------------------------------------
[INFO] Total time: 3:01.184s
[INFO] Finished at: Tue Jan 22 14:42:21 CET 2013
[INFO] Final Memory: 14M/151M
[INFO] 
------------------------------------------------------------------------
D:\work\tmb8>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Yes, I did all on the console now.
First, "svn checkout 
https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk 
D:\work\workspace-textmarker-build6"
Then, in folder "workspace-textmarker-build6", I called mvn.

So the commands are executed on the reactor project 
(uimaj-textmarker-parent), which is located in trunk.

I redo everything now with a bigger console buffer.

Peter


On 22.01.2013 14:10, Richard Eckart de Castilho wrote:
> Odd. In which folder do you run the release? In uimaj-textmarker or in the actual "trunk" folder (whatever the name of that is in your local checkout)? I suppose should be run on the "trunk" folder.
>
> -- Richard
>
> Am 22.01.2013 um 13:57 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>
>> On 22.01.2013 13:47, Richard Eckart de Castilho wrote:
>>> Hi,
>>>
>>> in my experience with Nexus (not the Apache instance in particular), it should show up immediately. Did you see in the Maven output that the files were properly uploaded?
>> Unfortunately not for the parent. The other modules say "Skipping the assembly in this project because it's not the Execution Root" and "Skipping artifact deployment".
>>
>> Peter
>>
>>
>>> -- Richard
>>>
>>> Am 22.01.2013 um 13:42 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>>>
>>>> Hi,
>>>>
>>>> next question:
>>>>
>>>> "mvn release:perform" finished with BUILD SUCCESS, but I cannot see a staging repository at [1]. There is only org.apache.uima-111 (u:cwiklik, a:129.34.20.23). Did I miss something or does it take a while until it appears there?
>>>>
>>>> Peter
>>>>
>>>> [1] https://repository.apache.org/index.html#stagingRepositories
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Odd. In which folder do you run the release? In uimaj-textmarker or in the actual "trunk" folder (whatever the name of that is in your local checkout)? I suppose should be run on the "trunk" folder.

-- Richard

Am 22.01.2013 um 13:57 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:

> On 22.01.2013 13:47, Richard Eckart de Castilho wrote:
>> Hi,
>> 
>> in my experience with Nexus (not the Apache instance in particular), it should show up immediately. Did you see in the Maven output that the files were properly uploaded?
> 
> Unfortunately not for the parent. The other modules say "Skipping the assembly in this project because it's not the Execution Root" and "Skipping artifact deployment".
> 
> Peter
> 
> 
>> -- Richard
>> 
>> Am 22.01.2013 um 13:42 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>> 
>>> Hi,
>>> 
>>> next question:
>>> 
>>> "mvn release:perform" finished with BUILD SUCCESS, but I cannot see a staging repository at [1]. There is only org.apache.uima-111 (u:cwiklik, a:129.34.20.23). Did I miss something or does it take a while until it appears there?
>>> 
>>> Peter
>>> 
>>> [1] https://repository.apache.org/index.html#stagingRepositories


-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
On 22.01.2013 13:47, Richard Eckart de Castilho wrote:
> Hi,
>
> in my experience with Nexus (not the Apache instance in particular), it should show up immediately. Did you see in the Maven output that the files were properly uploaded?

Unfortunately not for the parent. The other modules say "Skipping the 
assembly in this project because it's not the Execution Root" and 
"Skipping artifact deployment".

Peter


> -- Richard
>
> Am 22.01.2013 um 13:42 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>
>> Hi,
>>
>> next question:
>>
>> "mvn release:perform" finished with BUILD SUCCESS, but I cannot see a staging repository at [1]. There is only org.apache.uima-111 (u:cwiklik, a:129.34.20.23). Did I miss something or does it take a while until it appears there?
>>
>> Peter
>>
>> [1] https://repository.apache.org/index.html#stagingRepositories
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Hi,

in my experience with Nexus (not the Apache instance in particular), it should show up immediately. Did you see in the Maven output that the files were properly uploaded?

-- Richard

Am 22.01.2013 um 13:42 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:

> Hi,
> 
> next question:
> 
> "mvn release:perform" finished with BUILD SUCCESS, but I cannot see a staging repository at [1]. There is only org.apache.uima-111 (u:cwiklik, a:129.34.20.23). Did I miss something or does it take a while until it appears there?
> 
> Peter
> 
> [1] https://repository.apache.org/index.html#stagingRepositories


-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Hi,

next question:

"mvn release:perform" finished with BUILD SUCCESS, but I cannot see a 
staging repository at [1]. There is only org.apache.uima-111 (u:cwiklik, 
a:129.34.20.23). Did I miss something or does it take a while until it 
appears there?

Peter

[1] https://repository.apache.org/index.html#stagingRepositories


On 22.01.2013 13:22, Peter Klügl wrote:
> Looks like the problem is caused by a lagging subversion [1]
>
> Peter
>
> [1] 
> http://maven.40175.n5.nabble.com/apache-subversion-lagging-Was-Releasing-Maven-Archetype-Plugin-td216312.html
>
>
> On 22.01.2013 11:18, Peter Klügl wrote:
>> I am using apache-maven-3.0.4
>>
>> SCM location looks fine. I checked it again for the parent project.
>>
>> Peter
>>
>>
>>
>> On 21.01.2013 21:14, Richard Eckart de Castilho wrote:
>>> Good luck. When you find out what's the problem, drop us a note.
>>>
>>> I never run releases in Eclipse and teach anybody to do them on the 
>>> command line. I suppose it cannot hurt if you try. Make sure you the 
>>> latest Maven release.
>>>
>>> Another thing: are you sure the SCM location is correct in the POM?
>>>
>>> Cheers,
>>>
>>> -- Richard
>>>
>>> Am 21.01.2013 um 21:07 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>>>
>>>> Hi Richard,
>>>>
>>>> Am 21.01.2013 20:48, schrieb Richard Eckart de Castilho:
>>>>> Hi Peter,
>>>>>
>>>>> to avoid username/pw on the command line, I had to use a 
>>>>> differnent svn binary. Normally it should be enough to log in on 
>>>>> the command line once (e.g. by issuing a "svn log" command) and 
>>>>> let svn cache the credentials.
>>>>>
>>>>> But anyway, your error doesn't look like missing credentials (it 
>>>>> should say something along the lines "access denied") it rather 
>>>>> looks like a SVN server glitch - something I get on Google Code 
>>>>> every one in a while. Did you try just calling "mvn 
>>>>> release:prepare" again? Maven remembers where the release process 
>>>>> got stuck and will pick up again there. If you need to abort the 
>>>>> release, use "mvn release:rollback".
>>>> The first try was "mvn -DautoVersionSubmodules release:prepare 
>>>> release:perform" and failed. Then, I executed "mvn 
>>>> release:rollback" and tried only "mvn -DautoVersionSubmodules 
>>>> release:prepare". This also failed, followed by another rollback.
>>>>
>>>> I gonna do some internet search about the error message tomorrow . 
>>>> Maybe I find some explanation what might be causing this.
>>>>
>>>> Btw, I am doing this in Eclipse with "Maven/run as..." and with an 
>>>> external maven install. Shouldn't be a problem, I think.
>>>>
>>>> Peter
>>>>
>>>>> Cheers,
>>>>>
>>>>> -- Richard
>>>>>
>>>>> Am 21.01.2013 um 19:38 schrieb Peter Klügl 
>>>>> <pk...@uni-wuerzburg.de>:
>>>>>
>>>>>> On 17.01.2013 19:08, Richard Eckart de Castilho wrote:
>>>>>>> Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:
>>>>>>>
>>>>>>>>> If your release fails at some SVN operation like creating the 
>>>>>>>>> tag, try providing "-Dusername=XXX -Dpassword=YYY" on the 
>>>>>>>>> command line with your SVN credentials.
>>>>>>>> I've never had to do this.  I would be careful, in case these 
>>>>>>>> are sent in the
>>>>>>>> "clear" (I don't know about this).
>>>>>>> If you local SVN setup is well configured, this should not be 
>>>>>>> required. I've had some issues in the past on OS X with SVN not 
>>>>>>> picking up cached passwords during a Maven release. I didn't 
>>>>>>> read the code, but I expect the credentials are passed on when 
>>>>>>> Maven calls the external SVN process and are sent via whatever 
>>>>>>> protocol you use to communicate with the SVN server. But they do 
>>>>>>> end up in the shell history of course - clearing the command 
>>>>>>> from there after the process is certainly wise.
>>>>>>>
>>>>>>> -- Richard
>>>>>>>
>>>>>> Hmm... that probably happened to me now but the error doesn't 
>>>>>> look like missing SVN credentials.
>>>>>>
>>>>>> The SVN setup looks fine. Any idea how to avoid "-Dusername=XXX 
>>>>>> -Dpassword=YYY"?
>>>>>>
>>>>>> Btw, I wasn't asked yet for the tag (RC1), but I think that will 
>>>>>> happen later, right?
>>>>>>
>>>>>> Here's the console:
>>>>>>
>>>>>> ...
>>>>>> [INFO] [INFO] Reactor Summary:
>>>>>> [INFO] [INFO]
>>>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... 
>>>>>> SUCCESS [33.945s]
>>>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... 
>>>>>> SUCCESS [25.917s]
>>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>>> uimaj-ep-textmarker-engine  SUCCESS [24.788s]
>>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>>> uimaj-ep-textmarker-ide  SUCCESS [23.878s]
>>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>>> uimaj-ep-textmarker-caseditor  SUCCESS [9.476s]
>>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>>> uimaj-ep-textmarker-addons  SUCCESS [14.046s]
>>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>>> uimaj-ep-textmarker-textruler  SUCCESS [12.535s]
>>>>>> [INFO] [INFO] Apache UIMA TextMarker Documentation .............. 
>>>>>> SUCCESS [26.484s]
>>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>>> uimaj-textmarker-eclipse-feature  SUCCESS [7.376s]
>>>>>> [INFO] [INFO] 
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>> [INFO] [INFO] BUILD SUCCESS
>>>>>> [INFO] [INFO] 
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>> [INFO] [INFO] Total time: 2:59.468s
>>>>>> [INFO] [INFO] Finished at: Mon Jan 21 19:24:28 CET 2013
>>>>>> [INFO] [INFO] Final Memory: 146M/461M
>>>>>> [INFO] [INFO] 
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>> [INFO] Checking in modified POMs...
>>>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit 
>>>>>> --file 
>>>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-1977004734.commit 
>>>>>> --targets 
>>>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-2678525437479394015-targets"
>>>>>> [INFO] Working directory: 
>>>>>> D:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>>>> [INFO] Tagging release with the label 
>>>>>> uimaj-textmarker-parent-2.0.0...
>>>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy 
>>>>>> --file 
>>>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-343353279.commit 
>>>>>> --revision 1436535 
>>>>>> https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk 
>>>>>> https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmarker-parent-2.0.0" 
>>>>>>
>>>>>> [INFO] Working directory: 
>>>>>> d:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>>>> [INFO] 
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>> [INFO] Reactor Summary:
>>>>>> [INFO]
>>>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... 
>>>>>> FAILURE [3:16.435s]
>>>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
>>>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine 
>>>>>> SKIPPED
>>>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide 
>>>>>> SKIPPED
>>>>>> [INFO] Apache UIMA TextMarker Eclipse: 
>>>>>> uimaj-ep-textmarker-caseditor  SKIPPED
>>>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons 
>>>>>> SKIPPED
>>>>>> [INFO] Apache UIMA TextMarker Eclipse: 
>>>>>> uimaj-ep-textmarker-textruler  SKIPPED
>>>>>> [INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
>>>>>> [INFO] Apache UIMA TextMarker Eclipse: 
>>>>>> uimaj-textmarker-eclipse-feature  SKIPPED
>>>>>> [INFO] 
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>> [INFO] BUILD FAILURE
>>>>>> [INFO] 
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>> [INFO] Total time: 3:18.044s
>>>>>> [INFO] Finished at: Mon Jan 21 19:24:41 CET 2013
>>>>>> [INFO] Final Memory: 17M/221M
>>>>>> [INFO] 
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>> [ERROR] Failed to execute goal 
>>>>>> org.apache.maven.plugins:maven-release-plugin:2.1:prepare 
>>>>>> (default-cli) on project uimaj-textmarker-parent: Unable to tag SCM
>>>>>> [ERROR] Provider message:
>>>>>> [ERROR] The svn tag command failed.
>>>>>> [ERROR] Command output:
>>>>>> [ERROR] svn: E160006: No such revision 1436535
>>>>>> [ERROR] -> [Help 1]
>>>>>> [ERROR]
>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven 
>>>>>> with the -e switch.
>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug 
>>>>>> logging.
>>>>>> [ERROR]
>>>>>> [ERROR] For more information about the errors and possible 
>>>>>> solutions, please read the following articles:
>>>>>> [ERROR] [Help 1] 
>>>>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException 
>>>>>>
>>>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Looks like the problem is caused by a lagging subversion [1]

Peter

[1] 
http://maven.40175.n5.nabble.com/apache-subversion-lagging-Was-Releasing-Maven-Archetype-Plugin-td216312.html


On 22.01.2013 11:18, Peter Klügl wrote:
> I am using apache-maven-3.0.4
>
> SCM location looks fine. I checked it again for the parent project.
>
> Peter
>
>
>
> On 21.01.2013 21:14, Richard Eckart de Castilho wrote:
>> Good luck. When you find out what's the problem, drop us a note.
>>
>> I never run releases in Eclipse and teach anybody to do them on the 
>> command line. I suppose it cannot hurt if you try. Make sure you the 
>> latest Maven release.
>>
>> Another thing: are you sure the SCM location is correct in the POM?
>>
>> Cheers,
>>
>> -- Richard
>>
>> Am 21.01.2013 um 21:07 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>>
>>> Hi Richard,
>>>
>>> Am 21.01.2013 20:48, schrieb Richard Eckart de Castilho:
>>>> Hi Peter,
>>>>
>>>> to avoid username/pw on the command line, I had to use a differnent 
>>>> svn binary. Normally it should be enough to log in on the command 
>>>> line once (e.g. by issuing a "svn log" command) and let svn cache 
>>>> the credentials.
>>>>
>>>> But anyway, your error doesn't look like missing credentials (it 
>>>> should say something along the lines "access denied") it rather 
>>>> looks like a SVN server glitch - something I get on Google Code 
>>>> every one in a while. Did you try just calling "mvn 
>>>> release:prepare" again? Maven remembers where the release process 
>>>> got stuck and will pick up again there. If you need to abort the 
>>>> release, use "mvn release:rollback".
>>> The first try was "mvn -DautoVersionSubmodules release:prepare 
>>> release:perform" and failed. Then, I executed "mvn release:rollback" 
>>> and tried only "mvn -DautoVersionSubmodules release:prepare". This 
>>> also failed, followed by another rollback.
>>>
>>> I gonna do some internet search about the error message tomorrow . 
>>> Maybe I find some explanation what might be causing this.
>>>
>>> Btw, I am doing this in Eclipse with "Maven/run as..." and with an 
>>> external maven install. Shouldn't be a problem, I think.
>>>
>>> Peter
>>>
>>>> Cheers,
>>>>
>>>> -- Richard
>>>>
>>>> Am 21.01.2013 um 19:38 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>>>>
>>>>> On 17.01.2013 19:08, Richard Eckart de Castilho wrote:
>>>>>> Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:
>>>>>>
>>>>>>>> If your release fails at some SVN operation like creating the 
>>>>>>>> tag, try providing "-Dusername=XXX -Dpassword=YYY" on the 
>>>>>>>> command line with your SVN credentials.
>>>>>>> I've never had to do this.  I would be careful, in case these 
>>>>>>> are sent in the
>>>>>>> "clear" (I don't know about this).
>>>>>> If you local SVN setup is well configured, this should not be 
>>>>>> required. I've had some issues in the past on OS X with SVN not 
>>>>>> picking up cached passwords during a Maven release. I didn't read 
>>>>>> the code, but I expect the credentials are passed on when Maven 
>>>>>> calls the external SVN process and are sent via whatever protocol 
>>>>>> you use to communicate with the SVN server. But they do end up in 
>>>>>> the shell history of course - clearing the command from there 
>>>>>> after the process is certainly wise.
>>>>>>
>>>>>> -- Richard
>>>>>>
>>>>> Hmm... that probably happened to me now but the error doesn't look 
>>>>> like missing SVN credentials.
>>>>>
>>>>> The SVN setup looks fine. Any idea how to avoid "-Dusername=XXX 
>>>>> -Dpassword=YYY"?
>>>>>
>>>>> Btw, I wasn't asked yet for the tag (RC1), but I think that will 
>>>>> happen later, right?
>>>>>
>>>>> Here's the console:
>>>>>
>>>>> ...
>>>>> [INFO] [INFO] Reactor Summary:
>>>>> [INFO] [INFO]
>>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... 
>>>>> SUCCESS [33.945s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... 
>>>>> SUCCESS [25.917s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-engine  SUCCESS [24.788s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-ide  SUCCESS [23.878s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-caseditor  SUCCESS [9.476s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-addons  SUCCESS [14.046s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-textruler  SUCCESS [12.535s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Documentation .............. 
>>>>> SUCCESS [26.484s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-textmarker-eclipse-feature  SUCCESS [7.376s]
>>>>> [INFO] [INFO] 
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] [INFO] BUILD SUCCESS
>>>>> [INFO] [INFO] 
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] [INFO] Total time: 2:59.468s
>>>>> [INFO] [INFO] Finished at: Mon Jan 21 19:24:28 CET 2013
>>>>> [INFO] [INFO] Final Memory: 146M/461M
>>>>> [INFO] [INFO] 
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] Checking in modified POMs...
>>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit 
>>>>> --file 
>>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-1977004734.commit 
>>>>> --targets 
>>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-2678525437479394015-targets"
>>>>> [INFO] Working directory: 
>>>>> D:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>>> [INFO] Tagging release with the label 
>>>>> uimaj-textmarker-parent-2.0.0...
>>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file 
>>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-343353279.commit 
>>>>> --revision 1436535 
>>>>> https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk 
>>>>> https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmarker-parent-2.0.0" 
>>>>>
>>>>> [INFO] Working directory: 
>>>>> d:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>>> [INFO] 
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] Reactor Summary:
>>>>> [INFO]
>>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... FAILURE 
>>>>> [3:16.435s]
>>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine 
>>>>> SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide 
>>>>> SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-caseditor  SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons 
>>>>> SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-textruler  SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-textmarker-eclipse-feature  SKIPPED
>>>>> [INFO] 
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] BUILD FAILURE
>>>>> [INFO] 
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] Total time: 3:18.044s
>>>>> [INFO] Finished at: Mon Jan 21 19:24:41 CET 2013
>>>>> [INFO] Final Memory: 17M/221M
>>>>> [INFO] 
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [ERROR] Failed to execute goal 
>>>>> org.apache.maven.plugins:maven-release-plugin:2.1:prepare 
>>>>> (default-cli) on project uimaj-textmarker-parent: Unable to tag SCM
>>>>> [ERROR] Provider message:
>>>>> [ERROR] The svn tag command failed.
>>>>> [ERROR] Command output:
>>>>> [ERROR] svn: E160006: No such revision 1436535
>>>>> [ERROR] -> [Help 1]
>>>>> [ERROR]
>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven 
>>>>> with the -e switch.
>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug 
>>>>> logging.
>>>>> [ERROR]
>>>>> [ERROR] For more information about the errors and possible 
>>>>> solutions, please read the following articles:
>>>>> [ERROR] [Help 1] 
>>>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
I am using apache-maven-3.0.4

SCM location looks fine. I checked it again for the parent project.

Peter



On 21.01.2013 21:14, Richard Eckart de Castilho wrote:
> Good luck. When you find out what's the problem, drop us a note.
>
> I never run releases in Eclipse and teach anybody to do them on the command line. I suppose it cannot hurt if you try. Make sure you the latest Maven release.
>
> Another thing: are you sure the SCM location is correct in the POM?
>
> Cheers,
>
> -- Richard
>
> Am 21.01.2013 um 21:07 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>
>> Hi Richard,
>>
>> Am 21.01.2013 20:48, schrieb Richard Eckart de Castilho:
>>> Hi Peter,
>>>
>>> to avoid username/pw on the command line, I had to use a differnent svn binary. Normally it should be enough to log in on the command line once (e.g. by issuing a "svn log" command) and let svn cache the credentials.
>>>
>>> But anyway, your error doesn't look like missing credentials (it should say something along the lines "access denied") it rather looks like a SVN server glitch - something I get on Google Code every one in a while. Did you try just calling "mvn release:prepare" again? Maven remembers where the release process got stuck and will pick up again there. If you need to abort the release, use "mvn release:rollback".
>> The first try was "mvn -DautoVersionSubmodules release:prepare release:perform" and failed. Then, I executed "mvn release:rollback" and tried only "mvn -DautoVersionSubmodules release:prepare". This also failed, followed by another rollback.
>>
>> I gonna do some internet search about the error message tomorrow . Maybe I find some explanation what might be causing this.
>>
>> Btw, I am doing this in Eclipse with "Maven/run as..." and with an external maven install. Shouldn't be a problem, I think.
>>
>> Peter
>>
>>> Cheers,
>>>
>>> -- Richard
>>>
>>> Am 21.01.2013 um 19:38 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>>>
>>>> On 17.01.2013 19:08, Richard Eckart de Castilho wrote:
>>>>> Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:
>>>>>
>>>>>>> If your release fails at some SVN operation like creating the tag, try providing "-Dusername=XXX -Dpassword=YYY" on the command line with your SVN credentials.
>>>>>> I've never had to do this.  I would be careful, in case these are sent in the
>>>>>> "clear" (I don't know about this).
>>>>> If you local SVN setup is well configured, this should not be required. I've had some issues in the past on OS X with SVN not picking up cached passwords during a Maven release. I didn't read the code, but I expect the credentials are passed on when Maven calls the external SVN process and are sent via whatever protocol you use to communicate with the SVN server. But they do end up in the shell history of course - clearing the command from there after the process is certainly wise.
>>>>>
>>>>> -- Richard
>>>>>
>>>> Hmm... that probably happened to me now but the error doesn't look like missing SVN credentials.
>>>>
>>>> The SVN setup looks fine. Any idea how to avoid "-Dusername=XXX -Dpassword=YYY"?
>>>>
>>>> Btw, I wasn't asked yet for the tag (RC1), but I think that will happen later, right?
>>>>
>>>> Here's the console:
>>>>
>>>> ...
>>>> [INFO] [INFO] Reactor Summary:
>>>> [INFO] [INFO]
>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... SUCCESS [33.945s]
>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SUCCESS [25.917s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine  SUCCESS [24.788s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide  SUCCESS [23.878s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SUCCESS [9.476s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons  SUCCESS [14.046s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SUCCESS [12.535s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Documentation .............. SUCCESS [26.484s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  SUCCESS [7.376s]
>>>> [INFO] [INFO] ------------------------------------------------------------------------
>>>> [INFO] [INFO] BUILD SUCCESS
>>>> [INFO] [INFO] ------------------------------------------------------------------------
>>>> [INFO] [INFO] Total time: 2:59.468s
>>>> [INFO] [INFO] Finished at: Mon Jan 21 19:24:28 CET 2013
>>>> [INFO] [INFO] Final Memory: 146M/461M
>>>> [INFO] [INFO] ------------------------------------------------------------------------
>>>> [INFO] Checking in modified POMs...
>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file C:\Users\pkluegl\AppData\Local\Temp\maven-scm-1977004734.commit --targets C:\Users\pkluegl\AppData\Local\Temp\maven-scm-2678525437479394015-targets"
>>>> [INFO] Working directory: D:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>> [INFO] Tagging release with the label uimaj-textmarker-parent-2.0.0...
>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\Users\pkluegl\AppData\Local\Temp\maven-scm-343353279.commit --revision 1436535 https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmarker-parent-2.0.0"
>>>> [INFO] Working directory: d:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Reactor Summary:
>>>> [INFO]
>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... FAILURE [3:16.435s]
>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SKIPPED
>>>> [INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  SKIPPED
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] BUILD FAILURE
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Total time: 3:18.044s
>>>> [INFO] Finished at: Mon Jan 21 19:24:41 CET 2013
>>>> [INFO] Final Memory: 17M/221M
>>>> [INFO] ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on project uimaj-textmarker-parent: Unable to tag SCM
>>>> [ERROR] Provider message:
>>>> [ERROR] The svn tag command failed.
>>>> [ERROR] Command output:
>>>> [ERROR] svn: E160006: No such revision 1436535
>>>> [ERROR] -> [Help 1]
>>>> [ERROR]
>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>> [ERROR]
>>>> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>>>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Good luck. When you find out what's the problem, drop us a note. 

I never run releases in Eclipse and teach anybody to do them on the command line. I suppose it cannot hurt if you try. Make sure you the latest Maven release.

Another thing: are you sure the SCM location is correct in the POM?

Cheers,

-- Richard

Am 21.01.2013 um 21:07 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:

> Hi Richard,
> 
> Am 21.01.2013 20:48, schrieb Richard Eckart de Castilho:
>> Hi Peter,
>> 
>> to avoid username/pw on the command line, I had to use a differnent svn binary. Normally it should be enough to log in on the command line once (e.g. by issuing a "svn log" command) and let svn cache the credentials.
>> 
>> But anyway, your error doesn't look like missing credentials (it should say something along the lines "access denied") it rather looks like a SVN server glitch - something I get on Google Code every one in a while. Did you try just calling "mvn release:prepare" again? Maven remembers where the release process got stuck and will pick up again there. If you need to abort the release, use "mvn release:rollback".
> 
> The first try was "mvn -DautoVersionSubmodules release:prepare release:perform" and failed. Then, I executed "mvn release:rollback" and tried only "mvn -DautoVersionSubmodules release:prepare". This also failed, followed by another rollback.
> 
> I gonna do some internet search about the error message tomorrow . Maybe I find some explanation what might be causing this.
> 
> Btw, I am doing this in Eclipse with "Maven/run as..." and with an external maven install. Shouldn't be a problem, I think.
> 
> Peter
> 
>> Cheers,
>> 
>> -- Richard
>> 
>> Am 21.01.2013 um 19:38 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>> 
>>> On 17.01.2013 19:08, Richard Eckart de Castilho wrote:
>>>> Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:
>>>> 
>>>>>> If your release fails at some SVN operation like creating the tag, try providing "-Dusername=XXX -Dpassword=YYY" on the command line with your SVN credentials.
>>>>> I've never had to do this.  I would be careful, in case these are sent in the
>>>>> "clear" (I don't know about this).
>>>> If you local SVN setup is well configured, this should not be required. I've had some issues in the past on OS X with SVN not picking up cached passwords during a Maven release. I didn't read the code, but I expect the credentials are passed on when Maven calls the external SVN process and are sent via whatever protocol you use to communicate with the SVN server. But they do end up in the shell history of course - clearing the command from there after the process is certainly wise.
>>>> 
>>>> -- Richard
>>>> 
>>> Hmm... that probably happened to me now but the error doesn't look like missing SVN credentials.
>>> 
>>> The SVN setup looks fine. Any idea how to avoid "-Dusername=XXX -Dpassword=YYY"?
>>> 
>>> Btw, I wasn't asked yet for the tag (RC1), but I think that will happen later, right?
>>> 
>>> Here's the console:
>>> 
>>> ...
>>> [INFO] [INFO] Reactor Summary:
>>> [INFO] [INFO]
>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... SUCCESS [33.945s]
>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SUCCESS [25.917s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine  SUCCESS [24.788s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide  SUCCESS [23.878s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SUCCESS [9.476s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons  SUCCESS [14.046s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SUCCESS [12.535s]
>>> [INFO] [INFO] Apache UIMA TextMarker Documentation .............. SUCCESS [26.484s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  SUCCESS [7.376s]
>>> [INFO] [INFO] ------------------------------------------------------------------------
>>> [INFO] [INFO] BUILD SUCCESS
>>> [INFO] [INFO] ------------------------------------------------------------------------
>>> [INFO] [INFO] Total time: 2:59.468s
>>> [INFO] [INFO] Finished at: Mon Jan 21 19:24:28 CET 2013
>>> [INFO] [INFO] Final Memory: 146M/461M
>>> [INFO] [INFO] ------------------------------------------------------------------------
>>> [INFO] Checking in modified POMs...
>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file C:\Users\pkluegl\AppData\Local\Temp\maven-scm-1977004734.commit --targets C:\Users\pkluegl\AppData\Local\Temp\maven-scm-2678525437479394015-targets"
>>> [INFO] Working directory: D:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>> [INFO] Tagging release with the label uimaj-textmarker-parent-2.0.0...
>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\Users\pkluegl\AppData\Local\Temp\maven-scm-343353279.commit --revision 1436535 https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmarker-parent-2.0.0"
>>> [INFO] Working directory: d:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... FAILURE [3:16.435s]
>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SKIPPED
>>> [INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  SKIPPED
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] BUILD FAILURE
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Total time: 3:18.044s
>>> [INFO] Finished at: Mon Jan 21 19:24:41 CET 2013
>>> [INFO] Final Memory: 17M/221M
>>> [INFO] ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on project uimaj-textmarker-parent: Unable to tag SCM
>>> [ERROR] Provider message:
>>> [ERROR] The svn tag command failed.
>>> [ERROR] Command output:
>>> [ERROR] svn: E160006: No such revision 1436535
>>> [ERROR] -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException


-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
upgrade does not work:

upgrade D:/work/workspace-textmarker-build5/uimaj-textmarker-parent
     Invalid operation on the current working directory
svn: Can't upgrade 
'D:\work\workspace-textmarker-build5\uimaj-textmarker-parent' as it is 
not a pre-1.7 working copy directory
Can't find an entry
svn: Missing default entry


On 22.01.2013 11:02, Peter Klügl wrote:
> On 21.01.2013 22:27, Marshall Schor wrote:
>> One more strange thing to check:
>>
>> SVN changed its working directory "metadata" format going from 1.6 to 
>> 1.7
>> (client versions)
>>
>> If you accidentally have two client levels (one for 1.6 and one for 
>> 1.7) on your
>> checkout machine, and Eclipse uses one, but maven uses another, then 
>> that could
>> be trouble.
>>
>> Eclipse uses the one based on the level of the subclipse download you 
>> install.
>> Maven uses (I think) the one installed as a command line module.
>>
>> You can see the version on the command line module by doing:
>>
>> svn --version
>>
>> You can see the version in Eclipse by doing menu -> help -> install 
>> new software
>> -> what's already installed and then looking for Subclipse. If it 
>> says 1.6.xx,
>> then it for Subversion 1.6.x  If it says 1.8.x, it's for Subversion 
>> 1.7.x
>
> The svn versions I am using:
>
> command line: svn, Version 1.7.8-SlikSvn-1.7.8-X64 (SlikSvn/1.7.8) X64
> eclipse plugin: Subclipse (Required)    1.8.16 
> org.tigris.subversion.subclipse.feature.group    tigris.org
>
> The eclipse plugin offers me the option to upgrade the projects... I 
> gonna do that and then try to run mvn on command line.
>
> Peter
>
>
>> -Marshall
>> On 1/21/2013 3:07 PM, Peter Klügl wrote:
>>> Hi Richard,
>>>
>>> Am 21.01.2013 20:48, schrieb Richard Eckart de Castilho:
>>>> Hi Peter,
>>>>
>>>> to avoid username/pw on the command line, I had to use a differnent 
>>>> svn
>>>> binary. Normally it should be enough to log in on the command line 
>>>> once (e.g.
>>>> by issuing a "svn log" command) and let svn cache the credentials.
>>>>
>>>> But anyway, your error doesn't look like missing credentials (it 
>>>> should say
>>>> something along the lines "access denied") it rather looks like a 
>>>> SVN server
>>>> glitch - something I get on Google Code every one in a while. Did 
>>>> you try
>>>> just calling "mvn release:prepare" again? Maven remembers where the 
>>>> release
>>>> process got stuck and will pick up again there. If you need to 
>>>> abort the
>>>> release, use "mvn release:rollback".
>>> The first try was "mvn -DautoVersionSubmodules release:prepare
>>> release:perform" and failed. Then, I executed "mvn release:rollback" 
>>> and tried
>>> only "mvn -DautoVersionSubmodules release:prepare". This also 
>>> failed, followed
>>> by another rollback.
>>>
>>> I gonna do some internet search about the error message tomorrow . 
>>> Maybe I
>>> find some explanation what might be causing this.
>>>
>>> Btw, I am doing this in Eclipse with "Maven/run as..." and with an 
>>> external
>>> maven install. Shouldn't be a problem, I think.
>>>
>>> Peter
>>>
>>>> Cheers,
>>>>
>>>> -- Richard
>>>>
>>>> Am 21.01.2013 um 19:38 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>>>>
>>>>> On 17.01.2013 19:08, Richard Eckart de Castilho wrote:
>>>>>> Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:
>>>>>>
>>>>>>>> If your release fails at some SVN operation like creating the 
>>>>>>>> tag, try
>>>>>>>> providing "-Dusername=XXX -Dpassword=YYY" on the command line 
>>>>>>>> with your
>>>>>>>> SVN credentials.
>>>>>>> I've never had to do this.  I would be careful, in case these 
>>>>>>> are sent in the
>>>>>>> "clear" (I don't know about this).
>>>>>> If you local SVN setup is well configured, this should not be 
>>>>>> required.
>>>>>> I've had some issues in the past on OS X with SVN not picking up 
>>>>>> cached
>>>>>> passwords during a Maven release. I didn't read the code, but I 
>>>>>> expect the
>>>>>> credentials are passed on when Maven calls the external SVN 
>>>>>> process and are
>>>>>> sent via whatever protocol you use to communicate with the SVN 
>>>>>> server. But
>>>>>> they do end up in the shell history of course - clearing the 
>>>>>> command from
>>>>>> there after the process is certainly wise.
>>>>>>
>>>>>> -- Richard
>>>>>>
>>>>> Hmm... that probably happened to me now but the error doesn't look 
>>>>> like
>>>>> missing SVN credentials.
>>>>>
>>>>> The SVN setup looks fine. Any idea how to avoid "-Dusername=XXX
>>>>> -Dpassword=YYY"?
>>>>>
>>>>> Btw, I wasn't asked yet for the tag (RC1), but I think that will 
>>>>> happen
>>>>> later, right?
>>>>>
>>>>> Here's the console:
>>>>>
>>>>> ...
>>>>> [INFO] [INFO] Reactor Summary:
>>>>> [INFO] [INFO]
>>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... 
>>>>> SUCCESS
>>>>> [33.945s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... 
>>>>> SUCCESS
>>>>> [25.917s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-engine
>>>>> SUCCESS [24.788s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide
>>>>> SUCCESS [23.878s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-caseditor
>>>>> SUCCESS [9.476s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-addons
>>>>> SUCCESS [14.046s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-textruler
>>>>> SUCCESS [12.535s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Documentation .............. 
>>>>> SUCCESS
>>>>> [26.484s]
>>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse:
>>>>> uimaj-textmarker-eclipse-feature  SUCCESS [7.376s]
>>>>> [INFO] [INFO]
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] [INFO] BUILD SUCCESS
>>>>> [INFO] [INFO]
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] [INFO] Total time: 2:59.468s
>>>>> [INFO] [INFO] Finished at: Mon Jan 21 19:24:28 CET 2013
>>>>> [INFO] [INFO] Final Memory: 146M/461M
>>>>> [INFO] [INFO]
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] Checking in modified POMs...
>>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
>>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-1977004734.commit 
>>>>> --targets
>>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-2678525437479394015-targets" 
>>>>>
>>>>> [INFO] Working directory:
>>>>> D:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>>> [INFO] Tagging release with the label 
>>>>> uimaj-textmarker-parent-2.0.0...
>>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
>>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-343353279.commit 
>>>>> --revision
>>>>> 1436535 
>>>>> https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk
>>>>> https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmarker-parent-2.0.0" 
>>>>>
>>>>>
>>>>> [INFO] Working directory:
>>>>> d:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>>> [INFO] 
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] Reactor Summary:
>>>>> [INFO]
>>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... FAILURE 
>>>>> [3:16.435s]
>>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine 
>>>>> SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide 
>>>>> SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-caseditor  SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons 
>>>>> SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-ep-textmarker-textruler  SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
>>>>> [INFO] Apache UIMA TextMarker Eclipse: 
>>>>> uimaj-textmarker-eclipse-feature
>>>>> SKIPPED
>>>>> [INFO] 
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] BUILD FAILURE
>>>>> [INFO] 
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [INFO] Total time: 3:18.044s
>>>>> [INFO] Finished at: Mon Jan 21 19:24:41 CET 2013
>>>>> [INFO] Final Memory: 17M/221M
>>>>> [INFO] 
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-release-plugin:2.1:prepare 
>>>>> (default-cli) on
>>>>> project uimaj-textmarker-parent: Unable to tag SCM
>>>>> [ERROR] Provider message:
>>>>> [ERROR] The svn tag command failed.
>>>>> [ERROR] Command output:
>>>>> [ERROR] svn: E160006: No such revision 1436535
>>>>> [ERROR] -> [Help 1]
>>>>> [ERROR]
>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven 
>>>>> with the -e
>>>>> switch.
>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug 
>>>>> logging.
>>>>> [ERROR]
>>>>> [ERROR] For more information about the errors and possible 
>>>>> solutions, please
>>>>> read the following articles:
>>>>> [ERROR] [Help 1]
>>>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
On 21.01.2013 22:27, Marshall Schor wrote:
> One more strange thing to check:
>
> SVN changed its working directory "metadata" format going from 1.6 to 1.7
> (client versions)
>
> If you accidentally have two client levels (one for 1.6 and one for 1.7) on your
> checkout machine, and Eclipse uses one, but maven uses another, then that could
> be trouble.
>
> Eclipse uses the one based on the level of the subclipse download you install.
> Maven uses (I think) the one installed as a command line module.
>
> You can see the version on the command line module by doing:
>
> svn --version
>
> You can see the version in Eclipse by doing menu -> help -> install new software
> -> what's already installed and then looking for Subclipse.  If it says 1.6.xx,
> then it for Subversion 1.6.x  If it says 1.8.x, it's for Subversion 1.7.x

The svn versions I am using:

command line: svn, Version 1.7.8-SlikSvn-1.7.8-X64 (SlikSvn/1.7.8) X64
eclipse plugin: Subclipse (Required)    1.8.16 
org.tigris.subversion.subclipse.feature.group    tigris.org

The eclipse plugin offers me the option to upgrade the projects... I 
gonna do that and then try to run mvn on command line.

Peter


> -Marshall
> On 1/21/2013 3:07 PM, Peter Klügl wrote:
>> Hi Richard,
>>
>> Am 21.01.2013 20:48, schrieb Richard Eckart de Castilho:
>>> Hi Peter,
>>>
>>> to avoid username/pw on the command line, I had to use a differnent svn
>>> binary. Normally it should be enough to log in on the command line once (e.g.
>>> by issuing a "svn log" command) and let svn cache the credentials.
>>>
>>> But anyway, your error doesn't look like missing credentials (it should say
>>> something along the lines "access denied") it rather looks like a SVN server
>>> glitch - something I get on Google Code every one in a while. Did you try
>>> just calling "mvn release:prepare" again? Maven remembers where the release
>>> process got stuck and will pick up again there. If you need to abort the
>>> release, use "mvn release:rollback".
>> The first try was "mvn -DautoVersionSubmodules release:prepare
>> release:perform" and failed. Then, I executed "mvn release:rollback" and tried
>> only "mvn -DautoVersionSubmodules release:prepare". This also failed, followed
>> by another rollback.
>>
>> I gonna do some internet search about the error message tomorrow . Maybe I
>> find some explanation what might be causing this.
>>
>> Btw, I am doing this in Eclipse with "Maven/run as..." and with an external
>> maven install. Shouldn't be a problem, I think.
>>
>> Peter
>>
>>> Cheers,
>>>
>>> -- Richard
>>>
>>> Am 21.01.2013 um 19:38 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>>>
>>>> On 17.01.2013 19:08, Richard Eckart de Castilho wrote:
>>>>> Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:
>>>>>
>>>>>>> If your release fails at some SVN operation like creating the tag, try
>>>>>>> providing "-Dusername=XXX -Dpassword=YYY" on the command line with your
>>>>>>> SVN credentials.
>>>>>> I've never had to do this.  I would be careful, in case these are sent in the
>>>>>> "clear" (I don't know about this).
>>>>> If you local SVN setup is well configured, this should not be required.
>>>>> I've had some issues in the past on OS X with SVN not picking up cached
>>>>> passwords during a Maven release. I didn't read the code, but I expect the
>>>>> credentials are passed on when Maven calls the external SVN process and are
>>>>> sent via whatever protocol you use to communicate with the SVN server. But
>>>>> they do end up in the shell history of course - clearing the command from
>>>>> there after the process is certainly wise.
>>>>>
>>>>> -- Richard
>>>>>
>>>> Hmm... that probably happened to me now but the error doesn't look like
>>>> missing SVN credentials.
>>>>
>>>> The SVN setup looks fine. Any idea how to avoid "-Dusername=XXX
>>>> -Dpassword=YYY"?
>>>>
>>>> Btw, I wasn't asked yet for the tag (RC1), but I think that will happen
>>>> later, right?
>>>>
>>>> Here's the console:
>>>>
>>>> ...
>>>> [INFO] [INFO] Reactor Summary:
>>>> [INFO] [INFO]
>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... SUCCESS
>>>> [33.945s]
>>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SUCCESS
>>>> [25.917s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine
>>>> SUCCESS [24.788s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide
>>>> SUCCESS [23.878s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor
>>>> SUCCESS [9.476s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons
>>>> SUCCESS [14.046s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler
>>>> SUCCESS [12.535s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Documentation .............. SUCCESS
>>>> [26.484s]
>>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse:
>>>> uimaj-textmarker-eclipse-feature  SUCCESS [7.376s]
>>>> [INFO] [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] [INFO] BUILD SUCCESS
>>>> [INFO] [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] [INFO] Total time: 2:59.468s
>>>> [INFO] [INFO] Finished at: Mon Jan 21 19:24:28 CET 2013
>>>> [INFO] [INFO] Final Memory: 146M/461M
>>>> [INFO] [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Checking in modified POMs...
>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-1977004734.commit --targets
>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-2678525437479394015-targets"
>>>> [INFO] Working directory:
>>>> D:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>> [INFO] Tagging release with the label uimaj-textmarker-parent-2.0.0...
>>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
>>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-343353279.commit --revision
>>>> 1436535 https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk
>>>> https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmarker-parent-2.0.0"
>>>>
>>>> [INFO] Working directory:
>>>> d:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Reactor Summary:
>>>> [INFO]
>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... FAILURE [3:16.435s]
>>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SKIPPED
>>>> [INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
>>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature
>>>> SKIPPED
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] BUILD FAILURE
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Total time: 3:18.044s
>>>> [INFO] Finished at: Mon Jan 21 19:24:41 CET 2013
>>>> [INFO] Final Memory: 17M/221M
>>>> [INFO] ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on
>>>> project uimaj-textmarker-parent: Unable to tag SCM
>>>> [ERROR] Provider message:
>>>> [ERROR] The svn tag command failed.
>>>> [ERROR] Command output:
>>>> [ERROR] svn: E160006: No such revision 1436535
>>>> [ERROR] -> [Help 1]
>>>> [ERROR]
>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
>>>> switch.
>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>> [ERROR]
>>>> [ERROR] For more information about the errors and possible solutions, please
>>>> read the following articles:
>>>> [ERROR] [Help 1]
>>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
One more strange thing to check:

SVN changed its working directory "metadata" format going from 1.6 to 1.7
(client versions)

If you accidentally have two client levels (one for 1.6 and one for 1.7) on your
checkout machine, and Eclipse uses one, but maven uses another, then that could
be trouble.

Eclipse uses the one based on the level of the subclipse download you install. 
Maven uses (I think) the one installed as a command line module.

You can see the version on the command line module by doing:

svn --version

You can see the version in Eclipse by doing menu -> help -> install new software
-> what's already installed and then looking for Subclipse.  If it says 1.6.xx,
then it for Subversion 1.6.x  If it says 1.8.x, it's for Subversion 1.7.x

-Marshall 
On 1/21/2013 3:07 PM, Peter Klügl wrote:
> Hi Richard,
>
> Am 21.01.2013 20:48, schrieb Richard Eckart de Castilho:
>> Hi Peter,
>>
>> to avoid username/pw on the command line, I had to use a differnent svn
>> binary. Normally it should be enough to log in on the command line once (e.g.
>> by issuing a "svn log" command) and let svn cache the credentials.
>>
>> But anyway, your error doesn't look like missing credentials (it should say
>> something along the lines "access denied") it rather looks like a SVN server
>> glitch - something I get on Google Code every one in a while. Did you try
>> just calling "mvn release:prepare" again? Maven remembers where the release
>> process got stuck and will pick up again there. If you need to abort the
>> release, use "mvn release:rollback".
>
> The first try was "mvn -DautoVersionSubmodules release:prepare
> release:perform" and failed. Then, I executed "mvn release:rollback" and tried
> only "mvn -DautoVersionSubmodules release:prepare". This also failed, followed
> by another rollback.
>
> I gonna do some internet search about the error message tomorrow . Maybe I
> find some explanation what might be causing this.
>
> Btw, I am doing this in Eclipse with "Maven/run as..." and with an external
> maven install. Shouldn't be a problem, I think.
>
> Peter
>
>> Cheers,
>>
>> -- Richard
>>
>> Am 21.01.2013 um 19:38 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>>
>>> On 17.01.2013 19:08, Richard Eckart de Castilho wrote:
>>>> Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:
>>>>
>>>>>> If your release fails at some SVN operation like creating the tag, try
>>>>>> providing "-Dusername=XXX -Dpassword=YYY" on the command line with your
>>>>>> SVN credentials.
>>>>> I've never had to do this.  I would be careful, in case these are sent in the
>>>>> "clear" (I don't know about this).
>>>> If you local SVN setup is well configured, this should not be required.
>>>> I've had some issues in the past on OS X with SVN not picking up cached
>>>> passwords during a Maven release. I didn't read the code, but I expect the
>>>> credentials are passed on when Maven calls the external SVN process and are
>>>> sent via whatever protocol you use to communicate with the SVN server. But
>>>> they do end up in the shell history of course - clearing the command from
>>>> there after the process is certainly wise.
>>>>
>>>> -- Richard
>>>>
>>> Hmm... that probably happened to me now but the error doesn't look like
>>> missing SVN credentials.
>>>
>>> The SVN setup looks fine. Any idea how to avoid "-Dusername=XXX
>>> -Dpassword=YYY"?
>>>
>>> Btw, I wasn't asked yet for the tag (RC1), but I think that will happen
>>> later, right?
>>>
>>> Here's the console:
>>>
>>> ...
>>> [INFO] [INFO] Reactor Summary:
>>> [INFO] [INFO]
>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... SUCCESS
>>> [33.945s]
>>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SUCCESS
>>> [25.917s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine 
>>> SUCCESS [24.788s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide 
>>> SUCCESS [23.878s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor 
>>> SUCCESS [9.476s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons 
>>> SUCCESS [14.046s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler 
>>> SUCCESS [12.535s]
>>> [INFO] [INFO] Apache UIMA TextMarker Documentation .............. SUCCESS
>>> [26.484s]
>>> [INFO] [INFO] Apache UIMA TextMarker Eclipse:
>>> uimaj-textmarker-eclipse-feature  SUCCESS [7.376s]
>>> [INFO] [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [INFO] BUILD SUCCESS
>>> [INFO] [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [INFO] Total time: 2:59.468s
>>> [INFO] [INFO] Finished at: Mon Jan 21 19:24:28 CET 2013
>>> [INFO] [INFO] Final Memory: 146M/461M
>>> [INFO] [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Checking in modified POMs...
>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-1977004734.commit --targets
>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-2678525437479394015-targets"
>>> [INFO] Working directory:
>>> D:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>> [INFO] Tagging release with the label uimaj-textmarker-parent-2.0.0...
>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
>>> C:\Users\pkluegl\AppData\Local\Temp\maven-scm-343353279.commit --revision
>>> 1436535 https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk
>>> https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmarker-parent-2.0.0"
>>>
>>> [INFO] Working directory:
>>> d:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... FAILURE [3:16.435s]
>>> [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SKIPPED
>>> [INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
>>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature 
>>> SKIPPED
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] BUILD FAILURE
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Total time: 3:18.044s
>>> [INFO] Finished at: Mon Jan 21 19:24:41 CET 2013
>>> [INFO] Final Memory: 17M/221M
>>> [INFO] ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on
>>> project uimaj-textmarker-parent: Unable to tag SCM
>>> [ERROR] Provider message:
>>> [ERROR] The svn tag command failed.
>>> [ERROR] Command output:
>>> [ERROR] svn: E160006: No such revision 1436535
>>> [ERROR] -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
>>> switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions, please
>>> read the following articles:
>>> [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>
>
>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Hi Richard,

Am 21.01.2013 20:48, schrieb Richard Eckart de Castilho:
> Hi Peter,
>
> to avoid username/pw on the command line, I had to use a differnent svn binary. Normally it should be enough to log in on the command line once (e.g. by issuing a "svn log" command) and let svn cache the credentials.
>
> But anyway, your error doesn't look like missing credentials (it should say something along the lines "access denied") it rather looks like a SVN server glitch - something I get on Google Code every one in a while. Did you try just calling "mvn release:prepare" again? Maven remembers where the release process got stuck and will pick up again there. If you need to abort the release, use "mvn release:rollback".

The first try was "mvn -DautoVersionSubmodules release:prepare 
release:perform" and failed. Then, I executed "mvn release:rollback" and 
tried only "mvn -DautoVersionSubmodules release:prepare". This also 
failed, followed by another rollback.

I gonna do some internet search about the error message tomorrow . Maybe 
I find some explanation what might be causing this.

Btw, I am doing this in Eclipse with "Maven/run as..." and with an 
external maven install. Shouldn't be a problem, I think.

Peter

> Cheers,
>
> -- Richard
>
> Am 21.01.2013 um 19:38 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>
>> On 17.01.2013 19:08, Richard Eckart de Castilho wrote:
>>> Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:
>>>
>>>>> If your release fails at some SVN operation like creating the tag, try providing "-Dusername=XXX -Dpassword=YYY" on the command line with your SVN credentials.
>>>> I've never had to do this.  I would be careful, in case these are sent in the
>>>> "clear" (I don't know about this).
>>> If you local SVN setup is well configured, this should not be required. I've had some issues in the past on OS X with SVN not picking up cached passwords during a Maven release. I didn't read the code, but I expect the credentials are passed on when Maven calls the external SVN process and are sent via whatever protocol you use to communicate with the SVN server. But they do end up in the shell history of course - clearing the command from there after the process is certainly wise.
>>>
>>> -- Richard
>>>
>> Hmm... that probably happened to me now but the error doesn't look like missing SVN credentials.
>>
>> The SVN setup looks fine. Any idea how to avoid "-Dusername=XXX -Dpassword=YYY"?
>>
>> Btw, I wasn't asked yet for the tag (RC1), but I think that will happen later, right?
>>
>> Here's the console:
>>
>> ...
>> [INFO] [INFO] Reactor Summary:
>> [INFO] [INFO]
>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... SUCCESS [33.945s]
>> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SUCCESS [25.917s]
>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine  SUCCESS [24.788s]
>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide  SUCCESS [23.878s]
>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SUCCESS [9.476s]
>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons  SUCCESS [14.046s]
>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SUCCESS [12.535s]
>> [INFO] [INFO] Apache UIMA TextMarker Documentation .............. SUCCESS [26.484s]
>> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  SUCCESS [7.376s]
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [INFO] BUILD SUCCESS
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] [INFO] Total time: 2:59.468s
>> [INFO] [INFO] Finished at: Mon Jan 21 19:24:28 CET 2013
>> [INFO] [INFO] Final Memory: 146M/461M
>> [INFO] [INFO] ------------------------------------------------------------------------
>> [INFO] Checking in modified POMs...
>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file C:\Users\pkluegl\AppData\Local\Temp\maven-scm-1977004734.commit --targets C:\Users\pkluegl\AppData\Local\Temp\maven-scm-2678525437479394015-targets"
>> [INFO] Working directory: D:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>> [INFO] Tagging release with the label uimaj-textmarker-parent-2.0.0...
>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\Users\pkluegl\AppData\Local\Temp\maven-scm-343353279.commit --revision 1436535 https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmarker-parent-2.0.0"
>> [INFO] Working directory: d:\work\workspace-textmarker-build5\uimaj-textmarker-parent
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... FAILURE [3:16.435s]
>> [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine SKIPPED
>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide SKIPPED
>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SKIPPED
>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons SKIPPED
>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SKIPPED
>> [INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
>> [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  SKIPPED
>> [INFO] ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Total time: 3:18.044s
>> [INFO] Finished at: Mon Jan 21 19:24:41 CET 2013
>> [INFO] Final Memory: 17M/221M
>> [INFO] ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on project uimaj-textmarker-parent: Unable to tag SCM
>> [ERROR] Provider message:
>> [ERROR] The svn tag command failed.
>> [ERROR] Command output:
>> [ERROR] svn: E160006: No such revision 1436535
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Hi Peter,

to avoid username/pw on the command line, I had to use a differnent svn binary. Normally it should be enough to log in on the command line once (e.g. by issuing a "svn log" command) and let svn cache the credentials.

But anyway, your error doesn't look like missing credentials (it should say something along the lines "access denied") it rather looks like a SVN server glitch - something I get on Google Code every one in a while. Did you try just calling "mvn release:prepare" again? Maven remembers where the release process got stuck and will pick up again there. If you need to abort the release, use "mvn release:rollback".

Cheers,

-- Richard

Am 21.01.2013 um 19:38 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:

> On 17.01.2013 19:08, Richard Eckart de Castilho wrote:
>> Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:
>> 
>>>> If your release fails at some SVN operation like creating the tag, try providing "-Dusername=XXX -Dpassword=YYY" on the command line with your SVN credentials.
>>> I've never had to do this.  I would be careful, in case these are sent in the
>>> "clear" (I don't know about this).
>> If you local SVN setup is well configured, this should not be required. I've had some issues in the past on OS X with SVN not picking up cached passwords during a Maven release. I didn't read the code, but I expect the credentials are passed on when Maven calls the external SVN process and are sent via whatever protocol you use to communicate with the SVN server. But they do end up in the shell history of course - clearing the command from there after the process is certainly wise.
>> 
>> -- Richard
>> 
> 
> Hmm... that probably happened to me now but the error doesn't look like missing SVN credentials.
> 
> The SVN setup looks fine. Any idea how to avoid "-Dusername=XXX -Dpassword=YYY"?
> 
> Btw, I wasn't asked yet for the tag (RC1), but I think that will happen later, right?
> 
> Here's the console:
> 
> ...
> [INFO] [INFO] Reactor Summary:
> [INFO] [INFO]
> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... SUCCESS [33.945s]
> [INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SUCCESS [25.917s]
> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine  SUCCESS [24.788s]
> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide  SUCCESS [23.878s]
> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SUCCESS [9.476s]
> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons  SUCCESS [14.046s]
> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SUCCESS [12.535s]
> [INFO] [INFO] Apache UIMA TextMarker Documentation .............. SUCCESS [26.484s]
> [INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  SUCCESS [7.376s]
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD SUCCESS
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Total time: 2:59.468s
> [INFO] [INFO] Finished at: Mon Jan 21 19:24:28 CET 2013
> [INFO] [INFO] Final Memory: 146M/461M
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file C:\Users\pkluegl\AppData\Local\Temp\maven-scm-1977004734.commit --targets C:\Users\pkluegl\AppData\Local\Temp\maven-scm-2678525437479394015-targets"
> [INFO] Working directory: D:\work\workspace-textmarker-build5\uimaj-textmarker-parent
> [INFO] Tagging release with the label uimaj-textmarker-parent-2.0.0...
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\Users\pkluegl\AppData\Local\Temp\maven-scm-343353279.commit --revision 1436535 https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmarker-parent-2.0.0"
> [INFO] Working directory: d:\work\workspace-textmarker-build5\uimaj-textmarker-parent
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... FAILURE [3:16.435s]
> [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine SKIPPED
> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide SKIPPED
> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  SKIPPED
> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons SKIPPED
> [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  SKIPPED
> [INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
> [INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 3:18.044s
> [INFO] Finished at: Mon Jan 21 19:24:41 CET 2013
> [INFO] Final Memory: 17M/221M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on project uimaj-textmarker-parent: Unable to tag SCM
> [ERROR] Provider message:
> [ERROR] The svn tag command failed.
> [ERROR] Command output:
> [ERROR] svn: E160006: No such revision 1436535
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException


-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
On 17.01.2013 19:08, Richard Eckart de Castilho wrote:
> Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:
>
>>> If your release fails at some SVN operation like creating the tag, try providing "-Dusername=XXX -Dpassword=YYY" on the command line with your SVN credentials.
>> I've never had to do this.  I would be careful, in case these are sent in the
>> "clear" (I don't know about this).
> If you local SVN setup is well configured, this should not be required. I've had some issues in the past on OS X with SVN not picking up cached passwords during a Maven release. I didn't read the code, but I expect the credentials are passed on when Maven calls the external SVN process and are sent via whatever protocol you use to communicate with the SVN server. But they do end up in the shell history of course - clearing the command from there after the process is certainly wise.
>
> -- Richard
>

Hmm... that probably happened to me now but the error doesn't look like 
missing SVN credentials.

The SVN setup looks fine. Any idea how to avoid "-Dusername=XXX 
-Dpassword=YYY"?

Btw, I wasn't asked yet for the tag (RC1), but I think that will happen 
later, right?

Here's the console:

...
[INFO] [INFO] Reactor Summary:
[INFO] [INFO]
[INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... 
SUCCESS [33.945s]
[INFO] [INFO] Apache UIMA TextMarker: uimaj-textmarker .......... 
SUCCESS [25.917s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-engine  SUCCESS [24.788s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide  
SUCCESS [23.878s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-caseditor  SUCCESS [9.476s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-addons  SUCCESS [14.046s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: 
uimaj-ep-textmarker-textruler  SUCCESS [12.535s]
[INFO] [INFO] Apache UIMA TextMarker Documentation .............. 
SUCCESS [26.484s]
[INFO] [INFO] Apache UIMA TextMarker Eclipse: 
uimaj-textmarker-eclipse-feature  SUCCESS [7.376s]
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] BUILD SUCCESS
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] [INFO] Total time: 2:59.468s
[INFO] [INFO] Finished at: Mon Jan 21 19:24:28 CET 2013
[INFO] [INFO] Final Memory: 146M/461M
[INFO] [INFO] 
------------------------------------------------------------------------
[INFO] Checking in modified POMs...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file 
C:\Users\pkluegl\AppData\Local\Temp\maven-scm-1977004734.commit 
--targets 
C:\Users\pkluegl\AppData\Local\Temp\maven-scm-2678525437479394015-targets"
[INFO] Working directory: 
D:\work\workspace-textmarker-build5\uimaj-textmarker-parent
[INFO] Tagging release with the label uimaj-textmarker-parent-2.0.0...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file 
C:\Users\pkluegl\AppData\Local\Temp\maven-scm-343353279.commit 
--revision 1436535 
https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/trunk 
https://svn.apache.org/repos/asf/uima/sandbox/TextMarker/tags/uimaj-textmarker-parent-2.0.0"
[INFO] Working directory: 
d:\work\workspace-textmarker-build5\uimaj-textmarker-parent
[INFO] 
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache UIMA TextMarker: uimaj-textmarker-parent ... FAILURE 
[3:16.435s]
[INFO] Apache UIMA TextMarker: uimaj-textmarker .......... SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-engine SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-ide SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-caseditor  
SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-addons SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-ep-textmarker-textruler  
SKIPPED
[INFO] Apache UIMA TextMarker Documentation .............. SKIPPED
[INFO] Apache UIMA TextMarker Eclipse: uimaj-textmarker-eclipse-feature  
SKIPPED
[INFO] 
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] 
------------------------------------------------------------------------
[INFO] Total time: 3:18.044s
[INFO] Finished at: Mon Jan 21 19:24:41 CET 2013
[INFO] Final Memory: 17M/221M
[INFO] 
------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) 
on project uimaj-textmarker-parent: Unable to tag SCM
[ERROR] Provider message:
[ERROR] The svn tag command failed.
[ERROR] Command output:
[ERROR] svn: E160006: No such revision 1436535
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the 
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Am 17.01.2013 um 15:09 schrieb Marshall Schor <ms...@schor.com>:

>> If your release fails at some SVN operation like creating the tag, try providing "-Dusername=XXX -Dpassword=YYY" on the command line with your SVN credentials.
> 
> I've never had to do this.  I would be careful, in case these are sent in the
> "clear" (I don't know about this).

If you local SVN setup is well configured, this should not be required. I've had some issues in the past on OS X with SVN not picking up cached passwords during a Maven release. I didn't read the code, but I expect the credentials are passed on when Maven calls the external SVN process and are sent via whatever protocol you use to communicate with the SVN server. But they do end up in the shell history of course - clearing the command from there after the process is certainly wise.

-- Richard

-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
On 1/14/2013 8:51 AM, Richard Eckart de Castilho wrote:
> Am 14.01.2013 um 11:13 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>> On 09.01.2013 18:41, Richard Eckart de Castilho wrote:
>>> Am 09.01.2013 um 14:35 schrieb Marshall Schor <ms...@schor.com>:
>>>
>>>> You can add the server properties to your settings.xml, but please use the
>>>> encryption technique.
>>>> This would enable you to upload snapshots to the repository.apache.org server,
>>>> for instance.
>>> Jenkins is configured to deploy snapshot versions of TextMarker to the Apache
>>> repository server after every build. There is no need to do that manually.
>>>
>>> The server credentials in the settings.xml would only be necessary for regular
>>> releases.
>> In case of a TextMarker release, I still have to do it manually, e.g., because of the RC tag, right?
>>
>> I added the server information to my settings.xml (with encrypted passwords). What about "<id>stagingSite</id>" (must match hard-coded repository identifier in site:stage-deploy)? Do I need that element? Is that important for the documentation? I thought the documentation will be manually added to the website. I even do not know yet where it should be put or linked.
>>
>> What are my next steps? Just following the steps mentioned in http://uima.apache.org/release.html ?
> I didn't use the Apache Nexus yet, but the procedure appears to be pretty much the same as for the Sonatype OSS Nexus [1] which I have used in several projects. The link has some screenshots of Nexus you might find supplemental to the UIMA release documentation.
>
> If I understand the documentation right, you don't have to add any specific "staging" stuff anywhere. Just add the Nexus credentials to your settings.xml. Make sure the <id> of these credentials is the same used in the POM declaring the distributionManagement (I think that is the Apache master pom).

That is correct, it's in the Apache master pom.  Our inheritance goes
(typically) from project -> component-parent-pom (if there is one) -> UIMA
shared parent-pom -> Apache master pom -> Maven master pom.

>
> When you run a regular "mvn -DautoVersionSubmodules release:prepare release:perform", the artifacts go to Nexus who puts it automatically into a "staging repository". 

Right.  The release:perform is what does the deploy to the repository.apache.org
NEXUS "staging" (Not Snapshot) area.

> I never had to use "stage-deploy". From that point, there are normally two options:
>
> - closing and promoting the repository so the artifacts get deployed to Maven Central.

You have to do the closing first, which lets the team access the artifacts, test
them, confirm they're OK to release, and vote.

Only do the "promoting" step, of course, after a release vote has passed :-)

>
> - closing and dropping the repository if something went wrong or if you discard a release candidate.
>
> People can test the RC by via the staging repository.

In your note to the team to do the testing, you have to include the URL for the
team to access the staging repo.  This URL is available from
repository.apache.org, only after you "close" the staging repo.  (Once closed,
you cannot add anything more to it).
>
> If your release fails at some SVN operation like creating the tag, try providing "-Dusername=XXX -Dpassword=YYY" on the command line with your SVN credentials.

I've never had to do this.  I would be careful, in case these are sent in the
"clear" (I don't know about this).

-Marshall
>
> Cheers,
>
> -- Richard
>
> [1] https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
>

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
On 1/17/2013 8:10 AM, Peter Klügl wrote:
> On 14.01.2013 14:51, Richard Eckart de Castilho wrote:
>> Am 14.01.2013 um 11:13 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>>> On 09.01.2013 18:41, Richard Eckart de Castilho wrote:
>>>> Am 09.01.2013 um 14:35 schrieb Marshall Schor <ms...@schor.com>:
>>>>
>>>>> You can add the server properties to your settings.xml, but please use the
>>>>> encryption technique.
>>>>> This would enable you to upload snapshots to the repository.apache.org
>>>>> server,
>>>>> for instance.
>>>> Jenkins is configured to deploy snapshot versions of TextMarker to the Apache
>>>> repository server after every build. There is no need to do that manually.
>>>>
>>>> The server credentials in the settings.xml would only be necessary for regular
>>>> releases.
>>> In case of a TextMarker release, I still have to do it manually, e.g.,
>>> because of the RC tag, right?
>>>
>>> I added the server information to my settings.xml (with encrypted
>>> passwords). What about "<id>stagingSite</id>" (must match hard-coded
>>> repository identifier in site:stage-deploy)? Do I need that element? Is that
>>> important for the documentation? I thought the documentation will be
>>> manually added to the website. I even do not know yet where it should be put
>>> or linked.
>>>
>>> What are my next steps? Just following the steps mentioned in
>>> http://uima.apache.org/release.html ?
>> I didn't use the Apache Nexus yet, but the procedure appears to be pretty
>> much the same as for the Sonatype OSS Nexus [1] which I have used in several
>> projects. The link has some screenshots of Nexus you might find supplemental
>> to the UIMA release documentation.
>>
>> If I understand the documentation right, you don't have to add any specific
>> "staging" stuff anywhere. Just add the Nexus credentials to your
>> settings.xml. Make sure the <id> of these credentials is the same used in the
>> POM declaring the distributionManagement (I think that is the Apache master
>> pom).
>>
>> When you run a regular "mvn -DautoVersionSubmodules release:prepare
>> release:perform", the artifacts go to Nexus who puts it automatically into a
>> "staging repository". I never had to use "stage-deploy". From that point,
>> there are normally two options:
>>
>> - closing and promoting the repository so the artifacts get deployed to Maven
>> Central.
>>
>> - closing and dropping the repository if something went wrong or if you
>> discard a release candidate.
>>
>> People can test the RC by via the staging repository.
>>
>> If your release fails at some SVN operation like creating the tag, try
>> providing "-Dusername=XXX -Dpassword=YYY" on the command line with your SVN
>> credentials.
>
> Thanks for the information.
>
> However, is it really not neccessary to put something on my people.apache.org
> webspace?

Here's how to think about this.  A release can include parts that are intended
to be accessed (after releasing) from Maven Central, or it can include parts
that are intended to be accessed via the Apache distribution point (or its many
mirrors). 

A recent discussion on the Infrastructure list says that if a part is intended
to be accessed via Maven Central, it **also** **must** be put onto the Apache
Mirror System.   While this seems silly to me, it does allow one spot for people
to find all released distributed artifacts from Apache.

You can see this recent update to the dist point for maven projects, here:
http://www.apache.org/dist/maven/

Your eventual release should consist of several things:

1) a source-release.zip with all the sources  This goes on the Apache Mirror
system.  It is the main thing released by the ASF.

2) A convenience packaging of the build of the source, put into the Apache
Mirror system, updating our Eclipse-update-site with a new subsite.

3) A release of the plugin/feature Jars and their signings that go into Maven
Central.  These are for use by people (including our team) who are doing builds
of things (we use these to build the Eclipse-update-site, for instance).

------

To do the Vote, it's necessary to produce the signed artifacts and put them
somewhere for people to test.

For 1) - this should go into your people.a.o/~[userid]/public_html/XXXXX spot,
where XXXXX is something like "TextMarker-2.0.0-rc1" or some other
self-describing string :-).

For 2) - this should go into your people.a.o.... also

For 3) - these go into the repository.a.o "staging" spot.  They do not go on
people.a.o...

> What about the update site? I wonder if the update site is build with released
> artifacts, how can someone vote on a release candidate with no update site?

Right, you have to provide (see above) an update site on your people.a.o.... so
it can be tested/voted on.

Since you'll be adding a new sub-site, your update will include changes to the
composite and the new subsite itself.

>
> I assume it's enough to "mvn -DautoVersionSubmodules release:prepare
> release:perform" and provide a SNAPSHOT update site at
> http://people.apache.org/~pkluegl ?

Almost.  The results of release:prepare release:perform will be to produce
non-snapshot versions of things in the /target/checkout (I think that's the
name), and to deploy these to the "Staging" (not Snapshot) repo in
repository.apache.org.

You'll need to assemble the new eclipse update site into people.a.o...  by
copying the changed files from the uima-eclipse-composite-update-site's
/target/checkout and your own Textmarker's eclipse-update-site.

(This is because we haven't (yet) built any automation for this final assembly
of the composite update site and its subsites.)

>
> Am I missing something?
>
> Do I have to adapt something because of the latest changes in INFRA-5746?

Not yet.  The latest changes in there come into play when the vote passes. 
Then, you have to do svn operations to alter the content in /release/uima to
update it with the approved artifacts.

-Marshall  (hoping he didn't forget something ...)

> Peter
>
>
>
>
>
>
>
>> Cheers,
>>
>> -- Richard
>>
>> [1]
>> https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
>>
>
>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
On 14.01.2013 14:51, Richard Eckart de Castilho wrote:
> Am 14.01.2013 um 11:13 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>> On 09.01.2013 18:41, Richard Eckart de Castilho wrote:
>>> Am 09.01.2013 um 14:35 schrieb Marshall Schor <ms...@schor.com>:
>>>
>>>> You can add the server properties to your settings.xml, but please use the
>>>> encryption technique.
>>>> This would enable you to upload snapshots to the repository.apache.org server,
>>>> for instance.
>>> Jenkins is configured to deploy snapshot versions of TextMarker to the Apache
>>> repository server after every build. There is no need to do that manually.
>>>
>>> The server credentials in the settings.xml would only be necessary for regular
>>> releases.
>> In case of a TextMarker release, I still have to do it manually, e.g., because of the RC tag, right?
>>
>> I added the server information to my settings.xml (with encrypted passwords). What about "<id>stagingSite</id>" (must match hard-coded repository identifier in site:stage-deploy)? Do I need that element? Is that important for the documentation? I thought the documentation will be manually added to the website. I even do not know yet where it should be put or linked.
>>
>> What are my next steps? Just following the steps mentioned in http://uima.apache.org/release.html ?
> I didn't use the Apache Nexus yet, but the procedure appears to be pretty much the same as for the Sonatype OSS Nexus [1] which I have used in several projects. The link has some screenshots of Nexus you might find supplemental to the UIMA release documentation.
>
> If I understand the documentation right, you don't have to add any specific "staging" stuff anywhere. Just add the Nexus credentials to your settings.xml. Make sure the <id> of these credentials is the same used in the POM declaring the distributionManagement (I think that is the Apache master pom).
>
> When you run a regular "mvn -DautoVersionSubmodules release:prepare release:perform", the artifacts go to Nexus who puts it automatically into a "staging repository". I never had to use "stage-deploy". From that point, there are normally two options:
>
> - closing and promoting the repository so the artifacts get deployed to Maven Central.
>
> - closing and dropping the repository if something went wrong or if you discard a release candidate.
>
> People can test the RC by via the staging repository.
>
> If your release fails at some SVN operation like creating the tag, try providing "-Dusername=XXX -Dpassword=YYY" on the command line with your SVN credentials.

Thanks for the information.

However, is it really not neccessary to put something on my 
people.apache.org webspace? What about the update site? I wonder if the 
update site is build with released artifacts, how can someone vote on a 
release candidate with no update site?

I assume it's enough to "mvn -DautoVersionSubmodules release:prepare 
release:perform" and provide a SNAPSHOT update site at 
http://people.apache.org/~pkluegl ?

Am I missing something?

Do I have to adapt something because of the latest changes in INFRA-5746?

Peter







> Cheers,
>
> -- Richard
>
> [1] https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Am 14.01.2013 um 11:13 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
> On 09.01.2013 18:41, Richard Eckart de Castilho wrote:
>> Am 09.01.2013 um 14:35 schrieb Marshall Schor <ms...@schor.com>:
>> 
>>> You can add the server properties to your settings.xml, but please use the
>>> encryption technique.
>>> This would enable you to upload snapshots to the repository.apache.org server,
>>> for instance.
>> Jenkins is configured to deploy snapshot versions of TextMarker to the Apache
>> repository server after every build. There is no need to do that manually.
>> 
>> The server credentials in the settings.xml would only be necessary for regular
>> releases.
> 
> In case of a TextMarker release, I still have to do it manually, e.g., because of the RC tag, right?
> 
> I added the server information to my settings.xml (with encrypted passwords). What about "<id>stagingSite</id>" (must match hard-coded repository identifier in site:stage-deploy)? Do I need that element? Is that important for the documentation? I thought the documentation will be manually added to the website. I even do not know yet where it should be put or linked.
> 
> What are my next steps? Just following the steps mentioned in http://uima.apache.org/release.html ?

I didn't use the Apache Nexus yet, but the procedure appears to be pretty much the same as for the Sonatype OSS Nexus [1] which I have used in several projects. The link has some screenshots of Nexus you might find supplemental to the UIMA release documentation.

If I understand the documentation right, you don't have to add any specific "staging" stuff anywhere. Just add the Nexus credentials to your settings.xml. Make sure the <id> of these credentials is the same used in the POM declaring the distributionManagement (I think that is the Apache master pom).

When you run a regular "mvn -DautoVersionSubmodules release:prepare release:perform", the artifacts go to Nexus who puts it automatically into a "staging repository". I never had to use "stage-deploy". From that point, there are normally two options:

- closing and promoting the repository so the artifacts get deployed to Maven Central.

- closing and dropping the repository if something went wrong or if you discard a release candidate.

People can test the RC by via the staging repository.

If your release fails at some SVN operation like creating the tag, try providing "-Dusername=XXX -Dpassword=YYY" on the command line with your SVN credentials.

Cheers,

-- Richard

[1] https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
On 09.01.2013 18:41, Richard Eckart de Castilho wrote:
> Am 09.01.2013 um 14:35 schrieb Marshall Schor <ms...@schor.com>:
>
>> You can add the server properties to your settings.xml, but please use the
>> encryption technique.
>> This would enable you to upload snapshots to the repository.apache.org server,
>> for instance.
> Jenkins is configured to deploy snapshot versions of TextMarker to the Apache
> repository server after every build. There is no need to do that manually.
>
> The server credentials in the settings.xml would only be necessary for regular
> releases.

In case of a TextMarker release, I still have to do it manually, e.g., 
because of the RC tag, right?

I added the server information to my settings.xml (with encrypted 
passwords). What about "<id>stagingSite</id>" (must match hard-coded 
repository identifier in site:stage-deploy)? Do I need that element? Is 
that important for the documentation? I thought the documentation will 
be manually added to the website. I even do not know yet where it should 
be put or linked.

What are my next steps? Just following the steps mentioned in 
http://uima.apache.org/release.html ?

Peter

> Cheers,
>
> -- Richard
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Am 09.01.2013 um 14:35 schrieb Marshall Schor <ms...@schor.com>:

> You can add the server properties to your settings.xml, but please use the
> encryption technique.
> This would enable you to upload snapshots to the repository.apache.org server,
> for instance.

Jenkins is configured to deploy snapshot versions of TextMarker to the Apache
repository server after every build. There is no need to do that manually.

The server credentials in the settings.xml would only be necessary for regular
releases.

Cheers,

-- Richard

-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
On 1/9/2013 10:06 AM, Peter Klügl wrote:
> Hi,
>
> next question about "Building The Release Candidate"
>
> I did now a trial build of the release candidate with "mvn install
> -Papache-release". The only thing that looks not correct is the naming of the
> pom for the Eclipse plugins, for example:
>
> org.apache.uima.textmarker.addons_${parsedVersion.osgiVersion}.pom
>
> Do I have to take care of that? This happens also for the CAS Editor plugin in
> my workspace.

Can you say a bit more for those of us not following all the details :-) - for
instance, what should this be changed to, and where in the build (what part of
the build) is this being done?
>
> What is the next step? Should I already add the server properties to my
> settings.xml as described here [1], or is there an intermediate step, e.g.,
> uploading the trial to my people.apache.org webspace?

You can add the server properties to your settings.xml, but please use the
encryption technique.
This would enable you to upload snapshots to the repository.apache.org server,
for instance.

Before doing a release, we need to finish the ip clearance process, too.

-Marshall
>
> Best,
>
> Peter
>
> [1] http://maven.apache.org/developers/committer-settings.html
>
>
> On 08.01.2013 22:40, Peter Klügl wrote:
>> I have found the problem by taking a closer look at the uima-as pom.  ->
>> plugin version + config
>>
>> Can someone verify if the org.apache.uima:parent-pom works correctly? It did
>> not work for me and I think it needs to be updates for Jira >4.
>> The maven-changes-plugin version points to 2.6, for example.
>>
>> Peter
>>
>>
>> Am 08.01.2013 13:55, schrieb Peter Klügl:
>>> Hi,
>>>
>>> next question about "Preparing The Sourcecode For The Release".
>>>
>>> I added the jiraVersion property. However, if I try to generate the report
>>> with "mvn changes:jira-report -N", then I get an exception:
>>>
>>> org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
>>> Caused by: org.xml.sax.SAXParseException: The element type "meta" must be
>>> terminated by the matching end-tag "</meta>".
>>>
>>> A short google search indicates that the configuration in the pom is
>>> probably not correct. However, the related definitions are located in the
>>> org.apache.uima:parent-pom.
>>>
>>> Did I miss something, or do I have to override something in
>>> uimaj-textmarker-parent?
>>>
>>> Best,
>>>
>>> Peter
>>>
>>>
>>> On 21.12.2012 11:12, Peter Klügl wrote:
>>>> Hi,
>>>>
>>>> the next two questions:
>>>>
>>>> 1.  Release Discussions - Release Plan
>>>>
>>>> http://uima.apache.org/release.html says: "At the beginning of the "UIMA
>>>> Release Process" there must be consensus in the developer community about
>>>> the JIRA issues that should be part of the next release and the time frame
>>>> for the release..."
>>>>
>>>> Here's a list of unresolved issues:
>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20TextMarker%20ORDER%20BY%20priority%20DESC
>>>>
>>>> UIMA-2285 (Write documentation for the TextMarker projects) will be
>>>> resolved before the release as it is almost done.
>>>> UIMA-2528 (Open CAS Editor blocks eclipse start) is almost a blocker, but I
>>>> fear that I won't be able to change anything in the TextMarker projects
>>>> that will fix this problem.
>>>>
>>>> If there are no objections, then I will to move all the unresolved issues
>>>> to the next version (2.0.1).
>>>>
>>>>
>>>> 2. Preparing the Jira for the Release
>>>>
>>>> "...and that the "Fixed in release xxx" is set for each Jira issue that is
>>>> part of the release."
>>>>
>>>> "There is a saved "filter" you can adjust for this that will display all
>>>> fixed Jira issues with no Fixed in release xxx assigned. You can go through
>>>> subsets of this (use the filter to pick the subset you want) and do "bulk
>>>> Jira changes" to update multiples of these in parallel, if that makes sense."
>>>>
>>>> Is this necessary that all issues are updated as it will be the first
>>>> relase of the TextMarker system? And if yes, where can I find this filter?
>>>>
>>>>
>>>> Peter
>>>>
>>>>
>>>> On 12.12.2012 17:33, Peter Klügl wrote:
>>>>> Hmm, good point. Then, I prefer 2.0.0
>>>>>
>>>>> Peter
>>>>>
>>>>> On 12.12.2012 17:28, Jörn Kottmann wrote:
>>>>>> On 12/12/2012 05:21 PM, Peter Klügl wrote:
>>>>>>> Ok, after all comments, I think the TextMarker release number should be
>>>>>>> 1.0.0.
>>>>>>>
>>>>>>
>>>>>> It will confuse people when you release under a lower version number as
>>>>>> you did before.
>>>>>> I suggest to increment the version either to 1.6.0 or if there have been
>>>>>> significant changes to
>>>>>> 2.0.0.
>>>>>>
>>>>>>> Jörn, do you have an opinion about the additional CAS Editor views
>>>>>>> (uimaj-ep-textmarker-caseditor)? They have no dependency to TextMarker,
>>>>>>> only to the two CAS Editor projects. I will simply release them together
>>>>>>> with TextMarker.
>>>>>>
>>>>>> +1
>>>>>>
>>>>>> Jörn
>>>>
>>>>
>
>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Hi,

next question about "Building The Release Candidate"

I did now a trial build of the release candidate with "mvn install 
-Papache-release". The only thing that looks not correct is the naming 
of the pom for the Eclipse plugins, for example:

org.apache.uima.textmarker.addons_${parsedVersion.osgiVersion}.pom

Do I have to take care of that? This happens also for the CAS Editor 
plugin in my workspace.

What is the next step? Should I already add the server properties to my 
settings.xml as described here [1], or is there an intermediate step, 
e.g., uploading the trial to my people.apache.org webspace?

Best,

Peter

[1] http://maven.apache.org/developers/committer-settings.html


On 08.01.2013 22:40, Peter Klügl wrote:
> I have found the problem by taking a closer look at the uima-as pom.  
> -> plugin version + config
>
> Can someone verify if the org.apache.uima:parent-pom works correctly? 
> It did not work for me and I think it needs to be updates for Jira >4.
> The maven-changes-plugin version points to 2.6, for example.
>
> Peter
>
>
> Am 08.01.2013 13:55, schrieb Peter Klügl:
>> Hi,
>>
>> next question about "Preparing The Sourcecode For The Release".
>>
>> I added the jiraVersion property. However, if I try to generate the 
>> report with "mvn changes:jira-report -N", then I get an exception:
>>
>> org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA 
>> XML.
>> Caused by: org.xml.sax.SAXParseException: The element type "meta" 
>> must be terminated by the matching end-tag "</meta>".
>>
>> A short google search indicates that the configuration in the pom is 
>> probably not correct. However, the related definitions are located in 
>> the org.apache.uima:parent-pom.
>>
>> Did I miss something, or do I have to override something in 
>> uimaj-textmarker-parent?
>>
>> Best,
>>
>> Peter
>>
>>
>> On 21.12.2012 11:12, Peter Klügl wrote:
>>> Hi,
>>>
>>> the next two questions:
>>>
>>> 1.  Release Discussions - Release Plan
>>>
>>> http://uima.apache.org/release.html says: "At the beginning of the 
>>> "UIMA Release Process" there must be consensus in the developer 
>>> community about the JIRA issues that should be part of the next 
>>> release and the time frame for the release..."
>>>
>>> Here's a list of unresolved issues: 
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20TextMarker%20ORDER%20BY%20priority%20DESC
>>>
>>> UIMA-2285 (Write documentation for the TextMarker projects) will be 
>>> resolved before the release as it is almost done.
>>> UIMA-2528 (Open CAS Editor blocks eclipse start) is almost a 
>>> blocker, but I fear that I won't be able to change anything in the 
>>> TextMarker projects that will fix this problem.
>>>
>>> If there are no objections, then I will to move all the unresolved 
>>> issues to the next version (2.0.1).
>>>
>>>
>>> 2. Preparing the Jira for the Release
>>>
>>> "...and that the "Fixed in release xxx" is set for each Jira issue 
>>> that is part of the release."
>>>
>>> "There is a saved "filter" you can adjust for this that will display 
>>> all fixed Jira issues with no Fixed in release xxx assigned. You can 
>>> go through subsets of this (use the filter to pick the subset you 
>>> want) and do "bulk Jira changes" to update multiples of these in 
>>> parallel, if that makes sense."
>>>
>>> Is this necessary that all issues are updated as it will be the 
>>> first relase of the TextMarker system? And if yes, where can I find 
>>> this filter?
>>>
>>>
>>> Peter
>>>
>>>
>>> On 12.12.2012 17:33, Peter Klügl wrote:
>>>> Hmm, good point. Then, I prefer 2.0.0
>>>>
>>>> Peter
>>>>
>>>> On 12.12.2012 17:28, Jörn Kottmann wrote:
>>>>> On 12/12/2012 05:21 PM, Peter Klügl wrote:
>>>>>> Ok, after all comments, I think the TextMarker release number 
>>>>>> should be 1.0.0.
>>>>>>
>>>>>
>>>>> It will confuse people when you release under a lower version 
>>>>> number as you did before.
>>>>> I suggest to increment the version either to 1.6.0 or if there 
>>>>> have been significant changes to
>>>>> 2.0.0.
>>>>>
>>>>>> Jörn, do you have an opinion about the additional CAS Editor 
>>>>>> views (uimaj-ep-textmarker-caseditor)? They have no dependency to 
>>>>>> TextMarker, only to the two CAS Editor projects. I will simply 
>>>>>> release them together with TextMarker.
>>>>>
>>>>> +1
>>>>>
>>>>> Jörn
>>>
>>>

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
I tried running this on the current build/parent-pom (just to test), and got
that same error: failed to parse JIRA XML - the meta tag missing a closing element.

I agree it's broken :-)

I'll post a JIRA.  I may try to work on this also if I get some time, but others
should feel free to do that (use the Jira "assigned" to indicate you're doing this).

-Marshall
On 1/8/2013 4:40 PM, Peter Klügl wrote:
> I have found the problem by taking a closer look at the uima-as pom.  ->
> plugin version + config
>
> Can someone verify if the org.apache.uima:parent-pom works correctly? It did
> not work for me and I think it needs to be updates for Jira >4.
> The maven-changes-plugin version points to 2.6, for example.
>
> Peter
>
>
> Am 08.01.2013 13:55, schrieb Peter Klügl:
>> Hi,
>>
>> next question about "Preparing The Sourcecode For The Release".
>>
>> I added the jiraVersion property. However, if I try to generate the report
>> with "mvn changes:jira-report -N", then I get an exception:
>>
>> org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
>> Caused by: org.xml.sax.SAXParseException: The element type "meta" must be
>> terminated by the matching end-tag "</meta>".
>>
>> A short google search indicates that the configuration in the pom is probably
>> not correct. However, the related definitions are located in the
>> org.apache.uima:parent-pom.
>>
>> Did I miss something, or do I have to override something in
>> uimaj-textmarker-parent?
>>
>> Best,
>>
>> Peter
>>
>>
>> On 21.12.2012 11:12, Peter Klügl wrote:
>>> Hi,
>>>
>>> the next two questions:
>>>
>>> 1.  Release Discussions - Release Plan
>>>
>>> http://uima.apache.org/release.html says: "At the beginning of the "UIMA
>>> Release Process" there must be consensus in the developer community about
>>> the JIRA issues that should be part of the next release and the time frame
>>> for the release..."
>>>
>>> Here's a list of unresolved issues:
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20TextMarker%20ORDER%20BY%20priority%20DESC
>>>
>>> UIMA-2285 (Write documentation for the TextMarker projects) will be resolved
>>> before the release as it is almost done.
>>> UIMA-2528 (Open CAS Editor blocks eclipse start) is almost a blocker, but I
>>> fear that I won't be able to change anything in the TextMarker projects that
>>> will fix this problem.
>>>
>>> If there are no objections, then I will to move all the unresolved issues to
>>> the next version (2.0.1).
>>>
>>>
>>> 2. Preparing the Jira for the Release
>>>
>>> "...and that the "Fixed in release xxx" is set for each Jira issue that is
>>> part of the release."
>>>
>>> "There is a saved "filter" you can adjust for this that will display all
>>> fixed Jira issues with no Fixed in release xxx assigned. You can go through
>>> subsets of this (use the filter to pick the subset you want) and do "bulk
>>> Jira changes" to update multiples of these in parallel, if that makes sense."
>>>
>>> Is this necessary that all issues are updated as it will be the first relase
>>> of the TextMarker system? And if yes, where can I find this filter?
>>>
>>>
>>> Peter
>>>
>>>
>>> On 12.12.2012 17:33, Peter Klügl wrote:
>>>> Hmm, good point. Then, I prefer 2.0.0
>>>>
>>>> Peter
>>>>
>>>> On 12.12.2012 17:28, Jörn Kottmann wrote:
>>>>> On 12/12/2012 05:21 PM, Peter Klügl wrote:
>>>>>> Ok, after all comments, I think the TextMarker release number should be
>>>>>> 1.0.0.
>>>>>>
>>>>>
>>>>> It will confuse people when you release under a lower version number as
>>>>> you did before.
>>>>> I suggest to increment the version either to 1.6.0 or if there have been
>>>>> significant changes to
>>>>> 2.0.0.
>>>>>
>>>>>> Jörn, do you have an opinion about the additional CAS Editor views
>>>>>> (uimaj-ep-textmarker-caseditor)? They have no dependency to TextMarker,
>>>>>> only to the two CAS Editor projects. I will simply release them together
>>>>>> with TextMarker.
>>>>>
>>>>> +1
>>>>>
>>>>> Jörn
>>>
>>>
>
>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
I have found the problem by taking a closer look at the uima-as pom.  -> 
plugin version + config

Can someone verify if the org.apache.uima:parent-pom works correctly? It 
did not work for me and I think it needs to be updates for Jira >4.
The maven-changes-plugin version points to 2.6, for example.

Peter


Am 08.01.2013 13:55, schrieb Peter Klügl:
> Hi,
>
> next question about "Preparing The Sourcecode For The Release".
>
> I added the jiraVersion property. However, if I try to generate the 
> report with "mvn changes:jira-report -N", then I get an exception:
>
> org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
> Caused by: org.xml.sax.SAXParseException: The element type "meta" must 
> be terminated by the matching end-tag "</meta>".
>
> A short google search indicates that the configuration in the pom is 
> probably not correct. However, the related definitions are located in 
> the org.apache.uima:parent-pom.
>
> Did I miss something, or do I have to override something in 
> uimaj-textmarker-parent?
>
> Best,
>
> Peter
>
>
> On 21.12.2012 11:12, Peter Klügl wrote:
>> Hi,
>>
>> the next two questions:
>>
>> 1.  Release Discussions - Release Plan
>>
>> http://uima.apache.org/release.html says: "At the beginning of the 
>> "UIMA Release Process" there must be consensus in the developer 
>> community about the JIRA issues that should be part of the next 
>> release and the time frame for the release..."
>>
>> Here's a list of unresolved issues: 
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20TextMarker%20ORDER%20BY%20priority%20DESC
>>
>> UIMA-2285 (Write documentation for the TextMarker projects) will be 
>> resolved before the release as it is almost done.
>> UIMA-2528 (Open CAS Editor blocks eclipse start) is almost a blocker, 
>> but I fear that I won't be able to change anything in the TextMarker 
>> projects that will fix this problem.
>>
>> If there are no objections, then I will to move all the unresolved 
>> issues to the next version (2.0.1).
>>
>>
>> 2. Preparing the Jira for the Release
>>
>> "...and that the "Fixed in release xxx" is set for each Jira issue 
>> that is part of the release."
>>
>> "There is a saved "filter" you can adjust for this that will display 
>> all fixed Jira issues with no Fixed in release xxx assigned. You can 
>> go through subsets of this (use the filter to pick the subset you 
>> want) and do "bulk Jira changes" to update multiples of these in 
>> parallel, if that makes sense."
>>
>> Is this necessary that all issues are updated as it will be the first 
>> relase of the TextMarker system? And if yes, where can I find this 
>> filter?
>>
>>
>> Peter
>>
>>
>> On 12.12.2012 17:33, Peter Klügl wrote:
>>> Hmm, good point. Then, I prefer 2.0.0
>>>
>>> Peter
>>>
>>> On 12.12.2012 17:28, Jörn Kottmann wrote:
>>>> On 12/12/2012 05:21 PM, Peter Klügl wrote:
>>>>> Ok, after all comments, I think the TextMarker release number 
>>>>> should be 1.0.0.
>>>>>
>>>>
>>>> It will confuse people when you release under a lower version 
>>>> number as you did before.
>>>> I suggest to increment the version either to 1.6.0 or if there have 
>>>> been significant changes to
>>>> 2.0.0.
>>>>
>>>>> Jörn, do you have an opinion about the additional CAS Editor views 
>>>>> (uimaj-ep-textmarker-caseditor)? They have no dependency to 
>>>>> TextMarker, only to the two CAS Editor projects. I will simply 
>>>>> release them together with TextMarker.
>>>>
>>>> +1
>>>>
>>>> Jörn
>>
>>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Hi,

next question about "Preparing The Sourcecode For The Release".

I added the jiraVersion property. However, if I try to generate the 
report with "mvn changes:jira-report -N", then I get an exception:

org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
Caused by: org.xml.sax.SAXParseException: The element type "meta" must 
be terminated by the matching end-tag "</meta>".

A short google search indicates that the configuration in the pom is 
probably not correct. However, the related definitions are located in 
the org.apache.uima:parent-pom.

Did I miss something, or do I have to override something in 
uimaj-textmarker-parent?

Best,

Peter


On 21.12.2012 11:12, Peter Klügl wrote:
> Hi,
>
> the next two questions:
>
> 1.  Release Discussions - Release Plan
>
> http://uima.apache.org/release.html says: "At the beginning of the 
> "UIMA Release Process" there must be consensus in the developer 
> community about the JIRA issues that should be part of the next 
> release and the time frame for the release..."
>
> Here's a list of unresolved issues: 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20TextMarker%20ORDER%20BY%20priority%20DESC
>
> UIMA-2285 (Write documentation for the TextMarker projects) will be 
> resolved before the release as it is almost done.
> UIMA-2528 (Open CAS Editor blocks eclipse start) is almost a blocker, 
> but I fear that I won't be able to change anything in the TextMarker 
> projects that will fix this problem.
>
> If there are no objections, then I will to move all the unresolved 
> issues to the next version (2.0.1).
>
>
> 2. Preparing the Jira for the Release
>
> "...and that the "Fixed in release xxx" is set for each Jira issue 
> that is part of the release."
>
> "There is a saved "filter" you can adjust for this that will display 
> all fixed Jira issues with no Fixed in release xxx assigned. You can 
> go through subsets of this (use the filter to pick the subset you 
> want) and do "bulk Jira changes" to update multiples of these in 
> parallel, if that makes sense."
>
> Is this necessary that all issues are updated as it will be the first 
> relase of the TextMarker system? And if yes, where can I find this 
> filter?
>
>
> Peter
>
>
> On 12.12.2012 17:33, Peter Klügl wrote:
>> Hmm, good point. Then, I prefer 2.0.0
>>
>> Peter
>>
>> On 12.12.2012 17:28, Jörn Kottmann wrote:
>>> On 12/12/2012 05:21 PM, Peter Klügl wrote:
>>>> Ok, after all comments, I think the TextMarker release number 
>>>> should be 1.0.0.
>>>>
>>>
>>> It will confuse people when you release under a lower version number 
>>> as you did before.
>>> I suggest to increment the version either to 1.6.0 or if there have 
>>> been significant changes to
>>> 2.0.0.
>>>
>>>> Jörn, do you have an opinion about the additional CAS Editor views 
>>>> (uimaj-ep-textmarker-caseditor)? They have no dependency to 
>>>> TextMarker, only to the two CAS Editor projects. I will simply 
>>>> release them together with TextMarker.
>>>
>>> +1
>>>
>>> Jörn
>
>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Hi,

the next two questions:

1.  Release Discussions - Release Plan

http://uima.apache.org/release.html says: "At the beginning of the "UIMA 
Release Process" there must be consensus in the developer community 
about the JIRA issues that should be part of the next release and the 
time frame for the release..."

Here's a list of unresolved issues: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20TextMarker%20ORDER%20BY%20priority%20DESC

UIMA-2285 (Write documentation for the TextMarker projects) will be 
resolved before the release as it is almost done.
UIMA-2528 (Open CAS Editor blocks eclipse start) is almost a blocker, 
but I fear that I won't be able to change anything in the TextMarker 
projects that will fix this problem.

If there are no objections, then I will to move all the unresolved 
issues to the next version (2.0.1).


2. Preparing the Jira for the Release

"...and that the "Fixed in release xxx" is set for each Jira issue that 
is part of the release."

"There is a saved "filter" you can adjust for this that will display all 
fixed Jira issues with no Fixed in release xxx assigned. You can go 
through subsets of this (use the filter to pick the subset you want) and 
do "bulk Jira changes" to update multiples of these in parallel, if that 
makes sense."

Is this necessary that all issues are updated as it will be the first 
relase of the TextMarker system? And if yes, where can I find this filter?


Peter


On 12.12.2012 17:33, Peter Klügl wrote:
> Hmm, good point. Then, I prefer 2.0.0
>
> Peter
>
> On 12.12.2012 17:28, Jörn Kottmann wrote:
>> On 12/12/2012 05:21 PM, Peter Klügl wrote:
>>> Ok, after all comments, I think the TextMarker release number should 
>>> be 1.0.0.
>>>
>>
>> It will confuse people when you release under a lower version number 
>> as you did before.
>> I suggest to increment the version either to 1.6.0 or if there have 
>> been significant changes to
>> 2.0.0.
>>
>>> Jörn, do you have an opinion about the additional CAS Editor views 
>>> (uimaj-ep-textmarker-caseditor)? They have no dependency to 
>>> TextMarker, only to the two CAS Editor projects. I will simply 
>>> release them together with TextMarker.
>>
>> +1
>>
>> Jörn

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Hmm, good point. Then, I prefer 2.0.0

Peter

On 12.12.2012 17:28, Jörn Kottmann wrote:
> On 12/12/2012 05:21 PM, Peter Klügl wrote:
>> Ok, after all comments, I think the TextMarker release number should 
>> be 1.0.0.
>>
>
> It will confuse people when you release under a lower version number 
> as you did before.
> I suggest to increment the version either to 1.6.0 or if there have 
> been significant changes to
> 2.0.0.
>
>> Jörn, do you have an opinion about the additional CAS Editor views 
>> (uimaj-ep-textmarker-caseditor)? They have no dependency to 
>> TextMarker, only to the two CAS Editor projects. I will simply 
>> release them together with TextMarker.
>
> +1
>
> Jörn

Re: Questions about TextMarker release

Posted by Jörn Kottmann <ko...@gmail.com>.
On 12/12/2012 05:21 PM, Peter Klügl wrote:
> Ok, after all comments, I think the TextMarker release number should 
> be 1.0.0.
>

It will confuse people when you release under a lower version number as 
you did before.
I suggest to increment the version either to 1.6.0 or if there have been 
significant changes to
2.0.0.

> Jörn, do you have an opinion about the additional CAS Editor views 
> (uimaj-ep-textmarker-caseditor)? They have no dependency to 
> TextMarker, only to the two CAS Editor projects. I will simply release 
> them together with TextMarker.

+1

Jörn

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Ok, after all comments, I think the TextMarker release number should be 
1.0.0.

Jörn, do you have an opinion about the additional CAS Editor views 
(uimaj-ep-textmarker-caseditor)? They have no dependency to TextMarker, 
only to the two CAS Editor projects. I will simply release them together 
with TextMarker.

Peter

On 12.12.2012 16:36, Marshall Schor wrote:
> On 12/12/2012 8:10 AM, Peter Klügl wrote:
>> On 12.12.2012 13:57, Jörn Kottmann wrote:
>>> On 12/12/2012 01:53 PM, Peter Klügl wrote:
>>>> Thanks for the answers.
>>>>
>>>> The next question: What about the version number of the TextMarker release?
>>>>
>>> If you align with the UIMA releases you are somehow bound to its development
>>> cycle, in
>>> case you want to release more frequently this could be problematic.
>>>
>> Yes, at least for the beginning this can be problematic. However, I do not
>> know if it is better to start with 1.0.0 or even 0.1.0.
>>
>> Is there a possibility for releases with sub-versions or additional build
>> numbers? Then again, the more frequent releases would be especially of the
>> type "maintenance", which corresponds to the third digit.
> Maven only supports 3 levels x.y.z for versions, I think.  (not sure if that was
> your question, though). -Marshall
>> Peter
>>

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
On 12/12/2012 8:10 AM, Peter Klügl wrote:
> On 12.12.2012 13:57, Jörn Kottmann wrote:
>> On 12/12/2012 01:53 PM, Peter Klügl wrote:
>>> Thanks for the answers.
>>>
>>> The next question: What about the version number of the TextMarker release?
>>>
>>
>> If you align with the UIMA releases you are somehow bound to its development
>> cycle, in
>> case you want to release more frequently this could be problematic.
>>
>
> Yes, at least for the beginning this can be problematic. However, I do not
> know if it is better to start with 1.0.0 or even 0.1.0.
>
> Is there a possibility for releases with sub-versions or additional build
> numbers? Then again, the more frequent releases would be especially of the
> type "maintenance", which corresponds to the third digit.

Maven only supports 3 levels x.y.z for versions, I think.  (not sure if that was
your question, though). -Marshall
>
> Peter
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
> One thing we did in UIMA for this kind of a change was to deliver a code-change
> tool.  IIRC, it walked over a user source tree and and did a bunch of
> rename-like changes. 
> 
> http://uima.apache.org/d/uimaj-2.4.0/overview_and_setup.html#ugr.project_overview_migrating_from_ibm_uima

I wasn't thinking of following that example. But I hope that there will be a way that for some time uimaFIT and Apache uimaFIT components can just peacefully coexist - even for people which cannot just recompile their codebase. Switching to the Apache version shouldn't involve much more than changing the dependency and doing a global "Organize Imports" I think. As I said, I'll dig into that.

-- Richard

-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
On 12/12/2012 8:38 AM, Richard Eckart de Castilho wrote:
>>> You could also want to make minor or major releases independent from the UIMA release cycle, e.g. when you introduce new features, change the script grammar or do other potentially incompatible changes (e.g. fully qualified type names and aliases for them? ;) ).
>> Yes, I agree.
>>
>> What about the version numbers of uimafit? Do they remain the same (1.5.0)?
>>
>> …btw... after uimafit completely arrived, we need to talk about how TextMarker can interact better with the uimafit concepts :-)
> I'd rather tend towards a 2.0.0 since all the package names and stuff will change. It's going to be interesting if and what kind of backwards compatibility can be provided. I have yet to dive down into the dirty details.

One thing we did in UIMA for this kind of a change was to deliver a code-change
tool.  IIRC, it walked over a user source tree and and did a bunch of
rename-like changes. 

http://uima.apache.org/d/uimaj-2.4.0/overview_and_setup.html#ugr.project_overview_migrating_from_ibm_uima

-Marshall
>
> -- Richard
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
The latest uimaFIT release is 1.4.0.

-- Richard

> What was the version of your last non-Apache release?
> 
> Jörn
> 
> On 12/12/2012 02:38 PM, Richard Eckart de Castilho wrote:
>>>> You could also want to make minor or major releases independent from the UIMA release cycle, e.g. when you introduce new features, change the script grammar or do other potentially incompatible changes (e.g. fully qualified type names and aliases for them? ;) ).
>>> Yes, I agree.
>>> 
>>> What about the version numbers of uimafit? Do they remain the same (1.5.0)?
>>> 
>>> …btw... after uimafit completely arrived, we need to talk about how TextMarker can interact better with the uimafit concepts :-)
>> I'd rather tend towards a 2.0.0 since all the package names and stuff will change. It's going to be interesting if and what kind of backwards compatibility can be provided. I have yet to dive down into the dirty details.
>> 
>> -- Richard


-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Sorry, should have read your mail more closely ;-)

On 12.12.2012 14:48, Peter Klügl wrote:
> I did not care too much about good release cycles/versioning. It was 
> just 1.0.0.qualifier.
>
> I already broke with backwards compability straightaway, so I have no 
> problem to start with a completely new version number.
>
> Peter
>
> On 12.12.2012 14:40, Jörn Kottmann wrote:
>> What was the version of your last non-Apache release?
>>
>> Jörn
>>
>> On 12/12/2012 02:38 PM, Richard Eckart de Castilho wrote:
>>>>> You could also want to make minor or major releases independent 
>>>>> from the UIMA release cycle, e.g. when you introduce new features, 
>>>>> change the script grammar or do other potentially incompatible 
>>>>> changes (e.g. fully qualified type names and aliases for them? ;) ).
>>>> Yes, I agree.
>>>>
>>>> What about the version numbers of uimafit? Do they remain the same 
>>>> (1.5.0)?
>>>>
>>>> …btw... after uimafit completely arrived, we need to talk about how 
>>>> TextMarker can interact better with the uimafit concepts :-)
>>> I'd rather tend towards a 2.0.0 since all the package names and 
>>> stuff will change. It's going to be interesting if and what kind of 
>>> backwards compatibility can be provided. I have yet to dive down 
>>> into the dirty details.
>>>
>>> -- Richard
>>>

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
I did not care too much about good release cycles/versioning. It was 
just 1.0.0.qualifier.

I already broke with backwards compability straightaway, so I have no 
problem to start with a completely new version number.

Peter

On 12.12.2012 14:40, Jörn Kottmann wrote:
> What was the version of your last non-Apache release?
>
> Jörn
>
> On 12/12/2012 02:38 PM, Richard Eckart de Castilho wrote:
>>>> You could also want to make minor or major releases independent 
>>>> from the UIMA release cycle, e.g. when you introduce new features, 
>>>> change the script grammar or do other potentially incompatible 
>>>> changes (e.g. fully qualified type names and aliases for them? ;) ).
>>> Yes, I agree.
>>>
>>> What about the version numbers of uimafit? Do they remain the same 
>>> (1.5.0)?
>>>
>>> …btw... after uimafit completely arrived, we need to talk about how 
>>> TextMarker can interact better with the uimafit concepts :-)
>> I'd rather tend towards a 2.0.0 since all the package names and stuff 
>> will change. It's going to be interesting if and what kind of 
>> backwards compatibility can be provided. I have yet to dive down into 
>> the dirty details.
>>
>> -- Richard
>>

Re: Questions about TextMarker release

Posted by Jörn Kottmann <ko...@gmail.com>.
What was the version of your last non-Apache release?

Jörn

On 12/12/2012 02:38 PM, Richard Eckart de Castilho wrote:
>>> You could also want to make minor or major releases independent from the UIMA release cycle, e.g. when you introduce new features, change the script grammar or do other potentially incompatible changes (e.g. fully qualified type names and aliases for them? ;) ).
>> Yes, I agree.
>>
>> What about the version numbers of uimafit? Do they remain the same (1.5.0)?
>>
>> …btw... after uimafit completely arrived, we need to talk about how TextMarker can interact better with the uimafit concepts :-)
> I'd rather tend towards a 2.0.0 since all the package names and stuff will change. It's going to be interesting if and what kind of backwards compatibility can be provided. I have yet to dive down into the dirty details.
>
> -- Richard
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
>> You could also want to make minor or major releases independent from the UIMA release cycle, e.g. when you introduce new features, change the script grammar or do other potentially incompatible changes (e.g. fully qualified type names and aliases for them? ;) ).
> 
> Yes, I agree.
> 
> What about the version numbers of uimafit? Do they remain the same (1.5.0)?
> 
> …btw... after uimafit completely arrived, we need to talk about how TextMarker can interact better with the uimafit concepts :-)

I'd rather tend towards a 2.0.0 since all the package names and stuff will change. It's going to be interesting if and what kind of backwards compatibility can be provided. I have yet to dive down into the dirty details.

-- Richard

-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
>
> You could also want to make minor or major releases independent from the UIMA release cycle, e.g. when you introduce new features, change the script grammar or do other potentially incompatible changes (e.g. fully qualified type names and aliases for them? ;) ).
>
> -- Richard
>

Yes, I agree.

What about the version numbers of uimafit? Do they remain the same (1.5.0)?

...btw... after uimafit completely arrived, we need to talk about how 
TextMarker can interact better with the uimafit concepts :-)

Peter

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
+1 -Marshall
On 12/12/2012 8:17 AM, Richard Eckart de Castilho wrote:
> Am 12.12.2012 um 14:10 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
>> On 12.12.2012 13:57, Jörn Kottmann wrote:
>>> On 12/12/2012 01:53 PM, Peter Klügl wrote:
>>>> Thanks for the answers.
>>>>
>>>> The next question: What about the version number of the TextMarker release?
>>>>
>>> If you align with the UIMA releases you are somehow bound to its development cycle, in
>>> case you want to release more frequently this could be problematic.
>>>
>> Yes, at least for the beginning this can be problematic. However, I do not know if it is better to start with 1.0.0 or even 0.1.0.
>>
>> Is there a possibility for releases with sub-versions or additional build numbers? Then again, the more frequent releases would be especially of the type "maintenance", which corresponds to the third digit.
>
> You could also want to make minor or major releases independent from the UIMA release cycle, e.g. when you introduce new features, change the script grammar or do other potentially incompatible changes (e.g. fully qualified type names and aliases for them? ;) ).
>
> -- Richard
>

Re: Questions about TextMarker release

Posted by Richard Eckart de Castilho <ec...@ukp.informatik.tu-darmstadt.de>.
Am 12.12.2012 um 14:10 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
> On 12.12.2012 13:57, Jörn Kottmann wrote:
>> On 12/12/2012 01:53 PM, Peter Klügl wrote:
>>> Thanks for the answers.
>>> 
>>> The next question: What about the version number of the TextMarker release?
>>> 
>> 
>> If you align with the UIMA releases you are somehow bound to its development cycle, in
>> case you want to release more frequently this could be problematic.
>> 
> 
> Yes, at least for the beginning this can be problematic. However, I do not know if it is better to start with 1.0.0 or even 0.1.0.
> 
> Is there a possibility for releases with sub-versions or additional build numbers? Then again, the more frequent releases would be especially of the type "maintenance", which corresponds to the third digit.


You could also want to make minor or major releases independent from the UIMA release cycle, e.g. when you introduce new features, change the script grammar or do other potentially incompatible changes (e.g. fully qualified type names and aliases for them? ;) ).

-- Richard

-- 
------------------------------------------------------------------- 
Richard Eckart de Castilho
Technical Lead
Ubiquitous Knowledge Processing Lab (UKP-TUD) 
FB 20 Computer Science Department      
Technische Universität Darmstadt 
Hochschulstr. 10, D-64289 Darmstadt, Germany 
phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
eckart@ukp.informatik.tu-darmstadt.de 
www.ukp.tu-darmstadt.de 
Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
-------------------------------------------------------------------

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
On 12.12.2012 13:57, Jörn Kottmann wrote:
> On 12/12/2012 01:53 PM, Peter Klügl wrote:
>> Thanks for the answers.
>>
>> The next question: What about the version number of the TextMarker 
>> release?
>>
>
> If you align with the UIMA releases you are somehow bound to its 
> development cycle, in
> case you want to release more frequently this could be problematic.
>

Yes, at least for the beginning this can be problematic. However, I do 
not know if it is better to start with 1.0.0 or even 0.1.0.

Is there a possibility for releases with sub-versions or additional 
build numbers? Then again, the more frequent releases would be 
especially of the type "maintenance", which corresponds to the third digit.

Peter

Re: Questions about TextMarker release

Posted by Jörn Kottmann <ko...@gmail.com>.
On 12/12/2012 01:53 PM, Peter Klügl wrote:
> Thanks for the answers.
>
> The next question: What about the version number of the TextMarker 
> release?
>

If you align with the UIMA releases you are somehow bound to its 
development cycle, in
case you want to release more frequently this could be problematic.

Jörn

Re: Questions about TextMarker release

Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Thanks for the answers.

The next question: What about the version number of the TextMarker release?

The projects are developed against the head of the svn and therefore the 
current version is also 2.4.1-SNAPSHOT.
TextMarker should work just fine with uimaj-(core, ...)-2.4.0, but I do 
not remember right now, what changes of the CAS Editor are already 
released in 2.4.0. I got no compile errors yet when I set the dependency 
for the CAS Editor to 2.4.0. However, I need more testing here.

So, 2.4.0 it would be? Or is an alignment, e.g., to other Eclipse-based 
tooling, not necessary?

Are there any best practices for that? I am thinking, for example, about 
the version of the parent pom. Do I have to create a new workspace with 
some UIMA projects in the 2.4.0 revision?

Best,

Peter



On 12.12.2012 02:39, Marshall Schor wrote:
> <snip>
>> - Is there a release manager for this?
> You can be the release manager, or someone else could.  The RM is just the
> person pushing through all the steps to get the release done.
>
>> I guess that I will do the complete release, right? I do not even know if I
>> have the rights for all steps.
> You should have all the rights.  If not, we'll get that fixed :-)
>
>> - Is it recommended to create an "aggregate-uimaj-textmarker" project?
> A popular method for users to interact with our source, is to check out some
> portion of the tree they're interested in , and do mvn install.  Right now, if
> you check out the TextMarker directory (which has all the other projects in it),
> it appears that
>    - the projects are "flat" - all exist as children of the top TextMarker directory
>    - there is no overall "pom" the containing TextMarker directory - it has no
> files, only the subdirectories.
>
> I would suggest creating a pom for the entire project, and storing it as a file
> in the TextMarker directory (not in a separate new project called
> aggregate-uimaj-textmarker).  This pom's purpose would be to do the aggregation
> (via <modules>) of all the subprojects that normally ought to be built when a
> user wants to build from source.
>
>> - How does it work with the documentation? The pdf has more than 80 pages
>> right now. I created a book for the developement, but maybe it's better if the
>> TextMarker documentation stays in its own book?
> Sure, that's sounds correct.  Some other sandbox projects also have docbook
> documentation.
>
>> I was reading  much about doing a release, but I do not know if all applies
>> one-to-one on the TextMarker projects.
> We'll only discover what is needed as we go step by step through the process :-).
>
> -Marshall

Re: Questions about TextMarker release

Posted by Marshall Schor <ms...@schor.com>.
<snip>
> - Is there a release manager for this? 

You can be the release manager, or someone else could.  The RM is just the
person pushing through all the steps to get the release done.

> I guess that I will do the complete release, right? I do not even know if I
> have the rights for all steps.

You should have all the rights.  If not, we'll get that fixed :-)

> - Is it recommended to create an "aggregate-uimaj-textmarker" project?

A popular method for users to interact with our source, is to check out some
portion of the tree they're interested in , and do mvn install.  Right now, if
you check out the TextMarker directory (which has all the other projects in it),
it appears that
  - the projects are "flat" - all exist as children of the top TextMarker directory
  - there is no overall "pom" the containing TextMarker directory - it has no
files, only the subdirectories.

I would suggest creating a pom for the entire project, and storing it as a file
in the TextMarker directory (not in a separate new project called
aggregate-uimaj-textmarker).  This pom's purpose would be to do the aggregation
(via <modules>) of all the subprojects that normally ought to be built when a
user wants to build from source.

> - How does it work with the documentation? The pdf has more than 80 pages
> right now. I created a book for the developement, but maybe it's better if the
> TextMarker documentation stays in its own book?

Sure, that's sounds correct.  Some other sandbox projects also have docbook
documentation.

>
> I was reading  much about doing a release, but I do not know if all applies
> one-to-one on the TextMarker projects.


We'll only discover what is needed as we go step by step through the process :-).

-Marshall