[ 
https://issues.apache.org/jira/browse/UIMA-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495416#comment-13495416
 ] 

Marshall Schor commented on UIMA-2475:
--------------------------------------

Following on Peter's suggestion for a future Eclipse update site process - here 
are some thoughts.

1) I originally "felt bad" about putting binaries like plugin jars, etc., into 
SVN.  I still wonder if this the right place for "built" objects like this.  
But, the Apache infrastructure people seem to like this approach - the whole 
release mechanism is moving toward this kind of thing.  So, perhaps I should 
"get over it" :-).

2) In addition to the idea of having a separate project for the update site 
and/or P2 repository (we already have a separate project for this - 
"uimaj-eclipse-update-site" in the uimaj component), I suggest we have a new, 
1-level up thing (a "component", like uimaj, uima-as, addons, builds, site), 
that would be for special binary packagings (builds) of our code.  If the only 
thing in this (for the foreseeable future) would be the eclipse update site, 
then I would call this something like eclipse-packagings.  It would have the 
update site and the feature and categories information for how we're organizing 
these things, as "projects".  It would have it's own versioning, because it 
would be updated more frequently than our normal releases.  (The individual 
plugins which were tied to other components like the uimaj-ep-configurator, 
would continue to carry their particular versions).


                
> eclipse p2 update site instead of old-style update site
> -------------------------------------------------------
>
>                 Key: UIMA-2475
>                 URL: https://issues.apache.org/jira/browse/UIMA-2475
>             Project: UIMA
>          Issue Type: Bug
>          Components: Eclipse plugins
>            Reporter: Steven Bethard
>            Assignee: Peter Klügl
>         Attachments: uimaj-eclipse-update-site.zip
>
>
> The UIMA Eclipse update site (www.apache.org/dist/uima/eclipse-update-site) 
> is an Eclipse 3.3 (or older) update site. Since Eclipse 3.4, the recommended 
> update site layout is p2:
> http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Releng#Why_should_I_make_changes_to_adopt_p2.3F
> I've been bitten by this update site issue because old-style update sites 
> make it impossible to resolve build-time dependencies when building Eclipse 
> plugins:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=380438#c3
> Could the UIMA update site be modernized to the p2 layout?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to