Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [lyo-dev] OSLC4J project names in the rio repo
Dear all,

I like also Steve's suggestion for using org.eclipse.<project-name>.<component>.<oslc-domain>.<rio|client|...> as project naming convetion.

I think it is more elegant using project name like:

* org.eclipse.lyo.oslc4j.am.rio
* org.eclipse.lyo.oslc4j.cm.rio
* org.eclipse.lyo.oslc4j.qm.rio

but "am" or "cm", as you said, are ambiguous. Thus, I vote for:

* org.eclipse.lyo.oslc4j.archmgmt.rio
* org.eclipse.lyo.oslc4j.archmgmt.client

* org.eclipse.lyo.oslc4j.changemgmt.rio
* org.eclipse.lyo.oslc4j.changemgmt.client

* org.eclipse.lyo.oslc4j.configmnt.rio
* org.eclipse.lyo.oslc4j.configmnt.client

* org.eclipse.lyo.oslc4j.qualitymgmt.rio
* org.eclipse.lyo.oslc4j.qualitymgmt.client

...

The build project names can be as follows:

* org.eclipse.lyo.oslc4j.core.releng.builds (for org.eclipse.lyo.core repo)
* org.eclipse.lyo.oslc4j.rio.releng.builds
* org.eclipse.lyo.oslc4j.client.releng.builds


At the same time, I suggest re-structuring also repositories as follows:

org.eclipse.lyo.oslc4j.core/rio/client
 + plugins - containing plug-in projects
 + features - containing feature projects
 + examples - containing example projects
 + tests - containing test projects
 + releng - containing release engineering aspects

Separately, should the "common" projects be moved to a different repo?

"common" projects can be located inside the "plugins" folder...

Question:
Currently the goal of lyo is not providing OSLC4J as Eclipse projects.
To facilitate Lyo OSLC4J's integration with other existing Eclipse projects, is there planned to provide also an Eclipse SDK version and/or p2 repository containing Eclipse projects/features?

Best regards,

Idrissa DIENG
Technology Manager, itemis France.



2013/8/19 Sean Kennedy <seanpk@xxxxxxxxxx>

This is moderately related to a previous topic on renaming the OSLC4J projects [1].

There is a slightly off-topic discussion in bug 415365 [2] that I'd like to bring onto the mailing list.

Basically it starts with the suggestion that the OSLC4J-based RIOs should have "rio" in their project/package name, e.g.:
org.eclipse.lyo.oslc4j.changemanagement > org.eclipse.lyo.oslc4j.changemanagement.rio

Steve Speicher then suggested that he prefers:
"org.eclipse.lyo.oslc4j.cm as the "parent" project identifier for all things developed using oslc4j for CM and then attach right "sub names" such as: ".rio", ".client", etc."

In principle I like Steve's suggestion, but I have the concern that for people new to OSLC the meaning of CM is ambiguous, i.e. is the C for Change or Configuration?
(Also the same with AM ... is that Asset or Architecture?)

On the Communications wiki there are some naming suggestions [3] that might be good to apply here. If those are followed, then the RIO for Change Management could be called:
org.eclipse.lyo.oslc4j.changemgmt.rio

That said, now that the whole discussion of projects in the RIO package is open, it seems odd to me that any of these packages have "oslc4j" in their names.
Do they extend OSLC4J and are a reusable asset for developers? I think the projects named "common" do, but only them. And in their case, isn't it strange that they're in the rio repo?

Here is a proposal to throw stones at:
Given the short names from the naming guidelines [3], rename as follows
org.eclipse.lyo.oslc4j.$long_name --> org.eclipse.lyo.rio.$short_name
org.eclipse.lyo.oslc4j.$long_name.common --> org.eclipse.lyo.oslc4j.$short_name
org.eclipse.lyo.oslc4j.$long_name.test --> org.eclipse.lyo.rio.$short_name.test

e.g. for Change Management:
org.eclipse.lyo.oslc4j.changemanagement --> org.eclipse.lyo.rio.changemgmt
org.eclipse.lyo.oslc4j.changemanagement.common --> org.eclipse.lyo.oslc4j.changemgmt
org.eclipse.lyo.oslc4j.changemanagement.test --> org.eclipse.lyo.rio.changemgmt.test

Separately, should the "common" projects be moved to a different repo?

[1]: http://dev.eclipse.org/mhonarc/lists/lyo-dev/msg00411.html
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=415365
[3]: http://open-services.net/wiki/communications/Workgroup-and-Spec-Naming-Style/

Best regards,

Sean Kennedy 
IBM
OSLC Community Development Leader for IBM Rational  
Operations Coordinator for the OSLC Steering Committee  
     
Phone:+1-905-413-4385 8200 Warden Ave
Fax:+1-905-413-4850 Markham, Ontario L6G 1C7
Email:seanpk@xxxxxxxxxx D1/R0A/8200/MKM
LinkedIn:http://www.linkedin.com/in/seanpk Canada
   
