uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <...@schor.com>
Subject Re: TextMarker maven build process update
Date Thu, 28 Jun 2012 18:29:46 GMT
I'm not sure what Eclipse artifacts you need; did you try seeing if they are in
this repository:

http://maven.eclipse.org/nexus/index.html#welcome?

-Marshall
On 6/28/2012 12:58 PM, Peter Klügl wrote:
>  On 28.06.2012 17:44, Marshall Schor wrote:
>> If a public repo can't be found, do you use the
>> http://maven.apache.org/plugins/maven-eclipse-plugin/to-maven-mojo.html plugin
>> for adding the eclipse plugins to the local repo, as part of your build?
>>
>> -Marshall
>>
>
> Yes, I am doing this right now manually with eclipse:make-artifacts
> (http://maven.apache.org/plugins/maven-eclipse-plugin/make-artifacts-mojo.html).
> My maven knowledge isn't yet good enough to get the idea to include that in
> the build process. That a good idea, but won't we get problems for an
> automatic build in future since you have to provide the Eclipse installation
> dir? Could we provide that on a build server some time in future?
>
> Peter
>
>
>
>> On 6/28/2012 11:38 AM, Marshall Schor wrote:
>>> Is there not a "public" repository for the bundles you need?  I'm looking
>>> around
>>> for one...
>>>
>>> -Marshall
>>> On 6/28/2012 11:34 AM, Peter Klügl wrote:
>>>>   Hi,
>>>>
>>>>> Hi Peter,
>>>>>
>>>>> I'm sorry if I've missed the thread - has it been discussed why the Eclipse
>>>>> plugins can't be built with the pom-first approach that our current Eclipse
>>>>> plugins are built with?
>>>>>
>>>> No, they can be and are actually built this way right now. Everything works
>>>> fine, if you add a complete Eclipse Indigo release with DLTK Core 3.0
>>>> installed to your local maven repository. I think that the pom-first build
is
>>>> only reasonable if the user does not have to do that, but we can provide
a
>>>> repository like that somehow.
>>>>
>>>> Building the bundles the manifest-first way does not have such problems
>>>> because the dependencies are automatically resolved using p2 repositories.
In
>>>> my opinion, that is a much nicer solution and should work just fine. However,
>>>> after the time I spent with this problem and with hardly any progress, I
must
>>>> admit that I don't care too much anymore about how the bundles are built.
>>>>
>>>> Is a repository for the bundles an option for us?
>>>>
>>>> Best,
>>>>
>>>>   Peter
>>>>
>>>>
>>>
>
>



Mime
View raw message