OSLC: Lifecycle integration inspired by the web http://open-services.net
Eclipse Lyo: Enabling tool integration with OSLC http://eclipse.org/lyo
 
There is nothing more powerful than an idea whose time has come. -- Victor Hugo
   


Inactive hide details for Samuel Padgett ---2013/07/15 11:38:01 AM---Thanks, I opened this bug: https://bugs.eclipse.org/bugs/sSamuel Padgett ---2013/07/15 11:38:01 AM---Thanks, I opened this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=412988

From: Samuel Padgett <spadgett@xxxxxxxxxx>
To: Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>,
Cc: lyo-dev-bounces@xxxxxxxxxxx
Date: 2013/07/15 11:38 AM
Subject: Re: [lyo-dev] Any objections to changing OSLC4J project names?
Sent by: lyo-dev-bounces@xxxxxxxxxxx



Thanks, I opened this bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=412988

I plan to use Idrissa's suggestions.
--
Samuel Padgett | IBM Rational | spadgett@xxxxxxxxxx


Inactive hide details for Sean Kennedy ---07/09/2013 12:54:29 PM---+1 for Idrissa's suggestions Best regards,Sean Kennedy ---07/09/2013 12:54:29 PM---+1 for Idrissa's suggestions Best regards,
    From:

Sean Kennedy <seanpk@xxxxxxxxxx>
    To:

lyo-dev@xxxxxxxxxxx
    Date:

07/09/2013 12:54 PM
    Subject:

Re: [lyo-dev] Any objections to changing OSLC4J project names?
    Sent by:

lyo-dev-bounces@xxxxxxxxxxx



+1 for Idrissa's suggestions


Best regards,
Sean Kennedy 
IBM
OSLC Community Development Leader for IBM Rational  
Operations Coordinator for the OSLC Steering Committee  
     
Phone:+1-905-413-4385 8200 Warden Ave
Fax:+1-905-413-4850 Markham, Ontario L6G 1C7
Email:seanpk@xxxxxxxxxx D1/R0A/8200/MKM
LinkedIn:http://www.linkedin.com/in/seanpk Canada
   
OSLC: Lifecycle integration inspired by the web http://open-services.net
Eclipse Lyo: Enabling tool integration with OSLC http://eclipse.org/lyo
 
There is nothing more powerful than an idea whose time has come. -- Victor Hugo
   


Inactive hide details for Idrissa ---2013/07/09 12:40:37 PM---Hi Samuel, Yes I think it is a good idea to follow the naming conIdrissa ---2013/07/09 12:40:37 PM---Hi Samuel, Yes I think it is a good idea to follow the naming conventions of Eclipse

From: Idrissa <idydieng@xxxxxxxxx>
To: Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>, Samuel Padgett <spadgett@xxxxxxxxxx>, lyo-dev-bounces@xxxxxxxxxxx,
Date: 2013/07/09 12:40 PM
Subject: Re: [lyo-dev] Any objections to changing OSLC4J project names?
Sent by: lyo-dev-bounces@xxxxxxxxxxx



Hi Samuel,

Yes I think it is a good idea to follow the naming conventions of Eclipse projects. But I have a suggestion for Lyo project names: I think rather to:

* org.eclipse.lyo.oslc4j.core
* org.eclipse.lyo.oslc4j.provider.jena
* org.eclipse.lyo.oslc4j.provider.json4j
* org.eclipse.lyo.oslc4j.wink
* ...


2013/7/9 Idrissa <idydieng@xxxxxxxxx>
    Hi Samuel,

    Yes I think it is a good idea to follow the naming conventions of Eclipse projects. But I have a suggestion for Lyo project names: I think rather to:

    * org.eclipse.lyo.oslc4j.core
    * org.eclipse.lyo.oslc4j.provider.jena
    * org.eclipse.lyo.oslc4j.provider.json4j
    * org.eclipse.lyo.oslc4j.wink
    * ...


    2013/7/9 Samuel Padgett <    spadgett@xxxxxxxxxx>
      I am considering changing the OSLC4J project names to match the conventions used elsewhere in Lyo. So instead of

      OSLC4J/

      we'd have

      org.eclipse.lyo.core.oslc4j/

      (and the same for the other dozen or so projects). Does anyone object?

      If you have these projects loaded, you will probably need to remove them from your Eclipse workspace and re-import them. We will also need to update the Lyo wiki pages and Hudson build scripts for the new names.
      --
      Samuel Padgett | IBM Rational |       spadgett@xxxxxxxxxx
      _______________________________________________
      lyo-dev mailing list
      lyo-dev@xxxxxxxxxxx
      https://dev.eclipse.org/mailman/listinfo/lyo-dev



    --
    Cordialement,
    Idrissa Abdoulaye DIENG
    ----------------------------------------



--
Cordialement,
Idrissa Abdoulaye DIENG
---------------------------------------- _______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/lyo-dev
_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/lyo-dev

_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/lyo-dev


_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/lyo-dev


GIF image

GIF image

GIF image

GIF image

Back to the top